Develop Bugs

Froyo Root - Pending?

Hey all, just wondering if anyone has tried to see if they can root the OTA to Froyo. Not that I need it, but I figure there is bound to be people who do in the coming days (both from their own stupidity, and some from being absolutely new after the update). The PRI doesn't change, so I'm guessing that's got to be at least some good news. I have no idea what it might take to root it, or even what measures were included in the OTA to prevent rooting. Just wondering if anyone is working on it.
Also, does anyone know how we can change our PRI's? I used the Froyo flash without root and still have the old pre-1.40 PRI. Also, does the PRI have anything to do with the market not showing copy protected apps? If it does, then I may actually need root again... LOL. Anyways, just hoping someone is looking in to finding a new root method and perhaps figuring out PRI/market issues.

superlinkx said:
Hey all, just wondering if anyone has tried to see if they can root the OTA to Froyo. Not that I need it, but I figure there is bound to be people who do in the coming days (both from their own stupidity, and some from being absolutely new after the update). The PRI doesn't change, so I'm guessing that's got to be at least some good news. I have no idea what it might take to root it, or even what measures were included in the OTA to prevent rooting. Just wondering if anyone is working on it.
Also, does anyone know how we can change our PRI's? I used the Froyo flash without root and still have the old pre-1.40 PRI. Also, does the PRI have anything to do with the market not showing copy protected apps? If it does, then I may actually need root again... LOL. Anyways, just hoping someone is looking in to finding a new root method and perhaps figuring out PRI/market issues.
Click to expand...
Click to collapse
The OTA is rooted. Search the forums. PRI is tied to the ENG HBOOT, so you are stuck with 1.34 if you want to keep root.

superlinkx said:
Hey all, just wondering if anyone has tried to see if they can root the OTA to Froyo. Not that I need it, but I figure there is bound to be people who do in the coming days (both from their own stupidity, and some from being absolutely new after the update). The PRI doesn't change, so I'm guessing that's got to be at least some good news. I have no idea what it might take to root it, or even what measures were included in the OTA to prevent rooting. Just wondering if anyone is working on it.
Also, does anyone know how we can change our PRI's? I used the Froyo flash without root and still have the old pre-1.40 PRI. Also, does the PRI have anything to do with the market not showing copy protected apps? If it does, then I may actually need root again... LOL. Anyways, just hoping someone is looking in to finding a new root method and perhaps figuring out PRI/market issues.
Click to expand...
Click to collapse
Wow just wow
sent with my evo from a secret place

SteelH said:
The OTA is rooted. Search the forums. PRI is tied to the ENG HBOOT, so you are stuck with 1.34 if you want to keep root.
Click to expand...
Click to collapse
I think he is talking about a root method for those running the stock OTA.

SteelH said:
The OTA is rooted. Search the forums. PRI is tied to the ENG HBOOT, so you are stuck with 1.34 if you want to keep root.
Click to expand...
Click to collapse
If we don't want to keep root is there a way to change the pri back?
Sent from my PC36100 using XDA App

TheBiles said:
I think he is talking about a root method for those running the stock OTA.
Click to expand...
Click to collapse
Ditto thats what I think hes referring to as well. Hopefully the method doesn't include downgrading like before and then losing the PRI, but if it does we can get a way of extracting it this time.

dylan6879 said:
If we don't want to keep root is there a way to change the pri back?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
If you don't want root, v1.47 OTA has PRI 1.40 in it's HBOOT, same as Froyo release floating around.
sgt. slaughter said:
Ditto thats what I think hes referring to as well. Hopefully the method doesn't include downgrading like before and then losing the PRI, but if it does we can get a way of extracting it this time.
Click to expand...
Click to collapse
As far as the OTA being rooted, no it's is not.If you upgrade OTA you will NOT have root. The rooted froyo roms in the forums all use THE SAME ENG HBOOT, which means you will be stuck with PRI 1.34

SteelH said:
If you don't want root, v1.47 OTA has PRI 1.40 in it's HBOOT, same as Froyo release floating around.
Click to expand...
Click to collapse
My problem is that I already flashed the "unofficial" Froyo update that I got directly from HTC. It didn't update the PRI, and I don't think I can flash a downgraded ROM. I guess I can try, but most likely I'd have to use the RUU and the 1.47 RUU never works for me.

