Develop Bugs

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

stock device, can I RUU to older updates?

Here's my question. My friend's brother attempted to root his stock Evo using simpleroot instructions I sent my friend 4-5 months ago (pre-2.2) without knowing that simpleroot isn't supported. His phone is now borked. When he tries to load into bootloader, he gets an error (not sure which one), but his phone will boot into android.
What I'm wondering is this: As of yesterday, his phone was updated and current as per sprint and the update commands in the system menus... Can he flash back to an older stock rom via RUU (such as this one) without causing other problems? If my understanding is correct, the latest sprint updates aren't yet rootable, right?
Any help on this issue?
Thanks

Is the phone s-off?
Sent from my PC36100 using XDA App

badutahboy said:
Here's my question. My friend's brother attempted to root his stock Evo using simpleroot instructions I sent my friend 4-5 months ago (pre-2.2) without knowing that simpleroot isn't supported. His phone is now borked. When he tries to load into bootloader, he gets an error (not sure which one), but his phone will boot into android.
What I'm wondering is this: As of yesterday, his phone was updated and current as per sprint and the update commands in the system menus... Can he flash back to an older stock rom via RUU (such as this one) without causing other problems? If my understanding is correct, the latest sprint updates aren't yet rootable, right?
Any help on this issue?
Thanks
Click to expand...
Click to collapse
No, you can not run an older ruu. If he updated to today or yesterdays update hes stuck. If he is on HBOOT 2.02 he can flash the 3.30.651.3 ruu or ths 3.70.651.1 but you can not ruu further back.

animal7296 said:
No, you can not run an older ruu. If he updated to today or yesterdays update hes stuck. If he is on HBOOT 2.02 he can flash the 3.30.651.3 ruu or ths 3.70.651.1 but you can not ruu further back.
Click to expand...
Click to collapse
Are either of these rootable yet?
and can someone explain what S-on and off means?

badutahboy said:
Are either of these rootable yet?
and can someone explain what S-on and off means?
Click to expand...
Click to collapse
Yes, they're both rootable.
S-ON vs S-OFF; is just basically a security parameter that's being locked/unlocked. This allows for PC36IMG's files to be flashed via the bootloader without having to use or have authenticated signature keys from Google.
Basically, if you ever accept an OTA and it flashes and removes your recovery (CWM or Amon_RA); then you have no way of flashing custom roms/mods, etc... however with S-OFF, you have the ability to get your recovery back and set yourself back to root if need be.
Essentially, S-OFF allows for another method of flashing stuff to the phone besides just using the CWM or Amon_RA recoveries.
Hboot versions however can affect S-OFF; so it's important that if there is a new OTA that you always hold off, until a developer can validate that the hboot can be exploited and that the OTA can be rooted.

badutahboy said:
Are either of these rootable yet?
and can someone explain what S-on and off means?
Click to expand...
Click to collapse
1. 2.02 is rootable 2.10 is not and is the newest one.
2.0 S-ON means you can not flash roms s-off means you can. It is the security of the phone kind of.
If you can not get into bootloader then you can try running the oldest ruu and then the next. It wont hurt the phone at all (I just did it today) it will just give you an error and reboot the phone.

pseudoremora said:
Yes, they're both rootable.
S-ON vs S-OFF; is just basically a security parameter that's being locked/unlocked. This allows for PC36IMG's files to be flashed via the bootloader without having to use or have authenticated signature keys from Google.
Basically, if you ever accept an OTA and it flashes and removes your recovery (CWM or Amon_RA); then you have no way of flashing custom roms/mods, etc... however with S-OFF, you have the ability to get your recovery back and set yourself back to root if need be.
Essentially, S-OFF allows for another method of flashing stuff to the phone besides just using the CWM or Amon_RA recoveries.
Hboot versions however can affect S-OFF; so it's important that if there is a new OTA that you always hold off, until a developer can validate that the hboot can be exploited and that the OTA can be rooted.
Click to expand...
Click to collapse
Thanks for the explanations and the help.
How do I find out if it's S-on or off, and is it possible to change?

