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.
Related
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
So I have been out of the loop for HTC devices and came to a brick wall known as S-Off for current devices.
I am trying to convert two phones for a friend and he is willing to pay the $25 for each for Sunshine, I want to try FireWater but cannot locate the APK just to try, I am aware of the low percentage of success, but if I can save him $50 I'll give that a try. I want to make both phones STOCK T-Mobile, no Root, DeOdexed, etc. After much reading, found out can't change CID and MID without S-Off
MMS was the main issue not receiving, also them wanting WiFi calling. I have unlocked bootloader and have put a 4.4.2 T-Mobile ROM that works fine, but don't want the "updates" to be a issue. I then tried applying a TWRP Restore of 5.0.1 Lollipop and everything EXCEPT WiFi works, bummer and since I can't flash a radio without S-Off.
So in order:
1) Should I even try FireWater at this point (also, can't locate the APK so if any of you have it PM me please)?
2) Changing CID and MID will allow me to do use the HTC RUU Stock T-Mobile ROM?
3) I want to S-On after I convert, should I or just leave it?
quedijo said:
So I have been out of the loop for HTC devices and came to a brick wall known as S-Off for current devices.
I am trying to convert two phones for a friend and he is willing to pay the $25 for each for Sunshine, I want to try FireWater but cannot locate the APK just to try, I am aware of the low percentage of success, but if I can save him $50 I'll give that a try. I want to make both phones STOCK T-Mobile, no Root, DeOdexed, etc. After much reading, found out can't change CID and MID without S-Off
MMS was the main issue not receiving, also them wanting WiFi calling. I have unlocked bootloader and have put a 4.4.2 T-Mobile ROM that works fine, but don't want the "updates" to be a issue. I then tried applying a TWRP Restore of 5.0.1 Lollipop and everything EXCEPT WiFi works, bummer and since I can't flash a radio without S-Off.
So in order:
1) Should I even try FireWater at this point (also, can't locate the APK so if any of you have it PM me please)?
2) Changing CID and MID will allow me to do use the HTC RUU Stock T-Mobile ROM?
3) I want to S-On after I convert, should I or just leave it?
Click to expand...
Click to collapse
I would s-off an leave s-off. Once s-off. Myself I would change mid/cid with eng-hboot to T-Mobile then fastboot T-Mobile firmware wirh no boot.img an no stock recovery.img an thena T-Mobile stock ROM guessing your not going to find a stock unrooted ROM but maybe if not just remove root. Then I would fastboot the stock recovery an your friends devices should now be T-Mobile m8's stock unrooted.
So I have ended up keeping S-Off since there's no indication that I could 100% S-Off later according to their F.A.Q.
However if anyone else was thinking of doing the same, I did just have to change CID and MID then used the HTC Stock T-Mobile RUU package and it's like a M8 straight out of the T-Mobile store.
In case anyone would want to know, this is the process I did:
1) HTC Stock RUU to start clean as a AT&T M8 (http://www.htc.com/us/support/rom-downloads.html)
2) Followed instructions to unlock Bootloader (http://www.htcdev.com/bootloader/)
3) Used this toolkit to flash TWRP (http://forum.xda-developers.com/showthread.php?t=2699065)
4) Installed and Ran (and paid) Sunshine to S-Off the phone (http://theroot.ninja/download.html)
5) Followed instructions to change CID (http://www.droidviews.com/change-cid-mid-htc-one-devices/) *** ONLY THE CID INSTRUCTIONS *** DIDN'T USE SUPERCID, USED T-MOBILE CID ***
6) Followed instructions to change MID (http://forum.xda-developers.com/showthread.php?t=2708581)
7) Put phone in FastBoot, download and ran the HTC Stock T-Mobile RUU (http://www.htc.com/us/support/rom-downloads.html)
8) Stock, Locked Bootloader, *** Software status: Official *** with S-Off. T-Mobile ROM v.4.20.531.4 (Android Lollipop v.5.0.1)
quedijo said:
So I have ended up keeping S-Off since there's no indication that I could 100% S-Off later according to their F.A.Q.
However if anyone else was thinking of doing the same, I did just have to change CID and MID then used the HTC Stock T-Mobile RUU package and it's like a M8 straight out of the T-Mobile store.
In case anyone would want to know, this is the process I did:
1) HTC Stock RUU to start clean as a AT&T M8 (http://www.htc.com/us/support/rom-downloads.html)
2) Followed instructions to unlock Bootloader (http://www.htcdev.com/bootloader/)
3) Used this toolkit to flash TWRP (http://forum.xda-developers.com/showthread.php?t=2699065)
4) Installed and Ran (and paid) Sunshine to S-Off the phone (http://theroot.ninja/download.html)
5) Followed instructions to change CID (http://www.droidviews.com/change-cid-mid-htc-one-devices/) *** ONLY THE CID INSTRUCTIONS *** DIDN'T USE SUPERCID, USED T-MOBILE CID ***
6) Followed instructions to change MID (http://forum.xda-developers.com/showthread.php?t=2708581)
7) Put phone in FastBoot, download and ran the HTC Stock T-Mobile RUU (http://www.htc.com/us/support/rom-downloads.html)
8) Stock, Locked Bootloader, *** Software status: Official *** with S-Off. T-Mobile ROM v.4.20.531.4 (Android Lollipop v.5.0.1)
Click to expand...
Click to collapse
Nothing against the way you did it at all. But using toolkits are very bad idea I have seen many things go wrong an have fix phones soft brick after toolkit/app to flash. Just a friendly tip... An if you don't want to wipe your whole device you can use the way I stated above but glad you are converted. An good choice to keep s-off. Once you r s-off I would never turn s-on again for any reason..Also glad it went smooth for you
Thanks. I've never had an issue with Toolkits, I can see where things would go wrong, but I don't rely on them fully. I am aware it's all pretty much ADB or FastBoot commands that you're running. I like them for confirmation of commands or just as simple click, wait, done.
I'm invested in the Samsung and Sony family now and was a HTC guy in the early days of their product, back when WM6.1 only had RUU options. I actually prefer Odin stuff, which is why I prefer RUU's still, directly to hardware, so have to triple check what I'm doing. I have yet to brick a phone, of course that's thanks to having Download Mode/FastBoot as a final option
quedijo said:
So I have ended up keeping S-Off since there's no indication that I could 100% S-Off later according to their F.A.Q.
However if anyone else was thinking of doing the same, I did just have to change CID and MID then used the HTC Stock T-Mobile RUU package and it's like a M8 straight out of the T-Mobile store.
In case anyone would want to know, this is the process I did:
1) HTC Stock RUU to start clean as a AT&T M8 (http://www.htc.com/us/support/rom-downloads.html)
2) Followed instructions to unlock Bootloader (http://www.htcdev.com/bootloader/)
3) Used this toolkit to flash TWRP (http://forum.xda-developers.com/showthread.php?t=2699065)
4) Installed and Ran (and paid) Sunshine to S-Off the phone (http://theroot.ninja/download.html)
5) Followed instructions to change CID (http://www.droidviews.com/change-cid-mid-htc-one-devices/) *** ONLY THE CID INSTRUCTIONS *** DIDN'T USE SUPERCID, USED T-MOBILE CID ***
6) Followed instructions to change MID (http://forum.xda-developers.com/showthread.php?t=2708581)
7) Put phone in FastBoot, download and ran the HTC Stock T-Mobile RUU (http://www.htc.com/us/support/rom-downloads.html)
8) Stock, Locked Bootloader, *** Software status: Official *** with S-Off. T-Mobile ROM v.4.20.531.4 (Android Lollipop v.5.0.1)
Click to expand...
Click to collapse
Hi, I just gained access to my bootloader, rooted my phone, bought sunshine and was able to get the phone to S-off, Changed my CID and MID and got the most current RUU from T-Mobile and am flashing now! initially the dialog box that pops up advises that it will take 10 minutes or more...well I am at about 2 hours now and the flash is still not completed...how long does this take????....
quedijo said:
So I have ended up keeping S-Off since there's no indication that I could 100% S-Off later according to their F.A.Q.
However if anyone else was thinking of doing the same, I did just have to change CID and MID then used the HTC Stock T-Mobile RUU package and it's like a M8 straight out of the T-Mobile store.
In case anyone would want to know, this is the process I did:
1) HTC Stock RUU to start clean as a AT&T M8 (http://www.htc.com/us/support/rom-downloads.html)
2) Followed instructions to unlock Bootloader (http://www.htcdev.com/bootloader/)
3) Used this toolkit to flash TWRP (http://forum.xda-developers.com/showthread.php?t=2699065)
4) Installed and Ran (and paid) Sunshine to S-Off the phone (http://theroot.ninja/download.html)
5) Followed instructions to change CID (http://www.droidviews.com/change-cid-mid-htc-one-devices/) *** ONLY THE CID INSTRUCTIONS *** DIDN'T USE SUPERCID, USED T-MOBILE CID ***
6) Followed instructions to change MID (http://forum.xda-developers.com/showthread.php?t=2708581)
7) Put phone in FastBoot, download and ran the HTC Stock T-Mobile RUU (http://www.htc.com/us/support/rom-downloads.html)
8) Stock, Locked Bootloader, *** Software status: Official *** with S-Off. T-Mobile ROM v.4.20.531.4 (Android Lollipop v.5.0.1)
Click to expand...
Click to collapse
Funny I can get to step 7, but when I do step 7, I get ERROR [159] Image Error
Hello ,
I have an HTC M8 ( HTC__203 CID ) and i want to bring it back to fully stock. Lock my bootloader and install official ROM.
I follow this GUIDE but i have to be s-off in order to finish it.
http://forum.xda-developers.com/show....php?t=2735235
How can i turn my m8 to S-OFF from S-ON ?
I cant pay SUNSHINE 25$ ..
Is there any other way?
Or any way to lock my bootloader?
Without s-off you can put the flag from UNLOCKED to RELOCKED
only with s-off you can let it show LOCKED. sunshine is the only real (and cheapest) way to s-off the device. No other method available.
The nearest you can get to stock is to run the appropriate RUU with a relocked bootloader. Or restore the matching stock nandroid backup for your device and flash back the stock recovery, then relock the bootloader.
That's about it. Ow yeah and please post questions in the Q&A section next time. This is the GENERAL section.
alexis333 said:
I have an HTC M8 ( HTC__203 CID ) and i want to bring it back to fully stock.
Click to expand...
Click to collapse
The only real reason to return the phone to full stock with LOCKED bootloader is for warranty purpose. Is that what you are trying to do?
If so, then sunshine is the only way to s-off.
redpoint73 said:
The only real reason to return the phone to full stock with LOCKED bootloader is for warranty purpose. Is that what you are trying to do?
If so, then sunshine is the only way to s-off.
Click to expand...
Click to collapse
Yeah something like that. I want to sell it so the person who will take it to have full warranty access.
Thanx both of you. The problem is that in Greece ( where i live ) i dont have the access to my paypal in order to pay Sunshine because of Bank System.
We have Capital Controls so we cant buy anything from outside of our country.
Mr Hofs said:
Without s-off you can put the flag from UNLOCKED to RELOCKED
only with s-off you can let it show LOCKED. sunshine is the only real (and cheapest) way to s-off the device. No other method available.
The nearest you can get to stock is to run the appropriate RUU with a relocked bootloader. Or restore the matching stock nandroid backup for your device and flash back the stock recovery, then relock the bootloader.
That's about it. Ow yeah and please post questions in the Q&A section next time. This is the GENERAL section.
Click to expand...
Click to collapse
So whats the proper RUU to flash. And how can i flash it in relocked bootloader ?
I tried this -> 0P6BIMG_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10_Radio_1.25.214500021.06G_20.68.4196t.01_F_release_417809_signed
and this one -> One_M8_4.16.401.10_stock_system_dump.zip
but after i type " fastboot flash zip ruu.zip " in the end it shows me this error -> 12 signature verify fail
What does it mean ?
Hello to everyone!
I have HTC M8(second hand...) I check the IMEI and i see is from Australia - Sold to Singapore. I don't know if it means something.
It was unlocked bootloader and modified software(Custom ROM-android 6), S-OFF and CID was 11111111(I don't know what was the original CID, because this is how i bought the phone)
I decided to get it back to stock. I found a few threads about how to get the HTC M8 fully stock, but nothing works for now. l have the the stock recovery, stock boot.img and locked the bootloader.
When i installed/restored from the RUU file it was ok. When i check for updates it's downloading, but cannot install.
There is a message:
'Variant system version - We have determined that your phone may be running a modified version of its system software. For your protection, we cannot update your phone. Please revert your phone to the official HTC system software to update your phone. If you did not modify your system software or would like help reverting your system please contact us via the support section at HTC - Mobile Phones, Smartphones, Cell Phones, Tablets'
I'm sure i have official software, stock recovery and boot.img, but i have no idea why this message appears.
Right now i am using InsertCoin ROM and i have noticed the message, that tells "Software status: Modified or Official" Mine tells always OFFICIAL. No matter if i have installed insertcoin or stock rom.
Here is the infor from my bootloader:
***Software status: Official*** (Just to remind... I'm with insertcoin rom)
***UNLOCKED***
M8_UL PVT SHIP S-OFF
CID - 11111111
HBOOT-3.19.0.0000
RADIO-1.25.214500021.06G
OpenDSP-v48.2.2-00564-M8974_FO.1211
OS-4.16.401.10
eMMC-boot 2048MB
Jan 15 2015, 22:51:08.0
Can anyone tell me how to download the official updates?
(sorry for my english)
No one can help with this ?
Jared89 said:
I decided to get it back to stock. I found a few threads about how to get the HTC M8 fully stock, but nothing works for now. l have the the stock recovery, stock boot.img and locked the bootloader.
Click to expand...
Click to collapse
None of that includes an actual stock ROM, which is required to OTA.
Jared89 said:
When i installed/restored from the RUU file it was ok. When i check for updates it's downloading, but cannot install.
Click to expand...
Click to collapse
You're sure the RUU installed correctly, with no errors?
Did you try to update immediately after RUU, with not mods at all (unlocking the bootloader, root, custom ROM)?
redpoint73 said:
None of that includes an actual stock ROM, which is required to OTA.
You're sure the RUU installed correctly, with no errors?
Did you try to update immediately after RUU, with not mods at all (unlocking the bootloader, root, custom ROM)?
Click to expand...
Click to collapse
Yes. I have no errors during the installing process and after that...
And yes... I try to update immediately after the phone boot to the home screen. I have no idea how to fix this. With my previous HTC M8 i was using the same custom rom(InsertCoin) and when i decidet to go back to stock, all i was doing is to lock the bootloader and install the RUU. Then i'm able to get the updates with no problems.
Jared89 said:
when i decidet to go back to stock, all i was doing is to lock the bootloader and install the RUU. Then i'm able to get the updates with no problems.
Click to expand...
Click to collapse
Yes, its strange. RUU by definition should put you on a fully stock image, and therefore allow OTA updates.
You can try to RUU straight to 6.12.401: http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Curious to see if you get the same error with that RUU.
redpoint73 said:
Yes, its strange. RUU by definition should put you on a fully stock image, and therefore allow OTA updates.
You can try to RUU straight to 6.12.401: http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Curious to see if you get the same error with that RUU.
Click to expand...
Click to collapse
I was trying this a few times. It says there is not enough space or something. C
I'm still looking for solution. Any suggestion is welcome!
Are you still S-OFF? On the M9 one hast to change the CID from SuperCID (11111111) back to a WWE CID to take the update to MM, as HTC uses a new routine to check the state of the phone.
In your case you'd have to reboot to fastboot mode, open a command prompt and change the CID to HTC__001 (8 digits!!) by using the command "fastboot oem writecid HTC__001"
Send by the swarm intelligence of my coffee machine ?.
Yes, i'm still S-OFF.
Thanks! I will try it and i will let you know if it works.
HTCNerdYoda said:
Are you still S-OFF? On the M9 one hast to change the CID from SuperCID (11111111) back to a WWE CID to take the update to MM, as HTC uses a new routine to check the state of the phone.
In your case you'd have to reboot to fastboot mode, open a command prompt and change the CID to HTC__001 (8 digits!!) by using the command "fastboot oem writecid HTC__001"
Send by the swarm intelligence of my coffee machine .
Click to expand...
Click to collapse
I just try your method, but when i try to get it back to stock with RUU.exe i get Error 130, which means is a wrong device. I gues i will have to get back the super CID?
Jared89 said:
I just try your method, but when i try to get it back to stock with RUU.exe i get Error 130, which means is a wrong device. I gues i will have to get back the super CID?
Click to expand...
Click to collapse
Which RUU are you using? In case of an x.xx.401.x RUU it is indeed WWE. Thus the CID should be HTC__001 or HTC__102.
maybe you should tray to RUU with the later one and if it doesn't work go back to SuperCID.
Send by the swarm intelligence of my coffee machine ?.
HTCNerdYoda said:
Which RUU are you using? In case of an x.xx.401.x RUU it is indeed WWE. Thus the CID should be HTC__001 or HTC__102.
maybe you should tray to RUU with the later one and if it doesn't work go back to SuperCID.
Send by the swarm intelligence of my coffee machine .
Click to expand...
Click to collapse
4.16.401.10 Europe.
I can't use the latest RUU, because is only on ZIP file. When i try to install it with fastboot it says there is no space or something.
You could rename the RUU zip to 0P6BIMG.zip and copy it to the root direction of a - at max - 32GB microSD card that has been formatted to fat32.
Insert this SD into your M8 and reboot to bootloader. It will then recognize the RUU and start to flash it automatically.
After a full flash you got to take the SD Card out again, to prevent it to start again during the next reboot
Send by the swarm intelligence of my coffee machine ?.
HTCNerdYoda said:
You could rename the RUU zip to 0P6BIMG.zip and copy it to the root direction of a - at max - 32GB microSD card that has been formatted to fat32.
Insert this SD into your M8 and reboot to bootloader. It will then recognize the RUU and start to flash it automatically.
After a full flash you got to take the SD Card out again, to prevent it to start again during the next reboot
Send by the swarm intelligence of my coffee machine .
Click to expand...
Click to collapse
I'll try this later. Just flashed the RUU(4.16.401.10_Europe), but even with CID HTC__02 i get "Variant system version" message...
Jared89 said:
I'll try this later. Just flashed the RUU(4.16.401.10_Europe), but even with CID HTC__02 i get "Variant system version" message...
Click to expand...
Click to collapse
Sure you took HTC__02, as it hast to have 8 digits and thus HTC__102. In case it doesn't help return to SuperCID 11111111.
Send by the swarm intelligence of my coffee machine ?.
HTCNerdYoda said:
Sure you took HTC__02, as it hast to have 8 digits and thus HTC__102. In case it doesn't help return to SuperCID 11111111.
Send by the swarm intelligence of my coffee machine .
Click to expand...
Click to collapse
Nothing works for now. I bring it back to InsertCoin rom.
My phone is from Singapore, so i might need the correct RUU for it. I have no idea!
Jared89 said:
Nothing works for now. I bring it back to InsertCoin rom.
My phone is from Singapore, so i might need the correct RUU for it. I have no idea!
Click to expand...
Click to collapse
Your problem is not the SuperCID 11111111 but wrong MID for the ROM that you installed.
To run a EU RUU x.xx.401.x, the MID must be 0P6B10000
You said your device is from Singapore, most probably the MID is 0P6B11000 and that's the reason for your "Variant System Version" error.
You can check your current MID by running command fastboot getvar mid
And for S-Off, there is no need to relock bootloader for OTA or running a RUU.
ckpv5 said:
Your problem is not the SuperCID 11111111 but wrong MID for the ROM that you installed.
To run a EU RUU x.xx.401.x, the MID must be 0P6B10000
You said your device is from Singapore, most probably the MID is 0P6B11000 and that's the reason for your "Variant System Version" error.
You can check your current MID by running command fastboot getvar mid
And for S-Off, there is no need to relock bootloader for OTA or running a RUU.
Click to expand...
Click to collapse
Didn't think about that. MID is 0P6B11000, as you said. I have changed it to 0P6B10000. I'll try later if i get the updates. Thanks a lot for the info!
Ok, when i changed MID the problem was solved! Now i get all the updates! Thanks a lot!
I followed instructions from this post:
http://forum.xda-developers.com/showthread.php?t=2708581
Hi everybody,
I'm sorry, I'm sure this question may be asked so much time, but after 1 hour searching I don't find anything usefull for me... (Maybe a keywork issue ?)
I don't know what I've done, but after I locked again the bootloader in order to flash on a RUU, I blocked my HTC 10 and can't boot on android again.
When I tried it the phone is only going to bootloader mode and don't want to get to my Os. I have TWRP and was on the custom LeeDroid 7.0.
I can't backup or do anything and while i try the dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota on the terminal, it won't work...
And I can't unlock again the phone, I've tried and it's "relocked".
Has someone have the same issues ? Really need your help ! :crying:
Thank you !
Why did you even lock the bootloader to flash a RUU? Is that mandatory? Sticking with Lee is always a better idea .
You might wanna try using a RUU.exe to get your OS back. What firmware and model do you currently have?
bamidrol said:
Why did you even lock the bootloader to flash a RUU? Is that mandatory? Sticking with Lee is always a better idea .
Click to expand...
Click to collapse
Yes it was lol...
But i've read that it was better to be on a locked bootloader to flash ruu :crying:
Yes, you need to lock the bootloader to flash an RUU.
Some people like custom roms, some want to go back to stock.
From the bootloader you can go to download mode and get the unlock token and try the process again to unlock, I would guess. Beyond that, I'm assuming the RUU screwed up somewhere. It is generally not possible to flash an RUU unless the phone matches the RUU's CID and MID parameters. And if it didnt work, the RUU wont have gotten far enough to do any damage.
silegeek said:
Yes, you need to lock the bootloader to flash an RUU.
Some people like custom roms, some want to go back to stock.
From the bootloader you can go to download mode and get the unlock token and try the process again to unlock, I would guess. Beyond that, I'm assuming the RUU screwed up somewhere. It is generally not possible to flash an RUU unless the phone matches the RUU's CID and MID parameters. And if it didnt work, the RUU wont have gotten far enough to do any damage.
Click to expand...
Click to collapse
I've re-unlocked the phone but it won't install the ruu but i think i've made the good RUU choice from the HTC website (was this one : on the website HTC us/support/htc-10-t-mobile/news/)
And i got an error 155 (ERROR UPDATING IMAGE) can't update your android phone.
But i've checked and i'm CID: T-MOB101 | MID: 2PS620000 on my HTC 10 ...
silegeek said:
Yes, you need to lock the bootloader to flash an RUU.
Some people like custom roms, some want to go back to stock.
From the bootloader you can go to download mode and get the unlock token and try the process again to unlock, I would guess. Beyond that, I'm assuming the RUU screwed up somewhere. It is generally not possible to flash an RUU unless the phone matches the RUU's CID and MID parameters. And if it didnt work, the RUU wont have gotten far enough to do any damage.
Click to expand...
Click to collapse
so you can't flash ruu with a unlocked bootloader?? thats odd...people use rru to get back to stock after running custom rom and you shouldn't lock bootloader with custom firmware bc it supposedly bricks you...or is download mode still operatable?
edit: i just flashed an ruu to check and can confirm ruu worked with unlocked bootloader and s-on.
Tech_Savvy said:
so you can't flash ruu with a unlocked bootloader?? thats odd...people use rru to get back to stock after running custom rom and you shouldn't lock bootloader with custom firmware bc it supposedly bricks you...or is download mode still operatable?
edit: i just flashed an ruu to check and can confirm ruu worked with unlocked bootloader and s-on.
Click to expand...
Click to collapse
Fair enough, advice I followed at the time suggested I relock bootloader to do an RUU. Being S-ON or OFF doesn't matter.
However, since there was no RUU for my CID (H3G__001) I had to S-OFF in order to change my CID to WWE (HTC__001) to flash that RUU. My phones status at the time was S-OFF, Relocked. It worked fine. It also worked fine under those same conditions after I changed my CID to BS_US001 and MID to 2PS6500000.
---------- Post added at 04:26 AM ---------- Previous post was at 04:24 AM ----------
hadory said:
I've re-unlocked the phone but it won't install the ruu but i think i've made the good RUU choice from the HTC website (was this one : on the website HTC us/support/htc-10-t-mobile/news/)
And i got an error 155 (ERROR UPDATING IMAGE) can't update your android phone.
But i've checked and i'm CID: T-MOB101 | MID: 2PS620000 on my HTC 10 ...
Click to expand...
Click to collapse
Isn't the US MID 2PS650000?
so you can't flash ruu with a unlocked bootloader?? thats odd...people use rru to get back to stock after running custom rom and you shouldn't lock bootloader with custom firmware bc it supposedly bricks you...or is download mode still operatable?
Click to expand...
Click to collapse
The download mode works, bootloader too
I'm not able to flash with an unlocked or a locked bootloader, i've tried the RUU and the custom ROM like Leedroid for example.
Fair enough, advice I followed at the time suggested I relock bootloader to do an RUU. Being S-ON or OFF doesn't matter.
However, since there was no RUU for my CID (H3G__001) I had to S-OFF in order to change my CID to WWE (HTC__001) to flash that RUU. My phones status at the time was S-OFF, Relocked. It worked fine. It also worked fine under those same conditions after I changed my CID to BS_US001 and MID to 2PS6500000.
Click to expand...
Click to collapse
Isn't the US MID 2PS650000?
Click to expand...
Click to collapse
I don't think it's the US MID, my IMEI is German and the phone works great on 4G / LTE in France (where I live) and i've read that 4G won't work with an US version in France, but maybe you're true and their is no RUU for my version ... (fragmentation pleasures).
Do you know how i can s-off this phone in order to change those CID which block me ? ^^' because i can't use sunshine bc no OS installed and can't flash one ...
In fact, the only think i can flash / unflash is TWRP and the recovery stock..