[UTILITY] Return to GB from ICS fxz script -- Now includes 2.3.6 fxz 09/26/2012

jimbridgman said:

Ok, so you want to return to GB from ICS, right?

Well I have written a script for AT&T users to get back to GB 2.3.5 from ICS with the fxz patched with the same patch the Chinese forum had used.

It is very simple just download the correct file there is a version for windows users in a batch file, and shell script for the Linux and Mac users.

This has been tested and will not brick your phone. We have several confirmed cases that this works Even one of our devs soft bricked on ICS today and was able to get back to 2.3.5 from this.

Windows:

You will download the following zip file:
http://www.androidfilehost.com/main/Motorola_ATRIX_2_Developers/jimbridgman/a2_return_to_gb_win.zip

MD5sum: 85dd75fc711a723837d927c6de6ca1fa

Then unzip the whole thing, do not drag and drop the files, there is an A2_go_back_win directory with all the files in it... extract this directory to either you desktop or C:\ BE VERY CAREFUL YOU DO NOT DRAG JUST THE FILES TO C:\ but you extract the WHOLE directory there.

Then go t your command line (cmd) and cd to either your Desktop or C:\A2_go_back_win then run the restore-to-gb.bat file

Code:

C:\ > cd A2_go_back_win
C:\A2_go_back_win > restore-to-to-gb.bat

Linux and Mac:

You will download the following zip file:
http://www.androidfilehost.com/main/Motorola_ATRIX_2_Developers/jimbridgman/a2_return_to_gb_lm.zip

MD5sum: 58b4c47c02e9ad0a379ca8cc5734687a

unzip the file and go to the command line and cd to where you unzipped the file to and cd into the A2_go_back directory. Then run the return_to_gb.sh shell script

The following is an example of how to run this the directory I use is just and example, please cd to the correct directory you extracted the zip to on your machine.

Code:

$ cd ~/Downloads/A2_go_back
$ ./restore_to_gb.sh

This will ONLY work if you are on ICS, I will get something for 2.3.6 and 2.3.5 from once you have been on ICS, those are "special" cases so PLEASE do not attempt that until further notice.

Thanks to the following users:
jerrycrystal, sky2k4@CHN, mntlion, KEB64, leifmagnuson, seraphielx, ri4naire, Fall of Enosis, jspugh, rdavisct, cogeary, JRW 28, alteredlikeness, a special thanks to dicksteele.

If I forgot you please PM me, all those guys deserve for you hit their thanks button for either testing getting the needed files or other support.

One last thing, if you brick or soft brick I am not responsible, you hacked your phone and made the choice freely, to do so.

Now upward and onward to more android development.

Click to expand...

Click to collapse

Thanks a lot man for all the hard work you have put on this, it's really appreciated. :good:

not working for me this is what I get
after the flash it sits on the red m and never boots


Checking for phone...
0146DDCC09011007 fastboot
If your phone serial did not show up then exit this,
reconnect your phone, and try again!
If you did see the serial then this will continue
Waiting; if you want to cancel press c (Ctrl+C)
Press any key to continue
Press any key to continue . . .
Allowing bootloader flashing
sending 'mbm' (256 KB)... OKAY [ 0.032s]
writing 'mbm'... OKAY [ 0.470s]
Flashing bootloader mbm.bin
sending 'mbm' (256 KB)... OKAY [ 0.242s]
writing 'mbm'... OKAY [ 0.464s]
Rebooting into bootloader
rebooting into bootloader... OKAY [ 0.281s]
Flashing cdt.bin
sending 'cdt.bin' (16 KB)... FAILED (command write failed (No such file or
directory))
Erasing userdata
erasing 'userdata'... FAILED (command write failed (No such file or
directory))
Erasing cache
erasing 'cache'... FAILED (command write failed (No such file or
directory))
Flashing lbl
sending 'lbl' (16 KB)... FAILED (command write failed (No such file or
directory))
Flashing logo.bin
sending 'logo.bin' (854 KB)... FAILED (command write failed (No such file or
directory))
Flashing ebr
sending 'ebr' (16 KB)... FAILED (command write failed (No such file or
directory))
Flashing mbr
< waiting for device >
sending 'mbr' (16 KB)... OKAY [ 0.010s]
writing 'mbr'... OKAY [ 0.469s]
flashing device_tree.bin
sending 'devtree' (512 KB)... OKAY [ 0.351s]
writing 'devtree'... OKAY [ 0.519s]
Flashing System
sending 'system' (262144 KB)... OKAY [ 24.863s]
writing 'system'... OKAY [ 29.543s]
sending 'system' (229120 KB)... OKAY [ 21.285s]
writing 'system'... OKAY [ 25.757s]
Flashing Boot image
sending 'boot' (8192 KB)... OKAY [ 0.779s]
writing 'boot'... OKAY [ 1.408s]
flashing recovery
sending 'recovery' (9216 KB)... OKAY [ 1.120s]
writing 'recovery'... OKAY [ 1.833s]
Flashing Radio
sending 'radio' (12080 KB)... OKAY [ 1.362s]
writing 'radio'... OKAY [ 1.467s]
Flashing cdrom
sending 'cdrom' (12032 KB)... OKAY [ 1.357s]
writing 'cdrom'... INFOPreflash validation failure
FAILED (remote: )
Flashing preinstall
sending 'preinstall' (262144 KB)... OKAY [ 23.968s]
writing 'preinstall'... OKAY [ 29.349s]
sending 'preinstall' (20480 KB)... OKAY [ 1.945s]
writing 'preinstall'... OKAY [ 1.893s]
Flashing webtop, This will take a LONG time, be patient
sending 'webtop' (262144 KB)...

