I have a T-Mobile HTC One M8 and about a week ago I tried rooting it using Hasoon 2000s All-in-one toolkit. It worked until I decided to unroot it (for my warranty). Using the instructions from theunlockr, I tried to unroot it. However, after getting to the final step, my phone is stuck in the bootloader with no way of getting out of it from the bootloader. It says software status: Modified, relocked, and security warning (this goes away after attempting fastboot), and s-on. How do I fix this.
If you have a unlocked boot-loader, and need to return to stock this is what I would do (follow at your own risk).
- load up TWRP recovery
- flash a non-rooted ROM
- flash back the recovery for your phone
good luck
skeetc15 said:
I have a T-Mobile HTC One M8 and about a week ago I tried rooting it using Hasoon 2000s All-in-one toolkit. It worked until I decided to unroot it (for my warranty). Using the instructions from theunlockr, I tried to unroot it. However, after getting to the final step, my phone is stuck in the bootloader with no way of getting out of it from the bootloader. It says software status: Modified, relocked, and security warning (this goes away after attempting fastboot), and s-on. How do I fix this.
Click to expand...
Click to collapse
Related
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?
I just followed all of the steps to unlock the bootloader through HTCDev, but I'm having trouble in getting it to an unlocked state. Every time I flash the unlock_code.bin in fastboot, it prompts me if I want to unlock the bootloader, I select yes and the device formats and restarts. After I go through the initial setup again and enable usb debugging to reboot into fastboot, the status of the phone is still locked. Is there some step I missed to unlock this phone or is there a problem with HTCdev?
RhinoShock said:
I just followed all of the steps to unlock the bootloader through HTCDev, but I'm having trouble in getting it to an unlocked state. Every time I flash the unlock_code.bin in fastboot, it prompts me if I want to unlock the bootloader, I select yes and the device formats and restarts. After I go through the initial setup again and enable usb debugging to reboot into fastboot, the status of the phone is still locked. Is there some step I missed to unlock this phone or is there a problem with HTCdev?
Click to expand...
Click to collapse
I had trouble when I unlocked mine, but not with what you're describing. When I received my initial unlock code, I had done the HTCdev method with choosing one (M8) for my phone and the file would not flash. I re-ran HTCdev choosing "all other devices" and everything worked like a charm. Worth a shot.
I ended up getting it working by downloading the latest software update and trying again. I was just trying to get a GPE rom on here quickly because sense was aggravating me so much. Hopefully this helps anyone else that ends up having this problem!
Remember to get s-off first
RhinoShock said:
I ended up getting it working by downloading the latest software update and trying again. I was just trying to get a GPE rom on here quickly because sense was aggravating me so much. Hopefully this helps anyone else that ends up having this problem!
Click to expand...
Click to collapse
Great thanks this worked for me as well. I was trying a few times and it wouldn't unlock then as your said I ran the update and then it allowed me to unlock fine.
im having problems too
madskills843 said:
Great thanks this worked for me as well. I was trying a few times and it wouldn't unlock then as your said I ran the update and then it allowed me to unlock fine.
Click to expand...
Click to collapse
hi guys i hust bought a second handed htc on m8 for tmobile, i want to unlocked it to flash a custom rom, but i see its not stock nd i dond know what the first owner did with the phone. ok so the phone has a grey flag tagged as *** TAMPERED *** and a purple flag tagged as *** UNLOCKED *** and it seems its on S-ON status Hboot 3.18 and radio 1.19.213311491.03g any help on what i need to flash a custom rom???
luismendez said:
hi guys i hust bought a second handed htc on m8 for tmobile, i want to unlocked it to flash a custom rom, but i see its not stock nd i dond know what the first owner did with the phone. ok so the phone has a grey flag tagged as *** TAMPERED *** and a purple flag tagged as *** UNLOCKED *** and it seems its on S-ON status Hboot 3.18 and radio 1.19.213311491.03g any help on what i need to flash a custom rom???
Click to expand...
Click to collapse
It sounds like that is already bootloader unlocked. Boot into recovery and see if it's stock or not. If recovery is stock, you need to install twrp or cwm then you can flash a rom. If one of those is already there you're ready to flash a rom already. Instructions on installing recoveries and roms, etc are here in the forums if you do a quick search.
thankssomuch
awesome..after updating to 4.4.4 ,everything worked like charm....thanks a zillion:good::laugh::laugh::laugh:
Hi guys,
I have an HTC one mini its says locked on the bootloader screen with OS 1.32.502.3 and S-on I tried everything did the HTC Dev bootloader unlock did nott work it goes thru all the steps and says ok at the end but nothing happens on the phone tried the recovery but it goes right back to bootloader screen Please Help
Greetings! I've been unlocked / rooted for a while using HTDEV / TWRP / SuperSU with S-ON and would like to revert back to stock just enough to start receiving OTA again... and eventually Marshmallow. Sadly, I'm getting older and would rather limp along the stock road as I don't find myself tweaking as much anymore. Some facts:
HTC One M9 AT&T US
Android 5.1
HTC Sense 7.0
2.11.502.18
*** Software status: Modified ***
***RELOCKED***
***S-ON***
I unlocked bootloader via htcdev and made sure to make a backup of my stock rom before doing anything so I have that.
What I've done so far:
-TWRP restore my stock ROM (message popped up upon completion stating that device is not rooted, do you wish to root and I chose NO)
-Found (what I think to be) correct replacement stock recovery and flashed via fastboot. It was 2.6.502.16 (Android 5.1) AT&T US stock recovery download from andromods
-"Relocked" bootloader.
Is this all I need to do? I see some walkthrough that involve using Sunshine for S-OFF along with MID/CID and RUU back to 100% stock, but do I need to do all that with all I've saved during my original unlock/root process?
I saw right away that there was an 80ish mb update already so I decided to try and install the update but it stalled out about 10% with the red "!" phone graphic.
I follow you guys quite a bit over here at xda and really dig this community. Any help would be much appreciated!
Have the same problem with my HTC one m9 but with unrooting and installing the ruu 3.35.161.12.
New Update received to android 7... It restarts and install it but until 25% comes the red triangle with the exclamation.... Need also help
Solved.
I flashed the 3.35.401.12 RUU according to Flippy498's guide
https://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698 (Thread #5)
All the Phone data was wiped during the process.
shivadow and computerslayer thanks again for your help
Hello,
My friend's HTC M9 got bricked during the new Nougat update (was turned off during update).
Ever since it is bootlooping, in can put it in Bootloader and Download mode but can't load it to recovery mode.
Tried to flash the stock recovery via download mode but the phone is S-ON and locked.
What are my options in getting the phone back to life (gave up on saving any of the data on the device)?
Any help will be appreciated.
P.S.
First time handeling HTC but have a lot of experience with nexus devices
Device info:
HTC M9 himauhl
S-ON,
Locked,
OS - 3.35.401.32
You need to run the ruu.exe but I don't know if one exists for your version. You can flash any 3.35.401.xx ruu but those that aren't "xx" must match. Not sure you can flash a signed zip in s-on state..
If the ruu.exe doesn't exist then you'll either have to wait for it to be released or rtm for repair.
There is no actual way to know exactly how buggered the phone is because it died in the middle of a flash process. It is very possible it died just as it was flashing recovery, explaining why there isn't one, but I wouldn't like to bet money on it, or it being recoverable at all.
Beamed in by telepathy.
shimshi said:
Hello,
My friend's HTC M9 got bricked during the new Nougat update (was turned off during update).
Ever since it is bootlooping, in can put it in Bootloader and Download mode but can't load it to recovery mode.
Tried to flash the stock recovery via download mode but the phone is S-ON and locked.
What are my options in getting the phone back to life (gave up on saving any of the data on the device)?
Any help will be appreciated.
P.S.
First time handeling HTC but have a lot of experience with nexus devices
Device info:
HTC M9 himauhl
S-ON,
Locked,
OS - 3.35.401.32
Click to expand...
Click to collapse
You've access to download mode, so you should be able to use the SD card method of applying the matching RUU. Check out the readme thread for instructions and the necessary file.
Thanks for your help shivadow and computerslayer,
I will look at the RUU method and try to learn more about it and replay if it worked or not.
I have the same problem and have tried everything but it's still bricked. If I send it in for repair will they charge me? My phone is out of warranty (it's 1.5 years old). Since their update caused this problem you would think they wouldn't make me pay. Thoughts?
jewels76 said:
I have the same problem and have tried everything but it's still bricked. If I send it in for repair will they charge me? My phone is out of warranty (it's 1.5 years old). Since their update caused this problem you would think they wouldn't make me pay. Thoughts?
Click to expand...
Click to collapse
If you unlocked bootloader, the warranty is void anyway.
Try flashing the stock rom which doesn´t need a unlocked bootloader via htc_fastboot.exe. Place the stock rom in your sd-card. Then in bootloader it will say directly "Do you want to flash xxx.img".
albaniax said:
Try flashing the stock rom which doesn´t need a unlocked bootloader via htc_fastboot.exe. Place the stock rom in your sd-card. Then in bootloader it will say directly "Do you want to flash xxx.img".
Click to expand...
Click to collapse
Those are two different methods: The SD card method and the htc_fastboot method (which requires a PC).
And it's actually the other way round. The htc_fastboot method requires a locked or at least re-locked bootloader whereas the SD card method can be used with an unlocked bootloader, as well.