yashsingh1/xdaforums huggingface dataset:
[EVO 4G Android Development] Freelancerx:
Ok I have a question.... I did the archived method. Is there any difference between this new method and the archived method. Basically what i want to know is if what I have running now on my phone would be the exact same thing if I used that new ruu that you on the front page white?
[EVO 4G Android Development] notmike:
What is the likelihood that this process will be streamlined and consolidated into a nice little package some time soon. I've refrained from installing the ota on my wife and I's phones, but I've had a hard enough time just keeping up with the latest possibilities, let alone committing to trying to completely root and flash these phones using all those steps, or worse yet troubleshoot any hiccups. But I'd really like to have the battery and WiFi enhancements in the latest ota, what to do what to do
[EVO 4G Android Development] whitslack:
Firstly, this is not my ROM. It's straight from HTC, no modifications whatsoever.

The reason some ROMs take you straight into a root shell when you run adb shell is that the ROM author unpacked the boot image and changed the value of the ro.secure system property, then repacked it. I prefer to stay as close to stock as possible so that the incremental upgrade path remains reliable in the future, so I do not alter the boot image in any way.
[EVO 4G Android Development] Land Master:
No final difference at all. Just fewer steps.
[EVO 4G Android Development] whitslack:
If HTC has a thorough quality control team, there is no difference. What you have is the initial release that has been updated incrementally, just as phones that were upgraded over-the-air. What is being offered now is more like the brand new phones that are being loaded at the factory with the latest version of the system. There is most likely no discernible difference. I wouldn't bother flashing the new image; there's no reason to do so.

EDIT: Ah ha! This time Land Master beat me! :P
[EVO 4G Android Development] Land Master:
I have waited and watched this for three days. This is currently (in my opinion) the cleanest way for people to keep root have NAND unlocked and upgrade to the latest software.

Now...With that said...while this procedure is VERY simple, you will need to perform Toast's steps (1 and 2) as outlined. These steps allow you to unlock nand, update to the Engineering HBOOT and thereby make the procedure in this thread go smooth.

I personally researched ALL of the steps in Toasts procedure between here and other websites before I dove in. Some sites have screen shots others don't. By reviewing all the available information out there I was able to get my head around it before I started. I also reviewed issues others had written about and was "ready" for them if they came up. In my case they never did. I believe this was because of my preparation.

Research, Take your time, and be prepared.

Good Luck!
[EVO 4G Android Development] Freelancerx:
Thank you for the reply
[EVO 4G Android Development] whitslack:
This is already pretty consolidated and streamlined. With all of HTC's efforts to prevent us from having full control of the devices we bought, it's never going to be simple to break through all of their barriers.

Here's the basic idea, starting with a brand new phone:

Attain root privileges on the device. This can be done either by the original unrEVOked method or by Toast's Part 1.

Overwrite the nv ("misc") partition with one bearing an older MainVer. This is necessary so that the stock HBOOT doesn't refuse to downgrade.

Install the engineering HBOOT. Since you'd be starting from the release HBOOT, the only way to accomplish this is to flash a full RUU signed by HTC. This is what Toast's Part 2 does.

Install a custom recovery and stock system 1.47.651.1 image. This is what the first half of this thread does.

Install the superuser package (so you have root access while booted). This is what the second half of this thread does.

EDIT: The problem with the new phones that are coming out now is that step #1 is impossible. UnrEVOked doesn't work on the new phones (because they're running 1.47), and the release HBOOT won't downgrade to the userdebug RUU from Toast's Part 1 because it has a lower MainVer.
[EVO 4G Android Development] Land Master:
You know even though its been said in this thread before... its worth repeating.

The original method which is now "greyed-out" provides ALL the HTC/Sprint files from initial release (launch day) forward to after the most recent OTA.

By maintaining NAND unlock (Engineering HBOOT) you could actually revert your phone to an out of the box condition OR the condition after the first OTA (released on day 1) OR to the current OTA conditions. This is what is special about the work and files that Whitslack has provided.

Very NICE!!
[EVO 4G Android Development] Berner:
whitslack, you have a talent for simplifying complex concepts. Your original steps in this thread were so simple and direct that they were, well, obvious in hindsight -- and yet no one had compiled them in the way you did.

Similarly, the explanation above is also an elegant summary of the current rooting situation. I recommend that you include it in the original post.
[EVO 4G Android Development] bdorr1105:
Incredible Work Guys

