What's new
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

files are correct in the directory.. I have the Win32 fastboot...
I'm thinking that I am comprehending something incorrectly....

the OP states enable USB Debugging, which I have... does the phone need to be booted up fully or does it need to be in fastboot when you start the process?
 
Doesn't matter. I boot into fastboot using quick boot, personally, but, the very first thing the script does is boot into fastboot. Your issue is it's not finding moto-fastboot.exe.
 
Okay, my guess is that you have the Linux fastboot and you are on Windows? Am I correct? You need the Windows 32 fastboot files.


grrrr.... I didn't bother to look farther down the list and actually see the WIN32 file... I just grabbed the 32 which of course failed.
also had to add the 2 .dll's to the dir.

hopefully this is actually working this time... had some strange messages when it first fired up but it looks like it's flashing now.
 
I'm assuming it's going to work this time since I'm now flashing the ICS image.
Thanks for all your help Sam :)

At least NEXT time I'll know what to expect... heh!
 
Sorry for the bumpy road. All these little issues that people encounter and we overcome help make the road smoother for others that come along and try this out. Much appreciated.
 
Ok, running into a bit of a problem. Neither my laptop nor my pc can find my bionic once I start the script. It says flashing 902 an then gets immediately stuck on <waiting for device> Debugging is enabled. I'm rooted. Are there new drivers I need to install since updating to 2233? Any help would be greatly appreciated.
 
Downloaded the device manager, but it was still stuck on <waiting for device>. Just booted into fastboot and it seems like it is working now.
 
Very strange. The very first thing it does is boot into fastboot. Not sure why that's not working for some people. I added a troubleshooting section with advice for that issue. Thanks!
 
Last edited:
Downloaded the device manager, but it was still stuck on <waiting for device>. Just booted into fastboot and it seems like it is working now.

Same here. Despite the drivers being installed, it never detected the phone while it was booted up. Shut down and launched into fastboot, then the script started working.
 
Back
Top