SteelH said:
If you don't want root, v1.47 OTA has PRI 1.40 in it's HBOOT, same as Froyo release floating around.
Click to expand...
Click to collapse
What is this PRI and what are the differences in the versions?

I'm already rooted but would like to go back to full stock so there is no way for me to get my pri back to 140 because others are saying when you unroot it stays at 134
Sent from my PC36100 using XDA App

dylan6879 said:
I'm already rooted but would like to go back to full stock so there is no way for me to get my pri back to 140 because others are saying when you unroot it stays at 134
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Yeah...even going back to stock you will still have 1.34, unfortunately. You can hex edit it to say 1.40 but that is cosmetic only.
Sent from my PC36100 using Tapatalk

If the Froyo update really did wipe HBOOT, why didn't the PRI change? Maybe it didn't actually do anything to the HBOOT? If that's the case, maybe those who had full root can still gain root through the bootloader. Anyways, someone really needs to find a way to get our PRI upgraded. Its sad that even switching to stock won't fix it.

I have Pri 1.40.003 and have root and nand unlocked

Ok this is how i got the current pri. I used whitslack idea but used the latest ruu zip files that were extracted from the 2.2 froyo update and replaced the recovery and eng-bootloader updated my phone by putting it on my sd card. Once that was done and booted back up granted i did not have su cause i don't know where to find the most current version. I then turned phone off booted into recovery and flashed dc 3.5. I then rebooted and then installed root explorer and deleted stuff i do not use. I then dialed ##786# did factory reset u must have msl code. Once it booted into recovery and wiped data/cache i also deleted dalvik-cache and then rebooted phone it did hands free activation and updated prl and then it checked for firmware update. And once i went to about phone and software information i saw i had pri 1.40.003. I do not know if this will work for you but i did for me.
*EDIT* If someone does try this could u check after the update using the PC36IMG and see if just that updates the pri. Thank you
Ok i will provide links to the files i used but if u lose root or brick your phone i not responsible.
Thank you to dc dev team for a great rom and whitslack for the idea on the PC36IMG idea. And xda for a great forum
Here is the link to dc thread. http://forum.xda-developers.com/showthread.php?t=745659
Here is the link to the PC36IMG i used http://www.megaupload.com/?d=YVHC5NY2
and finally here is a video of it for proof http://www.youtube.com/watch?v=CWLwP4XsPrk

Punctuation was invented for a reason. *head explodes*

mjohnson4580 said:
Ok this is how i got the current pri used whitslack idea but used the latest ruu zip files that were extracted from the 2.2 froyo update and replaced the recovery and eng-bootloader updated my phone by putting it on my sd card once that was done and booted back up granted i did not have su cause i dont know where to find the most current version i then turned phone off booted into recovery and flashed dc 3.5 rebooted then installed root explorer and deleted stuff i do not use then dialed ##786# did factory reset u must have msl code. once it booted into recovery and wiped data/cache i also deleted dalvik cache rebooted phone it did hands free activation and updated prl and checked firmware. once i went to about phone and software information i saw i had pri 1.40.003. i do not know if this will work for you but i did for me
Ok i will provide links to the files i used but if u lose root or brick your phone i not responsible.
Thank you to dc dev team for a great rom and whitslack for the idea on the PC36IMG idea. And xda for a great forum
Here is the link to dc thread. http://forum.xda-developers.com/showthread.php?t=745659
Here is the link to the PC36IMG i used http://www.megaupload.com/?d=YVHC5NY2
and finally here is a video of it for proof http://www.youtube.com/watch?v=CWLwP4XsPrk
Click to expand...
Click to collapse
and you had pri 1.34 prior to doing this?

Yes i had 1.34.003 pri before this

so let me get this straight, im currently rooted and full nand unlocked, and i have pri 1.34. All i gotta do is flash the linked PC36IMG.zip, Lose root. And ill still retain engineering Recovery? that way when i get into the "somewhat" official rom, i can do all teh necessary programing and updating, so that i can flash back to DC Rom, and get my PRI to be the latest?
i need clarification.

Thats the way I am understanding this. I'm very tempted to try it, if nothing else to just to help the cause.