pseudoremora said:
Yes, they're both rootable.
S-ON vs S-OFF; is just basically a security parameter that's being locked/unlocked. This allows for PC36IMG's files to be flashed via the bootloader without having to use or have authenticated signature keys from Google.
Basically, if you ever accept an OTA and it flashes and removes your recovery (CWM or Amon_RA); then you have no way of flashing custom roms/mods, etc... however with S-OFF, you have the ability to get your recovery back and set yourself back to root if need be.
Essentially, S-OFF allows for another method of flashing stuff to the phone besides just using the CWM or Amon_RA recoveries.
Hboot versions however can affect S-OFF; so it's important that if there is a new OTA that you always hold off, until a developer can validate that the hboot can be exploited and that the OTA can be rooted.
Click to expand...
Click to collapse
I have been trying to root 2.10 since yesterday and it has proven to not be possible as of yet. If you have a rooting method that works for me then would you share please?

animal7296 said:
I have been trying to root 2.10 since yesterday and it has proven to not be possible as of yet. If you have a rooting method that works for me then would you share please?
Click to expand...
Click to collapse
Im with u brotha im stuck on 2.10 from a mistake i made. Was originally on 0.76.2
Sux man
Sent from my PC36100 using Tapatalk

badutahboy said:
Thanks for the explanations and the help.
How do I find out if it's S-on or off, and is it possible to change?
Click to expand...
Click to collapse
To see if you're S-OFF or S-ON; you can boot your phone into bootloader mode.
To do this:
1. Power down the phone
2. Hold the Volume Down + Power button
3. You'll see a white screen with three little Androids
4. Read the very top of the screen; should tell you if you are S-ON or S-OFF.
You can reboot afterwards.
And yes, you can switch from the S-ON to S-OFF and vise versa, though I don't see why you would want to do the latter.
animal7296 said:
I have been trying to root 2.10 since yesterday and it has proven to not be possible as of yet. If you have a rooting method that works for me then would you share please?
Click to expand...
Click to collapse
luckylui said:
Im with u brotha im stuck on 2.10 from a mistake i made. Was originally on 0.76.2
Sux man
Click to expand...
Click to collapse
I apologize to the both of you guys; I was under the impression that 2.10 was S-OFF, apparently testing is still being done. For now, looks like you'll have to sit tight. Sorry guys.

pseudoremora said:
To see if you're S-OFF or S-ON; you can boot your phone into bootloader mode.
To do this:
1. Power down the phone
2. Hold the Volume Down + Power button
3. You'll see a white screen with three little Androids
4. Read the very top of the screen; should tell you if you are S-ON or S-OFF.
You can reboot afterwards.
And yes, you can switch from the S-ON to S-OFF and vise versa, though I don't see why you would want to do the latter.
I apologize to the both of you guys; I was under the impression that 2.10 was S-OFF, apparently testing is still being done. For now, looks like you'll have to sit tight. Sorry guys.
Click to expand...
Click to collapse
However it has been verified that if you were S-OFF on 2.02 you can install the OTA and you will end up with HBOOT 2.10 with S-OFF.

pseudoremora said:
To see if you're S-OFF or S-ON; you can boot your phone into bootloader mode.
To do this:
1. Power down the phone
2. Hold the Volume Down + Power button
3. You'll see a white screen with three little Androids
4. Read the very top of the screen; should tell you if you are S-ON or S-OFF.
You can reboot afterwards.
And yes, you can switch from the S-ON to S-OFF and vise versa, though I don't see why you would want to do the latter.
I apologize to the both of you guys; I was under the impression that 2.10 was S-OFF, apparently testing is still being done. For now, looks like you'll have to sit tight. Sorry guys.
Click to expand...
Click to collapse
No prob pimp
Ima call sprint n see if i can some how get me a phone w the 2.02 hboot and just pretty much get an upgrade from 0003 hardware to 0004 Lol
Im like jumpy rite now ahaha
Sent from my PC36100 using Tapatalk

tpbklake said:
However it has been verified that if you were S-OFF on 2.02 you can install the OTA and you will end up with HBOOT 2.10 with S-OFF.
Click to expand...
Click to collapse
True this, but when i did it i was at 0.76.2 and now screw at 2.10 cause it updated all the way n i didnt want to do that.. Got lost in the tangle haha
Sent from my PC36100 using Tapatalk

