Develop Bugs

[Q] I got the indian m8, Am i limited to anything in regards to flashing?

Hi, I bought an unlocked htc one m8 but i recieved the indian version (m8q) and I'm not from india, Everything works fine and I called htc and they told me that I shouldn't have a problem since the indian verison comes with international warrenty.
The only thing I'm worried about here is compatibility with the stuff here on xda, will i be able to flash roms without probelms and will i be able to convert it to a gpe device if i wanted to.
The Cid is HTC__038, the model id is 0P6B65000 the software version i have currently is 1.56.720.6 and the product name (from the getvar all command) is m8_ul. Is the hardware incompatible with roms made for the international gsm version (with the sku 401) or can i just change the cid/mid or make it supercid to use it with any of the guides hosted here.
I havent been able to find anything so i would really appreciate any help.

I own the same device and to be true, the Indian Variant lacks support for all Sense based ROMs as they are based on different model with different CID and MID number. Custom ROMs work fine.
If you are very proficient with flashing stuff in HTC devices then you can use firewater to S-OFF on 4.4.2 . Ver. 4.4.3 has patched some vulnerabilities that do not allow firewater S-OFF to work nor the sunshine one.
I had already updated to 4.4.3 due to which now it's currently impossible for me to obtain S-OFF.
Also Indian Variants have yet not received the latest updates i.e. 4.4.4

Mayank7795 said:
I own the same device and to be true, the Indian Variant lacks support for all Sense based ROMs as they are based on different model with different CID and MID number. Custom ROMs work fine.
If you are very proficient with flashing stuff in HTC devices then you can use firewater to S-OFF on 4.4.2 . Ver. 4.4.3 has patched some vulnerabilities that do not allow firewater S-OFF to work nor the sunshine one.
I had already updated to 4.4.3 due to which now it's currently impossible for me to obtain S-OFF.
Also Indian Variants have yet not received the latest updates i.e. 4.4.4
Click to expand...
Click to collapse
Thanks for the reply, but are you saying that If i can acheive s-off and change the cid and mid will that make the device compatible with the roms or will flashing them brick my device? Also, do you have any idea about compatibilty with gpe based roms?

tinclan said:
Thanks for the reply, but are you saying that If i can acheive s-off and change the cid and mid will that make the device compatible with the roms or will flashing them brick my device? Also, do you have any idea about compatibilty with gpe based roms?
Click to expand...
Click to collapse
This is my first HTC device and the first expensive one that I bought so I am being really cautious about tampering my phone.
Yes, if you achieve S-OFF, then you can change your CID. Don't know about MID (I have yet to know more about it). Then flashing other Sense-based ROMs should be fairly easy.
But after you achieve S-OFF, you need to be more cautious while flashing anything as the security would have been totally put off and whichever file you flash will be flashed without any error and may result in your device getting bricked if a wrong file is flashed.
It will be really great to backup the important partitions like recovery, boot, system etc. if you are still stock (not bootloader unlocked and not rooted)
To backup important partitions, visit this thread for instructions. (Be sure to backup your stock recovery as it will be needed to receive OTA updates) - http://forum.xda-developers.com/showthread.php?t=2701376
IMPORTANT: Read the Question "How do i backup the stock HTC recovery ?" and the procedure below that in the provided thread properly to successfully backup your device's partition.
~~Other Helpful threads which needs a reading~~
♦ HTC One M8 F.A.Q's
♦ HTC ONE M8 Repository