i wouldn't do it.
I just don't see how it works.
He never said he still had nand after updating.

He only has 10 posts he might just be trying to make us delete everything on our phones. But I am going to try it anyway and hopefully not loose root permanently. I will post back with my findings.
Upon inspecting his file it looks like he has nand unlocked unless he is trying to screw with everyone and renaming files to throw us off well here is the moment of truth i'm gonna flash it.

I would be good to get toast's input on this thread.

l33tlinuxh4x0r said:
He only has 10 posts he might just be trying to make us delete everything on our phones. But I am going to try it anyway and hopefully not loose root permanently. I will post back with my findings.
Upon inspecting his file it looks like he has nand unlocked unless he is trying to screw with everyone and renaming files to throw us off well here is the moment of truth i'm gonna flash it.
Click to expand...
Click to collapse
i'm staying on this thread and refreshing to see status

l33tlinuxh4x0r said:
He only has 10 posts he might just be trying to make us delete everything on our phones. But I am going to try it anyway and hopefully not loose root permanently. I will post back with my findings.
Upon inspecting his file it looks like he has nand unlocked unless he is trying to screw with everyone and renaming files to throw us off well here is the moment of truth i'm gonna flash it.
Click to expand...
Click to collapse
Let me know bro, I have been following your post all day and was just getting ready to flash when I saw your post lol. I'll be refreshing this page every 5 mins lol.

I went ahead and took the plunge, so far everything looks legit. I'm currently doing the hands free activation atm

ranmasaotome510 said:
i'm staying on this thread and refreshing to see status
Click to expand...
Click to collapse
L33t is trying it again as we speak, first attempt was a no go, but he said he missed a step or two, so we are still waiting for his results

Subscribed. If this works I'll ****.
Thanks.

I thought that the rcdata.img was not on any of the ota roms. Hmmm

pongoface said:
I thought that the rcdata.img was not on any of the ota roms. Hmmm
Click to expand...
Click to collapse
it must be...people are claiming that from 1.32 to the OTA 1.47 their pri goes up to 1.40 (unless they are lying )

kinda quiet now. Hope all is well with the 2 guinea pigs. Crosses fingers.

It won't work unless he has the extracted "rcdata.img" from a stock phone that hasn't flashed the "rcdata.img" from the eng-PC36IMG. We wouldn't need to flash the whole PC36IMG, just the rcdata.img. If your bootloader is unlocked you can create a PC36IMG zip with only the rcdata.img and it will flash only that and leave all else in place. If you notice, while you flash the rcdata.img it says...custom radio listed as the partition being flashed....I've flashed the PC36IMG in many different forms and the 1.40 PRI is no where in any of what's on this Forum. As others have said...we need the extracted rcdata.img from a non-flashed, eng-rcdata.img phone....

adeyo said:
it must be...people are claiming that from 1.32 to the OTA 1.47 their pri goes up to 1.40 (unless they are lying )
Click to expand...
Click to collapse
But isn't whitslacks method based off the stock 1.47 rom in which he replaced the hboot and recovery just like here. You would assume that the pri would be updated using that method.

there is no rcdata.img in his pc36img.zip so it doesn't look like he extracted it and it does not look like he put in the faked one either so this might actually be legit if it works still waiting for my phone to boot up.

HELP!!: OTA (1.47) wanting to install upon boot!!

ok, i thought the 1.47 OTA would download to my sdcard...it didn't. But i wasn't quite convinced it was on the device so i clicked "install update" w/ the sd card pulled...as soon as it began i pulled the battery. Now, whenever i boot it automatically goes straight to the black update screen (with the hard drive icon) trying to install the OTA !!!
How can i stop this and boot normally back into 1.32??? w/o forcing the 1.47 update!!
(i am unrooted btw) THANKS FOR ANY TIPS!!

adeyo said:
ok, i thought the 1.47 OTA would download to my sdcard...it didn't. But i wasn't quite convinced it was on the device so i clicked "install update" w/ the sd card pulled...as soon as it began i pulled the battery. Now, whenever i boot it automatically goes straight to the black update screen (with the hard drive icon) trying to install the OTA !!!
How can i stop this and boot normally back into 1.32??? w/o forcing the 1.47 update!!
(i am unrooted btw) THANKS FOR ANY TIPS!!
Click to expand...
Click to collapse
I could be wrong but i dont think there is a way to stop it if unrooted. in good news even if you let it update to 1.47 you can still root (just dont go to 2.2) so not sure why you would want to stay at 1.32

