ICS 6.7.232

[Yaish]

I've flashed over to .232 now and it seems snappier. I'm still on 1ghz, likely that's hardware and there's nothing for it.

I used your script SamuriHL, it worked perfectly this time. The all in one package was awesome too.

I actually ran the script twice because the first time I forgot to swap for the new leak, so I flashed to .230 again. I added the new update to the folder and it worked perfectly.

Sent from my DROID BIONIC using Android Central Forums

 

[matthimrod]

Interesting discovery. Once you flash ICS or FXZ back to a previous version and are using Google Authenticator, you will need to set it up again from the start. You have to log into your account (better have your backup codes handy) and you need to remove your device from authentication and add your "new" device.

Authentication Help

Authenticator doesn't tie in with your account, it stores information necessary to generate the authentication codes locally. You can actually restore it with Titanum Backup -- if you backed it up.

 

[Lee_Bo]

Authenticator doesn't tie in with your account, it stores information necessary to generate the authentication codes locally. You can actually restore it with Titanum Backup -- if you backed it up.

Well according to all that I have read, it is associated with your account. But that a discussion for another thread.

I tried restoring from Titanum but found out some apps either didn't work at all, gave massive force close issues, or only worked some of the time. Once I uninstalled and reinstalled the apps that were giving issues, everything was fine. I figured since I was trying a new leak, I would start with all fresh app installs.

 

[matthimrod]

Well according to all that I have read, it is associated with your account. But that a discussion for another thread.

I tried restoring from Titanum but found out some apps either didn't work at all, gave massive force close issues, or only worked some of the time. Once I uninstalled and reinstalled the apps that were giving issues, everything was fine. I figured since I was trying a new leak, I would start with all fresh app installs.

Well, yes, it's probably a discussion for another thread, but for the sake of trying to be helpful: The app doesn't have any account level permissions to sync with your account, otherwise you wouldn't need the QR-code business when you set it up with your device -- that's what associates wit with your account. So you either need a backup of it or to re-scan the barcode to relink it with your device. What I've done in the past is save the image of the QR code in a safe place so that when I flash a new ROM I can easily re-set it up.

 

[SamuriHL]

Yep, sure did. All the other .902 files loaded fine, but when it got to that last webtop file, the script gave some sort of error. It said that .902 installed successfully, but obviously it didn't.

Sent from my DROID BIONIC using Android Central Forums

I'm not sure what could have happened on that. Webtop REQUIRES the actual moto-fastboot.exe which I do include in my zips. Some of the versions floating around are renamed fastboot.exe which is not capable of flashing webtop. But if you used the zip version of my script then it should have simply worked.

 

[SamuriHL]

I had the same happen to me when I used it to flash to .230. I modified the script and inserted some pauses after every reboot command sent to the phone... seems to me like fastboot was trying to send files to the phone before the phone was ready for them.

Very possible. I just told others that they can add either a pause or a PING 127.0.0.1 -n 10 > NUL line to add a pause after each one.

 

[DroidST]

are you posting about adding a pause in front of both mbmloader and cdt.bin?

That is what I suggest in the other forum...

I was going to insert those and re-do the process but I think I will just wait for the next leak

 

[SamuriHL]

Yes it was posted by me.

For those having issues with flash errors, try modifying the following lines in the script to do this:

adb reboot bootloader
PING 127.0.0.1 -n 10 > NUL
moto-fastboot flash mbm allow-mbmloader-flashing-mbm.bin
moto-fastboot reboot-bootloader
PING 127.0.0.1 -n 10 > NUL
moto-fastboot flash mbmloader mbmloader.bin
moto-fastboot flash mbm mbm.bin
moto-fastboot reboot-bootloader
PING 127.0.0.1 -n 10 > NUL
moto-fastboot flash cdt.bin cdt.bin

 

[Lee_Bo]

So you either need a backup of it or to re-scan the barcode to relink it with your device. What I've done in the past is save the image of the QR code in a safe place so that when I flash a new ROM I can easily re-set it up.

