[Q] XT926 issue - waiting for device topic

Phone: Droid Razr HD XT926, locked bootloader, was rooted, not sure now
Issue: OTAs had not worked for awhile, but I wanted to go to KitKat. So, I tried to use Matt's 1.41 utility. I may not have had the most up-to-date Motorola USB drivers when I started. The update did not work. Now, I just get the "Motorola Logo and Dual Core Technology text", but phone then goes black. I am able to get to AP fastboot screen, but all attempts to re-try Matt's 1.41 utility, or the House of Moto 4.1, or RSD Lite 6.2.4 are unsuccessful. All of them show <waiting for device>.

Any ideas why I can't get past <waiting for device>?

Fastboot screen:
Device is LOCKED. Status Code: 0
Battery OK
Transfer Mode:
USB Connected

Fastboot Reason: Boot menu selected

[Q&A] Is this it, is this the root for retail we have been waiting for, maybe? topic

Q&A for Is this it, is this the root for retail we have been waiting for, maybe?

Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.

Before posting, please use the forum search and read through the discussion thread for Is this it, is this the root for retail we have been waiting for, maybe?. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.

Thanks for understanding and for helping to keep XDA neat and tidy! :)

Is this it, is this the root for retail we have been waiting for, maybe? topic

Note: I am not responsible for anything that might happen to your device. Please make a backup if possible or please make sure you know how to restore your phone back to factory using the correct stock roms. This Note 4 Developer forum does have resources to do so. Before proceeding below, please ensure you have tried to restore from stock roms via ODIN 3.09 (or correct version), as it may be the only way to recover your device.

The post here suggests (but untested / verified on a retail Verizon Note 4 NJ5) that a system.img.ext4 image, with root (Super SU), can be flashed using ODIN 3.09 to a retail device. I ask more experienced developers to try this first, and post your responses here. I will cite / note the steps which I have done below. I really hope other developers assist in the verification process - let me know if this works or not. I will pull this post if in fact this process fails


Using EFS Professional v2.1.80 Beta and a Verizon Note 4 Developer Edition SM-N910V, on the 4.4.4 version N910VVRU1ANJ5, did the following.

0. Restored the SM-N910V (Developer) to near stock - the only thing different was the recovery partition which had been previously flashed to TWRP

1. Downloaded UPDATE-SuperSU-v2.16.zip from this post (also where TWRP came from), and with my Note 4 connected to a PC, copied the zip file to the phone; rebooted into recovery, flashed Super SU with TWRP. Now it's rooted, right? restarted phone. Installed Busybox (required by EFS Professional), prompted me for root access, permission granted. Busybox ran. Good.

2. Used EFS Professional to backup the previously rooted system.img.ext4, saved as SM-N910V_2015130_0116.tar (on android file host)

3. Using TWRP, reflashed my phone back to stock before root. Used ODIN 3.09 with my phone in download mode, flashed the SM-N910V_2015130_0116.tar back to my Developer edition, performed a factory reset, rebooted, did a minimal phone setup (bailed out of setup when I could) but Used the busybox.apk (stericson) to test root; installed it using the unknown resources option, ran it, it asked for root, I assume this was a sign that the ODIN flash went well and root held...

So, what remains - asking the developer community to test flashing the SM-N910V_2015130_0116.tar on a retail device using ODIN AP Mode, I do not have one to test...

Here is what I'm hoping for. That the SM-N910V_2015130_0116.tar can be successfully flashed to a retail device, which will then be fortified with root, yes. Maybe that can lead to the "promised land" where a developer, again - more talented than me, can find a weakness in the retail version, from within, to obtain root by other means; unless what I have done, is it!! If it is. Excellent...

If this does work on a retail verizon Note 4 (NJ5), excellent, glad to have helped. If there is a bounty due, ok, I suppose I could accept but not expecting it. I am more excited to give back to the community who has so given their precious time / resources... and so it goes...

Again, please let me know if this worked. I will down this thread immediately if it is detrimental to devices...

Rob

[Q] Note 3 [OCTA] When it official lollipop official arrive it been years waiting ? topic

:confused::confused::confused::confused:

[Q] Waiting for device while easy rooting kit topic

Hi, I was root my sp before then I install lollipop rom and I dont like this , so ı want to install stock room ı use flashtool to install stock room ı installed but while use easyrooting kit to rooting my photo the cmd stuck at the waiting for devide ı did usb debugging and the others sorry for my bad english please help my how to root my xperia and install cmw menu then upgrade 4.3 ı did one time but in this time not working