omegasun18 said:
I could be wrong but i dont think there is a way to stop it if unrooted. in good news even if you let it update to 1.47 you can still root (just dont go to 2.2) so not sure why you would want to stay at 1.32
Click to expand...
Click to collapse
thanks. i hadn't backed up everything yet. also, i had unrevoked so i hope this doesn't drop my pri down to 1.32 from 1.40 (i guess i lose free tethering too)...other than those things, i was just about to root and get froyo!
so, you don't think i can boot into recovery and wipe something before it completely installs upon reboot??

adeyo said:
thanks. i hadn't backed up everything yet. also, i had unrevoked so i hope this doesn't drop my pri down to 1.32 from 1.40 (i guess i lose free tethering too)...other than those things, i was just about to root and get froyo!
so, you don't think i can boot into recovery and wipe something before it completely installs upon reboot??
Click to expand...
Click to collapse
Not without root. Whatever is trying to run is almost certainly on /system, which is not writable without root access. Just let it go and root after that.
Also, NEVER PULL THE BATTERY WHILE THE SYSTEM IS FLASHING! That's a real good way to end up with a half-written (bricked) ROM.

Just let it update to 1.47 and then use Simple Root or whitslacks method to gain root again. Then flash back to 1.32 if you so desire. As mentioned before, do not allow it to update to 2.2 as there is not yet a method to gain root for the OTA 2.2.
Furthermore, check the dev forum for the PRI issue. They need someone with an unrooted OTA 1.47 with a PRI 1.40_003. You could be everyone's hero.
Sent from my PC36100 using XDA App

SilverZero said:
Not without root. Whatever is trying to run is almost certainly on /system, which is not writable without root access. Just let it go and root after that.
Also, NEVER PULL THE BATTERY WHILE THE SYSTEM IS FLASHING! That's a real good way to end up with a half-written (bricked) ROM.
Click to expand...
Click to collapse
wow...thanks!!! i hope i didn't screw anything up! i'm letting it finish up now...EHHH...THIS IS WIERD??? this time i was just going to let it flash and so i went ahead and plugged in my usb, but instead of flashing it went to the boot animations and back to my phone????...i'll check to see if i screwed anything up??
**EDIT: wow, it prompted me to install the update again, looks like i am back. I will try cancelling installation this time... (it gives me a discard update option) i click yes, it says "this will wipe the update from your phone" ....so I guess all is well!!!!

adeyo said:
wow...thanks!!! i hope i didn't screw anything up! i'm letting it finish up now...EHHH...THIS IS WIERD??? this time i was just going to let it flash and so i went ahead and plugged in my usb, but instead of flashing it went to the boot animations and back to my phone????...i'll check to see if i screwed anything up??
Click to expand...
Click to collapse
It probably tried to flash, found nothing there, and removed the instructions from the boot process. So you may have gotten away with it. Check your software version in Settings - About Phone to see where you ended up. Also, is your SD card still out of the phone? It may be waiting to spring back on you when you put it back in, but just let it go anyway if that's the case.

sombdy said:
Just let it update to 1.47 and then use Simple Root or whitslacks method to gain root again. Then flash back to 1.32 if you so desire. As mentioned before, do not allow it to update to 2.2 as there is not yet a method to gain root for the OTA 2.2.
Furthermore, check the dev forum for the PRI issue. They need someone with an unrooted OTA 1.47 with a PRI 1.40_003. You could be everyone's hero.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
everyone's hero?? haha...that PRI thread is why i was trying to download the 1.47 OTA in the first place anyway, i am still at 1.32 now. do you have a tip as to how i can help them??

SilverZero said:
It probably tried to flash, found nothing there, and removed the instructions from the boot process. So you may have gotten away with it. Check your software version in Settings - About Phone to see where you ended up. Also, is your SD card still out of the phone? It may be waiting to spring back on you when you put it back in, but just let it go anyway if that's the case.
Click to expand...
Click to collapse
ahh...maybe you are right? maybe it was a phantom flash anyway b/c i never put my sd card back in, also, i did delete that update.zip that was on there anyway...so i'll see if anything happens when i put the card back in. my settings show 1.32 still
**UPDATE: no attempt to reload/reboot system with update after sd card is in. Looks good!

