Develop Bugs

Changing ROM and FW to go to WWE vs Dev

Hey everyone,
I first want to say thanks for all the instructions here on this one, it's been a lot of searching, but got through getting my phone boot unlocked, TWRP installed, rooted, and finally through Venom, S-OFF.
I bought an M9 from eGlobal Central which landed me a HK phone and Asia ROM. It's also meant that with the subsequent upgrade to the 1.4 firmware package the battery has gone from terrible to paper weight.
I've got Venom on there for the moment (That got me through Sunshine) and I'm looking either at a stock Dev edition or WWE ROM (To get up to a >2.8 firmware), however, I'm wondering where to go now in regards to WWE or Dev. Errr... OK, just correct me where I'm wrong here:
I'll need a firmware package that matches the ROM.
I'm guessing I'll need a complete RUU, but for European Dev perhaps? What's the CID for that?
Actually is there any difference at all in the radio software between the different firmware releases and capabilities?
What is the current Android version in WWE that's available? (And what firmware more to the point, I just want off 1.4)
I've seen Dev is now on Android 5.1 and 2.8 firmware (And I'm guessing this has been patched higher again)
I assume that Dev has a faster release schedule than WWE?
I basically want to get myself back to the point where I'm getting OTA updates, but my phone lasts a day instead of a couple of hours (I should've bought another M8).
I'm sure that this has been done before, but hours of Google searches has left me well, slightly less in the dark, but the light at the end of the tunnel could be an oncoming train, so, thought I'd just ask.
Thanks for all your help,
Berny

You're s-off so just go supercid and you can flash the latest 2.10 firmware. Forget OTAs because you can't get them unless you're 100% stock, and the back and forth required to do it is far more trouble than its worth IMO.
Can't speak for everyone but battery life on 2.x has been fine.
Sent from my HTC One M9 using Tapatalk

iElvis said:
You're s-off so just go supercid and you can flash the latest 2.10 firmware. Forget OTAs because you can't get them unless you're 100% stock, and the back and forth required to do it is far more trouble than its worth IMO.
Can't speak for everyone but battery life on 2.x has been fine.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Exactly...also this is what i did, I had same issue as you and I followed this steps to do it:
DevCID BS_US001
DevMID 0PJA11000 (Dev)
Installed Dev 2.8.617.4 by SDCARD Method Ruu ZIP File
Installed TWRP 2.7.8.1b again.
SuperCID 11111111 (WWE)
Placed BACKUP 2.8.617.4
Flashed WWE FW 2.10.401.1
Flashed any Custom ROm.

Looking for general advice about CIDs, S-OFF, debranding and running RUUs?

