S-OFF, Bootloader locked - need help to get OTA updates - One (M9) Q&A, Help & Troubleshooting

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.

Related

can't flash ROM or update

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.

HTC One M9 stuck in Flight Mode after Nougat OTA

Hey there,
I own a HTC One M9 with Stock ROM, not rooted, nothing modified. Recently I got the Nougat OTA update as a notification (don't know why not earlier...).
It did update without any problems, but after it, it occured to me that it didn't get any signal. WiFi, bluetooth and everything else works fine, it even recognizes my SIM card.
In the settings, the "flight mode" is grey and permanently "setting off" and I can't set it on or off.
(But strangely, if I hold the power button, it says "airplane mode off", same within the status bar/quick settings.)
I don't know much about flashing etc (nearliy nothing), but I read as most threads which seemed to be similar as I could. Even if some people had the problem with the One X and M8, I couldn't find a solution for me...
I rebootet the phone several times, did the "battery pull out simulation" with power and volume keys, did a factory reset in the settings, wiped cache partition within the recovery mode. Even tried booting in safe mode and a factory reset within the recovery mode.
Nothing works, the airplane mode is still stuck at "setting off" and I don't get any cell phone signal or mobile internet.
Phone /software information:
- Model: HTC One M9; OPJA100
- Not rooted
- "LOCKED"
- htc_hiauhl PVT S-ON
- Software status: Official
- Android-Version: 7.0
- Software-Version: 4.18.111.2
- OpenDSP-20.7.3.00545.8994_1012
- Kernel-Version: 3.10.84-perf-ga97f624
[email protected] #1
SP PREEMPT
- Android safety-patch: 01. Nov. 2016
-Baseband-Version: 01.01_U114401011_117.00.61117G_2_F
- Build-Nr.: 4.18.111.2 CL839204 release-keys
I hope, that it will be fixed, if I flash the Stock ROM myself, but I didn't find one with the same software-version and do not know how to do this.
Any suggestions, what could be wrong and how I manage to fix it?
Thank you all for your help!
Flashing instrtructions can be found in the ReadMe thread. The catch is that no one contributed a RUU or a TWRP backup for your current firmware version, yet.
Therefore, I only see the following solutions at the moment (which all aren't available for free - sorry):
Getting S-OFF and flashing the 3.x RUU for your SKU. (Infos are located in the ReadMe thread.)
Contacting Llabtoofer's RUU service. (A link can be found in the further reading section of the ReadMe thread.)
Searching on sites like ir-file or easy-firmware for the needed RUU. (If you choose this option you'll need your phone's codename which is HIMA_UHL.)
I was able to unlock the Bootloader, flashed TWRP, got S-OFF (didn't get Root, but I don't know why...tried several SuperSU versions...) and changed the CID to be able to flash RUUs without the T-Mobile branding.
But I'm not sure which RUU I can use for flashing with a SD card.
Those I found were only 3.xx with SKU "111", but the actual version is 4.xx.
I thought with S-OFF I would be able to flash early every RUU?
Can someone explain this to me and give me an advice which RUU (preferably a non-branded Nougat one) I can flash and where to get it?
Thank you all in advance for you help!
As written in my last post, no one contributed 4.x files for your SKU, yet.
All needed information and files should be available in the ReadMe thread. There's a conversion guide, the RUU section contains all infos you might need in regard to RUUs and the further reading section contains a link to a spreadsheet with with all SKUs and their meanings.
Sent from my HTC One M9 using XDA Labs
Thanks again!
I did read those threads, but got a bit confused afterwards... :/
E .g. easy-firmware has a RUU 4.xxx with SKU "111", and as I understood, I can also use free 4.xxx RUUs with SKU "401", because I got S-OFF and changed the CID?
Sorry to bother
That's correct. You can use 401 RUUs thanks to S-OFF, now.
The catch with ir-file and easy-firmware is that their files aren't available for free. Most RUUs in the ReadMe thread got bought on one of those sites in the past.
Since you already paid for S-OFF I'd suggest you to not pay once more. Either convert to SKU 401 or use the infos in the RUU section of the ReadMe thread for flashing the 3.x RUU for your current SKU.
Sent from my HTC One M9 using XDA Labs
Now I got it, thank you!
I tried flashing it with a RUU_4.28.401.3 (worked on the second try, first one didn't find the file).
Flashing worked without problems (checked the phone info), but it's still stuck in the flight mode.
No changes there... :crying:
Is there a chance, that it's still a software issue, maybe with Nougat itself?
Or do I have to "bury" it, because sending to be repaired isn't worth it's value?
If it was a general Nougat problem on the M9 then there would be more threads like this one... Sorry, that I can't provide better news.
Sent from my HTC One M9 using XDA Labs

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

Hello,
I have bought HTC One M9 off Aliexpress.
I bought it as developer version. When it came I started OTA upgrade. It downloads and then it says update cannot be performed because of modified system.
I cant even use RUU to get it working, I receive error 132. While chatting to HTC support their run my IMEI by their system. It came back as T-Mobile (US) version. Even though on back of my phone is engraved -
Model: OPJA110 which should mean it is developer version.
On my download mode it states: S-on, official system and locked bootloader.
Can anyone give me some tips how to get the newest system installed?
I have been trying for past 2 days without any luck to figure it out.
Any help is appreciate.
EDIT: Forgot CID:11111111 MID: 0PJA11000
Thank you very much.
Please read the ReadMe thread. It'll explain the causes of your issues and contains the needed files and instructions for fixing it. (C.f. the conversion guide, the RUU and the OTA section)
The most important infos: OTAs aren't installable while the phone is using the SuperCID and firmware 4.x RUUs aren't flashable on phones with firmware 3.x or lower due to new encryption keys.
Sent from my HTC One M9 using XDA Labs
Thanks for your time.
Flippy498 said:
Please read the ReadMe thread. It'll explain the causes of your issues and contains the needed files and instructions for fixing it. (C.f. the conversion guide, the RUU and the OTA section)
The most important infos: OTAs aren't installable while the phone is using the SuperCID and firmware 4.x RUUs aren't flashable on phones with firmware 3.x or lower due to new encryption keys.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
I have read ReadMe.
So that means I need to S-OFF my phone using SunShine (other oprions?)
Then changing CID to BS_US001 (because Im running .617. system)
Then I can flash RUU (3.35.617.31)
And after that I can use OTA updates?
Do I need to unlock bootloader through HTCdev or is enough to check OEM Unlocking under developer options?
Thank you again for your time.
Oh, I missed that you're S-ON. Follow the unlocking/rooting guide in the same thread.
If you're lucky the previous owner used Sunshine, as well, so that you don't have to pay, again. (The license is saved on their servers and gets linked to the device.) The alternatives to Sunshine are a Java card, an XTC clip or similar tools which are way more expensive.
It doesn't matter which of the CIDs that belong to SKU 617 you use. They both work fine.
Alternatively, you could send the device back to the seller and ask for a refund. He obviously modified the phone and didn't restore the phone to a stock state properly before he sold it. The phone definetly was S-OFF in the past since no HTC phone gets shipped with the SuperCID. And if the IMEI belongs to a T-Mobile M9 according to HTC then the MID got changed with the help of S-OFF, as well. The backside can actually get replaced, too, if you know how to do it.
After you restored a CID that corresponds to your SKU you should be able to receive OTAs, again. Just for safety reasons I'd flash a 3.x RUU, as well, if I were you. The differences between the GSM versions of the M9 are so minor that you can convert the phone from one version to another. Therefore, you don't need to use the T-Mobile firmware and can stick with the dev one if you want.
Flippy498 said:
Oh, I missed that you're S-ON. Follow the unlocking/rooting guide in the same thread.
If you're lucky the previous owner used Sunshine, as well, so that you don't have to pay, again. (The license is saved on their servers and gets linked to the device.)
It doesn't matter which of the CIDs that belong to SKU 617 you use. They both work fine.
Alternatively, you could send the device back to the seller and ask for a refund. He obviously modified the phone and didn't restore the phone to a stock state properly before he sold it. The phone definetly was S-OFF in the past since no HTC phone gets shipped with the SuperCID. And if the IMEI belongs to a T-Mobile M9 according to HTC then the MID got changed with the help of S-OFF, as well. The backside can actually get replaced, too, if you know how to do it.
After you restored a CID that corresponds to your SKU you should be able to receive OTAs, again. Just for safety reasons I'd flash a 3.x RUU, as well, if I were you. The differences between the GSM versions of the M9 are so minor that you can convert the phone from one version to another. Therefore, you don't need to use the T-Mobile firmware and can stick with the dev one if you want.
Click to expand...
Click to collapse
Ok, Im gona pay that 25 bucks, it doesnt really matter.
So, I should start with unlocking bootloader via HTCdev.
After that I need to use SunShine.
Changing CID.
Flashing 3.x RUU.
And then doing OTA.
Is that all correct?
And should I install TWRP or stay on stock recovery after unlocking bootloader?
Really appreciate your time.
Correct.
Just follow the guides in the ReadMe thread starting from this post till the end of the conversion guide. (Theoretically, you can skip the backup part and save some time since you should be able to use the 3.x RUU even with the SuperCID on your phone.)
Flippy498 said:
Correct.
Just follow the guides in the ReadMe thread starting from this post till the end of the conversion guide. (Theoretically, you can skip the backup part and save some time since you should be able to use the 3.x RUU even with the SuperCID on your phone.)
Click to expand...
Click to collapse
Thanks,
is there a point in TWRP backup? Wont it stop OTA updates? On my other phone (Ulefone Metal) It is not possible to get OTA with custom recovery.
It actually is possible on the M9 and newer HTC phones as long as the system partition doesn't get modified, beforehand. (Further info can be found in the OTA section of the ReadMe thread.)
However, flashing a RUU restores everything on the phone back to stock (including the recovery). That's why I suggested flashing one after changing the CID.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
It actually is possible on the M9 and newer HTC phones as long as the system partition doesn't get modified, beforehand. (Further info can be found in the OTA section of the ReadMe thread.)
However, flashing a RUU restores everything on the phone back to stock (including the recovery). That's why I suggested flashing one after changing the CID.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Thank you, I did as I said.
After flashing 3.x RUU OTA was successful.
That updated my system to: 4.16.617.6.
After that I continued by flashing latest RUU (4.30.617.12).
Everything went well. Until this point. When I booted the device I got to choose language. But there are just few (20 or so) available.
Unfortunately no Czech which I want. On previous version (4.16.617.6) there was huge list to choose from, including Czech.
Im still using 617 edition.
Where is the problem? Is here a way to get Czech lang. working again?
One again thank you for your time and effort
HTC probably removed the languages from the selection. Don't ask me why. I have no clue.
You could try setting up the phone in English and then switching to Czech via the app MoreLocal2. There's a thread about the app somewhere hidden on xda (sorry, I don't have a direct link at hand). You should be able to find it via google.
Sent from my HTC One M9 using XDA Labs

Help to return to stock RUU

Hi,
I'm totally new to this and I'm looking for help.
I have a HTC One (M9), unlocked. I realised since I got the handset (insurance replacement in 2016) I've never had an OTA update. I contacted HTC support who advised that I am running unofficial software and that is why I cannot get OTA updates. I've asked them to elaborate on what is "unofficial" about it as I have never rooted the handset or messed around in any way. They couldn't elaborate and advised I should send it to them to be flashed (at cost, as it's out of warranty).
Anyway, I want to put my handset into a condition where I can receive OTA updates & also ensure that I benefit from the latest software updates so I started looking into how I could do this. As a noob to Android the easiest method seemed to be via RUU exe. I've downloaded 2 different RUU's from HTC website but both errored with "incorrect version" when I tried to install. I then downloaded a ZIP which I followed the instructions to boot to recovery & install from phone storage, this also errored with "cannot find files".
As above I've tried going from Android v5 to v7 and that failed, I don't know whether I had the wrong RUU or I need to upgrade to v6 first.
I'm in the UK with I presume a UK handset but the RUUs were downloaded from htc.com not htc.com/uk as the UK one doesn't seem to provide this.
So long story short I'm looking for help getting the correct RUU for my handset and I'm having no luck. I'd appreciate any advice given.
HTC One M9
CID: HTC_001 (WWE)
Android: 5.0.2
HTC Sense: 7.0
SW: 1.32.401.17
S-ON
Cheers
Breezo
Firmware 1.32.401.17 only got distributed in one single country (I always forget which one it was - it definitely wasn't the UK). Therefore, the combination of that version together with the HTC__001 CID can only get achieved by tinkering with the phone.
You're actually using an official stock rom but you can't update your phone since the UK never was meant to receive this specific version and/or its OTAs.
You should be able to "return" to 1.32.401.15 without much hassle by following one of the guides in the ReadMe thread. Even with S-ON this little downgrade should be possible (c.f. the RUU section of the ReadMe thread).
If flashing the 1.32.401.15 RUU fails you'll have no choice but unlocking the bootloader, getting root, setting the phone S-OFF and retrying to flash the RUU. All needed steps are explained in the ReadMe thread, as well.
Sent from my HTC One M9 using XDA Labs
Hi Flippy498,
Thanks very much for the response and advise.
I've no idea how it ended up like that. I can only assume as it was an insurance replacement that it was initially branded then flashed incorrectly before it was issued to me.
I'll try your suggestions over the weekend.
Thanks again for the knowledge, its appreciated.
Cheers
Breezo
Hi Flippy498,
That worked perfectly thanks very much for your help. Took the software down from .17 to .15 and OTA updates kicked in immediately.
Now running on Android 7.0
Cheers again
Breezo
Flippy498 said:
Firmware 1.32.401.17 only got distributed in one single country (I always forget which one it was - it definitely wasn't the UK). Therefore, the combination of that version together with the HTC__001 CID can only get achieved by tinkering with the phone.
You're actually using an official stock rom but you can't update your phone since the UK never was meant to receive this specific version and/or its OTAs.
You should be able to "return" to 1.32.401.15 without much hassle by following one of the guides in the ReadMe thread. Even with S-ON this little downgrade should be possible (c.f. the RUU section of the ReadMe thread).
If flashing the 1.32.401.15 RUU fails you'll have no choice but unlocking the bootloader, getting root, setting the phone S-OFF and retrying to flash the RUU. All needed steps are explained in the ReadMe thread, as well.
Click to expand...
Click to collapse
Deffo not a UK phone. We went from 5.0.1 out of the box straight to 6.0.
I'm pretty sure that UK received Android 5.1, as well. No variant of the M9 skipped firmware 2.x.
Firmware 1.x = Android 5.0.2
Firmware 2.x = Android 5.1
Firmware 3.x = Android 6.0
Firmware 4.x = Android 7.0
Since the UK M9 is the "normal" European unbranded version (SKU 401) it received the following versions:
1.32.401.8
1.32.401.15
1.40.401.8
2.10.401.1
2.10.401.180*
3.35.401.12
3.35.401.32
4.14.401.7
4.28.401.3
In addition to that there are:
1.32.401.6 (a pre-release firmware shown on the MWC)
1.32.401.17 (which got distributed in only one country)
* Normally the three numbers behind the last dot indicate a beta firmware. Since the Nougat update couldn't be applied in one single update they had to distribute this version, as well.
Sent from my HTC One M9 using XDA Labs

can't install updates please help

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.

Categories

Resources