Then you're the **** of the walk!

now, should i root and then go straight to 2.2 or go to 1.47 first?? what is the best way to keep my PRI 1.40_003 intact????

adeyo said:
now, should i root and then go straight to 2.2 or go to 1.47 first?? what is the best way to keep my PRI 1.40_003 intact????
Click to expand...
Click to collapse
I don't think you can, that's why there's a bounty out for it. When you root, your PRI will change to 1.34 because you have to use the engineering ROMs. Correct me if I'm wrong.
You don't want to just upgrade to 2.2 OTA . . . unless you WANT to block root until somebody finds a way to root Froyo on the Evo.
PRI aside, you should probably root from 1.32, no reason to go up through 1.47 and you'll avoid the "Main Version is Older" problem.

SilverZero said:
I don't think you can, that's why there's a bounty out for it. When you root, your PRI will change to 1.34 because you have to use the engineering ROMs. Correct me if I'm wrong.
You don't want to just upgrade to 2.2 OTA . . . unless you WANT to block root until somebody finds a way to root Froyo on the Evo.
PRI aside, you should probably root from 1.32, no reason to go up through 1.47 and you'll avoid the "Main Version is Older" problem.
Click to expand...
Click to collapse
great, thanks! i will root and go straight to 2.2. I guess there is no known way to keep PPI 1.4 and actually root. ...it just gets to me that unrevoked users can keep PRI 1.40 and full rooters can't...there should be some way!

adeyo said:
great, thanks! i will root and go straight to 2.2. I guess there is no known way to keep PPI 1.4 and actually root. ...it just gets to me that unrevoked users can keep PRI 1.40 and full rooters can't...there should be some way!
Click to expand...
Click to collapse
I wasn't aware of that, but the reason is probably that Unrevoked users can't flash any ROMs that would update the PRI anyway.

SilverZero said:
I wasn't aware of that, but the reason is probably that Unrevoked users can't flash any ROMs that would update the PRI anyway.
Click to expand...
Click to collapse
oh...what ROMs wouldn't update the PRI? My friend is an unrevoked 2?3? user and i know he has tried a few different ROMs ...one of them being DamageControl, most recently. He has also tried a few different kernels.
***EDIT: Here are the steps he took:
1) Started w/ Unrevoked 1
2) OTA'd 1.47
3) Unrevoked 3 from 1.47 (then was able to flash froyo rooted roms
4) He still doesn't have nand access, but he flashed the following roms: Fresh (most recent), Burnt Droid, the odexed Stock "FINAL" by netarchy, and DamageControl. Burnt droid didn't take, but neither did DamageControl at first, but now works fine. His recovery is ClockworkMod.

[Q] IM a noob that Needs help rooting my new evo!

Hey guys well i crashed the software on my old evo due to rooting lol. IM getting a new one shortly. What Im asking is a REALLY GOOD step by step guide, with the links to download the right files, to root the 2.2 stock froyo it comes with BUT ALSO nand-unlocking it while im rooting it. The reason im asking for this was I had a hard time flashing cyanogen mod 6 after i used the root method from djr3Z from the droid demos website (It was downgrading the stock 2.2 to stock 2.1, rooting 2.1 and then finally going to a rooted 2.2 with Amon Ra recovery) Please help me! Im a noob and i would really appreciate it. Thx in advance!

Nand wasn't unlocked fully with the method you used. Many people had that issue. You can either unlock nand and be done, or wait a few days for the latest unrevoked to come out.
Here is how to unlock nand :
http://theunlockr.com/2010/07/20/how-to-unlock-nand-on-the-htc-evo-4g/
Unrevoked if you wait :
http://unrevoked.com/rootwiki/doku.php/public/unrevoked3
Sent from my PC36100 using Tapatalk

