Related
I just rooted my HTC Desire using unrEVOked 3.21. Everything was fine. I had superuser permission and so on.
Than i had a sudden reboots. After reboot the N1 gallery crashed. N1 gallery might have cause the reboots. So i remove it and everything is fine till now.
I wanted to load a custom rom. I boot in to bootloader and notice that its s-on.
My question is can I load custom roms with s-on. How come I'm s-on and I have root access. If everything is fine, than what does this s-on do. I'm new at all this, so please bare with me.
Thank you.
harvin23 said:
I just rooted my HTC Desire using unrEVOked 3.21. Everything was fine. I had superuser permission and so on.
Than i had a sudden reboots. After reboot the N1 gallery crashed. N1 gallery might have cause the reboots. So i remove it and everything is fine till now.
I wanted to load a custom rom. I boot in to bootloader and notice that its s-on.
My question is can I load custom roms with s-on. How come I'm s-on and I have root access. If everything is fine, than what does this s-on do. I'm new at all this, so please bare with me.
Thank you.
Click to expand...
Click to collapse
S-Off = Full root ( Not really necessary unless you want to write to system and stuff while in Android. you can also change your splash screen if you would like)
S-On with root by unrevoked = Flash custom roms, radios, kernels, etc..
S-On is Sercurity On which means that the System files are only Read-Only.
S-Off uses AlphaRev's Hboot as this removes S-On. Its the Only way to get S-Off. I just S-Offed myself yesterday. It was scary at first but i really think its a good thing as you can use Metamorph/NinjaMorph or stuff.
I'd recommend just keep this information and when you get used to clockworkmod recovery then S-Off.
Remember that to get into recovery you must boot into Bootloader then scroll to Recovery with the volume up and down buttons then press the power down.
Oh, and to scroll between the clockworkmod menu, just use the trackpad. I also would not ecommend using Rom Manager as i remember the first time i used it and booted into recovery i was scqred to death as it brought me to a attention thing. I was scared to death.
Have Fun
shockem said:
S-Off = Full root ( Not really necessary unless you want to write to system and stuff while in Android. you can also change your splash screen if you would like)
S-On with root by unrevoked = Flash custom roms, radios, kernels, etc..
S-On is Sercurity On which means that the System files are only Read-Only.
S-Off uses AlphaRev's Hboot as this removes S-On. Its the Only way to get S-Off. I just S-Offed myself yesterday. It was scary at first but i really think its a good thing as you can use Metamorph/NinjaMorph or stuff.
I'd recommend just keep this information and when you get used to clockworkmod recovery then S-Off.
Remember that to get into recovery you must boot into Bootloader then scroll to Recovery with the volume up and down buttons then press the power down.
Oh, and to scroll between the clockworkmod menu, just use the trackpad. I also would not ecommend using Rom Manager as i remember the first time i used it and booted into recovery i was scqred to death as it brought me to a attention thing. I was scared to death.
Have Fun
Click to expand...
Click to collapse
Thank you so much.. That was really usefull information bro... you mention that my system files are read only with unrEVOked... yday i used root explorer to change some system files... could that be the cause my device rebooted...
another thing i want to know is that i want to install busybox.. do i need s-off to do this... if i ever hard/soft reset will the busybox also be removed...
and i also removed some stock applications... will they also be reinstalled if i reset my HTC desire...
You dont need S-OFF to install busybox. Dont worry about S-OFF. Most power users dont need it. It's more a liability.
Stock apps may be reinstalled with choosing to install a ROM which includes them. Most ROMS have addon files with stock apps. Or you may choose and pick from a ROM Kitchen.
harvin23 said:
Thank you so much.. That was really usefull information bro... you mention that my system files are read only with unrEVOked... yday i used root explorer to change some system files... could that be the cause my device rebooted...
another thing i want to know is that i want to install busybox.. do i need s-off to do this... if i ever hard/soft reset will the busybox also be removed...
and i also removed some stock applications... will they also be reinstalled if i reset my HTC desire...
Click to expand...
Click to collapse
No problem Last time when i rooted without S-Off, i tried copying things around the system folders and it never worked. That might and should have been the cause of your reboots. The rest of it has been answered by Droidzone
thanks guys for all the information... i just download a new custom rom and was going to flash it... but there is something bothering me... its the radio... the custom rom has different radio... will the radio change once i install the custom... is there any complications...
what is the things i need to consider before flashing a rom... im really sorry guys but this phone cost RM2000 (Malaysian Ringgit)... i dont want screw it... just taking precautions...
thanks for all the help guys...
harvin23 said:
thanks guys for all the information... i just download a new custom rom and was going to flash it... but there is something bothering me... its the radio... the custom rom has different radio... will the radio change once i install the custom... is there any complications...
what is the things i need to consider before flashing a rom... im really sorry guys but this phone cost RM2000 (Malaysian Ringgit)... i dont want screw it... just taking precautions...
thanks for all the help guys...
Click to expand...
Click to collapse
Flashing a ROM is not a big deal. If something happens to go wrong, you can always revert to the Nandroid restore. Custom ROMs often come with different Radios. Just install whichever Radio the developer recommends, and it should go smoothly.
At times a ROM may have different Radios for different functions. Like, if you want the phone running faster, use one radio. If you want more battery life, use another and so on.
If you've already rooted, flashing a new ROM wont create any more trouble than you're already in. Just dont be that hasty to do S-OFF. It's S-OFF that often leads to softbricks (usually).
droidzone said:
Flashing a ROM is not a big deal. If something happens to go wrong, you can always revert to the Nandroid restore. Custom ROMs often come with different Radios. Just install whichever Radio the developer recommends, and it should go smoothly.
At times a ROM may have different Radios for different functions. Like, if you want the phone running faster, use one radio. If you want more battery life, use another and so on.
If you've already rooted, flashing a new ROM wont create any more trouble than you're already in. Just dont be that hasty to do S-OFF. It's S-OFF that often leads to softbricks (usually).
Click to expand...
Click to collapse
^^
but ussually i dont really do nandroid restore's because i keep lots of Roms for backup in case one does go wrong. Its best to do both
I tried flashing the custom splash via fastboot at first, and the transfer went through. However, the splash screen is the same. I flashed it as evosplash1.rgb565. So then I continued to look at other ways, and found this. I used unrevoked to root. I used forever to root the first time, and I can't remember what I used for my 2nd evo. It appears I used unrevoked 3 (which doesn't enable s-off?) but I think I still had the unrevoked program laying around so it should have been forever.
I looked around a bit and found out the unrevoked users can do it using this method, which seems very simple:
Here is how i do it:
I create an unsigned zip to be flashed.
Im Fully rooted, NAND Unlocked, and S-Off
via unrEVOked 3.21
1) Download Unrevoked Forever's custom splash screen PC36IMG.zip
2) Open the zip and delete the splash1.img
3) Download the custom splash screen you like and rename it: splash1.img
4) put the file in PC36IMG.zip
5) put the Zip on the root of your SD Card.
6) Power Down your phone.
7) Boot your phone into HBOOT (hold down "volume down" and press the power button)
8) Your phone will automatically find the zip and ask if you want to apply it.
9) Press "Volume Up" for yes
10) It will ask to reboot. Press "Volume Up" for yes.
11) your phone reboots, and you see the new Splash Screen.
Downlaoded their custom splash PC36IMG and put the splash of my choice in there as splash1.img. When I boot into fastboot, it checks the PC36IMG file, but then returns to the previous screen (bootloader?) without doing anything. I am not messing up any of these easy steps.
Click to expand...
Click to collapse
I even tried putting unrevoked's defualt splash screen PC36IMG file on the root of my sdcard, without adding my own file into it. It still doesn't give me an option to apply update when I go into HBOOT, it just returns me to the bootloader after checking the PCIMG36 file for about a second.
Very frustrating! Any help would be appreciated, I have searched around for a couple hours now to no avail.
If it makes a difference, I have one of the older evo's.
-update:
When I load up the bootloader the top says:
SUPERSONIC EVT2-3 SHIP S-ON
HBOOT-0.97.0000
the radio is 2.15.00.09.01
I know there is a file on my sdcard from something and its called S-OFF so I figured it was.
Since apparently I'm not S-OFF (I think?), how would I manage that? Do I rerun unrevoked forever?
Kekoh said:
I tried flashing the custom splash via fastboot at first, and the transfer went through. However, the splash screen is the same. I flashed it as evosplash1.rgb565. So then I continued to look at other ways, and found this. I used unrevoked to root. I used forever to root the first time, and I can't remember what I used for my 2nd evo. It appears I used unrevoked 3 (which doesn't enable s-off?) but I think I still had the unrevoked program laying around so it should have been forever.
I looked around a bit and found out the unrevoked users can do it using this method, which seems very simple:
I even tried putting unrevoked's defualt splash screen PC36IMG file on the root of my sdcard, without adding my own file into it. It still doesn't give me an option to apply update when I go into HBOOT, it just returns me to the bootloader after checking the PCIMG36 file for about a second.
Very frustrating! Any help would be appreciated, I have searched around for a couple hours now to no avail.
If it makes a difference, I have one of the older evo's.
-update:
When I load up the bootloader the top says:
SUPERSONIC EVT2-3 SHIP S-ON
HBOOT-0.97.0000
the radio is 2.15.00.09.01
I know there is a file on my sdcard from something and its called S-OFF so I figured it was.
Since apparently I'm not S-OFF (I think?), how would I manage that? Do I rerun unrevoked forever?
Click to expand...
Click to collapse
You will not be able to flash anything until you get s-off (security clearence)
Looking at your hboot you dont have to use unrevoked but the old root method.
this one will work for you
http://forum.xda-developers.com/showthread.php?t=706411
hope this was helpful
I appreciate the help, but since I'm already rooted and running CM6, etc, this won't have any affect on it? Or on my current backups?
So you can get into recovery?
Sent from my PC36100 using XDA App
Yeah, I have clockworkmod installed, etc. I have flashed quite a few ROMs, but currently using CM. I can get into fastboot and stuff, but it's just not letting me apply update on any PC36IMG file, it reads it, but nothing.
Kekoh said:
Yeah, I have clockworkmod installed, etc. I have flashed quite a few ROMs, but currently using CM. I can get into fastboot and stuff, but it's just not letting me apply update on any PC36IMG file, it reads it, but nothing.
Click to expand...
Click to collapse
To be honest I am not even sure how you are flashing with out root access... may need to redo the steps you followed to get s-off status
Sent from my PC36100 using XDA App
I have root access, just not s-off, unless they are the same thing?
This is confusing as ****.
Ok so I just read in another thread that unrevoked forever will give me s-off.
Will I be fine to reroot/flash forever, even though I'm already rooted? Will it affect:
-Cyanogenmod?
-Persnal info/data/prog data?
-Clockworkmod recoveries? Or Clockworkmod in general?
Hi, I have posted this before but it got deleted because I very stupidly posted it in the wrong place.
My question has been answered before due to searching but no one else happens to be in my EXACT situation and I don't want to mess up my phone.
Basically my Desire HD is rooted etc and I want to flash the Android Revolution ROM, but I havent flashed any ROM's since my OLD G1 and now everyone talks about S-OFF etc and I don't understand these, on my G1 it was simply rooting and flashing a Recovery and then flashing a ROM, so basically what do I need to flash this ROM
My situation:
I am running the stock ROM (permroot on 1.32.405.6)
I have stock radio
I have Clockwork mod 3.0.0.6
and Buzz Sense 1.3 + OC (OC'd 1.6Ghz) kernel.
(+Ever since I downgraded from 1.72 I have lost wi-fi, it connected to my wi-fi but I get no internet access through it, its definitely a problem with the phone and nothing else because I have tested my router etc, all my other devices have connectivity through my router)
We all were in your exact situation. The Desire HD employs an extra level of security to prevent users messing with their handsets, S-ON.
You need to turn this off, Ideally ENG (Engineering) S-OFF, before you can make persistent changes to your system.
Have a read through the very helpful guides in the Dev section. They also contain the tools you need. Turning S-OFF should be a one time process only, i.e once you've done it there is no need to repeat it to flash another ROM.
Hope that helps.
andyharney said:
We all were in your exact situation. The Desire HD employs an extra level of security to prevent users messing with their handsets, S-ON.
You need to turn this off, Ideally ENG (Engineering) S-OFF, before you can make persistent changes to your system.
Have a read through the very helpful guides in the Dev section. They also contain the tools you need. Turning S-OFF should be a one time process only, i.e once you've done it there is no need to repeat it to flash another ROM.
Hope that helps.
Click to expand...
Click to collapse
Sorry I forgot to mention that I have SHIP S-OFF and I'm unable to get ENG S-OFF because when I used the Easy S-OFF tool it can only give me SHIP S-OFF for some reason, I cant do anything now since its incompatible with my kernel as well. Can I flash a ROM with just SHIP S-OFF? I don't want to flash any radios because I bricked my G1 about 4 million times when flashing radios.
It you run a 1.32 WWE RUU and revert back to stock you can then reapply ENG S-OFF. A bit of a ball ache I know.
Most ROMs will work just fine with SHIP S-OFF but ENG is usually preferred.
To flash a radio you need Radio S-OFF another beast entirely. However there is a very good too to do it with. No bricks so far and your DHD will then have super CID and be SIM unlocked.
didge3 said:
Sorry I forgot to mention that I have SHIP S-OFF and I'm unable to get ENG S-OFF because when I used the Easy S-OFF tool it can only give me SHIP S-OFF for some reason, I cant do anything now since its incompatible with my kernel as well..
Click to expand...
Click to collapse
Just tick the "I have radio s-off" box and it becomes compatible with everything.
follow my guide in the sig and skip to eng s-off and radio s-off part, or skip to whatever comes next if you've already done them
Tried that, I get a "Connection Error", I have made sure its fully connected as "Disk Drive" and I allow the Super User request when I do it, but it still doesn't work, plus the radio tool just says "Incompatible kernel" - or something like that.
I mainly want to know, can I flash Android Revolution in my current situation, can I flash with just SHIP S-OFF and my current kernel, or do I have to go back to stock kernel, flash the ROM and then flash my kernel back?
and why should I have ENG S-OFF, if it makes a lot of difference I will give it ago, but I mainly want to just flash this ROM to see if it fixes my wifi issue and my camera doesn't drop so many frames! (known issue in 1.32, fixed in 1.7X)
Disk Drive. Yeah, read the guide again more carefully, mate... And change the tool, why are you using easy radio tool!? It won't give you ENG S-OFF. My ENG S-OFF tool will give you that. And it most definitely will not say incompatible kernel if you just tick the box I talked about.
You can flash ARHD now. Do not mess around with it's kernel after flashing, because it comes with the best kernel out there. The kernel has been made to fit ARHD's needs.
jkoljo said:
Disk Drive. Yeah, read the guide again more carefully, mate... And change the tool, why are you using easy radio tool!? It won't give you ENG S-OFF. My ENG S-OFF tool will give you that. And it most definitely will not say incompatible kernel if you just tick the box I talked about.
You can flash ARHD now. Do not mess around with it's kernel after flashing, because it comes with the best kernel out there. The kernel has been made to fit ARHD's needs.
Click to expand...
Click to collapse
I get the same as every other time, downloads the Easy S-OFF tool, "Pushing stuff to SD" Phone says "Unknown has been granted su access" and then the tool says "Error: Connection Problem!" - I get this every time, I have tried re-downloading this software every time, removing the "Unknown" in super user and then re-allowing it when it asks, I still get the same error...
Does it matter that I'm using Windows 7 64-bit?
EDIT: I think I've done it now, I downloaded the latest 2.3 SDK (I had 2.2) which updated my ADB drives, I didn't get the error this time, will boot into H-BOOT and check now.
Are you still using that disk drive mode? Because you should not.
THANKS
I have thanked everyones post, I can confirm my H-BOOT Now says PVT ENG S-OFF, one last thing, I'm all good to flash now? I can just put the ROM (sense version) on my SD card and flash it in CWM, with my current kernel, even though it will over write it with the one included for Android Revolution, I dont have to go back to stock kernel or anything first right?
Thanks again
Have you flashed ClockworkMod Recovery yet? If not download ROM Manager from the Market and flash it from there.
Once that is complete, download ROM, put on SD Card, Recovery, Wipe, Flash, Enjoy.
didge3 said:
Hi, I have posted this before but it got deleted because I very stupidly posted it in the wrong place.
My question has been answered before due to searching but no one else happens to be in my EXACT situation and I don't want to mess up my phone.
Basically my Desire HD is rooted etc and I want to flash the Android Revolution ROM, but I havent flashed any ROM's since my OLD G1 and now everyone talks about S-OFF etc and I don't understand these, on my G1 it was simply rooting and flashing a Recovery and then flashing a ROM, so basically what do I need to flash this ROM
My situation:
I am running the stock ROM (permroot on 1.32.405.6)
I have stock radio
I have Clockwork mod 3.0.0.6
and Buzz Sense 1.3 + OC (OC'd 1.6Ghz) kernel.
(+Ever since I downgraded from 1.72 I have lost wi-fi, it connected to my wi-fi but I get no internet access through it, its definitely a problem with the phone and nothing else because I have tested my router etc, all my other devices have connectivity through my router)
Click to expand...
Click to collapse
andyharney said:
Have you flashed ClockworkMod Recovery yet? If not download ROM Manager from the Market and flash it from there.
Once that is complete, download ROM, put on SD Card, Recovery, Wipe, Flash, Enjoy.
Click to expand...
Click to collapse
Note the very first post "Clockword mod 3.0.0.6" so in answer, yes.
Your good to go then, happy flashing.
I have seen some threads about un-rooting for warranty claims, but want a definite answer before doing anything.
My DHD has ENG S-OFF, Radio S-OFF and Clockwork Mod Recovery, and basically I want someone to be able to tell me/ point me in the direction of files and instructions for returning my handset to 1.32 stock with no superuser, custom recovery or s-off's of any kind.
Also, if the engineers where to update my phone like i know their prone to doing, is it still possible to downgrade back to 1.32 and root again to get my beloved MIUI back?
jamiegoldsworthy said:
I have seen some threads about un-rooting for warranty claims, but want a definite answer before doing anything.
My DHD has ENG S-OFF, Radio S-OFF and Clockwork Mod Recovery, and basically I want someone to be able to tell me/ point me in the direction of files and instructions for returning my handset to 1.32 stock with no superuser, custom recovery or s-off's of any kind.
Also, if the engineers where to update my phone like i know their prone to doing, is it still possible to downgrade back to 1.32 and root again to get my beloved MIUI back?
Click to expand...
Click to collapse
you can download a stock rom from the links on this thread:
http://forum.xda-developers.com/showthread.php?t=846248
And It'll take the HTC back to it's factory defaults, as if it was new. It'll probably be best to use the RUU (that's what it's called) for Orange UK (if your phone's locked to that, assuming you updated your operator)
HOWEVER! Running an OTA update to gingerbread from the new system'll leave you with a probably unrootable Desire HD (to check if it's still got the radio S-off at least, go into fastboot and check that the CID is just 1's)
hmohammed43 said:
you can download a stock rom from the links on this thread:
http://forum.xda-developers.com/showthread.php?t=846248
And It'll take the HTC back to it's factory defaults, as if it was new. It'll probably be best to use the RUU (that's what it's called) for Orange UK (if your phone's locked to that, assuming you updated your operator)
HOWEVER! Running an OTA update to gingerbread from the new system'll leave you with a probably unrootable Desire HD (to check if it's still got the radio S-off at least, go into fastboot and check that the CID is just 1's)
Click to expand...
Click to collapse
So I would install this like a ROM through Clockwork Mod?
So would this RUU remove all of my custom recovery, and S-OFF's? It's just I wanna make sure it's all gone just in case....
So there is no way that these can be downgraded like 1.72 can be?
Narh, you don't flash it through clockwork mod, it's run from your computer. You'll need the HTC Sync application installed on your computer, and a sense rom to connect the phone via htc sync.
When you run the RUU, it'll tell you what to do. I think it removes a ENG S-OFF but but a radio S-OFF'll stay on the phone (it is more or less permanent). However, I don't think the radio s-off'll show up in fastboot that obviously.
The reason you can't downgrade the firmware on RUUs is because in the process of rooting, the phone's CID changes to 111111111 (or something) so the PD98IMG file for downgrading will refuse to work with the phone because of an "Incorrect CID"
Sent from my Desire HD using XDA Premium App
hmohammed43 said:
Narh, you don't flash it through clockwork mod, it's run from your computer. You'll need the HTC Sync application installed on your computer, and a sense rom to connect the phone via htc sync.
When you run the RUU, it'll tell you what to do. I think it removes a ENG S-OFF but but a radio S-OFF'll stay on the phone (it is more or less permanent). However, I don't think the radio s-off'll show up in fastboot that obviously.
The reason you can't downgrade the firmware on RUUs is because in the process of rooting, the phone's CID changes to 111111111 (or something) so the PD98IMG file for downgrading will refuse to work with the phone because of an "Incorrect CID"
Sent from my Desire HD using XDA Premium App
Click to expand...
Click to collapse
So I need to flash a sense ROM, and then how do I use the RUU? Sorry if I'm a pain!
Right so i can't get rod of radio s-off :/ and if they upgraded my phone I can't root again? damn :/
jamiegoldsworthy said:
So I need to flash a sense ROM, and then how do I use the RUU? Sorry if I'm a pain!
Right so i can't get rod of radio s-off :/ and if they upgraded my phone I can't root again? damn :/
Click to expand...
Click to collapse
It's been a while since i had to use a RUU, but I believe it should work with any rom.
I am in desperate need of unrooting my phone now, but due to it being almost 2 years that I've owned this phone I can't remember how I rooted it in the beginning. Any way to figure this out?
Need to know your Hboot version and radio, and also is the phone S-ON or S-OFF (power off, then volume down and power buttons simultaeously).
HBOOT-2.18.0001
RADIO-2.15.00.12.19
Phone is S-OFF
Thanks for your help.
On a side note, my phone is in an infinite boot loop that only loads to the white evo screen, I can't flash custom recoveries, roms, or RUU. I think the problem is the fact that it says LOCKED in the pink label at the top of my bootloader. I tried using the command fastboot oem lock and it says it's already locked and doesn't unlock it or anything of the sort. If you know any way to aid my problem I thank you for the help.
Most infinite bootloops are never fixed, however;
The best advice that I can give you right now is to download these two files.
http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe
http://goo.im/stock/supersonic/ruu/...15.00.12.19_NV_2.33_release_234563_signed.exe
Connect your phone to your computer, then boot into your bootloader and click on FASTBOOT. The phone should be in FASTBOOT USB. Install the HTCDrivers exe file to your computer. Then try to run the RUU file with the phone still in FASTBOOT USB.
If that doesn't work, then the phone may already be permanently bricked. Interestingly, the phone was rooted nearly 2 years ago, but you have the latest everything. I hope you did not do that with OTA updates.
Thanks shortyydoggg, unfortunately I've tried that method with those exact files already and had no such luck. My last resort is that if I can change the LOCKED pink label to RELOCKED or UNLOCKED, I'll be able to flash through the bootloader again, and temporarily use my phone once more until i can get the EVO LTE. Also, there is basically no way to tell now which root method I used?
Yea, Unlocking the bootloader was going to be my other suggestion after trying the RUU. It's not much else you can do after that.
Sent from my PC36100 using xda premium
Ya the RUU unfortunately goes through successfully but then the phone restarts again. I can't help but feel this is all because my bootloader says LOCKED. The problem now is fastboot oem lock command doesn't work for me, and says the phone is locked and doesn't change the label to RELOCKED or anything else like it should? Do you know why this command isn't unlocking my bootloader or any other commands or ways to do this?
djs415 said:
Ya the RUU unfortunately goes through successfully but then the phone restarts again. I can't help but feel this is all because my bootloader says LOCKED. The problem now is fastboot oem lock command doesn't work for me, and says the phone is locked and doesn't change the label to RELOCKED or anything else like it should? Do you know why this command isn't unlocking my bootloader or any other commands or ways to do this?
Click to expand...
Click to collapse
That's the wrong command. You need to go to the htcdev site (www.htcdev.com), register, and unlock the bootloader. Since you're already S-OFF, have you tried running a PC36IMG file for a custom RECOVERY. You might not need to be unlocked to do that.
I'm almost positive I tried to flash a custom recovery through the bootloader and it didn't work... however, you were right and my bootloader is now unlocked so THANK YOU! Will post back after flashing the recovery you attached.
To answer your previous question about which root method you used, unrevoked-forever was used at some point to S-OFF the phone, since you are on Hboot 2.18 and still S-OFF and not on the old Engineering S-OFF Hboot. Whether the phone was rooted with Unrevoked, Toast Method 2, Simple Root or AutoRoot, there is no exact way to tell right now, but it can be guesstimated that it might have been Unrevoked.
Now for the confusion if you dare to read:
AutoRoot is Toast Method 1, unrevoked-forever, and a custom ROM inside a program, and Simple Root is Toast Method 1 and a custom ROM inside a program along with the engineering S-OFF bootloader. Unrevoked is uh, Unrevoked and Unrevoked forever inside a program. Toast method 2 is just a custom ROM flashed along with the same S-OFF bootloader as SimpleRoot. If you used Toast Method 2, then you did everything AutoRoot did in order to S-OFF the phone. You just needed unrevoked-forever to keep it S-OFF for any other and your bootloader. Toast Method 1 alone does not S-OFF the phone. If you used SimpleRoot, which does not use unrevoked-forever, you needed unrevoked-forever at some point again to keep the phone S-OFF on any other Hboot (your 2.18). So again, you would have done everything AutoRoot did.
So that brings it down to AutoRoot and Unrevoked, since everything else you did is the same thing that AutoRoot does. Since you rooted nearly 2 years ago, and Unrevoked-forever is inside AutoRoot, AutoRoot has to be newer than unrevoked-forever to contain it inside its program. Also Unrevoked is newer than AutoRoot and already contained Unrevoked-forever. So the likely-hood that you used Unrevoked is very great, but not for sure. It is also the easier method and the one that nearly everyone else used at that time.
Somehow, still no luck. Flashed that file you linked and it goes through successfully, asks to reboot and then back to white screen boot loop. How can this be possible at this point, with the bootloader unlocked it goes through with the process but the actual writing of the data seems to fail. Trying the RUU one last time now that it is unlocked, but if this doesn't work I'm stumped.
I thought the whole beauty of the the bootloader, and more importantly being able to reach it, was that it meant your phone couldn't be bricked. Last try, will report back.
Bootloader unlocked, RUU flashed this time through PC. Nothing, and completely out of ideas here.
Shortydoggs been doing a lot of help around here for similar situations. There have been cases (maybe a dozen I've seen) where people get into a situation like yours where bootloader is accessible , but that is about it. And from what I've read, in those cases, when the phone tries to boot, it does 4 or 5 short vibrates before going back to bootloader.
Your situation is also strange in that, you rooted 2yrs ago, but don't have S-off, a locked bootloader. Hboot 2.18, which is the latest but is unlockable thru HTC dev, but no S-off available for it yet. And your radios are latest, too (mostly irrelevant).
First there was toasts root for baseband 1.37 (which downgraded you to 1.17 with eng hboot to get s-off before bringing you back up to 1.37). Then there was simple root by jiqqaman, which worked for people who took the baseband 1.47 OTA. Then when froyo came out, anyone who took that OTA (baseband 3.25, or 3.26, I forget) had to wait for unrevoked to be developed. I think hboot at that point was 2.08 and 2.10. Unrevoked forever worked on that, and gave you S-off.
I know none of that info helps you necessarily. It's just puzzling how you rooted 2yrs ago, bit have the latest hboot with S-on. Maybe you didn't finish toasts part 2 S-off guide, then sometime recently updated your radio and hboot? No. You need S-off to flash radio. Were you recently on a stock rooted ROM and took an OTA (is that even possible) when you were still S-on (from not finishing toasts guide)?
Sorry, I know it's not a lot of help. Just trying to figure out how things could not match up so much, and if that's how you ended up in this situation (that could be helpful info for others). I hope you don't have the bootloop of death and can get it sorted. Between shortydogg and captain throwback, I HAVE seen some phones saved.
sent from 2yr old Evo on ICS
Yea, I'm not going to waste your time any further. There's not much else to do.
Ya unfortunately I'm quite confused myself... however, if this information helps you at all... For starters, I have S-OFF and until recently (2 weeks or so since my phone started acting up like this) I was running a ROM perfectly fine until one day it restarted into this never ending boot loop. I'm not sure how my HBOOT is the most up to date, seeing as I was always very careful not to do something stupid like change my HBOOT for no reason. The interesting thing is that I had never seen that pink label before on my bootloader saying unlocked or locked OOW until the problem started occuring 2 weeks ago.
Also something I'm realizing... are you telling me that the HBOOT I have does not have S-OFF yet, and therefore you can't flash roms or custom recoveries... but my bootloader still says I am S-OFF. So the problem is I am S-OFF for the most recent HBOOT which can't be changed to S-OFF yet? Could downgrading hboots work?
He did not realize that you were S-OFF. Your phone is set to stay S-OFF regardless of what Hboot you have or how that Hboot usually comes.
Also, your phone appears to have a hardware, and not software issue, so, changing Hboots, might not hurt to try, but may not help much. In case I'm wrong, do not try anything below Hboot 2.10. Here is one for 2.16.
What rom were you running up until the time the bootloops started happening? This sounds alot like the cyanogen mod bootloop of death which no one has ever fixed I believe.
I believe I was using some version of SOS or a sense rom, but I'm leaning more towards SOS.
Just tried using that HBOOT thought it's still not working. Would going to the engineering hboot make any difference?
What could be the hardware problem causing this?
I see that shortydogg is in here taking good care of you .
The bottom line is, if you can't flash/get into recovery from HBOOT, you're probably in an unrecoverable situation.
It's unclear after my review of the thread, but you have tried flashing a recovery through HBOOT using a PC36IMG.zip file, right? And then after flashing, you choose not to reboot, but to boot into Recovery?
If you can get into recovery, then we can resolve your issue (if in fact it is software related).
If the problem is bad NAND blocks on your recovery or boot partitions, then there's nothing that can be done.
Also, the watermark on your bootloader (LOCKED, UNLOCKED, etc) has nothing to do with your issue. That's just connected to the version you were running. As long as you're S-OFF, that's irrelevant.