OK, So after searching and Searching for a way to go back to complete stock after taking the latest 1.31 update and rooting my HTC One, and not being able to use any current RUU without having to gain S-off. I finally did it. I am 100% stock on an updated software version of 1.31.651.2.
So here is what I did and please feel free to step in and let me know if there was an easier way.
Step 1.
I unlocked my boot-loader to gain root privileges
Step 2.
I flashed TWRP
Step 3.
Created Nand Backup if something fails
Step 4.
I flashed SuperSU
OK, so that got me rooted. but I wanted to go back to stock after playing around with certain roms my phone started acting goofy.
this is the part where it gets a lil tricky.
in order for me to get back to stock on my One to the most current version of 1.31.651.2.
this is what I had done.I installed an app from the market called Rom toolbox lite(FREE) put REVONE in /data/local/temp
gained S-off. installed a stock RUU 1.29.651.7. Now the only problem is that I was S-off and my boot loader shows tampered and unlocked.so I used revone to remove tampered with the -t command and also wanted to lock the boot loader with the -l command. in order to get s-on. booted into the boot loader and selected fastboot and entered fastboot command, fastboot oem writesecureflag 3 to regain s-on.
ok so I am still technically rooted so in order to remove all root instances I ran again the RUU 1.29.651.7. all good so far. I double checked by booting into the boot loader to make sure I am s-on and locked along with no tampered flag. YES!!!!. so now I booted up my phone . skipped all setup processes. and went straight to the check for updates in the phone menu. I updated to the next most recent after the 1.29.651.7 and installed 1.29.651.10. I download and installed the update. again checking to see if there were any changes in the boot loader. NOPE STILL ALL GOOD,YESSSS!!!!
so now it rebooted and again went straight to the HTC update menu and ran a check for updates and it then downloaded the most recent update 1.31.651.2. Installed and I checked the bootloader and I AM NOW 100% STOCK and on the latest software version.
At least a Thank You ??
Thanks for Sharing!
viper1723 said:
At least a Thank You ??
Click to expand...
Click to collapse
I was having the same issues when trying different Roms and screwed up my phone to the point where roms would boot but them restart over and over and over...no matter what rom i loaded and any kind of wiping i did.
so I also returned to stock locking the bootloader and flashing stock RUU as you mention. Just tried going from 1.29 to 1.31 with OTA last night and it wiped my phone and didn't upgrade. So i'm hoping it was just a hiccup and going to try again.
Hope it works this time.
Solartrooper said:
I was having the same issues when trying different Roms and screwed up my phone to the point where roms would boot but them restart over and over and over...no matter what rom i loaded and any kind of wiping i did.
so I also returned to stock locking the bootloader and flashing stock RUU as you mention. Just tried going from 1.29 to 1.31 with OTA last night and it wiped my phone and didn't upgrade. So i'm hoping it was just a hiccup and going to try again.
Hope it works this time.
Click to expand...
Click to collapse
Let me know how it went I'll give u a more detailed method of what I did exactly
That's were I'm at right now.
viper1723 said:
Let me know how it went I'll give u a more detailed method of what I did exactly
Click to expand...
Click to collapse
Okay guys so everything you described is exactly where I'm at. I've tried a million ROMs, process, adb.exe (no devices), etc...... Anyway here's my scenario.... Exactly yours: got my phone, rooted it, had S-On. the phone ran it's updated to 1.31.651.2 so there are no RUUs for this. Any extra details to get me there?
Where should I start? Please let me know if you can help.
Thanks!:cyclops:
I've got the fuzzy lens problem and I want to get the phone replaced (preferably via T-Mobile but I'll go directly to HTC if I have to). I know you can scratch off the coating on the lens and get some camera improvement but I'm not interested in that solution.
My goal: Return the phone to completely stock condition. No root, locked bootloader and preferably S-ON. I've read a few stories where HTC insisted on replacing the motherboard (with an additional full price fee) because the device was S-OFF and I don't want to go there.
Background: I used firewater to S-off the phone as soon as I got it (it was running 1.12 at the time). I have flashed the Harmon Kardon audio stuff (http://forum.xda-developers.com/showthread.php?t=2737498). I have turned off the tamper flag (http://forum.xda-developers.com/showthread.php?t=2708565). I am running the Stock+ rom which is based on 1.57 (http://forum.xda-developers.com/showthread.php?t=2716843).
My plan:
1) Reset my bootloader to locked (http://forum.xda-developers.com/showthread.php?t=2708571)
2) Wipe the phone and restore my very first nandroid backup I made with TWRP. That will get me back to unrooted 1.12 firmware but without the stock bootloader and still S-OFF. Staying with 1.12 will allow me to S-OFF again with firewater if it comes to that. If some kind of emergency came up, I'd hate to spend $25 on sunshine for a one time use on a phone that is going back to HTC forever.
3) Install the stock bootloader that matches 1.12 firmware. Not sure how to do this yet. I'm afraid I won't be able to achieve this with a locked bootloader and no root.
4) Verify everything is back to stock.
5) Set the phone back to S-ON (http://forum.xda-developers.com/showthread.php?t=2758818)
6) Run the 1.57 RUU (http://forum.xda-developers.com/showthread.php?t=2714456)
7) Proceed with the warranty exchange.
I'm not sure running the RUU is 100% necessary, but I figure it's the best bet I have to make the phone completely stock.
Questions: Is this a sane plan? Am I doing anything in the wrong order? Are there any steps that won't work because I've lost root or unlocked bootloader? Am I setting myself up for a brick anywhere?
There is a thread about doing this on a EU M8 (http://forum.xda-developers.com/showthread.php?t=2735235) but I can't tell what, if any, modifications need to be done for the USA T-Mobile version of the M8. There is talk about having to flash a firmware file twice or risk a hard brick when setting S-ON. Do I need to be worried about any of that?
UPDATE: T-Mobile gave me a warranty replacement to fix the camera lens problem. I did get the old phone back to completely stock with locked bootloader and S-on before sending it back.
I found it was easiest to use the sunshine installer to gain temp root. You don't need to pay anything since you stop before it goes through the whole S-Off process. Just run the APK and select temp root. When sunshine shows you the next screen, you can exit out and still have root. (http://theroot.ninja/)
In the end I didn't bother with the old nandroid and keeping the exploitable version. I also had the order messed up in my initial post. Here is what worked for me:
1) factory reset the phone (in TWRP I did advanced wipe and also wiped internal storage). This step kills root. Rebooted the phone and verified it was back to factory defaults. Go through the setup wizard and skip all the steps. I couldn't find a way to bail out without going through every step in the wizard.
2) flashed stock recovery (the bootloader was unlocked and the phone was S-Off). Root is not necessary for this since it is done in fastboot. (http://forum.xda-developers.com/tmo...l/ota-recovery-ruus-firmware-dumps-t-t2852107). Rebooted the phone.
3) achieved temp root using sunshine APK
4) locked the bootloader (required before running the RUU). You must have root since you need a SU # prompt in the shell. (http://forum.xda-developers.com/showthread.php?t=2708571). I rebooted again for good measure but it's probably not necessary.
5) reset the phone back to completely stock using the latest 2.22.531.5 RUU. This step does not require root. I found it was easiest to put the phone into fastboot mode before running the RUU. (http://www.htcdev.com/devcenter/downloads)
6) Once the phone booted back up, I looked over everything and made sure it is all completely stock. Checked HBOOT said locked (not relocked) and dis not say tampered.
7) OPTIONAL - set S-On. Again root is not required since this is a fastboot command. (http://forum.xda-developers.com/showpost.php?p=52823014&postcount=2)
My actual process wasn't this streamlined. I ended up doing the RUU a couple of times because I didn't flash the stock recovery first and I didn't think the RUU installed the stock recovery right. Turned out I just didn't know what the stock recovery looked like (it was very confusing since I had never actually used a HTC stock recovery).
Thanks to the authors of the various threads I pulled info from. They are the real MVP's.
I flashed the stock HTC RUU via the .EXE and wasn't able to get the "RELOCKED" off the phone. Tried some steps here:
http://www.droidviews.com/restore-att-htc-one-m8-stock-firmware/
however I wasn't able to get "SU" to properly run in terminal.
No w the phone says *** RELOCKED ***
and im S-On
anything I can do?
Hi all
Im unbranding my O2 UK locked M8 to an unbranded UK one (with offical Htc 501 rom), so Ive done quite alot of reading around and followed guides
- Ive SIM Unlocked my device
- Ive successfully unlocked bootloader through HTCDev using Adb
- Ive installed and am running TWRP 2840
- Ive rooted with SuperSU
From what ive read.. AM I Right in thinking the next steps are:
S-Off and SuperCID with Sunshine (Firewater is no more)
Install Stock 1.54.401.10 through TWRP
Install Stock Recovery
Reboot
UPdate OTA to 501.
Any advice guides or help will be greatly appeciated.
Cheers all
1. S-OFF
2. Change CID to HTC__001
3. Flash 4.16.401.10 RUU
4. Done, no more o2 gumpf!
Thanks for the guide, I installed Sunshine 284 (latest, but it says that its not compatible with my device yet and theyre working on it,
My device is running LP 501 from O2, so maybe I need to wait for SDunshine 3.
Oh well
Ive done a factory reset and Ill just use the phone until SS 3 comes out.. or is there another way to S-Off from LP 501.
What effect will Factory reseting at this point have have...
I can still see SuperSU in my apps, but Sunshine app has gone..
I also assume the bootloader unlock is a permanent thing, so I just pickup where i left off ...
S-Off
If you're on 5.0 now then you'll have to wait for SS to be updated, hopefully it won't be too long! A factory reset now will just reset the phone, nothing else. And yes, bootloader will remain unlocked unless you lock it again
EddyOS said:
If you're on 5.0 now then you'll have to wait for SS to be updated, hopefully it won't be too long! A factory reset now will just reset the phone, nothing else. And yes, bootloader will remain unlocked unless you lock it again
Click to expand...
Click to collapse
Cheers. I did try the last firewater update, but adb reboot, just restarts the phone. I was thinking of manually getting into fastboot then taking it from there, but didnt want to chance a brick
Ill just wait for SS 3
Do you know.. since rooting und unlocking the M8... its running better than it was, faster and smoother...
I'm done with these issues that my phone is having. It keeps locking up no matter what ROM I use or how little apps I have installed. Something has got to be wrong with my phone and it's time to bring it back to TMO for repair/replacement.
I found this link on HTC to download the RUU: http://www.htc.com/us/support/rom-downloads.html#tmobile
My question is, would this be enough to bring my phone back to stock so that they don't know I've rooted it?
Edit: Also, I just remembered about my bootloader being s-off/unlocked. Would this make a difference or would the RUU set everything back like it should?
Edit again: I found this thread: http://forum.xda-developers.com/showthread.php?t=2735235
So, would I be able to follow his instructions but change the CID to t-mob010 instead of the ones he has listed?
Nobody? I could really use some input on this, I don't want to brick my phone. I have to do this today, I can't take the lockups anymore.
There is a thread dedicated to returning your device to stock. It's intended for European users, but the instructions apply equally well to US users.
The first step is running the RUU, then locking (not relocking) the bootloader using adb commands. Reference http://forum.xda-developers.com/showthread.php?t=2708571 (for instructions on locking your bootloader)
Note that you can run the RUU without locking your bootloader if you are S-off. Once you are back to bone stock (recovery + OS), you can then go back S-on if you are concerned about the warranty, though I strongly advise AGAINST this in general.
Also, you may find that simply re-running the RUU will clear up your issue. I'd run it for a few days after restoring the phone before assuming a hardware fault.
jshamlet said:
There is a thread dedicated to returning your device to stock. It's intended for European users, but the instructions apply equally well to US users.
The first step is running the RUU, then locking (not relocking) the bootloader using adb commands. Reference http://forum.xda-developers.com/showthread.php?t=2708571 (for instructions on locking your bootloader)
Note that you can run the RUU without locking your bootloader if you are S-off. Once you are back to bone stock (recovery + OS), you can then go back S-on if you are concerned about the warranty, though I strongly advise AGAINST this in general.
Also, you may find that simply re-running the RUU will clear up your issue. I'd run it for a few days after restoring the phone before assuming a hardware fault.
Click to expand...
Click to collapse
Yes, I did find that post and am planning on following those instructions. However, you've confused me. According to that thread, they say to lock the bootloader first and then install the RUU; but you said the opposite. Which is it?
http://forum.xda-developers.com/showthread.php?t=2735235
Also, why are you against turning back S-on? I had planned on it because I don't want to take the chance of TMO or HTC having a problem.
ned4spd8874 said:
Yes, I did find that post and am planning on following those instructions. However, you've confused me. According to that thread, they say to lock the bootloader first and then install the RUU; but you said the opposite. Which is it?
http://forum.xda-developers.com/showthread.php?t=2735235
Also, why are you against turning back S-on? I had planned on it because I don't want to take the chance of TMO or HTC having a problem.
Click to expand...
Click to collapse
You are S-off, which means you do NOT have to lock the bootloader first. Most instructions for running an RUU assume you are S-on, however, which does require your bootloader to be locked. It's one of the checks that is disabled by S-off.
Also, S-off is getting harder to obtain, so unless there is a pressing reason to go S-on, it's safer to remain S-off. Warranty support could be that pressing reason.
Time to turn back S-on. Even after the RUU, it's still very buggy. Locking up, slow, lag, etc. Time to bring it back to TMO.
Anyone know what that will work? I do have the warranty service on it. So will they just replace my phone with a refurb M8, will it be sent out, what can I expect?
ned4spd8874 said:
Time to turn back S-on. Even after the RUU, it's still very buggy. Locking up, slow, lag, etc. Time to bring it back to TMO.
Anyone know what that will work? I do have the warranty service on it. So will they just replace my phone with a refurb M8, will it be sent out, what can I expect?
Click to expand...
Click to collapse
If you think your phone has bad hardware, then yeah, at this point you need to go ahead and S-on with the assumption that you will get a refurb - especially now that the M9 has been out a while. Who knows what you will get, though. You might even luck out and get a "new old stock" device with 4.4.2. Or, the refurb place could RUU it up to the latest. It's purely the luck of the draw.
Well this sucks. Can't get adb to recognize my phone in recovery. I can when it's booted into the system, but not recovery or the bootloader....
What a pain this is becoming!!!!!!!!!!!! I'm even trying to get into shell when the phone is booted up and sure I can do that, but I can't su! The binary isn't installed. So, what now I have to f'ing install a different ROM, s-on it and then ruu again????
So I f'ed up and turned S-ON by mistake before I did the commands to clear the bootloader modified messages. And now I can't get S-OFF for the life of me! Sunshine can't get root it says, SuperSU is installed and says a binary needs updating, but when I click on it, it just freezes and won't update the binary. I tried pushing it down via zip/bootloader but that doesn't help. I ran a root checker and it says my phone is rooted, but nothing is working like I expect it to.
I'm still running the stock ROM from the RUU, could that be the issue? Do I have to install a different ROM before I can S-OFF and then RUU again? This is such a pain!!!
ned4spd8874 said:
So I f'ed up and turned S-ON by mistake before I did the commands to clear the bootloader modified messages. And now I can't get S-OFF for the life of me! Sunshine can't get root it says, SuperSU is installed and says a binary needs updating, but when I click on it, it just freezes and won't update the binary. I tried pushing it down via zip/bootloader but that doesn't help. I ran a root checker and it says my phone is rooted, but nothing is working like I expect it to.
I'm still running the stock ROM from the RUU, could that be the issue? Do I have to install a different ROM before I can S-OFF and then RUU again? This is such a pain!!!
Click to expand...
Click to collapse
If you are still bootloader unlocked, install TWRP, restore an appropriate nandroid backup for your device, root that install, and re-run Sunshine.
If you are bootloader locked, restart the phone into bootloader mode and select the RUU option. Then, re-run the RUU. If your bootloader is locked, it should run and restore everything to stock. Note that if you updated to Lollipop, you may have to use Kingroot to get temp root. I meant to suggest you RUU down to the original version (4.4.2) prior to going S-on and forgot - sorry about that.
jshamlet said:
If you are still bootloader unlocked, install TWRP, restore an appropriate nandroid backup for your device, root that install, and re-run Sunshine.
If you are bootloader locked, restart the phone into bootloader mode and select the RUU option. Then, re-run the RUU. If your bootloader is locked, it should run and restore everything to stock. Note that if you updated to Lollipop, you may have to use Kingroot to get temp root. I meant to suggest you RUU down to the original version (4.4.2) prior to going S-on and forgot - sorry about that.
Click to expand...
Click to collapse
Bootloader is still unlocked, but even after installing a couple different ROMs, sunshine just won't work. Says it's incompatible. It says to flash a stock sense or near stock rom. I'm on SkyDragon right now...
I'm at a loss. Anyone have a industrial shredder?
ned4spd8874 said:
Bootloader is still unlocked, but even after installing a couple different ROMs, sunshine just won't work. Says it's incompatible. It says to flash a stock sense or near stock rom. I'm on SkyDragon right now...
I'm at a loss. Anyone have a industrial shredder?
Click to expand...
Click to collapse
There are probably some T-mobile nandroid backups around here somewhere. Get one, put it on an SD card, and use TWRP to flash it. Unfortunately, I only have DevEd and AT&T images.
jshamlet said:
There are probably some T-mobile nandroid backups around here somewhere. Get one, put it on an SD card, and use TWRP to flash it. Unfortunately, I only have DevEd and AT&T images.
Click to expand...
Click to collapse
Things are looking up! Found a ROM called something like Alex V that was stock enough to get SunShine to work. Also, I was using the original version so once I got it to run, it was giving network errors. Once I installed the latest version, that's when I got was able to go S-OFF. So, now I'm S-OFF, the bootloader is saying Official and locked so now I'm going to RUU and throw it in TMO's face!
hello
i attempted to unlock bootloader on my wife's old HTC M8 (Australian/Vodafone), i was able to unlock the bootloader, but had to do some serious trial and error to get a custom recovery installed, eventually got an older twrp loaded, but the phone just refused to boot into recovery.
i then relocked the bootloader (no S-OFF), and when i try and unlock he bootloader now, the phone attempts to boot into the recovery, and is failing...
i've been trying to find an RUU from somewhere, just to blat the phone back to an old state, and try again.
are there RUUs available anywhere? i dont' care if its not for the local carrier, i just want to get a basic android rom on the thing.
However, im curious if i need to s-off to do this (wasnt the case with my previous HTC)
help!
what an idiot, i assumed this was an htc One m8, it wasnt, its an m7... reposting in there ...