Related
With all the bootloader unlocking and flashing up to different RUU's, etc..
Will there be a way that someone might be able to come up with a procedure to revert back to complete stock?
Just wondering if you get going flashing roms and encounter a problem where you will need to exchange or take back your phone, a way to get it to stock form.
thanks
1.change you cid back to your original one.
2. relock your bootloader.
3. flash a ruu..
niceppl said:
1.change you cid back to your original one.
2. relock your bootloader.
3. flash a ruu..
Click to expand...
Click to collapse
Has anyone came up with a way to change the cid back to stock
and I thought if you were on 1.85, you simply couldnt flash a prior ruu
joho5 said:
Has anyone came up with a way to change the cid back to stock
and I thought if you were on 1.85, you simply couldnt flash a prior ruu
Click to expand...
Click to collapse
one you have unlocked your bootloader, your phone will either say unlocked or relocked. There's nothing that we can do about that. even if you changed the CID back to the AT&T one.
SuperCID means you can flash any RUU you want
gunnyman said:
one you have unlocked your bootloader, your phone will either say unlocked or relocked. There's nothing that we can do about that. even if you changed the CID back to the AT&T one.
SuperCID means you can flash any RUU you want
Click to expand...
Click to collapse
So I guess the best we can do is flash the stock ruu at the time and relock it and hope for the best.
joho5 said:
So I guess the best we can do is flash the stock ruu at the time and relock it and hope for the best.
Click to expand...
Click to collapse
you worried about returning a phone? It's been my experience that they don't look.
Hi everyone,
I feel kind of bad for asking such a generic question like this, and I assure you that I have read around and done my research, but before I do potentially dangerous, irreversible, things to my device, I just want to make sure that I will perform the necessary steps correctly.
Basically, I have owned my HOX since launch date, and it came with either 1.73 or 1.85 base. As such, I rooted and unlocked the bootloader as soon as the exploits were available, and have been comfortably flashing ROMs and kernels every since. However, I have been experiencing some issues with data connectivity and stuff, issues that remain with any ROM, kernel, or radio that I flash. The details aren't important...
Now, I want to basically "start over" with my HOX. As if it was a brand new, unmodified, fresh device. So basically, unroot, relock bootloader, RUU, etc... And then start all over, root, unlock bootloader, install recovery, etc.....
Basically, what exact steps do I need to take to accomplish the "starting over"? As in the methods to use, the RUU to use, etc... ?
An outline of the steps, basically. My biggest fear is restoring to the wrong thing and losing my old HBOOT.
Again, I know this question probably gets asked often, but please bear with me through this.
I ruu'd my wife a and it was about 3 weeks before att sent her the next update lol. As long as you don't accept it you'll be fine. I'm sure you'd prolly root as soon as its finished anyway..
But you got it right. No need to unroot, just fire up fastboot and enter "fastboot oem lock". (Without quotes)
Figure out which ruu you need, most likely 1.85. Make sure you have the right HTC drivers updated, and make sure HTC sync is working right. Download ruu, which is an executable application, and run it. It should factory restore your phone like the day you bought it.
As far as restoring to the "bad" hboot, it shouldn't let you complete an ruu that's for another firmware other than what you had on it when you got root... So you'll be safe. Good luck bro, come back and let us know how it went :thumbup:
Sent from my One X using Tapatalk 2
So basically relock the bootloader with "fastboot oem lock" , and then RUU, and I have a fresh new phone?
And for determining which RUU I need, either 1.73 or 1.85, if I try running the wrong one, it will stop me?
And since I'm still on the older HBOOT with the older initial base, root and unlock the same way I did originally?
And also, once I relock my boot loader, should I immediately RUU?
So a full outline would be:
Connect phone to computer ( with drivers and all)
Boot into fast boot
Relock bootloader with command
RUU
Let phone boot
Re-root
Re-unlock bootloader
Install recovery
Flash ROMS!
?
And just because it's been forever since I've done it, what are the steps again for RUUing? Do I need to boot the phone into any special mode? Or I just connect the phone to the PC and run the RUU?
And after I relock the bootloader, will the phone reboot out of fastboot or anything? Or should I go immediately from the relock phase to the RUU phase?
Thanks
So basically relock the bootloader with "fastboot oem lock" , and then RUU, and I have a fresh new phone? You got it.
And for determining which RUU I need, either 1.73 or 1.85, if I try running the wrong one, it will stop me? Yes, it'll throw an error when you try to go through the RUU install process.
And since I'm still on the older HBOOT with the older initial base, root and unlock the same way I did originally? Yes. This is a fresh phone install after you run the RUU (like the day you bought it).
And also, once I relock my boot loader, should I immediately RUU? Yes. There's not a lot else you really need to do (especially on bricked phones, not a lot you CAN do).
So a full outline would be:
Connect phone to computer ( with drivers and all)
Boot into fast boot
Relock bootloader with command
RUU
Let phone boot
Re-root
Re-unlock bootloader
Install recovery
Flash ROMS!
? - Yes, that's pretty much it.
And just because it's been forever since I've done it, what are the steps again for RUUing? Do I need to boot the phone into any special mode? Or I just connect the phone to the PC and run the RUU? - Connect to pc in fastboot usb and run it from there.
And after I relock the bootloader, will the phone reboot out of fastboot or anything? - Nope, it'll stay in fastboot unless you reboot it.
Or should I go immediately from the relock phase to the RUU phase? - That makes things a little faster
Yep.. Run it from anywhere, as long as your computer recognizes your device let us know how it goes
Sent from my One X using Tapatalk 2
Ok, thanks a lot.
I don't have a PC with me right now (mac user) but once I get the opportunity I will go through with this. Thanks again!
Im hoping this thread may help me to solve my problem (I'm a total noob too lol)
I rooted and flashed a Rom on my HTC One S, and I had the same issues as OP
Im with Fido, but I was told that both Fido and Rogers use the same RUU
Trying to go back to stock, I relocked the bootloader.
1. then I ran the RUU (found a tutorial online), but I got an error message (155: wrong RUU or file cant be larger or something like that)
2. then I tried an alternative method : extract 2 files from the RUU, move them to another folder and from there run a cmd; didnt work either
(By the way, in method number 1, I also had to flash a recovery file (stock recovery) during the bootloader unlock process)
Did I do it the right way?
Can some Senior member give me a detailed step by step method?
Why do you keep posting HTC ONE S questions in our HTC ONE X forum? What is wrong with using the correct forum?
954wrecker said:
Why do you keep posting HTC ONE S questions in our HTC ONE X forum? What is wrong with using the correct forum?
Click to expand...
Click to collapse
Yeah.
954wrecker said:
Why do you keep posting HTC ONE S questions in our HTC ONE X forum? What is wrong with using the correct forum?
Click to expand...
Click to collapse
I did ???
Hey what do you know :laugh:
I have tried to do this multiple times, but no matter how many times a run the 2.2 exploit, and flash the unlock code bootloader continues to say relocked? any ideas
Yes, you need to check your pm. You need to hard reset the device. Hold power until device reboots, capacitive keys will flash during the process. Then run the unlock and you're device will unlock. I spent a full day to figure this out... Lol
Sent from my HTC One XL using Tapatalk 2
anyone happen to have a link on how to reset your phone back to factory defaults? i've had too many issues with roms, and my wifi, and as i use it for work, i cant have this happening.
I didn't back up the factory ROM before i started flashing, does that mean im pretty much screwed?
I have Hboot 1.14
Behemyth said:
anyone happen to have a link on how to reset your phone back to factory defaults? i've had too many issues with roms, and my wifi, and as i use it for work, i cant have this happening.
I didn't back up the factory ROM before i started flashing, does that mean im pretty much screwed?
I have Hboot 1.14
Click to expand...
Click to collapse
If you want to reset to stock just run the ruu like the poster above is trying to do.
Sent from my HTC One XL
ECEXCURSION said:
If you want to reset to stock just run the ruu like the poster above is trying to do.
Sent from my HTC One XL
Click to expand...
Click to collapse
Nobody answered his question about if he needs to find a RUU specific to his device. I've been looking and can't find an RUU specific to 1.14, and I dont want to chance bricking my device.
Behemyth said:
Nobody answered his question about if he needs to find a RUU specific to his device. I've been looking and can't find an RUU specific to 1.14, and I dont want to chance bricking my device.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1671237
scroll down to the stock ruu section and look up the firmware 2.2 not the hboot 1.14
Well, I'm the OP, and I ended up figuring out what RUU to use, which was 1.73. Basically, I ran 'fastboot oem lock' , then ran the RUU right afterwards, then booted up and ran the root exploit, rooted, and then ran 'fastboot oem unlock' using my old Unlock.bin file that I had from the very first time I unlocked the bootloader. From there, I installed a custom recovery and was good to go.
Yah, if your using 2.20 firmware, run the below link, works like a charm. Must make sure you re-lock the bootloader before, or it will error out. Just hold down the power button until it turns off if this happens.
possible brick
Skeeterdrums said:
So basically relock the bootloader with "fastboot oem lock" , and then RUU, and I have a fresh new phone? You got it.
And for determining which RUU I need, either 1.73 or 1.85, if I try running the wrong one, it will stop me? Yes, it'll throw an error when you try to go through the RUU install process.
And since I'm still on the older HBOOT with the older initial base, root and unlock the same way I did originally? Yes. This is a fresh phone install after you run the RUU (like the day you bought it).
And also, once I relock my boot loader, should I immediately RUU? Yes. There's not a lot else you really need to do (especially on bricked phones, not a lot you CAN do).
So a full outline would be:
Connect phone to computer ( with drivers and all)
Boot into fast boot
Relock bootloader with command
RUU
Let phone boot
Re-root
Re-unlock bootloader
Install recovery
Flash ROMS!
? - Yes, that's pretty much it.
And just because it's been forever since I've done it, what are the steps again for RUUing? Do I need to boot the phone into any special mode? Or I just connect the phone to the PC and run the RUU? - Connect to pc in fastboot usb and run it from there.
And after I relock the bootloader, will the phone reboot out of fastboot or anything? - Nope, it'll stay in fastboot unless you reboot it.
Or should I go immediately from the relock phase to the RUU phase? - That makes things a little faster
Click to expand...
Click to collapse
I did this, but my phone never boots. It just stays at the bootloader after i run the RUU. Any ideas? :/
Also, i get the "this build is for development purposes only" message under the HTC logo before the phone enters the bootloader.
EDIT: managed to get the bootloadr unlocked again via HTCDev.com and flashed recovery and ROM. Guess Im not starting fresh after all lol
Ok, so I installed Cleanrom 6 and flashed Elemental 6.0(I know it's experimental, I should have been prepared for something like this). I went into recovery(CWM) for something and instead of getting into recovery it just showed cwm logo and immediately rebooted to the splash screen and stayed there. I then tried to reboot several times into recovery and the rom, only resulting in the same thing. SOO while in bootloader I decide "hey I'll just run the 2.20 ruu and everything will be ok.". Well, I ran fastboot oem lock and it said it failed but now the bootloader says RELOCKED. Now, having relocked, the RUU program STILL can't detect my phone. Then I realize, I don't have the Unlock_code.bin anymore. So now I'm stuck in bootloader, (somewhat)relocked, and have absolutely no idea what to do next. Oh and I have S-OFF if that helps.
Thanks for taking the time to read that wall of text(hopefully), Does ANYONE have an idea of what I can do next? I sincerely appreciate any help I can get.
Thanks
Ouch. I've done stuff like this, so I'll be nice. This is what happens when something goes wrong and you panic and start trying a lot of stuff without thinking it through.
Does adb devices detect the phone? You should be able to get another unlock token by going back to htcdev, assuming you're still supercid. Try that before running the RUU.
iElvis said:
Ouch. I've done stuff like this, so I'll be nice. This is what happens when something goes wrong and you panic and start trying a lot of stuff without thinking it through.
Does adb devices detect the phone? You should be able to get another unlock token by going back to htcdev, assuming you're still supercid. Try that before running the RUU.
Click to expand...
Click to collapse
Thanks so much for the reply, Yeah I'm still SuperCID and I'll try that. I am supposed to be in bootloader for the RUU to detect my phone, right? and when it "relocked" it said
Code:
C:\ADB>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = -2228225 (0xFFDDFFFF)
FAILED (status read failed (Too many links))
finished. total time: 0.938s
Again, sorry. I know this was REALLY dumb. I just panicked. Thanks for taking the time to help.
Are you s-off or not? You can run a ruu not being in bootloader, but once you relock, you can't boot up without running the ruu unless you're s-off.
If you're s-on, proceed very carefully. People with s-on and supercid have bricked running the latest ruu.
iElvis said:
Are you s-off or not? You can run a ruu not being in bootloader, but once you relock, you can't boot up without running the ruu unless you're s-off.
if you're s-on, proceed very carefully. People with s-on and supercid have bricked running the latest ruu.
Click to expand...
Click to collapse
I'm S-OFF. I guess I just got cocky and figured WELL I'M S-OFF SO I'LL JUST TRY EVERYTHING HURR DURR lol. But yeah I'm s-off.
He said he's s-off. So just get a new unlock code from HTC dev and reunlock and reinstall cwm or twrp and flash cleanrom again
Sent from my VENOMized HoxL
jacobas92 said:
I'm S-OFF. I guess I just got cocky and figured WELL I'M S-OFF SO I'LL JUST TRY EVERYTHING HURR DURR lol. But yeah I'm s-off.
Click to expand...
Click to collapse
If you're s-off, you're fine. Just get a new unlock code and you can flash what you want.
iElvis said:
If you're s-off, you're fine. Just get a new unlock code and you can flash what you want.
Click to expand...
Click to collapse
Ok, thanks guys. I REALLY appreciate the help. It's booting fine now. I guess the only problem now is why it won't get past the first 3 seconds into booting to recovery or the rom. I had also flashed multiple versions of TWRP but still had the same problems. I'll just shut it down for an hour or 2 and try again later.
fastboot erase cache
You switched from CWM to TWRP and need to clear the cache.
iElvis said:
fastboot erase cache
You switched from CWM to TWRP and need to clear the cache.
Click to expand...
Click to collapse
AH. Wow. I would hit thanks again but it seems I've hit my limit. I guess the rom wouldn't boot cause I had been undervolting. It's strange, I only undervolted to 825 and it usually only gets unstable around 800. Plus, I was at stock clock speeds. Oh well. Guess I'll be trying flars bulletproof kernel. lol I NEED s2w.
Thanks again for all the help. You guys are awesome.:good:
jacobas92 said:
AH. Wow. I would hit thanks again but it seems I've hit my limit. I guess the rom wouldn't boot cause I had been undervolting. It's strange, I only undervolted to 825 and it usually only gets unstable around 800. Plus, I was at stock clock speeds. Oh well. Guess I'll be trying flars bulletproof kernel. lol I NEED s2w.
Thanks again for all the help. You guys are awesome.:good:
Click to expand...
Click to collapse
My phone doesn't like undervolting at all. Bulletproof is a great way to go.
Sent from my HTC One XL
area51avenger said:
He said he's s-off. So just get a new unlock code from HTC dev and reunlock and reinstall cwm or twrp and flash cleanrom again
Sent from my VENOMized HoxL
Click to expand...
Click to collapse
If he's s-off he doesn't need to relock or unlock bootloader right? At least I didn't when I ruu'd back to stock while s-off.
Sent from my Elemental Venomized S-off HTC One XL
majortaylor said:
If he's s-off he doesn't need to relock or unlock bootloader right? At least I didn't when I ruu'd back to stock while s-off.
Sent from my Elemental Venomized S-off HTC One XL
Click to expand...
Click to collapse
Its all good now they helped me. But to answer your question, I do know that even with s-off there are a few if not all fastboot commands that write to certain partitions that require an unlocked bootloader (at least from my experience).
Hello! Third HTC I'll (potentially) root, so I'm not sure why I'm stuck on this, but here goes....
I have an AT&T (Evita) on 2.20. It seemed the first step was to unlock using the X-Factor root exploit, so I did. When I was done, my bootloader said *UNLOCKED*, but it still said "S-OFF".
When I read any of the rollup/Q&A/FAQ threads, they all seem to indicate that my next step should be to flash a custom recovery. The first time I installed GooManager, then settings/Install OpenRecoveryScript. It said recovery had been installed, but when I selected Reboot Recovery, it wouldn't reboot.
So I powered down and came back up in the bootloader. I clicked recovery from there and after a few seconds I wound up with a mostly black screen with a drive or something in the middle and a red X over the middle. Something's clearly not working.
So I manage to get out of that, get the phone booted back into Android, back to the bootloader and into Fastboot USB to try and install the TWRP img file I downloaded from their site. did "fastbook flash recovery nameofmyimage.img" and it appeared to have moved the IMG to my device. Typed "fastboot reboot" and I wound up rebooted back to Android. Went back into GooManager to see if the "reboot into recovery" command would work now, it doesn't. Powered bown and back into the bootloader screen, select Recovery and I wind up back in Android.
What am I missing or doing wrong? Anyone?
finallygreen said:
I have an AT&T (Evita) on 2.20. It seemed the first step was to unlock using the X-Factor root exploit, so I did. When I was done, my bootloader said *UNLOCKED*, but it still said "S-OFF".
Click to expand...
Click to collapse
You mean S-off or S-on? S-on is the stock condition, and S-off is the modified condition (all security off).
finallygreen said:
So I powered down and came back up in the bootloader. I clicked recovery from there and after a few seconds I wound up with a mostly black screen with a drive or something in the middle and a red X over the middle. Something's clearly not working.
Click to expand...
Click to collapse
That is the stock recovery. GooManager is a big quirky when installing TWRP, the fastboot way is safer. Of course, you tried that way and still having trouble.
Try:
fastboot erase cache
Also, what version of TWRP exactly are you trying to install by fastboot (exact filename)?
redpoint73 said:
You mean S-off or S-on? S-on is the stock condition, and S-off is the modified condition (all security off).
That is the stock recovery. GooManager is a big quirky when installing TWRP, the fastboot way is safer. Of course, you tried that way and still having trouble.
Try:
fastboot erase cache
Also, what version of TWRP exactly are you trying to install by fastboot (exact filename)?
Click to expand...
Click to collapse
I typed it correctly....when I'd finished the process of unlocking the bootloader, my bootloader screen said:
***UNLOCKED***
EVITA PVT SHIP S-On RL
And that's what it still says. Is this what's stopping me from proceeding? Did I miss something because I can't find a step I missed in any of these tutorials...they all say to move on to installing a custom recovery right after you unlock the bootloader.
Oh, and the img I was flashing:
openrecovery-twrp-2.6.3.0-evita.img
Can you post the text from the command prompt on an attempt so we can try troubleshoot it?
Sent from my Evita
which text?
The text from the command prompt when you're trying to flash TWRP recovery.
Sent from my Evita
timmaaa said:
The text from the command prompt when you're trying to flash TWRP recovery.
Sent from my Evita
Click to expand...
Click to collapse
OK, so today I go back to the bootloader screen and I see this:
*** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-1.14.0002
Yesterday, I didn't have *** TAMPERED *** at the top.
Anyways, I've tried flashing TWRP again. here's the command prompt text:
Code:
c:\android>fastboot flash recovery openrecovery-twrp-2.6.3.0-evita.img
sending 'recovery' (8176 KB)... OKAY
writing 'recovery'... OKAY
And that's it. But this time, my results are different. I rebooted the bootloader, selected recovery, and now I'm IN TWRP!
So, I guess that's a good thing. However, since I don't at all understand why doing the same thing gave a different result today (and that *** TAMPERED *** thing that wasn't there yesterday), I'm a bit confused at to where to go next. So that I don't muck this up, could you tell me what the next logical step should be now?
Make a nandroid backup. Download an evita Rom and flash away
Sent from my VENOMized HoxL
area51avenger said:
Make a nandroid backup. Download an evita Rom and flash away
Sent from my VENOMized HoxL
Click to expand...
Click to collapse
OK, so I made a backup (just data/system/boot...hopefully that was the right choice), and when I went to reboot, it said that SuperSU was not yet installed. Now I'm not sure why none of the writeups mentioned that part because I know that every HTC I've ever rooted in the past needed that. Anyways, I said yes, it installed, and now I'm back in Android. I went back to the bootloader to check what it was saying...it still says "Tampered/Unlocked/S-On". I then went into TWRP and told it to reboot, this time it didn't prompt me to install SuperSU, so I guess that's good.
So:
1. Will the backup I made prior to the SuperSU install be good or will I need to redo that now that SuperSU is installed?
2. Why still S-On? Are HOX users sticking with S-On or....is this another step I've missed or is it even necessary with this device?
3. I keep seeing something about SuperCID...something that never came up in my previous HTC rooting adventures. What is this? How can I tell if I have it? Do I need it?
4. If this does indeed mean I'm fully rooted now and it's time to select a ROM, could anyone recommend one? I tend to prefer the latest Android that's known to run well on the device, running as close to stock and least amount of bloatware possible. But then again, I've no clue what the ROMs for this device can do since I just got it, so I'd certainly try something outside those parameters if it was extremely well-recommended.
Thanks!
Yeah that backup configuration looks fine to me. TWRP 2.6 has a feature where it detects if you don't yet have root installed when you're about to reboot, so it can install it for you, makes rooting a lot easier. You don't need to backup again, the one you made is fine.
The phone is still s-on because you haven't gone through the s-off process yet. Having s-off and unlocking the bootloader are two different things.
SuperCID is needed to get s-off, so you'll need to get SuperCID before you attempt the s-off process. The hex edit method is the best method for you to achieve SuperCID. One you've done that you can go to the Facepalm S-off thread and get s-off.
You are now fully rooted and can install custom ROMs. Asking for best/favourite/most stable/recommended ROMs isn't really allowed here, this is because saying one ROM is superior infers that the others are inferior in some way which isn't fair to the devs who spend a lot of time developing them for us. Take a look through our two development sections which are here and here. Pick one you think you'll like and give it a shot. Make sure you read the OP for the ROM you select because some have firmware upgrades prior to flashing them, these firmware upgrades usually need s-off to be done.
My suggestion is to do this: get SuperCID, get s-off, find a ROM, make sure you meet any requirements stated, and then flash it. If you have any questions dying be afraid to ask.
Sent from my Evita
timmaaa said:
Yeah that backup configuration looks fine to me. TWRP 2.6 has a feature where it detects if you don't yet have root installed when you're about to reboot, so it can install it for you, makes rooting a lot easier. You don't need to backup again, the one you made is fine.
The phone is still s-on because you haven't gone through the s-off process yet. Having s-off and unlocking the bootloader are two different things.
SuperCID is needed to get s-off, so you'll need to get SuperCID before you attempt the s-off process. The hex edit method is the best method for you to achieve SuperCID. One you've done that you can go to the Facepalm S-off thread and get s-off.
You are now fully rooted and can install custom ROMs. Asking for best/favourite/most stable/recommended ROMs isn't really allowed here, this is because saying one ROM is superior infers that the others are inferior in some way which isn't fair to the devs who spend a lot of time developing them for us. Take a look through our two development sections which are here and here. Pick one you think you'll like and give it a shot. Make sure you read the OP for the ROM you select because some have firmware upgrades prior to flashing them, these firmware upgrades usually need s-off to be done.
My suggestion is to do this: get SuperCID, get s-off, find a ROM, make sure you meet any requirements stated, and then flash it. If you have any questions dying be afraid to ask.
Sent from my Evita
Click to expand...
Click to collapse
First off, thank you very much for explaining things so clearly...I really appreciate that!
Second, I honestly didn't stop to think about the full ramifications of asking for a ROM recommendation. Based on your explanation, I completely understand why I shouldn't ask!
I'm gonna take your suggested route (SuperCID/S-Off) then start exploring for ROMs.
Thanks again for all the help!
No problems, glad to help. About the ROM question, you didn't know so it's all good, no harm no foul.
PS. If someone helps you around here, please press the thanks button.
Sent from my Evita
OK, so maybe I'm not as clear as I thought I was.
I did the X-Factor thing to unlock the bootloader at the beginning, and that involved spoofing my CID to get the unlock code from htcdev.com, right?
In any case, right now when I type: fastboot getvar cid
I get:
cid: 11111111
But you told me I still needed to do some hex editing?
You are good with the vid, time to achieve s-off
Sent from my HTC One XL using xda app-developers app
Yeah, you already have SuperCID do you can go for s-off now.
Sent from my Evita
My device is S-OFF and I'm running unlocked bootloader, custom recovery, and custom ROM.
I'm going to be returning it so I want to restore to completely stock (including S-ON). Any guides for this?
RedBullet said:
My device is S-OFF and I'm running unlocked bootloader, custom recovery, and custom ROM.
I'm going to be returning it so I want to restore to completely stock (including S-ON). Any guides for this?
Click to expand...
Click to collapse
Not exactly an all in one. Start here: http://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
The method for turning S-On and relocking can be found here: http://forum.xda-developers.com/showthread.php?t=2745257 near the bottom of the first post
Dottat's pre-rooted RUUs can be found here: http://forum.xda-developers.com/ver...zw-m8-master-ruu-firmware-collection-t2946473
My advice would be to flash a pre rooted RUU, Lock the bootloader, turn s-on then flash the stock RUU that matches the pre-rooted RUU. Don't forget to do a factory reset at the end as the RUUs are no-wipe.
I would say that turning s-on should be the last thing you do. Get the phone the way you want it. Flashed back to stock, locked bootloader and whatever else you want to do. Then make sure it's all the way you want it. Once you know for sure, then turn s-on. If you turn it on before you flash back to stock and you should somehow end up with it rooted or the have the tampered flag set, whatever the case may be (I've seen plenty of posts where something like this has happened), you'll be out of luck and not be able to fix it. Do it all and then turn s-on. That's my thinking anyway.
robocuff said:
I would say that turning s-on should be the last thing you do. Get the phone the way you want it. Flashed back to stock, locked bootloader and whatever else you want to do. Then make sure it's all the way you want it. Once you know for sure, then turn s-on. If you turn it on before you flash back to stock and you should somehow end up with it rooted or the have the tampered flag set, whatever the case may be (I've seen plenty of posts where something like this has happened), you'll be out of luck and not be able to fix it. Do it all and then turn s-on. That's my thinking anyway.
Click to expand...
Click to collapse
flashing the Stock RUU is the LAST thing you do, to remove root. You need root to turn s-on
edit: you need root to lock the bootloader, but not go S-on. In any event The steps Dottat outlines in his thread says to go S-on first then ruu the stock image