OK, now that we have a way back, is there any reason to do it for those of us on scv7?
when the ota comes out im sure the development will go crazy.
is this only useful for those that want to have the "official" update? a backup and boot menu should fix most issues with a soft brick right?

thank you for all the time and effort that everyone have put into this!!!

Thanks a lot jim And thanks a lot "Chinese Guy" ^_^

Got few questions :

1.Only At n T users ? I guess thats coz is that the only leak ?
2.Will this work only on ICS leak or will work on SC v7 too ?
3. Back to 2.3.5 and the 2.3.6 OTA can be done as usual ?

regards.

Archmag3 said:

Thanks a lot jim And thanks a lot "Chinese Guy" ^_^

Got few questions :

1.Only At n T users ? I guess thats coz is that the only leak ?
2.Will this work only on ICS leak or will work on SC v7 too ?
3. Back to 2.3.5 and the 2.3.6 OTA can be done as usual ?

regards.

Click to expand...

Click to collapse

1. Yes it is for AT&T users. Jim says that in the first line of the the post.
2. Yes, it should work for SC v7 also as it is based on the same firmware (someone can correct me if I am wrong on this)
3. Yes, I know this for sure, cause I tested it, and I OTA'd to 2.3.6 no problem. :good:

I used the china fix and flashed with rsd with out any issues game back on!

For anybody who runs this, if it doesn't go through the first time, just run it again. Its a great utility.

Sent from my MB865 using xda premium

Hey Jim, do you have a script for 2.3.6 to 2.3.5

Tooooooo laaaatttteeeee for me ....

Hope all of you guys will be happy with this .............

Can I get a confidence factor on when the ICS OTA is released that those of us that are on the leak, then return to 2.3.6 using this script, will be alright, even regarding that one file that is ignored? As I said in another thread, I am patiently waiting for the OTA to happen before I go back from the leak, but I want to know how confident the devs feel that the storm is over and its safe to come out from our rocks.

For the record, I am running the leak, rooted, no other build.prop mods or scv7 or anything, about as 'stock' as it can be.

jimbridgman said:

Cool.. sorry you had issues. Not sure what happened. Glad you got back up and running.

Sent from my SAMSUNG-SGH-I747 using xda premium

Click to expand...

Click to collapse

who knows my machines hate me haha just waiting for the push now

jimbridgman said:

just 2.3.6 to 2.3.5, or did you EVER install the ICS leak?

If you did not install the ICS leak, then yes I have a script that this one was ripped from, that I have already completed, and been through beta testing here on the board. If you EVER installed ICS, I do not have a script to get you from 2.3.6 to 2.3.5, just yet, but I am doing some testing for that.

If you want my a2_all_in_one script let me know through PM, and I will reply to you with it.

Don't everyone PM me asking for it. It will be released to everyone very soon, and I will have an option in it to include the script posted in this thread as well, in the near future and before I release to everyone

Click to expand...

Click to collapse

Jim, correct me if I'm wrong, but (assuming they have installed the ICS leak) could they just go from 2.3.6 to the leak and then use your script again to get back to 2.3.5? I know that's a round-a-bout way. I'm also confirming this for my own interest: If you've already installed leak, but got your way back to 2.3.5 using your script and then ota to 2.3.6, you would have to go the route of installing the leak again in order to get back to stock 2.3.5, right? Otherwise, you would just have to wait for the new script? My apologies if this is obvious...

After flashing this, what BL will we have? 0A.65 or 0A.72?

CapnPez said:

Jim, correct me if I'm wrong, but (assuming they have installed the ICS leak) could they just go from 2.3.6 to the leak and then use your script again to get back to 2.3.5? I know that's a round-a-bout way. I'm also confirming this for my own interest: If you've already installed leak, but got your way back to 2.3.5 using your script and then ota to 2.3.6, you would have to go the route of installing the leak again in order to get back to stock 2.3.5, right? Otherwise, you would just have to wait for the new script? My apologies if this is obvious...

Click to expand...

Click to collapse

The only problem with that is that you can't mod 2.3.6 ie. Install bootstrap because then you wkbt be able to update to ICS to re FKZ back to 2.3.5

Sent from my MB865 using xda app-developers app

farshad525hou said:

The only problem with that is that you can't mod 2.3.6 ie. Install bootstrap because then you wkbt be able to update to ICS to re FKZ back to 2.3.5

Sent from my MB865 using xda app-developers app

Click to expand...

Click to collapse

I was under the impression that you didn't need bootstrap to install the leak ics. I thought it was stock recovery...

Of course, since I still haven't left 2.3.6 yet, I can't speak from any experience . If you're correct, wouldn't that mean people won't be able to get back to the leak if they've returned to 2.3.5 using the script (or am I mis-interpreting?)? I had assumed that with Jim's script people could go 4.0.4 to 2.3.5, then ota to 2.3.6, then stock recovery to 4.0.4 and repeat ad infinitum?