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

[nofxdan]

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".

 

[OutOfPhase]

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.

 

[nofxdan]

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

 

[nofxdan]

Ok, so after a bunch of tinkering, I was able to get it rooted again.

I disabled/enabled USB Debugging, and restarted adb in USB mode. After that, I ran R3L34S3DRoot.bat, and it worked without a hitch.

I'm willing to guess the problem was related to USB debugging.

 

[SNeitzel]

I got that error at one point as well and a reboot of the PC fixed it.

 

[johnlgalt]

Easier to kill the ADB service and then restart it - and usually a lot faster too

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.