This was about the easiest rooting process I have ever seen and I would like to say thanks for all the effort

Question on the side, i helped my buddy root his wifes phone, however I wanted to smack him upside the head cause he did the 1.47.651.1 update via OTA without Full Root previously done? Is there a way to unrevoke root or do anything to make it possible to fully root that phone, It looks like it is impossible at this point..Thanks
[EVO 4G Android Development] gerald410:
Thx for the info.
[EVO 4G Android Development] xcopmanx2:
Okay, so I went through the whole process but I noticed then I still have the 04.26 radio and possibly old wimax? What is the safe way to update those two and should I still have those as old versions? I see that I have the updated kernel and firmware version.
[EVO 4G Android Development] sanjsrik:
Awesome, worked like a charm. What wouldn't update before, worked without ANY issues. The only advice I'd give people is backup your applications first. The only application I had to download was Titanium backup and because the license key was still on my /sdcard, it automatically unlocked to pro version. I updated with the second zip file and everything was unlocked with root.

I used titanium backup to restore all my applications and data from the sdcard.

Absolutely awesome.
[EVO 4G Android Development] Land Master:
Sorry to be blunt but if you went through this procedure there is no way for you to have ANY "older" stuff.

You must have missed something. Probably some of the initial unlocking (Toast) stuff.

Start by reviewing your current HBOOT version (outlined herein) and take it from there.

While most us us have praised this method for its cleanliness and simplicity, it is only meant for those that have previously (or already) rooted and unlocked their phone using methods that were devised for the pre-OTA software.
[EVO 4G Android Development] jrmithdobbs:
Hey whitslack will this pc36img.zip flash from inside of fastboot RUU mode so that the whole thing could be scripted? Or does RUU always insist upon checking the zip signature no matter the hboot version?
[EVO 4G Android Development] xcopmanx2:
Hmm, that's odd. I will have to do it again. I redid the whole process today starting with toast's initial root, then did NAND, checked the version to be the .2000 and went from there following the procedure.
[EVO 4G Android Development] Land Master:
Hmmm is right.

Those are the right steps and you do have the proper HBOOT which is good. Try again and let us know. Did you check the md5 sums on your downloaded files? Md5 checker software is available for free (Google search) and before you go too far I would recommend this additional but not mandatory step.
[EVO 4G Android Development] sanjsrik:
I can attest this works. I have 4G working, 4Mb down, and only 250k up, but wow, never had 4G working so consistently before.

This method has me totally rooted AND with the latest radio, etc.
[EVO 4G Android Development] chandlerw88:
yeah i give up. i appreciate it but i think im just screwed. cant blame a noob for trying but its not lettin me, thanks though for the help
[EVO 4G Android Development] jwwolfe77:
Hmmmm.... I downloaded the PC36IMG and renamed it as such but when i go into hboot it doesnt recognize it...... Anybody know why? Maybe ill try to redownload it and try again.
[EVO 4G Android Development] Reanimatedshad0w:
I noticed that I named it zip.zip and thats why it didn't show up.
[EVO 4G Android Development] jwwolfe77:
Yep. Redownloaded, renamed, and put it on the root of my sd card and HBOOT still wont recognize it. Any suggestions?
[EVO 4G Android Development] Reanimatedshad0w:
I know this might be a bit out there but why don't we ever have to wipe ect? Even though this isn't a rom, thats just something they beat into your head after a while if you read it long enough
[EVO 4G Android Development] jwwolfe77:
LOL im such a ratard. I figured it out. When i renamed it i put PC36IMG.zip instead of PC36IMG. It automatically puts the .zip at the end. DUH!!!!!!:o
[EVO 4G Android Development] Land Master:
In essence you ARE wiping. This procedure installs a 100% fresh image as noted by the need to rerun setup upon first boot.
[EVO 4G Android Development] itsthen:
Hi guys.... New here.

I just rooted my phone using this method. Nice and simple. Thanks so much for the hard work. But I did have a couple quick questions.

I plan to flash to Fresh 0.5.3... When I want to go back to this fully rooted stock rom, is there an easier way to do so then having to load these two files onto the sd card, renaming the file, etc?

Is there a way to back this rom up so I may flash it from the phone directly?

How about alternating between custom roms?

I know this has been covered many times, but I have'nt found a direct answer.

