You're quite welcome. I'd be curious if it works when you run it manually or if you get the same issue. Maybe the phone just needed another reboot. Some of the odd things we've seen with ICS on the bionic are quickly cured by a reboot so it's not impossible to imagine.
DroidForums.net | Android Forum & News
This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!
Downgrade to 902 - No app or data loss
- Thread starter SamuriHL
- Start date
You're quite welcome. I'd be curious if it works when you run it manually or if you get the same issue. Maybe the phone just needed another reboot. Some of the odd things we've seen with ICS on the bionic are quickly cured by a reboot so it's not impossible to imagine.
100% correct. It just rooted without a hitch after I ran it manually.
I had to go to the zip FXZ file and copy that (emstorage.img) over to the directory manually.
Should be 23 files in that directory by my count.
Good Luck,
RMD
Is that line just a direction, can i take it from an older FXZ? Neither of the 902 FXZ's that i have , have that line in it
edit: I just took it from an older FXZ and I still get the white window, saying i am flashed back to 902
edit: I also noticed that even after re naming the RUNME file, to bat, it still shows as a text file in the new folder with 23 lines
edit: changed file to batch by saving in notepad with quotes before and after, just not sure about using the older emstorage.img file
edit: I just took it from an older FXZ and I still get the white window, saying i am flashed back to 902
edit: I also noticed that even after re naming the RUNME file, to bat, it still shows as a text file in the new folder with 23 lines
edit: changed file to batch by saving in notepad with quotes before and after, just not sure about using the older emstorage.img file
Last edited:
Ok, I've updated the OP again and uploaded a new version of the script. There are some significant changes to take care of the troubleshooting issues we've found. First, the script now requires moto-fastboot.exe to be in the 902 FXZ directory. Not just in the path. And the script checks for it....if not found, it will error out of the script. adb.exe is also good to have in the 902 FXZ dir, but, is not required. If it's not found, you will be shown manual instructions on how to reboot into fastboot. Otherwise we use adb.exe to do it for you. I like automation. 
After the moto-fastboot commands I pause to give you a chance to see any errors that may have happened so you can report them. I cleaned up the text for the manual steps a bit. This should make things smoother. As always please report issues as you find them. Thanks all!
After the moto-fastboot commands I pause to give you a chance to see any errors that may have happened so you can report them. I cleaned up the text for the manual steps a bit. This should make things smoother. As always please report issues as you find them. Thanks all!Ok, I've updated the OP again and uploaded a new version of the script. There are some significant changes to take care of the troubleshooting issues we've found. First, the script now requires moto-fastboot.exe to be in the 902 FXZ directory. Not just in the path. And the script checks for it....if not found, it will error out of the script. adb.exe is also good to have in the 902 FXZ dir, but, is not required. If it's not found, you will be shown manual instructions on how to reboot into fastboot. Otherwise we use adb.exe to do it for you. I like automation.
If only motorola/verizon could put out updates as fast as you, we would already be on official Jelly Bean OS.
Sent from my DROID BIONIC using Tapatalk 2
I've been a software engineer for many years. But, remember, I'm not doing as much QA and validation as moto/vzw. You guys are doing a lot of the testing. I just fix it when I can.
SDroidDawg
Member
Like others I got stuck originally at the <waiting for device> Debugging is enabled. I then booted to fastboot and I'm running it again. I am now getting messages that different functions has stopped and then the phone reboots. It has probably restarted 7 times now.
Last edited:
That's really not normal. If you're stuck in a boot loop you may not have much of a choice but to use the full 902 FXZ to restore the phone. That will wipe the data unfortunately. Ugh.
Sent from my Xoom using Tapatalk 2