yashsingh1/xdaforums huggingface dataset:
[EVO 4G Android Development] frankenstein\:
No other way that I know. I tried directly editing the xml file but the changes did not persist. They were immediately reverted to the current values upon reboot which makes me think the xml file is generated at each boot from data stored elsewhere. Reboot is required for the change to take effect.

Why can't you run the ##data# code? I struggled to get it to run until I hooked the phone up via usb and ran logcat while inputting the ##data# code. There I saw that the phone wasn't resolving the localhost name properly and that I had to make some changes to the /etc hosts file to fix this. basically, the hosts file requires a specific number of spaces between the ip and name for it to be cached properly and I had modified mine in an attempt to block adds and broken it. logcat was posting java class errors with references to the localhost name and indicating that the name was unknown / couldn't be resolved.

In logcat I saw errors like these intersperced among system.err entries attempting to call various java classes:

W/System.err( 448): java.net.UnknownHostException: localhost

V/DMAgentConnector( 448): connection fail:java.net.UnknownHostException: localhost
[EVO 4G Android Development] mrkmrk:
To be completely honest, I don't know the particular reason that I can't run the code. Hero_Over said that he's not sure why, either, and it's just a problem with his ROM... hopefully, it's resolved soon.

As far as your process, if I wanted to try that, how would I go about it? As far as I know, I can only get adb to mount properly while the phone is in recovery, thus couldn't do the process which you described.

Thanks for the quick and thorough response.
[EVO 4G Android Development] stylz3:
I tried to follow the steps in this thread to see if 4G is working but I can't find the .tree.xml file once I enter the ls /data/misc/wimax/ command. I just get socket when I press enter. I also noticed whenever I power up my phone and go into settings under 4G it says fail. Futhermore, when I go into settings>about phone>Hardware information my wifi, bluetooth and 4G MAC addresses are unavailable, does this mean anything?
[EVO 4G Android Development] jbcain:
i do NOT have a .tree.xml file in the /data/misc/wimax directory.

hell, there's nothing in my sd card/data except a titanium backup folder. am i missing something?

no 4g

just scans

flashed new radio

update prl/pro

flashed new wimax

update prl/pro

verified correct mac

4g toggles and just "scans"

again, i have nothing in my sdcard/data folder...

Microsoft Windows [Version 6.0.6002]

Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\Cain>cd c:\

c:\>cd

c:\

c:\>cd android\tools

c:\android\tools>adb

Android Debug Bridge version 1.0.26

c:\android\tools>adb shell

# ls /data/misc/winmax

ls /data/misc/winmax

/data/misc/winmax: No such file or directory

#
[EVO 4G Android Development] TheMike1:
Ok, thank you. It seems DC 3.2.2.1 already is based off of this update, so I should just download, wipe, and flash that and I will have this software correct?
[EVO 4G Android Development] Badious:
Ah I see, I misread and assumed it worked on Fresh, sorry about that.
[EVO 4G Android Development] whitslack:
Should be fine. The worst that might happen is that Clockwork Recovery might refuse the signatures in the update zip. In that case, nothing would have been altered on your system.

I think I did read that DamageControl had already incorporated the 1.47.651.1 update into his ROM. I have no idea how he did that, though, so I don't know whether his update will do the WiMAX flash like the stock update process does. Good luck!
[EVO 4G Android Development] hecklbrg:
If I am running a stock rooted .36 ROM do I just flash this on top? Or do I need to do a wipe first?

Also, if I upgraded to Caulkin's stock 1.47 ROM and flashed the radio and the wimax fixes (although the wimax fix was the one that Caulkin said didn't write...not his subsequent update he posted in the forum around page 12) is this going to be ok?

Just want to make sure that flashing the radio AGAIN will be ok for it.

I'm also assuming that I should run my nandroid to place me back at stock .36 before doing this
[EVO 4G Android Development] whitslack:
I haven't seen a stock .36 ROM. The version before the latest update was 1.32.651.6. This update will only apply to that version. You should *NOT* wipe, or this update will have nothing to patch. This is an incremental update, not a full update.

You can flash the radio again. I've flashed mine three times with the same version now, and it still works fine.