Any insight is appreciated.
[EVO 4G Android Development] Land Master:
Glad you got it sorted. Everything should be good to go!
[EVO 4G Android Development] jwwolfe77:
While its going thru the PC36IMG process, on the recovery part it says failed-pu. Is that ok?
[EVO 4G Android Development] jwwolfe77:
I guess its not ok cause after it finished it said update fail. Im useing clockwork recovery. Am i supposed to be using something else?
[EVO 4G Android Development] davidlightle:
For someone that has done this, what is the resulting PRI?
[EVO 4G Android Development] Reanimatedshad0w:
Honestly went through perfectly with me. Downloaded it and dragged and dropped it into the sd card :(
[EVO 4G Android Development] Land Master:
Well..to use 100% correct terminology this procedure did not "root" your phone. The mandatory initial steps (Toast ETC.) did that.

Fresh 0.5.3 is still based upon the pre-ota system code and may NOT give you desired results. It has been recommended that you stick with ROM's based upon the 1.47 code although I am standing pat for the time being.

Easier way? Doesn't get any easier than this.

Flash away til' your hearts content. Just don't do ANYTHING to allow the Engineering HBOOT to get replaced.

Not sure if the recovery image installed pursuant to this procedure allows for nandroid back-ups but that is the best method for "backing up"
[EVO 4G Android Development] Reanimatedshad0w:
He could just flash the latest here and try out fresh right? If things get shaky just flash back?
[EVO 4G Android Development] Land Master:
This procedure doesn't mention clockwork at all. If followed it installs a version of RA. Don't know what you are trying to do.
[EVO 4G Android Development] Reanimatedshad0w:
damm I just upgraded mine. I was under the assumption its the oldest one. My semi constant 4g signal usually got a bar before I upgraded the PRI. So I assuming it was an older one since an upgrade did happen. My results may be different from yours though, I barely had any signal when I got my phone and I also live in ny where its not offically outl
[EVO 4G Android Development] ewells38:
Thanks, followed the steps to the letter, and worked smoothly. Updated while retaining ROOT & NAND access with WiMax. So thanks again. :D

Quick question, i'm in philly (which has 4G), but I get a (good to excellent) connection, then after abt 2 minutes it goes back to "scanning", then a few minutes afterwards it connects again, then the cycle repeats. Does not retain a connection to 4G

Anyone has any ideas??? :confused::confused::confused:

Anyone ?????
[EVO 4G Android Development] Land Master:
Sure. He can try anything as long as that HBOOT (engineering version) doesn't get replaced. If for some reason access to the SD card gets borked and the proper files can't be placed there, that may cause issues. This would require additional steps such as perhaps adb and/or fastboot, but that is another topic.
[EVO 4G Android Development] davidlightle:
Sorry, I was vague before. I haven't done this method, but I did whitslack's previous root-safe path to get the 1.47 OTA while remaining rooted. I still have 4g keys, but I'm not in a 4g area to know whether mine works or connect-loops. Anyway, that's a different subject. The real reason I ask is because Toast Part 2 (NAND unlock) downgrades the PRI to 1.34_003 [which I currently have] but it is rumored that the PRI is connected to the nv.img which this method uses 100% from the OTA. In that case, using this should have the most up-to-date PRI even after NAND-unlocking. I'm just trying to verify if that's the case, or if PRI is still downgraded. If it's still downgraded, the PRI may be connected with HBOOT which would be unfortunate.
[EVO 4G Android Development] Land Master:
Mine is at 1.34_003 also after following this procedure. Are you saying that the users who accepted the OTA have a different version?
[EVO 4G Android Development] jwwolfe77:
Yeah... I forgot to put on my f'ing thinking hat today. The istructions clearly say useing toasts part 2 root method and i was useing clockwork. Now i AM updated, but i dont have root or recovery and im srewed. Son of a beeeeyaaaatch!!!!!
[EVO 4G Android Development] Knight2011:
I got this to go flawlessly.Question:Can the recovery be switched back to clockwork?
[EVO 4G Android Development] davidlightle:
I'm not sure about those who used the OTA -- but now I'm suspecting this depends on whether they did the OTA with or without doing NAND-unlock previously.

Basically, I believe the PRI on the phone was originally 1.40_003; NAND-unlock took it to 1.34_003. It's been discussed in this thread (a little dormant right now as it's a smaller focus at the moment) that this is tied to the nv.img (which I hear is [part of?] the misc partition).
[EVO 4G Android Development] Land Master:
Hmm. When you say "originally" do you mean out of the box?

