[GUIDE] Forcing update 2.2.1 and re-rooting after downgrading

---

Force update + Re-Root Instructions!

Disclaimer: This is aimed at those of us who used travisjames' method of downgrading to stock. brian6685 confirmed this WILL work with a new phone running stock. I am not responsible for you bricking your phone, but there have been no reports of any bricking with this that I am aware of.

I don't know if many of you are running a software number starting with 1.13, but if you are before you follow these instructions you MUST first follow the "downgrade" instructions (actually an upgrade for you)

The downgrade post can be found here.

First: Forcing the Update

1. download this file save this as PD15IMG.zip
* This is not the same file as in the downgrading instructions!

2. reboot into bootloader and flash this update
* for me Wi-Fi stopped working at this point and my 3g/4g was acting funky

3. This is going to appear as if no updates were made when you reboot, but you will now be able to follow the root instructions in this thread perma root guide to get S-OFF

4. download Clockwork Mod, and The OTA

5. install the clockwork recovery (to do this because my 3g/4g was acting up I dialed *#*#INFO#*#* and in the phone info settings I set it to GSM only) then flash the update and you will have 2.2.1 and full working WIFI... also at this point if you did set it to GSM Only go back in and change it back to WCDMA preferred

**The big problem is wifi will not work after step 2 which is why I included the web downloads for clockwork rom... I used ADB to install them, but if you have astro or something similar you can get them installed that way too... Another way to fix this is to download the broadcom kernel module and insmod it... the reason for this is when you do the update off of the img it's just loading the system files and not running the patches against them. ie kernel gets updated but modules aren't applied

-----------------------------------------------------------------------------

Second: Re-Rooting

This was solved by following Grankin's instructions for fixing root and su after a flash... This requires uninstalling superuser and visionary then following thise steps. The referenced file is here and the original post about this is here

1. Using Explorer navigate to the root of your sdk. Hold shift and right mouse click on the tools folder. Select "Open command window here".

2. Type "adbbat" + enter. Wait till the batch file finishes.

3. Disconnect your phone from the PC.

4. Open terminal emulator on the phone and type "/data/local/rage" + enter. Wait for "Forked XXXXXXXX children" to appear and then close the terminal.
**Just ran through this again... the program you should use is "Android Terminal Emulator" the one labeled just "Terminal Emulator" repeatedly force closes...

5. Start terminal back up. It should force close.

6. Start terminal back up, again. This time it should stay open and you should have a "#" prompt instead of a "$" prompt. Then type "/data/local/temp.sh.

7. When the script finishes run /data/local/rage again and sit tight. The phone should start acting weird and do a soft reboot. Then right after everything loads it should do a hard reboot. After the hard reboot reboot and check S.(If it doesn't do the two reboots just reboot into hboot yourself after rage finishes with the "forked xxxxxxxx children" message.

-----------------------------------------------------------------------------

**When I did this on step 4 I had to go into settings>applications>manage applications>Terminal Emulator and Force Stop because it was not force closing, but when I did I had the "#" prompt when I reopened terminal then it worked as advertised

**If you experience force closes of sense after updating to 2.2.1 run the fix permissions from clockwork recovery and it should fix it. If it is still happening do a factory reset and continue from there.

**For you linux folks here's a little script to replace the adbbat.bat file. adbbat.sh I tested this and it moves all the files and chmods properly.

Credit goes to travisjames for figuring out how to downgrade to stock and grankin01's post about using rage to root when visionary is having issues.

Great find man! Hopefully this will work on all the pre-OTA devices and everyone can have root utopia!

My MyGlacier 4G MINE!!!

I'd love to try this, but I don't see where the OTA plays a part here? May give it a shot when I get off work tonight.

Originally Posted by grankin01

Great find man! Hopefully this will work on all the pre-OTA devices and everyone can have root utopia!

My MyGlacier 4G MINE!!!

Thanks man, I'm here to help if anyone has questions... I spent about a week waiting for someone smarter than me to figure it out... I have a little linux experience (I run a few servers for fun), but didn't think I would be able to figure this out... turned out it really wasn't too hard... I was about to try the rage thing when I came home today, but someone beat me to it and posted a link to your post, and that was the last piece of the puzzle.

I'd love to try this, but I don't see where the OTA plays a part here? May give it a shot when I get off work tonight.

the first file you're downloading is actually the image files from the OTA, this updates some files but doesn't do a full system patch. The thing it does update is the kernel, which allows you to use the original S-OFF method. Once you're S-Off you can install clockwork and flash the actual OTApkg.zip through clockwork's recovery. Then you have to reroot using rage because for some reason visionary thinks it's already rooted and su won't work...

Thanks alot man! I have a pre-ota device and im gonna give it a shot in a few minutes to see if it works. Ill let you know soon!

I am on a pre-ota device, i followed the instructions, and now I am s-off wow thanks alot man! Im gonna do the rest and get clockwork installed and install the update

Okay so everything went successfully. Wifi working again and everything works. I am on the second part now to re-root. I am using linux..... that adbbat is for windows...... any suggestions?

Originally Posted by brian6685

Okay so everything went successfully. Wifi working again and everything works. I am on the second part now to re-root. I am using linux..... that adbbat is for windows...... any suggestions?

VirtualBox? ... I kid I kid . Just open up adbbat in a text editor and run the commands by hand I'd say.

Originally Posted by brian6685

Okay so everything went successfully. Wifi working again and everything works. I am on the second part now to re-root. I am using linux..... that adbbat is for windows...... any suggestions?

I can either wip up a script or you can "edit" the batch file and use the commands inside it manually in your shell.

Edit: Genocaust beat me to it.
My MyGlacier 4G MINE!!!

Originally Posted by grankin01

I can either wip up a script or you can "edit" the batch file and use the commands inside it manually in your shell.

Edit: Genocaust beat me to it.
My MyGlacier 4G MINE!!!

Oh, i see Ill do it thanks lol