Hi Guys,
So I have an M9 which I bought on eBay brand new from China.
It came with an USA Rom which had been tweaked to work in the UK.
Anyhoo, I unlocked the bootloader, S-Off using Sunshine, installed a recovery, Rooted and SuperCID it.
They I replace the Rom with the international Rom:
0PJAIMG_HIMA_UHL_N70_SENSE80_MR_HTC_Europe_4.28.401.3_Radio_01.01_U114401011_117.00.61117G_2_F_release_498151_signed_2.zip
I had to change my MID from 0PJA11000 to 0PJA10000 for it to work.
Well it all works beautifully except the Phone.
I am sure I have the wrong Radio for the UK.
The signal is weak and cuts out, I know I'm in a very strong signal area and all my other phones work fine. Indeed I had the same problem with my M8 until I changed Radios.
Now I have used (or tried to use) every Radio in this thread:
https://forum.xda-developers.com/one-m9/general/recovery-flashable-radio-zip-t3122983
But none of them stick, sure they go through the motions of flashing and even say they had finished (Using TWRP) but they don't actually change the Radio.
Currently my Radio is:
01.01_U114401011_117.00.61117G_2
Im in the UK and I'm on the O2 network so I need a Radio specific for that.
I downloaded this Rom:
0PJAIMG_HIMA_UHL_M60_SENSE70_MR_O2_UK_3.35.206.13_Radio_01.01_U11440792_93.00.51117G_F_release_464855_signed
But I get Error 12 whilst trying to install.
Do I have to just change my MID back to 0JPA11000?
If it's not that I'm at a loss as to what the problem is.
Here is my Getvar:
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) serialno: ***************
(bootloader) current-slot:
(bootloader) imei: *******************
(bootloader) version-main: 4.28.401.3
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U114401011_117.00.61117G_2_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: 11111111
Please help me get this sorted, its such a great phone..
Thanks
Oh joy....
Well I've been up all night after soft bricking my phone.
Eventually managed to install the O2 RUU I wanted!!
Had to format a 8GB microsd to fat32 so the phone would see it even though the hboot said it was on 4.xx firmware.
I also couldn't write mid or cid, they wouldn't change.
Anyhoo formatted microsd copied RUU onto it renamed OPJAIMG and it worked!!
BUT NOW....
Well now I want the OTA which it downloads then says my software's not official...
So do I have to relock it, s-on it and unroot it for the ota or can I just flash it from somewhere?
All I know is I've got the correct Radio installed.
So that's good!
Any help from the Pro's would be much appreciated.
I believe what I will do is update the firmware in increments no-wipe using the firmware thread...it's got the correct O2 ones on there.......If only I could find it..
No that won't work...the firmwares are older than what I already have installed...
Anyone got any ideas?
I just want to receive the OTA really, how do I convince my phone its genuine?
OR
Where does it download it to so I can rename it and flash it? (Can I do that?)
Well guys I'm getting there, I have found the OTA on this site so am downloading now.
Hopefully that will be that and I can get some sleep!
Now I'm getting Error 12...
How do I sort that?
In the error listings 12 is not sure what it is...
So in my wisdom(!) I thought it couldn't make a giant leap from firmware 3 to 4.
I figured(!) It need the firmware in between.
4.14.617.6 So I downloaded that and whilst trying to flash it sdcard method I get error code 7
All I know is that the M7 and M8 were a lot easier to do!
My New Getvar:
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei: ************
(bootloader) version-main: 3.35.206.13
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440792_93.00.51117G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA11000
(bootloader) cid: O2___001
Well I've now changed my MID to 0PJA10000 and that's not worked even though that is the right MID and so I then changed the CID from the correct O2 one to Super CID which I believe is 8 1's...so 11111111.
But that hasn't worked...
What have I got to do guys, it's not this difficult ever, what's going wrong?
I know I'm not rooted any more and I don't have a custom recovery but that shouldn't matter or does it?
I hope this isn't one of those threads that just sits here...
Why I had an O2 UK RUU that gave me a MID of 0PJA11000 makes no sense if it's supposed to be 0PJA10000...and that one worked!!
I'm stuck as to what to do......
Well I've gone in a big loop only to end up with the international version back on my phone. Its the latest one, the O2 ones although they have the right radio are stuck on Lolipop or Marshmallow. They want to update but cant as my phone software is not recognised as official due to being rooted....
So I have the phone back up and running on WWE but the signal is dire.
If anyone can tell me how to extract the radio from the O2RUU and apply it to my phone it would be appreciated...if not I will just send my phone back to HTC and get them to do it.
I've never seen such scrappy out of date software.
I'll just start at your first post and reply to everything that catches my eyes since you already created that many posts in this thread. In general I highly recommend you to carefully read the ReadMe thread.
In general: Are you sure that you bought a GSM variant and not a CDMA one? These technologies aren't compatible with each other an flashing GSM files on a CDMA device or vice cersa always leads to headaches (worst case: unrecoverable hardware damages).
Post 1: It doesn't matter whether you use the unbranded 401 baseband or the O2 branded 206 one. The reception should be the same. (CDMA devices can't read their own IMEI anymore and lose all reception if you flash GSM RUUs on them, though.)
SCID isn't recommended to be used anymore. It prevents your phone from installing OTAs and it won't make your phone ignore MID mismatches with RUUs like it did on the M8 and older HTC devices.
Post 2: The M9 and all newer devices don't have an hboot, anymore. There's the download mode and the aboot which replace what you know as hboot from older HTC devices.
Never re-lock this phone or re-S-ON it unless you know for 100000000000000 % that it's absolutely 100 % stock and completely unmodified. There are security checks which will prevent the phone from booting if it's modified and you e.g. re-lock the bootloader.
Post 6: Error 12 indicates that you tried to flash a RUU with a different encryption key than the one your phone's current firmware is using.
Post 7: I haven't seen error 7, before. Since you already had problems with flashing the other RUU via your SD card while the SD card wasn't formatted to fat32 I assume it might indicate some SD card hardware issue.
Post 9: RUUs can't change your MID. That's something you need to do manually via fastboot commands.
Post 11: If the OTAs fail although you directly used a RUU beforehand than you're either using the wrong MID or an incorrect CID. The only other possible reason might be that you're suffering from the first symptoms of a nand death. Like all smartphones with the Snapdragon 810, the M9's hardware can suddenly die due to the hardware damages that get caused by the heat of the infamous processor.
Flippy498 said:
I'll just start at your first post and reply to everything that catches my eyes since you already created that many posts in this thread. In general I highly recommend you to carefully read the ReadMe thread.
In general: Are you sure that you bought a GSM variant and not a CDMA one? These technologies aren't compatible with each other an flashing GSM files on a CDMA device or vice cersa always leads to headaches (worst case: unrecoverable hardware damages).
Post 1: It doesn't matter whether you use the unbranded 401 baseband or the O2 branded 206 one. The reception should be the same. (CDMA devices can't read their own IMEI anymore and lose all reception if you flash GSM RUUs on them, though.)
SCID isn't recommended to be used anymore. It prevents your phone from installing OTAs and it won't make your phone ignore MID mismatches with RUUs like it did on the M8 and older HTC devices.
Post 2: The M9 and all newer devices don't have an hboot, anymore. There's the download mode and the aboot which replace what you know as hboot from older HTC devices.
Never re-lock this phone or re-S-ON it unless you know for 100000000000000 % that it's absolutely 100 % stock and completely unmodified. There are security checks which will prevent the phone from booting if it's modified and you e.g. re-lock the bootloader.
Post 6: Error 12 indicates that you tried to flash a RUU with a different encryption key than the one your phone's current firmware is using.
Post 7: I haven't seen error 7, before. Since you already had problems with flashing the other RUU via your SD card while the SD card wasn't formatted to fat32 I assume it might indicate some SD card hardware issue.
Post 9: RUUs can't change your MID. That's something you need to do manually via fastboot commands.
Post 11: If the OTAs fail although you directly used a RUU beforehand than you're either using the wrong MID or an incorrect CID. The only other possible reason might be that you're suffering from the first symptoms of a nand death. Like all smartphones with the Snapdragon 810, the M9's hardware can suddenly die due to the hardware damages that get caused by the heat of the infamous processor.
Click to expand...
Click to collapse
Thanks Flippy, I learn so much every time I post here you are truly experts.
I will look at all my posts as questions solved by the last post!
I'm pretty sure it's GSM but would love to know how to check.
I have through chance, luck and what I thought was knowledge secured a good running International RUU....
I am rooted, unlocked, supercid and running beautifully.
Yet my Radio is wrong.
I try and try (this was the start of the post and is still the end) to try and install a new Radio.
When using the old O2 RUU it was clear that was the correct Radio.
An old one!
However I have not been able to flash any other Radio from the M9 Radio post.
This as you can imagine is a huge problem as much that we all like to use our phones as superfast little Chromebooks, they are first and foremost Phones!!!
If I cannot find a good Radio I must get HTC to sort it for me.
It would be wonderful if I could find a tutorial on how to pull the Radio from a firmware Rom as I have the old O2 RUU that has a Radio (all be it old) that suits my needs.
I've not been able to find such a Radio and unfortunately the RUU that would have been exactly what I was looking for turned out to be German and as such had the incorrect Radio.
I can't believe (but believe I must) that HTC UK do not support rooted phone and provide the software as they do for the USA....but there you go they don't.
They have however offered to "fix" my phone...i.e. replace the software...for a price I may add, rather than providing me with software and allowing me to do the 5 second operation for free...
That's where I'm up to Flippy, its kept me awake for over 36hrs and ruined my weekend.
Thank goodness for Bank Holidays.
May I add that the M9 is my favorite HTC so far, I have played with the SPV (Very slow but very cool!!) One X (Popular but over rated), One X+(great phone for the time), the M7 (Equally an excellent phone), the M8 (lasted me for years, amazing) and now the M9. I don't like the M10 because of the iPhone/Samsung One button and I haven't been privy to the U11/U12/U12+ but don't much rate anything you have to squeeze...let alone get a decent case for so your £700 (I can buy a car for that) phone doesn't get a scratch....at the end of the day a Nokia Dumb phone was good enough and a Laptop was a laptop.
I know it's going to progress to jewelry, glasses and smart clothes...then onto holographic VR and Thought(!) and Implants(!) but all I want is a phone that does a few things, first and foremost PHONE people!
God bless technology and God bless the back engineering from downed UFO's.
But technology and the concept of God doesn't sit right.
So thank Science!
eskimosound said:
I've not been able to find such a Radio and unfortunately the RUU that would have been exactly what I was looking for turned out to be German and as such had the incorrect Radio.
Click to expand...
Click to collapse
As already explained in your other thread. There is no "German" RUU. HTC got rid of a whole bunch of SKUs with the M9. Several countries now share the same SKU (and therefore the same firmware) while only the CID differs. You were using the correct baseband after you had flashed the 4.27.206.4 RUU. Officially, it's even labeled as O2 UK RUU by HTC.
However, I took a closer look at the latest O2/206 and the latest unbranded European/401 RUU. Both use the exact same baseband/radio version. So whatever your issue is, it's not baseband related.
eskimosound said:
I can't believe (but believe I must) that HTC UK do not support rooted phone and provide the software as they do for the USA....but there you go they don't.
Click to expand...
Click to collapse
They never provided RUUs outside the US. And HTC even stopped providing RUUs for all of their newer phones. The HTC 10 is the latest model for which you can find RUUs on their US website.
Finding out whether you own a CDMA device or a GSM one can be quite easy if no one has ever replaced the backplate of the phone. There's a small engraving with the MID at the bottom of the backplate. If the backplate got replaced it's impossible to say which version you own, though. With S-OFF you can cross-flash GSM files on CDMA devices and vice versa after you manually changed the MID since S-OFF means nothing else than all Security checks being set OFF. And after cross-flashing, there's no way to find out which version you own via the software.
Flippy498 said:
I'll just start at your first post and reply to everything that catches my eyes since you already created that many posts in this thread. In general I highly recommend you to carefully read the ReadMe thread.
In general: Are you sure that you bought a GSM variant and not a CDMA one? These technologies aren't compatible with each other an flashing GSM files on a CDMA device or vice cersa always leads to headaches (worst case: unrecoverable hardware damages).
Post 1: It doesn't matter whether you use the unbranded 401 baseband or the O2 branded 206 one. The reception should be the same. (CDMA devices can't read their own IMEI anymore and lose all reception if you flash GSM RUUs on them, though.)
SCID isn't recommended to be used anymore. It prevents your phone from installing OTAs and it won't make your phone ignore MID mismatches with RUUs like it did on the M8 and older HTC devices.
Post 2: The M9 and all newer devices don't have an hboot, anymore. There's the download mode and the aboot which replace what you know as hboot from older HTC devices.
Never re-lock this phone or re-S-ON it unless you know for 100000000000000 % that it's absolutely 100 % stock and completely unmodified. There are security checks which will prevent the phone from booting if it's modified and you e.g. re-lock the bootloader.
Post 6: Error 12 indicates that you tried to flash a RUU with a different encryption key than the one your phone's current firmware is using.
Post 7: I haven't seen error 7, before. Since you already had problems with flashing the other RUU via your SD card while the SD card wasn't formatted to fat32 I assume it might indicate some SD card hardware issue.
Post 9: RUUs can't change your MID. That's something you need to do manually via fastboot commands.
Post 11: If the OTAs fail although you directly used a RUU beforehand than you're either using the wrong MID or an incorrect CID. The only other possible reason might be that you're suffering from the first symptoms of a nand death. Like all smartphones with the Snapdragon 810, the M9's hardware can suddenly die due to the hardware damages that get caused by the heat of the infamous processor.
Click to expand...
Click to collapse
Flippy498 said:
As already explained in your other thread. There is no "German" RUU. HTC got rid of a whole bunch of SKUs with the M9. Several countries now share the same SKU (and therefore the same firmware) while only the CID differs. You were using the correct baseband after you had flashed the 4.27.206.4 RUU. Officially, it's even labeled as O2 UK RUU by HTC.
However, I took a closer look at the latest O2/206 and the latest unbranded European/401 RUU. Both use the exact same baseband/radio version. So whatever your issue is, it's not baseband related.
They never provided RUUs outside the US. And HTC even stopped providing RUUs for all of their newer phones. The HTC 10 is the latest model for which you can find RUUs on their US website.
Finding out whether you own a CDMA device or a GSM one can be quite easy if no one has ever replaced the backplate of the phone. There's a small engraving with the MID at the bottom of the backplate. If the backplate got replaced it's impossible to say which version you own, though. With S-OFF you can cross-flash GSM files on CDMA devices and vice versa after you manually changed the MID since S-OFF means nothing else than all Security checks being set OFF. And after cross-flashing, there's no way to find out which version you own via the software.
Click to expand...
Click to collapse
Thanks Flippy, very informative.
It's a new phone, came in a sealed box.
Marking on the back of phone:
Model: 0PJA100 FCC ID: NM80PJA100 M9u
I can't find what I need, so I will send to HTC.
I didn't want to root this M9 but had to as supplied with USA software. But have conceded and will let HTC deal with it.
Thanks for your time.
According to everything you described it's impossible that you bought a new phone. And I wouldn't trust a seller just because the device got shipped sealed. Breaking a seal and re-sealing the box at a later point isn't that difficult.
Assuming that the backplate didn't get replaced, the MID on the backside indicates that you own the international hardware variant. Without tinkering (in other words: without opening the box and breaking the seal) it's not possible to flash US firmware on that device.
And if we assume that the backplate indeed got replaced it's even less possible that you bought a "new" phone.
Sent from my HTC U12+ using XDA Labs
Flippy498 said:
According to everything you described it's impossible that you bought a new phone. And I wouldn't trust a seller just because the device got shipped sealed. Breaking a seal and re-sealing the box at a later point isn't that difficult.
Assuming that the backplate didn't get replaced, the MID on the backside indicates that you own the international hardware variant. Without tinkering (in other words: without opening the box and breaking the seal) it's not possible to flash US firmware on that device.
And if we assume that the backplate indeed got replaced it's even less possible that you bought a "new" phone.
Sent from my HTC U12+ using XDA Labs
Click to expand...
Click to collapse
I might right it off then and go for a U11.
Will see what HTC say and yeah I don't trust the company I bought it from, once I unlocked it I was sure there was tampering......
Wwe works just as good as o2 firmware. Can you flash an m9u with m9 firmware?.
The M9u is the M9. The u only indicates that you're talking about one of the GSM variants and not about one of the CDMA ones (M9w).
Sent from my HTC U12+ using XDA Labs
Flippy498 said:
The M9u is the M9. The u only indicates that you're talking about one of the GSM variants and not about one of the CDMA ones (M9w).
Sent from my HTC U12+ using XDA Labs
Click to expand...
Click to collapse
Just been told by HTC that the phone is a counterfeit!
The IMEI and Serial Numbers just don't exist.
Thankfully I'm covered by PayPal who are now dealing with it, but really...!!!
First time in the 10 years I've been doing this that I've bought fake...
Related
Good
I have a htc one m8 Mobile operator T; changing operator in my country of origin and previously used frequency 850 mhz and 1900; and the new operator uses frequency band 3G and 4G to 900 mhz and m8 T Mobile does not accept that band there any possibility to change this frequency.
I am root, S-Off, super CID Android 6
Some help.
greeting
Enviado desde mi hTC One_M8
You're s-off, so this isn't too hard. You can either flash another carrier versions firmware.zip, or RUU. Euro and Asia versions should support 900 Mhz for both 3G and LTE (at least in theory - see more below regarding LTE).
You may need to change MID, depending on what route you want to go, and what file you use.
But it should also be noted, that I've seen a number of folks that properly changed to a firmware (or full RUU conversion) containing the radio which supports their carrier's LTE band. But they still were not able to get LTE service. I don't know the reason for this, and have not seen any solution. So be aware, that there is a possibility you may not get LTE, even after adding the proper band support. But you should at least be able to get 3G on 900 MHz.
Firmwares (and info on flashing) are posted here: http://forum.xda-developers.com/htc-one-m8/development/progress-fuu-m8-t2813792
RUUs are posted in a variety of places. But I can advise, depending on what variant you want to "convert" to (Asia or Euro) if you want to go RUU route. You'll also need to change MID if you decide this route.
redpoint73 said:
You're s-off, so this isn't too hard. You can either flash another carrier versions firmware.zip, or RUU. Euro and Asia versions should support 900 Mhz for both 3G and LTE (at least in theory - see more below regarding LTE).
You may need to change MID, depending on what route you want to go, and what file you use.
But it should also be noted, that I've seen a number of folks that properly changed to a firmware (or full RUU conversion) containing the radio which supports their carrier's LTE band. But they still were not able to get LTE service. I don't know the reason for this, and have not seen any solution. So be aware, that there is a possibility you may not get LTE, even after adding the proper band support. But you should at least be able to get 3G on 900 MHz.
Firmwares (and info on flashing) are posted here: http://forum.xda-developers.com/htc-one-m8/development/progress-fuu-m8-t2813792
RUUs are posted in a variety of places. But I can advise, depending on what variant you want to "convert" to (Asia or Euro) if you want to go RUU route. You'll also need to change MID if you decide this route.
Click to expand...
Click to collapse
Thank you for this valuable info!
guorium said:
Thank you for this valuable info!
Click to expand...
Click to collapse
Tread carefully. The information I gave was for the original poster's specific case. It may or may not apply in your case, and even be dangerous! For instance, if you have the Sprint or Verizon version M8, trying to flash a different radio or firmware will result in a radio brick (possibly permanent)! And you can't always easily tell if it a Sprint/Verizon version - we've seen these devices modified by third party vendors to appear "unbranded".
For the best info and help, please post your specific device info. Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
redpoint73 said:
Tread carefully. The information I gave was for the original poster's specific case. It may or may not apply in your case, and even be dangerous! For instance, if you have the Sprint or Verizon version M8, trying to flash a different radio or firmware will result in a radio brick (possibly permanent)! And you can't always easily tell if it a Sprint/Verizon version - we've seen these devices modified by third party vendors to appear "unbranded".
For the best info and help, please post your specific device info. Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
Click to expand...
Click to collapse
Yes I read the unlock qualcomm post and it looks like a dozen GSM handsets failed and only CDMA devices successed. I am just trying to change the radio of mine which getvar reports to be a china mobile issued phone (certainly GSM). The Chinese radio does not support it vital 3G band (900MHz my carrier uses) in my home suburb. Apparently from some digging I did on the Australian forum whirlpool, all three carriers in Australia got different firmware versions but the radio img is all the same and the same radio means all 3 carriers are supported by m8 running the aussie radio in Australia. So I am doing soff on my handset to modify MID and CID so I can flash a Australian firmware to my phone and have full reception at home.
Funny enough I cannot get those firmwares from all three carriers nor htc australia. Their online chat support all refused to offer firmware to me. They did not even tell what the firmware versions are so I could look for it (wasted my time but my research paid off). Fellows on whirlpool offered their RUU in zip form for download. I can't easily tell if the Aussie radio support the bands I needed without using one of the fellow's imei to search for band support spec on imei.info. So yeah not hiding it helped me. I really want to just flash the aussie radio on top of the Chinese firmware I already got though. No one has the radio image for download. Do you know how to extract it from a 0P6BIMG.zip? I kinda wanna avoid having to extract the radio myself... it takes a while to put the Aussie firmware on and after that, extracting radio image would be almost pointless since it is already installed.
See my responses below in red font:
guorium said:
I am just trying to change the radio of mine which getvar reports to be a china mobile issued phone (certainly GSM). The Chinese radio does not support it vital 3G band (900MHz my carrier uses) in my home suburb.
So I am doing soff on my handset to modify MID and CID so I can flash a Australian firmware to my phone and have full reception at home.
If it is the Chinese M8 variant I'm thinking of, I don't think this will work.
Further, s-off is only possible with sunshine app ($25 US), which is probably wasted money for the above reason.
Please post your getvar data (deleting IMEI and serial number before posting) as previously requested, so we can advise more properly.
Funny enough I cannot get those firmwares from all three carriers nor htc australia. Their online chat support all refused to offer firmware to me. They did not even tell what the firmware versions are so I could look for it
I've never heard of HTC supplying firmware that way. Most they will do is send the RUU for your phone version. They will not support you changing your M8 to another version (different CID, MID) and therefore not supply those files. Also, there are a lot of CIDs that do not even have RUU.
No one has the radio image for download. Do you know how to extract it from a 0P6BIMG.zip? I kinda wanna avoid having to extract the radio myself... it takes a while to put the Aussie firmware on and after that, extracting radio image would be almost pointless since it is already installed.
I don't recommend only flashing the radio. img. Better to flash the whole firmware.zip, to make sure all the partitions are compatible. When I saw "firmware.zip" this is a small package that contains radio, hboot, and a few other partitions, but does not contain the ROM.
Then you say "firmware" it sounds like you are referring to the RUU or ROM, in which case please just say RUU or ROM, to avoid confusion.
Click to expand...
Click to collapse
redpoint73 said:
See my responses below in red font:
Click to expand...
Click to collapse
Yes it is a 1.5G big boy. A RUU in 0P6BIMG.ZIP form. Changed to super CID and Australian MID. I am flashing it whole now. Keeps reporting large image update fail. Fastboot getvar all below
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.23.213311231.14G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.30.1403.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: nopenopenope
(bootloader) imei: nopenopenope
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_tl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse
Far as I know the Chinese variant isn't compatible with the RUU or firmware.zip for "standard" M8. It's product name is m8_tl
Where most other M8 variants are m8_ul
M8 variants that share the same product name M8_ul can be "converted" between each other using the RUU. M8 variants with different product name (like yours) in every case I've seen, the RUUs are not cross compatible.
Further, the "large image" error when flashing RUU is commonly seen when you try to flash an RUU for a different hardware.
Not sure if it is technically a different hardware, but I tend to think it is. From what I'm reading, China has a specific implementation of 3G, which probably required different hardware.
Moral of the story, I don't think you can mod this phone to add the desired band support.
redpoint73 said:
Far as I know the Chinese variant isn't compatible with the RUU or firmware.zip for "standard" M8. It's product name is m8_tl
Where most other M8 variants are m8_ul
M8 variants that share the same product name M8_ul can be "converted" between each other using the RUU. M8 variants with different product name (like yours) in every case I've seen, the RUUs are not cross compatible.
Further, the "large image" error when flashing RUU is commonly seen when you try to flash an RUU for a different hardware.
Not sure if it is technically a different hardware, but I tend to think it is. From what I'm reading, China has a specific implementation of 3G, which probably required different hardware.
Moral of the story, I don't think you can mod this phone to add the desired band support.
Click to expand...
Click to collapse
Ok thanks for the help. The phone appears to be limbo now. I tried to flash Aussie RUU as 0B6PIMG.zip and it gives me the large file error. Then I thought oh maybe it is because it is still unlock flag for bootloader (But I thought it should not matter sin Soff is there). So I used the fastboot oem lock command. It went to relock. I still cannot flash it. So I used fastboot flash zip RUU.zip to flash A small ~30MB Aussie firmware which actually when through fine, then I flashed the newer version of that firmware (the old one had to be done first). That turned my OS number in the bootloader to the Aussie one instead of Chinese.
Then I cannot flash any RUU in 0B6PIMG.zip anymore, not aussie not Chinese. I can only enter bootloader now. No recovery is present. Cannot flash recovery and cannot unlock bootloader with token. Both just tell me failed. If I try to flash 0B6PIMG.zip via usb cable with "fastboot flash zip 0B6PIMG.zip". It says "load_file: could not allocate blah blah bytes" when I am sure there is a lot of space left. AT&T RUU exe cannot write successfully too.
So I got a semi brick with bootloader only now haha. The 3 little androids look cute though.:cyclops:
guorium said:
So I got a semi brick with bootloader only now haha. The 3 little androids look cute though.:cyclops:
Click to expand...
Click to collapse
Maybe I wasn't clear, but you really should have stopped when I said your device is not compatible with other M8 firmware. It is almost certainly a different hardware, which means flashing the wrong firmware (anything but firmware for m8_tl) is not only going to not work (phone will not function properly), but may result in permanent damage.
Just because the firmware flashed, does not mean it is a good thing. You've removed all the safeguards by doing s-off, changing the CID/MID. So it will flash, no surprise there. But folks have previously done something similar with the US CDMA variants (m8_wlv and m8_whl) by trying to flash firmware for m8_ul (the "standard" M8, the most common product name) which results in a radio brick.
These variants are never partitioned the same. What you have done is overwritten the wrong partitions with the m8_ul firmware.zip. Unless there is an RUU or firmware zip for m8_tl, there probably is not a way to fix this.
redpoint73 said:
Maybe I wasn't clear, but you really should have stopped when I said your device is not compatible with other M8 firmware. It is almost certainly a different hardware, which means flashing the wrong firmware (anything but firmware for m8_tl) is not only going to not work (phone will not function properly), but may result in permanent damage.
Just because the firmware flashed, does not mean it is a good thing. You've removed all the safeguards by doing s-off, changing the CID/MID. So it will flash, no surprise there. But folks have previously done something similar with the US CDMA variants (m8_wlv and m8_whl) by trying to flash firmware for m8_ul (the "standard" M8, the most common product name) which results in a radio brick.
These variants are never partitioned the same. What you have done is overwritten the wrong partitions with the m8_ul firmware.zip. Unless there is an RUU or firmware zip for m8_tl, there probably is not a way to fix this.
Click to expand...
Click to collapse
Yes thanks for your advise. Very helpful indeed! I got good support from HTC China. They provided all RUUs including my model for everyone to download. I found out some other dude writing a blog post about how m8_tl can only use m8_tl's RUUs (there are two, one bring lighter with less carrier ****). No surprise my attempt to flash m8_ul's RUUs never succeeded. It will not even begin when I load up the 0P6BIMG.zip. I just unlocked bootloader again (needed a new token since MID was altered) so I can flash twrp and in turn use the adb shell to edit my MID back to orginal so I can put on the lighter version of stock RUU.
The lighter one still runs much better than China Mobiles tainted RUU. It cannot be done unless you soff. The soff was definitely worth it. I flashed some Australian radios and none of them give me the desired 3G band. It kinda behaved the same as the Chinese stock radio image. Very weird. Perhaps the Chinese GSM version of M8 are actually having different hardware compared to the international version. I just have not seen anyone rip a m8_tl apart and introduce us all the components.
I was very much aware that flashing CDMA RUU could do very bad things to a GSM M8. So I did not even think about it. Suppose my last hope of getting an extra 3G band is using QPST but that sounds very dangerous and I have just seen CDMA types succeeding. Will carefully read first...
UPDATE: I skimmed over all M8 related postes on that massive "Unlock all bands for Qualcomm" post. Apparently only the CDMA handsets worked. Those with GSM phones did not get it to work... Probably a hardware limitation. I will stay on my current state of my phone then. I came across a couple Chinese posts talking about replacing carrier_policy.xml with QPST on my exactly model m8t. That had no choice of specific bands. It simply sets the rules of network switching when various SIMs are inserted. Interesting none the less.
guorium said:
Yes thanks for your advise. Very helpful indeed! I got good support from HTC China. They provided all RUUs including my model for everyone to download. I found out some other dude writing a blog post about how m8_tl can only use m8_tl's RUUs (there are two, one bring lighter with less carrier ****). No surprise my attempt to flash m8_ul's RUUs never succeeded. It will not even begin when I load up the 0P6BIMG.zip. I just unlocked bootloader again (needed a new token since MID was altered) so I can flash twrp and in turn use the adb shell to edit my MID back to orginal so I can put on the lighter version of stock RUU.
The lighter one still runs much better than China Mobiles tainted RUU. It cannot be done unless you soff. The soff was definitely worth it. I flashed some Australian radios and none of them give me the desired 3G band. It kinda behaved the same as the Chinese stock radio image. Very weird. Perhaps the Chinese GSM version of M8 are actually having different hardware compared to the international version. I just have not seen anyone rip a m8_tl apart and introduce us all the components.
I was very much aware that flashing CDMA RUU could do very bad things to a GSM M8. So I did not even think about it. Suppose my last hope of getting an extra 3G band is using QPST but that sounds very dangerous and I have just seen CDMA types succeeding. Will carefully read first...
UPDATE: I skimmed over all M8 related postes on that massive "Unlock all bands for Qualcomm" post. Apparently only the CDMA handsets worked. Those with GSM phones did not get it to work... Probably a hardware limitation. I will stay on my current state of my phone then. I came across a couple Chinese posts talking about replacing carrier_policy.xml with QPST on my exactly model m8t. That had no choice of specific bands. It simply sets the rules of network switching when various SIMs are inserted. Interesting none the less.
Click to expand...
Click to collapse
I ended up testing possibility on my machine. The Chinese method in changing policy file with EFS explorer did not give me 900MHz. I then edited NV values with QXDM to enable 900MHz and again it did not give me reception even when the edits were sticking. Just to test I removed 2100MHz as well and sure that killed the 3G reception. My lesson is the TDSCDMA version of m8 just has different hardware compared to the global version. It is incapable of picking up 900MHz. I reflashed the stock RUU and everything is normal again. No brick.:good:
I recently got my hands on a One M9 but I'm having trouble updating anything on it. I check for updates and it says there aren't any available. However, my software version is 1.14.531.1, which is older than anything I've seen in any threads anywhere.
Here's the readout from fastboot getvar all:
kernel: lk
product: htc_himaul
version: 1.0
vzwisLTE:
vzwmid: HTC
max-download-size: 800000000
imei:
battery-status: good
version-main: 1.14.531.1
boot-mode: download
version-bootloader: 1.0.0.0000
mid: 0PJA12000
cid: 11111111
It doesn't say it here, but the phone is s-off.
I started by following the instructions at Cyanogenmod: unlocked, installed TWRP, installed ROM. However, it wouldn't install the ROM. It failed at the point where it tries to verify the device. I changed the recovery to the Cyanogenmod recovery and tried again, but that didn't work either. After a bit of reading, I thought that perhaps I needed to update the bootloader and that a RUU update might do the trick. I got the most recent one from HTC and ran it. It stalled where it says "sending" at 0%. I put the ROM.zip on the SD card to try it that way. That also failed. I relocked the bootloader and tried the RUU again with the same result.
I've wondered if I need to update the firmware per this thread http://forum.xda-developers.com/one-m9/development/firmware-t3068243 but I'm still new to the HTC world and not sure if that's it or if I'm just guessing. The firmware files I found there are much smaller than I expected, so I'm not sure what exactly they will update or if they'll fix the problem or just make it worse.
Can anyone tell me where to go from here, or at least point me in the right direction?
You can't flash offical firmwares unless your phone is stock. I think you should be ok flashing unsigned zips though. I couldn't tell you if htc do incremental or if you can just flash the latest. Flippy's thread might shine a light on something.. Your Cid is supercid.
Beamed in by telepathy.
So, are you saying that if I go back to the stock recovery that I should be able to use the RUU to update everything? There are a bunch of stock recoveries here, but none of them match my phone. The oldest ones there are several versions newer than mine and none match my CID. Can I still use one of them or do I need to find one that matches my phone exactly?
When I got the phone there was an SD card in it with a 0PJAIMG.zip file and a text file with a very long name with the software version (1.14.531.1) in it. Fortunately I saved them. I put those files back on and tried flashing that 0PJAIMG file and this time it worked. It seems to have removed the recovery I put on it and now it looks completely stock, with a locked bootloader and everything. Updating with the latest RUU still doesn't seem to work, however. It's still stalled at "sending" and 0%.
I would like to try a different RUU that's a smaller jump, but I haven't had any luck finding one yet.
OTA updates are incremental. A RUU on the other hand contains the whole firmware that has been distributed for its SKU until the point that RUU got released. Besides it contains the whole system. That's why RUUs are so big.
Sneakyghost's files lack some parts of the official firmware packs since they're not meant to get flashed if you want to get back to stock. They're meant to get flashed if you want to update your phone's firmware without reverting it's system back to stock since this way is less time consuming if you want to flash a new custom rom afterwards. That's why they're so much smaller than a RUU. Besides, they're unsigned and you won't be able to use them without S-OFF.
I personally don't like the *.exe versions of RUUs since they use fastboot and many users aren't able to set up their adb/fastboot environment correctly. Therefore, I neither support flashing RUU.exe files nor fastboot flashing of RUU.zip files. However if you extract the RUU.zip from the latest x.xx.531.x RUU.exe you could flash it via a SD card. I don't have a direct link to a guide for the extraction at the moment but there should be several here on xda which you should be able to find via google. It doesn't matter if they're written for an older HTC phone since the steps you need to do are always the same. Instructions for flashing a RUU via SD card can be found in my google sheet (which is linked in my signature).
And one last thing: The SCID prevents the M9 from installing OTAs. Therefore, you should revert it back to its original CID if you want to install any OTA.
Personal opinion: Since you can't use RUUs with a different MID than the one of your phone although you use the SCID (that was possible on older HTC phones) and you aren't able to install OTAs if you use it (that was possible on older phones, too) I personally don't think that there is any benefit left in using it.
Edit: I forgot to mention that there is a dedicated forum for the T-Mobile US M9 here on xda which can be found with the xda search function. You might find the files you need over there. Due to that other forum the T-Mobile US variant of the M9 isn't that much supported here in the forum for the international variant.
Sent from my HTC One S using XDA Labs
Thanks for the info on the T mobile forum. I wasn't aware of that and thought this was the only forum for the M9 here. I'll look for it.
I've already tried using the SD card method and that also failed.
I haven't changed the CID. It was the superCID when I got it. I don't think the previous owner changed it either because the phone seems unused. It still has the barcode sticker on the back and it's clearly be barely handled at all. The phone was originally a test unit or something because it has a serial number engraved on the front and it runs some HTC reporting software. It's rooted out of the box. I'm trying to replace the ROM to get rid of that extra software. I just mention that to explain why it's already rooted, s-off and superCID.
drfarmkid said:
Thanks for the info on the T mobile forum. I wasn't aware of that and thought this was the only forum for the M9 here. I'll look for it.
I've already tried using the SD card method and that also failed.
I haven't changed the CID. It was the superCID when I got it. I don't think the previous owner changed it either because the phone seems unused. It still has the barcode sticker on the back and it's clearly be barely handled at all. The phone was originally a test unit or something because it has a serial number engraved on the front and it runs some HTC reporting software. It's rooted out of the box. I'm trying to replace the ROM to get rid of that extra software. I just mention that to explain why it's already rooted, s-off and superCID.
Click to expand...
Click to collapse
I would say the phone is modified. As far as I know, test units don't need S-OFF or the SCID since they simply use different firmware versions than normal units. You can change every version of the M9 into a test unit by applying for HTCs beta program.
What was the error that got shown when the SD card method failed? Did you try to flash the correct RUU.zip for your phone? As mentioned before your MID needs to match even if the phone has the SCID. Therefore, you can only use x.xx.531.x RUUs.
Edit: I forgot to mention that every S-OFFed device runs that reporting software you mentioned if that device is running the stock rom. That Software gets triggered by the S-OFF flag.
Sent from my HTC One S using XDA Labs
Well, I managed to find the 1.32.531.33 RUU in the forum for the T-mobile variant (thanks flippy498 for bringing it to my attention) and that ran just fine. Once that was done I tried running the RUU I downloaded earlier from HTC (3.39.531.31) and it worked fine. It seems the problem was indeed that I just needed something that was a smaller jump. I've seen no mention of any software version earlier than 1.32 anywhere in this forum, so I wonder if my phone was an early test unit or something that the version 1.14 mine had was an earlier pre-release version or something and that is why I had the problems I did.
Thanks for the info regarding the reporting software running on all s-off phones. I saw something about red text in other threads and wondered if that's what it referred to. Now I know.
Hi there,
I'll start with the essentials
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.20.502.5
(bootloader) version-misc: UNKNOWN SHIP S-OFF
(bootloader) serialno: xxxxxxxxx
(bootloader) imei: 35xxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000d f/e/lc/mbkp s1se=68
x
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
So my phone is originally a Rogers from Canada and I am using it in India. This device does not pick up LTE bands in India and my assumption was that it was because of Rogers somehow restricting the phone as HTC m8 does in fact support the bands present in India (3,5,40). I assumed that if I flashed a different region RUU where those bands are supported then it would solve my problem. I had been running Lineage OS on it and over the weekend I get S-off, SuperCID. Then I went back to Rogers Stock through this thread https://forum.xda-developers.com/showthread.php?t=2710735
From there I went to AT&T latest RUU as mentioned in this thread https://forum.xda-developers.com/ht...ance-jio-volte-m8-t3566379/page9#post75932527
For this I needed to change my MID to 0P6B12000
On it, I flashed the RR 6.0
Now I hoped it would solve my problem but this has presumably locked my network to AT&T as no other carrier or network is getting recognized. I understand how I can revert to a different stock ROM, but doing that has still not helped the 4G problem. Would be great if someone could guide me on this. Have tried reading as many guides and how to but now I feel utterly confused.
[EDIT] - Have I bricked my Radio? Is there a sure way of finding that out?
Thanks in advance.
abhijin said:
This device does not pick up LTE bands in India and my assumption was that it was because of Rogers somehow restricting the phone as HTC m8 does in fact support the bands present in India (3,5,40). I assumed that if I flashed a different region RUU where those bands are supported then it would solve my problem.
Click to expand...
Click to collapse
We've seen a lot of folks on this forum, with a lot of trouble getting LTE working on devices not specifically intended for their region/carrier.
First of all, while the Snapdragon 801 chipset is capable of support most GSM, 3G, and LTE bands worldwide; the specific bands supported by the M8 model is determined by the radio baseband firmware.
For instance, in you case, I believe the Rogers version has the same band support as the AT&T version (due to the history of the countries and companies). In that case, the Rogers version only supports LTE bands 2,4,5,7, and 17. Of the LTE bands you desire, it only includes LTE band 5.
Additionally (as mentioned), we've seen many cases, where even on the proper firmware, folks have had trouble getting LTE on their local carrier (as mentioned, on devices not specifically intended for their region, but "converted" with RUU).
abhijin said:
Now I hoped it would solve my problem but this has presumably locked my network to AT&T as no other carrier or network is getting recognized.
Click to expand...
Click to collapse
Are you saying, after flashing the AT&T RUU, that no network is recognized at all, even voice service?
Flashing AT&T RUU does not carrier lock the phone (SIM lock). But lack of service, even voice service; may indeed indicate an issue with the radio baseband firmware.
abhijin said:
For this I needed to change my MID to 0P6B12000
(bootloader) modelid: 0P6B12000d f/e/lc/mbkp s1se=68
x
Click to expand...
Click to collapse
Your MID shouldn't look like that. Something went wrong when you tried to change it. Try the command again, to change it properly to AT&T MID, and let's see what the result is.
redpoint73 said:
We've seen a lot of folks on this forum, with a lot of trouble getting LTE working on devices not specifically intended for their region/carrier.
First of all, while the Snapdragon 801 chipset is capable of support most GSM, 3G, and LTE bands worldwide; the specific bands supported by the M8 model is determined by the radio baseband firmware.
For instance, in you case, I believe the Rogers version has the same band support as the AT&T version (due to the history of the countries and companies). In that case, the Rogers version only supports LTE bands 2,4,5,7, and 17. Of the LTE bands you desire, it only includes LTE band 5.
Additionally (as mentioned), we've seen many cases, where even on the proper firmware, folks have had trouble getting LTE on their local carrier (as mentioned, on devices not specifically intended for their region, but "converted" with RUU).
Click to expand...
Click to collapse
Yes I have come across this often in the forums. Still thought it is worth a shot.
redpoint73 said:
Are you saying, after flashing the AT&T RUU, that no network is recognized at all, even voice service?
Flashing AT&T RUU does not carrier lock the phone (SIM lock). But lack of service, even voice service; may indeed indicate an issue with the radio baseband firmware.
Click to expand...
Click to collapse
Yes, this is when the no network problem started. I tracked the radio baseband firmware (from this thread https://forum.xda-developers.com/showthread.php?p=52770589#post52770589) and flashed that too but with no luck. In fact the phone now has become extremely volatile, it reboots often, crashes often. Sometimes just tapping the home button will push it to reboot.
redpoint73 said:
Your MID shouldn't look like that. Something went wrong when you tried to change it. Try the command again, to change it properly to AT&T MID, and let's see what the result is.
Click to expand...
Click to collapse
Had the same feeling. Had tried it right then but it still gave the same result. I think I might try changing it to something else. This happened just before flashing the AT&T RUU, wonder if this is the cause of all problems. Shall get back after trying tonight. Do let me know if you have any other suggestions. Thanks!
abhijin said:
Yes, this is when the no network problem started. I tracked the radio baseband firmware (from this thread https://forum.xda-developers.com/showthread.php?p=52770589#post52770589) and flashed that too but with no luck. In fact the phone now has become extremely volatile, it reboots often, crashes often. Sometimes just tapping the home button will push it to reboot.
Click to expand...
Click to collapse
None of the radios in the post you linked, correspond to the current firmware number (6.20.502.5). And al the radios on that post are rather old. Newest is Lollipop, with most others being even older.
I also would recommend against flashing radio baseband, without replacing the whole firmware and ROM as well. The crashes and reboots are probably due to incompatibility between the radio and the firmware and/or ROM.
I would suggest to flash the firmware 6.20.502.5 from the following thread. I always user fastboot (RUU mode) Method 32 personally. Be sure to flash it twice:
https://forum.xda-developers.com/htc-one-m8/development/progress-fuu-m8-t2813792
Then see if you have any change.
abhijin said:
Had the same feeling. Had tried it right then but it still gave the same result. I think I might try changing it to something else. This happened just before flashing the AT&T RUU, wonder if this is the cause of all problems.
Click to expand...
Click to collapse
That is what I would try: try to change to another MID (a known one, such as Euro), than back to AT&T.
It's possible the "no network" problem may be linked to the MID being screwed up. I can't say for sure. But I know SuperCID enables SIM unlock. So maybe it's possible that a broken MID will break some other things (like the network).
redpoint73 said:
None of the radios in the post you linked, correspond to the current firmware number (6.20.502.5). And al the radios on that post are rather old. Newest is Lollipop, with most others being even older.
I also would recommend against flashing radio baseband, without replacing the whole firmware and ROM as well. The crashes and reboots are probably due to incompatibility between the radio and the firmware and/or ROM.
I would suggest to flash the firmware 6.20.502.5 from the following thread. I always user fastboot (RUU mode) Method 32 personally. Be sure to flash it twice:
https://forum.xda-developers.com/htc-one-m8/development/progress-fuu-m8-t2813792
Then see if you have any change.
That is what I would try: try to change to another MID (a known one, such as Euro), than back to AT&T.
It's possible the "no network" problem may be linked to the MID being screwed up. I can't say for sure. But I know SuperCID enables SIM unlock. So maybe it's possible that a broken MID will break some other things (like the network).
Click to expand...
Click to collapse
Hey I tried to to flash through fastboot RUU but at the htc_fastboot oem rebootRUU command it gives me an error saying dns server not authoritative for zone
No clue how to proceed further into this.
Should I just try to get a stock nanodroid backup and restore that?
abhijin said:
Hey I tried to to flash through fastboot RUU but at the htc_fastboot oem rebootRUU command it gives me an error saying dns server not authoritative for zone
No clue how to proceed further into this.
Should I just try to get a stock nanodroid backup and restore that?
Click to expand...
Click to collapse
Hey I was successful in flashing the AT&T by the RUU method by using fastboot commands instead of htc_fastboot but for some reason I got stuck in bootloops post that and it kept booting to recovery.
redpoint73 said:
None of the radios in the post you linked, correspond to the current firmware number (6.20.502.5). And al the radios on that post are rather old. Newest is Lollipop, with most others being even older.
I also would recommend against flashing radio baseband, without replacing the whole firmware and ROM as well. The crashes and reboots are probably due to incompatibility between the radio and the firmware and/or ROM.
I would suggest to flash the firmware 6.20.502.5 from the following thread. I always user fastboot (RUU mode) Method 32 personally. Be sure to flash it twice:
https://forum.xda-developers.com/htc-one-m8/development/progress-fuu-m8-t2813792
Then see if you have any change.
.
Click to expand...
Click to collapse
Hey, so it finally came through. Now I am on the Dev Edition and running RR 6 on it but for some reason no sim card is being recognized. Has the worst happened then? Does this mean that I have bricked the radio and there would be no way to change it?
abhijin said:
Hey, so it finally came through. Now I am on the Dev Edition and running RR 6 on it but for some reason no sim card is being recognized. Has the worst happened then? Does this mean that I have bricked the radio and there would be no way to change it?
Click to expand...
Click to collapse
Can't say, with info (or lack of info) given by you. I never said to flash Dev Edition, so I don't really understand what you did, or trying to do (I see from above you had trouble with the AT&T RUU, but that still doesn't tell the whole story). I can't tell whether you flashed the Dev Edition firmware, or RUU or both.
I also advised to try to fix the MID, but you don't mention if you tried, or were successful or not.
I also don't understand why you are running RR6. Did the SIM work after flashing Dev Edition (before flashing RR6). I don't recommend messing with custom ROMs until you get the radio/SIM worked out, as custom ROMs add another layer of complexity and possible bugs.
redpoint73 said:
Can't say, with info (or lack of info) given by you. I never said to flash Dev Edition, so I don't really understand what you did, or trying to do (I see from above you had trouble with the AT&T RUU, but that still doesn't tell the whole story). I can't tell whether you flashed the Dev Edition firmware, or RUU or both.
Click to expand...
Click to collapse
I flashed both. Also returned back to stock.
redpoint73 said:
I also advised to try to fix the MID, but you don't mention if you tried, or were successful or not.
Click to expand...
Click to collapse
I did try but nothing has changed. The initial parts change i.e. 0P6B12000d will change but the latter f/e/lc/mbkp s1se=68 doesn't change at all.
redpoint73 said:
I also don't understand why you are running RR6. Did the SIM work after flashing Dev Edition (before flashing RR6). I don't recommend messing with custom ROMs until you get the radio/SIM worked out, as custom ROMs add another layer of complexity and possible bugs.
Click to expand...
Click to collapse
Honestly, I'm just trying a few different things just to see if something will work out
abhijin said:
I flashed both. Also returned back to stock.
Click to expand...
Click to collapse
Stock what? Firmware? RUU? Stock for your device would be Rogers.
When you returned to "stock" (whatever that means) did the SIM still not work?
After flashing the Dev Edition firmware and RUU, did the SIM work or not?
Really, I'm just asking the same kinds of questions over and over. But you fail to properly answer them.
Hi folks, I've read the Flippy498's M9 ReadMe thread and understand most of it but still need a helping hand from you more experienced folk in order to update the software on the M9.
I bought a "like new" M9 a few months ago from a seller somewhere in Asia (Hong Kong I think). I know, bad idea, but I had a tight budget. The phone has lollipop - I've been happily using it in the UK but now a few apps I need won't install (apps to access work email etc. since lollipop isn't supported by these apps).
I know the phone has been tinkered with (S-OFF and supercid) - but I'm not sure why (to unlock?). I get an OTA update notification, but it won't apply (see screenshot). I've included a couple more informational screenshots below.
Bootloader locked, S-OFF
0PJA100 (this is written on the back of the phone as well - no reason to believe it's a frankenphone)
htc_himulatt PVT S-OFF
CID-11111111
LK-1.0.0.0000
RADIO-01.01_XXX
OpenDSP-XXX
OS-2.11.617.258
My situation might be similar to these folks, neither of who had any luck:
https://forum.xda-developers.com/one-m9/help/unlock-bootloader-android-6-0-software-t3741019
https://androidforums.com/threads/phone-wont-update.1157270/
I don't want root (banking apps fail). I might be wrong, but I think my work apps won't function with TWRP - rather not chance it.
I'd like to update the phone's software as simply as possible. (Note that the Ebay listing said that they recommend I do not update - not sure why)
Questions:
I'm aware that the CID is incorrect. If I change it to something else (what?) - will the update work? If so this seems to be the simplest method.
Is this a CDMA phone?
Is it possible that the phone becomes locked after updating? Right now I can use it in the UK and 4G works.
Would you recommend some other method? Like changing the CID and flashing an RUU (which one will work? I'm aware that version numbers need to match.)
The phone seems to default to Canadian English - not a big deal - would I be better converting it to another edition?
Thank you very much for any help/advice you can offer. I've rooted, installed custom recoveries and flashed loads of ROMS (on an S3 - nothing as complicated as the M9). If any further information is required I will provide this ASAP.
You didn't buy a CDMA device and your issue isn't similar to the ones you linked.
At the moment, there are two problems that are preventing your phone from being able to install OTAs:
You're using the SCID (11111111). Unlike on previous HTC models, OTAs will abort when they notice this CID.
Your current firmware doesn't match the system version you're using. The firmware that is shown in download mode belongs to the developer edition (SKU 617). The OTA on the other hand belongs to the Canadian Telus version (SKU 661). OTAs will abort if they notice such a mismatch as seen on the pic that shows your phone's stock recovery.
In addition to that, the firmware with SKU 617 actually belongs to the 0PJA11000 (hima_ulatt - a US model) while you own the 0PJA10000 (hima_uhl - the International model) according to the engraving on its backside. Since both are GSM versions and the differences are almost non-existent, cross-flashing is absolutely no problem, though.
I'd recommend you to follow the conversion guide that can be found in the ReadMe thread. Use one of the European RUUs that share the same decryption keys as your current firmware. (In other words a 2.x or a 3.x RUU for SKU 401.) Due to problem 2 you won't be able to solve your issue just by changing the CID. You'll need to flash a RUU for fixing that.
Since SKU 401 belongs to the unbranded European firmware you don't have to fear a sim lock or something similar.
Flippy498 said:
You didn't buy a CDMA device and your issue isn't similar to the ones you linked.
At the moment, there are two problems that are preventing your phone from being able to install OTAs:
You're using the SCID (11111111). Unlike on previous HTC models, OTAs will abort when they notice this CID.
Your current firmware doesn't match the system version you're using. The firmware that is shown in download mode belongs to the developer edition (SKU 617). The OTA on the other hand belongs to the Canadian Telus version (SKU 661). OTAs will abort if they notice such a mismatch as seen on the pic that shows your phone's stock recovery.
In addition to that, the firmware with SKU 617 actually belongs to the 0PJA11000 (hima_ulatt - a US model) while you own the 0PJA10000 (hima_uhl - the International model) according to the engraving on its backside. Since both are GSM versions and the differences are almost non-existent, cross-flashing is absolutely no problem, though.
I'd recommend you to follow the conversion guide that can be found in the ReadMe thread. Use one of the European RUUs that share the same decryption keys as your current firmware. (In other words a 2.x or a 3.x RUU for SKU 401.) Due to problem 2 you won't be able to solve your issue just by changing the CID. You'll need to flash a RUU for fixing that.
Since SKU 401 belongs to the unbranded European firmware you don't have to fear a sim lock or something similar.
Click to expand...
Click to collapse
Thank you Flippy498 - that's just the type of clarification I was looking for! I'll follow your instructions and let you know how I get on. (It might be a few days before I get the block of time I need to do this properly, but I will certainly feed back.) Thanks again.
Hi Flippy498 - just thought I'd check in and let you know how I got on. I followed your instructions exactly and everything is sorted now - I have a fully updated stock M9.
In the unlikely event anyone else finds themselves in this particular situation, and for reference - here are the steps I followed:
Installed a fully functional adb/fastboot environment as per the ReadMe section "Setting up ADB/Fastboot/HTC_Fastboot correctly".
Changed the CID and MID (as outlined here "How to convert your M9 to a different version": https://forum.xda-developers.com/showthread.php?p=71421945#post71421945). For reference the CID I used was HTC__001, the MID was 0PJA10000.
Used the 2.10.401.1 RUU (https://www.androidfilehost.com/?fid=24269982087011324)
Used the SD card method outlined in the ReadMe section titled "RUU Section"
Flash went perfectly. OTA updates all came through as expected. Job done!
Thank you very much Flippy498 - your explanation was crucial to allaying my fears of bricking the device, and giving me the confidence to go through with it. :good:
r2mahara said:
Hi Flippy498 - just thought I'd check in and let you know how I got on. I followed your instructions exactly and everything is sorted now - I have a fully updated stock M9.
In the unlikely event anyone else finds themselves in this particular situation, and for reference - here are the steps I followed:
Installed a fully functional adb/fastboot environment as per the ReadMe section "Setting up ADB/Fastboot/HTC_Fastboot correctly".
Changed the CID and MID (as outlined here "How to convert your M9 to a different version": https://forum.xda-developers.com/showthread.php?p=71421945#post71421945). For reference the CID I used was HTC__001, the MID was 0PJA10000.
Used the 2.10.401.1 RUU (https://www.androidfilehost.com/?fid=24269982087011324)
Used the SD card method outlined in the ReadMe section titled "RUU Section"
Flash went perfectly. OTA updates all came through as expected. Job done!
Thank you very much Flippy498 - your explanation was crucial to allaying my fears of bricking the device, and giving me the confidence to go through with it. :good:
Click to expand...
Click to collapse
This description was very uselfull to me, this summer (July 2021) I purchased 2 brand new HTC One M9 in Sealed packages from a Danish auction house, they was both european phones, but both of them had the folloving configuration:
Locked bootloader
S-ON
Developer version 3.35.617.12
Supercid 11111111
MID 0PJA11000
I need firmware 4.x in order to use the latest Android 11 version of one of the following: crDroid, LineageOS or Ice Cold Project.
I could have lived with the developer version but the super CID 11111111 prevented me from getting to version 4.x
I did the following.
1) For the first phone I registered with HTC developer site in order to get the code to unlock the phone, later on I learned the Sunshine app also unlock the phone, much easier Also I did not need to root the phone because Sunshine App did that temporary, for 25$ this app did some very dificult stuff for me in an rather easy way.
2) From the RUU section I downloaded and flashed 3.35.617.31 on the first phone (still with S-ON) using the SD card method, because there was an OTA file that could bring me to 4.14.617.6, but the update complained about the Super CID 11111111, there was no way around it, I had to use Sunshine app.
3) The first phone I S-OFF'ed with Sunshine locked at the white HTC boot screen, I was unable to power it down, I reached out to support and they adviced med to power the device down by pressing all 3 keys VOL Up/Down and power for 60 seconds and then uninstall Sunshine app, reboot the phone and install it again, then everything went as expected.
4) Now I wanted to get to a 3.x version that will allow me to change to 4.x via OTA file
4a) for both phones I used the SD Card method
4b) for the first phone I had already flashed 3.35.617.31, now I changed the CID to BS_US001
4c) the other phone I changed to H3G__G04, MID to 0PJA10000, and flashed 3.35.771.12
5) Now I was reddy to get to 4.x version
5a) For the phone with version 3.35.617.31 I loaded the OTA file from SD Card to 4.14.617.6, after that I changed the MID to 0PJA10000 and the CID to HTC__001 and flashed a european RUU 4.28.401.3
5b) For the phone with version 3.35.771.12 I loaded the OTA file from SD Card to version 4.30.771.2
5c) For both OTA files I experienced that the script stopped at the last line before completion, I had to power off and run the OTA file once more, where both cases completed as expected.
6) now I have two phones that are ready to go to Android 11, I expect that I wil leave the one with version 4.30.771.12 with the original latest HTC version and keep it as a spare phone, the other one I will use to load Android 11 and Gapps
I hope the can be usefull to someone else in a similar situation.
hello guy's, i'm a real noob with htc or "rooting" etc and i'm facing a problem. I just bought a htc one m9 with android 6. I think its refurbished because it look like new but the left speaker is louder than the right, and are not loud at all. So I thought I would update it for maybe solve the problem, but I have the update notification and when i click on it, it say the sytem is not stock so can't update. The phone isn't root so i don't know why i'm facing this, so after a long research i did many things like try to install RUU..exe or with RUU;zip and no one want to install. At one moment i change the CID and the OTA begin the update by itself (don't show the "not stock system" message anymore" but stop at 25% and reboot. I'm really confused and don't understand anythings, last thing i did is unlock the bootloader but doesn't change anythings. Is it possible to reinstall a pure stock version ? and after update it ? I am not interested by rooting the phone, i just want pure stock version and be able to update the phone, is it possible to get help? Thanks !
What's the current CID of the phone? Which firmware version is currently installed? Which model name is engraved on the backside of the phone? Is the phone S-ON or S-OFF?
Please read the ReadMe thread in the general section if you don't know how to answer any of the questions.
Flippy498 said:
What's the current CID of the phone? Which firmware version is currently installed? Which model name is engraved on the backside of the phone? Is the phone S-ON or S-OFF?
Please read the ReadMe thread in the general section if you don't know how to answer any of the questions.
Click to expand...
Click to collapse
current cid : htc 001 (don't remember what it was before i change it, something like 1111111)
firmware : 3.35.401.12
model : nothing on the backside (just htc) but on download mode i see "product: htc_himauhl"
S-OFF
Ok. The SuperCID (11111111) was the culprit of your initial problem. On older HTC phones it was a way to unlock kind of a region free mode. On the M9 however, that CID prevents official updates from being installed.
Is your current CID really htc 001? Or is it HTC__001? Only the latter one is written in the legit format. The former one won't work.
HTC__001 is one of the CIDs that would match your current SKU (401).
The model name in download mode can be changed via RUUs. As long as no one changed the backplate, only the engraving on the backside of the phone shows the true model name. The engraving is quite small on the downer part of the backplate. Can you please take another look and see if you can find it? The ReadMe contains some commonly asked questions. There should be one that covers the engraving.
We should only proceed with flashing RUUs if we know the model name of your phone. It's not wise to flash GSM RUUs on a CDMA phone or vice versa.
Flippy498 said:
Ok. The SuperCID (11111111) was the culprit of your initial problem. On older HTC phones it was a way to unlock kind of a region free mode. On the M9 however, that CID prevents official updates from being installed.
Is your current CID really htc 001? Or is it HTC__001? Only the latter one is written in the legit format. The former one won't work.
HTC__001 is one of the CIDs that would match your current SKU (401).
The model name in download mode can be changed via RUUs. As long as no one changed the backplate, only the engraving on the backside of the phone shows the true model name. The engraving is quite small on the downer part of the backplate. Can you please take another look and see if you can find it? The ReadMe contains some commonly asked questions. There should be one that covers the engraving.
We should only proceed with flashing RUUs if we know the model name of your phone. It's not wise to flash GSM RUUs on a CDMA phone or vice versa.
Click to expand...
Click to collapse
real cid is : HTC__001 (from getvar all)
I search everywhere with camera and there is nothing about the model, the person I bought it from told me it was refurbished, maybe thats a false case ? am I stuck ?
It's up to you to decide whether you want to try flashing the 3.35.401.12 RUU or not. All clues imply that you have a 0PJA10000. However, we don't know for sure.
In case you want to proceed: Check the MD5 sum of the file that you can find in the ReadMe thread. Flash it with the instructions for the SD card method.
Afterwards the phone should be working normally, again. Unless it's not a CDMA variant. In the latter case you would at least get problems with network reception.
Edit with another thougt that comes to my mind: What's the fastboot getvar result for your MID. Since the refurbisher used the SCID they most likely didn't know that the M9 behaves differently than older HTC phones and probably didn't change the original MID.
the getvar mid is : 0PJA10000 but i change it too and don't know the initial.
I will try the process, i don't understand what you mean by "check the MD5"
is this file is good ? : https://androidfilehost.com/?fid=23991606952597788
Is it possible to flash it with the pc instead of sd card ? if it's mandatory the sd card I will buy one
Well, if you manually changed the MID, didn't write down the original MID and there's no engraving on the backside of the phone then there's no way to know for sure which variant you own.
C.f. https://en.m.wikipedia.org/wiki/MD5
Tl;dr: Check whether the file didn't get broken during download (e.g. due to connectivity issues). The ReadMe thread suggests useful programs for that purpose.
Flashing broken files might lead to unrecoverable bricks; especially on S-OFF phones. "Good" file hosts like AndroidFileHost will always mention the reference MD5 value for their downloads.
The SD card method is the most fail safe method for flashing RUUs on a M9. That's why I recommend to use it, always. You'll want to get a card that has not more than 32 gb due to the needed format. Those cards should cost less than 10 €.
Edit: You can't use the RUU that you linked. Please read the ReadMe thread, thoroughly. That RUU uses a different encryption key. Everything you need can be found in the ReadMe thread. Trying to flash just any random RUU is quite dangerous on a S-OFF device due to the security checks being turned off. You might risk a brick.