Database Info

[GUIDE]Updating to 4.22.651.2 OTA WITHOUT flashing a new ROM or wiping your Phone

This assumes you:
- Have the latest FROYO OTA installed 3.70.651.1
- Have some experience working with flashing things in recovery
- Have NOT deleted/uninstalled ANYTHING in /system
- Have defrosted any bloat you froze with Bloat Freezer or Ti Backup Pro
- Have S-OFF (Used Unrevoked Forever or a version of Unrevoked3 that includes Forever)
OK now let us get to it.
1. Go ahead and download the OTA like normal on your phone, but DO NOT install it.
2. Using a file manager copy the OTA zip file from /cache to /sdcard
3. Using Rom Manager, flash Amon RA Recovery 2.3 (Down at the bottom)
4. In Rom Manager, click the Reboot into Recovery button.
5. Select apply zip from SD Card and flash the OTA zip file that you put in /sdcard
--10 Minutes later.....you now have the UNROOTED OTA installed just as if you installed it normally--
6. Download the 2.6.0.1 ClockWorkMod Recovery zip from here and place it in the root of your SD card
7. Under settings > applications > disable FastBoot (re-enable this when you are done with the whole process)
8. Power off and reboot holding Volume down. The bootloader will scan and then will and ask you to press Volume up to install. Reboot.
9. Delete the PC36IMG.zip file from your SD card and place the attachment below in the root of the SD card.
10. Power off and reboot holding Volume down and then select recovery to start CWM recovery.
11. Choose apply zip from sd card. Choose select zip on sd card. You will see the SU file on the list, flash it to root your phone. Reboot.
You should now be rooted and can upgrade the recovery now to whatever style and version you want!
Enjoy! Please click the THANKS button if it worked for you!
----------------------------------------
Developer of Bloat Freezer - Freeze Your Pre Installed System Apps in One Click
Bloat Freezer - Android Market Link

Very cool!!

Great info ..hey if I follow these steps and skip the last part will my phone be stock / uprooted and good to go.for a trade in or repair? I've been trying to figure out the best way to unrest when.e3d comes out

I never updated to 3.70. I'm assuming I can do that the same way, root again, download the gingerbread, and root again?
I'm thinking it might just be easier to flash the rooted ROM and radios, but I'm not sure what's best.

if you have amon ra recovery (and a stock rom), you can simply download and click install.
I clicked install, amonra booted up, detected and ran update, click reboot, then the stock recovery will be active and updates the radios, once back in to sense, you can reinstall amonra or clockwork, then SU
worked for me.
http://forum.xda-developers.com/showthread.php?t=1109230

im curious why the title says "WITHOUT flashing a new ROM" yet you are clearly flashing the rom in amon ra. sorry just got to nit pick

what happens if you have deleted some system apps. Such as nova and blockbuster. I saved the APKS on the SD card however but I did delete them?

JMQUINT00 said:
what happens if you have deleted some system apps. Such as nova and blockbuster. I saved the APKS on the SD card however but I did delete them?
Click to expand...
Click to collapse
Well I wouldn't want to try it unless your prepared to do a full ruu reset if it fails.
the OTA is like a patcher, it deletes unneeded files, adds new files, and updates existing files... if its not completely stock it may (or may not) cause an error which the updater can't handle, and then you may be left with a half upgraded system.
if you nandroid *before* downloading the ota, you should always be able to go back, assuming you have perm soff from unrevoked forever.

it should run whether you have removed files or not. if it tries to delete a file that does not exist the script will just skip it. op i think you have bit of confusion going on though. you were only able to reattain root because you are s-off from unrevoked forever. if you are not s-off and do your method, which is no different then just excepting the ota and letting it do its thing btw, you will loose root until this new ota is cracked. just fwi, there was no "magic" from you flashing manually, the same script is ran and the same files are moved and patches are made regardless.

cant I reinstall the apps and put the apks in their original system folder?

DomSim said:
it should run whether you have removed files or not. if it tries to delete a file that does not exist the script will just skip it. op i think you have bit of confusion going on though. you were only able to reattain root because you are s-off from unrevoked forever. if you are not s-off and do your method, which is no different then just excepting the ota and letting it do its thing btw, you will loose root until this new ota is cracked. just fwi, there was no "magic" from you flashing manually, the same script is ran and the same files are moved and patches are made regardless.
Click to expand...
Click to collapse
Lol OK so which one is it? Can n just accept the ota and run? I'm rooted on stock rom, but I deleted nova and blockbuster from the system? I know I will loose root which I got by using unrevoked 3, but I just want to know if I can do it without bricking the phone. Ty

JMQUINT00 said:
Lol OK so which one is it? Can n just accept the ota and run? I'm rooted on stock rom, but I deleted nova and blockbuster from the system? I know I will loose root which I got by using unrevoked 3, but I just want to know if I can do it without bricking the phone. Ty
Click to expand...
Click to collapse
shouldn't be any worry about bricking but make 100% sure you are s-off from unrevoked forever and you should be able to re-root pretty much how the op outlined.

im currently running cm7. if i go back to a rooted stock froyo rom, will this work???