Hi, all...
My M8 is bootloader unlocked, rooted (with Chainfire 2.46) and TWRP 2.8.7.0 custom recovery installed, and just recently I spent $25 to acquire S-OFF. Currently, there are no problems or issues with it.
A few days ago, I received the libStageFright (and Lollipop 5.0.2 update) OTA for CID: H3G__001.
(It's available here if anybody wants it.)
I didn't allow it to install for reasons which will become obvious in the next paragraph...
----
From what I've been reading here on XDA over the past few weeks, if rooted, simply unrooting and fastboot flashing the stock recovery isn't sufficient to allow the OTA.
Indeed, the various accounts I've read here on XDA seem to indicate that allowing the OTA causes bootloop/softbrick, remedied only by one of two options...
-----
i) Restoring an unmodified/unrooted NANDROID backup.
- or -
ii) Running an RUU.
-----
The first isn't an option for me, since I can't find an unrooted NANDROID backup for H3G__001. Leaving only the second option, of running an RUU.
(And which is why I bought Sunshine/S-OFF two weeks ago.)
The precise command line arguments don't concern me at the moment. I'm just looking for general clarification on several points of principle before I proceed.
----
I have several general questions...
-- As I understand it, with S-OFF, I can now pretty much flash what I want on my M8.
-- In order for me to run an RUU, I understand I may need to re-write my CID from H3G__001 to [what exactly???]
-----
My M8 is on the 3Mobile network in the United Kingdom.
** Which CID should I choose? What is recommended?
** Or is it obvious I just use Super-CID?
That's Globally Universal... right? Or am I wrong?
Super-CID is better? yes or no?
** What is the difference between a WWE CID and Super-CID? Or am I misunderstanding something here?
** Would my 3Mobile network SIM be recognized on the 3Mobile network once I've changed my CID?
** Would I need to also change my MID to run an RUU, and if so, to what?
** Finally, what RUU should I run?
-----
I'm just looking for general guidance here; some pointers really - I can take care of the fine details myself.
I'm in no immediate hurry to do any of this... patience is my watchword... but I'd like to understand exactly what I'm about to do before I do it.
I'm not concerned about wiping the device, nor am I concerned about loosing root. These are mere trifles. Root can re-acquired and all my data is safely backed up on my laptop... including a TWRP Nandroid of my current setup, should I need it in the event of any foul ups.
---
Apologies if my questions have been dealt with elsewhere and please feel absolutely free to tell me to come back after I've read every post on this forum if you think I'm clueless (...and you probably wouldn't be too far wrong ).
----
My ultimate goal here is simple... I want to 'convert' my M8 into a device I can simply and easily reflash by running an RUU, similar in some regards to reflashing Google Factory stock images on my Nexus 7 or Nexus 9 tablets... and where I don't have to worry about rooting it and then not being able to take the next OTA... and where I can just simply reflash back to stock in the event of some Xposed Module gone wrong... or perhaps maybe after experimenting with some Custom ROMs.
Right now, I don't feel I have complete control of my M8, and acquiring S-OFF was my first step in changing that. I just need some help/advice/pointers in the right direction.
-----
I've spent weeks reading everything I can... But the time is drawing near when I need to stop reading and start doing... I mean, I've paid $25 for S-OFF... I might as well start availing myself of the benefits it confers .
----
Thanks in advance, guys.
Cheers, all...
Rgrds,
Ged.

GedBlake said:
The first isn't an option for me, since I can't find an unrooted NANDROID backup for H3G__001. Leaving only the second option, of running an RUU.
(And which is why I bought Sunshine/S-OFF two weeks ago.)
Click to expand...
Click to collapse
I don't want to comment about other things except the above part.
You can find non-rooted nandroid backup for H3G__001 here : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
You should have asked for the nandroid when you can't find one here : http://forum.xda-developers.com/showpost.php?p=62846028&postcount=5696
In fact the thread is linked in my signature.

ckpv5 said:
I don't want to comment about other things except the above part.
You can find non-rooted nandroid backup for H3G__001 here : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
You should have asked for the nandroid when you can't find one here : http://forum.xda-developers.com/showpost.php?p=62846028&postcount=5696
In fact the thread is linked in my signature.
Click to expand...
Click to collapse
Excellent, and thank you, @ckpv5...
So... I located the 4.20.771.2 Nandroid I needed via your link. Restored it with TWRP 2.8.7.0 with no problems. Fastboot flashed the stock recovery (which I also found via your link ). Allowed the libStageFright+Lollipop 5.0.2 OTA to proceed - again, no problems.
(And it was this part that worried me - any problems, they were going to happen during the OTA update process - a bit nerve wracking to say the least !!)
Rebooted normally, and then booted back into the bootloader and remote booted TWRP from my laptop with <fastboot boot twrp.img>, and created a new unrooted 4.25.771.6 Nandroid in readiness for the next OTA should there be one. Whilst still in TWRP, re-rooted with Chainfire v2.46. Rebooted and re-installed all my apps with Titanium Pro.
The whole procedure took about an hour and a half, maybe a little longer.
-----
I can now rest a little easier, knowing now that although my M8 is rooted, I have both a current unrooted Nandroid AND the current stock recovery safely tucked away on my laptop .
Thank you once again for your help and for your extensive collection of Nandroids and stock recoveries.
Rgrds,
Ged.

No problem ... glad that I could help

Looks like the OP has solved the base problem. And I certainly do not recommend messing with the CID or RUUs at this point.
But academically speaking; just for their info (and any others that may have similar questions and be reading this thread):
GedBlake said:
** Which CID should I choose? What is recommended?
** Finally, what RUU should I run?
Click to expand...
Click to collapse
These questions are sort of circular in nature. Meaning, the RUU you intend to run, determines what you need to change your CID and MID (model ID) to.
Phrased another way, the MID and CID need to match what the RUU is looking for (intended for); or the right MID and SuperCID.
GedBlake said:
** Would my 3Mobile network SIM be recognized on the 3Mobile network once I've changed my CID?
Click to expand...
Click to collapse
Yes, your present carrier will still work. From what I've seen, changing the CID does not "lock" you to that particular network.
From what I understand, a good long while back, SuperCID on this device was related to SIM unlock (but no longer the case, SuperCID will not SIM unlock the phone anymore). But the opposite is not true; to my knowledge, changing the CID will not lock you to a carrier, or prevent you from using another carrier.
GedBlake said:
** Or is it obvious I just use Super-CID?
That's Globally Universal... right? Or am I wrong?
Super-CID is better? yes or no?
** What is the difference between a WWE CID and Super-CID? Or am I misunderstanding something here?
Click to expand...
Click to collapse
The WWE CID (rather, a number of different CIDs) are actual distinct CIDs (although unbranded, and not really "carrier" IDs) which start with HTC__ (HTC__001, etc.). SuperCID is 1111111.
WWE CIDs identify the phone as an unbranded Euro Device. Where SuperCID makes the phone "generic" in that it will "pass" any CID check in an RUU or OTA. In that way (modding perspective), SuperCID can be looked at as "better".
Some folks have stated that SuperCID prevents official OTAs from installing (and that you need an actual CID). But folks smarter than me, I believe have contradicted that statement (OTA is okay with SuperCID).
That's the only possible "downside" that I can think of for SuperCID. And one that I don't believe is true, anyway.

Can executable RUUs be used to downgrade?

There's something that I'm a bit unclear on when it comes to RUUs
Let's say that I'd like to try out the latest Marshmallow release without waiting for the OTA and use the HTC-provided RUU .exe (3.35.617.12)
I'm on a T-Mobile branded M9 and would like to keep WiFi Calling and Visual Voicemail. If I find that I am unable to use these features in the non-branded HTC MM release, will I simply be able to use the T-Mobile branded RUU .exe (2.11.531.19) to revert back or will I be unable to as it's an older version (Android 5.1)
I'm currently still locked and S-ON
I seem to remember downgrades not being possible on my M7 once the hboot was updated to a newer version, but am a bit confused about the specifics of the M9
Thank you, and my apologies if this is a dumb question -- I've done my best to find an answer through searching

You cannot flash RUU that does not match your device variant. In this case, you would need 3.35.531.xx RUU, to try marshmallow. 3.35.617.xx won't install on your phone, unless you S-off and change the variant CID.

But once your phone is S-OFF then you are able to downgrade, too. (Although it doesn't matter whether you use a RUU.zip or a RUU.exe.)

asestar said:
You cannot flash RUU that does not match your device variant. In this case, you would need 3.35.531.xx RUU, to try marshmallow. 3.35.617.xx won't install on your phone, unless you S-off and change the variant CID.
Click to expand...
Click to collapse
Well, now I'm a bit confused as far as variants are concerned. This HTC release page states
This software upgrade comes in the form of two sequential updates. The first update will install software version 2.11.617.180 , which does not include the Android OS upgrades. The following update will install software version 3.35.617.12 , which includes the changes to the Android OS.
Click to expand...
Click to collapse
Am I correct in understanding now that the '617' portion of those two versions is what indicates the device variant? And that my device's variant is '531'?
So then it appears that the only ways for me to try out Marshmallow at this point would be:
1) Wait until HTC/T-Mobile unleash their official release and update via OTA or RUU
2) Unlock my bootloader, flash TWRP, and install whatever ROM I please
3) Unlock bootloader, S-OFF, and RUU as I please
Flippy498 said:
But once your phone is S-OFF then you are able to downgrade, too. (Although it doesn't matter whether you use a RUU.zip or a RUU.exe.)
Click to expand...
Click to collapse
And so long as I'm S-OFF I could use this particular T-Mobile RUU executable to revert back to stock at any point and then re-lock my bootloader, correct? But as long as I'm S-ON, then downgrading is not an option, even using an RUU of the '531' variant?
(bootloader) kernel: lk
(bootloader) product: htc_himaul
(bootloader) version: 1.0
(bootloader) imei: REDACTED
(bootloader) version-main: 2.11.531.19
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440601_86.09.50731G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA12000
(bootloader) cid: T-MOB010
Click to expand...
Click to collapse

Miguel_Lancaster said:
Am I correct in understanding now that the '617' portion of those two versions is what indicates the device variant? And that my device's variant is '531'?
Click to expand...
Click to collapse
Correct. 617 is the SKU for the unlocked/developer edition and 531 belongs to T-Mobile US.
Miguel_Lancaster said:
So then it appears that the only ways for me to try out Marshmallow at this point would be:
1) Wait until HTC/T-Mobile unleash their official release and update via OTA or RUU
2) Unlock my bootloader, flash TWRP, and install whatever ROM I please
3) Unlock bootloader, S-OFF, and RUU as I please
Click to expand...
Click to collapse
1) Correct.
2) You can't flash Android M Sense roms when your phone is using the Android L firmware. So you need to look for the Android L versions of the roms (e.g. ARHD 14.0 or Viper 3.5). Sense-less Android M roms like CM should be fine, though.
3) Correct.
Miguel_Lancaster said:
And so long as I'm S-OFF I could use this particular T-Mobile RUU executable to revert back to stock at any point and then re-lock my bootloader, correct? But as long as I'm S-ON, then downgrading is not an option, even using an RUU of the '531' variant?
Click to expand...
Click to collapse
Correct (both times). Although you should keep in mind that your phone will bootloop if it's not 100% stock and you lock or relock the bootloader. (I personally think there is no benefit in locking/re-locking or even setting S-OFF back to S-ON unless you want to send your phone to HTC for warranty claims.)

