Downgrade to 902 - No app or data loss

[nastygullom]

You mean like it says to do in the OP? LOL! Yes. The script will push any zip files found in the updates folder to your sdcard-ext, so, when a new leak comes out you put it in the updates dir and you're good to go.

Thanks! You all rock!!

 

[rduckwor]

Interesting afternoon.

I had a couple of hours and decided to upgrade to 232 using Sam and dfib's script.

I had a forced close yesterday on the home screen of all things, so it was time to move on from 230.

Well, all went well , or so I thought.

When I finished up, I wiped the cache and rebooted and immediately got the Android is upgrading message. Went thru 100 files and then the fun began.

All sorts of errors and fc's as the device was loading the software .

I ended up powering down and rebooting into recovery. Ran the upgrade for 902->905 and it failed like I expected. Ran the 905-> 232 and it failed.

So I resigned myself to an FXZ recovery.

Loaded the software up and extracted the file.

FXZ failed?

Damn!! Loaded another XML file and it failed again.

Oh, oh. I was beginning to feel a bit screwed, but resolved to press forward.

Pulled the battery a couple of times, booted into recovery and wiped the cache, fooled around and finally I got it to boot into 232 from recovery. I don't know how, I don't know why, but it booted. I signed to Google and the torrent of downloads began.

The handset is running now but the issue is that if I power off, and power on, it opens the AP fastboot screen with the message "flash failed" instead of the normal boot cycle.

I can boot from recovery into 232 and it runs O.K.

Don't know where to go from here, but I can live with it if necessary.

Verified that I have 232 on the phone and it seems to work well so far aside for the power up issue.

Help me remember, how do I get Gmail to stop making noise for every new email received?

Thanks,

RMD

 

[SamuriHL]

I can't stress this enough....if you have issues with the ICS build you're already on, using my script to update to another is not really the best of ideas. You're taking corrupt data from one build and hoping against all hope that somehow it magically works in the new build. Recipe for disaster now being served. Always try to resolve those kinds of issues BEFORE doing the script to update to a new build. Remedies include things like wiping the cache, wiping dalvik, fixing permissions, etc.

As for your boot issue, you need to flash something, anything, successfully in fastboot and it'll go away.

 

[rduckwor]

I can't stress this enough....if you have issues with the ICS build you're already on, using my script to update to another is not really the best of ideas. You're taking corrupt data from one build and hoping against all hope that somehow it magically works in the new build. Recipe for disaster now being served. Always try to resolve those kinds of issues BEFORE doing the script to update to a new build. Remedies include things like wiping the cache, wiping dalvik, fixing permissions, etc.

As for your boot issue, you need to flash something, anything, successfully in fastboot and it'll go away.

Yep. Live and learn. I'll get it straightened out.

RMD

 

[SamuriHL]

Yep. Live and learn. I'll get it straightened out.

RMD

I know you will. My warning was mostly meant for others who may find themselves in a similar situation. The same power of the script to keep your data around can also be a curse if your data is messed up. Fun times ain't it?

 

[SamuriHL]

@shawner47 & @fastpakr

I've updated the OP with your new links. Thanks!!

 

[SamuriHL]

shawner47 pointed out a very minor error in the script. Those using my full or lite packages will not run into it ever so it's NOT something anyone needs to worry about. I've uploaded the fixed version just for completeness. It's an error in the check for adb...if adb.exe is missing, the error message won't display properly. Absolutely no functionality is affected by this issue. If you're concerned, grab the latest. Otherwise ignore it since you likely have adb.exe in your dir anyway so you'll never ever hit the bug. Thanks for pointing it out, shawner47!

 

[rduckwor]

I know you will. My warning was mostly meant for others who may find themselves in a similar situation. The same power of the script to keep your data around can also be a curse if your data is messed up. Fun times ain't it?

Yeah, the bleeding edge. I had forgotten what fun it can be.

Nice piece of work you guys pulled off. Moto should put you on the payroll.

RMD

 

[mranderson1]

both menus are flawless samuri!

 

[mranderson1]

I can't stress this enough....if you have issues with the ICS build you're already on, using my script to update to another is not really the best of ideas. You're taking corrupt data from one build and hoping against all hope that somehow it magically works in the new build. Recipe for disaster now being served. Always try to resolve those kinds of issues BEFORE doing the script to update to a new build. Remedies include things like wiping the cache, wiping dalvik, fixing permissions, etc.

As for your boot issue, you need to flash something, anything, successfully in fastboot and it'll go away.

all these noobs! lol....live and learn = D

 

[jcwilliams]

Hey we are all noobs at one point! Lol

 

[SamuriHL]

Exactly. There are the real masters that are in a league of their own. Those that create roms, the root exploits we use, and generally lead our community. Those of us that try to bring all that work together to make for easier consumption are NOT the real heroes of the community. The people who are creating the things we use are the ones who deserve our utmost respect. But even they were newbies at one point. Just keep that in mind.

 

[Camoxjeep]

ok dumb question, which file to I check the check sum against LOL ? thanks

Edit, nevermind figured it out LOL it was the whole zip file. thanks

EDIT again
Just ran the latest script and it ran flawless. Thanks for everyone that made this possible.

 

[Dieselgeek]

Question... I am finally on ICS, but have an issue. I can't boot into recovery mode. I can't select anything in the bootloader actually. If I boot into recovery from Titanium, I get the android with needing surgery logo (red exclamation). With qe 1/1 shown. What did I do wrong, how might I go about fixing it?

Thank you to all who made the leak possible!

 

[Bigv5150]

, mine does the exact same thing and then when I hit the up and down volume at same time it puts me into recovery and I can choose whatever I want but yes the android does look different from when I was on gingerbread