confused. I just don't understand why you wouldn't download the rooted version of the ROM from here on XDA and just flash it like a normal rom. Maybe I'm overtired and missing the point.
To me, its like this. If you're rooted, and want an OTA update, just wait for the devs at XDA to go through it and root it, and make it available for download. Then just download it and flash it. You get the same exact update that way, as if you took the OTA from sprint. Except this way you don't risk losing root, and your good to go.
If you're not rooted and your phone is stock, accept OTA like normal.
I don't understand why all this extra stuff needs to be done, and add more to the confusion. If your rooted, updating to the latest is simple. Download it and flash it in recovery.

DaEXfactoR said:
im currently running cm7. if i go back to a rooted stock froyo rom, will this work???
Click to expand...
Click to collapse
Just download the update from here http://forum.xda-developers.com/showthread.php?t=1038701
Do a full wipe and flash like any other rom you've ever flashed before. You'll then be on the latest and greatest . (you'll probably be going right back to CM)
EDIT: and to the OP, sorry that I don't agree with you. I just find it more confusing that way, and I guess that whatever the point of doing it that way is, is sailing miles above my head.

k2buckley said:
confused. I just don't understand why you wouldn't download the rooted version of the ROM from here on XDA and just flash it like a normal rom. Maybe I'm overtired and missing the point.
To me, its like this. If you're rooted, and want an OTA update, just wait for the devs at XDA to go through it and root it, and make it available for download. Then just download it and flash it. You get the same exact update that way, as if you took the OTA from sprint. Except this way you don't risk losing root, and your good to go.
If you're not rooted and your phone is stock, accept OTA like normal.
I don't understand why all this extra stuff needs to be done, and add more to the confusion. If your rooted, updating to the latest is simple. Download it and flash it in recovery.
Click to expand...
Click to collapse
I see your point. I guess I am anxious. So there will be a stock ROM that is rooted, thats what I was wondering. I wasnt sure if every ROM would be customized somewhat...Thanks

DaEXfactoR said:
I see your point. I guess I am anxious. So there will be a stock ROM that is rooted, thats what I was wondering. I wasnt sure if every ROM would be customized somewhat...Thanks
Click to expand...
Click to collapse
That link I supplied a couple posts up is a completely 100% stock and rooted version of the OTA update.
This is from the first paragraph of the first post of that thread.
"Stock 4.22.651.2 ROM, rooted and ready for your flashing pleasures. This is a completely stock ROM that has had nothing done to it outside of rooting & deodexing, it's not even zip aligned yet (sorry DrMacinyasha)
As always make sure your wipe your dalvik and create a nandroid before flashing."

k2buckley said:
That link I supplied a couple posts up is a completely 100% stock and rooted version of the OTA update.
This is from the first paragraph of the first post of that thread.
"Stock 4.22.651.2 ROM, rooted and ready for your flashing pleasures. This is a completely stock ROM that has had nothing done to it outside of rooting & deodexing, it's not even zip aligned yet (sorry DrMacinyasha)
As always make sure your wipe your dalvik and create a nandroid before flashing."
Click to expand...
Click to collapse
thanks for your insight. only thing I am confused on at this point is why there are kernels listed to flash from May just below it? wouldnt the htc stock kernel from the ota be in this rom already? seems like alot of folks are looking for newer kernels to flash after flashing xhaus rom. Any insight would be great. thanks again!

rileyd5 said:
thanks for your insight. only thing I am confused on at this point is why there are kernels listed to flash from May just below it? wouldnt the htc stock kernel from the ota be in this rom already? seems like alot of folks are looking for newer kernels to flash after flashing xhaus rom. Any insight would be great. thanks again!
Click to expand...
Click to collapse
I was a little curious about why those kernels were linked there too. I honestly haven't really kept up with thread, because I don't have an interest in flashing the update to begin with. I noticed those kernels are from May 4th, so it doesn't seem like they'd be the most current one. Without reading that thread, I first would've presumed that the kernel that comes with the rom would be the one to use. So, you've read through the thread and you're seeing that people are having trouble with the kernel that the rom comes with?? I'll take a gander over in the thread in a few minutes and see what I make out of it.

Well I f'd up and installed the latest update straight from sprint, instead of waiting for the rooted version to come out. I guess I thought I would find something exciting, but now I would realize it was kind of worthless and want to go back to a different rom like miui or vaelpak. I am s-off with unrevoked. Is there some combination of the steps listed I can use to back out of this?
Let me take a guess...did this update my radios and hboot to a version that would be incompatible with these roms?

How to Unroot Your Phone if Using Unrevoked 3

So, I had some trouble unrooting my Evo 4G today because I wanted to bring my phone in for a replacement. It's been awhile since I last rooted the device so I figured I could just download the appropriate zip files and get on with it. I ran into a few snags.
A little background of the phone:
-Rooted via Unrevoked 3
-Running the latest Radio 2.15.00.05.02
-S-OFF
So, this method works if you rooted your phone via Unrevoked3 or Unrevoked Forever. I was reading all over and many people flashed to sense ROMs and did many steps that weren't really needed. The way I did was very simple.
**If you did not root your phone via Unrevoked skip to Step 7.
1. Downgrade your Radio to 2.15.00.07.28 (Anything earlier than the previous update should work) at http://forum.xda-developers.com/showthread.php?t=7154 All the radios should be located at the previous link.
2. Download the Unrevoked Forever S-ON zip file that is provided.
3. Move the S-ON zip file to the root of your SD card.
4. Flash the zip file so that your device now reads S-ON, NOT S-OFF.
5. Wipe Cache, Dalvik Cache, and Data.
6. Reboot into Bootloader and verify that you are now S-ON.
7. Download the PC36IMG.zip from http://www.4shared.com/file/5U4M4eVi/PC36IMG.html?cau2=403tNull
8. Move the PC36IMG zip file to the root of your SD card.
9. Reboot into Bootloader and the phone should recognize the PC36IMG and begin to finish the UNROOT process.
10. Follow on-screen instructions and apply the update and reboot the phone.
11. You are now UNROOTED!!!
I hope this little tutorial helped. It definitely is nice to finally unroot the device after all the problems I was running into.

NOW sticky it. lol

Does this enable S-On ?

nyc_zx10 said:
Does this enable S-On ?
Click to expand...
Click to collapse
Step six...

Unroot for repair
Just in case anyone doing this for the first time, I recently took my evo in and exchanged for another. Make sure you remove all evidence of root from your sd card i.e. root explorer, my back up root TI(any root programs) and get the pc36img off there too. Now depending how cool your Sprint techs are they might not care. My particular store said they would blacklist my phone if they suspected it of root. That will ruin your plans of getting any service in the future, let alone the reason you came in. Their little "diagnostics" term to me says,"Let me check if I am going to dash your hopes of repair today." Or to be safer you could just pull the sd. Hopefully if you do forget you have cool techs that appreciate what we do here.

Just a heads up, the radio link is broken. I've been using the same one as well in my bookmarks. That thread is apparently no longer there?

when i try to flash the radio is comes up with a message saying something about "it was necessary to remove it when upgrading to the CWM 3.0 gingerbread based recovery, please switch to edify scripting" do i have to downgrade my CWM?

I'll give this process a 7 on the pucker scale, but it does work
I downgraded my cm image before I started just so I wouldn't have to deal with any errors
I then flashed the 2.15.00.07.28 radio
then flashed the s-on tool
then applied the pc36img.zip in bootloader
took a while but I am back up, and running unrooted

[email protected] said:
All this does is change S-OFF to S-ON. I still have SuperUser and can still run root apps with ease. I assume this hack is just for taking the phone in?
Click to expand...
Click to collapse
Actually, after flashing the PC36IMG, that removes the root and puts the phone back to the initial state. It does put the phone to S-ON and remove SuperUser.

tkdkicker04 said:
Actually, after flashing the PC36IMG, that removes the root and puts the phone back to the initial state. It does put the phone to S-ON and remove SuperUser.
Click to expand...
Click to collapse
If you do take it in do not let them update anything. I even signed a paper saying I didn't want a hard reset.
Sent from my PG86100 using XDA Premium App

Will this wipe all my contacts, messages, and apps? What app should I use to back everything up (Mybackup Pro, or Titanium Backup)?

Yes you will lose everything. Google should save your contacts to the cloud. Any installed apps can be redownloaded. You will lose any saved messages/text/etc.
Keep in mind "S-OFF" and having root privileges are two different things. You can be rooted and be S-ON, and S-OFF and not rooted (which would mean you flashed a ROM that didn't have the su binary which almost doesn't exist outside of stock).

Why is it necessary to downgrade the radio? Just curious. Mine is currently running 2.15.00.11.19.
Question two... is that PC36IMG linked the stock 2.3.3?

Here is the post containing the Radios and more...
[ Radios ][ 7-4 ] All EVO Radio, WiMAX, PRI, NV & HBoot versions
For anyone having trouble flashing the Radios using ClockworkMod either:
1) Downgrade your CWM to 2.5.0.7 (within ROM Manager)
or
2) Using ROM Manager (or manually) Flash Alternative [Recovery] [09-Feb-2011] RA-supersonic-v2.3
To be able to use CWM nandroids in Amon_RA's Recovery you need to:
1) Make a folder on the root of your SD Card called Nandroid
2) Create a Nandroid using Amon_RA
3) Amon_RA will create another folder inside Nandroid
4) Place your nandroid that you made in CMW inside the folder that Amon_RA creates along with that nandroid too
Hope this helps people... If in fact it does please leave a thanks

