yashsingh1/xdaforums huggingface dataset:
[EVO 4G Android Development] whitslack:
If you didn't remove or modify any system apps that have received changes in this update, then it should work just fine. It won't hurt anything to try it. It'll fail on "apply_patch_check" if it doesn't like something about your installation. That happens before it's made any alterations to your phone, so there's no harm in giving it a try.

And yes, since I removed the recovery.img from this update, it will not change your recovery, so you will be able to restore Nandroid backups if something somehow goes wrong. (Don't take the battery out while it's flashing the radio, though. That *would* brick your phone.)
[EVO 4G Android Development] MadhouseMedic:
Whitslack, Thank you so much for the recovery idea, it worked perfect for pushing the new build.prop onto the phone. Now i am having problems flashing this with the clockwork mod.

It's saying

assert failed: apply_patch_check("/system/bin/debuggered", "05b00c5b/c3340e37d882922be07bf67ffbaa948", "c151b753a01259b00a8c221e9a0bdecc6acbdf")

E: Error in /sdcard/OTA_supersonic_1.47.651.1-1.32.651.6_rootsafe-Sprint.zip

(Status 7)

Installation Aborted
[EVO 4G Android Development] telugite:
Thanks whitslack
[EVO 4G Android Development] whitslack:
You'll still have to overwrite the build.prop with the stock version (linked in the OP) in order for the incremental update to apply. The most direct way of doing that is to use adb push, although there are other ways. My next reply will talk about one of those other ways.
[EVO 4G Android Development] Zabalba:
I'm attempting to flash your zip (Sprint TV, and Qik) via Recovery Console(RA I believe).
[EVO 4G Android Development] whitslack:
If you don't want to use adb push to put the build.prop in your /system directory, there is a way you can do it entirely on the phone.

Download the build.prop-1.32.651.6 file to your SD card. You can even use the phone's browser to do this.

Use a file manager to move the build.prop-1.32.651.6 to the root of your SD card if it's not already there.

Open a terminal emulator on the phone. If you don't have one, try this one. (You can search for "Terminal Emulator" in the Android Market.)

Once you have a command prompt on the phone, type su and press enter.

Press "Allow" if the Superuser Permissions app asks permission.

Enter these commands EXACTLY as shown:

mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
cat /sdcard/build.prop-1.32.651.6 > /system/build.prop
reboot recovery

This is not an easy method because it requires you to type all kinds of crazy symbols using the on-screen keyboard, and the terminal emulator doesn't really support the touch-and-hold method of getting symbols from the virtual keyboard. Therefore, I don't recommend this method, as it's very easy to screw up. But it would work if you did it perfectly.
[EVO 4G Android Development] kpoz:
You're a fantastic OP. Thanks for the incredibly prompt response. Place a donate link somewhere!

I'll be applying your update after I hear about the alternative ways to overwrite the build.prop haha.

Also, one final (wait, I'll probably need to take that back at some point) question: you mentioned the "stock version linked in the OP" with regard to the build.prop file. Is that flashed before or after the update.zip file?
[EVO 4G Android Development] halorin:
How did you manage to downgrade?
[EVO 4G Android Development] whitslack:
Just a note, it looks like you selected the wrong zip to flash. You want the one that ends in -Sprint.zip if you want it to update Sprint Qik and Sprint TV.

From that error message, it almost seems like your recovery program is not understanding the syntax of the update script. Could you try switching to the recovery.img linked from Toast's Part 2? That's the one I used, and the update installed fine.

Note, this isn't an issue with anything I did to make this update; the official OTA update wouldn't have worked either. Your recovery program apparently doesn't understand the newer update

r

-script syntax, only the older update-script (no "r") syntax.
[EVO 4G Android Development] Rene2.5RS:
Thanks for the update whitslack! Everything went smoothly
[EVO 4G Android Development] whitslack:
Replace build.prop file on the phone with the one linked from the OP.

Flash update zip linked from the OP.

The update zip will refuse to apply if you still have the build.prop from Flipz's rooted stock ROM. The one linked from the OP is the *really* stock one.
[EVO 4G Android Development] whitslack:
Your copy of /system/bin/debuggered must be different from the one in the stock 1.32.651.6 ROM.

Try flashing this ROM (which is purely stock, plus su, a super-old version of the Superuser Permissions app, and an extra line in /system/build.prop, which is the reason that file has to be repaired before this update can work). Then do this update from the beginning.
[EVO 4G Android Development] drmacinyasha:
Alright. Downgraded again, then upgraded again, still getting permission errors on su and wonky outputs of commands, so I rebooted into recovery, installed Super User Permissions (the one with the downgraded ROM is apparently buggy-as-hell) and now everything's working fine. Going to be doing a Nandroid backup then get risky and try installing busybox.

I used flipzmode's OTA Update 1.32.651.6. Just copy it to SD card, flash it, reboot, copy radio update to SD card, reboot to recovery, flash radio update, reboot. Voila, downgraded.

EDIT: And success! Busybox installed. Now to just find that pesky remount command...
[EVO 4G Android Development] Zabalba:
Thanks again for your reply.

Correct me if I'm wrong but I believe in the 50 step tutorial to root the EVO uses toast's files. Is there any easy way to update it to that recovery.img so I can attempt your update again?

P.S. I renamed the zip without the -Sprint. :D
[EVO 4G Android Development] m03sizlak:
OP, this looks pretty sweet and is exactly what I've been waiting for (should hold me over until froyo comes in 2-3 weeks). I'm fully nand-unlocked running the .6 rooted stock.

My *only* concern is what was said here about mtg-eng needing to be re-flashed to the /misc partition after applying this incremental update. When I used toast's root/nand-unlock method, my understanding was that something "special" was flashed to the /misc partition...does this update overwrite that? Should I reflash /misc immediately after applying this incremental update? Can you (or someone else) elaborate on this a bit?

Also, would it be a good idea to change the build.prop AFTER applying this incremental update to make sure that future OTA updates fail?

Thanks!
[EVO 4G Android Development] whitslack:
There are two main ways of flashing a recovery. Pick one:

Using flash_image:

Obtain flash_image.zip from Toast's Part 2.

Extract it and put the flash_image program file on your SD card along with the recovery.img.

Start up adb shell and issue these commands:

su
cat /sdcard/flash_image > /app-cache/flash_image
chmod 0755 /app-cache/flash_image
/app-cache/flash_image recovery /sdcard/recovery.img

Using fastboot:

Obtain fastboot by some means.

Reboot the phone into the bootloader. Easiest way is to turn it off and then turn it back on by holding Volume Down and Power until the white bootloader screen appears. Then select FASTBOOT from the menu.

Run this command on your computer:

fastboot flash recovery recovery.img

The fastboot method will only work if you're using an engineering SPL (i.e., you've gone through Toast's Part 2).
[EVO 4G Android Development] whitslack:
As far as I can tell, this update doesn't touch the misc partition. There are only these images in the firmware.zip file it contains:

boot.img

radio.img

wimax_25641R01.img

I would expect there to be a misc.img if they were overwriting that partition. I may be wrong about this, though.

The previous post about the mtg-eng was saying that my update means that it is still possible to reflash the mtg-eng later if ever there is a need to do so. It doesn't suggest that this update actually changes that partition.

You can add some crap to your /system/build.prop if you want to, to make it impossible for an incremental OTA update to patch it. Seems like more of a hassle than it's worth to me, since OTA updates always ask before installing, and I always say no.
[EVO 4G Android Development] gagdetdad:
Great job whitslack! Its been a while but felt the need to post this.

I was already "stock rooted" and followed exactly the steps listed in Post#1 and my update went smooth.

Verified the information in About Screen., however here are my observations

1. adb remount results to "remount failed: Operation not permitted"

2. adb shell

$ whoami

whoami: permission denied

$ su

Permission denied

here1here2here3here4here5$ <------- Look at the prompt I get

3. 4G not verified because of no 4G coverage.

I am wondering if the commands in the updater-script incorrectly set the permissions for 'su' or maybe the symlinks didn't get repaired? Just a thought.

Meanwhile I am going to try few things I know.

Assuming NAND is still unlocked I should be able to restore.
[EVO 4G Android Development] HPLouis:
Hi,

When I try this method, everything goes well except for the last line. it's telling me that reboot is not allowed. Can anyone help me?

Henry
[EVO 4G Android Development] mrsexkey:
Everything worked fine except that for whatever reason i cant get Titanium backup to open up now. Did the new update affect it ?
[EVO 4G Android Development] joeykrim:
i could be wrong, but as far as i can tell, they didn't change the bootloader, hboot.img, as that wasnt included in the OTA update.zip, but they did change the MainVer which is stored in the misc partition through the radio.img update.

they are preventing OUR leaked versions of the userdebug and eng zips from being flashed because they have a version number which is older than the MainVer this OTA update loads into our misc partition.

our custom recovery could flash most parts of the PC36IMG.zip files but the OTA update.zip also flashes back the stock recovery overwriting the custom recovery to prevent our PC36IMG.zip and anything else from being flashed.

if im wrong, it'd be great to have somebody explain with greater clarity.

that isnt 100% true. toast's step 1 (userdebug) allows write access to /system from recovery mode where as toast's step 2 (eng build) allows write access to /system from recovery and normal android mode.
[EVO 4G Android Development] whitslack:
adb remount won't work after the update because adb isn't root by default in the stock ROM. You can change the /default.prop file if you want adb shell to start out as root. You can still do the mount -o remount,rw command after switching to root, even if you don't set adb to start up as root.

I suspect that you have an old su binary at /system/bin/su. That should be a symlink to /system/xbin/su. My guess would be that unrEVOked put the /system/bin/su binary there. My update doesn't restore permissions on /system/bin/su because on my phone it's a symlink to /system/xbin/su, and symlinks don't have their own permissions.
[EVO 4G Android Development] joeykrim:
i agree with everything you've said. since the main version on my phone has been updated by loading the official OTA with all the files you listed above and the only method we've seen of changing the MainVer is thru flashing the misc partition, i'm left to assume the Radio.img updates the MainVer and its stored in the misc partition.

if you've flashed the radio.img, try loading the eng or userdebug PC36IMG.zip or using one of our two RUU .exe, the hboot should spit out the MainVer error.

i'm also guessing by flashing the mtd-eng.img to the misc partition, it will clear this error.

i've only been able to do get the MainVer error, not fix it since i've lost root.

i could be wrong, but everything i've seen posted in this board that i can remember, so far seems to point in this direction.
[EVO 4G Android Development] acrh2:
People are fond of donations here.

Why not start a donation to bribe an HTC tech to make another leak of whatever is needed to attain root? :)
[EVO 4G Android Development] drmacinyasha:
You're having the same problems I did. Install a new copy of Superuser Permissions (

su-2.1-e-unsecure-signed.zip on xdaforums.com/showthread.php?t=682828 ). Just copy the zip to your SD card, reboot into recovery, and install the zip. Reboot back to Android and try again, you shouldn't have a problem with su or "adb remount".
[EVO 4G Android Development] whitslack:
True. And this was confirmed in Post #83 of this thread.
[EVO 4G Android Development] kpoz:
To enter the above adb commands "exactly as shown", do I need to hit enter after "system", "prop" and "recovery" (aka at the end of every line) or do I just keep typing?

Also, after this when I install the update that includes Qik and Sprint TV, do I need to rename the file as "update.zip" or do I just leave it with the same name and then "install from sd card" while in recovery?

Again, thank you, and please tell me where I (and others) can donate for the time you've spent helping everyone out.
[EVO 4G Android Development] Zabalba:
Ok, I attempted the first set of instructions and it told me there was not enough space to work....

It looks like the second set of instructions worked. I was able to flash the new recovery using that.

After that was completed I attempted to flash the zip via the new recovery and it provided the same error :(
[EVO 4G Android Development] whitslack:
Yes, press Enter after each line.

You don't need to rename the zip file. The recovery program should let you pick which update zip you want to flash.

I didn't intend to collect donations, but if you really feel obliged, my PayPal-enabled email address is matt (at) whitlock PERIOD name. (Sorry, I can't type it any more clearly than that without attracting spam bots to it. Yes, it's a .name address. Yes, that really works.)
[EVO 4G Android Development] whitslack:
I'm really sorry; I don't know what the problem is. If you're using the recovery.img from Toast's Part 2, the update script should run fine.
[EVO 4G Android Development] drmacinyasha:
Just out of curiosity (and a few minutes of searching hasn't brought up an answer) how can one go about editing the default.prop so that it stays ro.secure=0? From what I can see, it's part of the ramdisk and gets reset every time you reboot. Is there another copy hidden somewhere that it restores from, or would you have to create a full-blown ROM/update.zip?
[EVO 4G Android Development] kpoz:
Hmm status 7 error when attempting to install the update.
[EVO 4G Android Development] Zabalba:
Thanks for the assistance though. I suppose I will wait until there is a stock rooted ROM I can just flash too.
[EVO 4G Android Development] kpoz:
I used Astro File Manager to make sure the build.prop file was in the root of the sd card.

I messed up the first time on the second line in the terminal portion, but then I backed out and correctly entered the commands. The phone rebooted and I attempted to install the update when I received the installation abortion notification.
[EVO 4G Android Development] whitslack:
The ramdisk is initialized from the boot.img. It's actually an initramfs. Because this update reflashes the boot.img, we lose the ro.secure=0 that Flipz's ROM had. You could always unpack it, change the file, repack it, and reflash it. Personally, I don't use root from adb shell often enough to go through the trouble of deviating from stock in this regard.
[EVO 4G Android Development] kpoz:
I'm currently restoring and then I'll try again after you chime in.

Here is the error message I received:

failed: apply_patch_check (“system/app/GSD.apk ––– E:Error in /sdcard/OTA_Supersonic...Sprint.zip
[EVO 4G Android Development] whitslack:
Did the installation process complain that the /system/build.prop file was wrong? It would say something like assert failed: apply_patch_check("/system/build.prop", yadda yadda yadda.

If it was complaining about some other file, or if you saw an E:unknown command, you have another problem besides the /system/build.prop file.
[EVO 4G Android Development] tcd2004:
If I am running the stock .6 software rooted, can I install this through recovery mode instead of using the adb prompt? If so, how would I go about doing it this way. I'm guessing I just put both files on the root of my sd card and then boot into recovery, but what options do I select once I'm in the recovery mode? Little bit of a noob, so thanks for the help
[EVO 4G Android Development] skunkiechris:
I'm getting this:

assert failed: apply_patch_check("/system/bin/reboot", "940543d1d4b853eE:unknown command [092928c888c8fbae42d250900",]

E:Error in /sdcard/OTA_Supersonic_1.47.651.1-1.3.2.621.6_rootsafe-Sprint.zip
(Status 7)

Installation aborted

I'm currently running joeykrim stock rooted .6 release (his v1.08), with Amon-RA 1.7.0.1 recovery. I did try changing my recovery to the (older) version linked in Toast's part two instructions, but it did not help.

Any thoughts?
[EVO 4G Android Development] kpoz:
This is the error message I received: failed: apply_patch_check (“system/app/GSD.apk ––– E:Error in /sdcard/OTA_Supersonic...Sprint.zip
[EVO 4G Android Development] whitslack:
You're definitely not using a rooted stock ROM. Wait for a full update to 1.47.651.1 (or try Calkulin's).
[EVO 4G Android Development] whitslack:
Hmm, it can't be a problem with Amon-RA incorrectly parsing the updater-script file. (I couldn't get Amon-RA to accept my signatures at all, so it didn't even get as far as you got.)

There was a link to a post from another thread a few pages back talking about some tool that had modified the reboot binary.

People: seriously, this update only works if you are usually a totally stock system with su added to it. If you've changed anything else, the patches aren't going to apply. You'll have to use a full ROM.
[EVO 4G Android Development] kpoz:
Ok, thanks for the tip. I thought I was. I'll get in touch with Joeykrim.

Should I remove the build.prop file from the root of my sd card?
[EVO 4G Android Development] whitslack:
You're going to have to revert the /system/build.prop some way, or the incremental update is going to refuse to patch it. My instructions in the OP talk you through how to do that. You're going to have to use adb to do it. If that's beyond your capability or patience, wait for a full ROM of 1.47.651.1 to be made from the yet-to-be-released RUU (or try using Calkulin's ROM, which is presumably reverse built from a rooted stock system with the OTA update applied).
[EVO 4G Android Development] skunkiechris:
Ohhhh, that did it - I know what it is, I applied the quickboot fix. I was misreading the error. Thank you!!
[EVO 4G Android Development] whitslack:
Okay, everyone, I simply cannot devote any more time to this. I'm sorry if people still have questions, but I can't take time to answer them. I've given you everything I know.

*poof*
[EVO 4G Android Development] kpoz:
Cheers.

Everyone donate!
[EVO 4G Android Development] joeykrim:
as ive posted before in a diff thread and is in the unrevoked FAQ

reboot has been modified in quite a few custom ROMs to allow commands like reboot recovery and reboot bootloader which it seemed the original reboot binary didnt

adb push this file into your system/bin directory

http://www.joeyconway.me/evo/stock/reboot-ruu6

adb push c:\downloads\reboot-ruu6 /system/bin/reboot

overwrite the build.prop with the one listed in this OP

adb push c:\thisthread\build.prop /system/build.prop
[EVO 4G Android Development] kpoz:
Ah, see, that's why I wanted to contact you. I remembered your post about the reboot modifications, but I wasn't sure if that applied here. I'm still new to all of this, and it can be difficult searching through various threads to try and piece a question or answer together.

I should be able to handle this, and I'll report back. Since I can't seem to find your original post where you discussed the original reboot binary, are there any consequences to replacing the custom reboot binary in your ROM with the original reboot binary? Will I still be able to reboot into recovery in ROM Manager?
[EVO 4G Android Development] gagdetdad:
Thank you very much this worked for su.

For adb remount, change "ro.secure=1" to "ro.secure=0" in the /default.prop
[EVO 4G Android Development] dpbutler65:
I installed without a problem, but it seems as if I lost root, wireless tether nor titanium back can gain root access, which they had prior, I updated superuser, still nothing...
[EVO 4G Android Development] fido9956:
4G stuck "Scanning"

Hi all,

Just wanted to post a warning.

After this update, my 4G is stuck in the "scanning" state and will not connect any longer.

Anyone experiencing this - and anyone have a solve. Looks like I will need to nandroid back to the previous version and Baseband in the mean time.
[EVO 4G Android Development] whitslack:
That's disappointing. This can only mean that HTC added some new function to their recovery program that we don't have in our custom recoveries. Once someone figures out what they added, maybe the same functionality can be added to Amon RA, Clockwork, etc.
[EVO 4G Android Development] wsantiagow:
By the way, EVERYTHING completed

sucessfully

. BUT DID NOT WORK.

No 4G at all. It just goes into the scanning mode. I did the Profile and PRL updates too.

I will be holding out for now. Good luck to the rest of you.
[EVO 4G Android Development] whitslack:
For what it's worth, /system/bin/wimax_mtd on my phone reports the version of the installed WiMAX firmware as 4.6.2.2v25641_. That same version string is embedded in the wimax_25641R01.img file that was included in the firmware.zip in this OTA update. This leads me to believe that the WiMAX firmware was correctly updated. I wish I had a way of testing whether my WiMAX works.
[EVO 4G Android Development] Rene2.5RS:
I have the same issue. Seems like I will have to do a nandroid restore.
[EVO 4G Android Development] dpbutler65:
yeah, nandroid brought it back, but i wish i knew whether or not 4G was working, because i cant use it now, but i will need it a week from now when im going to baltimore...
[EVO 4G Android Development] Diesektor:
For those that got this working, how much better is the battery life?
[EVO 4G Android Development] Rene2.5RS:
I had to reflash the first radio update after the nandroid restore. I don't have 4G any where near me until I goto vegas in july
[EVO 4G Android Development] whitslack:
If /system/xbin/su exists and has permissions -rwsr-sr-x, and /system/bin/su is a symlink to /system/xbin/su, and /system/app/Superuser.apk exists, then everything is correct on the root side of things.
[EVO 4G Android Development] kpoz:
Wayyyyyyy over my head.