You must restore your backup so you're running 1.32.651.6 stock + root. This update will not apply over Calkulin's update.
[EVO 4G Android Development] acrh2:
TO OP:

Aside from changes to radios,

what do you think would be different between your method and this

EVO_1.47.651.1_Rooted.zip

http://xdaforums.com/showpost.php?p=6983017&postcount=1

?

(I think I already know that PRI version would be different, but what else?)
[EVO 4G Android Development] wsantiagow:
i am on a fully rooted 1.47.651.1 and I flashed the Wimax and Radio. Now the Wimax just goes into a scanning loop. I am reaching for anything right now.
[EVO 4G Android Development] hecklbrg:
Is there any reason to do this even if I've already done the other stock rooted 1.47 update?
[EVO 4G Android Development] whitslack:
That image is a full update, which wipes the system partition and populates it from scratch. My update is the incremental update that Sprint/HTC send out. As such, it's a much smaller file, since it only includes the changes from the previous version to the current version. That also means it won't apply to anything other than 1.32.651.6, whereas the EVO_1.47.651.1_Rooted.zip will overwrite anything.

I preferred to stick with the official upgrade image rather than trusting that a full image was composited cleanly. Flipz has the same opinion, I daresay, as he's decided not to release a stock+root full ROM until HTC has released the RUU for this.

EDIT: The PRI doesn't change. I'm still at 1.34_003, which came from the engineering SPL that toastcfh posted. That's what gives us unlocked NAND.
[EVO 4G Android Development] whitslack:
The only reason might be if the other update failed to properly flash the WiMAX firmware. I don't know whether it does or not. This one probably does, since it's almost exactly the official update file that was sent out over the air.
[EVO 4G Android Development] acrh2:
I just read a conversation here

http://xdaforums.com/showpost.php?p=7011167&postcount=76

This man said that the OTA patched a bunch of security holes, including the debug/eng bootloader (hboot?) What would happen with this incremental update?
[EVO 4G Android Development] whitslack:
# mount
rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
none /dev/cpuctl cgroup rw,cpu 0 0
/dev/block/mtdblock4 /system yaffs2 ro 0 0
/dev/block/mtdblock6 /data yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock5 /cache yaffs2 rw,nosuid,nodev 0 0
tmpfs /app-cache tmpfs rw,size=8192k 0 0
/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
# ls /system/does_it_write
/system/does_it_write: No such file or directory
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
# mkdir /system/does_it_write
# ls /system/does_it_write
# mount -o remount,ro -t yaffs2 /dev/block/mtdblock4 /system
# ls /system/does_it_write

Seems that NAND is still unlocked.
[EVO 4G Android Development] Zabalba:
Please forgive my misunderstanding, I'm still learning about rooting.

