Database Info

*Root-safe* stock OTA 1.47.651.1 *incremental* update w/ radio+WiMAX

IMPORTANT: The process described in this post breaks WiMAX, so I have removed the download links, and I recommend that no one attempt it. Please see this thread for a way to get from the original stock everything all the way up to the latest rooted OTA with the latest radio+WiMAX firmwares without even needing adb.
~~~ remainder of this post retained for historical interest only ~~~
Background: I didn't want to flash a full /system partition to upgrade my EVO 4G from Flipz's rooted stock 1.32.651.6 ROM to the latest 1.47.651.1, and I feel better using a barely modified "official" update from Sprint/HTC, so here's what I did:
Allowed the phone to download the update from Sprint/HTC. (It downloads into /cache.)
Copied the update to my computer and unzipped it.
Edited the META_INF/com/google/android/updater-script. (See below for a diff.)
Removed the recovery.img from the firmware.zip. (I don't want to go back to a stock recovery.)
Deleted the patch files for Sprint_Qik.apk and Sprint_TV.apk, since I've deleted those apps from my phone.
Edited the /system/build.prop file on the phone to remove the line that Flipz added at the bottom, thus restoring it to its stock condition (sha1=ee40d5143cf1089af2575045a9db9061f0d0dca9).
Zipped the update back up and signed it.
Download the update here:
OTA_Supersonic_1.47.651.1-1.32.651.6_rootsafe.zip
(md5=913c7594ca8ca94594a2c8e1ec9b5564)
Download the original build.prop file here:
build.prop-1.32.651.6
(md5=a29ab0ec25ad976bd12bc8bad5a97063)
Alternate: If you kept Sprint TV and Sprint Qik, use this update zip instead:
OTA_Supersonic_1.47.651.1-1.32.651.6_rootsafe-Sprint.zip
(md5=410f57feeaebcf89c5497cd6e599a807)
Before you begin: You MUST be using a rooted stock 1.32.651.6 ROM, such as this one released by Flipz. Because this update is an incremental update, it cannot apply to any other ROM, even custom ROMs having the same base system version.
How to install this update:
Caution: There has been a report that updating using this method breaks the WiMAX. If that's true, it can only be because HTC must have added some new function to their recovery program that the custom recoveries don't have. It is recommended that you run a Nandroid backup in case you need to revert.
Download the two files linked above.
adb push OTA_Supersonic_1.47.651.1-1.32.651.6_rootsafe.zip /sdcard/ (Or copy the update zip to your SD card by some other means.)
adb remount
adb push build.prop-1.32.651.6 /system/build.prop (See below for what to do if this step fails.)
adb reboot recovery
Run a Nandroid backup just in case.
Flash from the update zip and reboot.
The radio+WiMAX updates will install. This takes a while. Don't touch it. When it's finished, it will reboot on its own.
You'll find yourself in recovery one last time. Reboot.
It'll sit on the "4G" splash for a long time. Don't panic.
Once the home screen appears, go to Settings, About Phone, and verify that your "Software number" is 1.47.651.1 and your "Baseband version" is 2.05.00.06.10.
You may need to remove and re-add some home screen widgets.
If you're still using su and Superuser.apk from Flipz's stock rooted ROM, you will need to install the su-2.1-e-unsecure-signed.zip from this thread. It's a much, much newer version than the one Flipz included. It's an update zip, so install it via recovery.
Enjoy!
What to do if pushing build.prop fails:
This probably means you haven't unlocked NAND by flashing the engineering SPL. That's okay. Your custom recovery program probably supports adb while in recovery mode. If so, you can simply reboot the phone into recovery, perform step #4 from above, skip step #5, and continue from step #6.
For the curious, here's the diff of the updater-script from the stock update to mine: updater-script-1.47.651.1.diff
Troubleshooting
If you're getting an error that says assert failed: apply_patch_check, it means something about your system is different from a totally stock 1.32.651.6 system. Most likely you're running a custom ROM, not a rooted stock ROM, you've already applied the update, or you've installed some kind of hack like QuickBoot. Because this update is an incremental update, it can only be applied to a rooted (but otherwise unaltered) stock 1.32.651.6 ROM. Try flashing Flipz's stock rooted 1.32.651.6 ROM and then proceeding with the steps above under "How to install this update."
If Wireless Tether gets stuck when starting tethering, it probably means you still have the old and crusty su and Superuser.apk. Install the su-2.1-e-unsecure-signed.zip update mentioned above to get the latest set of superuser tools. Then Wi-Fi Tether should work fine.

Thank you. Will see if this fixes my broken 4G.

wsantiagow said:
Links Please?
Click to expand...
Click to collapse
The forum wouldn't let me post links. Apparently it's an anti-spam policy. As soon as a moderator is nice enough to bless my account, I'll turn those URLs into links.

please add back in Qik and TV... let users delete that after? many people use those programs.
either way, nice work

Does this include all of the contents of the original update, including the change to the Bit Rate of the Camera?

blehzz said:
please add back in Qik and TV... let users delete that after? many people use those programs.
either way, nice work
Click to expand...
Click to collapse
Get the rootsafe-Sprint.zip instead. The only differences between it and the stock update are that it doesn't include the recovery image and it preserves setuid+setgid root for /system/xbin/su.

wsantiagow said:
Thank you. Will see if this fixes my broken 4G.
Click to expand...
Click to collapse
I'm assuming broken as in you ran the unrevoked update?
Any luck?
Also, OP:
Does 4G work for you after this? I remember reading in some other threads that 4G wasn't working for images flashed without the default recovery. Not sure if I'm taking it out of context or if this is an issue.

wphend00 said:
Does this include all of the contents of the original update, including the change to the Bit Rate of the Camera?
Click to expand...
Click to collapse
It's exactly the update package furnished from Sprint over-the-air (the 30.2 MiB one), but with one line added to the updater script so that the update doesn't kill the setuid permissions on /system/xbin/su.
That means it changes everything Sprint changed in the latest update, including kernel, radio, WiMAX, and anything else.

So can I use this over a rooted Fresh .53 without breaking the root? Is this what you are running?

whitslack said:
The forum wouldn't let me post links. Apparently it's an anti-spam policy. As soon as a moderator is nice enough to bless my account, I'll turn those URLs into links.
Click to expand...
Click to collapse
..........

ViViDboarder said:
Also, OP:
Does 4G work for you after this? I remember reading in some other threads that 4G wasn't working for images flashed without the default recovery. Not sure if I'm taking it out of context or if this is an issue.
Click to expand...
Click to collapse
There's no 4G coverage in my area, so I can't know whether it works for sure. I can turn on 4G, though, and it says "Scanning." Also, the ip link command shows the wimax0 network interface is present, so I would assume that means the kernel module loaded successfully.
FWIW, I flashed the update using toast's recovery (md5=0ba574fe3a8d82e4e796cc306efa63a7). It definitely goes through the extra reboot cycle for flashing the firmwares. I see no reason why it wouldn't flash the WiMAX firmware, given that it's essentially the stock update process.
bjrmd said:
So can I use this over a rooted Fresh .53 without breaking the root? Is this what you are running?
Click to expand...
Click to collapse
I can't guarantee the patches will apply cleanly against anything other than the stock 1.32.651.6. It won't hurt to try it. The updater script has checks to be sure everything will apply cleanly before it touches anything, so the worst that can happen to you is that it will politely refuse to apply.

whitslack said:
I can't guarantee the patches will apply cleanly against anything other than the stock 1.32.651.6. It won't hurt to try it. The updater script has checks to be sure everything will apply cleanly before it touches anything, so the worst that can happen to you is that it will politely refuse to apply.
Click to expand...
Click to collapse
Only a stock 1.32.651.6? What if I'm running a stock ROOTED 1.32.651.6?
Also, can I just drop it in my SD card and flash it from there using Clockwork Recovery, or does it have to go through via the commands?
Thanks, btw!

whitslack said:
There's no 4G coverage in my area, so I can't know whether it works for sure. I can turn on 4G, though, and it says "Scanning." Also, the ip link command shows the wimax0 network interface is present, so I would assume that means the kernel module loaded successfully.
FWIW, I flashed the update using toast's recovery (md5=0ba574fe3a8d82e4e796cc306efa63a7). It definitely goes through the extra reboot cycle for flashing the firmwares. I see no reason why it wouldn't flash the WiMAX firmware, given that it's essentially the stock update process.
Click to expand...
Click to collapse
Right... Well, here it scans and then turns off wimax and then turns it back on and keeps doing that. Working with joshua_ last night I got it to keep scanning... It never did get an IP though but the interface was definitely present. I could see it with netcfg from the adb shell.
I pointed joshua_ to this thread to see what he things of these patches. I had been trying to help him use my phone to debug this issue so I don't want to mess things up too much for him.

I get an install aborted when trying to run the update zip. Starts the install then just stops and give an install aborted.
BTW I am now using a Fresh and not DC on my phone. And I am fully rooted(NAND unlocked) and have been able to run several other updates.zip without issue, currently using Clockwork MOD for recovery and not RA

rugedraw said:
Only a stock 1.32.651.6? What if I'm running a stock ROOTED 1.32.651.6?
Also, can I just drop it in my SD card and flash it from there using Clockwork Recovery, or does it have to go through via the commands?
Thanks, btw!
Click to expand...
Click to collapse
It will probably fail if you don't have a file at /system/xbin/su, which only rooted ROMs have. If you're running totally stock, you should just use the automatic OTA update from Sprint. If you're running rooted stock, you should use this. (I was using Flipz's rooted stock initially, so that's what I tested against.)

Badious said:
I get an install aborted when trying to run the update zip. Starts the install then just stops and give an install aborted.
Click to expand...
Click to collapse
What recovery are you using? Amon RA 1.7.0.1 wouldn't work for me. It kept complaining about no signatures, even though I had signed the update. I used toast's recovery successfully.
If that's not the problem, then it can only be that some file on your phone is not identical to the version from the stock 1.32.651.6. Did you replace the /system/build.prop file with the stock one linked in the OP? In particular, this update will not apply against Flipz's stock rooted ROM unless you replace that file with the really stock one.

Yep downloaded the buildprop in the OP and copied that over via ADB successfully(checked softwar version and it shows stock buildprop info)
Let me try it one more time and see exactly what it is bawking about.
Ok. Error Reads as Such:
Verifying Current System....assert failed: apply_patch_check ("system/app/AccountandSyncSettings.apk" . TWO LONG SETS OF HEX NUMBERS[if you need them I can provide them])
E: Error in /sdcard/OTA..(name of full file)
(status 7)
Installation Aborted.

ERROR:
Verifying current system...
assert failed: apply_patch_check ("/system/app/AccountAndSyncSettings.apE:unknown command [k",]
E:unknown command [56479c22c")]
E:Error in /sdcard/OTA_Supersonic_1.47.651.1-1.32.651.6_rootsafe-Sprint.zip
(Status 7)
Installation aborted.
Can someone assist please, would like to get this new Radio OTA flashed....
Edit: Running DC 3.2.1 with Aloyisus Theme

whitslack said:
It will probably fail if you don't have a file at /system/xbin/su, which only rooted ROMs have. If you're running totally stock, you should just use the automatic OTA update from Sprint. If you're running rooted stock, you should use this. (I was using Flipz's rooted stock initially, so that's what I tested against.)
Click to expand...
Click to collapse
Thanks for the quick response! I am running a rooted version of 1.32.651.6 and I've been waiting for something like this. So I should be OK using clockwork recovery to run this?

rugedraw said:
Also, can I just drop it in my SD card and flash it from there using Clockwork Recovery, or does it have to go through via the commands?
Click to expand...
Click to collapse
You can put it on your SD card by any means available to you. The only requirement is that your recovery program does not care that it's signed by someone other than HTC.
TheMike1 said:
ERROR:
Verifying current system...
assert failed: apply_patch_check ("/system/app/AccountAndSyncSettings.apE:unknown command [k",]
E:unknown command [56479c22c")]
E:Error in /sdcard/OTA_Supersonic_1.47.651.1-1.32.651.6_rootsafe-Sprint.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
That can only mean that you're not using the stock ROM (w/ root added). This is an incremental update straight from the official sources with one slight tweak to preserve root access, so you must be using a stock system in order for it to apply.
Users of custom ROMs should be flashing new versions of those custom ROMs. The incremental upgrade path here will not work on custom ROMs.

Stock 3.30.651.2 PC36IMG.ZIP Format

Phone: HTC Evo
Requirement: NAND unlock S-OFF (this allows for unsigned ROM)
Format: PC36IMG.ZIP
OS: 3.30.651.2 (2.6.32-15 Kernal)
Radio: 9.01
hboot: 2.02.0000
recovery: clockworkMod 2.5.0.1
WIMAX: 26023
PRI Version: 1.77_003
Wipes all user data: YES
Rooted: Yes
Link: http://www.megafileupload.com/en/file/278989/PC36IMG-zip.html
How to install: Download the file from the link above and and rename it from [Megafileupload]PC36IMG.zip to PC36IMG.zip. Place the file "PC36IMG.ZIP" file on the root of the SD-CARD. Power down the phone. Power up the phone while holding down the volume down button. The phone will prompt you to install a new rom, follow the prompts and reboot after flashing.
Purpose:
To create a current base rom to flash other roms without starting at the 1.47 PC36IMG.zip version.
Disclaimer: I am not responsible for any damage to your phone! Please do a nano backup prior to using this rom. This definately is a test rom, worked perfectly for myself, but not tested by anyone else. If you have any problems, boot into recovery and restore your nano backup.
Acknowledgments:
All the developers that have shared their hard work on XDA!
Note: You can unzip the file, remove the modules like ClockWorksMod or hboot then rezip the file as PC36IMG.zip to prevent those portions from being installed if you prefer.

I was just about to request this. Thanks!

Just to Clarify: (not that your directions weren't clear, just want to make sure there are no hiccups for anyone.)
The phone will scan for and find the image.
It will take a little while to load. Should have a blue status bar to the right.
Do you want to start update? Volume Up: Yes
Once it is finished: Do you want to reboot device? Volume Up: Yes

uberlemur let me know how it works for you. Like I said I only tested it on my phone. But I am confident that it will work, or I wouldn't have tried it on my own phone.
Karadorde, thanks for the more detailed instructions.

weidnerj said:
uberlemur let me know how it works for you. Like I said I only tested it on my phone. But I am confident that it will work, or I wouldn't have tried it on my own phone.
Karadorde, thanks for the more detailed instructions.
Click to expand...
Click to collapse
Yours were fine and it is pretty self explanatory, but I know doing things through HBoot can sometimes be daunting for those who have never tried it.

Just wanted to clarify if flashing this IMG with the .79 hboot will re lock Nand protection. I've used Toasts part 1&2 and yet skeptical about using unrevoked forever.

good stuff man!

Here is a picture of my Evo screen. I had used unrevoked forever prior to flashing the rom.

weidnerj said:
Here is a picture of my Evo screen. I had used unrevoked forever prior to flashing the rom.
Click to expand...
Click to collapse
The reason why I asked is that when rooting a new EVO,the radio, pri and wimax partitions get downgraded(using the traditional root method). With this, you can revert to the most current partitions all in a single flash including the Rom base instead of multiple flashes correct ??

You are correct, as long as you have ran the unrevoked forever to turn off the NAND unlock S-OFF prior to installing this ROM so that you can flash unsigned ROMs. This ROM has root built into it, so it would be just one step process to flash with this rom to have the latest of everything yet still have root.

mendez_v said:
Just wanted to clarify if flashing this IMG with the .79 hboot will re lock Nand protection. I've used Toasts part 1&2 and yet skeptical about using unrevoked forever.
Click to expand...
Click to collapse
Sounds like you will lose the Engineering HBOOT if you use this zip.

weidnerj said:
You are correct, as long as you have ran the unrevoked forever to turn off the NAND unlock S-OFF prior to installing this ROM so that you can flash unsigned ROMs. This ROM has root built into it, so it would be just one step process to flash with this rom to have the latest of everything yet still have root.
Click to expand...
Click to collapse
Thanks. My only question now is can I expect the same results if I obtained S-OFF through Toasts part 2, simple root or any other method other than unrevoked?

thanks
it worked

mobilemaniac said:
Sounds like you will lose the Engineering HBOOT if you use this zip.
Click to expand...
Click to collapse
Yep. Two different hboot.imgs. You can still take advantage of this information though. Keep your engineering bootloader but still update your radio, pri, etc.

noob here... in a bit of a bind
i did this update and it gave me this message
[5] BOOT Fail-pu
now the phone just goes to a back screen with green writing
ClockworkMod Recovery v2.5.0.1
what did i do?!?!?

peepeesea said:
noob here... in a bit of a bind
i did this update and it gave me this message
[5] BOOT Fail-pu
now the phone just goes to a back screen with green writing
ClockworkMod Recovery v2.5.0.1
what did i do?!?!?
Click to expand...
Click to collapse
Try it again.

Or if trying it again fails, you can boot into recovery and restore your nano backup. The part that failed is the system, but clockworkmod is still here.

weidnerj said:
uberlemur let me know how it works for you. Like I said I only tested it on my phone. But I am confident that it will work, or I wouldn't have tried it on my own phone.
Karadorde, thanks for the more detailed instructions.
Click to expand...
Click to collapse
The first time I tried I got a Fail-PU message for the boot partition. I'm pretty sure that's my phone's fault though, as the boot partition has been acting screwed up for days. (Not coincidentally, this is the reason I was looking for a complete PC36IMG.zip).
I flashed it a second time though, and all was well. Thanks again.

uberlemur thanks for the feedback.
Hopefully peepeesea was able to get it to work or able to restore the old nano backup...
So I guess that means that I have had 2 successful installations. LOL

will this work if you have Amon_RA recovery already?

RECOVERY -TWRP - new method

Hi all.
I found this look through the Kindle thread.
I didn't know it existed until now.
Check it out...looks interesting.
http://www.youtube.com/watch?feature...&v=xMdj_QzfGmw
http://teamw.in/project/twrp2

Naice! Just read about this on AndroidPolice but didn't see that video, nice to see it working right off the bat on a Gtab

wow neat! I wonder what android kernel version this is based of off...

fosser2 said:
wow neat! I wonder what android kernel version this is based of off...
Click to expand...
Click to collapse
Yeah..I bit the bullet and DL it and followed directions.
I couldn't boot into recovery.
It hangs at the birds.
Normal boot runs the underlying ROM fine though.
I'm on a 1.2BL. Was running a series of FB from 8.0 to 10.1 without NVFlashing.
I had only factory reset and wipe and booted into Beasty/Clem Ultimate as the latest ROM. (This FROYO is very fast and stable btw...)
Tried the TWRP 2.0 but couldn't get it to work either.
It's on the YT video though. Obviously it works
I wonder maybe they were on the 1.1 BL...
Anybody running 1.1BL confirm this recovery works?

qkster said:
I wonder maybe they were on the 1.1 BL...
Anybody running 1.1BL confirm this recovery works?
Click to expand...
Click to collapse
Works fine on the 1.1 bootloader.

rajeevvp said:
Works fine on the 1.1 bootloader.
Click to expand...
Click to collapse
Yup, confirmed by Jazzruby.
only for 1.1 BL.
JR did emailed TeamWin re: possible 1.2BL application
thanks..
how do you like it btw?

Looks like they just changed one of the 2 links...both were pointing to the same 1.1 file yesterday.
Now one points to twrp-harmony-12-2.0.0RC0.zip (1.2) & the other to twrp-harmony-11-2.0.0RC0.zip (1.1).
Al

aabbondanza said:
Looks like they just changed one of the 2 links...both were pointing to the same 1.1 file yesterday.
Now one points to twrp-harmony-12-2.0.0RC0.zip (1.2) & the other to twrp-harmony-11-2.0.0RC0.zip (1.1).
Al
Click to expand...
Click to collapse
will give it a try...thanks

fosser2 said:
I wonder what android kernel version this is based of off...
Click to expand...
Click to collapse
It's a (newly compiled) stock VS kernel for 1.1 and a clemsyn kernel for 1.2 bootloaders.
---------- Post added at 09:02 PM ---------- Previous post was at 08:45 PM ----------
qkster said:
JR did emailed TeamWin re: possible 1.2BL application
Click to expand...
Click to collapse
It's easy enough to insert a 1.2 kernel into any recovery partition since the both the boot and the recovery partition on the gTab has an identical structure (necessarily so).
1. Download any of pershoot's kernel zips.
2. Replace the kernel/zImage file in the zip file with either a stock 1.2 kernel from an existing recovery image (Or, just use pershoot's 1.2 kernel).
3. Edit META-INF/com/google/android/updater-script and
a) get rid of the lines involving /system
b) change the string "boot" to "recovery" in the first run_program() and the write_raw_image() directive.
4. Pack everything up into a zip file and then just flash it.
how do you like it btw?
Click to expand...
Click to collapse
Works as advertised.

Has anyone else gotten this to work? I flashed it and now I can't boot into recovery - my GTab just hangs at the three birds (with the message about the recovery key being pressed at the top left). I can boot into Flashback just fine, just not recovery. I'm on BL1.2, and I downloaded TWRP 2.0 for BL1.2 and followed the instructions.

timbck2 said:
Has anyone else gotten this to work? I flashed it and now I can't boot into recovery - my GTab just hangs at the three birds (with the message about the recovery key being pressed at the top left). I can boot into Flashback just fine, just not recovery. I'm on BL1.2, and I downloaded TWRP 2.0 for BL1.2 and followed the instructions.
Click to expand...
Click to collapse
This is a TWRP screwup. Both zip files have identical MD5/SHA1 checksums, which means that both have the same recovery image, and hence, the same kernel--ie. a 1.1 kernel.
This was the reason for my post, above.

rajeevvp said:
This is a TWRP screwup. Both zip files have identical MD5/SHA1 checksums, which means that both have the same recovery image, and hence, the same kernel--ie. a 1.1 kernel.
This was the reason for my post, above.
Click to expand...
Click to collapse
Ah, I see. Did they give any indication when you contacted them that they were going to fix this? I don't know how to replace the kernel in the recovery.img file myself (I can't seem to find anything that can extract or mount the .img file so I can modify it).

timbck2 said:
Did they give any indication when you contacted them that they were going to fix this?
Click to expand...
Click to collapse
Haven't contacted them--I'm running on a 1.1 bootloader, and, as I said, the problem is easy enough to fix on your own.
I don't know how to replace the kernel in the recovery.img file myself (I can't seem to find anything that can extract or mount the .img file so I can modify it).
Click to expand...
Click to collapse
You don't need any tools if you have a 1.2 kernel ready; otherwise you need the unpackbootimg program.
See post #9 and just use a pershoot 1.2 kernel.

I contacted them, and they say the zip downloads have been fixed. I checked, and the BL1.2 download has been updated. I can't try it until I get home this evening, but I will and I'll post the results.
Update: After NVflashing and then installing TWRP 2.0 from the new download, it works as advertised. Very nice! One thing I'm disappointed about is that it doesn't appear to recognize CWM backups.
Update #2: The next time I rebooted and tried to go into recovery, my GTab wouldn't boot again; it got stuck at the three birds image, and did NOT give me the message about the recovery key being pressed. Even worse, it refused to boot normally after this - essentially, it appears that TWRP soft-bricked my tablet. I'm NVflashing again and going back to CWM. Very disappointing.

timbck2 said:
I contacted them, and they say the zip downloads have been fixed. I checked, and the BL1.2 download has been updated. I can't try it until I get home this evening, but I will and I'll post the results.
Update: After NVflashing and then installing TWRP 2.0 from the new download, it works as advertised. Very nice! One thing I'm disappointed about is that it doesn't appear to recognize CWM backups.
Update #2: The next time I rebooted and tried to go into recovery, my GTab wouldn't boot again; it got stuck at the three birds image, and did NOT give me the message about the recovery key being pressed. Even worse, it refused to boot normally after this - essentially, it appears that TWRP soft-bricked my tablet. I'm NVflashing again and going back to CWM. Very disappointing.
Click to expand...
Click to collapse
Same here...
I had NVflashed back to 4349.
Comfirmed the stock 4349 worked.
Booted into cwm.
Wiped everything in cwm. Partition 4096 then back to 2048/0
Aplied the twrp update.
Booted into recovery.
TWRP 2 looks great. The menu and screen is responsive.
Tried wiping with it...looks good
I then flashed a rom with it...Beasty/Clem Ultimate to be exact.
Installation reported complete.
Booted up and...got the birds....nothing else...
Tried going back in recovery... recovery is also gone too...
Soft bricked...
Good thing I know how to nvflashed back to stock but for someone new to gtablet, twrp2 may be bad news.
I saw a few post with people having twrp2 installed...has anyone successfully install a rom with twrp?

I have gone total brick (no boot, no recovery) twice and both times TWRP2 was loaded. I can't prove it is the cause, but I never had that problem before even with heavy duty flashing of ROMs etc.
However, all you really need to do is clear the MSC partition.
Use the --getpartitiontable command in nvflash and figure out what your MSC partition is (mine was #7). Then grab a "stock image" and flash its MSC partition (look in the cfg file, usually 7 although my true blue stock was at 6) into partition 7 with --download.
That has fixed it with no data loss every time for me.
Meanwhile, I've gone back to cwm.
Oh, I should say that TWRP2 did work most of the time. But sometimes I would reboot and just hang permanently until MSC gets reflashed.
I liked it in general, although it looked on the internal SD and not external like the version of CWM I have does. Would be nice to either pick or have a 2nd version. But if it keeps corrupting MSC and hanging the box, it isn't worth the trouble. CWM is clunky but fine.

wd5gnr said:
However, all you really need to do is clear the MSC partition.
Use the --getpartitiontable command in nvflash and figure out what your MSC partition is (mine was #7). Then grab a "stock image" and flash its MSC partition (look in the cfg file, usually 7 although my true blue stock was at 6) into partition 7 with --download.
Click to expand...
Click to collapse
It's better to wipe it clean using the ``--format_partition'' flag to nvflash instead of relying on someone else's partition images.

[HowTo] Root the latest OTA when the HTC Unlocker tool doesn't work

So, you've got the latest OTA (1.55.531.3) and the HTC unlocker tool won't work? Tired of waiting for HTC to issue a fix/resume the OTA? You no longer have to wait in agony.
These are the steps I took to unlock the latest OTA. They worked for me, they may not work for you. Anything you do to your phone is not my responsibility.
That said..
Backup what you can. Your phone is going to be wiped.
Make sure your battery is charged up.
Download the full 1.55.531.3 image. This contains the confirmation splash screen which wasn't loaded on older MT4GSes, and is the reason the unlocker tool won't work on our devices. You can get the full image (it's over 400MB) here:
http://www.filefactory.com/file/c0f....00_11.16.3504.20_2_release_227956_signed.zip
Click to expand...
Click to collapse
Download the CWM recovery image:
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.7-doubleshot.img
Click to expand...
Click to collapse
Rename the full image downloaded in the first step to PG59IMG.zip and place it on the root of the SD card in your phone.
Shut the phone down, remove the battery, and boot back up while holding both the volume down and power buttons down.
The phone will check the PG59IMG.zip file and will ask you if you want to restore that image. You want to do this, but keep in mind this is going to wipe your phone. All data will be lost.
The phone will restore the image. This takes a few minutes. When it's done, you'll be prompted to reboot, and you'll boot into a completely stock MT4GS experience.
Use the unlock tool on htcdev.com to generate your unlock code. The splash screen is now on your phone, and you should be able to unlock (I had no issues).
I rebooted at this point, just to be safe, and set up my phone.
Copy the recovery image you downloaded earlier into the directory where you're running fastboot. Rename it to recovery.img
Shut down, boot into the bootloader/fastboot, and enter the following command to flash CWM recovery:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
At this point, you should probably reboot the bootloader before entering CWM. Once you've done that, you can go ahead and flash superuser/roms/etc.
Here's a pointer to restoring your phone to stock, courtesy of blue:
http://forum.xda-developers.com/showpost.php?p=17424340&postcount=24

So if we've gotten this far, is S-OFF going to gain us anything more? Are we still locked out of certain areas? The tool worked for me, but I'm using the rest of your guide to flash CWM. Thanks for writing it!

xzuhto said:
So if we've gotten this far, is S-OFF going to gain us anything more? Are we still locked out of certain areas? The tool worked for me, but I'm using the rest of your guide to flash CWM. Thanks for writing it!
Click to expand...
Click to collapse
In my opinion, S-Off won't really gain you much more. You'll have to flash kernels separately when flashing ROMs, but that doesn't seem to be a big deal (IMO).
You could probably flash back to the original release software if you wanted, and gain S-OFF with revolutionary, but I haven't tried that and have no idea if it will work.
The only thing you can't do with Unlocked/S-ON is flash radios.

Well in that case this phone is right where I want it. I've never messed with kernels on any phone I've had previously nor have I messed with flashing radios. I just got done completing the steps and I'm now root along with CWM. Great work throwing this up for everyone.

jonnycat26 said:
So, you've got the latest OTA (1.55.531.3) and the HTC unlocker tool won't work? Tired of waiting for HTC to issue a fix/resume the OTA? You no longer have to wait in agony.
These are the steps I took to unlock the latest OTA. They worked for me, they may not work for you. Anything you do to your phone is not my responsibility.
That said..
Backup what you can. Your phone is going to be wiped.
Make sure your battery is charged up.
Download the full 1.55.531.3 image. This contains the confirmation splash screen which wasn't loaded on older MT4GSes, and is the reason the unlocker tool won't work on our devices. You can get the full image (it's over 400MB) here:
Download the CWM recovery image:
Rename the full image downloaded in the first step to PG59IMG.zip and place it on the root of the SD card in your phone.
Shut the phone down, remove the battery, and boot back up while holding both the volume down and power buttons down.
The phone will check the PG59IMG.zip file and will ask you if you want to restore that image. You want to do this, but keep in mind this is going to wipe your phone. All data will be lost.
The phone will restore the image. This takes a few minutes. When it's done, you'll be prompted to reboot, and you'll boot into a completely stock MT4GS experience.
Use the unlock tool on htcdev.com to generate your unlock code. The splash screen is now on your phone, and you should be able to unlock (I had no issues).
I rebooted at this point, just to be safe, and set up my phone.
Copy the recovery image you downloaded earlier into the directory where you're running fastboot. Rename it to recovery.img
Shut down, boot into the bootloader/fastboot, and enter the following command to flash CWM recovery:
At this point, you should probably reboot the bootloader before entering CWM. Once you've done that, you can go ahead and flash superuser/roms/etc.
Click to expand...
Click to collapse
the doubleshot img downloads painfully slow, do you have another link?
edit: also i think you missed somthing here"
[*]Shut down, boot into the bootloader/fastboot, and enter the following command to flash CWM recovery:
"

ac3theone said:
the doubleshot img downloads painfully slow, do you have another link?
...
Click to expand...
Click to collapse
Well, where football is hosting the new PG59IMG.zip file is the only place we have it - i just found it yesterday and we haven't had time to up it anywhere else yet.
We are working on making mirrors for it now - give us some time to get set up with our new data.
---------- Post added at 01:38 AM ---------- Previous post was at 01:33 AM ----------
jonnycat26 said:
In my opinion, S-Off won't really gain you much more. You'll have to flash kernels separately when flashing ROMs, but that doesn't seem to be a big deal (IMO).
You could probably flash back to the original release software if you wanted, and gain S-OFF with revolutionary, but I haven't tried that and have no idea if it will work.
The only thing you can't do with Unlocked/S-ON is flash radios.
Click to expand...
Click to collapse
No, you can't go back to retail factory if you are S-ON. This new PG59IMG.zip I found is the furthest back you can go completely.
With S-ON you cannot replace hboot, or radio - those two are a big deal - i'm still working on an S-OFF solution for S-ON people with hboot 1.45.0013.
With S-OFF I can swap out hboots on a whim, and thrice43 even flashed a Sensation hboot to his doubleshot and it worked out for him - but with S-ON you cannot do this. (and if you could, you would brick)
S-OFF is very much preferable to S-ON UNLOCKED.
I've also had problems flashing OTA updates through stock recovery manually when S-ON where I had no trouble doing so while S-OFF.
There are still a lot of things you can't do with your device while S-ON.
EDIT:
also, all the PG59IMG.zip files I made for people to flash recoveries, hboots, and so on in the dev reference sticky cannot be used by anyone S-ON because they fail the signature checks. My custom PG59IMG.zip files don't have an HTC signature which you must have for an S-ON device to load the PG59IMG.zip file.
...so there are a number of reasons why S-OFF is something to get.

xzuhto said:
Well in that case this phone is right where I want it. I've never messed with kernels on any phone I've had previously nor have I messed with flashing radios. I just got done completing the steps and I'm now root along with CWM. Great work throwing this up for everyone.
Click to expand...
Click to collapse
You must flash a kernel if you want to flash an ICS ROM or any GB ROM with a modified kernel.
Also:
Here's a faster mirror, hopefully: http://www.4shared.com/zip/vVHQuid0/PG59IMG_Doubleshot_TMOUS_15553.html

I see the downsides to s-on but I'm happy to have root and cwm. I will however be excited to get this thing fully unlocked. I won't be messing with custom roms till then. lol
Sent from my myTouch_4G_Slide using Tapatalk

I managed to host it on my Dropbox
Edit:
Oh sorry Lime, I didn't see that you were already hosting it...

this might deserve a sticky?

If anyone is going to mirror it please keep the original filename - we have more then one PG59IMG.zip file with an HTC signature (retail launch and this one).
If they are not named including the software version and radio then people may be confused on what they are getting - thanks guys!

it worked, now to get su. thanks for the guide

delete post

jonnycat26 said:
So, you've got the latest OTA (1.55.531.3) and the HTC unlocker tool won't work? Tired of waiting for HTC to issue a fix/resume the OTA? You no longer have to wait in agony.
These are the steps I took to unlock the latest OTA. They worked for me, they may not work for you. Anything you do to your phone is not my responsibility.
That said..
Backup what you can. Your phone is going to be wiped.
Make sure your battery is charged up.
Download the full 1.55.531.3 image. This contains the confirmation splash screen which wasn't loaded on older MT4GSes, and is the reason the unlocker tool won't work on our devices. You can get the full image (it's over 400MB) here:
Download the CWM recovery image:
Rename the full image downloaded in the first step to PG59IMG.zip and place it on the root of the SD card in your phone.
Shut the phone down, remove the battery, and boot back up while holding both the volume down and power buttons down.
The phone will check the PG59IMG.zip file and will ask you if you want to restore that image. You want to do this, but keep in mind this is going to wipe your phone. All data will be lost.
The phone will restore the image. This takes a few minutes. When it's done, you'll be prompted to reboot, and you'll boot into a completely stock MT4GS experience.
Use the unlock tool on htcdev.com to generate your unlock code. The splash screen is now on your phone, and you should be able to unlock (I had no issues).
I rebooted at this point, just to be safe, and set up my phone.
Copy the recovery image you downloaded earlier into the directory where you're running fastboot. Rename it to recovery.img
Shut down, boot into the bootloader/fastboot, and enter the following command to flash CWM recovery:
At this point, you should probably reboot the bootloader before entering CWM. Once you've done that, you can go ahead and flash superuser/roms/etc.
Click to expand...
Click to collapse
Copy the recovery image you downloaded earlier into the directory where you're running fastboot. Rename it to recovery.img
Shut down, boot into the bootloader/fastboot, and enter the following command to flash CWM recovery:
fastboot flash recovery recovery.img
Cant do this last few steps.Don't understand what to do as yet

Scondrel said:
Copy the recovery image you downloaded earlier into the directory where you're running fastboot. Rename it to recovery.img
Shut down, boot into the bootloader/fastboot, and enter the following command to flash CWM recovery:
fastboot flash recovery recovery.img
Cant do this last few steps.Don't understand what to do as yet
Click to expand...
Click to collapse
You need to transfer the recovery image to the directory with your fastboot.exe file.
You would then need to rename it to recovery.img
Then you boot your phone into fastboot mode, and plug it into the computer.
Open a command prompt, and navigate to the directory with fastboot.exe and run the command:
fastboot flash recovery recovery.img

Thanks got it now.Appreciate the help
---------- Post added at 01:23 AM ---------- Previous post was at 12:53 AM ----------
Scondrel said:
Thanks got it now.Appreciate the help
Click to expand...
Click to collapse
Didn't work for me,I all the way to final step, but once i enter recovery for CWM,and try to flash the superuser file or anything else, it just shows the icon and nothing else happens.Once i click the power button it goes back to the CWM Home screen.Any advice on this guys ?

Scondrel said:
Thanks got it now.Appreciate the help
---------- Post added at 01:23 AM ---------- Previous post was at 12:53 AM ----------
Didn't work for me,I all the way to final step, but once i enter recovery for CWM,and try to flash the superuser file or anything else, it just shows the icon and nothing else happens.Once i click the power button it goes back to the CWM Home screen.Any advice on this guys ?
Click to expand...
Click to collapse
You are using the trackpad to "select" within CWM, not the power button, right?

jonnycat26 said:
You are using the trackpad to "select" within CWM, not the power button, right?
Click to expand...
Click to collapse
Thanks it was 'nt that. There wasn't enough space on the memory card and I didn't have USB debugging on.Got it solved now .Thanks for the speedy responses.Truly appreciated .Feels so good to be a part of this community.

jonnycat26 said:
So, you've got the latest OTA (1.55.531.3) and the HTC unlocker tool won't work? Tired of waiting for HTC to issue a fix/resume the OTA? You no longer have to wait in agony.
These are the steps I took to unlock the latest OTA. They worked for me, they may not work for you. Anything you do to your phone is not my responsibility.
That said..
Backup what you can. Your phone is going to be wiped.
Make sure your battery is charged up.
Download the full 1.55.531.3 image. This contains the confirmation splash screen which wasn't loaded on older MT4GSes, and is the reason the unlocker tool won't work on our devices. You can get the full image (it's over 400MB) here:
Download the CWM recovery image:
Rename the full image downloaded in the first step to PG59IMG.zip and place it on the root of the SD card in your phone.
Shut the phone down, remove the battery, and boot back up while holding both the volume down and power buttons down.
The phone will check the PG59IMG.zip file and will ask you if you want to restore that image. You want to do this, but keep in mind this is going to wipe your phone. All data will be lost.
The phone will restore the image. This takes a few minutes. When it's done, you'll be prompted to reboot, and you'll boot into a completely stock MT4GS experience.
Use the unlock tool on htcdev.com to generate your unlock code. The splash screen is now on your phone, and you should be able to unlock (I had no issues).
I rebooted at this point, just to be safe, and set up my phone.
Copy the recovery image you downloaded earlier into the directory where you're running fastboot. Rename it to recovery.img
Shut down, boot into the bootloader/fastboot, and enter the following command to flash CWM recovery:
At this point, you should probably reboot the bootloader before entering CWM. Once you've done that, you can go ahead and flash superuser/roms/etc.
Click to expand...
Click to collapse
These instructions worked perfectly! Can not believe it worked. This should be stickied! Thank you.

tbalden said:
this might deserve a sticky?
Click to expand...
Click to collapse
revo420 said:
This should be stickied!
Click to expand...
Click to collapse
Eh, why not. Done .

[Q][A700]How to undo CWM and restore factory recovery

Hi,
I'm in the situation of having a working tablet, but the dodgy version of CWM. The original thread has been deleted and I remember there was adb command at the end to stop the original update.zip from flashing the factory recovery, but not what it was so I can reverse it !
So if anyone can help me out, that would be great, so I can avoid a bricked device !

jpearn said:
Hi,
I'm in the situation of having a working tablet, but the dodgy version of CWM. The original thread has been deleted and I remember there was adb command at the end to stop the original update.zip from flashing the factory recovery, but not what it was so I can reverse it !
So if anyone can help me out, that would be great, so I can avoid a bricked device !
Click to expand...
Click to collapse
go finding a original recovery dump,and flashing it in fastbootmode.

Has anybody been able to find a stock recovery for the A700? JP, I also flashed this broken CWM, thankfully I haven't used it but I want to put the stock one back on to avoid any issues.

1
californiarailroader said:
Has anybody been able to find a stock recovery for the A700? JP, I also flashed this broken CWM, thankfully I haven't used it but I want to put the stock one back on to avoid any issues.
Click to expand...
Click to collapse
reflashing the official update.zip
but,delete the first and the third comands in the updating list,this could avoid wiping/formating action to avoid damage to the /data partition.

lsnc said:
reflashing the official update.zip
but,delete the first and the third comands in the updating list,this could avoid wiping/formating action to avoid damage to the /data partition.
Click to expand...
Click to collapse
Thanks! However, the US Version doesn't have an update for it, at least not yet, and I haven't been able to find a stock US A700 ROM.

So we would need to rename the install-recovery.old back to install-recovery.sh in /system as this was disabled in CWM ??

So has anyone managed to successfully put on the stock recovery ?? !!

jpearn said:
So has anyone managed to successfully put on the stock recovery ?? !!
Click to expand...
Click to collapse
Take a little advice folks. If you don't know what you're doing, and your tab is running fine, don't be messing with anything. Just leave it alone til a better method comes.
My guess, if you rename your recovery.sh, is that when you boot, you will either get;
A. a "loading recovery kernel" message that just stays there
or
B. an "invalid recovery image", or something similar.
MD

Moscow Desire said:
Take a little advice folks. If you don't know what you're doing, and your tab is running fine, don't be messing with anything. Just leave it alone til a better method comes.
My guess, if you rename your recovery.sh, is that when you boot, you will either get;
A. a "loading recovery kernel" message that just stays there
or
B. an "invalid recovery image", or something similar.
MD
Click to expand...
Click to collapse
That's what I'm doing, I'm just leaving the CWM on there until somebody comes up with a fixed version.

californiarailroader said:
That's what I'm doing, I'm just leaving the CWM on there until somebody comes up with a fixed version.
Click to expand...
Click to collapse
Sounds like a plan I'll keep things working for now, thanks !

jpearn said:
Sounds like a plan I'll keep things working for now, thanks !
Click to expand...
Click to collapse
View attachment updater-script.rar
use this attachment to replace the original file,then reflash update.zip via cmw.
'cos i delete the formating commands in the list,u could reflash the official package to restore the official recovery.

lsnc said:
View attachment 1190247
use this attachment to replace the original file,then reflash update.zip via cmw.
'cos i delete the formating commands in the list,u could reflash the official package to restore the official recovery.
Click to expand...
Click to collapse
I don't understand these instructions. What original file is being replaced? What update.zip are you referring to?
EDIT
Well, I tried to swap out the update script that came in the ROM: SDs_Acer_A700_AV043.RV00RC00_AV043.RV07RC04_EMEA_CUS1, with the one provided above and seemed to have made some progress...I put on an external SD card and renamed to update and then flashed it through the CWM recovery and it completed. A random offset was noted and then the SD update completed note. However, when I rebooted the device it stuck at the Acer logo and never went any further.
EDIT
So, it then occurred to me that the flash through CWM was probably only partially successful - maybe the replacement of the recovery worked. So, I took the same ROM I noted above, unmodified, placed on the external SD card, renamed, etc. and flashed it and it worked - I never saw any signs of CWM during this process. I hope this helps others too.
EDIT
Looks like I spoke too soon...the flash never got past a 1/4 of the progress bar. Looks like I still have a non-functioning device.

lsnc said:
View attachment 1190247
use this attachment to replace the original file,then reflash update.zip via cmw.
'cos i delete the formating commands in the list,u could reflash the official package to restore the official recovery.
Click to expand...
Click to collapse
Hi, I'm a A510 user. I used the CWM to wipe data/factory reset, after that i cant flash any zip, and even cant enter the system. When i turn on the tab, it stuck on 'iconia tab' LOGO, I tried to hard reset, then i got a 'Unrecoverable bootloader error (0x19000008)'
I enter the fastboot and flash the stock recovery back. next i use the recovery to flash update.zip as usual, but every time the flash will stuck in 1/5 of the whole progress bar, I changed it with other rom zip, or even change the SD card, it didn't work anyway!
every time the flash stuck in the same place of the whole progress bar, i guess it is not an accident! After read your solution, I check the script in my zip, then i delete 2 lines about 'format' command. I think this time will be ok! but to my surprise the green turtle fell down when flashing.
I think the idea is great, but it maybe make the script incomplete, so it cant be flash in.:crying: