Hello,
This afternoon I made what feels like a monumental mistake on my flashed and rooted DHD. I was running CM 7.0.2, as I have been since it was released at some point last week, when it started to reboot by itself... Being impatient I did a hard reset and then pressed the volume up button, starting some kind of update, which I can only assume was a bad idea. Since this update I have lost almost everything and my phone is S-ON again!
I rooted and flashed my DHD using one of the tutorials on this board which worked fine. I downgraded from 1.72 to 1.32, used Visionary+ to give permanent root access, turned S-OFF and then used ROM Manager to install CM7.
Now I am finding it difficult to get back to CM 7.0.2. I can give myself permanent root using Visionary+ but cannot seem to turn S-OFF.
I used this link to download the H-BOOT files:
http://forum.xda-developers.com/showthread.php?t=835746
I load the unzipped files to the root of my SD card and type: sh /sdcard/DHD/check
in Terminal Emulator and now when I press enter no MD5 appears and the error message after Testing Kernel Module does not match.
I have tried a factory reset which does nothing, I have tried downloading different versions of the DHD H-BOOT files from across the web but I get the same problem and when I look under my software the build number is 1.32.405.6 CL278359 release-keys.
Any advice on getting CM7 back would be appreciated!
It could have been worse and I could have bricked my phone but the tutorials on doing this were excellent so I saw no real risk... but CM7 rocks and I need it back!
My first thought is that you still had the PD98IMG.zip on your sdcard, and you somehow managed to flash that which will remove the s-off?
Are you able to boot up at all, or just Bootloader? Edit: No sleep here, read you post properly and you say can boot into cm7.
What does Bootloader / System Info : CID ?
Try this all-in-one tool: [DEV APP] Updated! AMT v1.2 - ROOT, S-OFF, Flash Radio, Recovery, Boot
Setting: Default, Permroot > "commit changes" ENG S-off if you require to flash a recommened radio later.
Download here, extract, & just follow the instructions exactly. ENG HBOOT image is included.
That is correct, I do still have PD98IMG.zip on my sdcard.
I can boot up fine also.
System info is showing
Android Version 2.2,
Kernel version 2.6.32.21-gf3f553d [email protected] #1,
Build number 1.32.405.6 CL278359 release-keys,
Software number 1.32.405.6.
Bootloader is showing:
ACE PVT SHIP S-ON,
HBOOT- 0.85.0007
I found my CID through Terminal Emulator it is: HTC_001
If that sdcard is your Goldcard, either copy the whole contents to pc (in a safe place) so it's clean, or FULL format fat32 new one and insert before boot.
Most of the guides will tell you to remove the PD98IMG.zip, although maybe in fine print.
Yep, Permroot & S-off is gone as you don't have CID-11111111 & S-off.
If you decide to ENG S-off as well, HBOOT will only show ENG S-off not both. You will have S-off, although it doesn't say.
The tool should work, just give it a go (no need for visionary). Read the Dev's thread & follow instructions exactly step by step. After that, should be done in minutes.
Afterthat, power off. Boot into Bootloader (HBOOT). HOLD vol down and press power on once. You should have -Off or ENG S-off. Check System Info in HBOOT menu for CID-11111111
Hi Brucey89
Brucey89 said:
That is correct, I do still have PD98IMG.zip on my sdcard.
I can boot up fine also.
System info is showing
Android Version 2.2,
Kernel version 2.6.32.21-gf3f553d [email protected] #1,
Build number 1.32.405.6 CL278359 release-keys,
Software number 1.32.405.6.
Bootloader is showing:
ACE PVT SHIP S-ON,
HBOOT- 0.85.0007
I found my CID through Terminal Emulator it is: HTC_001
Click to expand...
Click to collapse
Remove PD98IMG.zip from SDCard once it has been installed after a downgrade, otherwise it will keep trying to [will] reinstall itself.
Take Care
TheQuest
The sdcard is not my goldcard so I can format the sdcard completely, where do I go from there? Just start to rooting/flashing process from scratch and it should work fine?
I'm TheQuest said:
Hi Brucey89
Remove PD98IMG.zip from SDCard once it has been installed after a downgrade, otherwise it will keep trying to [will] reinstall itself.
Take Care
TheQuest
Click to expand...
Click to collapse
Read my apost above yours, doesn't need to be said twice
Brucey89 said:
The sdcard is not my goldcard so I can format the sdcard completely, where do I go from there? Just start to rooting/flashing process from scratch and it should work fine?
Click to expand...
Click to collapse
Yep, should be fine. Just use the tool, follow my instructions in the above post/s, won't take long. Just follow the Devs thread steps exactly........... not too many. Short & sweet.
Hi UpInTheAir
UpInTheAir said:
Read my apost above yours, doesn't need to be said twice
Click to expand...
Click to collapse
You have edited your post to say what it is saying now, it had said
I thought you still had PD98IMG.zip on your SD Card
Click to expand...
Click to collapse
.
Take Care.
TheQuest
I'm TheQuest said:
Hi UpInTheAir
You have edited your post to say what it is saying now, it had said .
Take Care.
TheQuest
Click to expand...
Click to collapse
Didn't edit tht bit matey, was added info further down and also underlined remove. Never mind, as you can see in my first reply, have edit for not reading properly.
Hi UpInTheAir
UpInTheAir said:
Didn't edit tht bit matey, was added info further down and also underlined remove. Never mind, as you can see in my first reply, have edit for not reading properly.
Click to expand...
Click to collapse
I can now see you have not edited your first post.
When I started writing my reply to Brucey89 where I made a part of his post bold, your second reply post was not up.
Take Care
TheQuest
It worked like a charm, thank you!
Brucey89 said:
It worked like a charm, thank you!
Click to expand...
Click to collapse
No problem at all. Glad to have helped.
@ Quest,
OK, I think that particular edit was put in when I was about to submit on the first post. Just getting sick of members repeating the same "fix" that's already been said. I do realeize you7rs was unintentional, and probably responding at the same time I was or when I was editing. I'm sure Brucey was glad for the extra input to confirm the suspicions. Take care.
Related
So I first followed these instructions to use Unrevoked to root my girlfriend's new phone, as this was how I rooted my phone:
http://theunlockr.com/2010/07/20/how-to-root-the-htc-evo-4g-unrevoked-method/
Unrevoked said it was triumphant, but when I rebooted into my bootloader, and selected fastboot -> recovery I just got a black screen with a red triangle. Apparently, there's no nandroid loaded on my phone.
So I proceeded to follow Toast's 2 part guide here:
Part 1: http://forum.xda-developers.com/showthread.php?t=718889
Part 2: http://forum.xda-developers.com/showthread.php?t=701835
Apprehensive about not being able to perform a nandroid backup, I proceeded anyways, but when I tried to create /data/flash_image I received an error: permission denied. So I'm positive I don't have root either.
So I went to this tutorial believing that I probably had a newer version (even though my notification bar is telling me I need to download the mandatory update) and followed these directions:
http://forum.xda-developers.com/showthread.php?t=718889
I repeated my previous steps, but was still no closer. Finally, I went to these directions:
http://forum.xda-developers.com/showthread.php?t=690762
but when I tried to update using the pc36img file, after it finished checking the file it said "Main version is older! Update fail! Do you want to reboot device?"
So I'm pretty much stuck. What can/should I do?
e:
Sprint HTC Evo 4G
Supersonic EVT3 Ship S-On
HBOOT-2.02.0000
MICROP-041f
TOUCH PANEL-ATMELC03_16ac
RADIO-2.15.00.09.01
Oct 14 2010, 19:14:47
Well, you need to figure out what version the phone is in the bootloader as in what hboot version.. And also you need to see what hardware version. You are trying to use methods that WILL NOT work on a new Evo.
Yellowcard8992 said:
Well, you need to figure out what version the phone is in the bootloader as in what hboot version. And also you need to see what hardware version. You are trying to use methods that WILL NOT work on a new Evo.
Click to expand...
Click to collapse
Pretty much what this guy said.
You're going to need to use the new method for the 2.02 HBOOT since S-ON is present. If S-OFF was present you'd obviously be ready to go to flash a custom recovery and flash your ROM of choice.
Here's a guide to get your S-OFF with 2.02, follow it to the "T": http://forum.xda-developers.com/showthread.php?t=829045
Once you've got S-OFF and a custom recovery loaded, you'll just have to flash a ROM. Personally, I'd recommend Myn's Warm 2.2 RLS4. It's the fastest ROM I've used and looks/works the best, imo.
Yellowcard8992 said:
Well, you need to figure out what version the phone is in the bootloader as in what hboot version.. And also you need to see what hardware version. You are trying to use methods that WILL NOT work on a new Evo.
Click to expand...
Click to collapse
cosine83 said:
Pretty much what this guy said.
You're going to need to use the new method for the 2.02 HBOOT since S-ON is present. If S-OFF was present you'd obviously be ready to go to flash a custom recovery and flash your ROM of choice.
Here's a guide to get your S-OFF with 2.02, follow it to the "T": http://forum.xda-developers.com/showthread.php?t=829045
Once you've got S-OFF and a custom recovery loaded, you'll just have to flash a ROM. Personally, I'd recommend Myn's Warm 2.2 RLS4. It's the fastest ROM I've used and looks/works the best, imo.
Click to expand...
Click to collapse
Like all any other nerd in this forum on a thought about "How do I root this phone?" - Check the fkn specs of the phone to root with the instructions that has the details of your phone ONLY...gosh jeez peeoople where did we go wrong here?
Bad luck you wrote the wrong root method on a new females phone. >_<
Make sure you find out the Hboot version and the S-OFF has to be there for your phone to be flashed with a new rom / kernel for use.
What everyone said, but in case you don't know. To check your Hboot version boot to the bootloader (power on + vol down) to check your version.
cosine83 said:
Here's a guide to get your S-OFF with 2.02, follow it to the "T": http://forum.xda-developers.com/showthread.php?t=829045
Click to expand...
Click to collapse
This is what I needed, thanks. Sorry, but it had been since the EVO launched since the last time I had to unlock one, sorry I wasn't completely versed in the nuances of hboot versions and the appearance of S-On. I'm glad someone was nice enough to simply post the correct guide.
This is the jist of my problem, and im trying to get it fixed, as i have work tomorrow.
Bought an Evo 4g about a week ago. Decided i wanted to root it today, went on here, found some threads for rooting it.
Now before i say this next part, i have rooted other phones with no problems, so i didnt think this would happen to me.
Back to my point, followed the steps as thoroughly as possible, but when It was installing the PC36IMG file, it said "Radio_v2 : Fail PU or something like that. Rebooted the phone, and it sits at the HTC evo 4g screen... tried doing that same step over with the same problem. So i chose the clear storage option, restarted, same problem, then got into recovery and did the factory reset option, and now when i start my phone, it goes straight to recovery mode. Nothing more nothing less.
Anybody out there know how i can just get the factory stock rom or what ever back on this thing? ill be up all night till i get it fixed. Also maybe the update.zip? idk.
Any help would be much appreciated!
Are you in recovery or the boot loader? do you see skating androids?
wildgillis said:
Are you in recovery or the boot loader? do you see skating androids?
Click to expand...
Click to collapse
I can get to both screens. If i just start it up without holding volume down, it goes to recovery and i have to take out the battery and restart it again holding volume down to get to the bootloader screen
on the bootloader screen (skating androids) what is your hboot version (second line) and is s-off or s-on (second line)
also link to instructions you used to root (different hboot versions use different instructions)
wildgillis said:
on the bootloader screen (skating androids) what is your hboot version (second line) and is s-off or s-on (second line)
also link to instructions you used to root (different hboot versions use different instructions)
Click to expand...
Click to collapse
Okay check it out, here is an update of where im at, and im going to get you most of that information in just a minute..
Anyways, i found a Different pc36img.zip file and used that through bootloader and i didnt get any failure messages. Now my phone is started up and i received like 15 texts, and 3 voice mails so far..
the file was uploaded to megaupload and the descrpition was "EVO RESTORE 3.29.65.1.5"
Ill restart my phone now into bootloader mode to get you that info.
Do you happen to know what the original version was on your phone?
wildgillis said:
on the bootloader screen (skating androids) what is your hboot version (second line) and is s-off or s-on (second line)
also link to instructions you used to root (different hboot versions use different instructions)
Click to expand...
Click to collapse
Okay i took a picture of what it says, but sincei just joined today i cant post it so this is the link from imageshack where i uploaded the picture
img26.imageshack . us/ img26 /4523 / evo4g.jpg
Just delete the spaces. and if it doesnt work, ill just type out everythingi t says
wildgillis said:
Do you happen to know what the original version was on your phone?
Click to expand...
Click to collapse
I just bought it last week from Radio Shack, so im assuming 2.2... But im not sure.
Current update is the phone works now and im pretty happy about that. Think maybe i should do some more research before i try to root it and flash custom roms. I do want to though, one day.
Phone says:
SUPERSONIC EVT2-3 SHIP S-ON
HBOOT-2.02.0000
MICROP-O41f
TOUCH PANEL-ATMELC03_16ac
RADIO-2.15.00.09.01
Oct 14 2010, 19:14:47
If your phone is working now after recovery use one of the following methods for root
http://forum.xda-developers.com/showthread.php?t=838448
or
http://forum.xda-developers.com/showthread.php?t=829045
(make sure to follow instructions for hboot 2.02)
Glad you got it up and working the last phone I rooted was an 2.02 and it took me a few tries before I got it figured out.
wildgillis said:
If your phone is working now after recovery use one of the following methods for root
http://forum.xda-developers.com/showthread.php?t=838448
or
http://forum.xda-developers.com/showthread.php?t=829045
(make sure to follow instructions for hboot 2.02)
Click to expand...
Click to collapse
Thank you, i didnt see these posts before. I recently looked at the posts i was following, and they were dated back to august. So im sure these will be much better.
Another quick question...
So after all this friggen work, does this mean its rooted now?
no, if your rooted it will say S-off, and you will have a working recovery installed not just the bootloader.
cruise350 said:
no, if your rooted it will say S-off, and you will have a working recovery installed not just the bootloader.
Click to expand...
Click to collapse
alright thank you. ill refer to the links posted earlier in this thread to root it properly then.
Hi,
I've got my DZ a couple of days ago. It's a secondhand DZ. Previously i've used HTC Touch, Touch Dual, TP2, so this is my first Android experience. I did lots of ROM playing on previous winmo phones, but after reading for these couple of days of Android modding, i learn that flashing another Android ROM is not so simple as winmo ROM.
This is my DZ info:
Android version 2.2.1
Baseband version 12.28e.60.140fU_26.04.02.17_M2
Kernel version 2.6.32.21-g6e170e7
Build number 1.82.707.1 CL317545 release-keys
Software number 1.82.707.1
VISION PVT SHIP S-OFF
HBOOT - 0.85.0009
MICROP - 0425
RADIO - 26.04.02.17_M2
eMMC - boot
Dec 13 2010
I've check with root checker and Titanium Backup, it says NO root access.
I've learned that with 1.82, i will have to downgrade first to 1.34.
In the steps for downgrading, i found that i will have to flash signed PC10IMG. But i also found in the sticky thread there's a warning, not to flash signed PC10IMG if i have S-OFF. So before i can downgrade, i have to get the S-ON.
I've read in a thread :
If for some reason (sending phone for warranty or repair, etc) you want to go back to S-ON:
- If you got S-OFF by flashing an Engineering hBoot, download the official HTC RUU for your phone version and flash the stock firmware back again. S-ON will be restored. This forum contains many threads with official RUUs.
- If you got S-OFF with gfree, it saved a backup copy to your SD card called "part7backup-xxxxxxxxxx.bin". It can be flashed back from a terminal emulator or from an ADB shell:
"dd if=/wherever/your/part7backup-xxxxxxx.bin of=/dev/block/mmcblk0p7
The problem is, i got a secondhand unit without microSD card. How can I get S-ON? I don't know how (what method) my DZ got S-OFF at the first place.
Any help is much appreciated.
prazzo said:
Hi,
I've got my DZ a couple of days ago. It's a secondhand DZ. Previously i've used HTC Touch, Touch Dual, TP2, so this is my first Android experience. I did lots of ROM playing on previous winmo phones, but after reading for these couple of days of Android modding, i learn that flashing another Android ROM is not so simple as winmo ROM.
This is my DZ info:
Android version 2.2.1
Baseband version 12.28e.60.140fU_26.04.02.17_M2
Kernel version 2.6.32.21-g6e170e7
Build number 1.82.707.1 CL317545 release-keys
Software number 1.82.707.1
VISION PVT SHIP S-OFF
HBOOT - 0.85.0009
MICROP - 0425
RADIO - 26.04.02.17_M2
eMMC - boot
Dec 13 2010
I've check with root checker and Titanium Backup, it says NO root access.
I've learned that with 1.82, i will have to downgrade first to 1.34.
In the steps for downgrading, i found that i will have to flash signed PC10IMG. But i also found in the sticky thread there's a warning, not to flash signed PC10IMG if i have S-OFF. So before i can downgrade, i have to get the S-ON.
I've read in a thread :
If for some reason (sending phone for warranty or repair, etc) you want to go back to S-ON:
- If you got S-OFF by flashing an Engineering hBoot, download the official HTC RUU for your phone version and flash the stock firmware back again. S-ON will be restored. This forum contains many threads with official RUUs.
- If you got S-OFF with gfree, it saved a backup copy to your SD card called "part7backup-xxxxxxxxxx.bin". It can be flashed back from a terminal emulator or from an ADB shell:
"dd if=/wherever/your/part7backup-xxxxxxx.bin of=/dev/block/mmcblk0p7
The problem is, i got a secondhand unit without microSD card. How can I get S-ON? I don't know how (what method) my DZ got S-OFF at the first place.
Any help is much appreciated.
Click to expand...
Click to collapse
You are already S-OFF? I'd find it strange that you'd be S-OFF and not be rooted.
install rom manager and check if there has been a recovery already flashed. Might answer your question
Why do you want s-on? S-off is a good thing
Sent from my T-Mobile G2 using XDA Premium App
You can check if you got S-OFF or S-ON
by entering bootloader
Power off your phone, then, hold the volume down key and the power key.
You might need to disable fastboot
Spastic909 said:
install rom manager and check if there has been a recovery already flashed. Might answer your question
Why do you want s-on? S-off is a good thing
Sent from my T-Mobile G2 using XDA Premium App
Click to expand...
Click to collapse
I've already installed Rom manager and there's no clockwork recvery installed.
I want to flash custom rom. I need a root to do that. To get a root, i need to downgrade. To downgrade, i need to flash signed pc10img. And there's a warning here that said DONT flash pc10img with S-OFF. That's the problem.
Shinfang said:
You can check if you got S-OFF or S-ON
by entering bootloader
Power off your phone, then, hold the volume down key and the power key.
You might need to disable fastboot
Click to expand...
Click to collapse
I already did that. Bootloader says VISION PVT SHIP S-OFF. So that means i definitely have S-OFF.
I've learned some more from the post here and there. I think i figured out what happen with my DZ. I think the previous owner rooted and S-OFF the phone in the old firmware 1.34 then got an OTA update to 1.84. That update destroyed the root but somehow still S-OFF.
If I follow the direction in this thread, i assume that i can downgrade and root again. I will not need a goldcard to downgrade because currently i have S-OFF.
http://forum.xda-developers.com/showthread.php?t=905261
Am i right?
prazzo said:
I've learned some more from the post here and there. I think i figured out what happen with my DZ. I think the previous owner rooted and S-OFF the phone in the old firmware 1.34 then got an OTA update to 1.84. That update destroyed the root but somehow still S-OFF.
If I follow the direction in this thread, i assume that i can downgrade and root again. I will not need a goldcard to downgrade because currently i have S-OFF.
http://forum.xda-developers.com/showthread.php?t=905261
Am i right?
Click to expand...
Click to collapse
I am not sure whether it will work. But I am curious too.
I once upgrade via OTA and then I downgrade it following the instruction as per your link reference too. I rooted succesfully.
But, my DZ was S-ON.
Now you are in a different situation. You want to downgrade and root it but you already S-OFF.
Do you want to try it?
Cheers
silverwind said:
I am not sure whether it will work. But I am curious too.
I once upgrade via OTA and then I downgrade it following the instruction as per your link reference too. I rooted succesfully.
But, my DZ was S-ON.
Now you are in a different situation. You want to downgrade and root it but you already S-OFF.
Do you want to try it?
Cheers
Click to expand...
Click to collapse
I guess i have to try it.. will report after trying. Thnks all for the help..
Your theory on the previous owner having used the over the air update after rooting seems right to me. I've read more than a few times it will still show S-OFF but not be true S-OFF. Because you can't get S-OFF without root (well surely not on the newer 1.82's)
I'm not familiar with the 1.82 issues (why normal root methods fail on 1.82) but I wonder if temp root works, if you have radio S-OFF and temp root works it might be as simple as:
1. Obtain Temp Root (even Visionary could work)
2. Flash CWM Recovery (I'd use the flash_image method and not ROM Manager)
3. Reboot into CWM recovery
4. ...
5. Profit (Install a new pre-rooted ROM)
Of course this all depends on if temp root works with 1.82 and if your S-OFF is really S-OFF but it seems like a quick & easy thing to try.
I did it guys. It went smooth. Still needs goldcard though due to unmatched CID.
I'm on 1.34, rooted and S-OFF. Next find out ROM that i like most. Any recommendation? it has to be cool and fast..
So i figured that the warning "do not flash signed PC10IMG if you have S-OFF" is before we have the misc_version method. With misc_version "main is older" problem will never occur, provided misc_version done correctly.
Thank you all guys for your help and time especially for those guides starter. You guys are the ones who make this forum SO GREAT!
prazzo said:
I did it guys. It went smooth. Still needs goldcard though due to unmatched CID.
I'm on 1.34, rooted and S-OFF. Next find out ROM that i like most. Any recommendation? it has to be cool and fast..
So i figured that the warning "do not flash signed PC10IMG if you have S-OFF" is before we have the misc_version method. With misc_version "main is older" problem will never occur, provided misc_version done correctly.
Thank you all guys for your help and time especially for those guides starter. You guys are the ones who make this forum SO GREAT!
Click to expand...
Click to collapse
Congrats .
The first time I did after rooting was install ROM MANAGER premium version.
There a lot of rom to try with the easiest way..
Good luck
Hi everyone
I was advising somebody on rooting their Desire HD.
We got as far as installing the 1.32 stock ROM and I stupidly (and now I regret it so damn much) forgot about radio S-offing the device first so we tried Eng-S-Off. That said do not turn off the device because the bootloader is corrupt.
Then we tried the Radio S off tool and that said Unknown error, possibly connection.
How can we fix this?
EDIT: Will installing an RUU fix it?
raze599 said:
Hi everyone
I was advising somebody on rooting their Desire HD.
We got as far as installing the 1.32 stock ROM and I stupidly (and now I regret it so damn much) forgot about radio S-offing the device first so we tried Eng-S-Off. That said do not turn off the device because the bootloader is corrupt.
Then we tried the Radio S off tool and that said Unknown error, possibly connection.
How can we fix this?
EDIT: Will installing an RUU fix it?
Click to expand...
Click to collapse
Ya it will just do that way and do the rooting again after following these steps.....
find the stock splash screen here: http://forum.xda-developers.com/showthread.php?p=15430340&highlight=stock#post15430340
Uncompress that and put the .img file in the same folder as your fastboot file (in the Android SDK, it used to be in the Tools folder but nowadays they put it in the Platform-Tools folder), then open a CMD window, (Make sure the file is called splash1.img) and type:
fastboot flash splash1 splash1.img
That will restore the stock splash screen.
To restore the software you have to:
1: Find a 1.32.405.6 RUU that matches the original state of your phone. 2: Flash that RUU 3: Use Visionary R14 to Temproot and then Permroot 4: The Jkoljo's Easy Radio Tool to change the CID back to stock (If you phone was unbranded it will be HTC__001)
Now its ready to root again...
Hope that helps.
No I'm saying because the bootloader is corrupt, will installing an RUU restore the original bootloader?
There is no custom splash screen. We got as far as installing the 1.32 ROM.
raze599 said:
No I'm saying because the bootloader is corrupt, will installing an RUU restore the original bootloader?
There is no custom splash screen. We got as far as installing the 1.32 ROM.
Click to expand...
Click to collapse
I honestly think people are just copying and pasting stuff they've read somewhere without thinking about what they're saying. The bulk of that is nothing to do with the query you asked (apart from maybe the line about the RUU); I mean, replacing the splash image?! How's that going to help with a corrupted bootloader? Let alone telling you to download the full Android SDK just for that
On topic: the RUU should do it, but I've never tried it myself so you're probably safer waiting for someone with some actual experience to confirm before you flash. I have seen that error mentioned in one of the guides I used back when I rooted (January time), so I'll see if I can dig that out.
//sent from my Desire HD using Tapatalk; all errors entirely intentional.
---------- Post added at 08:07 AM ---------- Previous post was at 07:42 AM ----------
Okay, found it: a few people were having "bootloader corrupt" issues using the One-click ENG S-OFF tool.
Try the advice in that post (or maybe search that thread a bit further for mentions of "corrupt") before you waste time flashing a RUU. IIRC you can do Radio S-OFF & ENG S-OFF in any order (the ENG S-OFF tool has a box to tick whether you have Radio S-OFF or not); I don't think that's the problem here.
Thanks I will try that later. It seems like from the thread that if you didnt get a superuser message on the phone, nothing actually happened to the bootloader. We didnt get a superuser message on the phone. So could it be a false alarm and safe to reboot?
EDIT: By the way what the other user copied and pasted, I wrote originally lol but I didnt want to say that then in response.
raze599 said:
Thanks I will try that later. It seems like from the thread that if you didnt get a superuser message on the phone, nothing actually happened to the bootloader. We didnt get a superuser message on the phone. So could it be a false alarm and safe to reboot?
Click to expand...
Click to collapse
Yeah, that should be fine. If you didn't allow it root access when you ran it then it's not going to have been able to do anything. Reboot, clear the request in your superuser app and start again.
You don't mention it, but I assume you've already used Visionary to permroot before you tried the S-OFF tool? Just a thought when you mentioned you didn't get the su request on the phone.
raze599 said:
EDIT: By the way what the other user copied and pasted, I wrote originally lol but I didnt want to say that then in response.
Click to expand...
Click to collapse
Lol this is quite funny. I was actually instructing him over skype and then when I left Skype last night he did something and it worked lol THANK GOD!
I have no idea what he did but wierd things happen when I'm not looking lmao
Still though, since we have had some major problems, do you recommend that we install an RUU and start again from scratch? Just to avoid any future problems?
EDIT: Yes it was Permrooted, the superuser came up when he tried it himself and it worked.
I wouldn't bother personally; as long as you're s-off it doesn't matter how you got there. It's not like the phone's going to be left half s-on or something.
Besides, why let him waste time redoing that when he should be using that time to flash a load of new ROMs
//sent from my Desire HD using Tapatalk; all errors entirely intentional.
Thanks very much
I have an htc evo 4g 2.3.5 i wanted to downgrade it using this method http://forum.xda-developers.com/showthread.php?t=1473373 everything went well and i'm on the part where i use either revolutionary.io or unrevoked. I tried unrevoked but it kept saying it failed to push the recovery files, so i tried using revolutionary.io i downloaded it for windows but in the beta key screen it asks for my Hboot version. It has hboot 2.15.0001 and 2.16.0001 my hboot version is 2.10.0001 my understanding was that if i followed the instructions in the guide my hboot would be downgraded to one that i can root. Please help me! I have at least 4 hours into this and i don't want to give up. Am i suppose to pick one of these hboots? Please help.
Any help at all would be appreciated.
dave198803 said:
I have an htc evo 4g 2.3.5 i wanted to downgrade it using this method http://forum.xda-developers.com/showthread.php?t=1473373 everything went well and i'm on the part where i use either revolutionary.io or unrevoked. I tried unrevoked but it kept saying it failed to push the recovery files, so i tried using revolutionary.io i downloaded it for windows but in the beta key screen it asks for my Hboot version. It has hboot 2.15.0001 and 2.16.0001 my hboot version is 2.10.0001 my understanding was that if i followed the instructions in the guide my hboot would be downgraded to one that i can root. Please help me! I have at least 4 hours into this and i don't want to give up. Am i suppose to pick one of these hboots? Please help.
Click to expand...
Click to collapse
If you don't have the right hboot, run an RUU that will take you to the 2.15.0001/2.16.0001 hboot and then root from there using revolutionary
CNexus said:
If you don't have the right hboot, run an RUU that will take you to the 2.15.0001/2.16.0001 hboot and then root from there using revolutionary
Click to expand...
Click to collapse
I'm sorry i'm still a noob sorta. What is a RUU and how exactly do i run it? I don't have clockworkmod or any other recovery installed and can't install custom zips. How would i go about doing this?
dave198803 said:
I'm sorry i'm still a noob sorta. What is a RUU and how exactly do i run it? I don't have clockworkmod or any other recovery installed and can't install custom zips. How would i go about doing this?
Click to expand...
Click to collapse
No problem, I was once in your position
Ok so an RUU is just the acronym for a Rom Update Utility. These are usually exe's that you can run to update the firmware on your phone. People who root their phones also use this to return their phone to factory conditions (it wipes all data and installs the manufacturers OS, wiping any custom ROM that is on the phone, thats how it differs from just doing a factory reset as a factory reset just wipes all app data)
RUU's are self-contained so all you need to do is plug in your device and follow the prompts in the exe.
Now to do what I told you, go to (on your phone) Settings > About phone > Software info > Firmware number / Software number, then look up "supersonic RUU's" to find the RUU's for the EVO 4G, and use the first one that has a higher number than yours (for example, if your phone says 3.30.651.3 then you would take the next one up, 4.24.651.1, and not 4.53.651.1). Then go into bootloader and see if the hboot version is supported by the rooting method you are using.
EDIT: Supersonic RUU's here -> http://forums.team-nocturnal.com/showthread.php/1010-RUU-EVO-4G-SuperSonic-RUU-s
CNexus said:
No problem, I was once in your position
Ok so an RUU is just the acronym for a Rom Update Utility. These are usually exe's that you can run to update the firmware on your phone. People who root their phones also use this to return their phone to factory conditions (it wipes all data and installs the manufacturers OS, wiping any custom ROM that is on the phone, thats how it differs from just doing a factory reset as a factory reset just wipes all app data)
RUU's are self-contained so all you need to do is plug in your device and follow the prompts in the exe.
Now to do what I told you, go to (on your phone) Settings > About phone > Software info > Firmware number / Software number, then look up "supersonic RUU's" to find the RUU's for the EVO 4G, and use the first one that has a higher number than yours (for example, if your phone says 3.30.651.3 then you would take the next one up, 4.24.651.1, and not 4.53.651.1). Then go into bootloader and see if the hboot version is supported by the rooting method you are using.
EDIT: Supersonic RUU's here -> http://forums.team-nocturnal.com/showthread.php/1010-RUU-EVO-4G-SuperSonic-RUU-s
Click to expand...
Click to collapse
Thank you cnexus I will give this a try and see if it works.
Thank you CNexus it worked like a charm!
dave198803 said:
Thank you CNexus it worked like a charm!
Click to expand...
Click to collapse
Noooo problem, I'm glad it fixed the problem for you
By the way, edit your thread title please so anyone else with the same problems reads through this too
Make it something like "[SOLVED] Upgrading hboot version"