• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root OTA Update Failed, Can't flash FXZ or Root

nofxdan

Newbie
Feb 18, 2010
41
1
The other day while trying to downgrade to receive OTA updates again, RSDLite was getting stuck on "flashing system.img". I finally pulled the plug, and had to use R3L34S3DRoot to get my phone functional again.

Since doing this, I get an "update failed" dialog after trying to do the OTA update, and forever root will not work.

Attached is the problem I am having with forever root...

I have tried factory resets, etc, all to no avail. Any ideas on how to get my phone back to normal, rooted goodness?

edit:
The error I'm receiving is "error: more than one device and emulator".
 

Attachments

  • droid_root_problem.jpg
    droid_root_problem.jpg
    293.8 KB · Views: 94
The other day while trying to downgrade to receive OTA updates again, RSDLite was getting stuck on "flashing system.img". I finally pulled the plug, and had to use R3L34S3DRoot to get my phone functional again.

Since doing this, I get an "update failed" dialog after trying to do the OTA update, and forever root will not work.

Attached is the problem I am having with forever root...

I have tried factory resets, etc, all to no avail. Any ideas on how to get my phone back to normal, rooted goodness?

edit:
The error I'm receiving is "error: more than one device and emulator".


Open a comand promp it windows where you have sdk installed type adb devices and see how many devices show up.
 
Upvote 0
PHP:
0A3BAB0F0100C00C        offline
0A3BAB0F0100C00C        offline
0A3BAB0F0100C00C        offline
0A3BAB0F0100C00C        offline
0A3BAB0F0100C00C        offline
0A3BAB0F0100C00C        offline
0A3BAB0F0100C00C        offline
0A3BAB0F0100C00C        offline
0A3BAB0F0100C00C        offline
0A3BAB0F0100C00C        offline
0A3BAB0F0100C00C        offline
0A3BAB0F0100C00C        offline
0A3BAB0F0100C00C        offline
0A3BAB0F0100C00C        device
 
Upvote 0
Easier to kill the ADB service and then restart it - and usually a lot faster too :p

usually, when you see multiple devices like that, killing the adb service is the best bet - disabling and re-enabling USB debugging might work but I know of at least one person for whom it did not, whereas the reboot of the PC (and hence just a kill / restart of the adb service) will work fine as well.
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones