Hi there, I picked up an HTC One M9 for a good price from China and overall I am pretty pleased with it however it seems to be wired for CDMA updates only and so it is stuck on Android 6.0, as attempting to update it says that updates are only available over CDMA networks.
Rebooting to bootloader It tells me
*** Software status: Official ***
*** UNLOCKED ***
*** S-OFF ***
I have tried using a wide selection of RUU files to update the phone and pretty much every one of them gives me an error. For example RUU_HIMA_UL_N70_SENSE80_ATT_MR_NA_Gen_Unlock_4.30.617.12 takes me through the install process, reboots the phone to the bootloader and after several warning screens tells me that it will update from 3.37.605.19 to 4.30.617.12 The phone shows it is uploading, but then quickly ends up frozen whilst the PC dialog shows:
ERROR [132]: SIGNARURE ERROR
Exiting reboots the phone back to the starting condition.
I've tried all of the RUU files that I could find (with a higher version) and had the same error. Not sure where to go next, any help very gratefully received!
Cheers,
..alex
Please take a look at the ReadMe thread. It will tell you why you can't use 4.x RUUs on a phone with a 3.x firmware and why you should never try to flash a GSM RUU on a CDMA device.
Sent from my HTC One M9 using XDA Labs
Thanks for your response and the redirect to the readme I can see that the RUU update path is not going to work. Is there any way to switch this phone to GSM or is it permanently stuck add a CDMA device?
Cheers
..alex
It's permanently stuck on the CDMA firmware. Those are two completely different technologies.
However, the CDMA M9 supports some GSM frequencies so it shouldn't be completely useless for you. You probably just won't get LTE with it.
In regard to android updates: I don't know whether there already is an android 7 update for the verizon variant (verizon is super slow). If there is you might be able to update the phone with an unofficial firmware pack (like the ones that Sneakyghost provides) since you already have S-OFF. Although Sneakyghost himself doesn't provide ones for verizon phones you might find some in the verizon M9 forum. Afterwards you would only need to re-flash the corresponding 4.x RUU (assuming that you want to stay on the stock rom - otherwise you could directly flash whichever custom rom you want to use).
Sent from my HTC One M9 using XDA Labs
If I were to pursue this strategy would the end product be a phone that had flipped to GSM and could connect to 4G? It feels like the difference is not a hardware one - that is the phones must have the hardware to go either way right? Or do they have a different comms chipset?
Cheers,
..alex
Flippy498 said:
It's permanently stuck on the CDMA firmware. Those are two completely different technologies.
However, the CDMA M9 supports some GSM frequencies so it shouldn't be completely useless for you. You probably just won't get LTE with it.
In regard to android updates: I don't know whether there already is an android 7 update for the verizon variant (verizon is super slow). If there is you might be able to update the phone with an unofficial firmware pack (like the ones that Sneakyghost provides) since you already have S-OFF. Although Sneakyghost himself doesn't provide ones for verizon phones you might find some in the verizon M9 forum. Afterwards you would only need to re-flash the corresponding 4.x RUU (assuming that you want to stay on the stock rom - otherwise you could directly flash whichever custom rom you want to use).
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
You cannot flash a GSM firmware on a CDMA device (or vice versa) without damaging it unrecoverably. The partition layout isn't the same. All you can do is upgrading or downgrading your firmware but switching your SKU (even if it's another CDMA one*) will result in damages. The difference between GSM and CDMA phones lies within their hardware and their software. Although newer CDMA phones support some GSM frequencies and are therefore able to connect to some GSM networks they still aren't able to get G/2G/3G/H+/LTE on every carrier's network.
* Not even the different CDMA variants of the M9 share the same partition layout.
Related
Ok, found this to be a recurring question here at the forum and read through as many posts as I could. Unfortunately none seem to be quite what I need...
Bought a rooted Verizon 4G HTC One and it was working kind of fine with the rom it came though I wanted to try the Google Play one.
Well it didn't work - and - I accidentally wiped the original rom installer (was a NuSense). Now it bootloops with every other rom I've tried. Last one being NOS 1.0.2 m7wlv Google Play Edition - http://forum.xda-developers.com/showthread.php?t=2416875 )
My device information (from the bootloader screen):
Code:
M7_WLV PVT SHIP S-OFF RH
CID-11111111
HBOOT-1.54.0000
RAID-4T.21.3218.21
OpenDSP-v31.120.274.0617
OS-1.10.605.10
eMMC-boot 2048MB
Sep 9 2013,11:53:38.0
And the recovery is
Code:
Team Win Recovery Project v2.6.3.2
Please someone put me out of this misery
thanks!
I've been doing some tinkering and I'm about to try some other roms - not really specific ones to m7wlv though.
Found some posts of people blaming on TWRP version used causing similar problem.
Was worried though: by Team Win's page I couldn't find a m7wlv specific recovery (for 2.7 or any other). They do have a simple "M7" version... is it safe to install that one?
I'm worried that if I break the recovery mode, I won't be able to upload files not even with ADB, thus meeting the fine brick stage for the device.
thoughts?
Update to the newest twrp 2.6.3.4 and try again. http://vzw1files.dyndns.org/RECOVERIES/twrp/openrecovery-twrp-2.6.3.4-m7vzw.img
update your firmware which will upgrade your radios and such for those roms
coldconfession13 said:
update your firmware which will upgrade your radios and such for those roms
Click to expand...
Click to collapse
I am confused now. Not sure which firmware should I update to. My phone is a M7_WLV, however it is a GSM phone - this is the opposite a this blog post (cant add the URL) says:
(...) If you’ve got the International GSM HTC One (m7) or the Verizon CDMA variant (m7wlv) (...)
Click to expand...
Click to collapse
(note: I already have S-OFF, this is just an example).
In the other hand Wikipedia seems to agree (although it doesn't says if GSM ou CDMA):
The HTC One 801n LTE versions (M7_WLJ, M7_WLV), Verizon HTC One HTC6500LVW (M7_WLV) LTE version
Click to expand...
Click to collapse
So, to be sure, could someone tell me the correct firmware to update on a Verizon 4G GSM HTC One M7_WLV?
thanks,
f.
cmlusco said:
Update to the newest twrp 2.6.3.4 and try again. http://vzw1files.dyndns.org/RECOVERIES/twrp/openrecovery-twrp-2.6.3.4-m7vzw.img
Click to expand...
Click to collapse
Thanks a lot cmlusco! I managed to get some of the ROMs working now. Still, my phone isn't connecting to the GSM network - over configurations I see CDMA items, so I think I either updated the wrong firmware or still have to update.
I've tried the same rom you show in your signature (since you seem to have the same phone - which by the way, is it GSM or CDMA?), but it reboots during these "welcome" screen after the SO loads up.
Could you hint me which firmware are you using?
thanks!
f.
What country are you in, and who is your wireless provider?
The Verizon One (like most smartphones Verizon releases these days) is a GSM + CDMA hybrid that supports GSM out of the box unlocked for global roaming. It's still meant to be used on Verizon's CDMA network though - that means support for just a few 2G GSM bands and no 3G HSPA as far as we can tell.
So no, there's only one M7_WLV and that's the CDMA Verizon One. GSM support on this phone is really just an added bonus. If you're not in the US and don't use them, I'd recommend you exchange it with the international model, or at least an AT&T or T-Mobile model so you get proper GSM support.
Thank you all!
Finally managed.
Updated latest firmware version and recovery and all started working again!
cheers lads,
f.
Hi. I have a M9 with model id 0PJA100. I bought it unlocked and s-off. One day, I flashed this rom named ICE with android nougat. After that, I cannot use my mobile data. I installed back stock rom to this phone and it is still the same. I can answer call and sms but I cannot get any mobile data. Today, I flashed Viper M9 v6 (nougat) and during the setup, I got H+ signal only for a few second and then it dissapeared. I dont really understand the problem and managed to install a lot of rom before. If anyone have any idea that can possibly make this device working, please reply to this thread. I hate to use my 5s as daily driver.
abdinsyakirin said:
Hi. I have a M9 with model id 0PJA100. I bought it unlocked and s-off. One day, I flashed this rom named ICE with android nougat. After that, I cannot use my mobile data. I installed back stock rom to this phone and it is still the same. I can answer call and sms but I cannot get any mobile data. Today, I flashed Viper M9 v6 (nougat) and during the setup, I got H+ signal only for a few second and then it dissapeared. I dont really understand the problem and managed to install a lot of rom before. If anyone have any idea that can possibly make this device working, please reply to this thread. I hate to use my 5s as daily driver.
Click to expand...
Click to collapse
Has your phone's firmware been updated to Nougat? What OS version does your phone report?
computerslayer said:
Has your phone's firmware been updated to Nougat? What OS version does your phone report?
Click to expand...
Click to collapse
I came from marshmallow stock rom 3.37 firmware but verizon version since i thought that my phone is verizon edition. Do i need to flash stock nougat before changing to nougat based custom rom?
Access point names. Change it to what you carrier uses or get them to send it to your phone.
abdinsyakirin said:
I came from marshmallow stock rom 3.37 firmware but verizon version since i thought that my phone is verizon edition. Do i need to flash stock nougat before changing to nougat based custom rom?
Click to expand...
Click to collapse
Yes you do. If you flash a nougat based rom over marshmallow it wont boot.
Beamed in by telepathy.
shivadow said:
Access point names. Change it to what you carrier uses or get them to send it to your phone.
Yes you do. If you flash a nougat based rom over marshmallow it wont boot.
Beamed in by telepathy.
Click to expand...
Click to collapse
I've changed the apn but still the same. I will try flashing nougat based firmware and then give u my feedback. U have any link for the firmware?
abdinsyakirin said:
Hi. I have a M9 with model id 0PJA100.
Click to expand...
Click to collapse
abdinsyakirin said:
I came from marshmallow stock rom 3.37 firmware but verizon version since i thought that my phone is verizon edition.
Click to expand...
Click to collapse
That's not the Verizon MID. Don't flash anything unless you definetely know which version of the M9 you own.
abdinsyakirin said:
U have any link for the firmware?
Click to expand...
Click to collapse
Did Verizon already release the android N update? I haven't heard of it, yet.
shivadow said:
If you flash a nougat based rom over marshmallow it wont boot.
Click to expand...
Click to collapse
Are you sure? I know that this was the case when you tried to use an android M rom with an android L firmware. However, I haven't heard of such cases after people flashed an android N rom on an android M firmware. Sometimes newer HTC stock roms/stock-based custom roms are booting fine on older firmware versions (but that doesn't mean that there won't be any other issues due to the mismatch of the rom base and the current firmware).
Flippy498 said:
That's not the Verizon MID. Don't flash anything unless you definetely know which version of the M9 you own.
Did Verizon already release the android N update? I haven't heard of it, yet.
Are you sure? I know that this was the case when you tried to use an android M rom with an android L firmware. However, I haven't heard of such cases after people flashed an android N rom on an android M firmware. Sometimes newer HTC stock roms/stock-based custom roms are booting fine on older firmware versions (but that doesn't mean that there won't be any other issues due to the mismatch of the rom base and the current firmware).
Click to expand...
Click to collapse
Yes i just know that my phone is an international version. Before this i thought it was verizon m9. Verizon did not release any nougat based firmware. But i think there is international version of nougat available
For the marshmallow to nougat question, i encountered some issues with the other rom. Some roms doesnt boot up and some others stuck on setup wizard since wifi cannot be enable.
So do u think i need to flash international version of nougat on my phone? Will it fix this mobile network problem.
abdinsyakirin said:
So do u think i need to flash international version of nougat on my phone? Will it fix this mobile network problem.
Click to expand...
Click to collapse
If you already flashed a Verizon firmware then you definetely need to flash a GSM RUU and should hope that your phone didn't get damaged unrecoverably. GSM devices and CDMA firmware (or vice versa) aren't compatible with each other.
Did you change your CID or your MID somewhen in the past? If not then please boot to download mode and tell us what version is stated behind "OS". If you did then I hope you wrote down your original MID and CID. At the moment I'd recommend you to flash whatever RUU belongs to your original firmware version since the issues you describe shouldn't happen if you use the correct stock rom.
After all reception problems on the stock rom got solved we can think about updating your phone to android 7 but at the moment we should only make one step at a time.
Flippy498 said:
If you already flashed a Verizon firmware then you definetely need to flash a GSM RUU and should hope that your phone didn't get damaged unrecoverably. GSM devices and CDMA firmware (or vice versa) aren't compatible with each other.
Did you change your CID or your MID somewhen in the past? If not then please boot to download mode and tell us what version is stated behind "OS". If you did then I hope you wrote down your original MID and CID. At the moment I'd recommend you to flash whatever RUU belongs to your original firmware version since the issues you describe shouldn't happen if you use the correct stock rom.
After all reception problems on the stock rom got solved we can think about updating your phone to android 7 but at the moment we should only make one step at a time.
Click to expand...
Click to collapse
My phone has SuperCID. Based on download mode, the OS- 3.37.605.13. Model ID 0PJA100 as stated before. I think the OS version is vzw not wwe since i flashed the vzw before. Actually, I bricked this device after i had my "mobile data disconnected" problem and asked somebody to help me fix it, and he flashed that firmware version (it is my fault since i thought this phone is verizon m9).
So, should I fully flash the wwe 3.35 firmware? Or what?
That's odd. I would have expected the current MID to be 0PJA30000. Did the MID get changed back to its original state after you flashed the Verizon RUU? Normally the M9 shouldn't accept a RUU if the MID doesn't match. Even the SCID won't change this fact, anymore, as it did on older HTC phones. Or are you talking about the original MID of the phone that is stated on the backside of the phone? I assume the answer to this question is yes since the MID you're talking about is two zeros too short for being a digital MID. Only the engraving on the backside of the phone uses this short version of MIDs.
Revert the SCID to one of the CIDs that belong to SKU 401 (but don't choose the demo unit CID HTC__002), if needed revert the MID to the one that belongs to this SKU and then flash the 3.35.401.12 RUU. Instructions can be found in the FAQ section of the ReadMe thread (the stickied one in the Q&A section and the General section).
After you flashed the GSM RUU your phone should be working normally, again, if the Verizon RUU didn't damage it unrecoverably. In addition, you should be able to install two OTAs (the latter is the update for Android 7) via the software update function of the phone.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
That's odd. I would have expected the current MID to be 0PJA30000. Did the MID get changed back to its original state after you flashed the Verizon RUU? Normally the M9 shouldn't accept a RUU if the MID doesn't match. Even the SCID won't change this fact, anymore, as it did on older HTC phones. Or are you talking about the original MID of the phone that is stated on the backside of the phone? I assume the answer to this question is yes since the MID you're talking about is two zeros too short for being a digital MID. Only the engraving on the backside of the phone uses this short version of MIDs.
Revert the SCID to one of the CIDs that belong to SKU 401 (but don't choose the demo unit CID HTC__002), if needed revert the MID to the one that belongs to this SKU and then flash the 3.35.401.12 RUU. Instructions can be found in the FAQ section of the ReadMe thread (the stickied one in the Q&A section and the General section).
After you flashed the GSM RUU your phone should be working normally, again, if the Verizon RUU didn't damage it unrecoverably. In addition, you should be able to install two OTAs (the latter is the update for Android 7) via the software update function of the phone.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Oh yes the MID changed to 0PJA30000, sorry for my last reply, that one i referred to the back engraving of m9. Im gonna change the CID and flash the firmware version u talked about. I will give you an update once I done it.
Flippy498 said:
That's odd. I would have expected the current MID to be 0PJA30000. Did the MID get changed back to its original state after you flashed the Verizon RUU? Normally the M9 shouldn't accept a RUU if the MID doesn't match. Even the SCID won't change this fact, anymore, as it did on older HTC phones. Or are you talking about the original MID of the phone that is stated on the backside of the phone? I assume the answer to this question is yes since the MID you're talking about is two zeros too short for being a digital MID. Only the engraving on the backside of the phone uses this short version of MIDs.
Revert the SCID to one of the CIDs that belong to SKU 401 (but don't choose the demo unit CID HTC__002), if needed revert the MID to the one that belongs to this SKU and then flash the 3.35.401.12 RUU. Instructions can be found in the FAQ section of the ReadMe thread (the stickied one in the Q&A section and the General section).
After you flashed the GSM RUU your phone should be working normally, again, if the Verizon RUU didn't damage it unrecoverably. In addition, you should be able to install two OTAs (the latter is the update for Android 7) via the software update function of the phone.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
I dont get any mobile network, even worse than before. I flashed 3.35.401.12 like u told so. Do i need to flash it manually by extracting the folder and flash all the img inside it independently? If u have any suggestion let me know.
UPDATE: Actually i dont think the problem is with verizon firmware since I had the problem after I flashed ICE nougat rom (I came from SDreamTeam Sense8 rom). After that I bricked the device and told other person to help me flash vzw firmware because I thought it was verizon m9. This problem is very weird and i dont know how to relate the ICE rom with my current problem. OP of ICE rom said the rom not compatible with verizon m9 but since this phone is not verizon m9, i dont think there should be a problem right?
The RUU needs to get flashed via the SD card method that is described in the ReadMe thread.
As written there and in some of my posts in this thread, GSM devices and CDMA firmware (or vice versa) aren't compatible with each other due to the different partition layouts. Therefore, cross-flashing can lead to unrecoverable damages.
I can't tell you what happened while you've been using ICE and therefore I can't tell you whether your phone had been in a recoverable state at that time. However, chances are high that flashing a Verizon RUU instead of the correct GSM RUU was the nail in the coffin of your phone. Sorry, that I don't have better news.
Edit: Oh, and please remove the quote from your last post. It's not necessary to quote me every time you post here.
Flippy498 said:
That's not the Verizon MID. Don't flash anything unless you definetely know which version of the M9 you own.
Did Verizon already release the android N update? I haven't heard of it, yet.
Are you sure? I know that this was the case when you tried to use an android M rom with an android L firmware. However, I haven't heard of such cases after people flashed an android N rom on an android M firmware. Sometimes newer HTC stock roms/stock-based custom roms are booting fine on older firmware versions (but that doesn't mean that there won't be any other issues due to the mismatch of the rom base and the current firmware).
Click to expand...
Click to collapse
Exactly that, it's not worth the risk seeing as many people have reported that their phone won't boot after mismatching roms to base firmware. Updating to a nougat custom rom to a marshmallow firmware would be bad as the api's are completely different and would explain the non booting situation.
So, until someone can confirm that flashing a nougat custom rom over a marshmallow base is 100% safe I'm going to swing with "yes I'm sure".
Beamed in by telepathy.
shivadow said:
So, until someone can confirm that flashing a nougat custom rom over a marshmallow base is 100% safe I'm going to swing with "yes I'm sure".
Click to expand...
Click to collapse
Re-read what I posted. I never said that it would be "100% safe" *. Of course there'll be problems due to the mismatch. I was only asking whether there have been reports about bootloops. (Btw, Android n and Android m don't differ as much as Android m and Android l did.) And according to this post the brick didn't happen directly after flashing the nougat rom.
However, I searched through the dev section yesterday and according to the Viper thread and the 4.x TWRP Backup thread people have been able to boot nougat roms on Android m. A lot of them faced problems. E.g. I have read about many user who used the old firmware and faced overheating and/or battery drain problems in the backup thread. They all needed to root their rom for getting rid of the problems. (Altough I personally can't explain why SuperSU should be able to fix those problems...) It seems like users with the newer firmware on the other hand don't necessarily have to face these issues. Take my phone as an example. It's running just fine without any heat and/or battery problems.
* Although I think that the usage of "safe" might imply that flashing a rom might damage your phone and that's not the case. The worst things that can happen are a bootloop or if the rom is booting fine some lags/bugs. Only flashing an incompatible firmware (via a RUU or a firmware pack) leads to damages.
Edit: Don't know how I could forget that but the answer to the OP's original problem with the reception on ICE is probably explained with Q1 of the FAQ section.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
After you flashed the GSM RUU your phone should be working normally, again, if the Verizon RUU didn't damage it unrecoverably. In addition, you should be able to install two OTAs (the latter is the update for Android 7) via the software update function of the phone.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Since u didn't reply, i assume my device now damaged unrecoverably right?
EDIT: SORRY, I DID NOT GET ANY NOTIFICATION AND DONT READ THIS FORUM. VERY SORRY MY BAD. I AM VERY NEWBIE IN THIS KIND OF THINK.
Flippy498 said:
Edit: Don't know how I could forget that but the answer to the OP's original problem with the reception on ICE is probably explained with Q1 of the FAQ section.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Thanks for the reply. Again sorry for my previous quote just now. Yes i read that q&a section and i did not have any of the problem except no mobile internet data. I can receive and make a phone call. Only mobile internet data. I am from 3.35 firmware if i am not mistaken since there was no official update after I purchased the phone. But NOW, I faced the problem after flashed GSM RUU. I do it twice, through exe and sdcard method. I also changed my CID and MID as u told me to.
The thing is that we don't know your original CID and your original firmware version. Not every SKU had a 3.35.x firmware version. That's why I'm guessing what the first problem might have been. If you say that there hasn't been any update at that time you probably used one of the SKUs that didn't have a 3.35.x firmware since those are the majority of SKUs that received the Android n update at a later time. But again, I can only assume what happened.
The problems you're facing now are probably a consequence of the cross-flashing. If flashing a GSM RUU could fix them then they're unrecoverable.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
The thing is that we don't know your original CID and your original firmware version. Not every SKU had a 3.35.x firmware version. That's why I'm guessing what the first problem might have been. If you say that there hasn't been any update at that time you probably used one of the SKUs that didn't have a 3.35.x firmware since those are the majority of SKUs that received the Android n update at a later time. But again, I can only assume what happened.
The problems you're facing now are probably a consequence of the cross-flashing. If flashing a GSM RUU could fix them then they're unrecoverable.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
So if i can find my original firmware version, i can solve this problem (if the verizon does not damage it) by flashing that version on my phone right? The only thing that I remember on my phone after i bought it is, it does not have any bloatware such as kid mode app, and when i clicked on software update, it said "please connect to XXXX to check an update" or something like that. XXXX referred to service provider in usa but i dont remember what company it was. I think there are still hope to recover this device.
I don't think that we can recover the phone even if we knew it's original firmware. That's why they're called "unrecoverable" damages.
For a GSM M9 it doesn't matter which RUU you flash (as long as it isn't a CDMA RUU). So if one GSM RUU didn't fix the situation then a different one won't be able to do so, either. And that's the reason why the ReadMe thread warns everybody not to cross-flash firmware files.
That part of my last post you're referring to was an explanation why I think that you faced problems with ICE. It has nothing to do with your current situation.
Sent from my HTC One M9 using XDA Labs
I currently have a customer who has HTC One M9 at my house and it is the AT&T variant. They have it carrier unlocked so that it works on the T-Mobile service provider. Problem is they keep dropping GPS signal so I tried to check what their software version is. It looks like they have software version 5.0. I tried to use the are ruu to update it, but every time it gets into download mode to start loading the file or bootloader mode rather it just tells me that the phone is not the right software. I'm using the AT&T ruu. Is there any reason why this is not working? I also tried the carrier unlocked version but the phone is clearly of AT&T pedigree
Cid and mid needs to be known
Currently running super Sid but previously was AT&T Sid. I can change the SIDS anything I want with Chimera tools. I don't know what the mid is though I'm not even sure what a mid is
Changing the CID without changing the firmware has the same effect as drinking snake oil. In addition the SuperCID prevents the M9 from accepting OTAs. You should take a look at the ReadMe thread. All information you might need are either there or linked in the further reading section of that thread.
I personally don't think that people should use such tools as the one that you mentioned. You don't know what kind of commands the tool is actually using so that you don't have any control about what's happening to the phone. (Not to mention that you don't learn how to fix a problem if the tool fails due to whatever reason.) Most of the features that tool is offering for HTC devices are available for free and don't take longer than a handful of minute if done manually.
Sent from my HTC One M9 using XDA Labs
If I load the t-mobile cid will it take the tmobile ruu?
CID 11111111
MID OPJA11000
Need this to run on tmobile network. It is an AT&Tb phone
No, changing the CID is not enough since the MID of the T-Mobile US variant isn't the same as the one for the AT&T version. As said before, please read the ReadMe thread. The RUUs are sorted by MID and CID, there, and the conversion guide tells you what to do for converting one version of the M9 to another. Be aware that the US T-Mobile variant RUUs are not the ones at the top of the download section. Those are the ones for T-Mobile Germany and T-Mobile Poland.
I converted it to an AT&T unlocked
I've bought second hand m9 , this last was flashed and rooted because I found supersu integrated with it, the problem is some settings are missing comparing with regular m9 like mobile network sharing for example, is there a way to fix the problem?
First of all, never use a second hand device without reinstalling the whole OS. I factory resetted my M9 right after buying it. (And rooted it, etc...)
Just look at you CID and MID and find the latest RUU for your phone and install it.
Maybe the person that had it before removed the certain settings, because the HTC settings app is quite modular from what i've seen. The settings app is split into many apps. Probably when debloating it he accidentally deleted that. (For example, if you install HTC's chinese performance management tool, a new setting will pop up in the settings app. Same with Sense Toolbox)
Or if is already rooted, just install S-Team ROM (sun_dream's ROM).
where can i find cid mid numbers?
and what is the best rom should i install?
leo-pard said:
where can i find cid mid numbers?
and what is the best rom should i install?
Click to expand...
Click to collapse
I suggest you first install stock rom.
I have been searching for a while for how to update the rom image
I checked my phone and I found the following information:
***unlocked***
htc_himawhl pvt s-off
cid-11111111
os-3.41.651.4
feb 3 2016
I believe that my phone was for developers, so I downloaded devRUU "HTC One M9 4.30.617.12" from HTC website and I tried to install it but I got error 132 (get the correct RUU...)
I switched to another RUU "HTC One M9 4.27.651.4", but I got the same error error 132
I've tried to get my CID and MID numbers using CMD but I've got nothing, it shows me:
CID:
MID:
nothing, blank, no information. after some research I realized that it was CID free "unlocked"
the main question is, how can I upgrade my system to get my full setting options? I appreciate your help
Forget whatever you read. It's wrong and you should thank whichever god you believe in that the dev edition RUU didn't get flashed.
First of all, you own the Sprint version (SKU 651) which is a CDMA device. The dev edition RUU (SKU 617) is meant to be used on GSM devices only. Those are two completely different technologies used by different US network carriers. Flashing GSM files on CDMA devices or vice versa leads to unrecoverable hardware damages in most cases since those versions have different partition layouts. It's not even safe to flash Verizon (another CDMA carrier) files on a Sprint device or vice versa since even these models use different layouts.
Second, there is no such thing as an HTC phone without CID. The dev/"unlocked" version has CID BS_US002. If the app doesn't give you any info then it's not working. In addition, it's recommended to use the current firmware version for finding the correct RUU instead of MID and CID. With the latter you still need to guess a lot whereas the former gives you the exact version of the RUU that is flashable.
Btw, you should get rid of the SuperCID your phone is currently using (11111111) since it causes more problems than benefit.
You'll never be able to flash a 4.x RUU on a phone that uses firmware 3.x. The encryption keys changed between those two firmware versions. You'll need to update the phone by using unencrypted files (OTAs or - if you have S-OFF - custom made 4.x firmware packs). You should have S-OFF since getting the SCID is impossible without it (the same applies to getting rid of it). However, Sneakyghost doesn't support CDMA devices so I don't know whether there are any custom firmware packs you could use.
If I were you I'd take the time to carefully read the ReadMe thread and to make sure that I understand everthing. Then I'd use the conversion guide for getting rid of the SCID (you can ignore the warnings if you use a RUU for your current SKU 651). Afterwards, that phone should be able to receive 4.x OTAs so that it can get updated to the latest firmware.
Sidenote in regard to the original question with the missing settings: I could be wrong but if I'm not mistaken then it's completely normal that Sprint models lack the network sharing option since that carrier doesn't allow it and therefore asked HTC to remove that option.
what a wonderful explanation, it's all clear, thanks a lot!
one more question,
how do i know for sure that my M9 is CDMA and has not been only changed to sprint rom version ?
I've googled for the differences between CDMA and GSM, I found that CDMA network basically depends on the device itself, whereas the GSM network depends on the SIM card. However the Sprint HTC One M9 had a nano sim slot in it in order to connect to GSM 3G and 4G bands, which were not devloped yet in CDMA networks. if this is right, could I still use my GSM network through 3g or 4g?
Since LTE is a GSM-only technology there are not many "pure" CDMA devices, anymore. Nowadays, all CDMA phones support Sim cards and some GSM frequencies. However, that doesn't mean that you can get reception with every GSM carrier if you own a CDMA phone since different carriers use different frequencies. In addition, one and the same carrier might even be using different frequencies for its network depending on the location. You'll have to try out whether you can get mobile reception with your current carrier and that phone.
Assuming that no one tinkered with the hardware of that phone, you can find out its original MID by taking a look at the engraving on the bottom of the back side (c.f. the FAQ of the ReadMe thread).
Sent from my HTC One M9 using XDA Labs
It's written :
Model:0PJA120 FCC ID:NM80PJA120 M9u
2200
actually the phone can read my gsm sim card, I have no problem with that except I want to make sure if it is CDMA version or not
I've looked everywhere in the internet but I didn't find a direct answers
Mhm... That MID belongs to the T-Mobile US (GSM) model. But your firmware is a CDMA one. The question is whether your phone still has its original backplate or not. Normally, cross-flashing GSM and CDMA will make the phone failing to recognize sim cards.
You could contact HTC and ask them whether they can tell you what kind of M9 you own with the help of its IMEI.
Sent from my HTC One M9 using XDA Labs
yes it does recognize my sim card
thank you very much for your help:good:
I'll try to contact htc to solve this contradiction
I'm facing same problem....
Dear Leo-pard,
could you please help me out....is your problem solved after chatting with HTC Customer care..
I'm facing same problem as my HTC M9 is also not showing Mobile Network Sharing Option....
Please help me out also....
I'll be waiting for your reply...
A lot of carriers charge extra for hotspotting. More than likely mobile network sharing will be off because the carrier wants you to pay for it. What I don't know is if it is coded into the firmware or not.
Hey @Flippy498
I have a sitting HTC m9 and like you said have missing mobile network sharing settings. My phone is s off with locked bootloader.
What can I do to use USB tethering it mobile hotspot? Can I use a third party app to use them?
Thanks
I bought second hand htc M9, I found sprint rom in it :
"***unlocked***
htc_himawhl pvt
s-off
cid-11111111
os-3.41.651.4
feb 3 2016"
Click to expand...
Click to collapse
but in the back cover of the phone it was written model: 0PJA120 (that was Tmobile model)
I decided to convert it to dev Edition,I changed the CID and MID
I installed fullstock firware 4.23.617.1 then the RUU 4.23.617.1 and I rebooted the device but no simcard no imei no baseband,
* I tried to flash another kernel "HTC Sense Android 7.0 Nougat ElementalX-m9-5.00" so in order to perform the flashing:
I installed twrp-2.8.5.0-hima.img then I updated it to twrp-3.1.1-0-hima.img using sd card method
The recovery offer me to root the device so I accept,
After that I copied the ElementalX-m9-5.00 zip to sd card and flashed it using twrp recovery,
but, unfortunately, after rebooting to system it's stuck in logo screen and won't start nor reboot to download mode and couldn't connect to PC.
I need real help!
If you lose your reception and the sim doesn't get recognized after flashing a GSM RUU then you definitely own a CDMA model. Due to the different partition layouts of the CDMA and the GSM versions of the M9 you might have damaged the hardware at that point.
You can try un-converting the phone. If you're lucky the phone will be working, again.
The bootloop on the other hand probably got caused by an incompatible SuperSU version. Older TWRP versions flashed SuperSU versions that are only compatible with firmware 1.x of the M9. Due to the bootloop problem in connection with higher firmware versions that feature got removed from newer TWRP versions.
Sent from my HTC One M9 using XDA Labs
leo-pard said:
but, unfortunately, after rebooting to system it's stuck in logo screen and won't start nor reboot to download mode and couldn't connect to PC.
I need real help!
Click to expand...
Click to collapse
You need to hold volume up and power for about 15-20 seconds and phone will power off, then hold volume down and power to enter download mode.
From there I think it's simple for you. Do what @Flippy498 said.
Flippy498 said:
If you lose your reception and the sim doesn't get recognized after flashing a GSM RUU then you definitely own a CDMA model. Due to the different partition layouts of the CDMA and the GSM versions of the M9 you might have damaged the hardware at that point.
You can try un-converting the phone. If you're lucky the phone will be working, again.
The bootloop on the other hand probably got caused by an incompatible SuperSU version. Older TWRP versions flashed SuperSU versions that are only compatible with firmware 1.x of the M9. Due to the bootloop problem in connection with higher firmware versions that feature got removed from newer TWRP versions.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
I have tracked my phone details using IMEI in the internet and here is the information:
IMEI 35722**********
Model HTC One M9
Serial Number HT53********
Part 99HADF163-00
Series HIMA#UHL_64G-C9
Part Description SKU , HTC , Traditional Chinese , TWN , CA , Bootloader Lock , Silver/Golden , DEF00 , w/o SIM Lock ,
HIMA#UHL_64G-C9#ASIA
Customer Description 聯強國際股份有限公司
Country TAIWAN
Warranty start 2015/03/30
Warranty end 2016/06/30
Click to expand...
Click to collapse
I think the HIMA_UHL ASIA twn is gsm and its sku is 709, am i right?
BTW, I had access to the download mode after the battery was drained to 0, I'm keeping it in twrp recovery mode until I find a solution.
If your phone was GSM you wouldn't have lost your mobile reception and your sim card would have still been recognized after flashing the dev edition RUU. GSM variants can be converted from one version to another without any issues. If I were you I wouldn't trust whichever website you used and would ask HTC directly.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
If your phone was GSM you wouldn't have lost your mobile reception and your sim card would have still been recognized after flashing the dev edition RUU. GSM variants can be converted from one version to another without any issues. If I were you I wouldn't trust whichever website you used and would ask HTC directly.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
You are right, I flashed the sprint ruu edition and it works fine, then i flashed the twrp recovery and i rooted the device with supersu, and I followed some instruction to unlock the simcard, and finally everything is fine except the main problem which is the absence of mobile sharing network setting, and you already gave me a logical explanation for that.
thank you so much
I have learned flashing lesson from you