Mayank7795 said:
This is my first HTC device and the first expensive one that I bought so I am being really cautious about tampering my phone.
Yes, if you achieve S-OFF, then you can change your CID. Don't know about MID (I have yet to know more about it). Then flashing other Sense-based ROMs should be fairly easy.
But after you achieve S-OFF, you need to be more cautious while flashing anything as the security would have been totally put off and whichever file you flash will be flashed without any error and may result in your device getting bricked if a wrong file is flashed.
It will be really great to backup the important partitions like recovery, boot, system etc. if you are still stock (not bootloader unlocked and not rooted)
To backup important partitions, visit this thread for instructions. (Be sure to backup your stock recovery as it will be needed to receive OTA updates) - http://forum.xda-developers.com/showthread.php?t=2701376
IMPORTANT: Read the Question "How do i backup the stock HTC recovery ?" and the procedure below that in the provided thread properly to successfully backup your device's partition.
~~Other Helpful threads which needs a reading~~
♦ HTC One M8 F.A.Q's
♦ HTC ONE M8 Repository
Click to expand...
Click to collapse
This is my first htc phone too, actually this is my first high end android phone. I am just as paranoid about doing anything as you, i just wanted to make sure i'm not stuck forever, because i it was impossible to change the software of this phone i would've just sold it from now, purely because imo new software adds the most value to smartphone these days. I am a bit confused, but for now i decided to not install any updates until i figure out whats possible to do without screwing up myself

tinclan said:
This is my first htc phone too, actually this is my first high end android phone. I am just as paranoid about doing anything as you, i just wanted to make sure i'm not stuck forever, because i it was impossible to change the software of this phone i would've just sold it from now, purely because imo new software adds the most value to smartphone these days. I am a bit confused, but for now i decided to not install any updates until i figure out whats possible to do without screwing up myself
Click to expand...
Click to collapse
That's a good decision for now..
I did the mistake of not backing up recovery partition after I updated and instantly unlocked and rooted my phone but luckily I got the stock recovery from another thread.

tinclan said:
This is my first htc phone too, actually this is my first high end android phone. I am just as paranoid about doing anything as you, i just wanted to make sure i'm not stuck forever, because i it was impossible to change the software of this phone i would've just sold it from now, purely because imo new software adds the most value to smartphone these days. I am a bit confused, but for now i decided to not install any updates until i figure out whats possible to do without screwing up myself
Click to expand...
Click to collapse
Mayank7795 said:
That's a good decision for now..
I did the mistake of not backing up recovery partition after I updated and instantly unlocked and rooted my phone but luckily I got the stock recovery from another thread.
Click to expand...
Click to collapse
Thanks for all the help. I have one last question if you wouldnt mind answering, are all the gpe based rooms compatible with our version of the device, and can i flash the gpe ruu without bricking the thing if i got s-off.

tinclan said:
Thanks for all the help. I have one last question if you wouldnt mind answering, are all the gpe based rooms compatible with our version of the device, and can i flash the gpe ruu without bricking the thing if i got s-off.
Click to expand...
Click to collapse
Sorry but I seriously don't know because I never took an interest in converting my device to GPE.
I like the stock look.

[Q] Stock Recovery Question

Hey guys,
First post and thread, unfortunately. May have been done before, so sorry if that's the case (and if it is I guess a quick link can clear this confusion up!)
I've got a tmobile HTC One M8 running Android 4.4.4 with an unlocked boot loader, clockworkmod 6.0.4.8 with s-on.
New android update is out and while I'm not necessarily keen on updating it, the icon is annoying. As well, I originally rooted the phone for some apps and sorts that I don't even use and I'm mainly interested in just bringing the phone back to a stock recovery so I can unroot it.
Tried using the RUU posted but I believe due to the s-on and unlocked boot loader, it doesn't work for me. Step one is an error on it.
What can I do here to bring the phone back to stock recovery? I'm not 100% I made a backup before I put cwm on it. May have but for arguments sake let's say I didn't.
Any and all help is appreciated. thanks so much everyone.

Metilinos said:
Tried using the RUU posted but I believe due to the s-on and unlocked boot loader, it doesn't work for me. Step one is an error on it.
Click to expand...
Click to collapse
RUUs run fine with s-on, and I don't know why folks keep posting that it doesn't.
But you do however, need to relock the bootloader (since you are s-on) to run the RUU. Its absolutely mandatory (with s-on), and almost certainly why the RUU fails. THe RUU also needs to match your CID (but if you are properly trying a T-Mob RUU on a T-Mob version M8, that is not the issue), and further you cannot "downgrade" or run an older version RUU (older hboot) than what is on the phone.
But again, unlocked bootloader alone will make the RUU fail.

