S-Off, Unlocked - No OTA - One (M9) Q&A, Help & Troubleshooting

Hi,
As much as I tried to look for this information, I didn't find a clear answer.
I have an M9 running 1.32.401.17 (stock recovery, from an old RUU), which is S-Off with unlocked bootloader. I was really expecting to get all the OTAs, so you can imagine my surprise when I didn't get any.
I then thought that I need to relock the bootloader, and then I will receive the OTAs. I relocked the bootloader, and again - no OTAs.
1. For an S-Off phone, should one receive OTAs with unlocked bootloader, or does one have to relock the bootloader (if so, to "locked" or to "relocked") to get OTAs?
2. Is the OS version on my phone so old that OTAs are not provided anymore?
3. Does it mean that if I manage to get a more "contemporary" OS version on my phone I'll get the OTAs?
4. If none of the above are correct, what do I need to do to get OTAs on my S-Off M9?
Thank you very much.
Adrian

Thanks to the fantastic post from Nikolay82 "HTC One M9 - 3.35.401.12 RUU installer how to guide!"
https://forum.xda-developers.com/one-m9/help/htc-one-m9-3-35-401-12-ruu-installer-t3318517
I managed to upgrade to 1.40.401.8.
After that I started to get OTAs (I'm now at 3.35.401.12) . So I can confirm that one doesn't need to relock the bootloader for an S-Off phone in order to receive OTAs (S-Off and UNLOCKED is fine).
I still don't know why I didn't get any OTA update for 1.32.401.17, but I'm happy that it worked from 1.40.410.8.
Cheers

Correct bootloader unlocked makes no difference. S-off makes no difference.
There is a possibility that htc have stopped the release of the earliest firmware. There is also a possibility that there was a problem but it would be solved by the update you did.

Even with S-ON you can receive updates with an unlocked bootloader.
The reason for your issue was the firmware you were using. 1.32.401.17 only got distributed in one single country. Therefore, only one specific CID of the handful of CIDs that belong to SKU 401 supports this "special" firmware version. In other words, you can't update a M9 and are stuck with that firmware if you aren't using the supported CID. The only solution is flashing a RUU with a different firmware version. That's why the RUU for 1.32.401.17 isn't linked in the ReadMe thread.
Edit: I can't tell you which CID actually corresponds to that "special" version since I forgot which one it was.
Sent from my HTC One M9 using XDA Labs

Related

[Q] How can I change the CID of my S-OFF One X?

My phone is S-OFF and it is SuperCID(11111111), I found out that I won't receive updates if my phone has this CID. I want to change it to a\n unbranded CID where I can receive the JB OTA. I don't know how, though. Also, what CID do you think will receive the earliest JB OTA once it comes out? And if I am going to change my CID to an unbranded one, can I revert it back to SuperCID once I receive the update?
jed27.galvez said:
My phone is S-OFF and it is SuperCID(11111111), I found out that I won't receive updates if my phone has this CID. I want to change it to a\n unbranded CID where I can receive the JB OTA. I don't know how, though. Also, what CID do you think will receive the earliest JB OTA once it comes out? And if I am going to change my CID to an unbranded one, can I revert it back to SuperCID once I receive the update?
Click to expand...
Click to collapse
just run a RUU and that will make you s-on and with the RUU's CID...
That doesn't sound useful, why would you want to lose S-Off?
HTC_001 is probably the most likely to be first, but I'm not sure if the OTA will work. Do you have stock 2.17.401.2 and stock recovery?
BenPope said:
That doesn't sound useful, why would you want to lose S-Off?
HTC_001 is probably the most likely to be first, but I'm not sure if the OTA will work. Do you have stock 2.17.401.2 and stock recovery?
Click to expand...
Click to collapse
yep i agree, i wouldn't ever ever ever flash a RUU only to get official updates! we will get the official update before it will be released worldwide
I am currently on stock 2.17.401.2 after flashing the RUU a month ago. Before that, I was on 1.15.401.1(!). Stock recovery? I don't know what that means, sorry. Anyway, I don't want to lose my S-OFF just so I can receive updates. I know s-off phones can change CID by fastboot blah blah. Something about writing a command, ugh, I'm not really sure.
You wouldn't even need to flash the RUU...
If you're S-Off, you could just use fastboot oem writecid HTC__001 if you really wanted too, which would change your CID to HTC__001 and keep you S-Off, but i'd say staying SuperCID is the best idea, and just flash one of the many JB roms that are out there.
Brownie2k said:
You wouldn't even need to flash the RUU...
If you're S-Off, you could just use fastboot oem writecid HTC__001 if you really wanted too, which would change your CID to HTC__001 and keep you S-Off, but i'd say staying SuperCID is the best idea, and just flash one of the many JB roms that are out there.
Click to expand...
Click to collapse
I get that. But I am still in the process of learning things since this is my first Android phone. Things are still complicated specially because the tuts on inbstalling custom ROMs are all about S-ON HOXs. Anyway, if I change my CID to a normal unbranded one, can I revert it back to SuperCID?
Yes you could.
You'd just do fastboot oem writecid 11111111.
To get updates though, you'd need to have a locked bootloader, stock rom etc... You phone would basically become a Unbranded European One X. Not sure if flashing the update would put you S-On, which means you'd be stuck as a HTC__001.
Basically if you wanted to try Jellybean, you'd just have to flash the required firmware, followed by a custom recovery then flash the rom. You don't need to unlock bootloader because you're S-Off.
Brownie2k said:
Yes you could.
You'd just do fastboot oem writecid 11111111.
To get updates though, you'd need to have a locked bootloader, stock rom etc... You phone would basically become a Unbranded European One X. Not sure if flashing the update would put you S-On, which means you'd be stuck as a HTC__001.
Basically if you wanted to try Jellybean, you'd just have to flash the required firmware, followed by a custom recovery then flash the rom. You don't need to unlock bootloader because you're S-Off.
Click to expand...
Click to collapse
... and as an added bonus you don't need to flash the boot.img of a custom rom before flashing the Rom itself, as we s-on peeps need to. You can just flash the entire custom rom at once from the custom recovery.
I.E. you won't need a computer when you want to try another rom
Sent from my HTC One X using Tapatalk 2
That's my problem! There should be a thread about S-OFF phones and what to do with them. Haha.
jed27.galvez said:
That's my problem! There should be a thread about S-OFF phones and what to do with them. Haha.
Click to expand...
Click to collapse
Well to be fair, it's very rare to find an S-Off One X at the moment, so count yourself very very lucky!
You hold one big big big advantage over us all though, you can downgrade your HBOOT back to 1.12 if you didn't like Jellybean. Currently for the most of us, with compatible CID's, once we're on HBOOT 1.28, thats it, there is no way back which means things like CM10 etc doesn't work for us.
Actually, you can use CM10 with hboot 1.28, but you have to use the special boot.img posted in the CM10 thread. It works for hboot 1.23 and hboot 1.28.
http://forum.xda-developers.com/showpost.php?p=32486421&postcount=7308

[Q] Relock to send back to Verizon

Hello, just a quick question. I had my One rooted, s-off, and unlocked when my microphone went. So I relocked, s-on, and flashed an RUU via http://forum.xda-developers.com/showthread.php?t=2475216. Just making sure that before I pack it in the box, there is nothing else that could trip the people at Verizon that I had messed with my phone. I took the OTAs up to 4.3. I'm just paranoid about info not matching up such as the baseband version and build number etc. Thanks
Does the bootloader say locked or relocked? Locked is good relocked not so much. Other than that you should be fine. Ruu's wipe everything and install it all fresh, including the firmware (baseband, hboot, recovery, etc), so everything will match up.
In the bootloader I have "Locked" also s-on. I noticed though with the refurbished phone I received (not happy about having to get refurbished but thats besides the point) the CID number shows in the bootloader screen whereas on my original phone it is not displayed. Not sure if I even need to be this worried, but I'm just paranoid. Thanks
Are both phones on the same hboot version? I dont remember if it showed in older hboots or not. Either way i wouldn't worry, locked and s-on is all you need.
No they weren't. I'm just going to stop worrying too much about it. Thanks
If i send my phone back to verizon do i have to be on the original ROM? i understand that i need to lock my bootloader and have s-on, but what about the software itself?
It can be on stock rom/firmware of any version. Just no custom roms or anything.
Just to confirm, if I have a phone that is S-OFF, unlocked:
1. Do I need to lock the bootloader before flashing an RUU?
2. Does flashing an RUU revert the phone to S-ON?
3. Does anything special otherwise need to be done to the phone prior to flashing the RUU?
Thanks so much in advance.
I also have to return a phone to VZW due to a hardware issue (the autofocus issue finally too much for me to bear).
You only need to relock the bootloader if using a signed ruu. A decrypted ruu does not need it locked.
Flashing an ruu will not remove s-off or relock the bootloader. You can do it before or after, but i sugest after, that way if something goes wrong durring the ruu, you still have options.
Once you do the ruu you will be stock. So the only thing you would have to do is relock and go s-on.
Fantastically clear, Clumsco, thanks! Three quick additional questions
1. is there any advantage to flashing the signed RUU, and adding danger by locking the bootloader beforehand? In your links below your signature is a path to both decrypted and signed versions of the latest RUUs. So I thought to ask before going with one or the other. If there is no advantage then I guess the decrypted version would be the safer bet, right?
2. Is there a danger that locking after the RUU will result in a "relocked" versus the desired "Locked" status?
3. Will the RUU flash wipe my /sdcard area? If so I'll back everything up before embarking on this.
I VERY much appreciate the help. I ran rumrunner several months back and have forgotten a lot of the nuances. Thanks for the quick primer!
cmlusco said:
You only need to relock the bootloader if using a signed ruu. A decrypted ruu does not need it locked.
Flashing an ruu will not remove s-off or relock the bootloader. You can do it before or after, but i sugest after, that way if something goes wrong durring the ruu, you still have options.
Once you do the ruu you will be stock. So the only thing you would have to do is relock and go s-on.
Click to expand...
Click to collapse
There is no difference between a signed and decrypted ruu other than what their names suggest. Ones signed ones not, both do the exact same thing to the phone.
You can lock the bootloader first. As long as you still have s-off, you have a saftey net. As long as your s-off you can change it to say what ever you want it to say. Locked, relocked, or unlocked.
Yes the ruu will wipe everything.
You will want to back up your sd.
Do the ruu.
Take the ota to kitkat.
Lock the bootloader.
Go s-on.
Thanks, everything worked. For future knowledge, can you flash signed RUU's with an S-ON device?
cmlusco said:
There is no difference between a signed and decrypted ruu other than what their names suggest. Ones signed ones not, both do the exact same thing to the phone.
You can lock the bootloader first. As long as you still have s-off, you have a saftey net. As long as your s-off you can change it to say what ever you want it to say. Locked, relocked, or unlocked.
Yes the ruu will wipe everything.
You will want to back up your sd.
Do the ruu.
Take the ota to kitkat.
Lock the bootloader.
Go s-on.
Click to expand...
Click to collapse
Yes and no. You can flash a signed ruu if s-on, but not one that is an older version than currently on the phone. It has to be the same or a newer version. This is an issue if your on kitkat, as we do not currently have a kk ruu available.
cmlusco said:
Yes and no. You can flash a signed ruu if s-on, but not one that is an older version than currently on the phone. It has to be the same or a newer version. This is an issue if your on kitkat, as we do not currently have a kk ruu available.
Click to expand...
Click to collapse
I'm trying to learn here too, that is dependent on the hboot correct? So if you were to downgrade your hboot via the thread somewhere in the VZW HTC One forum, you should be able to flash any RUU right?
Technically yes, although as far as i know there is no way to do so while s-on and locked. In order to downgrade hboot you would need to have the bootloader unlocked. Since verizon does not let us use htcdev to unlock, it would be virtually imposible.
Your responses are clear and helpful. Thanks a bunch!
cmlusco said:
Technically yes, although as far as i know there is no way to do so while s-on and locked. In order to downgrade hboot you would need to have the bootloader unlocked. Since verizon does not let us use htcdev to unlock, it would be virtually imposible.
Click to expand...
Click to collapse
cmlusco said:
There is no difference between a signed and decrypted ruu other than what their names suggest. Ones signed ones not, both do the exact same thing to the phone.
You can lock the bootloader first. As long as you still have s-off, you have a saftey net. As long as your s-off you can change it to say what ever you want it to say. Locked, relocked, or unlocked.
Yes the ruu will wipe everything.
You will want to back up your sd.
Do the ruu.
Take the ota to kitkat.
Lock the bootloader.
Go s-on.
Click to expand...
Click to collapse
My phone is current S-Off and relocked, how can I change it to unlocked?
Thank you.
UPDATE: Nevermind, I got it here: http://forum.xda-developers.com/showthread.php?t=2470340

[Q] How do I update my second hand HTC One M8?

Hi
Bricked my old 16gb HTC One M8 - sending to HTC for repair tomorrow.
Ordered a replacement 32gb HTC One M8 from Hong Kong. It was billed as 'new' but on arrival it appears to be S-OFF but locked. Full bootloader details below:
*** LOCKED ***
M8_UL_CA PVT SHIP S-OFF
CID-11111111
HBOOT-3.16.0.0000
RADIO-1.15.2133156.UA13G
OpenDSP-v38.2.2-00542-M8974.0311
OS-1.54.401.5
eMMC-boot 2048MB
Mar 22 2014,00:53:32.16037
Whenever I try to update OTA, it tells me my phone is not stock and the update doesn't install. I just want to get the phone back to stock with the latest OTA firmware, nothing more. What would my best course of action be here?
I'm no expert but I did purchase a used M8 last week with similar status, which was able to return to (almost) stock.
First, I think your super cid (11111111) is stopping you from any OTA update. Change that to reflect your carrier.
If you are still not able to check for OTA update after that, you need to unlock the bootloader, install TWRP or CWM boot loader, and flash a backup of stock Rom from your carrier.
billyboy77 said:
Hi
Bricked my old 16gb HTC One M8 - sending to HTC for repair tomorrow.
Ordered a replacement 32gb HTC One M8 from Hong Kong. It was billed as 'new' but on arrival it appears to be S-OFF but locked. Full bootloader details below:
*** LOCKED ***
M8_UL_CA PVT SHIP S-OFF
CID-11111111
HBOOT-3.16.0.0000
RADIO-1.15.2133156.UA13G
OpenDSP-v38.2.2-00542-M8974.0311
OS-1.54.401.5
eMMC-boot 2048MB
Mar 22 2014,00:53:32.16037
Whenever I try to update OTA, it tells me my phone is not stock and the update doesn't install. I just want to get the phone back to stock with the latest OTA firmware, nothing more. What would my best course of action be here?
Click to expand...
Click to collapse
M8_UL_CA. You are on AT&T, correct?
You can download the latest AT&T RUU here.
Download it onto your PC. Hook up your phone and open command prompt. Direct it to your ADB folder, then enter these commands.
adb reboot bootloader
fastboot reboot-bootloader
fastboot rebootRUU waiting for it to boot after each command.
Then run the RUU download by double clicking on the download, and follow the prompts given.
You will have to run it twice. The first time will not install the whole package, the second time finishes the process. This is normal.
xunholyx said:
M8_UL_CA. You are on AT&T, correct?
Click to expand...
Click to collapse
I'm not with AT&T. I bought the phone carrier unlocked - I use a Three mobile SIM. If the phone has been made S-OFF and carrier unlocked then I'd like to return it to a stock unlocked model if possible...
ikeny said:
I'm no expert but I did purchase a used M8 last week with similar status, which was able to return to (almost) stock.
First, I think your super cid (11111111) is stopping you from any OTA update. Change that to reflect your carrier.
If you are still not able to check for OTA update after that, you need to unlock the bootloader, install TWRP or CWM boot loader, and flash a backup of stock Rom from your carrier.
Click to expand...
Click to collapse
Hi - I don't have a carrier - I bought the phone on its own, supposedly carrier unlocked, using an existing Three mobile SIM that I have.
Does anyone have any suggestions for a suitable SuperCID I could try?
Super cid (11111111) means you can flash any rom manually, but no OTA update.
If you want OTA updates, you either pick a carrier and use its cid, or use the GPE (Google play edition) cid. GPE means no HTC added stuffs, like sense 6.
Either way, Google for the cid numbers.
ikeny said:
Super cid (11111111) means you can flash any rom manually, but no OTA update.
If you want OTA updates, you either pick a carrier and use its cid, or use the GPE (Google play edition) cid. GPE means no HTC added stuffs, like sense 6.
Either way, Google for the cid numbers.
Click to expand...
Click to collapse
My last phone was a stock HTC which I converted to GPE. I got fed up with the phone and tried to revert to stock, but messed up. While HTC fix that one I'm trying to update this replacement... getting a bit fed up with non stock HTC phones now to say the least!
Will changing my CID to something like HTC__001 and rebooting risk bricking the phone?
My HTC M8 also has S-off, and I have no problem changing the cid to whatever I want with the toolkit on xda.
Running OTA updates, on the other hand, is more risky to me since I didn't know the history of my device. I chose to flash a nandroid backup via TWRP. (No RUU published from my carrier). Then I re-rooted the stock rom, retuned back to stock recovery, removed the "modified/tampered" status, and locked the boot loader. I left the S-off status, which is the only non-stock.
billyboy77 said:
My last phone was a stock HTC which I converted to GPE. I got fed up with the phone and tried to revert to stock, but messed up. While HTC fix that one I'm trying to update this replacement... getting a bit fed up with non stock HTC phones now to say the least!
Will changing my CID to something like HTC__001 and rebooting risk bricking the phone?
Click to expand...
Click to collapse
The guy that sold me the phone suggested I flash this RUU to the phone. It appears to be a Brighstar US RUU... which just confuses me even more.
"i have find a way to fix your problem, its very simple, but requires your attention to the following details
follow what this link tells you
http://www.htc.com/us/support/htc-one-m8/news/"
What did you ask from the seller? Was it just something "stock and unlocked"? The US rom quote was definitely stock. (Sim) unlocked or not is independent of the rom. Your phone could be locked/unlocked regardless of the rom you use.
All unmodified version from HTC are stock, including GPE. You need to first decide which carrier you want your phone to be "stock" for.
billyboy77 said:
The guy that sold me the phone suggested I flash this RUU to the phone. It appears to be a Brighstar US RUU... which just confuses me even more.
"i have find a way to fix your problem, its very simple, but requires your attention to the following details
follow what this link tells you
http://www.htc.com/us/support/htc-one-m8/news/"
Click to expand...
Click to collapse
I've just spoken to someone in HTC USA Customer services - the phone is formerly an AT&T contract phone. She told me that I'm better off returning the phone to the seller if I want regular OTA updates.
So either send it back and be without phone for a week or so, or try and return it to factory stock myself. Tricky one.
ikeny said:
What did you ask from the seller? Was it just something "stock and unlocked"? The US rom quote was definitely stock. (Sim) unlocked or not is independent of the rom. Your phone could be locked/unlocked regardless of the rom you use.
All unmodified version from HTC are stock, including GPE. You need to first decide which carrier you want your phone to be "stock" for.
Click to expand...
Click to collapse
OK so in theory, I could change the CID to Three UK, and find a Three UK RUU and convert the phone into a stock unlocked three UK one that works with my sim...?
billyboy77 said:
OK so in theory, I could change the CID to Three UK, and find a Three UK RUU and convert the phone into a stock unlocked three UK one that works with my sim...?
Click to expand...
Click to collapse
It looks like my best/safest option is installing the Developer edition RUU - but I am on a mac. Does anyone have the correct Zip file of this?
http://www.htc.com/us/support/htc-one-m8/news/
billyboy77 said:
It looks like my best/safest option is installing the Developer edition RUU - but I am on a mac. Does anyone have the correct Zip file of this?
http://www.htc.com/us/support/htc-one-m8/news/
Click to expand...
Click to collapse
I don't think the ROM update exe will run in Mac. You'll need to find a Windows pc for this, or try virtual machine running Windows on your mac.
billyboy77 said:
It looks like my best/safest option is installing the Developer edition RUU - but I am on a mac. Does anyone have the correct Zip file of this?
http://www.htc.com/us/support/htc-one-m8/news/
Click to expand...
Click to collapse
all the files you need to convert to DE are here >> https://www.androidfilehost.com/?a=show&w=files&flid=21320
This guide may be easier to convert to the DE as it used RUU. No custom recovery and s-off required.
http://forum.xda-developers.com/htc-one-m8/development/ruu-m8-developer-edition-sense-1-54-t2884777
billyboy77 said:
Hi
Bricked my old 16gb HTC One M8 - sending to HTC for repair tomorrow.
Ordered a replacement 32gb HTC One M8 from Hong Kong. It was billed as 'new' but on arrival it appears to be S-OFF but locked. Full bootloader details below:
*** LOCKED ***
M8_UL_CA PVT SHIP S-OFF
CID-11111111
HBOOT-3.16.0.0000
RADIO-1.15.2133156.UA13G
OpenDSP-v38.2.2-00542-M8974.0311
OS-1.54.401.5
eMMC-boot 2048MB
Mar 22 2014,00:53:32.16037
Whenever I try to update OTA, it tells me my phone is not stock and the update doesn't install. I just want to get the phone back to stock with the latest OTA firmware, nothing more. What would my best course of action be here?
Click to expand...
Click to collapse
If you ordered it from Mainland region then most sellers do S Off there even if the phone is new but if you wanted S On you could have talked to the seller. It's trend over there before getting a new android phone almost 90% sellers sells S OFF and Rooted new devices in almost all major Smartphone brands.
Edit: Yes, M8_UL_CA is definitely (AT&T) What country do you belong to? If you're based in the US then just run official HTC AT&T RUU and you will be able to get OTA updates in the near future.
maheshpatel said:
If you ordered it from Mainland region then most sellers do S Off there even if the phone is new but if you wanted S On you could have talked to the seller. It's trend over there before getting a new android phone almost 90% sellers sells S OFF and Rooted new devices in almost all major Smartphone brands.
Edit: Yes, M8_UL_CA is definitely (AT&T) What country do you belong to? If you're based in the US then just run official HTC AT&T RUU and you will be able to get OTA updates in the near future.
Click to expand...
Click to collapse
Actually, it is AT&T, T-Mob, plus Telus and Rogers (Canada, I'm on Telus).
I see he is unbranded(?) now. The first answer was assuming.
 @billyboy77 Your radio version is WWE. Sorry I didn't notice that before.
Download the International WWE RUU here.
You will be able to flash this to get to stock since you are S Off and superCID. It will bring you up to the latest firmware. No need for OTAs. Back up anything that is important to you before running the RUU, because it will wipe your device.
hm... Seems like you guys are really trying your hardest to make this more difficult than it needs to be. Having S-OFF he can practically make his device any device he wants it to be, T-Mobile, AT&T, Unlocked, Developer Edition, surely any GSM based carrier/unlocked version.
What's the problem? Unlock Bootloader, Get a custom recovery, Get Root, Change your MID to the one you want, Change your CID to the one you want, Restore a backup for the one you chose, run OTA's...
"OMG I'm S-OFF and bought unlocked but I can't get OTA's because my phone WAS an AT&T and I'm not on AT&T I'm on Three"
:silly:
BerndM14 said:
hm... Seems like you guys are really trying your hardest to make this more difficult than it needs to be. Having S-OFF he can practically make his device any device he wants it to be, T-Mobile, AT&T, Unlocked, Developer Edition, surely any GSM based carrier/unlocked version.
What's the problem? Unlock Bootloader, Get a custom recovery, Get Root, Change your MID to the one you want, Change your CID to the one you want, Restore a backup for the one you chose, run OTA's...
"OMG I'm S-OFF and bought unlocked but I can't get OTA's because my phone WAS an AT&T and I'm not on AT&T I'm on Three"
:silly:
Click to expand...
Click to collapse
After what happened with my last phone, I'd rather not muck about with unlocking, rooting or any of that balls. Just a stock OS with regular updates will do me just fine (until the new HTC comes out anyway)

Can someone please give a stock rom (marshmallow) of HTC One M9

Hi everybody, I have a HTC One M9 with bootloader unlocked and TWRP is installed on it but with S-ON. It's running on lollipop 5.1.
i could not gain S-OFF because i have to pay for it through sunshine application. But the problem is i am living in SENEGAL so there is no paypal. All the rom i have flashed fail to boot. I would like to get back to stock rom, unroot and relock the bootloader so that i can get the OTA update of marshmallow. but I could not find any stock marshmallow online for my phone. i would be very happy if someone can help me with a stock firmware. Here are the informations about my phone:
HTC ONE M9
CID: HTC_621 TWM TW
BOOTLOADER UNLOCKED
S-ON
CURRENTLY RUNNING ON ANDROID 5.1
Set up fastboot and do the command : fastboot getvar all, and report back
Skickat från min HTC One M9 via Tapatalk
mtraore21 said:
Hi everybody, I have a HTC One M9 with bootloader unlocked and TWRP is installed on it but with S-ON. It's running on lollipop 5.1.
i could not gain S-OFF because i have to pay for it through sunshine application. But the problem is i am living in SENEGAL so there is no paypal. All the rom i have flashed fail to boot. I would like to get back to stock rom, unroot and relock the bootloader so that i can get the OTA update of marshmallow. but I could not find any stock marshmallow online for my phone. i would be very happy if someone can help me with a stock firmware. Here are the informations about my phone:
HTC ONE M9
CID: HTC_621 TWM TW
BOOTLOADER UNLOCKED
S-ON
CURRENTLY RUNNING ON ANDROID 5.1
Click to expand...
Click to collapse
Hi mtraore21,
It looks like you've got your CID. Have you looked at Flippy498's Back-to-Stock spreadsheet? It looks like there are some RUU files that might help you.
An important caveat: you'll want to be sure you were flashing a RUU that was a lower version than the firmware you currently have - my understanding is that you'll damage your phone, or at least soft-brick it if you do that.
mtraore21 said:
Hi everybody, I have a HTC One M9 with bootloader unlocked and TWRP is installed on it but with S-ON. It's running on lollipop 5.1.
i could not gain S-OFF because i have to pay for it through sunshine application. But the problem is i am living in SENEGAL so there is no paypal. All the rom i have flashed fail to boot. I would like to get back to stock rom, unroot and relock the bootloader so that i can get the OTA update of marshmallow. but I could not find any stock marshmallow online for my phone. i would be very happy if someone can help me with a stock firmware. Here are the informations about my phone:
HTC ONE M9
CID: HTC_621 TWM TW
BOOTLOADER UNLOCKED
S-ON
CURRENTLY RUNNING ON ANDROID 5.1
Click to expand...
Click to collapse
Have you tried the HTC website? I had a very similiar situation with my phone and downloaded the current ROM from there - an RUU file that all I had to do was double-click to run and it did everything else. My M9 was returned to "factory new" when it finished. I worried myself half to death but it was SOOO simple! Just find your particular "variant" from the website and select "download".
http://www.htc.com/us/support/rom-downloads.html

Unrooting T-Mobile M8 Questions

Hey guys, I know there's a crazy amount of unrooting threads here and everywhere else on the internet, but the more I search the more confused I get. So here's my short situation and my few questions:
Got a T-mobile M8, rooted, S-On, Unlocked, Running S.ROM. I'm trying to do the Tmobile JUMP thing to get the new HTC 10, so I'm trying to unroot this as much as possible. I've found at least 7 different ways with different outcomes on how to do this, so here are my questions:
-I keep reading you can just flash the RUU with no other prerequisites and it'll take your phone back to stock (except for the "Relocked" status). Is this true?
-Follow up to previous question: has anyone had any experience with returning a Relocked phone to Tmobile for their JUMP plan? (Not warranty exchange, I feel they're more strict with that)
-Is the only way to change the Relocked status to Locked by going S-Off with Sunshine and doing all of the 8923479324 steps in order to erase all of the tampered flags?
-What is the BEST method with the BEST outcome to go back to full stock on the M8?
Thanks in advance!
TehAsher said:
-I keep reading you can just flash the RUU with no other prerequisites and it'll take your phone back to stock (except for the "Relocked" status). Is this true?
Click to expand...
Click to collapse
The statement "no other prerequisites" is not specific enough. If you mean stock ROM and/or stock recovery (which folks sometimes think is needed to RUU), its true that neither are needed in order to RUU.
There are however some prerequisites:
1) PC required. Win7 and USB 2.0 for the best compatibility with RUU.
2) RUU needs to be intended for your version (CID and MID)
3) RUU version needs to be greater or equal to main version on the phone (this requirement is bypassed with s-off)
4) Relocked or locked bootloaded (this requirement also bypassed with s-off)
TehAsher said:
-Is the only way to change the Relocked status to Locked by going S-Off with Sunshine and doing all of the 8923479324 steps in order to erase all of the tampered flags?
Click to expand...
Click to collapse
Correct.
TehAsher said:
-What is the BEST method with the BEST outcome to go back to full stock on the M8?
Click to expand...
Click to collapse
T-Mob is not my carrier, and I know nothing of their Jump program. But in most cases, the best bet with returning a phone is to RUU to stock, and make the bootloader LOCKED. Return to s-on (after s-off) is probably not needed.
Thanks for the info! I guess I'll be getting sunshine then and try to follow all of these guides. So if I S-off with sunshine, as long as I check my CID and MID (I got the RUU from the HTC website, but I'll double check it anyways), I can flash that and return to stock. And afterwards I can find a guide on how to reset the tampered flags and the Locked status?
TehAsher said:
And afterwards I can find a guide on how to reset the tampered flags and the Locked status?
Click to expand...
Click to collapse
Yes, that is what I would suggest. Guide on how to make it LOCKED and remove TAMPERED:
http://forum.xda-developers.com/showthread.php?t=2708571
How I went back to stock
I was rooted and running custom ROMS, but when MM came out I wanted to make sure that my firmware/radio was updated. So for me this is what I did
- first I am s-on
- When I unlocked the bootloader, just before I installed TWRP, I made a copy of the recovery. Also I backed up my stock ROM. Both I kept
So to restore:
- I re-installed via TWRP, the stock ROM, and made sure that I didn't root it
- I re-installed the stock recovery
- rebooted and phone saw the MM upgrade and proceeded to upgrade.
If you don't have the recovery/stock ROM you will need to remember what version of android you were on when you overwrote the recovery with TWRP. If your firmware + recovery + OS do not match the update won't work.
-brad
redpoint73 said:
Yes, that is what I would suggest. Guide on how to make it LOCKED and remove TAMPERED:
http://forum.xda-developers.com/showthread.php?t=2708571
Click to expand...
Click to collapse
Awesome, got my phone S-Off. I tried installing the RUU from the HTC website but I got an error and it failed, saying something about I'm using the wrong RUU. This is my CID and MID:
MID: 0P6B13000
CID: T-MOB010
I used this link to get my RUU:
http://www.htc.com/us/support/rom-downloads.html#tmobile
Am I doing something wrong?
TehAsher said:
I tried installing the RUU from the HTC website but I got an error and it failed, saying something about I'm using the wrong RUU. This is my CID and MID:
MID: 0P6B13000
CID: T-MOB010
I used this link to get my RUU:
http://www.htc.com/us/support/rom-downloads.html#tmobile
Am I doing something wrong?
Click to expand...
Click to collapse
What error number? If 155 or 159, you can't RUU from LP to MM (this is a new requirement they added with MM). You either need to flash the 6.20.531.5 full stock firmware from here, then run the RUU again. Or run the T-Mobile LP RUU.

Categories

Resources