Ah ha!! I'm glad one of us was thinking. Now to make a backup of the QR code and save it along with my back up codes. Thanks for the tip.

 

[Ry]

Up and running 232. Seems snappier. I'll give it a few days.

 

[SamuriHL]

I'm also up and running finally. That script is pretty darn handy. I managed to completely screw up my phone and was able to get it back from a nandroid and upgrade it to 232 with no problems or data/app loss.

 

[hokiesteve]

Well, yes, it's probably a discussion for another thread, but for the sake of trying to be helpful: The app doesn't have any account level permissions to sync with your account, otherwise you wouldn't need the QR-code business when you set it up with your device -- that's what associates wit with your account. So you either need a backup of it or to re-scan the barcode to relink it with your device. What I've done in the past is save the image of the QR code in a safe place so that when I flash a new ROM I can easily re-set it up.

That's brilliant keeping a screen capture and printout of the QR code in addition to the backup codes.

 

[SamuriHL]

For those using my script I updated my post with a new RUNME.zip (contains a new version of RUNME.bat). It has the pauses we've discussed as well as some cleaned up text.

 

[hokiesteve]

The newest leak seems great, especially now that webtop is working. It certainly makes for a much more functional webtop user experience than the old motorola one.

There's one issue i've noticed with this leak as well as one or two of the previous ones. Facebook seems to chew up a lot of CPU and battery, even when it's not active. Has anyone else noticed this?

 

[Ry]

For those using my script I updated my post with a new RUNME.zip (contains a new version of RUNME.bat). It has the pauses we've discussed as well as some cleaned up text.

Excellent work.

I'm still using your old script. I just manually put the phone in Fastboot mode then run the batch file. Now all I'm doing is swapping out the ICS leak file on my SD card.

Sent from my DROID BIONIC using Android Central Forums

 

[Ry]

Let's Golf 2 is on this version. I was able to Uninstall it (vs. Disable).

Forest Live Wallpaper is here. I don't remember that being on 230.

Sent from my DROID BIONIC using Android Central Forums

 

[jimdibb]

HELP please, I may be in trouble.
My bionic was already on the 905 OTA. I got your v2 zip download and the new RUNME.bat.

Ran it. Said it flashed back to 902. Now the script says install 905. My sdcard doesn't have 905 on it, only 893XT875 and the 905 to 232 files.

Can I use the 905 to 232 file because I was already at 905?
Thanks!!

 

[SamuriHL]

Um....if you don't have the 905 file on your sdcard-ext then my script didn't run properly. I include the 905 update in the updates folder and push it to your phone. Any way you can shut the phone down, pull the sdcard and put it in a card reader so you can copy the 905 update to it? You are definitely not on 905 now if you ran my script. Although you can probably just boot 902 and do an OTA update since you've not been on ICS yet. That should be a decent option, actually.

 

[Ry]

HELP please, I may be in trouble.
My bionic was already on the 905 OTA. I got your v2 zip download and the new RUNME.bat.

Ran it. Said it flashed back to 902. Now the script says install 905. My sdcard doesn't have 905 on it, only 893XT875 and the 905 to 232 files.

Can I use the 905 to 232 file because I was already at 905?
Thanks!!

You need to be on 905 to flash to any of the ICS leaks. You were at 905 but since you flashed back, you're now on 902.

I take no responsibility for what happens next, but I would shut the phone off. Then pull out the SD card and put the 902 to 905 file on it (root directory, just as the 905 to 232 file should be). Boot the phone back into Recovery, then flash to 905, then flash to 232, then wipe the cache, then reboot normally.


Sent from my DROID BIONIC using Android Central Forums

 

[jimdibb]

Ok, i will do that... but I just downloaded SamuriHL_HouseofBionic.v2.w6.7.232 and the updates folder on the zip file has no 5.9.905, only 5.9.902 and 5.9.905 to6.7.232 Did I get the wrong one?

Now I have to find a 5.9.905 file I guess.(?)