asestar said:
2) You can't flash Android M Sense roms when your phone is using the Android L firmware. So you need to look for the Android L versions of the roms (e.g. ARHD 14.0 or Viper 3.5). Sense-less Android M roms like CM should be fine, though.
3) Correct.
Click to expand...
Click to collapse
Hmm, and here I was thinking that ROMS included the firmware and both could be flashed through TWRP. Guess I was mistaken. Or...
asestar said:
Correct (both times). Although you should keep in mind that your phone will bootloop if it's not 100% stock and you lock or relock the bootloader. (I personally think there is no benefit in locking/re-locking or even setting S-OFF back to S-ON unless you want to send your phone to HTC for warranty claims.)
Click to expand...
Click to collapse
Phone was just purchased used, so if there's any warranty period left it probably isn't for very much longer. In the past I've gone S-OFF for all my HTC devices (Incredible, then One S, then One M7) but they've always seemed to have their own unique quirks and this M9 appears to be no different.
My main reasoning for staying S-ON/Stock at the moment is just in case I find a reason to return the device to the seller. After a few days when I'm sure everything is alright with it, I'm sure I'll be less reluctant to tweak.
Is a bootloop easily fixable?
So, to clarify (again!) --
In my phone's current state, I would be limited to Lollipop ROMs when flashing via TWRP?
So then, the shortest route to flashing custom Marshmallow ROMs would be to S-OFF and then RUU to an International Marshmallow firmware? Would I need to change CID manually or is that handled during RUU so long as I'm S-OFF?
And the safest route (in which S-OFF would be completely optional) would be to wait for the T-Mobile OTA release for Marshmallow before unlocking the bootloader and flashing TWRP?
Thanks a bunch for your responses. I'm sure this stuff gets answered all the time, but it can sometimes be difficult to find a specific answer in the depths of these boards. Plus, I find it hard to keep 100% on all development when I only buy a new device every couple of years.
I used the ARHD rom on my last device and quite liked it, but there was a T-Mobile specific variant that kept WiFi calling and all the other carrier-specific stuff. I'm pretty sure the developer has since long given up on maintaining those features., but it's my understanding that ViperOne may still have them.