I haven't really seen a whole lot of s-off since firewater hasn't worked any longer. I kind of figured the unlocked bootloader was an issue as well. Mobile right now and working so not a whole lot I can do. Basically make sure the CID matches the RUU and relock the bootloader and I should be good to go? I picked up the T-Mobile RUU and I have a tmobIle M8, I didn't really think to check the CID, I just mainly assumed the failed run was from other sources.

Metilinos said:
I haven't really seen a whole lot of s-off since firewater hasn't worked any longer. I kind of figured the unlocked bootloader was an issue as well. Mobile right now and working so not a whole lot I can do. Basically make sure the CID matches the RUU and relock the bootloader and I should be good to go? I picked up the T-Mobile RUU and I have a tmobIle M8, I didn't really think to check the CID, I just mainly assumed the failed run was from other sources.
Click to expand...
Click to collapse
As long as you have the right carrier RUU, the CID will also match. I assume T-Mobile US? As there is also T-Mobile in Europe.
As long as its right carrier (CID) and not trying to run an older version RUU, the unlocked bootloader is the only problem.

Yes T-Mobile US.
I'll have to double check the RUU, I'm pretty sure I grabbed it off here from a different thread, but like you said, the unlocked bootloader obviously was an issue.
In the case, and I'm assuming it's rare, that it could be that, is there an easy way to tell whether or not I have the most current RUU?
Thanks a bunch, really appreciating the help. I've been kind of at a standstill with this and haven't really tried much in fear of killing the phone.

Metilinos said:
In the case, and I'm assuming it's rare, that it could be that, is there an easy way to tell whether or not I have the most current RUU?
Click to expand...
Click to collapse
Do you mean its rare to run the wrong version RUU? If so, I'd say no, its not rare at all. Folks are often not aware of the version requirement (with s-on, this requirement is bypassed with s-off) and try to run an "old" RUU.
All the T-Mob US RUUs are posted here: http://forum.xda-developers.com/showthread.php?t=2714456
3.32 is Android 4.4.4
4.20 is Android 5.0

3.32 is what I have at the moment. With android 5 coming over the air a week or so ago for myself and 4.4.4 being on the phone when I got it just a couple months back, that's what I guess I was insinuating by rare. But thank you a bunch for your help. Again it's very much appreciated. Obviously got myself in a little over my head here.

[Q] I need help HTC One M8 AT&T

I am using AT & T HTC M8 S - OFF super CID. Can I install this recovery ?
[ROM][5.1] 9/17/2015-Lollipop Stock Rooted Google Play Edition LMY47O.H9
HTML:
http://forum.xda-developers.com/showthread.php?t=2706441
thanks alot!!!!! :good::good::good:

That's not a recovery, it's a ROM !

Mr Hofs said:
That's not a recovery, it's a ROM !
Click to expand...
Click to collapse
yes. i'm sorry but can i use it??

The short answer is yes. However, the longer answer is yes, but you need to think carefully about this before pulling the trigger.
Some people repartition their phones to fully convert to the GPE version, but I don't recommend this unless you are either certain you want a GPE ROM or are highly skilled in this area. In your case, since you aren't certain, I would install without altering your partitions. From what I read in the first post, it appears this ROM simply rewrites your existing Sense partitions with GPE code, so it should be perfectly safe.
Also, make sure you note the required firmware version. AT&T has released a Lollipop version of their ROM, so if you aren't sure, you might consider running their RUU as a way to ensure you have compatible firmware. (since you are S-off, you can also use the Developer Edition RUU, but since you are converting to GPE, it really doesn't matter) Attempting to run a Lollipop GPE build with KitKat firmware will not work well.

jshamlet said:
The short answer is yes. However, the longer answer is yes, but you need to think carefully about this before pulling the trigger.
Some people repartition their phones to fully convert to the GPE version, but I don't recommend this unless you are either certain you want a GPE ROM or are highly skilled in this area. In your case, since you aren't certain, I would install without altering your partitions. From what I read in the first post, it appears this ROM simply rewrites your existing Sense partitions with GPE code, so it should be perfectly safe.
Also, make sure you note the required firmware version. AT&T has released a Lollipop version of their ROM, so if you aren't sure, you might consider running their RUU as a way to ensure you have compatible firmware. (since you are S-off, you can also use the Developer Edition RUU, but since you are converting to GPE, it really doesn't matter) Attempting to run a Lollipop GPE build with KitKat firmware will not work well.
Click to expand...
Click to collapse
yes thank you very much. I just installed this ROM. first boot times appeared broken and I had to factory reset. so far has not detected any errors.
I used the AT & T version of the ROM, but I feel uncomfortable because of the bundled applications, which I never use because I was in Vietnam. So how to completely remove them?

