I have HTC M9 bootloader unlocked s-off CID 11111111 TWRP 2.8.7.0. I had tried to convert from android 6 to developer RUU with fastboot method found in ATT to developer edition forum that left me with no recovery or os. I was able to put TWRP 2.8 on with fastboot but more recent versions did not hold. I attempted to flash developer RUU (5,5.1,6) with TWRP and get "updating partition details...done,full selinux support is present,mtp enabled" then returns to TWRP main menu, reboot says no OS installed. Attempt with SD card/0pjaimng method with 5.0 RUU and bottom of screen showed file (filename) exit in yellow without ability to access, no other prompts. I am able to change CID (had started with developer Cid). Attempted to fastboot multiple versions of RUU and received file to large and several other messages. I am using a Macbook Pro OS X as computer. This is info displayed from download mode: ***unlocked***,HTC_himaulatt PVT s-off, CID-11111111, LK-1.0.0.0000,RADIO-01.01_U11440801_96.01.51207A_F, OpenDSP-15.6.1.00522.8994_1026, OS-3.38.502.12, Mar 23 2015,23:33:55(506785),
No meid listed on system info if that matters. Any ideas on getting to a working RUU would be appreciated. (I do not have easy access to PC)
THulbert said:
I have HTC M9 bootloader unlocked s-off CID 11111111 TWRP 2.8.7.0. I had tried to convert from android 6 to developer RUU with fastboot method found in ATT to developer edition forum that left me with no recovery or os. I was able to put TWRP 2.8 on with fastboot but more recent versions did not hold. I attempted to flash developer RUU (5,5.1,6) with TWRP and get "updating partition details...done,full selinux support is present,mtp enabled" then returns to TWRP main menu, reboot says no OS installed. Attempt with SD card/0pjaimng method with 5.0 RUU and bottom of screen showed file (filename) exit in yellow without ability to access, no other prompts. I am able to change CID (had started with developer Cid). Attempted to fastboot multiple versions of RUU and received file to large and several other messages. I am using a Macbook Pro OS X as computer. This is info displayed from download mode: ***unlocked***,HTC_himaulatt PVT s-off, CID-11111111, LK-1.0.0.0000,RADIO-01.01_U11440801_96.01.51207A_F, OpenDSP-15.6.1.00522.8994_1026, OS-3.38.502.12, Mar 23 2015,23:33:55(506785),
No meid listed on system info if that matters. Any ideas on getting to a working RUU would be appreciated. (I do not have easy access to PC)
Click to expand...
Click to collapse
Update- have been able to get TWRP 3.0 installed. Have been able to flash both ViperOne 1.9.1 and Android 5.0.2/HTC 7/ 1.32.617.30. Software update shows modified system, unable to update with both CID 11111111 and BS_US001. I am not getting wireless service and my IMEI, IMEI SV are blank, baseband version is unknown. Tried to repair with fastboot OEM writeimei #### but did not work. Still hoping for help. Thank you
What was the real cid and mid of the device ??
THulbert said:
Update- have been able to get TWRP 3.0 installed. Have been able to flash both ViperOne 1.9.1 and Android 5.0.2/HTC 7/ 1.32.617.30. Software update shows modified system, unable to update with both CID 11111111 and BS_US001. I am not getting wireless service and my IMEI, IMEI SV are blank, baseband version is unknown. Tried to repair with fastboot OEM writeimei #### but did not work. Still hoping for help. Thank you
Click to expand...
Click to collapse
I didnt know any M9 models were still using Android 5.x Lollipop. Oofta.
It will be important to know the original information about your phone - CID & MID would be great. Even better would be the original SKU.
For your information, SuperCID (11111111) is no longer useful - official software doesn't accept it and will fail to install on phones with it. Your CID and your MID must match the SKU of update (OTA) or RUU you are attempting to install.
By the way, are you using HTC fastboot or the Android fastboot? I wonder if the blank values you are getting for various fields is because the Android fastboot isn't entirely compatible with the M9. If you download HTC Sync Manager, that will install the HTC ADB tools (including fastboot).
SKU is 6735A. I was following instructions to set developer Cid to us_b001 , it is att brand US. Have not been able to get TWRP higher than 3.0.0 to flash successfuly. Haven't been able to find higher than 5.0 to flash successfully. Am using HTC sync manager adb and fastboot. Also tried using Flashify and TWRP manager apps but experienced errors with both.
THulbert said:
SKU is 6735A. I was following instructions to set developer Cid to us_b001 , it is att brand US. Have not been able to get TWRP higher than 3.0.0 to flash successfuly. Haven't been able to find higher than 5.0 to flash successfully. Am using HTC sync manager adb and fastboot. Also tried using Flashify and TWRP manager apps but experienced errors with both.
Click to expand...
Click to collapse
Your SKU is 6735A? That's nothing I've heard of before for the HTC One M9 - how did you gather this information? Your second sentence suggests that your phone is actually an AT&T branded M9. If that is correct, we can point you to the correct SKU and it's related software.
computerslayer said:
Your SKU is 6735A? That's nothing I've heard of before for the HTC One M9 - how did you gather this information? Your second sentence suggests that your phone is actually an AT&T branded M9. If that is correct, we can point you to the correct SKU and it's related software.
Click to expand...
Click to collapse
It is ATT branded. I had initially rooted it and had been using android 6. I got the SKU # printed on sticker on back of phone under imei and serial numbers. Thank you for helping.
THulbert said:
It is ATT branded. I had initially rooted it and had been using android 6. I got the SKU # printed on sticker on back of phone under imei and serial numbers. Thank you for helping.
Click to expand...
Click to collapse
A stick on the back of the phone under the IMEI & serial numbers? I don't have that on my model, but maybe that's because I bought the developer edition straight from HTC. I wonder if you are reading the SKU for AT&T's store (as in, the barcode they use for their own inventory to scan and sell the device), rather than the SKU of the phone OS. But that's beside the point - if it is indeed AT&T branded (USA), the phone's original SKU was 502. That's good information to know - both if you want to restore your phone to original software and to help you avoid incompatible software.
[EDIT]Sigh. I missed it in your original post, but your SKU is right there in the information you gave from download mode: OS-3.38.502.12. Sorry for the inconvenience.[/EDIT]
If your goal is to convert your phone to the developer edition, you'll need to change the CID and MID to match SKU 617. Follow the instructions in Q9 of the Flippy498's FAQ in the readme thread. Once you've done that, you can install the developer edition RUU.
Related
Hello,
I brought the phone this February and its working fine. It is running on Kitkat-4.4.2. Then when I searched for software update it shows an update available: 1.54.709.12 (233 MB). But when I download it and try to install, it says "We have determined that your phone may be running a modified version of its system software. For your protection, we cannot update your phone. Please revert your phone to the official HTC system software to update your phone. If you did not modify your system software or would like help reverting your system, please contact us via the support section at www . htc . com"
I saw the bootloader and its locked and cheked if its rooted using rootchecker and its not.
I would prefer not to root my mobile.
I want to update to marshmallow and I am unable to do it
Following are some details:
Current SW:
Android Ver# 4.4.2 (Sense 6)
SW no. 1.54.709.4
HTC SDK API level: 6.17
Baseband version: 1.15.2133156.UA14G_20.18n.4096.05L
Build no. 1.54.709.4 CL325784 release-keys
Bootloader:
***Locked***
M8_UL PVT SHIP S-OFF
CID-11111111
HBOOT-3.16.0.0000
RADIO-1.15.2133156.UA14G
OpenDSP-v38.2.2-00542-M8974.0311
OS-1.54.709.4
eMMC-boot 2048MB
Mar 21 2014,23:56:47.3
Please help.......and thank you in advance.
That's usually means the MID is wrong for the software region that you have.
As yours is a S-Off device, I would say it is easy to fix it.
First thing .. we need to know what the MID is. Run this command - fastboot getvar mid
If you need the driver & tools for this - http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4
ckpv5 said:
That's usually means the MID is wrong for the software region that you have.
As yours is a S-Off device, I would say it is easy to fix it.
First thing .. we need to know what the MID is. Run this command - fastboot getvar mid
If you need the driver & tools for this - http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4
Click to expand...
Click to collapse
Thank you very much for such quick reply.
I ran the command and it gave me
mid: 0P6B10000
I am from India and I want to get OTA updates in future.
Your MID is a EU MID
You can change it to India MID if you want to but it's a bit complicated for you I guess as it will involve change of MID, you may need to unlock bootloader & etc but it's not difficult.
Anyway .. for a start, make it totally EU version by flashing a Marshmallow EU RUU .. you don't need to unlock bootloader and you don't need to change MID. You will still can receive OTA if there is one but I think there will be no more OTA updates as M8 is already on its EOL (means no more HTC further support)
What you need to do :
option 1 : http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
option 2 : http://forum.xda-developers.com/showpost.php?p=66271711&postcount=4
either one should be fine for your device.
ckpv5 said:
Your MID is a EU MID
You can change it to India MID if you want to but it's a bit complicated for you I guess as it will involve change of MID, you may need to unlock bootloader & etc but it's not difficult.
Anyway .. for a start, make it totally EU version by flashing a Marshmallow EU RUU .. you don't need to unlock bootloader and you don't need to change MID. You will still can receive OTA if there is one but I think there will be no more OTA updates as M8 is already on its EOL (means no more HTC further support)
What you need to do :
option 1 : http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
option 2 : http://forum.xda-developers.com/showpost.php?p=66271711&postcount=4
either one should be fine for your device.
Click to expand...
Click to collapse
Thanks.....I am downloading the RUU zip and let you know what happens next.
By the way, will I have any issues networks or wifi or any other thing as it EU rom and I am in India
i have a question about updating bootloader 3.16 to 3.19 ? i keep trying to inatall cm13.0-20160408 but it keeps telling my it needs a higher bootloader where to find / install/flash
manasdb said:
By the way, will I have any issues networks or wifi or any other thing as it EU rom and I am in India
Click to expand...
Click to collapse
I don't think there will be issue as we notice most custom ROMs are based on EU ROM and many users from India are using them.
ckpv5 said:
I don't think there will be issue as we notice most custom ROMs are based on EU ROM and many users from India are using them.
Click to expand...
Click to collapse
Thanks.....I followed the procedure and installed it and its working fine.:good:
somungho said:
i have a question about updating bootloader 3.16 to 3.19 ? i keep trying to inatall cm13.0-20160408 but it keeps telling my it needs a higher bootloader where to find / install/flash
Click to expand...
Click to collapse
I'd recommend updating all the firmware (which in addition to hboot also includes radio, WiFi, Bluetooth, and a lot of other important modules) not just hboot. Being on hboot 3.16 means all your firmware is outdated, as in 2 years old. Updating to current firmware is best for compatibility with current ROMs.
You can either update by RUU (as discussed above) if available for your version. Or return to stock ROM and recovery, and update OTA (which will update the firmware). But we'd need to know more specifics about your device, to give more detailed direction. Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
I have the same problem with my htc m9. I cannot do these processes as I am not a professional and don't have a computer .I have a doubt ,If it is the problem with region ,Why can't we simply changes the region by turbo VPN and try to update the Android version
mpAsifMP said:
I have the same problem with my htc m9. I cannot do these processes as I am not a professional and don't have a computer .I have a doubt ,If it is the problem with region ,Why can't we simply changes the region by turbo VPN and try to update the Android version
Click to expand...
Click to collapse
You can't do that, since for HTC devices the region has little or nothing to do with spoofing where your phone is located (with VPN, etc.). The model ID (MID) and carrier ID (CID) are encoded into the phone. You typically can't change this on HTC devices, unless you have s-off. But further advice would be specific to the M9, and you should either search or post the M9 device forum. Following advice for a different device (this is for M8) is dangerous and can damage your phone!
when i turn on my htc m9 it goes to bootloader and i have access to download mode and recovery mode (rooted TWRP) and i tried with so many RUU but always i get error 131 (RUU not matched with your CID )
my phone is UNLOCKED and S-ON i cant get it to S-OFF and change the cid :/
kernel: lk
product: htc_himawhl
version: 1.0
imei:
version-main: 2.11.651.19
boot-mode: download
version-baseband: [email protected]
version-bootloader: 1.0.0.0000
mid: 0PJA10000
cid: SPCS_001
any solution ? or RUU for my MID and CID ?
Have you identified your MID & CID? This will be key in finding the correct RUU. The best resource is the SKU/CID/MID list by Sneakyghost & Behold_this (url below). Yes, we could look it up for you, but it's best to learn firsthand and will take just a minute or two.
Once you know your carrier and model, we can start searching for the matching. From your information, it looks like you're currently on Lollipop firmware, so we're talking about moving you to Marshmallow if it's available. This will get you the latest firmware and enable you to run the latest custom ROMs, if you should choose to do so.
Useful links for modding your HTC M9
Flippy498's Google Sheet
- the end-all, be-all resource for HTC M9 restoration
SKU-, CID- and MID-List by Sneakyghost and Behold_this
- a spreadsheet for using your CID & MID to identify your phone
HTC Sync Manager
- installs the necessary drivers & ADB tools for the HTC M9
Instructions for obtaining your CID, MID & software version on Windows:
a. Install HTC Sync Manager (this will install the necessary drivers & ADB tools)
b. Boot your phone into download mode (from a powered off state, turn on by holding the POWER+DOWNVOL)
c. Connect your phone to your PC
d. Open a command prompt window
e. Navigate to the ADB tools folder, typically C:\Program Files (x86)\HTC\HTC Sync Manager\HTC Sync
- assuming the path is correct, you can cut & paste this command into your terminal: cd C:\Program Files (x86)\HTC\HTC Sync Manager\HTC Sync
f. Execute the following command in a terminal (command prompt): fastboot getvar all
g. Copy the lines that mention product, version-main, mid, and cid.
@computerslayer: It's actually easier to look at the line with "OS" at the beginning which can be found in download mode (it states the same information as version-main from getvar all) and to search for a RUU that corresponds to that firmware version. There is no need for finding out the device's CID or MID.
Edit: Besides of that all the needed information can already be found in the OP.
@djope47: Visit HTC's US website. They provide RUUs for US carriers. The search function of your browser and your version-main will probably lead you to the correct RUU. Newer versions with the same SKU (the numbers behind the second dot in the firmware version and before the third dot) should be fine, too.
Edit2: Or you look at the RUU collections which are linked in my thread (located in the general section).
Sent from my HTC One M9 using XDA Labs
i got my firmware from HTC site (sprint) and in the begging of flashing (0%) it gives me error-155 (same result with unlocked/relocked bootloader and S-ON) and when i try with zip file it tells me i dont have the correct CID
Flippy498 said:
@computerslayer: It's actually easier to look at the line with "OS" at the beginning which can be found in download mode (it states the same information as version-main from getvar all) and to search for a RUU that corresponds to that firmware version. There is no need for finding out the device's CID or MID.
Edit: Besides of that all the needed information can already be found in the OP.
Click to expand...
Click to collapse
Thanks Flippy! I appreciate the chance to learn more about the M9.
djope47 said:
i got my firmware from HTC site (sprint) and in the begging of flashing (0%) it gives me error-155 (same result with unlocked/relocked bootloader and S-ON) and when i try with zip file it tells me i dont have the correct CID
Click to expand...
Click to collapse
So you tried the M9 x.xxx.651.xx RUU from HTCs website while your phone was relocked and booted to download mode? Your phone definitely has the correct Sprint CID therefore it's not normal that you face that error. How did you try to flash the *.zip from stifilz's collection (or did you extract the *.zip from the *.exe by yourself - if so: what have been your exact steps?)? Did you use fastboot or have you tried the SD card method described in my google sheet?
I personally don't like the *.exe files or the fastboot method (which actually work the same way). They fail so many times due to little mistakes a user can make. The SD card method on the other hand doesn't rely on working USB cables, drivers, the correct USB port, and a relocked bootloader (so you can use it with an unlocked bootloader, too) or in some cases the correct windows version (some people have problems with win 10 whereas the same setup with win 7 doesn't produce a single error for them).
ive tried the sd card method (go to download mode then press volume up button ) and i got the failed msg ,i tried it with different x.xxx.651.xx RUUs all gives the same result
Is it possible to install ruu from the US developer version to HTC One m9 bought from other country ? (Dubai version )
i found this https://www.youtube.com/watch?v=xWmnHwkDrKk ,its the same problem that i have but its for htc one ,ist safe if i try it on htc m9 ?
djope47 said:
i found this https://www.youtube.com/watch?v=xWmnHwkDrKk ,its the same problem that i have but its for htc one ,ist safe if i try it on htc m9 ?
Click to expand...
Click to collapse
I didn't watch the video, but I can tell you that he is using an HTC One M7 and that I wouldn't follow instructions for anything other than your phone model (HTC One M9).
i noticed that all RUU.zip files that i downloaded are corrupted i cant extract them ,and the size of zip file is more than 2GB but the total size of the files inside it is like 70MB is this normal ? ive downloaded several RUUs and they are all with the same problem
They're encrypted and not meant to be unzipped. Therefore many programs can't handle those archives. If you use 7-zip and the #-method then you're able to unzip a RUU. However there is absolutely no reason why you should do that since they get flashed as a zip.
Sent from my HTC One S using XDA Labs
so what should i do ive tried what u said and didnt work out ! should i try this method https://www.youtube.com/watch?v=xWmnHwkDrKk ?? and in those RUUs they have the same CIDnum with my phone but the MIDnum mine is 0PJA10000 and the sprint RUUs have 0PJA20000
any solution ?
Oh yeah, I totally missed that. The MID with the 2 is the correct one for sprint. Did you buy your phone second hand? It looks like someone set is S-OFF, changed the MID and set it S-ON, again. Maybe that person flashed a RUU that's not compatible with that phone, too. You should try to find out the Serialnumber of the phone and contact HTC for finding out whether it really is a sprint phone or whether someone borked an international M9 (your current MID is the international one). GSM firmware and CDMA hardware are not compatible and vice versa. In the worst case it's unrecoverable.
If we know it's original firmware we might be able to fix the phone with a RUU. However I can't guarantee anything.
Btw, instructions how to flash RUU.zip files can be found in my google sheet, too.
Sent from my HTC One S using XDA Labs
all what you said i was the one who done that ! i bought it with s-off and with TWRP and i was trying to get it back to stock so i followed a guide that told me to change my MID to 0PJA10000 (its was 0PJA20000 at first )then i flashed a wrong RUU that was in the guide and i set it S-ON again ! i contacted htc they told me its sprint
any solution now ?
Flippy498 said:
Oh yeah, I totally missed that. The MID with the 2 is the correct one for sprint. Did you buy your phone second hand? It looks like someone set is S-OFF, changed the MID and set it S-ON, again. Maybe that person flashed a RUU that's not compatible with that phone, too. You should try to find out the Serialnumber of the phone and contact HTC for finding out whether it really is a sprint phone or whether someone borked an international M9 (your current MID is the international one). GSM firmware and CDMA hardware are not compatible and vice versa. In the worst case it's unrecoverable.
If we know it's original firmware we might be able to fix the phone with a RUU. However I can't guarantee anything.
Btw, instructions how to flash RUU.zip files can be found in my google sheet, too.
Sent from my HTC One S using XDA Labs
Click to expand...
Click to collapse
all what you said i was the one who done that ! i bought it with s-off and with TWRP and i was trying to get it back to stock so i followed a guide that told me to change my MID to 0PJA10000 (its was 0PJA20000 at first )then i flashed a wrong RUU that was in the guide and i set it S-ON again ! i contacted htc they told me its sprint
any solution now ?
I guess you're talking about the "100%" guide here in the general forum. The problem is that it only applies to the international version of the M9. Since many users don't know that there is a dedicated forum for every US branded version of the M9 mistakes like yours may occur.
If possible flash a custom rom that is compatible with your current firmware and based on sense (like an old viper version for example). Then get the sunshine app and try to re-S-OFF your phone. If you're lucky and the previous owner used sunshine, too, you won't have to pay. If not you need to invest 25 bucks to recover your phone. After you got S-OFF you change the MID back to its original state. Afterwards you should be able to use the RUU.zip as described in my sheet.
Sent from my HTC One S using XDA Labs
Flippy498 said:
I guess you're talking about the "100%" guide here in the general forum. The problem is that it only applies to the international version of the M9. Since many users don't know that there is a dedicated forum for every US branded version of the M9 mistakes like yours may occur.
If possible flash a custom rom that is compatible with your current firmware and based on sense (like an old viper version for example). Then get the sunshine app and try to re-S-OFF your phone. If you're lucky and the previous owner used sunshine, too, you won't have to pay. If not you need to invest 25 bucks to recover your phone. After you got S-OFF you change the MID back to its original state. Afterwards you should be able to use the RUU.zip as described in my sheet.
Sent from my HTC One S using XDA Labs
Click to expand...
Click to collapse
where can i find that custom rom ?or which one is the right one for my phone ? can you give me a link to it ? help me please im a noob
Being a noob is not an excuse for not using the xda search or google. The rom is even linked in my signature.
Link to Team Venoms Website
I guess version 3.5 should work fine for you.
Flippy498 said:
Being a noob is not an excuse for not using the xda search or google. The rom is even linked in my signature.
Link to Team Venoms Website
I guess version 3.5 should work fine for you.
Click to expand...
Click to collapse
damn man it worked thanks a lot
Hi, everybody, This is my first thread in this wonderfull comunity.
I own a HTC one m9 Hima UHL
-Android 5.0.2
-Sense 7.0
-Soft. version: 1.10.709.2
-MID: 0PJA11000 (the original was 2PRG10000)
-CID: 11111111 (the original was HTC__621)
-What is really great is that I GOT S-OFF AND BOOTLOADER UNLOOKED (also rooted by KINGO app)
As the title says I can boot into android and use my phone normally, but due to a several tries to update my phone to android Nougat, I surelly did something wrong
-RUU.EXE NOT WORKING (I just tried with RUU1.36.709.3.exe)
Not because of the version, is bause I can not enter in download mode, afeter running the wizard it just reboot the device.
-I DO CAN ENTER TO BOOTLOADER MODE
But anithing to do from here, if I go to to recovery (latest TWRP installed when download mode still working) or download mode, It goes to the same place "nowere", just appear a message bellow about flashing unoficial Rom, and legal stuffs, etc......
PLEASE ANY HELP (about something not tried yet) WILL BE TOTALLY APPRECIATE
I JUST WANT TO TAKE MY PHONE TO STOCK AGAIN (keeping the s-off and boatloader)
PS:
I read that once getting s-off and bootloader unlocked, it would be normal to "Cross-Flash firmware", so what I was trying to do before messing all up was to install a different firmware (different SKU or region, e.g. 3.x.617.x), and once there apply the recent released 4.19.617.1. (If somebody can correct me about this as well it would be great, but my priority now is to reset my phone to factory, no problem about personal data loss)
jhon222 said:
Hi, everybody, This is my first thread in this wonderfull comunity.
I own a HTC one m9 Hima UHL
-Android 5.0.2
-Sense 7.0
-Soft. version: 1.10.709.2
-MID: 0PJA11000 (the original was 2PRG1000)
-CID: 11111111 (the original was HTC__621)
-What is really great is that I GOT S-OFF AND BOOTLOADER UNLOOKED (also rooted by KINGO app)
As the title says I can boot into android and use my phone normally, but due to a several tries to update my phone to android Nougat, I surelly did something wrong
-RUU.EXE NOT WORKING (I just tried with RUU1.36.709.3.exe)
Not because of the version, is bause I can not enter in download mode, afeter running the wizard it just reboot the device.
-I DO CAN ENTER TO BOOTLOADER MODE
But anithing to do from here, if I go to to recovery or download mode, It goes to the same place "nowere", just appear a message bellow about flashing unoficial Rom, and legal stuffs, etc......
PLEASE ANY HELP (about something not tried yet) WILL BE TOTALLY APPRECIATE
I JUST WANT TO TAKE MY PHONE TO STOCK AGAIN (keeping the s-off and boatloader)
PS:
I read that once getting s-off and bootloader unlocked, it would be normal to "Cross-Flash firmware", so what I was trying to do before messing all up was to install a different firmware (different SKU or region, e.g. 3.x.617.x), and once there apply the recent released 4.19.617.1. (If somebody can correct me about this as well it would be great, but my priority now is to reset my phone to factory, no problem about personal data loss)
Click to expand...
Click to collapse
First of all: Please reduce the size of the text in your post. It's hard to read.
You can flash RUUs for different regions with S-OFF but you don't own a M9. The M9 has 0PJA***** model IDs. Your phone's original model ID is 2PRG1000. It's probably a M9+ or a M9+ Prime Camera edition or something like that. These devices are completely different than the M9. Therefore you shoudn't flash any M9 files on your phone unless you want a fancy new paperweight.
I recommend you reverting your MID and your CID back to their original values and try to flash a RUU for your device. (I don't know whether there is one you could use. I don't own your device and therefore have no knowledge about the file that are available for it.) If you can't find a suitable RUU you'll need to contact Llabtoofer's RUU Service.
Flippy498 said:
First of all: Please reduce the size of the text in your post. It's hard to read.
You can flash RUUs for different regions with S-OFF but you don't own a M9. The M9 has 0PJA***** model IDs. Your phone's original model ID is 2PRG1000. It's probably a M9+ or a M9+ Prime Camera edition or something like that. These devices are completely different than the M9. Therefore you shoudn't flash any M9 files on your phone unless you want a fancy new paperweight.
I recommend you reverting your MID and your CID back to their original values and try to flash a RUU for your device. (I don't know whether there is one you could use. I don't own your device and therefore have no knowledge about the file that are available for it.)
Click to expand...
Click to collapse
Dear sir, @Flippy498
Im really greatful for your answer, I can not understand why I did not see what is obvious, It is not the model I thought...
Besides de MID, the product is not Hima, but HIMARUHL, the ram 2gb and Camera 13mp... (yeahh Im very silly)
I searched over Internet and badly there is not too much information about this especific MID number (2PRG10000), wich I think now belonges to a "HTC ONE M9E". Beyond the fact that there is a RUU available or not, I think I can not install one, because once an ruu.exe is runned this one tried to enter to download mode, wich is unavailable, then reboot and throw the error "USB communication failed", Before messing up the phone, the RUU.exe throwed the "signature error" WICH I UNDERSTAND NOW, because I was trying tu run the wrong one; so I appreciate if you suggest me another way different to ruu.exe installing.
Thanks for your great attendance.
jhon222 said:
Dear sir, @Flippy498
Im really greatful for your answer, I can not understand why I did not see what is obvious, It is not the model I thought...
Besides de MID, the product is not Hima, but HIMARUHL, the ram 2gb and Camera 13mp... (yeahh Im very silly)
I searched over Internet and badly there is not too much information about this especific MID number (2PRG10000), wich I think now belonges to a "HTC ONE M9E". Beyond the fact that there is a RUU available or not, I think I can not install one, because once an ruu.exe is runned this one tried to enter to download mode, wich is unavailable, then reboot and throw the error "USB communication failed", Before messing up the phone, the RUU.exe throwed the "signature error" WICH I UNDERSTAND NOW, because I was trying tu run the wrong one; so I appreciate if you suggest me another way different to ruu.exe installing.
Thanks for your great attendance.
Click to expand...
Click to collapse
Your phone seems to have a mediatek processor. Those devices need to get handled a bit different than snapdragon devices. However, I absolutely have no experiences with mediatek devices. If I were you I'd contact the service I linked in my earlier post...
Dear XDA developers, professionals and programmers:
Recently I came across a good deal (HTC M8 in mint condition) and bought it. It was running Android 4.4.4 and I was happy with it till I read that it could be updated to Marshmallow. I followed a few links and after some time discovered that it was originally bought from the USA and locked to AT&T even though the installed rom was WWE. Stupidly I downloaded Marshmallow update for AT&T (RUU) from the HTC website and ran the installer. The installer completed successfully and the phone now runs Marshmallow with Sense7.
Since the rom was filled to brim with useless AT&T crap that does not work outside AT&T network I decided to switch to developer WWE rom but the RUU refused to install on the phone (I have S-Off)
After doing a bit more reading I discovered it was because my new rom has a software number 6.20.502.5 while the RUU I would like to install has a software number of 6.12.1540.4
I googled and googled and searched and searched but could not find a single tutorial to explain how I can replace my current rom with the WWE version which has less bloatware and takes it easy on the RAM.
Can someone kindly explain (or redirect me to a link) of how to downgrade HTC M8 from image version 6.20.502.5 to image version 6.12.1540.4 or in layman's terms how to replace AT&T rom with Developer rom? BTW both roms are Marshmallow. I do not wish to install TWRP or CM so if there is a way besides this I'd be grateful. If not then I don't see any other options and I'd still be grateful
Awaiting your generous replies
What you want is not really a "downgrade" per se. While the AT&T version number is "larger" than the Dev Ed (6.20 versus 6.12), that is mostly just because it came later due to AT&T's slowness in approving the software. I don't think there is much (if anything) that is actually "newer" or "updated" in the AT&T stock ROM (versus Dev Ed). It just has (as you know) all the AT&T branding and bloatware crap.
What is keeping you from flashing the Dev Ed RUU 6.12.1540 is that your carrier ID (CID) needs to match the RUU (even with s-off). Therefore, you need to change your CID to that of the Dev Edition (or alternately SuperCID), which is easy since you already have s-off. You will however need root to do this, so either flash TWRP and SuperSU/Magisk to root, or you can run adb shell with run while booted to TWRP. Either way, you will need to install TWRP: https://forum.xda-developers.com/htc-one-m8/general/change-wwe-m8-to-dev-edition-ota-t2826567
No need to change the Model ID (MID) since the AT&T version and Dev Edition have the same MID.
After that, you should be able to run the Dev Ed RUU.
Sorry .. correction. No need root/twrp to change CID, only change MID need these.
Simply reboot to bootloader/fastboot then run command
To Dev Ed CID
fastboot oem writecid BS_US001
To SuperCID
fastboot oem writecid 11111111
Can't remember if this only can be done on unlocked bootloader. If can't, try this command first
fastboot oem rebootRUU
the follow by the above.
If still can't then need a unlocked bootloader to proceed.
ckpv5 said:
Sorry .. correction. No need root/twrp to change CID, only change MID need these.
Click to expand...
Click to collapse
Ah yes, obviously I was mixing up my methods to change CID versus MID.
Thanks for clarifying, yet again.
Thank you
Many thanks to you gentlemen for your generous assistance and helpful instructions. I really appreciate it. All the best
Update
Good day all:
Sorry to bother again but it failed again! I downloaded fastboot adb and followed the procedure, put the phone in fastboot mode and the CID was already 11111111 and still it refused to accept the RUU. Please find attached a photo of my fastboot screen, hope it can help determine where the problem is on my phone. [ The following errors occurred with your submission:
To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!] Site refused to allow me to attach the photo link so I'll just write everything here
*****Software Status - Official******
******LOCKED******** (Even though I can use a non AT&T sim normally)
MS_UL_CA PVT SHIP S-OFF
CID~11111111
HBOOT - 3.19.0.0000
Radio - [email protected](long number)
OPENDSP - v56.2.2. (loooooooong number)
OS-6.20.502.5
eMMC Boot - 2048MB
*end of pic*
On the official HTC site in the support section where they post the RUUs it states the following.
"Before you proceed, please confirm that this software upgrade to 6.12.1540.4 is a newer version than what is currently loaded on your device. If it is the same version, there is no need to reload the software. Navigate to the Home screen then tap All apps > Settings > About and locate the Software information . If your Software number is less than 6.12.1540.4 , you should proceed with the upgrade." end of quote
This paragraph is what let me to believe it is the software version that is stopping me from changing RUUs and why I called this post a downgrade (even though I know it's not)
Can any of you good gentlemen help me out a bit more? I'm willing to answer any questions to further clear the picture of my predicament.
Thank you again
Bootloader is fine, still ATT.
Explain more on the error that you have when you tried installing RUU.
Do note - to run RUU you need PC with USB 2.0;
Latest htc usb drivers which you'll get when you installed latesr htc sync manager (uninstall sync manager but leave all drivers to proceed RUU installation)
ckpv5 said:
Bootloader is fine, still ATT.
Explain more on the error that you have when you tried installing RUU.
Do note - to run RUU you need PC with USB 2.0;
Latest htc usb drivers which you'll get when you installed latesr htc sync manager (uninstall sync manager but leave all drivers to proceed RUU installation)
Click to expand...
Click to collapse
Thank you for your reply:
the RUU I'm trying to install is the developer RUU that I downloaded off the HTC official website. It is the same website I downloaded the AT&T RUU from which installed fine, upgrading the phone's OS from Android 4.4.4 to Android 6.0.
I have several laptops each running a different OS (Windows 7 which I use mostly and have been using for this process) Windows 10, Linux and Solaris.
I did download and install HTC Sync but disabled it's auto run when I noticed every time I plug my phone in it pops up. So that's disabled not uninstalled, but it didn't interfere in the RUU installation of the ATT update and it doesn't pop up when I try to install the developer update.
The Error get is as follows:
Upon running the RUU it does all the necessary checks and then asks me if I would like to install the update, I click on "I Agree" and next, then it puts the phone in boot mode (black screen with HTC written in grey) and after it begins the process by popping up a screen that says: Current info about your Android phone: Image Version: 6.20.502.5 select one below and the update button. After I click on it another screen pops up: Verify that you want to update the Rom version from image version 6.20.502.5 to image version 6.12.1540.4 Clicking on Next another windows shows explaining what happens when I click on Next. When I click next it puts the phone in boot mode and begins by Reading header, sending............................................. then it pops another screen that says update failed and I have to click on recovery and press the power button on my phone for 10 seconds to turn it off
Sir Lucifer said:
On the official HTC site in the support section where they post the RUUs it states the following.
"Before you proceed, please confirm that this software upgrade to 6.12.1540.4 is a newer version than what is currently loaded on your device. If it is the same version, there is no need to reload the software. Navigate to the Home screen then tap All apps > Settings > About and locate the Software information . If your Software number is less than 6.12.1540.4 , you should proceed with the upgrade." end of quote
This paragraph is what let me to believe it is the software version that is stopping me from changing RUUs and why I called this post a downgrade (even though I know it's not)
Click to expand...
Click to collapse
You can't really take the "official" HTC info literally, anymore. By having s-off and SuperCID, you are so far off the "official" path, that most of the rules no longer apply.
S-off bypasses version check (flashing older RUUs is allowed). In fact, you can RUU all the way back to Kitkat if you wanted with s-off (not recommended - just making a point).
---------- Post added at 09:56 AM ---------- Previous post was at 09:52 AM ----------
Sir Lucifer said:
The Error get is as follows:
Upon running the RUU it does all the necessary checks and then asks me if I would like to install the update, I click on "I Agree" and next, then it puts the phone in boot mode (black screen with HTC written in grey) and after it begins the process by popping up a screen that says: Current info about your Android phone: Image Version: 6.20.502.5 select one below and the update button. After I click on it another screen pops up: Verify that you want to update the Rom version from image version 6.20.502.5 to image version 6.12.1540.4 Clicking on Next another windows shows explaining what happens when I click on Next. When I click next it puts the phone in boot mode and begins by Reading header, sending............................................. then it pops another screen that says update failed and I have to click on recovery and press the power button on my phone for 10 seconds to turn it off
Click to expand...
Click to collapse
The RUU stalling out while "sending" is a common bug. Did you simply try running the RUU again? A lot of times, it will work on subsequent attempts.
The fact it got that far, means to me that it passed (or bypassed) any version or CID checks. Otherwise, it never would have gotten to the point of "sending". Instead, it would have told you something like "Error 140" with a description of what the problem was, and aborted the install before ever "sending".
redpoint73 said:
You can't really take the "official" HTC info literally, anymore. By having s-off and SuperCID, you are so far off the "official" path, that most of the rules no longer apply.
S-off bypasses version check (flashing older RUUs is allowed). In fact, you can RUU all the way back to Kitkat if you wanted with s-off (not recommended - just making a point).
---------- Post added at 09:56 AM ---------- Previous post was at 09:52 AM ----------
The RUU stalling out while "sending" is a common bug. Did you simply try running the RUU again? A lot of times, it will work on subsequent attempts.
The fact it got that far, means to me that it passed (or bypassed) any version or CID checks. Otherwise, it never would have gotten to the point of "sending". Instead, it would have told you something like "Error 140" with a description of what the problem was, and aborted the install before ever "sending".
Click to expand...
Click to collapse
Have tried it 5 times already, results are the same. I'm downloading the RUU again, maybe my download was corrupt. Will get back to you later with any results. Thank you for your patience and time. Much appreciated
redpoint73 said:
You can't really take the "official" HTC info literally, anymore. By having s-off and SuperCID, you are so far off the "official" path, that most of the rules no longer apply.
S-off bypasses version check (flashing older RUUs is allowed). In fact, you can RUU all the way back to Kitkat if you wanted with s-off (not recommended - just making a point).
---------- Post added at 09:56 AM ---------- Previous post was at 09:52 AM ----------
The RUU stalling out while "sending" is a common bug. Did you simply try running the RUU again? A lot of times, it will work on subsequent attempts.
The fact it got that far, means to me that it passed (or bypassed) any version or CID checks. Otherwise, it never would have gotten to the point of "sending". Instead, it would have told you something like "Error 140" with a description of what the problem was, and aborted the install before ever "sending".
Click to expand...
Click to collapse
Maybe my downloaded RUU is corrupt, I'll download another time and if it gives me the same problem I'll look for another source. I will keep you posted, thank you very much good man.
RUU Broken on HTC's website
Dear all:
After downloading the developer RUU for the second time and trying to install it again (Marshmallow for those of you who have just joined us) off the HTC support site I failed miserably at changing my firmware using that RUU. After a series of searches on the internet and darknet I came across a post on reddit dot com titled M8 marshmallow RUU from HTC is broken and the article was dated last year. Searching further I found a similar post on a Chinese website that stated the same thing. So in conclusion the developer RUU on HTC's site is damaged as confirmed by a few users/developers on both reddit and the Chinese website.
Sorry for wasting all your time gentlemen. I am very grateful (and very lucky) having assistance from good people like yourselves who have taken from their time to help a complete stranger. Much obliged gentlemen. And thank you all again
Cannot be the RUU is broken.
Another way to do this :
1. Install Dev Edition firmware. You can get the fw_6.12.1540.4.zip from - https://forum.xda-developers.com/showpost.php?p=60218734&postcount=5
2. Instead of using RUU exe, you can use RUU zip (rom.zip) to install RUU. I remember long time ago someone had same problem like you. Asked him to use zip format RUU and it was successful.
I believe there is RUU.zip somewhere on XDA. Can't search now as I'm on mobile.
You can get your own RUU.zip which is actually rom.zip yourself. Just run RUU.exe (no need to connect phone). Once it opens the agreement page, go to %temp% thru your search/run windows menu.
It's better to clear your temp directory first so easy to find 2 newly created folder when you run RUU.exe
The rom.zip is inside one of the folder. Copy that to your desktop.
Then follow this on how to install - https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
There are 3 methods but I prefer the htc_fastboot because easily can see any error if any.
So step 1 firmware & step 2 RUU (rom.zip)
Sir Lucifer said:
Dear all:
After a series of searches on the internet and darknet I came across a post on reddit dot com titled M8 marshmallow RUU from HTC is broken and the article was dated last year. Searching further I found a similar post on a Chinese website that stated the same thing. So in conclusion the developer RUU on HTC's site is damaged as confirmed by a few users/developers on both reddit and the Chinese website.
Click to expand...
Click to collapse
Did those threads specifically mention RUU 6.12.1540.4? If not, then you realize this device has dozens of RUUs for the M8? Most of which have been confirmed many times over to work properly.
My experience, is that 95% of the time, the problem with RUU running is with the PC. Try re-installing HTC drivers, different USB port, turn off USB 3.0. Also try a different USB cable, or if possible another PC.
Downloading the RUU again (as you tried) is not a bad idea. They do sometimes get corrupted while downloading. But if you download another time, and it still fails, the problem is probably not the RUU.
You should also verify your PC has Visual C++ installed, as the RUU exe requires it. The error your are encountering doesn't sound like the C++ problem. But it won't hurt to verify, anyway. Link here, but confirm it's the right install for your Windows version: https://forum.xda-developers.com/showpost.php?p=60021580&postcount=4
Or of course, you can use the RUU.zip method stated by ckpv5, which avoids all the of the above possible pitfalls. You'll need to search for the 6.12.1540.4 zip, as I don't know where it is off hand, either.
Downloaded Again
redpoint73 said:
Did those threads specifically mention RUU 6.12.1540.4? If not, then you realize this device has dozens of RUUs for the M8? Most of which have been confirmed many times over to work properly.
My experience, is that 95% of the time, the problem with RUU running is with the PC. Try re-installing HTC drivers, different USB port, turn off USB 3.0. Also try a different USB cable, or if possible another PC.
Downloading the RUU again (as you tried) is not a bad idea. They do sometimes get corrupted while downloading. But if you download another time, and it still fails, the problem is probably not the RUU.
You should also verify your PC has Visual C++ installed, as the RUU exe requires it. The error your are encountering doesn't sound like the C++ problem. But it won't hurt to verify, anyway. Link here, but confirm it's the right install for your Windows version: https://forum.xda-developers.com/showpost.php?p=60021580&postcount=4
Or of course, you can use the RUU.zip method stated by ckpv5, which avoids all the of the above possible pitfalls. You'll need to search for the 6.12.1540.4 zip, as I don't know where it is off hand, either.
Click to expand...
Click to collapse
I did download the developer RUU again, I also downloaded the Metro PCS RUU which has a software number of 6.20.531.5 and it installed just fine but refused to see the sim card so I reinstalled AT&T
I am an electronics engineer so yes my laptops are always up to date on flash, oracle, C++, Perl, Java, etc
ckpv5 said:
I believe there is RUU.zip somewhere on XDA. Can't search now as I'm on mobile.
Click to expand...
Click to collapse
redpoint73 said:
You'll need to search for the 6.12.1540.4 zip, as I don't know where it is off hand, either.
Click to expand...
Click to collapse
Sir Lucifer said:
I did download the developer RUU again, I also downloaded the Metro PCS RUU which has a software number of 6.20.531.5 and it installed just fine but refused to see the sim card so I reinstalled AT&T
I am an electronics engineer so yes my laptops are always up to date on flash, oracle, C++, Perl, Java, etc
Click to expand...
Click to collapse
I have the RUU.zip
You can download it from here :good:
Sir Lucifer said:
I also downloaded the Metro PCS RUU which has a software number of 6.20.531.5 and it installed just fine but refused to see the sim card so I reinstalled AT&T
Click to expand...
Click to collapse
That is the T-Mobile RUU. MetroPCS merged with T-Mobile, so it's a bit one and the same. But most everyone will call that RUU/version T-Mobile. It will change band support (as flashing any other RUU will). So if it was working before on the AT&T RUU(or Dev ED will support the same bands) I would not mess with random RUUs, unless we suggest them specifically.
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.