Miguel_Lancaster said:
Hmm, and here I was thinking that ROMS included the firmware and both could be flashed through TWRP. Guess I was mistaken. Or...
Click to expand...
Click to collapse
The difference between rom and firmware.
Miguel_Lancaster said:
Is a bootloop easily fixable?
Click to expand...
Click to collapse
Just reflash a RUU. The problem for most non-US firmwares is that HTC doesn't provide RUUs so sometimes there is no freely accessible RUU for a specific firmware version. (The only other method besides flashing a RUU is restoring a TWRP backup or re-/flashing a custom rom which needs an unlocked bootloader and TWRP.) If someone decides to re-S-ON and to lock/relock and the rom doesn't boot then that person might not be able to fix that bootloop without this RUU service. (The same applies to S-ON users who decide to relock if the rom doesn't boot.) HTC introduced a new security feature with Android 5.1 (firmware 2.x and higher). It prevents the bootloader unlock if the option OEM Unlock isn't activated in developer options. That's why I recommend everyone staying S-OFF and unlocked unless you need to send your phone back to HTC for a warranty claim since even OTAs can be installed with an unlocked bootloader. Well, RUU.exe deny to flash with S-ON and an unlocked bootloader but there are not many RUU.exe for non-US firmware versions and you can always extract the RUU.zip from a RUU.exe. (RUU.zip files can be flashed via an external SD card even if the bootloader is unlocked.)
Miguel_Lancaster said:
In my phone's current state, I would be limited to Lollipop ROMs when flashing via TWRP?
Click to expand...
Click to collapse
Correct if you're talking about Sense roms.
Miguel_Lancaster said:
So then, the shortest route to flashing custom Marshmallow ROMs would be to S-OFF and then RUU to an International Marshmallow firmware? Would I need to change CID manually or is that handled during RUU so long as I'm S-OFF?
Click to expand...
Click to collapse
Or you use an unlocked/dev edition RUU. There is no big difference between the firmware of those two M9 versions. Nevertheless you need to change both the CID and the MID. The commands are fastboot oem writecid <enterwhicheverCIDisneeded> and fastboot oem writemid <enterwhicheverMIDisneeded>. (SKU 617 - unlocked/dev edition - CID: BS_US002 - MID: 0PJA11000; SKU 401 - international version - CID: HTC__001 - MID: 0PJA10000; SKU 531 - T-Mobile US - CID: T-MOB010 - MID: 0PJA12000)
Miguel_Lancaster said:
And the safest route (in which S-OFF would be completely optional) would be to wait for the T-Mobile OTA release for Marshmallow before unlocking the bootloader and flashing TWRP?
Click to expand...
Click to collapse
Correct.
Miguel_Lancaster said:
I used the ARHD rom on my last device and quite liked it, but there was a T-Mobile specific variant that kept WiFi calling and all the other carrier-specific stuff. I'm pretty sure the developer has since long given up on maintaining those features., but it's my understanding that ViperOne may still have them.
Click to expand...
Click to collapse
Don't know about ARHD but Viper has that feature.
Btw: Getting S-OFF is quite easy but it costs 25 USD. You simply need to use the Sunshine App. (Or you look for someone who has a java card.)

Thank you for taking the time to answer all of my questions.

No problem. Maybe those detailed answers might help other users as well. (That's at least what I hope. )

Flippy498 said:
Or you use an unlocked/dev edition RUU. There is no big difference between the firmware of those two M9 versions. Nevertheless you need to change both the CID and the MID. The commands are fastboot oem writecid <enterwhicheverCIDisneeded> and fastboot oem changemid <enterwhicheverMIDisneeded>. (SKU 617 - unlocked/dev edition - CID: BSUS_002 - MID: 0PJA11000; SKU 401 - international version - CID: HTC__001 - MID: 0PJA10000; SKU 531 - T-Mobile US - CID: T-MOB010 - MID: 0PJA12000)
Click to expand...
Click to collapse
**** --
I changed my MID to the Developer edition, but I accidentally used the letter O and not the number 0 -- so OPJA11000
Then I attempted an RUU and now my phone is stuck in the RUU screen and I can't even turn it off. Is there any way to recover this? I don't even think I can use ADB anymore.
edit: I got it to reboot by holding BOTH volume buttons and POWER. What a stupid mistake. I'll leave this here though so hopefully no one else does anything so stupid.
Yikes :silly:
edit 2: Hmm, changed MID to the correct value but I'm still getting ERROR 131 CUSTOMER ID ERROR during RUU. Will have to investigate this further. Maybe I need to relock the bootloader.
P.S. The command to change the MID actually seem to be writemid, not changemid -- figured that out through trial and error
edit 3: Relocking the bootloader still gives the same error RUU. Now I'm stumped.
edit 4: Turns out the CID should actually be BS_US002, not BSUS_002, as you told me in the earlier reply.
edit 5: Yup, fixing the CID solved the problem

Miguel_Lancaster said:
P.S. The command to change the MID actually seem to be writemid, not changemid -- figured that out through trial and error
Click to expand...
Click to collapse
Ah, sorry. I don't know why I wrote changemid. It wasn't intended. Of course it has to be writemid. I will correct the post.
Miguel_Lancaster said:
Turns out the CID should actually be BS_US002, not BSUS_002, as you told me in the earlier reply.
Click to expand...
Click to collapse
Sinc I don't know every CID by heart I copied it from a CID list I found with google. I'm going to correct that mistake, too. Thanks for clarifying.
Sorry for the hassle.

Flippy498 said:
Ah, sorry. I don't know why I wrote changemid. It wasn't intended. Of course it has to be writemid. I will correct the post.
Sinc I don't know every CID by heart I copied it from a CID list I found with google. I'm going to correct that mistake, too. Thanks for clarifying.
Sorry for the hassle.
Click to expand...
Click to collapse
I didn't brick anything and got it all figured out in the long run, so no worries. I may not have attempted this in the first place without everything explained so concisely by you earlier, so thank you. Hopefully this thread (mistakes and all) can be beneficial to others.
Seriously though, who decided it was a good idea to put a zero before 'PJA' for the CID? That's just asking for trouble.

Miguel_Lancaster said:
I didn't brick anything and got it all figured out in the long run, so no worries. I may not have attempted this in the first place without everything explained so concisely by you earlier, so thank you. Hopefully this thread (mistakes and all) can be beneficial to others.
Seriously though, who decided it was a good idea to put a zero before 'PJA' for the CID? That's just asking for trouble.
Click to expand...
Click to collapse
That whole "0" or "O" bull**** ...
Cost me 3 days of heartache getting errors...
Yeah....that structure is a horrible idea....g

HTC M9 in UK (Verizon) Flash Help?

Hi, i have a HTC M9 bought on eBay which is Verizon... i'm in UK and want to flash the phone using a UK ROM .. is this possible please? The phone is S-Off and unlocked
CID 11111111
Radio [email protected]
Can't see any bootloader version?
Anyone help please?
Still time to send it back and get money back
Thanks

Craig_CFC said:
Hi, i have a HTC M9 bought on eBay which is Verizon... i'm in UK and want to flash the phone using a UK ROM .. is this possible please? The phone is S-Off and unlocked
CID 11111111
Radio [email protected]
Can't see any bootloader version?
Anyone help please?
Still time to send it back and get money back
Thanks
Click to expand...
Click to collapse
If you're on Lollipop, you can use sunshine to unlock and flash away. If on MM, you have to downgrade to LP, and then use sunshine to unlock (this is a cost of 25 USD). There is a thread for the downgrade here in the Verizon forum. As for a rom, I highly recommend LeeDroid, as he makes roms for all M9s, and he is based out of the UK. For that, just go to the HTC One M9 main forum, not the Verizon forum. I'm currently running it and it is fantastic.
Edit: Sorry, totally somehow thought you were locked. Anyway, just make sure you have the latest TWRP and flash any rom you want, but you'll find more activity here:
http://forum.xda-developers.com/one-m9
Roms based on stock (I recommend for stability, signal, and camera) are under "One (M9) Android Development."

Hi,
Thank you for your help .. i'm quite a beginner with this kinda thing.. firstly, the phone already came with TWRP 3.0.0-1 installed, do i need to upgrade that? and which firmware would i use please? i did find a list but forgot to bookmark it.
Thanks again

Craig_CFC said:
Hi,
Thank you for your help .. i'm quite a beginner with this kinda thing.. firstly, the phone already came with TWRP 3.0.0-1 installed, do i need to upgrade that? and which firmware would i use please? i did find a list but forgot to bookmark it.
Thanks again
Click to expand...
Click to collapse
Here's the link for the rom which has instructions for for installation: http://forum.xda-developers.com/one-m9/development/rom-leedroid-one-m9-v7-0-0-rc1-march-t3068468
I can't remember off the top of my head if your recovery is new enough (I believe it is), but here is the thread for TWRP: http://forum.xda-developers.com/one-m9/orig-development/recovery-twrp-touch-recovery-t3066720
If you don't feel comfortable rebooting your phone into different modes and doing some command prompt codes, I'm not sure I'd recommend doing any of this though. Make sure you do your research and read, read, read. Maybe even search YouTube for examples of people flashing TWRP and such.

thank you sending the phone back, will buy a uk version

Newb Needs advice and suggestions

Ok, so I did a little digging around, and it seems like I should be able to handle this. But I would really like some guidance from some experienced developers. I recently bought a certified refurbished factory unlocked m8 from Amazon, and it is branded T-Mobile. I I am a cricket user so I run on the att towers , not that that really matters. I just want to get this thing unbranded , and loaded with the HTC sense and or android software without having any of the T-Mobile screens or apps or any of that. Like it came straight from HTC with no carrier stuff on it. I understand I'll have to root, S off ( whatever that means) and a bunch of other things. I've played with it a little bit, getting into fast boot and recovery mode on the phone itself while not connected to the computer. I have no software that I need for this task, nor any of the roms yet or anything else. I am hoping this community of developers can help me with suggestions for the easiest and quickest way to do this, and then I think I want to relock it, not to a carrier but so that everything stays set until and if I decide I want to do any more with the m8. I want the m8 just stock HTC like fresh off the line, not really sure I need developer mode unlocked on it as far as the rom or what have you. But,I'm not sure, that's why I'm here hoping you guys can help me. And I was looking through the posts about doing this to m8'S so please don't just point me to those, I need some more clarification and basically just a step by step on how to get this done , and then I'll probably be asking for tips on what I can do with the desire 520 , if all goes well with the m8 and it replaces my 520 then I would like to use my 520 to practice and see what all I can do with rooting and modifying everything . Anyways. To recap Please help me get the m8 like I just bought it from HTC with no carrier so only stock HTC software, and I don't know if it still gets updated or not but the ability for ota updates just in case. And locked back up so I can't somehow accidently screw it up. And thanks in advance for all your help and advice everyone
UPDATE
Here is what I see on the screen when I do the volume down and power button when powering on the phone
***software status: official***
***LOCKED***
M8_UL PVT SHIP S-OFF
CID-T-MOB010
HBOOT-3.19.0.0000
RADIO-1.29.213311491.05G
OpenDSP-v51.2.2-00593-M8974_FO.1015
OS-6.20.531.5
eMMC-boot 2048MB
Mar 1 2016,00:59:13.3
Ok guessing I'm in S off mode already based on that and figured that this information would help you guys better inform me of what steps I will need to take .
Does anyone know if loading the newest rom from HTC for unlocked phones will get change the cid and remove the T-Mobile apps or will I need to manually change the cid to something somehow and then load the HTC rom. Please any advice would be very helpful, there is so much content on this site to sift through and I work twelve hour shifts 6 days a week and have a two year old, I am having a tough time finding the time to go through all these posts so any advice on this or please link me to a post that would solve this would be immensely helpful and very appreciated

Nd2learn said:
Does anyone know if loading the newest rom from HTC for unlocked phones will get change the cid and remove the T-Mobile apps or will I need to manually change the cid to something somehow and then load the HTC rom.
Click to expand...
Click to collapse
There are some different approaches you can take. If it's the official HTC RUU (ROM Update Utility) you want to use, you would need to change the phone's CID. Then I would suggest the US Developer's Edition RUU, which is designed for use on AT&T's network (and therefore will have full AT&T band support).
The process will be somewhat involved. Briefly, you'll need to:
1) Setup adb/fastboot and unlock the bootloader: https://forum.xda-developers.com/showthread.php?t=2708571
2) Put custom recovery TWRP 3.1 on the phone: https://twrp.me/devices/htconem8gsm.html
3) Root by flashing SuperSU 2.79 using TWRP: https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
4) Change the CID and MID: https://forum.xda-developers.com/htc-one-m8/general/guide-update-to-official-developer-t3002003
5) Finally, run the 6.12.1540 RUU: http://dl3.htc.com/application/RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4.exe
Another possible method, stop after step 2 above, then flash the ROM from here: https://forum.xda-developers.com/htc-one-m8/development/rom-stock-unlocked-developer-sense-7-t3262894