tpbklake said:
However it has been verified that if you were S-OFF on 2.02 you can install the OTA and you will end up with HBOOT 2.10 with S-OFF.
Click to expand...
Click to collapse
Yea, I heard about this in the IRC; too bad these guys can do that... unfortunate; but I'm sure the Unrevoked team will have a fix soon enough.
luckylui said:
No prob pimp
Ima call sprint n see if i can some how get me a phone w the 2.02 hboot and just pretty much get an upgrade from 0003 hardware to 0004 Lol
Im like jumpy rite now ahaha
Click to expand...
Click to collapse
Good luck with Sprint; I don't know how helpful they're going to be, but you never know...

@luckylui and animal7296, check out the 2.02/2.10 rooting thread again, it seems they got something working. Good luck.

badutahboy said:
Here's my question. My friend's brother attempted to root his stock Evo using simpleroot instructions I sent my friend 4-5 months ago (pre-2.2) without knowing that simpleroot isn't supported. His phone is now borked. When he tries to load into bootloader, he gets an error (not sure which one), but his phone will boot into android.
What I'm wondering is this: As of yesterday, his phone was updated and current as per sprint and the update commands in the system menus... Can he flash back to an older stock rom via RUU (such as this one) without causing other problems? If my understanding is correct, the latest sprint updates aren't yet rootable, right?
Any help on this issue?
Thanks
Click to expand...
Click to collapse
There actually is a way to downgrade without rooting, all you need to do is flash the mtd-eng.img file to your misc partition as explained in toast's rooting part 2 thread. After you do that it will let you flash any ruu that is compatible with your phone
Sent from my PC36100 using XDA App

Hboot questions

So it seems as there is still some uncertainty in terms of updating to new hboot. Read some people lost root by doing so and read some were successful possibly due to having unrevoked forever installed. I updated to latest radio, wimax and nv already. Has anybody been able to downgrade the radio? I ask as it seems if downgrading is possible than unrevoked could be installed and then the hboot could be updated without losing root s-off. I appreciate any information and all your help.
Sent from my PC36100 using XDA App

starkillers said:
So it seems as there is still some uncertainty in terms of updating to new hboot. Read some people lost root by doing so and read some were successful possibly due to having unrevoked forever installed. I updated to latest radio, wimax and nv already. Has anybody been able to downgrade the radio? I ask as it seems if downgrading is possible than unrevoked could be installed and then the hboot could be updated without losing root s-off. I appreciate any information and all your help.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Why would you want to upgrade the hboot?

Was reading a few threads that suggest we should. I believe calkulin posted saying that he would update the hboot if it weren't for the fact that he uses fastboot commands during his development. Page 110 of his thread.
xHausx said:
Why would you want to upgrade the hboot?
Click to expand...
Click to collapse
Sent from my PC36100 using XDA App

From what I've seen the new hBoots are all backward compatible, and as long as you have already ran Unrevoked Forever you *should* keep S-OFF, but the new hBoot has been particularly stubborn when it comes to abiding by the S-OFF. The extended commands on the eng-hBoot may not be very useful to most people but they can be very handy if something goes wrong and you manage to fubar your phone. So as long as you retain S-OFF or a custom recovery you should be ok using the 2.02 hBoot but I would wait awhile to find out more about ver 2.10. Especially if you plan on upgrading your radio.

I have already upgraded radio, wimax and nv and I don't have unrevoked forever installed . My hboot is the original with fastboot commands.
xHausx said:
From what I've seen the new hBoots are all backward compatible, and as long as you have already ran Unrevoked Forever you *should* keep S-OFF, but the new hBoot has been particularly stubborn when it comes to abiding by the S-OFF. The extended commands on the eng-hBoot may not be very useful to most people but they can be very handy if something goes wrong and you manage to fubar your phone. So as long as you retain S-OFF or a custom recovery you should be ok using the 2.02 hBoot but I would wait awhile to find out more about ver 2.10. Especially if you plan on upgrading your radio.
Click to expand...
Click to collapse
Sent from my PC36100 using XDA App

I have 0.79, and as long as everything else is working, I don't see why it should be necessary to upgrade. And now that I've already updated all my radio's with the latest combo pack, I'm apprehensive about doing it anyway.

DarkAudit said:
I have 0.79, and as long as everything else is working, I don't see why it should be necessary to upgrade. And now that I've already updated all my radio's with the latest combo pack, I'm apprehensive about doing it anyway.
Click to expand...
Click to collapse
Same here except I think I'm at even a lower version... 0.76
What would the point be to upgrading hboot to 2.02? It's one thing I don't really understand all that well.
Anyone care to explain?