Warning warning warning proceed at own risk etc etc
I used these instructions but in a different way.
1) I downgraded the radio. I still don't know why, it wasn't stated, but I went ahead and did it.
2) I downloaded the new radio and the unrevoked s-on tool (since I used unrevoked to root this phone in the first place)
3) I copied both the radio and s-on to my sd card while Evo was plugged into my PC via Disk Storage
4) On Amon's 2.3 recovery, I flashed the radio, let it do its thing and reboot and do its next lil thing it wants to do
5) Flashed the s-on. After it was done, I went back to the main menu of Amon's recovery and selected power off
6) Holding VOL+D and power, booted into the bootloader and saw it was S-ON.
7) Went through hboot to boot into recovery, then power off
8) Pulled battery to get to the sd card and put it into my PC so I could copy the PC36IMG.zip to it. Im really not convinced that its a big deal to copy this zip along with the radio and unrevoked s-on tool at the same time, except that it might idiot-proof flashing the pc36img prematurely. Then again, the instructions state to move it to the sd card...how? It can be done over ADB but theres not instructions given.
9) Put Sd card with PC36img copied to it onto the Evo, held VOL+D and power, booted into bootloader, it found PC36img, applied update and rebooted.
The linked PC36img is to android 2.2, on which im now unrooted.

cabbieBot said:
Warning warning warning proceed at own risk etc etc
I used these instructions but in a different way.
1) I downgraded the radio. I still don't know why, it wasn't stated, but I went ahead and did it.
2) I downloaded the new radio and the unrevoked s-on tool (since I used unrevoked to root this phone in the first place)
Click to expand...
Click to collapse
I think that the reason why you need an older radio is because if they saw that you had the newest radio released w/ the 2.3.3 and your on 2.2 it might look a little funny... this is my educated guess

.torrented said:
I think that the reason why you need an older radio is because if they saw that you had the newest radio released w/ the 2.3.3 and your on 2.2 it might look a little funny... this is my educated guess
Click to expand...
Click to collapse
that makes sense. so there isnt a 2.3.3 image to flash? or is there a reason to not want to do it if there it is?

cabbieBot said:
that makes sense. so there isnt a 2.3.3 image to flash? or is there a reason to not want to do it if there it is?
Click to expand...
Click to collapse
well when sprint released the latest OTA its a packaged deal you get all of the stuff (radio hboot PRI/NV ect.) well if you only have 1 of the many different things like the latest radio but not the latest hboot or w/e then i would assume that the phone has been rooted. so you wouldnt want the 4.24 software update and have all of the older firmware... im really not too sure and i could be wrong but this would seem pretty logic (to me)
oh and flashing the 2.3.3 image would render it unrootable

cabbieBot said:
Warning warning warning proceed at own risk etc etc
I used these instructions but in a different way.
1) I downgraded the radio. I still don't know why, it wasn't stated, but I went ahead and did it.
2) I downloaded the new radio and the unrevoked s-on tool (since I used unrevoked to root this phone in the first place)
3) I copied both the radio and s-on to my sd card while Evo was plugged into my PC via Disk Storage
4) On Amon's 2.3 recovery, I flashed the radio, let it do its thing and reboot and do its next lil thing it wants to do
5) Flashed the s-on. After it was done, I went back to the main menu of Amon's recovery and selected power off
6) Holding VOL+D and power, booted into the bootloader and saw it was S-ON.
7) Went through hboot to boot into recovery, then power off
8) Pulled battery to get to the sd card and put it into my PC so I could copy the PC36IMG.zip to it. Im really not convinced that its a big deal to copy this zip along with the radio and unrevoked s-on tool at the same time, except that it might idiot-proof flashing the pc36img prematurely. Then again, the instructions state to move it to the sd card...how? It can be done over ADB but theres not instructions given.
9) Put Sd card with PC36img copied to it onto the Evo, held VOL+D and power, booted into bootloader, it found PC36img, applied update and rebooted.
The linked PC36img is to android 2.2, on which im now unrooted.
Click to expand...
Click to collapse
To answer your first question, after doing my research and by trial and error, I ran into several errors and problems having the latest radios and HBOOT. The alternative to fix this problem was to downgrade the radio.
The reason why it's easier to move the PC36IMG after you are S-ON is to make sure that you do not make the mistake of updating prematurely. Mistakes can happen and if you move too fast, accidents may happen. This was done to insure that needless accidents don't happen. The way you move the file to the SD card is by enabling USB mode while in recovery mode (Amon RA and Clockwork). The disk drive appears on your computer, and you click and drag the files just like normal.
The PC36IMG contains Android 2.2

.torrented said:
Here is the post containing the Radios and more...
[ Radios ][ 7-4 ] All EVO Radio, WiMAX, PRI, NV & HBoot versions
For anyone having trouble flashing the Radios using ClockworkMod either:
1) Downgrade your CWM to 2.5.0.7 (within ROM Manager)
or
2) Using ROM Manager (or manually) Flash Alternative [Recovery] [09-Feb-2011] RA-supersonic-v2.3
To be able to use CWM nandroids in Amon_RA's Recovery you need to:
1) Make a folder on the root of your SD Card called Nandroid
2) Create a Nandroid using Amon_RA
3) Amon_RA will create another folder inside Nandroid
4) Place your nandroid that you made in CMW inside the folder that Amon_RA creates along with that nandroid too
Hope this helps people... If in fact it does please leave a thanks
Click to expand...
Click to collapse
Thanks for this man. I was having trouble finding a working link.

how do i update rooted phone w/ ota update?

