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
Just added this to the troubleshooting section:
Just did some testing. Those of you that have adb, you could change the first moto-fastboot reboot-bootloader to adb reboot bootloader and that seems to work as an alternative.
If you drop adb into the same dir and edit the RUNME.bat it'll reboot it for you. No idea why moto-fastboot is failing, but, I guess it's driver related.
Just did some testing. Those of you that have adb, you could change the first moto-fastboot reboot-bootloader to adb reboot bootloader and that seems to work as an alternative.
If you drop adb into the same dir and edit the RUNME.bat it'll reboot it for you. No idea why moto-fastboot is failing, but, I guess it's driver related.
Can you be more specific about what didn't work with rooting? As long as the razrs_edge_windows dir exists in the same dir as runme.bat it should work. You only continue once the phone has rebooted fully, however.
I wouldn't. I'd let it run and if after a much longer period of time it hasn't finished, only then would I stop it. Stopping a flash can leave things in a REALLY terrible state. If all else fails, you can use the full 902 FXZ to restore your phone.
After 30 minutes I closed the CMD window. I opened a new CMD and manually fastbooted the System, boot, preinstall, webtop, recovery, and erase cache. All successful. Rebooted Recovery and 905 failed so i wiped cache and then successfully flashed 905. 6.7.230 is flashing now. Thank goodness I was fully charged.
Yikes! Well, I'm glad you're up and flashing. No idea why that happened to you. I've done this process a bunch of times and haven't had any issues so far.
Short version:
Start-to-finish, went from .2233 -> .902 -> .905 -> .230 and rooted in under 30 minutes.
Bravo! :hail:
Long version:
Nice script. It was very simple to run once everything was downloaded, extracted, fondled, and set up.
The only glitch that I ran into was that for some reason, if my Bionic is connected to my PC via USB, whenever I boot into the stock recovery screen, the down arrow key does not work. This means that I cannot select any choices other than the highlighted one which is to reboot. So I must disconnect the USB cable prior to booting into stock recovery.
Other than that (and that is certainly not an issue with the script) everything worked start-to-finish in under 30 minutes.
Question:
So that said, I assume that when the OTA is available, we can still run this script and just stop after installing the .905 update (and wiping the cache) and then let the OTA happen as it happens. Correct?
Start-to-finish, went from .2233 -> .902 -> .905 -> .230 and rooted in under 30 minutes.
Bravo! :hail:
Long version:
Nice script. It was very simple to run once everything was downloaded, extracted, fondled, and set up.
The only glitch that I ran into was that for some reason, if my Bionic is connected to my PC via USB, whenever I boot into the stock recovery screen, the down arrow key does not work. This means that I cannot select any choices other than the highlighted one which is to reboot. So I must disconnect the USB cable prior to booting into stock recovery.
Other than that (and that is certainly not an issue with the script) everything worked start-to-finish in under 30 minutes.
Question:
So that said, I assume that when the OTA is available, we can still run this script and just stop after installing the .905 update (and wiping the cache) and then let the OTA happen as it happens. Correct?
Last edited:
Sorry about that. The phone upgraded without a hitch and rebooted into ICS. Then the script asked if i wanted to root. The directories were in the correct place (it stopped me the first time when they were not) and the process ran but any action it tried to take failed because it was unable to write.
Who knows what really happened. All computers and phones are setup different and there is always the Operator Error possibility. Not that I have ever bricked before. LOL. Thanks to Timmy10Shoes I learned moto-fastboot long ago and I am glad. In the end all is well and I learned new things. Still, thanks for your work on the script. I am sure we will get it down.
Odd about recovery. I didn't have that happen at all. Weird. As for your question, I wouldn't. The reason I wrote this script is basically to go from ICS leak to ICS leak without having to boot into a GB build (902 or 905). If you boot 905 with the data and apps from an ICS build there's a better than average chance of something getting screwed up/corrupted/bad evil gremlins. What I would recommend is when the OTA comes out, see if it matches what we already have (it very well may
) and if so, leave things alone. 
If it doesn't, we'll be sure to find the new OTA build and we'll just this process again to manually flash it like we've been doing all the leaks. That is far safer IMO.Uhhhhh, wow. I've not seen that happen at all. Were you able to run root manually after that?
timmy has been awesome. If it weren't for his work my bionic back in December would have been permanently bricked. I'm glad you were able to get it sorted out and get it working. The script is really there to make things easier so I don't like it when it screws up.
Have not tried it yet. I will let you know what happens. Thank you again for the help.