sgallos1 said:
Hey guys well i crashed the software on my old evo due to rooting lol. IM getting a new one shortly. What Im asking is a REALLY GOOD step by step guide, with the links to download the right files, to root the 2.2 stock froyo it comes with BUT ALSO nand-unlocking it while im rooting it. The reason im asking for this was I had a hard time flashing cyanogen mod 6 after i used the root method from djr3Z from the droid demos website (It was downgrading the stock 2.2 to stock 2.1, rooting 2.1 and then finally going to a rooted 2.2 with Amon Ra recovery) Please help me! Im a noob and i would really appreciate it. Thx in advance!
Click to expand...
Click to collapse
If you followed regaw's complete tutorial, including unrevoked-forever, you unlocked your nand and have the ability to flash custom roms. I know because I did it and am currently running Fresh 3.2. I also made nandroid backups and boot between them.
You can't jump right in to Cyanogen because you're on the wrong hboot. Cyanogen requires hboot 76, and you're probably on 93 or similar from regaw's method. Boot phone holding volume down and check it out.
I can't post links, but you can search the forums for "ENG hboot 76" and probably get the right post on how to get hboot back. Also, I believe it may be easier to find the link in the actual Cyanogen forums.
Keep in mind this downgrades your PRI to 1.3 instead of 1.40. Find the fix for that in a different thread.
Good luck.

thom_house said:
Nand wasn't unlocked fully with the method you used. Many people had that issue. You can either unlock nand and be done, or wait a few days for the latest unrevoked to come out.
Here is how to unlock nand :
http://theunlockr.com/2010/07/20/how-to-unlock-nand-on-the-htc-evo-4g/
Unrevoked if you wait :
http://unrevoked.com/rootwiki/doku.php/public/unrevoked3
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Ok thx for that. The only question is when i get my evo and its on stock 2.2 should i do the nand-unlock, will that also root the phone in the process?

By the time you get your phone unrevoked will be out, with unrevoked, you just do a couple of mouse clicks and your done.
Also, unlocking nand is different than rooting. You must be rooted first in order to unlock nand. Just wait for your phone first, unrevoked will make it easy and painless for you.
Sent from my PC36100 using Tapatalk

Unrevoked all the way
sgallos1 said:
Ok thx for that. The only question is when i get my evo and its on stock 2.2 should i do the nand-unlock, will that also root the phone in the process?
Click to expand...
Click to collapse
Unrevoked is a great tool that truly makes it easy. When i rooted without it, I lost everything. But unrevoked doesn't delete anything at all. Will the new one unlock and or will you still need forever and .76 boot img?

dkdude36 said:
Unrevoked is a great tool that truly makes it easy. When i rooted without it, I lost everything. But unrevoked doesn't delete anything at all. Will the new one unlock and or will you still need forever and .76 boot img?
Click to expand...
Click to collapse
Not sure, still no details on their site. I recommend getting the .76 hboot because roms like cyanogenmod wont flash on other versions.
Sent from my PC36100 using Tapatalk

yea i got my evo back that i broke. They fixed it and brought it back to 2.1. I turned it off to charge it. Whne it was done and i turned it on instead of it booting up the sprint music with the 4g symbol, it went into htc with the cursive letters popping up quietly brilliant. Anyone has had this issue? I mean after that it goes smooth im on the interface and all goes well any advice?

sgallos1 said:
yea i got my evo back that i broke. They fixed it and brought it back to 2.1. I turned it off to charge it. Whne it was done and i turned it on instead of it booting up the sprint music with the 4g symbol, it went into htc with the cursive letters popping up quietly brilliant. Anyone has had this issue? I mean after that it goes smooth im on the interface and all goes well any advice?
Click to expand...
Click to collapse
Sounds like you have the oldest version of 2.1 like they did a factory reset. No issue. Your phone is primed and ready for rooting. If you are going to run CM6, then I would suggest using Toast's method to root and nand unlock. This will give you the necessary eng hboot 0.76.2000 to run that ROM. Although you may want to do search through the forums for a means of unlocking nand without downgrading your PRI to 1.34_003 (current is 1.40_003). The eng-PC36IMG.zip in Toast's part 2 "How to unlock nand" will downgrade your PRI.
Sent from my PC36100 using XDA App

