Hey guys. A while ago I was trying to use the gfree method to unlock my sim (I had S-OFF) but I realized I had to downgrade my radio. Stupidly, I tried to flash the official RUU (RADIO-26.03.02.18_M3).
Half way through, I got an error (forgot what cause I wasn't paying much attention -_- ) and had to abort. After that, the phone would not go past the HTC screen. I go into bootloader and the phone was now S-ON and had the radio version 26.03.02.18_M3.
No matter which rom I flash the same thing happens. On another note, I can get into Bootloader and clockwork recovery and ADB works as well.
Anyone know what to do from here? Sorry for being stupid but i`m not the brightest at this
Sounds like you may wiped your boot and system partitions doing this. Did you have a nandroid backup to restore? You can try flashing the PC10IMG again to see if it works this time (risk of losing recovery) or try flashing a custom kernel in addition to the rom.
Kind Regards,
Kevin
Ok here it is, My son Never go s-off and we somehow got a ROM to install, Magnolia_2_0_Final, this one. Now he had revolutionary on it and unlocked. The fun part is, now he can't get into recovery, it just goes to a white HTC screen. We have tried to relock the phone and go back, and tried to do all the tricks of the forums, we are still stuck. I would like for some detailed instructions on how we can get this back if at all. If you could help that would great. Thanks.
It will help if we had more detail on what you exactly have done and how you are doing it.
First with the phone on go to your settings. Look under "POWER" setting and disable fastboot.
Then I recommend pulling battery and reinsert battery. Hold volume down and power button to access hboot. The go to recovery through that.
If you have root access the down load Rom manager from market place and make sure you have recovery installed. If not download and flash from Rom manager. From the Rom manager app you can reboot into recovery.
Sent from my ADR6350 using xda premium
Recovery
We we have got into recovery and all is ok. We have updated SU and Clockworks. We are running Magnolia 2.0 *Sense 3.5, Android 2.3.5, Tweaks*, S-ON. The weird part is I have no idea how we got the rom on without S-OFF, but here we are. Now we have tried to just install the PH32IMG file and have had no luck with that. No matter what we have tried, all we get to is a loop of the boot screen.
Wait, did you unlock via HTC Unlock first? Either way, unzip the ROM zip, pull the boot image from it and follow the instructions in guide 6 in my sig to flash it in fastboot.
HTC Unlock
Yes we have it unlocked though HTC Unlock and still S-ON with the ROM. Now we just need to either be able to go back and get S-OFF so we can move forward. The problem is if we try to flash the zip from CWM, it doesn't work.
So you're going to need to go to htcdev.com and relock your bootloader. Then, follow attn1's guide to downgrade to 2.3.3, then run revolutionary. You can find guides for all of this online.
Won't turn back on after I relock it
The phone stays at the HBOOT screen and wont reset so I can't use adb devices at all because it won't see that it is plugged in. what do I do?
Coming from 2.3.5
Oh and I'm also coming from 2.3.5 if that makes any difference
I think you're gonna have to go back to S-ON a diff way. There's a thread in the general section on how. Follow it and then revolutionary s-off.
All Ideas have FAILED so far
Ok here it is, My son Never go s-off and we somehow got a ROM to install, Magnolia_2_0_Final, this one. Now he had revolutionary on it and unlocked. The fun part is, now he can't get into recovery, it just goes to a white HTC screen. We have tried to relock the phone and go back, and tried to do all the tricks of the forums, we are still stuck. I would like for some detailed instructions on how we can get this back if at all.
This is what I said to begin with. Now I thank anyone who could help in this situation. We can get into recovery, we have a rom with 2.3.5 sence 3.5, s-on, CWM, and we have tried all of the ideas so far. We need to know is there a better solution getting this phone back to stock and s-off.
Hi all,
So long story short, I lost my Sensation in Thailand and am holding off buying a new phone until the One XL is released. In the mean time, I'm trying to recondition my Desire. It is rooted, but doesn't have S-Off. It is running HBoot 0.80.0000.
I want to flash a Data++ Hboot, as the low storage space warnings used to drive me crazy!
I want to use Revolutionary to obtain S-Off. but it only supports HBoot 0.93.0001 and upwards. I have no idea how to update my HBoot without having S-Off.
Tried the alpharev iso method, (which doesn't seem to care about the HBoot version) but it fails at step 3 (seems to boot loop). Thankfully it didn't brick!
So my question is:
How can I get S-Off?
Cheers.
Did you tried to flash the official 2.3 GB and then S-OFF?
It should change your hboot to 1.02.0001.
k3lcior said:
Did you tried to flash the official 2.3 GB and then S-OFF?
It should change your hboot to 1.02.0001.
Click to expand...
Click to collapse
This seems like the most logical answer.
Download this http://www.htcdev.com/process/legal_download/152
Then use revolutionary.
You'll only need the Data++ HBoot if the ROM you intend to use requires it. Make sure you pick the ROM you want first and flash the HBoot that applies to it, otherwise you'll have to flash downgrade and flash new Hboot all over again, making more work for yourself.
Thanks for the feedback all.
Ended up having to give up cos the phone keeps randomly boot looping. Sometimes it will boot, other times it reboots as soon as sense loads and then goes into a reboot loop.
I somehow managed to flash a stock ROM and remove root, yet it still randomly boot loops, so I'm suspecting it's hardware related, which totally sucks!
Would you agree with this assessment? If not, what else could be causing it to randomly reboot?
Cheers!
Try underclocking the phone's CPU and try it again. Also, try flashing to Cyanogenmod 7.1 ROM, run that on my Desire and I have no stability issues, unlike older ROMs.
stephendt0 said:
Try underclocking the phone's CPU and try it again. Also, try flashing to Cyanogenmod 7.1 ROM, run that on my Desire and I have no stability issues, unlike older ROMs.
Click to expand...
Click to collapse
Doubt it'd help. Boot cycling happens outside of the actual ROM.
An update on the S-Off process...
I successfully flashed the Gingerbread ROM and then got S-Off using Revolutionary. I flashed the Data++ HBoot and then flashed Leedroid HD v3.3.3-R5 Data++ build. Worked first boot and I was able to install a few apps and work the phone. Rebooted to see what would happen and then got boot loops (sometimes got as far as displaying the unlock screen before restarting but often rebooted whilst displaying the custom Leedroid boot animation).
Seems If I leave it off for a while it will successfully boot off a cold start, but once it's been on a while it boot loops. Overheating CPU??
If this is not hardware related, I'm out of troubleshooting ideas...
At this point, the phone is well and truly out of warranty, so I'm happy to tinker with it. Would it be worth taking it apart? Is it possible to add thermal paste to the CPU?
Would love some suggestions!
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.
I'm to this point and I do have some back ups but I wanted to know if I can acheive s-off where I'm at or do I need to go back to stock? Forgot to mentioned I'm unlocked and when I relocked while running a custom rom I got security warning so I quickly unlocked and it didn't seem to hurt anything I'm aware of.
farcus211 said:
I'm to this point and I do have some back ups but I wanted to know if I can acheive s-off where I'm at or do I need to go back to stock? Forgot to mentioned I'm unlocked and when I relocked while running a custom rom I got security warning so I quickly unlocked and it didn't seem to hurt anything I'm aware of.
Click to expand...
Click to collapse
theres many, many
threads about s-off.
please take a look for them, and also give some more information.
from what you say, you have recovery, at this point I have no idea the hboot you have, or anything or that matter.
so even if I wanted to help you, I can't.
hboot .98 and I didnt get s-off from the start because I couldn't get the downgrade tool to work at all and I searched for a week to find someone having the same issues as I was having with the model I have 6.01.605.05. I did find some people having the same issue when I would run the downgrade it would say failed 43 error and version older then the one I'm currently running. Which I new that. so I unlocked the phone and tried to install clockworkmod 5.0.2.0 using fastboot so I could get root and it would not take it. So I kept looking for a recovery that would work and found 4ext recovery used fastboot and it loaded and I backed up and installed superuser. Being unlocked I installed Aokp in recovery and Gapps and flashed boot.img and rebooted. I found a method to acheive s-off with tacroot and it didnt go very well.
There is a whole thread in general area for downgrading your software version. Start here
http://forum.xda-developers.com/showthread.php?t=1685387