so sadly im still running 1.28.531.10 and want to update to 1.63.531.2, i got a file - OTA_Doubleshot_TMOUS_1.63.531.2-1.28.531.10_release_245284jzymhpvbi39cqj18.zip but it fails to flash - as a non-developer I came across http://forum.xda-developers.com/showthread.php?t=1624516 and think i need to somehow get Modaco CWM ? i currently have titanium backup and rom manager apps with - CWM 5.0.2.7 flashed.
Might be stupid question but how exactly do i load in this new update, without messing up my current setup (using trimmed stock rom rooted with s-off)?
I see the article reference calls out some "PG59IMG.zip" file
but cant i simply use my "OTA_Doubleshot_TMOUS_1.63.531.2-1.28.531.10_release_245284jzymhpvbi39cqj18.zip" that got downloaded?
I guess i need a bit more help - as feeling pretty out of it and certainly dont want to mess up my phone. I got too much other stuff going on but would like to do the update - can someone please provide a list of instructions on how to update the phone without loosing all my stuff? - like where do i get this Modaco CWM and what version i need. and if i can use my ota.zip file
i tried flashing my ota.zip via cwm 5.0.2.7 but it just errors out
Any and all help would be greatly appreciated

You can only install manufacturer ota updates with a stock recovery.
Doing the update can equate to a factory reset, at the very least will lose root - you'll have to re-root it.
Installing a PG59IMG.zip file will wipe your system.
Sent from a digital distance.

steve_77 said:
so sadly im still running 1.28.531.10 and want to update to 1.63.531.2, i got a file - OTA_Doubleshot_TMOUS_1.63.531.2-1.28.531.10_release_245284jzymhpvbi39cqj18.zip but it fails to flash - as a non-developer I came across http://forum.xda-developers.com/showthread.php?t=1624516 and think i need to somehow get Modaco CWM ? i currently have titanium backup and rom manager apps with - CWM 5.0.2.7 flashed.
Might be stupid question but how exactly do i load in this new update, without messing up my current setup (using trimmed stock rom rooted with s-off)?
I see the article reference calls out some "PG59IMG.zip" file
but cant i simply use my "OTA_Doubleshot_TMOUS_1.63.531.2-1.28.531.10_release_245284jzymhpvbi39cqj18.zip" that got downloaded?
I guess i need a bit more help - as feeling pretty out of it and certainly dont want to mess up my phone. I got too much other stuff going on but would like to do the update - can someone please provide a list of instructions on how to update the phone without loosing all my stuff? - like where do i get this Modaco CWM and what version i need. and if i can use my ota.zip file
i tried flashing my ota.zip via cwm 5.0.2.7 but it just errors out
Any and all help would be greatly appreciated
Click to expand...
Click to collapse
Id say backup apps with titanium backup and flash the pg5 zip
Sent from my RubiX NonSense using Tapatalk 2

edited

update
UPDATE:
finally got root:
used:
http://forum.xda-developers.com/showthread.php?t=1532809
to get CMR flashed - then downloaded su-2.3.6.3-efgh-signed.zip
and flashed it through CMR...
for some reason other root methods just didnt work (i tried about 5 ) and at some point did have superuser.apk on phone but it said bad permissions, and i downloaded a "root checker" and it said i still did not have root..
but kudos to hasoon2000 -- for making the program - still dont know if i should "relock-bootloader" (i already has s-off, but used his program to flash CMR, then CMR to flash the su.zip ) but dont know what "unlock bootloader" did and if i should relock it, now that i got root up and going...

One thing I'd do is--
I apologize for being late to this thread; I would have listed a more straightforward method with source links had I referenced the conversation earlier. Be that as it may...
steve_77 said:
to get CMR flashed - then downloaded su-2.3.6.3-efgh-signed.zip and flashed it through CMR...
Click to expand...
Click to collapse
That's an older version of Superuser. And while it may be adequate, I recommend you flash the newer version from AndroidSU.com: http://downloads.androidsu.com/superuser/Superuser-3.0.7-efghi-signed.zip
From my experience, it sometimes doesn't want to install unless you follow these steps:
Boot into CWM recovery
Connect your phone to PC via USB
Choose "mounts and storage," then "mount USB storage"
When your phone directory shows up on your PC, copy the Superuser zip to the root of your SD card
Unmount USB storage and go back to the main CWM menu, then choose "install zip from sdcard"
Scroll down to the Superuser zip and select it. Installation should go without problems.
steve_77 said:
but kudos to hasoon2000 -- for making the program - still dont know if i should "relock-bootloader" (i already has s-off, but used his program to flash CMR, then CMR to flash the su.zip ) but dont know what "unlock bootloader" did and if i should relock it, now that i got root up and going...
Click to expand...
Click to collapse
Erm, no. You most definitely do not want to relock the bootloader. If you have root/s-off, updating Superuser is the only thing I'd recommend. You're golden for everything else.
Hope the above info proves helpful --
--
KingCheetah

