Phone won't load recovery -
My phone currently has 2.3.3 and will not root because the firmware is too "new" according to Unrevoked.
How do I backtrack to 2.2?
Also, the phone is not rooted (s-on) and recovery once again will not load properly; i get the red exclamation.
Any help would be greatly appreciated, thank you.
There are a few threads addressing this issue already, and the short answer from what I have found in my research, because I too took the OTA update and have looked in to this myself, is that there is no option.
If you are S-ON and have the new Bootloader and newest OTA update, you just have to hang tight until the devs behind Unrevoked or other such methods figure out a workaround for the newest bootloader.
denxnis said:
Phone won't load recovery -
My phone currently has 2.3.3 and will not root because the firmware is too "new" according to Unrevoked.
How do I backtrack to 2.2?
Also, the phone is not rooted (s-on) and recovery once again will not load properly; i get the red exclamation.
Any help would be greatly appreciated, thank you.
Click to expand...
Click to collapse
Hey man, I am sorry to inform you that there is currently no root method for the software you're on. You can't downgrade to 2.2, the RUU won't let you do it. The new bootloader that you're on is not downgradeable, and it is still currently locked. Hopefully a new exploit is figured out soon, but for now you just need to wait it out. Or trade your Evo with someone who still has froyo!
Thanks for the info guys.
Not sure is any of this could render your phone without functionality and If you are willing to give it a shot, try the first part of my post. After I unrooted the defective EVO to accept the OTA (since it was going back in a day anyway and didn't care if the root was lost) adn it was along with my .76 Hboot. I was able to get root back by using the HBOOT in stock recovery and loading the RUU posted with of course loading the usb drivers. Now, to be honest, I never used unrevoked to begin with on that EVO, so never checked son/soff before.
If for some glorious reason you are able to load the ruu and it comes up...try the root option also posted from the link to xHausx.
Here's hoping....but reality will probably set in and a short wait is needed for a real method.
http://forum.xda-developers.com/showthread.php?p=14496385#post14496385
unfortunately no root for 2.3 but rumor has it that htc is working on unlocking the new bootloader with a update coming in the near future prob 2.3.4
Hey!
I have problems downgrading to 2.2, since I dont like the new update at all. Alot of bugs and etc.
So I've tried installing the RUU from the computer, also renaming the file to PB99IMG.zip and putting it into the memory card.
Ive done this a thousand times when unrooting but now I get the error that my bootloader is up to date or something like that, I don't really remember.
Anyone who can help me ?
Thanks
EDIT: I get the error 140 bootloader error
Edit: It appears you can now unlock the bootloader and gain root access
Sent from my HTC Desire using XDA App
Is it possibly to root my phone and flash in a rom, and then unroot the phone to 2.2 froyo like I've always used to?
Understand that the hboot is locked with it locked you cannot do anything untill someone or team alpha and unrevoked come up with something that can..
Damnit, the damn 2.3 update sucks. Well then I have to wait then, I regret updating. I should have stayed on the 2.2.
2.3 update has just been unlocked using revolutionary!
yeah but i dont know the meaning of that.. im not used to s-off and i dont wanna brick my phone..
But if someone could do a quick guide for me for this s-off thing, and how to go back to the standard 2.2 froyo without s-off and root. By that I mean, that the phone is back to it's standard after doing this revolutionary.
Thanks
Ok, a few users here have offered advice/assistance, but I fear this problem has been forgotten.
I am stuck with an S-ON, 2.3.4 Droid Incredible, and am looking for a way to acquire root again.
This happened a few weeks ago, with the leak of the 2.3.4 OTA. Flashed S-ON via CWM (not aware I would permanently lose Root), then flashed the OTA as PB31IMG.zip in HBOOT.
Now, Unrevoked no longer roots the device. HBOOT will not allow downgrading to a 2.2 IMG, nor will it flash any downgraded Radio/HBOOT versions. I've tried them all from Dougpiston.com, even the signed ones.
I've attempted to contact the folks at Unrevoked about this issue on IRC, but I can't ever get a reliable dialogue going with anyone, and I believe they are busy working on Revolution, for Incredible 2/S & Newer devices.
Throwing my hands up, I even called Verizon, gave them an excuse to send me a replacement, just so I could start fresh with a 2.2 phone, but I am out of warranty.
I really want to enjoy Sense 3.0/MIUI, even Cyanogenmod, but the outlook is not so good.
Is there any solution I haven't tried yet? Please help.
Unless Unrevoked or someone else finds a new root method you're pretty much out of luck.
Sent from my Droid Incredible 3D using XDA App
Yep, same situation here, nothing will re-root if you did the GB OTA with S-ON bootloader. just have to wait and see if somebody comes up with something new or Unrevoked comes up with a new method.
EDIT: and I'm willing to bet if you get one from Verizon it might already be 2.3.4
resyek83 said:
Yep, same situation here, nothing will re-root if you did the GB OTA with S-ON bootloader. just have to wait and see if somebody comes up with something new or Unrevoked comes up with a new method.
EDIT: and I'm willing to bet if you get one from Verizon it might already be 2.3.4
Click to expand...
Click to collapse
That's most likely true. 2.3.4 is being pushed out to the Incredible now, so they would probably run the newest RUU on their Incredible devices.
I feel your pain deadsoulboy, and I've seen your posts lamenting your situation on other threads. Only solace I can offer you is that generally the source code and RUU are made available within 30 days of the OTA, at which point the developers are completely free to tear into them with reckless abandon and hopefully the folks at unrevoked figure things out.
It's also distinctly possible that HTC will unlock the bootloader the way it has with others of its handsets, in which case you'll be back in business.
Until then, my friend, I believe you are rootless.
i have the same problem. its been a couple months.... am i still hosed?
Have you tried this? http://forum.xda-developers.com/showthread.php?t=1306400
I used Scotty1223's instructions a few weeks ago and it worked like a charm.
So I burnt out my Cpu on my original rooted Dinc and got a replacement however after playing around on my replacement Dinc verizon pushed the update to 2.3.4 onto my phone. I would've stopped it but I figured I would just downgrade and root again however the new HBOOT 92 didn't let me downgrade i tried the unrevoked method anyway and i got a custom recovery so i restored MIUI on my current Dinc however i seem to still be unrooted? for example Titanium Backup can't delete system apps. i still have S-on and the new HBOOT 92 however i also have a mac so i am a little stuck and confused on how to regain full root access with s-off again any hep would be greatly appreciated.
alexyaz said:
So I burnt out my Cpu on my original rooted Dinc and got a replacement however after playing around on my replacement Dinc verizon pushed the update to 2.3.4 onto my phone. I would've stopped it but I figured I would just downgrade and root again however the new HBOOT 92 didn't let me downgrade i tried the unrevoked method anyway and i got a custom recovery so i restored MIUI on my current Dinc however i seem to still be unrooted? for example Titanium Backup can't delete system apps. i still have S-on and the new HBOOT 92 however i also have a mac so i am a little stuck and confused on how to regain full root access with s-off again any hep would be greatly appreciated.
Click to expand...
Click to collapse
Check this out. http://androidforums.com/incredible-all-things-root/427344-2-3-4-root-downgrade-s-off.html
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.