My 4G sucks, always has from day 1 (pre-root). I think I have a hardware issue (and I certainly don't want to swap it out now), but this PRI thing is interesting.
[EVO 4G Android Development] Land Master:
Sure. Download ROM Manager and install. Flash new recovery from top menu item.

If the currently installed RA has nandroid backup (haven't rebooted to check) than I personally am sticking with it for cleanliness.
[EVO 4G Android Development] Land Master:
Wow...that sucks!!
[EVO 4G Android Development] davidlightle:
Yeah, out-of-the-box, mine was 1.40_003 and from what I've read, others confirm that as well.

Just keep in mind PRI is not the same as PRL, and I don't know fully what PRI affects. At some point, it will be nice to find a way to upgrade the PRI, though.
[EVO 4G Android Development] itsthen:
ok thank you.
[EVO 4G Android Development] Land Master:
Thanks for the info...Yeah PRI, PRL, whatever, its all greek to me. Could be a concern for those taking their phones back as it would be simple for the tech's to see this information and subsequently determine something was "tweaked". I'm going to hunt down that other thread.
[EVO 4G Android Development] whitslack:
I don't believe you can flash the whole thing at once using fastboot, but you can flash each image contained in the PC36IMG.zip individually using fastboot, one after another. There might be a particular order you have to do them in, so I would follow the same order as HBOOT uses.
[EVO 4G Android Development] whitslack:
NAND flash memory always has to be erased before being written, so erasure is built into the flash procedure. These .img files are "full" images, meaning they cover the entire partition to which they are written, so you're rewriting every page of the partitions. You can separately erase them first, but there's no point in doing so. A notable exception to the above *might* be the WiMAX image. If you erase that whole partition, I think you'll have the MAC address problem.
[EVO 4G Android Development] rmk1825:
This worked flawlessly!

This by far is the most reliable and simplistic process.

Whitslack, thanks for instructions and the breakdown and what's being done.

I have the 1.47.651.1 with 4G in Dallas, TX.
[EVO 4G Android Development] Knight2011:
I used the simple 3 click method witch had clockwork and it went without a problem.
[EVO 4G Android Development] whitslack:
It's already pretty damn easy, but yes, you can make a Nandroid backup after following this method and restore it whenever you want. You can also leave the PC36IMG.zip file on your SD card if you rename it to something else so HBOOT doesn't see it.
[EVO 4G Android Development] engagedtosmile:
So I did the steps. Setup my device. I get a pop up instantly that says there is a system update.

Do I apply this or what?
[EVO 4G Android Development] rmk1825:
One question...

whitslack or anyone else. I followed all instructions and everything worked just fine. I have the superuser app installed.

When I connect my phone to the computer. I see "USB Debugging" which is a good sign.

* When I go into ADS Shell. I am seeing a "$" as opposed to the "#".

* When I type "su", I get prompted on the phone to grant SuperUser privaleges and I grant them.

* I then see the "#" sign which means I am root...correct?

* In the adb shell, I can successfully do a "cd system" to get to the system directory.

* I then tried to do a simple, "mkdir test" to see if I can make a test directory.

I get "mkdir failed for test, Read-only file system"

Is this what is expected? Should I even be able to make a directory called test under system?
[EVO 4G Android Development] whitslack:
Never apply OTA updates!

That being said, you shouldn't be seeing an available update if you've succeeded with the steps in this thread. The fact that you are means you didn't upgrade successfully. Which PC36IMG.zip file did you apply? The 1.47 one or the 1.32 one?
[EVO 4G Android Development] engagedtosmile:
Oh I didnt see theres a new PC36IMG, I'll download the new one and do that.
[EVO 4G Android Development] whitslack:
That all sounds good. To make changes to /system, you have to remount it read/write.

After switching to a root shell (# prompt), type mount and press Enter.

Look for a line that includes the word /system. On that line, look at the part that says /dev/block/mtdblockN, where N is a digit. That is the partition that your system lives on.

Type "mount -o remount,rw -t yaffs2 /dev/block/mtdblockN /system", substituting the digit you saw in the previous step for N.

Now your system is mounted read/write and you can make changes. Proceed cautiously. :-)
[EVO 4G Android Development] rmk1825:
That's it!!! Thanks again.

I'm not going to make any changes. I am just asking for more knowledge purposes! Your knowledge and work is awesome!!
[EVO 4G Android Development] whitslack:
Alternately, you can proceed with the original steps. It's just two more update zips to flash from recovery. Either way ends you up in the same place.
[EVO 4G Android Development] 2kmy477:
IF i installed the ota update,can i still use this method to root or am i pretty much hosed for now?
[EVO 4G Android Development] whitslack:
Depends on whether you have the engineering HBOOT. If you do, you're not hosed at all. If you don't, then yes, you're hosed.
[EVO 4G Android Development] 2kmy477:
I don't,i have the 0.79 version,it sucks.Anyway,thanks for the info.
[EVO 4G Android Development] canteenboy:
What is everyone's PRI version after this update. I'm still on 1.34_003

Any idea how we can update it or is it even necessary?
[EVO 4G Android Development] rmk1825:
Same here!
[EVO 4G Android Development] PikkonX:
Same here.
[EVO 4G Android Development] phazen18:
Worked awesome for me, thanks!!!
[EVO 4G Android Development] ebuechler3:
for some reason, i cant flash any roms..... i keep getting : E: wrong digest: system/app/Browser.apk E: Verification failed Installation aborted....... i performed all the steps to a t.... what should i do
[EVO 4G Android Development] whitslack:
If you're getting that error, you were following some other procedure, and not the one in this thread.
[EVO 4G Android Development] sdc177:
All seems to be well so far after doing this except for adb.

When I try "adb shell" it returns a $ instead of a # like it used to and my permissions are limited. Is there another command I'm supposed to issue to get into a full shell or what do I need to do?

I remember someone else had this issue and I think they just had to use a different command but I can't find that post!
[EVO 4G Android Development] ebuechler3:
i get that error while in recovery.... i think i accidently wiped my sd partition or something... i dont know... but i think everything else looks right except i keep getting that error when trying to flash roms
[EVO 4G Android Development] whitslack:
Yep, that's the purpose of the su (switch user) command. Before you enter it, be sure your phone's screen is on and unlocked, as you'll have to answer "Allow" on the dialog box that comes up.
[EVO 4G Android Development] whitslack:
This thread is not about flashing custom ROMs.
[EVO 4G Android Development] ebuechler3:
im very sorry.... i misunderstood... i never would have flashed this update on my phone right now if i knew i was gonna lose the ability to flash custom roms.... i mean thats the one of my only reasons for unrooting my phone..... So im stuck... With this method, can i or can't i flash custom roms?.... thankyou
[EVO 4G Android Development] whitslack:
Oh, no, you can still flash anything you want, assuming you have the engineering HBOOT, which you would have if you successfully followed the instructions in this thread. I'm just saying, this is not the thread in which to be asking for help with flashing a custom ROM.
[EVO 4G Android Development] Land Master:
This procedure is fine for still allowing you to flash custom ROM's. You are doing something else wrong. Check in the ROM section of the ROM you are trying to flash.

Again, this procedure does NOT hinder your ability to flash custom ROM's in any way, shape or fashion.

Good Luck.
[EVO 4G Android Development] ewells38:
This is what I did and it worked pretty well

at the $ prompt, type su and press enter, you should then have the # prompt
[EVO 4G Android Development] ebuechler3:
cool, im in the process or reformatting my sd card... ur instructions were perfect, and i have ur hboot.... i made an error along the way... hopefully i/we can fix it.. thanks again
[EVO 4G Android Development] ewells38:
Anyone have any ideas on what I could try to correct this? anyone else experiencing the same thing??
[EVO 4G Android Development] afxtwn:
Ok I dont think im doing something right, I load the pc36img and it does the blue bar but then it just says checking pc36img and goes back to the main menu.
[EVO 4G Android Development] whitslack:
My guess is you're running the release HBOOT. What version of HBOOT does it say at the top of the white screen?
[EVO 4G Android Development] afxtwn:
It says

0.79.0000
[EVO 4G Android Development] Reanimatedshad0w:
Edit:nvm

woops
[EVO 4G Android Development] sdc177:
Will try that when I get back to my pc. I didn't have to do that before. Thanks!
[EVO 4G Android Development] whitslack:
My guess was correct. You need to get the engineering HBOOT loaded on there. Follow Toast's Part 2.