KingCheetah said:
That's an older version of Superuser. And while it may be adequate, I recommend you flash the newer version from AndroidSU.com: http://downloads.androidsu.com/superuser/Superuser-3.0.7-efghi-signed.zip
KingCheetah
Click to expand...
Click to collapse
I tried that the other day, however If i flash that version v3.0.7 (41) -
I no longer have "root" and my "rom manager" and "titanium backup" will not work
- the new su app did look nicer but - defeats the point if it doesn't function, im still trying to find a way to revert my phone and get the old version back in there(have to start all over). Im hoping there is a workaround for this behavior (perhaps there should be a separate thread on getting a working version of superuser 3.0.7 - as it installed fine)?

HOLD ON THIS!!! How To Update TMOUS to 1.84 when Rooted!

HOLD ON UPDATING!!! There are a bunch of people having data and wifi issues with this release. I have not had them but that doesn't mean you won't. Update at your OWN risk. You've been warned.
If you would like to update the software but not the baseband (probable cause for data/wifi issues) then just use my Nandroid linked below and leave your current baseband.
To everyone that keeps trying to relock their phones and flash the RUU to get the update it will NOT work. If you look at your software version you will see that it has added and R2 in it. I don't know why it does this, maybe it's a why for HTC to screw over the hackers yet again. Here is how to get the update.
There are 2 ways to get the update.
First: Use my Stock Rooted 1.84 Nandroid that I posted here. Simple but you will have to flash the radio separate.
Second: More steps but worked for me. NOTE: Only works if your on stock rooted phone. Will not work on custom ROM. Get Stock 1.53 Nandroid here. Credit to Reviewers for posting.
This will NOT wipe your phone nor do you need to wipe your phone if you are on Stock Rooted.
1a - This step only needed if you are on a custom ROM. If your on Stock Rooted then proceed to step 1b.
Download the above linked Nandroid (for 1.53) and restore it in Recovery. Reboot.
1b - Download this tool and use it to flash stock recovery. It will auto reboot your phone into bootloader so just start with your phone normally booted.
Credit goes to hasoon2000 for creating the tool!
2 - Your phone will reboot, once booted back up go to Settings>About Phone>Software Update. It will find the update and download then prompt to install. Select yes and let your phone update and reboot.
3 - Fire up the tool from step 1b again and this time flash CWM Recovery (whichever you prefer).
4 - After reboot is complete reboot again back into recovery and flash this to restore SU permissions (seems the update breaks them, at least for me).
Credit goes to Chainfire for creating this!
5 - Reboot, Done.

Any way to force the update if you have already received it once? I downloaded it yesterday but it failed because I had CWM installed at the time. I've flashed back to stock recovery but when I check for an update it says one isn't available.
I wonder if I could call T-Mobile and have them push it again?

DigitalMonk said:
Any way to force the update if you have already received it once? I downloaded it yesterday but it failed because I had CWM installed at the time. I've flashed back to stock recovery but when I check for an update it says one isn't available.
I wonder if I could call T-Mobile and have them push it again?
Click to expand...
Click to collapse
Did you totally wipe your phone? If not then the update is in your " download" folder
Sent from my HTC One S

Yeah, I know it's in Download, I posted about that in another thread yesterday. But is there some way to flash it now from that file? I thought from reading the other threads there was no flashable version yet, or was that only if you are running CWM?

DigitalMonk said:
Yeah, I know it's in Download, I posted about that in another thread yesterday. But is there some way to flash it now from that file? I thought from reading the other threads there was no flashable version yet, or was that only if you are running CWM?
Click to expand...
Click to collapse
Try deleting that file and checking again. Back it up to your computer first of course.

setzer715 said:
Try deleting that file and checking again. Back it up to your computer first of course.
Click to expand...
Click to collapse
Didn't work for me. I got about 2 downloads out of the servers, and then they aren't sending it anymore. Weak.

No go so far. Copied it to my PC, deleted it from my Download folder, re-booted and then checked for an update 3 different times and nothing so far.

With all of the people having wifi and data issues TMO may have stopped sending it until they figure out what is going on. I do know for a fact that TMO tests any software update the send so something may have gone haywire with it. Maybe got radio mixed up.

DigitalMonk said:
I thought from reading the other threads there was no flashable version yet, or was that only if you are running CWM?
Click to expand...
Click to collapse
Wait.. I didn't know this. You mean even if we "unroot" and flash stock recovery (and using stock ROM of course), we cannot flash this ourselves?
I currently have the CWM touch recovery and root, u/l bootloader, etc., and TMO has sent me 2 updates, both were in the Downloads folder. I didn't notice that it updated (as I never confirmed) but they obviously didn't install.
But I would have done the above if I had known we couldn't just flash it ourselves. WTF T-mobile?? Those of us who know how to flash a file should at least not be prevented from doing so (especially since we need to have the original recovery installed).
Sent from my HTC One-S (rooted), stock ROM

[Q] Firmware News & Alternative Install Methods