minhtienls said:
yes thank you very much. I just installed this ROM. first boot times appeared broken and I had to factory reset. so far has not detected any errors.
I used the AT & T version of the ROM, but I feel uncomfortable because of the bundled applications, which I never use because I was in Vietnam. So how to completely remove them?
Click to expand...
Click to collapse
Since you have the AT&T variant, and you are S-off, this is easy. Install the Developer Edition RUU. They are the exact same phone (same MID) but the Developer Edition doesn't have any of the AT&T bloat.
You may have to change the CID back to match one or the other of the unlocked/developer phones for the RUU to install. (either BS_US001 for unlocked or BS_US002 for developer edition) but you don't have to alter the MID at all.
If you don't root, you will get OTA updates directly from HTC.
As an aside, you might also try the WWE (world-wide English) variant as well, though that WILL require altering the MID.

jshamlet said:
Since you have the AT&T variant, and you are S-off, this is easy. Install the Developer Edition RUU. They are the exact same phone (same MID) but the Developer Edition doesn't have any of the AT&T bloat.
You may have to change the CID back to match one or the other of the unlocked/developer phones for the RUU to install. (either BS_US001 for unlocked or BS_US002 for developer edition) but you don't have to alter the MID at all.
Click to expand...
Click to collapse
I agree, if the OP wants a relatively clean, unbranded Sense setup (including official OTAs, and band support same as AT&T version) that the Dev Edition RUU is the way to go.
OP stated the phone is SuperCID, so no need to change CID (and I'd recommend not to change the CID to flash the Dev Ed RUU
Although GPE and Sense are two completely different animals. Not sure if the OP prefers one or the other? Although OP's last post did make it sound like they wanted a Sense ROM, just without AT&T branding.

As an aside, I don't see the utility in super CID anymore. It no longer "unlocks" anything (you don't get a free SIM unlock), so really the only advantage is being able to install any another HTC ROM via RUU. On the flip side, super CID blocks OTA updates on official ROMs, which makes it more of a disadvantage now.
Since most people are going to need a specific HTC ROM (for band support), or they are going to go with a third-party ROM which doesn't care what your CID is, I'd actually suggest using the CID/MID for the appropriate Sense ROM instead of super CID to ensure there aren't problems down the road. If you do, your phone essentially becomes that model for all intents and purposes.
(The obvious exception being Sprint/Verizon devices, but that isn't applicable here)

jshamlet said:
super CID blocks OTA updates on official ROMs, which makes it more of a disadvantage now.
Click to expand...
Click to collapse
You sure of that? I've seen folks say that a lot, but others also contradict the statement. ckpv5 in particular, and that guy knows his stuff. He's stated it a number of times (SuperCID does not prevent OTA); just yesterday, in fact: http://forum.xda-developers.com/showpost.php?p=63075776&postcount=9
But I agree that SuperCID is very limited in its usefulness (since MID is also a requirement, and there are so many different MIDs) and probably only in specific circumstances. For instance, I made my M8 SuperCID to install the Dev Ed RUU, and be able to RUU back to ATT if I wanted. But also, like you mentioned, I also run custom ROMs often, in which case CID is fairly irrelevant.
In the OP's case, as long as SuperCID doesn't block OTA, it saves him from changing the CID (although its just a single fastboot command) and also go back to ATT if desired.
SuperCID is probably pretty useful for Euro M8 owners, as there are a ton of CIDs for the same MID.

redpoint73 said:
You sure of that? I've seen folks say that a lot, but others also contradict the statement. ckpv5 in particular, and that guy knows his stuff. He's stated it a number of times (SuperCID does not prevent OTA); just yesterday, in fact: http://forum.xda-developers.com/showpost.php?p=63075776&postcount=9
But I agree that SuperCID is very limited in its usefulness (since MID is also a requirement, and there are so many different MIDs) and probably only in specific circumstances. For instance, I made my M8 SuperCID to install the Dev Ed RUU, and be able to RUU back to ATT if I wanted. But also, like you mentioned, I also run custom ROMs often, in which case CID is fairly irrelevant.
In the OP's case, as long as SuperCID doesn't block OTA, it saves him from changing the CID (although its just a single fastboot command) and also go back to ATT if desired.
SuperCID is probably pretty useful for Euro M8 owners, as there are a ton of CIDs for the same MID.
Click to expand...
Click to collapse
I've read conflicting reports on SuperCID blocking OTA updates as well, so he may very well be right. I will say that when I first installed the KitKat DevEd ROM, it appeared to refuse to download the OTA update to 4.4.4 until I reverted to using the official CID (BS_US002), but it's also possible that I just didn't wait long enough. Maybe that has changed since Lollipop?
If it really doesn't block OTA updates, then it's probably a pure don't care. If you are S-off, it's a trivial change. Also, if you are rooted, it's a moot issue anyway, as that is more likely to foul up OTA updates than the CID.

jshamlet said:
I've read conflicting reports on SuperCID blocking OTA updates as well, so he may very well be right. I will say that when I first installed the KitKat DevEd ROM, it appeared to refuse to download the OTA update to 4.4.4 until I reverted to using the official CID (BS_US002), but it's also possible that I just didn't wait long enough. Maybe that has changed since Lollipop?
If it really doesn't block OTA updates, then it's probably a pure don't care. If you are S-off, it's a trivial change. Also, if you are rooted, it's a moot issue anyway, as that is more likely to foul up OTA updates than the CID.
Click to expand...
Click to collapse
SuperCID doesn't block OTAs. It allows you to flash firmware for any CID without the need to change it. The CID works with all.
Since the OP is S-Off, I would suggest using WWE/International firmware. It's updated sooner if a Sense ROM is what he is after. OP could run MaximusHD if he wishes to remain Stock.

Cant update from: 3.35.617.31, Getting errors with RUU, Cant OTA

Hello,
I have bought HTC One M9 off Aliexpress.
I bought it as developer version. When it came I started OTA upgrade. It downloads and then it says update cannot be performed because of modified system.
I cant even use RUU to get it working, I receive error 132. While chatting to HTC support their run my IMEI by their system. It came back as T-Mobile (US) version. Even though on back of my phone is engraved -
Model: OPJA110 which should mean it is developer version.
On my download mode it states: S-on, official system and locked bootloader.
Can anyone give me some tips how to get the newest system installed?
I have been trying for past 2 days without any luck to figure it out.
Any help is appreciate.
EDIT: Forgot CID:11111111 MID: 0PJA11000
Thank you very much.

Please read the ReadMe thread. It'll explain the causes of your issues and contains the needed files and instructions for fixing it. (C.f. the conversion guide, the RUU and the OTA section)
The most important infos: OTAs aren't installable while the phone is using the SuperCID and firmware 4.x RUUs aren't flashable on phones with firmware 3.x or lower due to new encryption keys.
Sent from my HTC One M9 using XDA Labs

Thanks for your time.

Flippy498 said:
Please read the ReadMe thread. It'll explain the causes of your issues and contains the needed files and instructions for fixing it. (C.f. the conversion guide, the RUU and the OTA section)
The most important infos: OTAs aren't installable while the phone is using the SuperCID and firmware 4.x RUUs aren't flashable on phones with firmware 3.x or lower due to new encryption keys.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
I have read ReadMe.
So that means I need to S-OFF my phone using SunShine (other oprions?)
Then changing CID to BS_US001 (because Im running .617. system)
Then I can flash RUU (3.35.617.31)
And after that I can use OTA updates?
Do I need to unlock bootloader through HTCdev or is enough to check OEM Unlocking under developer options?
Thank you again for your time.

Oh, I missed that you're S-ON. Follow the unlocking/rooting guide in the same thread.
If you're lucky the previous owner used Sunshine, as well, so that you don't have to pay, again. (The license is saved on their servers and gets linked to the device.) The alternatives to Sunshine are a Java card, an XTC clip or similar tools which are way more expensive.
It doesn't matter which of the CIDs that belong to SKU 617 you use. They both work fine.
Alternatively, you could send the device back to the seller and ask for a refund. He obviously modified the phone and didn't restore the phone to a stock state properly before he sold it. The phone definetly was S-OFF in the past since no HTC phone gets shipped with the SuperCID. And if the IMEI belongs to a T-Mobile M9 according to HTC then the MID got changed with the help of S-OFF, as well. The backside can actually get replaced, too, if you know how to do it.
After you restored a CID that corresponds to your SKU you should be able to receive OTAs, again. Just for safety reasons I'd flash a 3.x RUU, as well, if I were you. The differences between the GSM versions of the M9 are so minor that you can convert the phone from one version to another. Therefore, you don't need to use the T-Mobile firmware and can stick with the dev one if you want.

Flippy498 said:
Oh, I missed that you're S-ON. Follow the unlocking/rooting guide in the same thread.
If you're lucky the previous owner used Sunshine, as well, so that you don't have to pay, again. (The license is saved on their servers and gets linked to the device.)
It doesn't matter which of the CIDs that belong to SKU 617 you use. They both work fine.
Alternatively, you could send the device back to the seller and ask for a refund. He obviously modified the phone and didn't restore the phone to a stock state properly before he sold it. The phone definetly was S-OFF in the past since no HTC phone gets shipped with the SuperCID. And if the IMEI belongs to a T-Mobile M9 according to HTC then the MID got changed with the help of S-OFF, as well. The backside can actually get replaced, too, if you know how to do it.
After you restored a CID that corresponds to your SKU you should be able to receive OTAs, again. Just for safety reasons I'd flash a 3.x RUU, as well, if I were you. The differences between the GSM versions of the M9 are so minor that you can convert the phone from one version to another. Therefore, you don't need to use the T-Mobile firmware and can stick with the dev one if you want.
Click to expand...
Click to collapse
Ok, Im gona pay that 25 bucks, it doesnt really matter.
So, I should start with unlocking bootloader via HTCdev.
After that I need to use SunShine.
Changing CID.
Flashing 3.x RUU.
And then doing OTA.
Is that all correct?
And should I install TWRP or stay on stock recovery after unlocking bootloader?
Really appreciate your time.

Correct.
Just follow the guides in the ReadMe thread starting from this post till the end of the conversion guide. (Theoretically, you can skip the backup part and save some time since you should be able to use the 3.x RUU even with the SuperCID on your phone.)

Flippy498 said:
Correct.
Just follow the guides in the ReadMe thread starting from this post till the end of the conversion guide. (Theoretically, you can skip the backup part and save some time since you should be able to use the 3.x RUU even with the SuperCID on your phone.)
Click to expand...
Click to collapse
Thanks,
is there a point in TWRP backup? Wont it stop OTA updates? On my other phone (Ulefone Metal) It is not possible to get OTA with custom recovery.

It actually is possible on the M9 and newer HTC phones as long as the system partition doesn't get modified, beforehand. (Further info can be found in the OTA section of the ReadMe thread.)
However, flashing a RUU restores everything on the phone back to stock (including the recovery). That's why I suggested flashing one after changing the CID.
Sent from my HTC One M9 using XDA Labs

Flippy498 said:
It actually is possible on the M9 and newer HTC phones as long as the system partition doesn't get modified, beforehand. (Further info can be found in the OTA section of the ReadMe thread.)
However, flashing a RUU restores everything on the phone back to stock (including the recovery). That's why I suggested flashing one after changing the CID.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Thank you, I did as I said.
After flashing 3.x RUU OTA was successful.
That updated my system to: 4.16.617.6.
After that I continued by flashing latest RUU (4.30.617.12).
Everything went well. Until this point. When I booted the device I got to choose language. But there are just few (20 or so) available.
Unfortunately no Czech which I want. On previous version (4.16.617.6) there was huge list to choose from, including Czech.
Im still using 617 edition.
Where is the problem? Is here a way to get Czech lang. working again?
One again thank you for your time and effort

HTC probably removed the languages from the selection. Don't ask me why. I have no clue.
You could try setting up the phone in English and then switching to Czech via the app MoreLocal2. There's a thread about the app somewhere hidden on xda (sorry, I don't have a direct link at hand). You should be able to find it via google.
Sent from my HTC One M9 using XDA Labs

