Develop Bugs

Converting AT&T M8 to T-Mobile

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

Confused with update saga

Hello all I am new and so apologies if this is in the wrong place or is just a stupid question.
I have just got myself a new HTC OneM8 and was concerned that it does not see any updates as it is still on 4.4.2 i would have thought that it would at least see sence 7 or even lollipop by now if not Marshmellow yet
I went into the boot screen (fastboot off, power + vol down) and this is what i see: It is sim free and I am on Virgin UK
*** Software status: Official ***
*** LOCKED ***
M8_WHL PVT SHIP S-OFF
CID-11111111
HBOOT-3.19.0.0000
RADIO-1.09.20.0209
OpenDSP-v38.2.2-00542-M8974.0311
OS-1.54.651.8
eMMC-boot 2048MB
Aug 4 2015,19:05:23.3
My question to you guys is can this be updated? should it see the updates?
or is it a bad phone (i can send it back if needed for a refund)
Thx in advance for any help on this matter cheers all

If you can send it back for a refund or for another phone, do it.
It is not a bad phone but not suitable for you at where you are located now.
That's a Sprint US device and the official update will come only when you're on Sprint US network, not on any other SIM free network.
And yes .. you post this in wrong section, I'll ask moderator to move this to Q&A section

ckpv5 said:
If you can send it back for a refund or for another phone, do it.
Click to expand...
Click to collapse
I agree with the above that this is the worst version of the M8 to have (along with the Verizon version) if you aren't located in the US and on that actual network (Sprint or Verizon) for the following reasons:
1) Excessive carrier branding and bloatware common to most US branded devices
2) This version can't be fully converted to Euro version or any other version (to change radio baseband, OTA updates, etc.)
3) Can't flash many ROMs, unless they specifically support the Sprint version; or you install the proper kernel
Although points 2 and 3 above are mostly only relevant if you intend to mod the phone.
If the phone supports all the bands your carrier uses (3G, LTE) and you don't mind the Sprint branding,
you can still update it by RUU, with download link and instruction on the bottom of the following support page (be aware that RUU will wipe the whole phone):
http://www.htc.com/us/support/htc-one-m8-sprint/news/

Thank you. I was sure it had something to do with Sprint as under the current user in settings/about it is listed as [email protected]
thanks again for the speedy reply much appreciated I will send it back and get a UK version
Cheers
Funny I did try the update in that link and it failed

knocker221 said:
Funny I did try the update in that link and it failed
Click to expand...
Click to collapse
If it was Error 155, you need to flash the firmware.zip, then RUU (quirk with MM RUU).
But as you are returning the phone, I'd just not mess with it. Above is just an FYI, as it is confusing why the RUU that matches your version would fail.

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.

Revert unlocked HTC 10 that was converted to a Verizon HTC 10 back to US unlocked?

I got a red HTC 10 back when they first came out and, being on Verizon, knew I'd have to chance CID and all that to Verizon and flash a Verizon RUU in order to get it work. It all worked just fine and I haven't had any issues since following this guide - https://forum.xda-developers.com/verizon-htc-10/how-to/guide-convert-unlocked-to-verizon-t3380615. Currently my 10 is running a custom ROM with Verizon settings, is S-Off and has the bootloader unlocked.
Now, I'm considering selling this device, but need to return it to the US unlocked firmware, radios, etc. before I do (I am planning on keeping S-off and bootloader unlocked for selling it). I assume all I need to do is follow the steps that got me there in reverse, essentially. But I have a few questions before I attempt this:
1) I'm not sure which CID I should use?
2) After changing the CID back, do I just flash the US unlocked RUU and I'm good to go?
Thanks.

1) CID: BS_US001 or BS_US002
2) correct

You might want to consider selling it as is. I sold a red unlocked converted to Verizon on eBay and it sold pretty quickly. This was last month.

S-Off, Unlocked - No OTA

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