OK, so I rooted my phone with the 50-something step tut which I believe to be a rooted stock evo ROM. When the previous update for the radio and baseband came out (.6) I updated it (http://xdaforums.com/showthread.php?t=697636). Since ran into the same error that will not allow me to update, Am I in fact even running a rooted stock .6 EVO ROM?

The only reason I rooted the phone is to have the ability to tether. I was interested in flashing a more customized ROM much later on.
[EVO 4G Android Development] acrh2:
So, what do you think is going with this update?
[EVO 4G Android Development] Knight2011:
How do save the build.prop? clicking on it shows it as a bunch of text

example: ro.config.ringtone=Windchimer.mp3

ro.config.notification_sound=Little.mp3

# begin build properties

# autogenerated by buildinfo.sh

ro.build.id=ERE27

ro.build.display.id=1.32.651.6

ro.build.version.incremental=171253

ro.build.version.sdk=7

ro.build.version.codename=REL

How do i save this so i can drop it to the memory card.Do save it as a text file?

thanks
[EVO 4G Android Development] Rhys'Droid:
Right click - Save As
[EVO 4G Android Development] HPLouis:
Hello Whitslack,

Thank you for the hard work you've put into this and also for sharing it. I need a little bit of help. I downloaded the update file and placed it on my SD card, but when I try to download the build.prop file, it opens up into a text file.

How do I download the build prop file so I can place it on my SD card and update my phone?

Thank you,

Henry
[EVO 4G Android Development] HPLouis:
Thanks for the response. I had the same question.

Henry
[EVO 4G Android Development] wsantiagow:
I rolled everything back from a Nand Restore to 1.32.651.6 and baseband 1.39.00.05.31 and now my 4G is working again.
[EVO 4G Android Development] hecklbrg:
I'm sorry, I am confused here.

What do I do with the build.prop file? Is just putting it in the base of my SD card with the update.zip file sufficient? What exactly should I do with the file?

I appreciate the help. I have the other rooted 1.47 can roll back to my .6 and would like to use this here.

Thanks
[EVO 4G Android Development] YeOj:
Will this incremental update work if I am rooted using the unrevoked 2 method? Can I just download this zip file and use clockwork mod to flash it?
[EVO 4G Android Development] whitslack:
You can know if you're running a rooted ROM if you have a file at /system/xbin/su. Check by open a shell (either through adb or with a terminal emulator on the phone) and typing ls /system/xbin/su If it says "No such file or directory," you're not rooted.

I won't presume to know what all Sprint/HTC changed in this update. I've read some comments that say the SMS app seems snappier, and I have to agree. I've also read that battery life is dramatically improved. I haven't gone off AC yet, so I can't comment.
[EVO 4G Android Development] Knight2011:
Thanks for the quick reply

new problem

I put the two files on the sdcard and ran update.zip and i get

assert failed:apply_patch_check("/system/build.prop", "189001ad085fe035d008dcfcec19341a yada yada.....bunch of numbers and letters

E:Error in /sdcard/update.zip

(status 7)

Installation aborted

is it because i renamed the file to update.zip?
[EVO 4G Android Development] whitslack:
Follow the instructions in the original post. The build.prop file has to go in /system on your phone. It will overwrite the one that Flipz altered when he created his rooted stock ROM. It has to be put back to really stock in order for the official incremental update to apply.

I don't know what unrevoked 2 does. If it simply unlocks the NAND and installs su and Superuser Permissions, then yes, this update should work fine, assuming you were starting from a stock ROM when you ran unrevoked.
[EVO 4G Android Development] joeykrim:
since i am being referenced, "this man", let me clarify to account for this different scenario.

if you install the official OTA on top of RUU .6, wont be able to get root access.

if you install the official OTA on top of eng build system (prob have to modify build.prop and load updated version of software files into system which most ROMs do), it will still do everything i mentioned to close root methods, but it will not remove the nand unlock.

since it won't remove nand unlock and the main update.zip file in this thread removes the recovery.img, it will have the following benefits: custom recovery remains, root access (su) on /system remains and nand unlock remains.

the radio.img will update the main version, but since root access persists after using this update.zip method and nand remains unlocked, mtd-eng can be flashed to the misc partition using flash_image to change the main version allowing for eng or userdebug PC36IMG.zip files to be flashed in the future, if ever needed.
[EVO 4G Android Development] wphend00:
Says "read only" when I go to copy the prop file to my system directory. I will try again... but it repeatedly gives me that error...
[EVO 4G Android Development] Knight2011:
are the commands diffrent for mac?
[EVO 4G Android Development] whitslack:
Did you run adb remount like the instructions tell you to? That remounts the /system file system read/write so you can replace that file.
[EVO 4G Android Development] whitslack:
I wouldn't think so. I'm using Linux, which is more similar to Mac than either is to Windows. Should be the same on all three platforms, though.
[EVO 4G Android Development] wphend00:
OK, I get a Status 7 error as well...

I did "50-step-root" route (lol), and am running a custom ROM AospEvoSense....

I guess since I am rooted, I cannot apply this update, correct?

I guess I could do a nand backup and then flash to a stock rom, but I don't really know how to un-root.
[EVO 4G Android Development] Knight2011:
Just checked you have to add ./ in front of adb

thanks
[EVO 4G Android Development] rugedraw:
Wait a minute.....I think his problem may be the same as mine. In order to write to /system, you need to have NAND unlocked, right? I have the correct rooted rom, but I didn't do the NAND unlock and I am getting the same error message as Knight2011 and a few other people.

Thanks again.....you've been very helpful with your quick responses and it is much appreciated.
[EVO 4G Android Development] whitslack:
Glad you got it sorted. The ./ prefix is only if you have the adb binary in the current directory and not installed in a system-wide location. I have my Android SDK fully installed, so adb is in the shell's search path.
[EVO 4G Android Development] whitslack:
No, it's not because you're rooted. It's because you're running a custom ROM. This incremental update will only apply to the stock (rooted) ROM.

Yes, you do need to be fully rooted in order to write to /system. I'll add a note to the OP.
[EVO 4G Android Development] wphend00:
so run the updates on a stock rom, but the question begs to be asked, when you install a custom rom, will this get rid of the changes (outside of the Wimax and radio update)?
[EVO 4G Android Development] rugedraw:
Ahhhh.....that explains it. I think I'll just wait for someone to write a rooted stock rom with the new updates already worked into it, and just wipe everything and put that in. This is going way beyond my VERY basic knowledge of all of this.

Thank you for putting this up and for taking the time to answer our questions.
[EVO 4G Android Development] acrh2:
The bolded part is a speculation right? They did change the bootloader, didn't they? Couldn't they prevent those debug and eng zips from flashing?

And if so, could those be flashed from custom recovery?

Also, where is the nandroid backup stored?

Sorry, I'm still learning...
[EVO 4G Android Development] hecklbrg:
Can someone put a nub step by step on how to get boot.prop into the system file....

Where do I need to download the file to? etc?

Thanks and sorry, I am still learning.
[EVO 4G Android Development] Knight2011:
NM i got it

thanks
[EVO 4G Android Development] whitslack:
All custom ROMs are "full" ROMs, meaning they wipe out your /system partition and write the entire system from scratch. Therefore, if you install any custom ROM after applying this update, you might as well not have installed this update because it'll be overwritten. (EDIT: However, you are correct about the radio updates. If the custom ROM doesn't include those, you could get them by installing this update first.) If you want to use a custom ROM, you should wait until your ROM developer has integrated the 1.47.651.1 update into her ROM.

As long as they don't start locking NAND from HBOOT, we'll always be able to reflash anything from a custom recovery. The initial trick to rooting these phones (the proverbial foot in the door) is to get a custom recovery installed. From there, flashing system images with su included in them is trivial.

Nandroid stores its backups in a directory called nandroid on your SD card.
[EVO 4G Android Development] Knight2011:
Just to double check the build.prop gets saved as a text file correct?
[EVO 4G Android Development] whitslack:
Yes, it's just a plain text file. The reason we have to deal with this build.prop file at all is because when Flipz made his "rooted stock 1.32.651.6 ROM," he added a line to build.prop to prevent OTA updates from applying successfully. But that's exactly what this update is, so we have to undo the change Flipz made.
[EVO 4G Android Development] Knight2011:
I keep getting that error. I am full root with nand and i still get the error
[EVO 4G Android Development] whitslack:
To help verify that you have the correct build.prop file in your phone's /system directory, run this command from within an adb shell:

ls -l /system/build.prop

It should spit out something like this:

-rw-r--r-- root root 3962 2010-06-30 09:12 build.prop

If you see another number besides 3962 (which is the file size), then you don't have the right build.prop file in place.
[EVO 4G Android Development] drmacinyasha:
Alright, just tried to apply the update. I copied the build.prop to /system, copied over the zip, rebooted into recovery, did a nandroid backup, and then applied the zip.

Here's what I got:

My current ROM is the EVO_1.47.651.1_Rooted.zip by Calkulin with the 2.05.00.06.10 WiMax update and Toast's Part 2 NAND unlock and recovery before that.

I double-checked the build.prop file, and it matches in size, and I checked the MD5 as well, and it matches that of the OP.

Ideas?

(Edit): And yes, I do realize that the version numbers are the same, but Calkulin's update does not contain the Radio update, which is why I'm trying to run this.
[EVO 4G Android Development] whitslack:
There's your problem. This incremental update can only be applied to a rooted stock 1.32.651.6 ROM. If you're already on 1.47.651.1 and have applied the radio updates, then there's no reason for you to apply this update. If you haven't applied the radio updates and want to do so using this update, you'll first have to downgrade to the rooted stock 1.32.651.6 ROM.
[EVO 4G Android Development] acrh2:
http://xdaforums.com/showpost.php?p=6994302&postcount=14
[EVO 4G Android Development] fapstick:
Whitslack.. thanks so much for doing this. All us us noobs appreciate it.

I have a question that I did not see clarified in this thread.

Do I need to apply Toast's step 2 in order to flash this update?

Thanks again!!
[EVO 4G Android Development] whitslack:
Most likely, yes. If you rooted by Toast's step 1 and then installed Flipz's stock rooted ROM, then you won't be able to undo Flipz's alteration of /system/build.prop without having write access to /system, and that means you need NAND unlocked, which means you need to do "Part 2."

If that is beyond your ability or desire, you can flash a full ROM based on the 1.47.651.1 OTA update or wait until HTC releases the actual RUU and someone turns it into an update zip with root added and recovery image removed.
[EVO 4G Android Development] fapstick:
Thank you. I need to do step 2, I was just procrastinating. This gives me an excuse.
[EVO 4G Android Development] Zabalba:
Thanks for your prompt reply whitslack,

Please see attachment 01

Please see attachment 02

This means I'm fully rooted correct? If so, is there anyway for me to get around this error?
[EVO 4G Android Development] whitslack:
It means you have the su binary in the right place. It doesn't necessarily mean you are "fully rooted," since that implies you have NAND unlocked. However, since you do have the correct file size for build.prop, I am given to assume that you do indeed have NAND unlocked.

As far as I know from what you've told me, you're running the stock rooted 1.32.651.6 ROM and have successfully reverted the build.prop file to stock condition, so my update should apply perfectly for you. Something else must be different. What exactly is the error you're getting?
[EVO 4G Android Development] MadhouseMedic:
I need help unlocking NAND on OS X. Unless someone else can find an easier way to replace my build.prop file.
[EVO 4G Android Development] whitslack:
You might be able to do it using adb while the phone is in the recovery program. I think the NAND is not locked while in recovery, even if you haven't gone through the "NAND unlocking" procedure. It will depend on what recovery image you have installed. (The recovery would need to support adb in order for you to adb push the stock build.prop onto the phone.)
[EVO 4G Android Development] drmacinyasha:
Downgraded, still have root. Applied update after re-copying build.prop, and now when I try to adb shell, I get this:

Am I missing something here?
[EVO 4G Android Development] telugite:
Is this update based on the old OTA or Latest OTA released today.
[EVO 4G Android Development] whitslack:
You must be missing something. Here's what I get:

$ adb shell
$ su
#

Did you have the phone's screen turned on when you executed the su command? You have to tap the "Allow" button on the phone when the Superuser Permissions app asks.

If you don't have Superuser Permissions installed, that could be your problem. Try installing the su-2.1-e-unsecure-signed.zip update from this thread.
[EVO 4G Android Development] whitslack:
It's based on the OTA update with file size 31691906 and MD5 hash d7ad11265e47d48b08b3c1bf1855761f. I think that is the later one. I downloaded it (using the HTC Update utility on the phone) this morning.
[EVO 4G Android Development] hecklbrg:
Does anyone have a link to a tutorial to set up Android SDK so that I can open a shell to push the correct file in the /system folder?

Thanks
[EVO 4G Android Development] kpoz:
whitslack:

I have a question for you. In Post #20, you says the following:

"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."

I am using Joeykrim's odex 1.0.8 ROM (stock, but rooted) with the kitchen on top. Would I be able to install this rooted update, or would I have to somehow revert to to rooted update without the kitchen? Please note that I only used the kitchen to remove a few apps.

If I have a few nandroid backups in place, will I be able to revert if everything didn't properly install? Will I be able to install Joeykrim's kitchen on top of the new rooted update?

Thanks in advance. Hopefully, this will help the community as a whole.

Edit: Also, I have ROM Manager Premium installed with clockworkmod's custom recovery. You mentioned something about the recovery program caring that the update signed by someone other than HTC. Will clockworkmod's recovery allow me to flash this update without using shell/adb or whatever it's called?
[EVO 4G Android Development] Rhys'Droid:
First post (stickie) in the development forum:

http://xdaforums.com/showthread.php?t=694250

Specific wiki for ADB:

http://xdaforums.com/showthread.php?t=694250