Need help restoring factory specs

So I bought this 'new' phone with the intention of rooting it and got to the point of updating to the latest firmware before root. turns out the phone is already 'modified'. contacted htc support looking for a means to restore factory specs but they say it has been rooted and it'll take another 2-3 days before i can further pursue the issue.
wondering if someone here can enlighten me as to how i'd restore stock before i re-root (there's no telling what mischief the rooter was up to). it was pretty easy on my old samsung with odin but this is my first htc so i'm in unknown territory here. the phone is in an otherwise impeccable state so i'm not really bothered about returning it since i can't imagine anything that might survive a factory reflash.
a little guidance would be much appreciated!

Take a look at the ReadMe thread. The RUU section most likely contains everything you need. I personally recommend the SD card method. It's the easiest and most fail-safe one.
Sent from my HTC One M9 using XDA Labs

Been poring through it but frankly it is overwhelming. Wonder if you could answer a few noob questions.
1. the ruu section says not to re-lock the bootloader. will flashing an ruu re-lock the bootloader?
2. found my ruu which seems to be a sprint cdma version (sku:651). however the cid (SPCS_001) does not match with mine (11111111). not sure where to find the MID. where does this mismatch leave me?
3. will flashing the sprint cdma fw lock my carrier (ie prevent me from using other sim cards)
4. does the ruu rewrite/restore all of the partitions e.g. including recovery? (considering an unknown person has rooted and tinkered with the phone).

