Related
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
Recently been looking into purchasing a new HTC One for myself, but after reading up on it, I see that there are a ton of S-Off and stock issues flying around. I guess I have a few clarifying questions then...
If I buy the phone today, is S-Off still possible?
Is S-Off risky?
Can I return to 100% complete stock yet if I need to or not? If yes, how?
Really I'm wondering if it's worth it to even purchase this phone as I don't want to be without flashing ROMs but at the same time, I resell my phones after awhile so I'm going to need to go back to 100% stock eventually. Sorry if these questions have already been asked, my xda search function is a bit broken. Thanks for reading this far.
Edit - Did some more searching and found the HTC One m8 now has the RUU's? Could someone also explain this? I'm new to HTC devices, coming from a nexus 5 here.
Nobody knows at all...?
Sent from my HTC M8
DinoSoup said:
Recently been looking into purchasing a new HTC One for myself, but after reading up on it, I see that there are a ton of S-Off and stock issues flying around. I guess I have a few clarifying questions then...
If I buy the phone today, is S-Off still possible?
Is S-Off risky?
Can I return to 100% complete stock yet if I need to or not? If yes, how?
Really I'm wondering if it's worth it to even purchase this phone as I don't want to be without flashing ROMs but at the same time, I resell my phones after awhile so I'm going to need to go back to 100% stock eventually. Sorry if these questions have already been asked, my xda search function is a bit broken. Thanks for reading this far.
Edit - Did some more searching and found the HTC One m8 now has the RUU's? Could someone also explain this? I'm new to HTC devices, coming from a nexus 5 here.
Click to expand...
Click to collapse
Probably, it will be. But it's not for certain. If your phone comes with the stock 1.12 software, then you can do it. But there's also a possibility of your phone being one of those unlucky "Whelp, this sucks..." phones. If it comes with the latest 1.57 software installed, it won't be possible.
That being said, if it comes with 1.12, which it probably will, and you unlock the bootloader, root, and S-Off, you can always go back to 100% stock with no trace at all of it ever being rooted if you want to return it for warranty, exc.
IF it is one of the unlucky "Whelp, this sucks..." phones, and you unlock your bootloader, root, and try to S-Off, but can't, then you can re lock the bootloader, run the stock RUU, and the only trace of it being unlocked and rooted would be that in the bootloader, it would say "Relocked" instead of "Locked."
Remember that if the phone comes with the 1.12 software, NEVER accept the OTA update. If you do accept the update, you will never be able to S-Off.
But again, chances are you will probably get the 1.12 software and be able to S-Off your phone. Hope this helped.
XxKINGxX2580 said:
Probably, it will be. But it's not for certain. If your phone comes with the stock 1.12 software, then you can do it. But there's also a possibility of your phone being one of those unlucky "Whelp, this sucks..." phones. If it comes with the latest 1.57 software installed, it won't be possible.
That being said, if it comes with 1.12, which it probably will, and you unlock the bootloader, root, and S-Off, you can always go back to 100% stock with no trace at all of it ever being rooted if you want to return it for warranty, exc.
IF it is one of the unlucky "Whelp, this sucks..." phones, and you unlock your bootloader, root, and try to S-Off, but can't, then you can re lock the bootloader, run the stock RUU, and the only trace of it being unlocked and rooted would be that in the bootloader, it would say "Relocked" instead of "Locked."
But again, chances are you will probably get the 1.12 software and be able to S-Off your phone. Hope this helped.
Click to expand...
Click to collapse
Thanks a ton, this is exactly what I was hoping for. Final question - how do I go about getting to stock. I found the RUU and stock files but I don't know at all what to do. After I know that, I'll be ready to root!
Sent from my HTC M8
DinoSoup said:
Thanks a ton, this is exactly what I was hoping for. Final question - how do I go about getting to stock. I found the RUU and stock files but I don't know at all what to do. After I know that, I'll be ready to root!
Sent from my HTC M8
Click to expand...
Click to collapse
Sorry for the late reply,
To get to complete 100% stock, you have to download and run the RUU. It's a simple EXE file. There are a bunch of Youtube videos on how to run RUUs. Before running the RUU, you have to re-lock the bootloader. But, to go to 100% stock, you first have to to reset the tampered flag, LOCK, not re-lock the bootloader (there is a thread on how to make the bootloader say LOCKED, not Re-Locked) and then S-ON. After that, run the RUU file, and it will take you back to complete stock. Like you never unlocked the bootloader or rooted.
But, I would do everything except S-ON. If you go to S-ON and run the RUU, you will not be able to go back to S-Off again. The RUU will install the 1.57 software, and that version isn't supported by Firewater.
The only thing you really have to do is a simple re-lock of the bootloader before running the RUU. But, doing what I said would make the phone look like it was never rooted. Again, I would do everything I said except going back to S-ON.
I just successfully achieved completely stock with S-On. I gave my details here: http://forum.xda-developers.com/showpost.php?p=55374644&postcount=2
So I have totally been off the scene for quite sometime and now finding the time and interest to be involved in this again, but where to start really? I feel so lost and out of the loop. Read through a lot of the posts and done my research for root and s-off. After reading I see that 4.4.3 has been causing some issues. I have my Verizon M8 running Stock. No root. 4.4.3. Where the heck do i begin?
What do I need to do for root since Weaksauce no longer works?
How do I gain root access and what programs am I needing that are up to date and functioning properly.
S-off? Firewater? Understand I need temp root, but I want permanent root.
Interested in TWRP for sure for custom recovery and flashing.
Can I get some help for a returning lost person? I wanna know exactly what programs I am going to need that are up to date. I want to flash custom roms etc of course (already have one in mind) but would like to know what the best android L themed one would be.
Looking forward to hearing from you guys. Thanks for the help and time you took to read this.
You don't need S-OFF necessarily, but you either have to unlock your bootloader on htcdev site, or use Sunshine to unlock and S-OFF for 25 bucks.
Those are your 2 options.
Then you can flash custom recovery and ROOT.
Hello everyone,
I was hoping someone here can help point me in the right direction. I am trying to downgrade my stock t-mobile one m8 from lollipop back to kitkat. I have been very unimpressed with lollipop on this phone, as it has significantly hurt the experience of my phone. While I like some things, the loss of lock screen widgets to be replaced by notifications was a pretty big blow to me. While I could almost like the new notifications, I do not like how I constantly have my wifi calling notification on my lock screen. Sure I could disable it, but then it's disabled when my phone is unlocked too, and I do like to know if wifi calling is on and working. Same goes for things like Pandora.
I could almost live with that, but then HTC decided to remove Zoe video creation out of the gallery and made it standalone. Now it's a watered down version of itself, that forces me to have to upload my vids to htc before I can even save a copy of my own locally generated content. :/ That is some major BS. So, the last gallery app to have zoe vids built in, is only for kitkat. That pretty much sealed the deal for me to go back.
I have done some research, and I have downloaded the RUU that would take me back to 4.4.4. Only problem is my hboot is now newer, so the RUU fails with error 140. I see mention of having to s-off my phone to unlock the bootloader, to downgrade it, but I haven't found any explicit instructions for the m8 on t-mo.
Is this the best way to accomplish what I want? Can someone please point me in the right direction? I've been searching, but I'm still unsure what is going to be needed. I may be ok with staying with lollipop, if I can get the older version of gallery working on it. Anyone know if that's been done?
Thanks in advance!!
Running a previous RUU ("downgrade") is in fact only possible with S-off, as it seems you have already figured out.
S-off by sunshine ($25 US). Its an APK, and self-explanatory. You don't need any more additional guide.
You only need s-off to run a previous RUU ("downgrade"). Unlocked bootloader is not necessary. Although if you choose to pay for sunshine, you might research bootloader unlock and what that means, and see if you want it (since sunshine can also unlock the bootloader).
http://theroot.ninja/
I ran sunshine to see if my device would at least pass the pre-test. Says I need to pre-root my phone. Is there a preferred method to use? I see most of the methods require unlocking the bootloader, but doesn't sunshine take care of that if I want? I really just need temp root to get this to s-off, and then run the RUU. I do not really want to root it after I get this back to 4.4.4, unless I really need to to be able to install the older gallery app, or prevent an auto update to lollipop or something.
Thanks again!
I'm actually not that familiar with the details of sunshine, since I did s-off long ago using the (no longer working) firewater method. I do know there used to be a temp root option in sunshine. But Android 4.4.4 and 5.0 s-off was just added to sunshine version 3.x a few weeks ago. It seems HTC had patched the previous sunshine (version 2.x) exploit, so I'm guessing they patched the temp root as well. So since its asking for the phone to be rooted already, I gather from this that the temp root method does not work for those Android versions.
If that is the case, my previous statement that you don't need to unlock the bootloader is not completely correct (for your Android version). As the only way to root then would be to unlock the bootloader via HTCDev.com; than root by a few different methods (install TWRP and flash SU/SuperSU is probably the most straight-forward).
But perhaps some folks more familiar with the most up-to-date sunshine info can chime in and confirm.