I found this thread and since i am a newbie when i read it a few questions came on my mind
Alternative Firmware update Method
1. Decompress downloaded .zip file (it will be another .zip)
2. Rename it to EP201_768_SDUPDATE.zip
3. Format FAT32 the MicroSD card that you will be using for the update process
4. Copy the file to (the root directory of) your MicroSD
5. Insert it into the tablet
6. Shutdown (power off) the tablet
7. Power it on by pressing and holding VOLUME DOWN and POWER buttons simultaneously
8. When you see white text in the top left corner of the screen, release the buttons ^^ and press VOLUME UP button until you see Android logo and process bar
9. Wait patiently for 10 minutes or so
10. Enjoy!
Also remember that you will probably need to use RootKeeper to regain root privileges and reinstall BusyBox too (firmware update changes the /system partition).
That's the thread i have read and the questions that came to my mind are:
1.Do i use the same method for any update?
2.Is it a safe way to update my firmware because after you unlock bootloader no OTA update but only manual update is possible.So is this the right way to manually update any version of firmware update from now on?
3.Is there any other way to manually update my Asus?
4.Do i have to follow another way of installing the update because of the custom recovery that i have installed? (TWRP)
5.If i format the SD Card using exFAT will this method work or not?
I appreciate any help you could give me since i am a noob and some things seem really scary to me due to the fear of bricking my device,
Thank you in advance for your patience reading my questions:angel:

Help with OTA
Dino,
I have a few quesitons for you (just to verify).
Is your boot loader unlocked?
If so, are you running a custom recovery?
If not, then why don't you just use the over the air update?
If your boot loader is unlocked, and you are running a custom recovery (which I understand you are), then yes, you will likely need to update from SD Card from here on out. Once you unlock the boot loader you can no longer get OTA updates. I would recommend following this thread: http://forum.xda-developers.com/showthread.php?t=1915079
If you are already rooted then you can use SuperSU, and OTA Rootkeeper to regain root after the update. There are tons of threads that discuss this. If you are doing root for the first time, you should read this: http://forum.xda-developers.com/showthread.php?t=1916762
The SD Card format needs to be FAT32. In regards to being a "noob" and scared, you should be. Did you make a recovery image using NvFlash before you touched your tablet in the first place? If not, then I would recommend that once you get to JB that you never attempt to load anything on your tablet ever again, at least not until you are no longer a "noob", and you are understanding and accepting of the fact that you may hard brick your tablet some day.
dinothenino said:
I found this thread and since i am a newbie when i read it a few questions came on my mind
Alternative Firmware update Method
1. Decompress downloaded .zip file (it will be another .zip)
2. Rename it to EP201_768_SDUPDATE.zip
3. Format FAT32 the MicroSD card that you will be using for the update process
4. Copy the file to (the root directory of) your MicroSD
5. Insert it into the tablet
6. Shutdown (power off) the tablet
7. Power it on by pressing and holding VOLUME DOWN and POWER buttons simultaneously
8. When you see white text in the top left corner of the screen, release the buttons ^^ and press VOLUME UP button until you see Android logo and process bar
9. Wait patiently for 10 minutes or so
10. Enjoy!
Also remember that you will probably need to use RootKeeper to regain root privileges and reinstall BusyBox too (firmware update changes the /system partition).
That's the thread i have read and the questions that came to my mind are:
1.Do i use the same method for any update?
2.Is it a safe way to update my firmware because after you unlock bootloader no OTA update but only manual update is possible.So is this the right way to manually update any version of firmware update from now on?
3.Is there any other way to manually update my Asus?
4.Do i have to follow another way of installing the update because of the custom recovery that i have installed? (TWRP)
5.If i format the SD Card using exFAT will this method work or not?
I appreciate any help you could give me since i am a noob and some things seem really scary to me due to the fear of bricking my device,
Thank you in advance for your patience reading my questions:angel:
Click to expand...
Click to collapse

droidhaxxor said:
Dino,
I have a few quesitons for you (just to verify).
Is your boot loader unlocked?
If so, are you running a custom recovery?
If not, then why don't you just use the over the air update?
If your boot loader is unlocked, and you are running a custom recovery (which I understand you are), then yes, you will likely need to update from SD Card from here on out. Once you unlock the boot loader you can no longer get OTA updates. I would recommend following this thread: http://forum.xda-developers.com/showthread.php?t=1915079
If you are already rooted then you can use SuperSU, and OTA Rootkeeper to regain root after the update. There are tons of threads that discuss this. If you are doing root for the first time, you should read this: http://forum.xda-developers.com/showthread.php?t=1916762
The SD Card format needs to be FAT32. In regards to being a "noob" and scared, you should be. Did you make a recovery image using NvFlash before you touched your tablet in the first place? If not, then I would recommend that once you get to JB that you never attempt to load anything on your tablet ever again, at least not until you are no longer a "noob", and you are understanding and accepting of the fact that you may hard brick your tablet some day.
Click to expand...
Click to collapse
Thank you very much for your kind reply.I am rooted but still have not unlocked Bootloader. After i've read several threads i was too scared to unlock my bootloader,that's why i was waiting for some answers in order to do it. Basically the only reason for me to unlock the bootloader is the fact that i can keep a backup of my whole device (nandroid if i say it correctly) by using a custom recovery, that's it and that is for me the only reason to do it. I am not interested in flashing custom ROMs just Backup my device.
So what is your suggestion for me to do, with the fact in mind that i want to backup my device.
As for the other thing that you mentioned "nVFlash" i don't know how to do it and although i have read some threads about it i am still very confused how to do it. If you could guide me through it, in simple steps, i would be very grateful. I am on .26 version if that helps.
So to sum up,I got my Asus rooted, locked bootloader, firmware version .26, stock recovery, help is always appreciated !!!
Thank you again in advance,