jbonetwo said:
Been poring through it but frankly it is overwhelming. Wonder if you could answer a few noob questions.
Click to expand...
Click to collapse
Yes, you can. Follow-up questions are always welcome. (In contrast to questions that obviously show that people were too lazy to read anything. )
jbonetwo said:
the ruu section says not to re-lock the bootloader. will flashing an ruu re-lock the bootloader?
Click to expand...
Click to collapse
No. Re-locking the bootloader requires the usage of a certain fastboot command.
jbonetwo said:
found my ruu which seems to be a sprint cdma version (sku:651). however the cid (SPCS_001) does not match with mine (11111111). not sure where to find the MID. where does this mismatch leave me?
Click to expand...
Click to collapse
Your phone currently uses the SuperCID. That CID had a whole bunch of benefits on older HTC devices. It lost most of them on the M9, though. Changing the CID is only possible with S-OFF. I highly recommend you to use the conversion guide for restoring your phones original CID. (CDMA versions of the M9 can't get converted to different variants without breaking them. If you're able to get mobile reception with that phone then it didn't get converted and you definetely own a Sprint M9. You don't have to look for the MID in this case.)
jbonetwo said:
will flashing the sprint cdma fw lock my carrier (ie prevent me from using other sim cards)
Click to expand...
Click to collapse
I can't answer that question since sim locks don't exist in the European firmware versions of this phone and I therefore don't have much experiences with them.
jbonetwo said:
does the ruu rewrite/restore all of the partitions e.g. including recovery? (considering an unknown person has rooted and tinkered with the phone).
Click to expand...
Click to collapse
Yes, it does. RUUs overwrite everything on your phone with their files.

thank you for taking the time!
Flippy498 said:
If you're able to get mobile reception with that phone then it didn't get converted and you definetely own a Sprint M9. You don't have to look for the MID in this case.)
Click to expand...
Click to collapse
definitely a sprint m9 then. i wonder if they're rooting/unlocking sim-locked sprints and reselling them as unlocked phones.
will have to confirm the sim lock detail with htc support either way. but it's starting to look like i may have to return the phone. disappointing but at least rooting and flashing a genuine one is gonna be a breeze now