Issue upgrading a rooted evo from 2.2 to 2.3

Ok let start by getting a few things out of the way.
1 I'm sorta a Noob ok kick me crack a joke or two I don't care as long as you help
2. I have Htc evo of course running stock 2.2 (baseband ver 2.15.00.11.19)
Kernel ver 2.6.32.17-gee557fd htc-kernel and18-2 #15) (S-ON)
Radio-2.15.00.11.19 and I'm using a Mac (if that help)
3. I rooted it using the unrevoked method.
The device works fine but bit I'm having a big issue trying to upgrade from 2.2 to 2.3.
I have been trying to unroot the phone so that I can update OTA.
But no matter how many times I try to unroot it my super user is still there
I would rather flash the phone to a 2.3 GB rom thats 2.3 with sense 2.1 or 3.0.
I've tried this the method found on youtube using the s-on and dropping the image file (zip) on the sd card and flashing it
by making sure you install the (s-on) patch
and re-flashing the RUU (PC36IMG).
but when I did that it said that i was re-flashing a old version.. so I found a newer version.
But when I drop it on my SD card as (PC36IMG.zip) it reads it, checks it then... takes me right back to the Hbot screen like nothing never happen!!!
I've been working on this for 3 days I've even tried restoring and everything.
I've been searching online for answers but I can't find anything that helps either its not up to date or just flat out dont work.
at the end of the day i just want a damn evo running BG 2.3 sense 2.1 or 3.0 would be nice.
​
oh by the way when i try to run the OTA it reboots startes to load get about 35% then goes to the exclamation mark / triangle.
I'm out of options please help me out! I've searched and read on for about 3 days now.
please either help flash the device to a stable working 2.3 with sense 2.1-3 or un root it so i can update it ota and re root it again...

http://forum.androidcentral.com/htc...19278-how-unroot-return-stock-ruu-method.html
http://theunlockr.com/2010/06/14/how-to-unroot-the-htc-evo/
try these...
this link below should be a valuable resource for you...
http://forum.xda-developers.com/wiki/index.php?title=HTC_Supersonic/Guides_&_Tutorials

Wow man, between the general and q&a sections there are seven threads dealing with this very topic. Yet you couldn't find any of them?
If you want to unroot and take the ota you will need to flash the s-on update and run the 3.70 ruu to unroot. Once you do that you'll be completely unrooted and like new. Then just take the update and it should go through without any issues. If, however, your bootloader shows a firmware version higher than 3.70 and you are s-on then I'm sorry to say you are stuck like that.

xHausx said:
Wow man, between the general and q&a sections there are seven threads dealing with this very topic. Yet you couldn't find any of them?
If you want to unroot and take the ota you will need to flash the s-on update and run the 3.70 ruu to unroot. Once you do that you'll be completely unrooted and like new. Then just take the update and it should go through without any issues. If, however, your bootloader shows a firmware version higher than 3.70 and you are s-on then I'm sorry to say you are stuck like that.
Click to expand...
Click to collapse
I've dont that and i still can not remove the root

You'll need to flash the PC36IMG through fastboot to see what's going wrong with it then. To do that download the AutoRoot tools zip and the PC36IMG_3.70.651.1.zip from the link below. Once you have them both unzip the tools folder and place the PC36IMG in it, then run the FlashZip script and tell it to flash the 3.70.651.1 zip
It should flash ok but if not it'll give you an error message saying what went wrong with it. Keep in mind you're going to be completely unrooted if your bootloader shows S-ON.

tailsthecat3 said:
http://forum.androidcentral.com/htc...19278-how-unroot-return-stock-ruu-method.html
http://theunlockr.com/2010/06/14/how-to-unroot-the-htc-evo/
try these...
this link below should be a valuable resource for you...
http://forum.xda-developers.com/wiki/index.php?title=HTC_Supersonic/Guides_&_Tutorials
Click to expand...
Click to collapse
ok I've been trying this method but im getting a error 140 BOOTLOADER VERSION ERROR
where can i get a more up to date ruu?

SixReasons said:
ok I've been trying this method but im getting a error 140 BOOTLOADER VERSION ERROR
where can i get a more up to date ruu?
Click to expand...
Click to collapse
What version does it say your firmware is?