dinothenino said:
Basically the only reason for me to unlock the bootloader is the fact that i can keep a backup of my whole device (nandroid if i say it correctly) by using a custom recovery, that's it and that is for me the only reason to do it. I am not interested in flashing custom ROMs just Backup my device.
So what is your suggestion for me to do, with the fact in mind that i want to backup my device.
Click to expand...
Click to collapse
If you really just want to backup all your apps and your data, you do not need to unlock or install a custom recovery at all. Just use something like Titanium Backup and that's it. Everything else (kernel, system and recovery) can be restored from the official Asus firmware image.
dinothenino said:
So to sum up,I got my Asus rooted, locked bootloader, firmware version .26, stock recovery,
Click to expand...
Click to collapse
That's exactly the same as I have (locked, rooted, .26), and I am still not sure whether I want to unlock my bootloader and void my warranty. I am at least interested in trying some custom ROMs later, but first I need to understand what exactly the locked bootloader prevents me to do (flashing and loading custom recovery/kernel images and using fastboot - anything else?).

_that said:
If you really just want to backup all your apps and your data, you do not need to unlock or install a custom recovery at all. Just use something like Titanium Backup and that's it. Everything else (kernel, system and recovery) can be restored from the official Asus firmware image.
That's exactly the same as I have (locked, rooted, .26), and I am still not sure whether I want to unlock my bootloader and void my warranty. I am at least interested in trying some custom ROMs later, but first I need to understand what exactly the locked bootloader prevents me to do (flashing and loading custom recovery/kernel images and using fastboot - anything else?).
Click to expand...
Click to collapse
You pretty much say it all, with unlocked bootloader, you could flash, custom recovery, kernel, rom, using fastboot, scripts excepted for boot animation for now, cause you need a kernel that supporting it, once we have a custom kernel that support boot animation, you could do that too.
Back to the OP topic, if you have locked bootloader, rooted and running .26 build, you have 2 options to upgrade, but first make sure you read the thread about how to make a backup of your bootloader using NVFLASH before upgrade to .30 or JB. This is extremely important and since you're still at .26, consider yourself a lucky one. Next make sure you have Voodoo OTA installed and make a backup of your root. Also verify that indeed you do have root by download "root checker" from the market. Also use Titinum backup and backup your device. Finally, you have 2 easy options to upgrade.
A. OTA,(incremental upgrade), automatic download and upgrade your device push out by Asus.(No brainer)
B. Manual upgrade, if you prefer to do a full version (fresh install). It is recommended that you do a factory reset before and after the upgrade.
1) Download the correct latest firmware from Asus site, for JB the firmware called US_epad_user_10_4_4_16_UpdateLauncher.zip (this is US version).
2) Extract the .zip file, it will be another .zip file. This zip named EP201_768_SDUPDATE.zip.
3) Copy the file EP201_768_SDUPDATE.zip from your PC to the root of your MicroSD card.
4) Insert the MicroSD card in your tablet and use this button combination to go to recovery --> Start the tablet by pressing Volume Down and POWER together for 5 seconds ,a message will inform you that you have 5 seconds to enter the recovery,press Volume UP before the 5 seconds expire. At this point the device will go in recovery and should start updating your firmware.
5. If you upgrade from .30 to JB, you could skip step 4 and after step 3, just reboot your device and it should find and prompt you to update.
Thats it ..profit!!
There are couple more, but mainly used if you soft brick or issue, like extract the blog file from Asus download and use fastboot to push etc..but I don't think we need that right now.

I'd like to know more about the details of using fastboot and the blob file. Can you link me to a thread that shows that?

johnlgalt said:
I'd like to know more about the details of using fastboot and the blob file. Can you link me to a thread that shows that?
Click to expand...
Click to collapse
Here you go:
http://forum.xda-developers.com/showthread.php?t=1915598
I found that using fastboot from your pc is working bit better.

Actually, quite funny as I was just reading that. I'm attempting to downgrade to 9.4.5.30 now so I can root and then Keep Root and then re-upgrade and see if I can repair root.
I suppose this would be a bad time to think about 'blobbing' the tablet to JB
I would be more worried about the process except for the fact that I checked the binary-script file and all it does it put the blob on the device. No stupid patching like in Motorola devices. Makes like easier to deal with (in terms of applying updates) but a heck of a lot more bandwidth used (in terms of OTAs).
Speaking of which, are the OTAs the same files, full on blob installs, or are they patches? Just curious....

johnlgalt said:
Speaking of which, are the OTAs the same files, full on blob installs, or are they patches? Just curious....
Click to expand...
Click to collapse
The OTAs contain patches for files in /system, and a blob for kernel, bootloader, recovery (EBT, SOS, LNX).