I replied to your pm...
sgallos1 said:
yea i got my evo back that i broke. They fixed it and brought it back to 2.1. I turned it off to charge it. Whne it was done and i turned it on instead of it booting up the sprint music with the 4g symbol, it went into htc with the cursive letters popping up quietly brilliant. Anyone has had this issue? I mean after that it goes smooth im on the interface and all goes well any advice?
Click to expand...
Click to collapse
You are ready to rock n roll now.
First Step - Root
http://theunlockr.com/2010/07/20/how-to-root-the-htc-evo-4g-unrevoked-method/
Second Step - Unlock Nand with Toastcfh .76 Eng Bootloader
http://theunlockr.com/2010/07/20/how-to-unlock-nand-on-the-htc-evo-4g/
Third Step - Get ROM Manager
Go to the android market and download ROM Manager. Once installed, open the app and have it flash a custom recovery for you, either clockworkmod or RA.
Have Fun.

Hboot not responding to pc...zip

Ok, so this is a big problem for me. I recently got a new evo (little bro broke screen, so i got a replacement) and i instantly tried to root it. I am on hardware 0003 with hboot .79 running version 1.47. As you can see, I have gotten to 2.1 successfully. I started at 3.29 so this was pretty easy.
But now I have a huge problem. My hboot won't let me flash the pc.zips. I name them correctly, and it loads the zip, and even checks it, but just dumps me back at the menu with no error warning or anything. This is a really big problem. I can't even get back to froyo now.
So I downgraded to hb .79 software 1.47 using the rage against the cage and flashing misc method before the pc.zip. This took a few tries for the zip to update as well.
Then i used the flash exploit to try to root eclair. Everything went great. But my pc goes to checking, and then dumps me back at the menu.
Plz help me
Dk

I had the same issue hboot would search but than drop me back at main menu. This pc36 file woorked for me found it in another post let me know if it works.
View attachment PC36IMG.zip

jdh10475 said:
I had the same issue hboot would search but than drop me back at main menu. This pc36 file woorked for me found it in another post let me know if it works.
View attachment 438729
Click to expand...
Click to collapse
Thanks jdh. I. Will test in the morning. Could you tell me what is in the pc36img.zip? This would be very helpful for me to know what the he'll I am flashing. Does this fox the problem for pc.zips after it, or what? Any more info?

Did you make sure you have plenty of space on your SD card and that you still have S=OFF? I would also try the eng bootloader (.76) since it comes with S=OFF by default

I do have space, but I don't have s-off. I have just run the flash exploit though, so I think that gives me a chance to flash the eng build and then turn s-off. Correct me if I am wrong. I am just trying to root. Again, s is still on

dkdude36 said:
I do have space, but I don't have s-off. I have just run the flash exploit though, so I think that gives me a chance to flash the eng build and then turn s-off. Correct me if I am wrong. I am just trying to root. Again, s is still on
Click to expand...
Click to collapse
The flash exploit still works? I figured they would have fixed that by now, thats a pretty big security hole lol
ya, if you can get the # root prompt you should be able to flash the mtd-eng and then Toast's pc36img. Once you have root his part 2 guide should tell you how to do everything.
Edit: ignore that about the flash exploit, I forgot you said you downgraded lol

Hah ya I think that might be the problem. I did downgrade to the1.47, but I think something is broke. I will wipe, and do netarchy's method of deleting two files in 1.47 and then doing toasts part two (wow, fail htc. Only two files?) and report back. I will also check md5 which I have not yet done.

HBoot 76.200

not working. i am starting to get sort of annoyed. i can't even get back to froyo.

i am going to pm steelh. if he doesnt help, i am going to go to toast. unless anybody has any other suggestions of people i should ask before going straight to the root master

Invoke the OTA updates. About 3 times until you get to 3.29.
(Assuming s-off)
Then everything will work and you can flash whatever you want.

as i said before, s is not off. i am trying to get it off. it is much harder to do in 3.29, so i tried in 1.47 and i am stuck now. no otas. i am giving it another shot right now. thanks for trying

You need to downgrade farther. Go to 1.32
Make sure the s-off file is on your sdcard before you do so. You will lose USB until you upgrade back to 3.29

thanks for the suggestion. where can i find a 1.32 pc36im.zip so i can try it? i'm not even sure if it will accept it. could you post a link? i have rooted 1.32 before, so this should be a breeze