xHausx said:
What version does it say your firmware is?
Click to expand...
Click to collapse
3.70.651.1 cl294884

SixReasons said:
3.70.651.1 cl294884
Click to expand...
Click to collapse
What HBoot do you have... I think just flashing one of the stock GB roms probably would of been easier just my opinion....
Sent from my EVO rocking Evervolv Gingerbread

i just found a ruu for 3.70.651.1 ... installing so far so good

You do realize that you'll lose root until a new method is found, correct? If you want to stay rooted, you need to reroot, then flash the stock rooted 2.3 rom.
If you want a newer version of Sense, you'll be outta luck there too - the new update is same ol' Sense 1.0.
Just making sure you realize this, since so many people are whining about not being able to root the OTA and being stuck with the uneventful update.
(from... Evo/MIUI/Tapatalk)

hey guys i got it working thanks for your help!!!!

[Q] Another question about hboot

Is there any reason why somebody WOULD NOT want the latest hboot version?
For example, the latest version (according to forum.xda-developers.com/showthread.php?t=715485) is 2.16.0001. Yet I still see some members on here using 2.15.0001 and 2.10.0001. Is that because they just haven't gotten around to flashing the updated version? Are there are negative effects to having the latest hboot version? On that same website, it says some of the later versions are "not downgradeable". So why would you want to downgrade?
Also, in searching through threads, I think I've kinda picked up on a problem between certain hboot versions and certain Radio versions, that some versions are not compatible with each other. Is there any problem?
Thanks for the help!
Basic summary of questions:
1. Is it good to have the latest version of hboot?
2. Are there any negative effects to having X version of HBOOT versus Y version of HBOOT?
3. Would there ever be a point to downgrading your hboot, besides taking it back to the store?
4. Does X version of HBOOT conflict with Y version of RADIO?

jasongthang said:
Is there any reason why somebody WOULD NOT want the latest hboot version?
For example, the latest version (according to forum.xda-developers.com/showthread.php?t=715485) is 2.16.0001. Yet I still see some members on here using 2.15.0001 and 2.10.0001. Is that because they just haven't gotten around to flashing the updated version? Are there are negative effects to having the latest hboot version? On that same website, it says some of the later versions are "not downgradeable". So why would you want to downgrade?
Also, in searching through threads, I think I've kinda picked up on a problem between certain hboot versions and certain Radio versions, that some versions are not compatible with each other. Is there any problem?
Thanks for the help!
Basic summary of questions:
1. Is it good to have the latest version of hboot?
2. Are there any negative effects to having X version of HBOOT versus Y version of HBOOT?
3. Would there ever be a point to downgrading your hboot, besides taking it back to the store?
4. Does X version of HBOOT conflict with Y version of RADIO?
Click to expand...
Click to collapse
1. It is what it is, is just tells you what stock firmware you had; no hboot is better; though you could argue the .76 cuz of fastboot, though you can use fastboot regardless
2. Yes and no, just before 2.10, they can no longer be downgraded; the .76 also allows fastboot commands
3. You would only 'downgrade' really if you had to use evolutionary to go from 6.16 > 2.16 , and that is done for you in the unrooting process
4. No, the hboot won't conflict with your radio

Thanks man, appreciate it.

jasongthang said:
Thanks man, appreciate it.
Click to expand...
Click to collapse
No problem man.

2. The only negative effect of having a hboot above 2.10 is you cannot run unrevoked forever which means that any future ota cannot s-on your phone if you have flashed unrevoked forever. Also dont go getting any ideas of downgrading your hboot unless it is for unrooting like roxxorz said cuz you will most likely brick your phone
Sent from my DECK'ed out EVO

{ParanoiA} said:
2. The only negative effect of having a hboot above 2.10 is you cannot run unrevoked forever which means that any future ota cannot s-on your phone if you have flashed unrevoked forever. Also dont go getting any ideas of downgrading your hboot unless it is for unrooting like roxxorz said cuz you will most likely brick your phone
Sent from my DECK'ed out EVO
Click to expand...
Click to collapse
so if i dont plan on using any OTA's from sprint, i can just flash 2.16.0001 hboot and just run rooted roms correct? And then if I run the stock RUU to unroot back to complete stock, would that change the hboot?