HTC One (M9) ReadMe ThreadEdit from the 17.08.2018: I don't know what happened exactly but it looks like a lot of the files that were hosted on AFH by me and others aren't available, anymore. Since I don't have them backed up on my laptop, anymore, I won't be able to re-upload them if AFH isn't able to recover the files. All non-working links got removed, for now.
Welcome to the HTC One (M9) ReadMe Thread. Here, you'll find some basic information (which you should read before you start flashing) and every Stock File (e.g. RUUs, TWRP backups or OTAs) that you guys contributed, so far. Besides, you'll find instructions that are needed to flash these files. Make sure that you read them, as well. HTC changed a lot with the M9 and many things you might know from older HTC devices don't apply to the M9.
Be aware that this thread relies on your contribution or it will waste away. If no one contributes any newer OTAs, TWRP backups or RUUs then chances are high that you or others might face a situation in which you can't recover your phone without having to pay for help.
This thread is located in the forum of the [GSM] international HTC One M9 (codename: hima_uhl - MID: 0PJA10000). Therefore, most (not all) of the files you can find here can only be used with GSM versions of the M9. However, much of the information in this thread applies to the other versions, as well. There are device-specific forums for every US variant of the M9. Make sure you search through them, as well, if you own one of the following models:
[GSM] AT&T/Developer Edition/Unlocked HTC One M9 (codename: hima_ul / hima_ulatt - MID: 0PJA11000)
[GSM] T-Mobile (US) HTC One M9 (codename: hima_ul / hima_ultmus - MID: 0PJA12000)
[CDMA] Sprint HTC One M9 (codename: hima_whl - MID: 0PJA20000)
[CDMA] Verizon HTC One M9 (codename: hima_wl - MID: 0PJA30000)
If you don't know the difference between GSM and CDMA you should read this article before you continue reading my thread. The article explains why you might not be able to get LTE reception with a CDMA device while using it in other countries than the US, as well.
Disclaimer:
You are aware that you use the files and guides that get provided in this thread at your own risk.
You understand and agree that neither I nor xda nor any of the authors of linked guides are responsible for any damages that might result from using the files and/or guides.
You understand that you should not use any of the files or guides if you aren't willing to take the risk.
Important Note:
You should do yourself a favour and check the MD5 sum of the files you downloaded before you flash them. This way you can make sure that the files you're using didn't get broken during the download. You can use WinMD5 (for Win 7/8.0/8.1) or File Hasher (for Win 10) for that purpose. The desired value can be found on the download site of the dedicated files. Unfortunately neither Google Drive nor Mega.nz nor MediaFire provide MD5 sums for their downloads. Therefore, you can only hope that everything went well if you downloaded a file from one of these three file hosters.
Overview
Post #3: Setting up ADB/Fastboot/HTC_Fastboot correctly
Post #4: Unlocking the Bootloader and Rooting/Installing a Custom Rom
Post #5: How to convert your M9 to a different version
Post #6: Basics about RUUs, Download Links and Instructions how to flash them
Post #7: Common RUU errors
Post #8: Basics about TWRP Backups and Instructions how to create them
Post #9: Flashing/Restoring Instructions for TWRP Backups and Download Links
Post #10: Stock Recoveries and Instructions how to flash/restore them
Post #11: Basics about OTAs, Download Links and Instructions how to install them with TWRP
Post #12: Useful links for further reading
Post #13: FAQ
Post #14: Credits
Take me back to the Overview
Setting up ADB/Fastboot/HTC_Fastboot correctlyPrerequesits:
You need Windows 7/8/8.1/10.
You need this archive. (Those files got extracted manually from HTC's RUUs.)
You need the latest 7-zip version or any other program that can handle *.zip archives.
You should've installed all needed Runtimes.
An all-in-one Installer can be found e.g. here. (The website and the installer are using the German language. Send me a link if you know an English alternative.)
The HTC USB Driver Installer is needed.
Install the HTC Sync Manager and uninstall it immediately. The Manager is known to cause problems with ADB and Fastboot. The drivers won't get affected by uninstalling the Manager.
Instructions:
Create a new folder on your desktop called "android".
Unzip the ADB/Fastboot archive into that folder. There musn't be any subfolders!
Troubleshooting:
Make sure that the HTC USB drivers are installed.
If the HTC Sync Manager is installed on your PC you should uninstall it.
Make sure that all needed Runtimes are installed.
If you aren't using the cable that came with your phone you should try the original one.
If you're using a USB 3.0 port you should try a USB 2.0 port.
If you're using a Windows 8/8.1/10 PC you should try a Windows 7 PC.
Make sure that you only try to use Fastboot/HTC_Fastboot while your phone is booted to Bootloader or Download Mode. You can't use them while the phone is booted to the normal system.
Make sure that you only try to use ADB while your phone is booted to TWRP (if installed) or to the system. You can't use ADB while the phone is booted to Bootloader or Download Mode.
Take me back to the Overview
Take me back to the Overview
Unlocking the Bootloader and Rooting the M9/Installing a Custom RomPrerequisites and important infos:
You'll need an external SD card with a size of at least 8 GB.
This guide assumes that you're using the latest 4.x firmware.
You're going to verify that with step 1 of the instructions.
You can't follow step 4 (which is optional) if you don't use at least firmware 3.x!
Check Q4 and Q5 of the FAQ section if you skip step 2 while using firmware 1.x, 2.x or 3.x since these require older TWRP and SuperSU versions than firmware 4.x. Your phone will not be able to boot to recovery mode or end in a bootloop if you don't use the correct files.
You need a working ADB/Fastboot/HTC_Fastboot environment.
You need the official TWRP 3.2.2-0.
(Optional) Read the RUU section or TWRP section II if you want to restore an untouched system image and the stock recovery after following this guide.
The instructions aren't usable with a Verizon M9 due to the bootloader unlock being blocked by Verizon. You need S-OFF for being able to unlock it. Sunshine S-OFF only works on firmware 3.x or below (Android Marshmallow and older). Alternatively, you can look for someone who owns a Java card or an XTC clip. I recomend you taking a look at the Verizon M9 forum. Chances are higher that you'll find what you need over there.
Instructions:
Boot to download mode and look at the line with "OS" at the beginning for finding out your current firmware version.
That means: Power off the device, wait some seconds and turn it on again while you keep volume down pressed until you see a black screen with red, blue and yellow text. If you see a white screen with multicoloured text then you're facing the Bootloader mode. In that case you can navigate to "Boot to Download Mode" with the volume keys and select the option with the power button.
(Optional) Install all available OTAs (via the software update function of the system settings) if you aren't using the latest 4.x firmware
Unlock your phone's bootloader via HTCdev.
Your internal storage will get wiped by doing so!
Since you already have a working ADB/Fastboot/HTC_Fastboot environment you don't need to download the android SDK from HTCdev.
(Optional) I highly recommend to follow the instructions in the TWRP section I.
Even if you don't want to share your backup with us you should at least keep it on your PC so that you're prepared if you need to revocer your phone.
Boot Download Mode, again.
Open the folder that contains your ADB/fastboot/HTC_fastboot files on your PC.
Press and hold Shift on your keyboard.
Right-click into the folder.
Choose "open command window here".
If you're using the Win 10 Creator's update or any newer version then you need to choose "open powershell window here".
Type "start cmd" without the quotation marks and execute the command with pressing Enter on your keyboard.
Use the command
Code:
fastboot flash recovery twrp-3.2.2-0-hima.img
(execute it with Enter).
Wait a bit. TWRP should get flashed on your phone.
Reboot to Bootloader Mode.
Choose "Boot to Recovery Mode".
If you want to keep the stock rom and only gain root you need to follow instruction A. If you want to install a custom rom you need to follow instruction B. (Be aware that most custom roms come pre-rooted.)
Get either SuperSU 2.79 SR3 or the latest Magisk version and copy the *.zip you chose into the download folder of your external sd card. Choose "Install" and navigate to your external sd card's download folder. Select the SuperSU/Magisk file and install it by swiping. Reboot your phone after the flash got finished. It's rooted, now.
Get the latest version of the rom you want to flash from either the android development section or the original android development section (make sure that you read all important information that got posted in the first posts of the rom thread) and copy the *.zip you chose into the download folder of your external sd card. Choose "Wipe" and wipe everything except for "Micro SDcard", "USB-OTG" and "SD-Ext" via the advanced wipe. Get back to the main menu and choose "Install" and navigate to your external sd card's download folder. Select the rom and install it by swiping. (Be aware that roms that aren't based on HTC's stock rom (e.g. LineageOS or Resurection Remix) may lack all google apps. You can download them from here. Choose the ARM64 version that corresponds to the android version of your custom rom. It doesn't matter which variant you use so choose the one that suits you best and install it via the install option after you flashed the rom. This is not needed for roms like Android Revolution, ICE, MaximusHD, Viper or Leedroid.) Reboot your phone after the flash got finished. The first boot may take a while.
(Optional) If you want you can set your phone S-OFF with the Sunshine app, now. Be aware that this is only possible on roms that are based on HTC's stock rom or the stock rom itself. More information about S-OFF can be found here.
Take me back to the Overview
Take me back to the Overview
How to convert your M9 to a different version
This guide is based on clsA's conversion guides (older one/newer one). I only updated some of the information so most of the credits go to him.
Prerequisites and important infos:
This is only possible with S-OFF and only owners of a GSM version should follow these instructions.
[*]Owners of a CDMA device may damage their phone unrecoverably by using these instructions. Read the RUU section if you want to know why.
A working ADB/Fastboot/HTC_Fastboot environment is mandatory.
Instructions:
Boot to download mode and look at the line with "OS" at the beginning for finding out your current firmware version.
That means: Power off the device, wait some seconds and turn it on again while you keep volume down pressed until you see a black screen with red, blue and yellow text. If you see a white screen with multicoloured text then you're facing the Bootloader mode. In that case you can navigate to "Boot to Download Mode" with the volume keys and select the option with the power button.
Download the RUU for the firmware you want to convert to from the RUU section.
For minimizing headaches, you should only use RUUs whose major version (1.x, 2.x, 3.x or 4.x) matches the one your phone is using.
Connect your phone via USB with your PC.
Open the folder that contains your ADB/fastboot/HTC_fastboot files on your PC.
Press and hold Shift on your keyboard.
Right-click into the folder that contains your ADB/fastboot/HTC_fastboot files.
Choose "open command window here".
If you're using the Win 10 Creator's update or any newer version then you need to choose "open powershell window here".
Type "start cmd" without the quotation marks and execute the command with pressing Enter on your keyboard.
Copy'n'paste the command
Code:
fastboot getvar all
and execute it with Enter on your keyboard.
Write down your CID and your MID on a piece of paper so that you know them in case you want to revert to the original firmware of your phone.
Change your MID using the command
Code:
fastboot oem writemid <enter MID of the RUU you want to flash>
and executing it with Enter. This might not be needed if your original MID already matches the one of the RUU you want to flash, later on.
Example for the Dev Edition RUU 3.35.617.12:
Code:
fastboot oem writemid 0PJA11000
Change your CID by using the command
Code:
fastboot oem writecid <enter CID of the RUU you want to flash>
and executing it with Enter.
Example for the Dev Edition RUU 3.35.617.12:
Code:
fastboot oem writecid BS_US002
Choose the option "reboot to download mode" on your phone.
Verify whether CID and MID got changed correctly by using the command
Code:
fastboot getvar all
and executing it with Enter.
Flash the RUU you downloaded before with one of the methods from the RUU section.
It doesn't matter which method you use.
Congrats! You sucessfully converted your M9 to a different version.
Take me back to the Overview
Take me back to the Overview
RUU SectionGeneral infos:
Rom Update Utilities (RUUs) are *.exe or *.zip files with which you can reflash the stock system and the whole firmware of your phone quite easily.
Strictly speaking only the *.exe files are RUUs (which are nothing more than a *.zip file combined with a fancy installer and HTC_Fastboot files). However, people got used to call them both RUUs and since most of the files here are *.zip files I don't want to start nitpicking.
The catch is that HTC only provides RUU.exe files for their US customers. All other RUUs which you can find in this post got leaked somehow and no one knows if or when new non-US RUUs are going to be available. That's why it might happen that non-US users can't find a publicly available RUU they could use with their phone.
S-ON Users can (in most cases) only use RUUs which have at least the same firmware version as their phone.
That means a downgrade is (in most cases) not possible with S-ON.
S-OFF Users on the other hand can use almost every RUU they want. Be aware that flashing a CDMA RUU on a GSM device and vice versa will probably lead to unrecoverable damages due to differences in their partition layout. It's not even safe to flash a CDMA RUU on your phone if the SKU of your current firmware and the one of the RUU don't match. The partition layout of the different CDMA versions differs in many cases, as well.
In addition to that, there are some RUUs on the internet which contain "combined_signed" in their naming. These RUUs are not officially signed by HTC although the files inside these archives are signed correctly. You can compare this kind of RUUs with Sneakyghost's firmware packs. The content is official but the archive itself isn't.
Due to signature checks of the M9 you probably won't be able to flash combined_signed RUUs without S-OFF if you're using firmware 1.x or 2.x.
Since HTC seems to have changed the signature check you might be able to flash 4.x combined_signed RUUs on a 4.x device even with S-ON.
I haven't found any reports (neither positive nor negative ones) about 3.x combined_signed RUUs, yet. It would be nice if a user with firmware 3.x and S-ON could confirm whether combined_signed RUUs are working on that firmware already.
All combined_signed RUUs that are linked in this post are confirmed to be working with S-ON.
S-OFF users should be aware that the phone's CID and MID need to correspond to the SKU of the RUU you want to flash. The SCID (11111111) won't make your phone ignore mismatches between those ID numbers as it did on older HTC devices.
In addition to that, you can't flash RUU.zip files with fastboot, anymore. The RUUs for the M9 are too big so that fastboot can't handle them.
A special version which got developed by HTC (HTC_Fastboot) is needed for that purpose.
In contrast to RUUs of older HTC devices M9 RUUs can get flashed with an unlocked bootloader even if the phone is S-ON.
I highly discourage everyone from (re-)locking the bootloader unless you have a working RUU at hand and know that you're able to flash it (via HTC_fastboot or an SD card if it's a *.zip). Security features of the M9 prevent the phone from booting if anything is modified and the bootloader is (re-)locked. You can't even enter TWRP, anymore, in this situation. In addition, you can't re-unlock if "OEM Unlock" (introduced with firmware 2.x) isn't activated in the developer options. You've been warned about the risks.
Important Notes:
There are several reports about downgrades being possible with S-ON in some specific cases and without the need of any additional tricks (e.g. during this conversation: Link #1, Link #2). It looks like you're able to downgrade whenever the firmware version you're currently using and the one of the RUU only differ in the numbers behind the SKU. In other words the part marked with y of x.xx.xxx.yy is allowed to differ whereas x needs to be the same for your current firmware version and the RUU (e.g. downgrades from 1.32.401.15 to 1.32.401.8 or from 3.35.401.32 to 3.35.401.12 are possible but from 1.40.401.8 to 1.32.401.15 or from 3.35.401.12 to 2.10.401.1 aren't). I've tested it myself before I set my phone S-OFF and I can confirm that it is working.
In addition it's possible to downgrade anytime if you delete the main version of your phone via dd commands, beforehand. Be aware that the tiniest mistake while using dd commands can lead to unrecoverable damages because of the nature of these commands. Due to its risks I won't be supporting that method in this thread. However, you might be able to find a thread that deals with this method if you use the forum search.
It doesn't matter which method you use but the SD card method is the recommended one since it's the most fail-safe method.
If you have a RUU.exe at hand but want to use a different flashing method you can extract the *.zip file using these instructions. Although they're a bit older they can still be used with M9 RUUs. Alternatively, you can use the Universal Decryption Tool.
HTC changed the M9's encryption keys several times:
Firmware 1.x is unencrypted
Firmware 2.x and 3.x use the "first" encryption key
Firmware 4.x uses the "second" encryption key
The consequences are that you cant flash 2.x, 3.x or 4.x RUUs if your phone is currently using a 1.x firmware and that you cant flash 4.x RUUs if your phone is currently using a 2.x or a 3.x firmware. Both, OTAs and Sneakyghost's custom firmware packs, are unencrypted. In other words, for updating your M9 you either need to flash a NoWipe/Full-Wipe Firmware Pack that contains the new encryption key beforehand (only possible with S-OFF) or you need to use the latest RUU for your SKU that uses the same encryption key as your phone. If you choose the latter you need to install the available OTAs, afterwards.
Another consequence is that downgrades from 4.x to firmware 2.x or 3.x aren't that easy, either. You need to flash a NoWipe or a Full-Wipe Firmware Pack for either firmware 2.x or 3.x before you're able to use 2.x or 3.x RUUs, again.
Downgrading to firmware 1.x should be possible without any extra steps since that firmware isn't encrypted at all.
Instructions for the SD card method:
Be aware that you need an external SD card for your phone that is not bigger than 32 gb.
The size limit doesn't apply to phones with firmware version 3.x or higher.
According to the Download Mode of firmware 4.x you should be able to use USB-OTG instead of an SD card on firmware 4.x and higher. However, I haven't tried this alternative, yet. (If someone is willing to try it I would be happy if that person could report back whether it worked or not.)
Flashing a RUU will erase all personal data on your phone! Make a backup of everything you don't want to lose before you start flashing.
Boot to download mode and look at the line with "OS" at the beginning for finding out your current firmware version.
The "firmware version" in "settings>about>software information>more" is only the base of the (custom) rom you are running and might therefore differ from the real one in the download mode.
Remember that you can always flash newer RUUs as long as they use the same encryption key as your current firmware. (c.f. the important notes in this post)
Download or extract the correct RUU.zip for your phone.
Rename the file to "0PJAIMG.zip". (Make sure that file extensions are visible so that you don't rename the file to "0PJAIMG.zip.zip"!)
Copy the file to the root directory of a SD card which is formatted to fat32. (If you're on firmware version 3.x or higher you can use an exfat formatted SD card, too.)
It looks like this is only possible if the SD card is directly connected to your PC and not put into your phone.
However, it got reported that you can copy the file while the card is put into your phone if the RUU lacks its file extension (".zip"). Don't forget to re-add the extension if you choose to delete it.
Put the card into your phone and boot to Download Mode.
You will be asked whether you want to flash the file. Confirm with the volume up button.
Your phone will reboot at least one time.
Depending on your current firmware version it may reboot to Android or the Bootloader instead of rebooting to Download Mode. If this happens you just need to manually boot it to Download Mode.
Flashing may take some time.
At the end you will be asked to push the power button. You phone will shut down if you do so.
Wait some seconds and then turn your phone on, again.
First boot may take a while.
Congrats! Your system is now stock and able to receive and install official OTAs, again.
Instructions for RUU.exe files:
Windows 7/8/8.1/10 is required.
Flashing a RUU will erase all personal data on your phone! Make a backup of everything you don't want to lose before you start flashing.
Boot to download mode and look at the line with "OS" at the beginning for finding out your current firmware version.
The "firmware version" in "settings>about>software information>more" is only the base of the (custom) rom you are running and might therefore differ from the real one in the download mode.
Remember that you can always flash newer RUUs as long as they use the same encryption key as your current firmware. (c.f. the important notes in this post)
Download the correct RUU.exe for your phone from HTC's website.
Boot your M9 to Download Mode.
Connect your phone with your PC via a USB cable.
Run the RUU.exe and follow the on-screen Instructions.
Flashing may take some time. Your phone will power off at the end.
Wait some seconds and then turn your phone on, again.
First boot may take a while.
Congrats! Your system is now stock and able to receive and install official OTAs, again.
Instructions for the ARUWizard method:
Basically, you're creating your own RUU.exe for non-US RUUs with this method.
The credits for this method go to Golv and Nikolay82.
Windows 7/8/8.1/10 is required.
Flashing a RUU will erase all personal data on your phone! Make a backup of everything you don't want to lose before you start flashing.
Boot to download mode and look at the line with "OS" at the beginning for finding out your current firmware version.
The "firmware version" in "settings>about>software information>more" is only the base of the (custom) rom you are running and might therefore differ from the real one in the download mode.
Remember that you can always flash newer RUUs as long as they use the same encryption key as your current firmware. (c.f. the important notes in this post)
Download the correct RUU.zip for your phone.
Rename the file to "rom.zip". (Make sure that file extensions are visible so that you don't rename the file to "rom.zip.zip"!)
Download and unpack this archive.
Copy the RUU into the "Wizard_RUU" folder.
Boot to Download Mode.
Connect your phone with your PC via a USB cable.
Run the ARUWizard.exe and follow the on-screen Instructions.
Flashing may take some time. Your phone will power off at the end.
Wait some seconds and then turn your phone on, again.
First boot may take a while.
Congrats! Your system is now stock and able to receive and install official OTAs, again.
Troubleshooting for RUU.exe files and the ARUWizard method:
Make sure that the HTC USB drivers are installed. Install the HTC Sync Manager if they aren't.
If the HTC Sync Manager is installed on your PC you should uninstall it. This won't affect the USB drivers.
Make sure that all needed Runtimes are installed.
If you aren't using the cable that came with your phone you should try the original one.
If you're using a USB 3.0 port you should try a USB 2.0 port.
If you're using a Windows 8/8.1/10 PC you should try a Windows 7 PC.
Try to run the RUU.exe/ARUWizard.exe as an admin if you didn't do so before.
Deactivate your PCs internet connection (this is only meant for your own safety) and disable your firewall and you antivirus program, afterwards. In some cases these programs block a RUU.exe/ARUWizard.exe.
Instructions for the HTC_Fastboot method:
Basically, you're doing manually with this method what a RUU.exe/ARUWizard is doing automatically.
A working ADB/Fastboot/HTC_Fastboot environment is mandatory.
Flashing a RUU will erase all personal data on your phone! Make a backup of everything you don't want to lose before you start flashing.
Boot to download mode and look at the line with "OS" at the beginning for finding out your current firmware version.
The "firmware version" in "settings>about>software information>more" is only the base of the (custom) rom you are running and might therefore differ from the real one in the download mode.
Remember that you can always flash newer RUUs as long as they use the same encryption key as your current firmware. (c.f. the important notes in this post)
Download the correct RUU.zip for your phone.
Copy the RUU into the folder that contains your ADB/fastboot/HTC_fastboot files on your PC.
Boot to Download Mode.
That means: Power off the phone, wait some seconds and turn it on again while you keep volume down pressed until you see a black screen with red, blue and yellow text. If you see a white screen with multicoloured text then you're facing the Bootloader mode. In that case you can navigate to "Boot to Download Mode" with the volume keys and select the option with the power button.
Connect your phone with your PC via a USB cable.
Press and hold Shift on your keyboard.
Right-click into the folder that contains your ADB/fastboot/HTC_fastboot files.
Choose "open command window here".
If you're using the Win 10 Creator's update or any newer version then you need to choose "open powershell window here".
Type "start cmd" without the quotation marks and execute the command with pressing Enter on your keyboard.
Copy'n'paste the command
Code:
htc_fastboot flash zip <enter name of the RUU.zip here>
and execute it with Enter on your keyboard.
Example for the European RUU 3.35.401.12:
Code:
htc_fastboot flash zip 0PJAIMG_HIMA_UHL_M60_SENSE70_HTC_Europe_3.35.401.12_Radio_01.01_U11440792_97.00.51203G_F_release_signed.zip
Some firmware files will get flashed and you'll face error 90. Don't panic! This is completely normal and has already been like this for several older HTC devices.
Execute the flashing command a second time.
Flashing may take some time. Your phone will power off at the end.
Wait some seconds and then turn your phone on, again.
First boot may take a while.
Congrats! Your system is now stock and able to receive and install official OTAs, again.
Download Links:
Sidenote: The SKU is part of your firmware version and located between the second and the third dot. Example: If 3.35.401.12 is your current firmware then you need to look for RUUs with SKU 401.
GSM RUUs
codename: hima_uhl - MID: 0PJA10000
SKU: 401 - CID: HTC__001, HTC__J15, HTC__102, HTC__Y13, HTC__A07, HTC__032, HTC__016, HTC__M27, HTC__002 or HTC__031
1.32.401.8
1.32.401.15
1.40.401.8
2.10.401.1
3.35.401.12
4.14.401.7 (MD5: 148A8AF99EBDC7B26B4B14C09179D6E0)
4.28.401.3
SKU: 708 - CID: HTC__622 or HTC__044
1.32.708.15
SKU: 709 - CID: HTC__621
1.36.709.3
1.40.709.8
2.10.709.1
3.36.709.3
4.16.709.3
4.30.709.12
SKU: 710 - CID: HTC__039, TELNZ001, OPTUS001 or VODAP021
2.9.710.2
2.9.710.5
3.50.710.1
4.23.710.1
SKU: 111 - CID: T-MOB101
1.32.111.6
1.40.111.8
2.10.111.6
3.35.111.14
SKU: 118 - CID: T-MOB009
3.35.118.12
SKU: 161 - CID: VODAP001, VODAP102, VODAP304, VODAP405, VODAPE17 or VODAPD18
1.32.161.7
1.40.161.8
2.10.161.7
3.35.161.12
4.17.161.11
SKU: 206 - CID: O2___001 or O2___102
1.32.206.6
1.32.206.15
1.40.206.8
3.35.206.13
SKU: 771 - CID: H3G__001, H3G__106, H3G__402 or H3G__G04
1.32.771.15
3.35.771.12
SKU: 61 - CID: ORANG001
4.19.61.1
SKU: 73 - CID: ORANG202
3.35.73.14 (MD5: 1d829788af3fa566a4aab70cc547707b)
SKU: 841 - CID: TELST001
2.9.841.5
4.23.841.1
codename: hima_ul / hima_ulatt - MID: 0PJA11000
SKU: 617 - CID: BS_US001 or BS_US002
1.32.617.6
1.32.617.30
2.11.617.15
3.35.617.12
3.35.617.16
3.35.617.21
3.35.617.31
4.16.617.6
4.19.617.1
4.23.617.1
4.27.617.2
4.30.617.2
4.30.617.12
SKU: 502 - CID: CWS__001
1.32.502.9
1.32.502.31
2.6.502.16
2.11.502.18
3.38.502.41
4.27.502.7
SKU: 599 - CID: HTC__332
2.11.599.21
SKU: 600 - CID: HTC__332
1.27.600.1
SKU: 631 - CID: ROGER001
3.38.631.2
SKU: 661 - CID: TELUS001
2.11.661.2
3.40.661.2
SKU: 1500 - CID: GLOBA001
3.38.1500.2
SKU: 1530 - CID: VIDEO001
2.11.1530.180
codename: hima_ul / hima_ultmus - MID: 0PJA12000
SKU: 531 - CID: TMOB010
3.39.531.12
3.39.531.41
4.27.531.6
codename: hima_uhl - MID: 0PJA13000
SKU: 425 - CID: HTC__058 or HTC__059
2.11.425.6
CDMA RUUs
codename: hima_whl - MID: 0PJA20000
SKU: 651 - CID: SPCS_001
2.11.651.19
3.41.651.41
4.27.651.4
SKU: 510 - CID: ACG__001
2.11.510.16
codename: hima_wl - MID: 0PJA30000
SKU: 605 - CID: VZW__001
3.10.605.7
SKU: 512 - CID: LRA__001
2.6.512.14
Other RUU Collections
Some more (but older) RUUs can be found on AndroidRUU
Take me back to the Overview
Take me back to the Overview
Common RUU Errors
This List is based on 5m4r7ph0n36uru's list in his HTC 10 De-branding guide. I only changed some phrasings so most credits go to him.
07 RU_CID_FAIL: Your phone’s CID doesn't match the one that the RUU expects (c.f. its android-info.txt).
10 RU_MODELID_FAIL: Your phone’s MID doesn't match the one that the RUU expects (c.f. its android-info.txt). You might be trying to flash a RUU for a completely different device if you face this problem.
12 SIGNATURE FAIL: The phone expects an HTC signature and can't find one or found a wrong one. This error occurs if you try to flash a RUU that uses a different encryption key than the one your phone is using (e.g. firmware 3.x and older vs. 4.x).
22 RU_HEADER_ERROR: Something is wrong with your *.zip. Check the MD5 sum of the downloaded file.
23 PARSING IMAGE FAIL: Something is wrong with the image(s) within the *.zip.
24 ANDROID-INFO FAIL: Something is wrong with android-info.txt within the *.zip.
32 HEADER ERROR: The *.zip couldn't be read and unzipped properly. This seems to be the same as error 22.
33 NOT KNOWN YET: This might indicate a hardware failure.
35 FAILED (remote: 35 RU_PARTITION_NOT_SUPPORT <PartitionName>): This means you can’t flash an image in Download Mode as it has to be done in Bootloader Mode.
41 WRONG MODEL ID: Seems to be the same as error 10.
42 WRONG CUSTOMER ID: Seems to be the same as error 07.
90 PRE-UPDATE FAIL: The RUU only flashed the aboot and you have to re-run the process immediately to flash all other partitions. HTC_fastboot auto-reboots on error 90.
99 RU_UNKOWN_FAIL terrible mishap: This error often occurs if you're using a broken SD card for the SD card method.
130 WRONG MODEL ID: Seems to be the same as error 10.
132 SIGNATURE ERROR: Seems to be the same as error 12.
155 INDICATES DIFFERENT THINGS:
You need to relock the bootloader on a device with S-ON. (This only applies to devices that are older than the M9!)
The RUU cannot be executed because your phone is S-ON and its Rom and/or Firmware version is newer than the one of the RUU.
170 CHECK USB: The RUU won’t run because ADB isn't working properly.
171 USB ERROR: This can happen when a RUU reboots the phone to Download Mode. For some reasons the device is losing its connection making a RUU flash virtually impossible. There is an incompatibility between USB 3/3.1 and Fastboot/ADB, as well as an issue with the Windows Device Detection on some Windows 10 builds. (According to Sneakyghost, there seems to be a fix for this, though.)
255: This error often occurs if you're using a broken SD card for the SD card method.
Take me back to the Overview
Take me back to the Overview
TWRP Backup Section IGeneral Infos:
TWRP Backups can be used for getting back to stock if there is no RUU availabe you could use for the same purpose.
However, the TWRP Backup needs to contain the Boot Image, the Stock Recovery and a System Image that has never been mounted as read/write. If a backup only contains the needed Boot Image and the System Image you'll need to reflash the Stock Recovery manually, afterwards.
You should always check whether a RUU or a TWRP backup for your current firmware version is available before you start flashing.
If neither is available you need to create your own backup using the instructions in this post. (And hopefully you're going to upload it afterwards so that it can be shared with us. )
Important Notes:
Check whether we already have a backup for your current firmware in TWRP section II before you start uploading your own. Otherwise, you might waste your time since there is no need for more than one publicly available backup per firmware version.
Instructions:
Windows 7/8.0/8.1/10 is required.
You need an unlocked bootloader. Aside from that the M9 needs to be completely stock.
The instructions only work on firmware version 3.x or 4.x. Older firmware versions aren't able to boot to TWRP without flashing it in Download Mode.
The latest 7-zip version is needed.
The offical TWRP 3.2.2-0 version is needed.
An exfat-formatted SD card for your phone (at least 8 GB) is needed, as well. Use your PC for formatting.
A working ADB/Fastboot/HTC_Fastboot environment is mandatory.
Connect your M9 with your PC using a USB cable.
Boot to Bootloader Mode. NOT Download Mode.
That means: Power off the device, wait some seconds and turn it on again while you keep both volume buttons pressed until you see a white screen with multicoloured text. If you see a black screen with red, blue and yellow text then you're facing the download mode. In that case you can navigate to "reboot to bootloader" with the volume keys and select the option with the power button.
Open the folder that contains your ADB/fastboot/HTC_fastboot files on your PC.
Press and hold Shift on your keyboard.
Right-click into the folder.
Choose "open command window here".
If you're using the Win 10 Creator's update or any newer version then you need to choose "open powershell window here".
Type "start cmd" without the quotation marks and execute the command with pressing Enter on your keyboard.
Use the command
Code:
fastboot boot twrp-3.2.2-0-hima.img
(execute it with Enter on your keyboard).
Wait a bit. TWRP should boot on your M9 after some minutes.
DO NOT SWIPE! Choose "keep system mount read-only".
Open the Backup menu.
Backup "Boot", "System Image" and "Recovery" on the external SD card.
Copy the Backup (the whole folder - not only the files inside of the folder) to your PC.
Rename the Backup folder according to the firmware version of your phone. Example: Stock_Backup_4.14.401.7
Righ-click onto the Backup folder.
Choose "7-zip>add to an archive".
Choose "ok".
Upload the archive to a free filehoster like AFH.
AFH is recommended since it's free and states the MD5 sum of the uploaded files. This way you can check whether the file got damaged during the upload or not. In addition, others can verify whether the file got damaged during their download.
Post the download link here in this thread.
Take me back to the Overview
Take me back to the Overview
TWRP Backup Section II
Important Notes:
These Instructions got originally written for my Google sheet and my own backups. However, they can be used with every TWRP Backup that contains a System Image that has never been mounted as read/write, the corresponding Boot Image and the corresponding Stock Recovery.
If a backup lacks the corresponding Stock Recovery you might need to flash it manually.
On the other hand, if you want to keep TWRP you mustn't restore "Recovery".
Be aware that it's possible to flash OTAs with TWRP if you are at least on firmware 3.x and using at least the official TWRP version 3.1.0-0. For more information read the OTA section.
If you can't fulfill these two requirements you need to restore the Stock Recovery and an untouched System Image (e.g. with the instructions in this post) for being able to receive/install OTAs. Otherwise any Update will fail since Google introduced Block-based OTAs with android 5.
Instructions:
Be aware that you need an external SD card for your phone. In contrast to the RUU method, there is no size limit for the card if you want to restore a Backup.
There is no need to lock or re-lock the bootloader if you use this method.
If you follow my instructions all your personal data will be erased so backup everything that is important (e.g. contacts, messages, pictures, etc.)!
Format your SD card with a PC to exfat and put it back into your phone.
Boot to TWRP.
Create a backup on your external SD card.
Backing up "Boot" is more than enough. We only want TWRP to create the needed directories on your SD card.
Download the correct backup for your firmware version.
Boot to Download Mode. It is stated in the line with "OS" at the beginning. The "firmware version" in "settings>about>software information>more" is only the base of the (custom) rom you are running.
In contrast to RUUs, you mustn't use TWRP backups that are newer than your current firmware.
Unzip the downloaded backup.
Copy the unzipped backup folder to "TWRP/BACKUPS/<YourSerialnumber>/"on your SD card.
Sometimes this is only possible if the SD card is directly connected to your PC and not put into your phone. I don't know why some M9s refuse the copy process.
I recommend wiping everything except "Micro SDcard", "USB-OTG" and "SD-Ext".
Check the "Mount system as read-only" box in the Mount menu.
Restore the backup.
Boot to system (ignore the warning that no OS is installed). This process may actually take a while!
Congrats! Your system is now stock and able to receive and install official OTAs, again.
Download Links:
Sidenote: The SKU is part of your firmware version and located between the second and the third dot. Example: If 3.35.401.12 is your current firmware then you need to look for Backups with SKU 401.
GSM Backups
codename: hima_uhl - MID: 0PJA10000
SKU: 401 - CID: HTC__001, HTC__J15, HTC__102, HTC__Y13, HTC__A07, HTC__032, HTC__016, HTC__M27, HTC__002 or HTC__031
1.32.401.8
1.32.401.15
1.32.401.17
1.40.401.8 (Alternative Backup)
2.10.401.1 (Alternative Backup #1)
2.10.401.180
3.35.401.12 (Alternative Backup #1)
4.14.401.7
4.28.401.3
SKU: 708 - CID: HTC__622 or HTC__044
1.32.708.15
2.11.708.27 (Alternative Backup #1)
3.42.708.3
SKU: 709 - CID: HTC__621
2.10.709.1
3.36.709.3
4.16.709.3
SKU: 710 - CID: HTC__039, TELNZ001, OPTUS001 or VODAP021
4.23.710.1
SKU: 111 - CID: T-MOB101
1.32.111.15
2.10.111.6
3.35.111.14
SKU: 161 - CID: VODAP001, VODAP102, VODAP304, VODAP405, VODAPE17 or VODAPD18
1.32.161.7
2.10.161.7
2.10.161.180
3.35.161.12
4.17.161.11
SKU: 206 - CID: O2___001 or O2___102
2.10.206.2
2.10.206.180
3.35.206.13
SKU: 771 - CID: H3G__001, H3G__106, H3G__402 or H3G__G04
3.35.771.12
SKU: 73 - CID: ORANG202
1.40.73.3
2.10.73.3
3.35.73.14
SKU: 75 - CID: ORANG309
1.32.75.15
2.10.75.2
3.35.75.14
SKU: 1020 - CID: HTC__247
1.32.1020.15
1.40.1020.8
2.10.1020.2
3.35.1020.12
codename: hima_ul / hima_ulatt - MID: 0PJA11000
SKU: 617 - CID: BS_US001 or BS_US002
2.11.617.15
3.35.617.12
4.27.617.2
SKU: 502 - CID: CWS__001
2.6.502.18
codename: hima_ul / hima_ultmus - MID: 0PJA12000
SKU: 531 - CID: TMOB010
4.27.531.6
codename: hima_uhl - MID: 0PJA13000
none contributed to this thread, so far
CDMA Backups
codename: hima_whl - MID: 0PJA20000
none contributed to this thread, so far
codename: hima_wl - MID: 0PJA30000
none contributed to this thread, so far
Other Backup Collections
Back to Stock Files for Canadian Users
Take me back to the Overview
Take me back to the Overview
Stock Recovery SectionImportant Notes:
Things you might know from older HTC devices don't apply to the M9 since google introduced Block-based OTAs with android 5.
In other words: You can't install OTAs if you simply un-root and re-flash the Stock Recovery of your current firmware. Further information can be found in the OTA section.
Many of the TWRP Backups in this thread already contain the corresponding Stock Recovery.
However, if you need to restore a Backup that lacks the Stock Recovery you can use the instructions in this post for restoring/flashing it. It doesn't matter which method you choose.
Use the Universal Decryption Tool if you want to extract a Stock Recovery from a RUU.zip or a RUU.exe file.
Instructions for flashing the Stock Recovery via TWRP:
You'll need an external SD card. There is no size limit and it doesn't matter whether the card is formatted to fat32 or exfat.
Boot to TWRP.
Download the correct Stock Recovery for your firmware version.
Boot to Download Mode. The firmware version is stated in the line with "OS" at the beginning. The "firmware version" in "settings>about>software information>more" is only the base of the (custom) rom you are running.
Copy the Stock Recovery to the root/main directory on your SD card.
Sometimes this is only possible if the SD card is directly connected to your PC and not put into your phone. I don't know why some M9s refuse the copy process.
Choose "Install" in the TWRP main menu.
Choose "Install Image" at the bottom of the screen.
Choose the Stock Recovery and install it by swiping the slider.
Congrats! TWRP will be replaced with the Stock Recovery as soon as you reboot your device.
Instructions for restoring the Stock Recovery via TWRP:
You'll need an external SD card. There is no size limit and it doesn't matter whether the card is formatted to fat32 or exfat.
Step 2 can be skipped if the directories already exist on your SD card.
Boot to TWRP.
Create a backup on your external SD card.
Backing up "Boot" is more than enough. We only want TWRP to create the needed directories on your SD card.
Create a folder on your desktop and rename it to "Stock Recovery".
Download the correct Stock Recovery for your firmware version and copy it into the "Stock Recovery" folder.
Boot to Download Mode. The firmware version is stated in the line with "OS" at the beginning. The "firmware version" in "settings>about>software information>more" is only the base of the (custom) rom you are running.
Rename the Stock Recovery to "recovery.emmc.win". (Make sure that file extensions are visible so that you don't rename the file to "recovery.emmc.win.img"!)
Copy the "Stock Recovery" folder to "TWRP/BACKUPS/<YourSerialnumber>/" on your SD card.
Sometimes this is only possible if the SD card is directly connected to your PC and not put into your phone. I don't know why some M9s refuse the copy process.
Restore the Stock Recovery.
Congrats! TWRP will be replaced with the Stock Recovery as soon as you reboot your device.
Instructions for flashing the Stock Recovery via Fastboot:
A working ADB/Fastboot/HTC_Fastboot environment is mandatory.
Download the correct Stock Recovery for your firmware version.
Boot to Download Mode. The firmware version is stated in the line with "OS" at the beginning. The "firmware version" in "settings>about>software information>more" is only the base of the (custom) rom you are running.
Copy the Stock Recovery into the folder that contains your ADB/fastboot/HTC_fastboot files on your PC.
Boot to Download Mode.
That means: Power off the phone, wait some seconds and turn it on again while you keep volume down pressed until you see a black screen with red, blue and yellow text. If you see a white screen with multicoloured text then you're facing the Bootloader mode. In that case you can navigate to "Boot to Download Mode" with the volume keys and select the option with the power button.
Connect your phone with your PC via a USB cable.
Press and hold Shift on your keyboard.
Right-click into the folder that contains your ADB/fastboot/HTC_fastboot files.
Choose "open command window here".
If you're using the Win 10 Creator's update or any newer version then you need to choose "open powershell window here".
Type "start cmd" without the quotation marks and execute the command with pressing Enter on your keyboard.
Copy'n'paste the command
Code:
fastboot flash recovery <enter name of the Stock Recovery here>
and execute it with Enter on your keyboard.
Example for the European 3.35.401.12 Recovery:
Code:
fastboot flash recovery 3.35.401.12-recovery-signed.img
Congrats! TWRP got replaced with the Stock Recovery.
Download Links:
Sidenote: The SKU is part of your firmware version and located between the second and the third dot. Example: If 3.35.401.12 is your current firmware then you need to look for Recoveries with SKU 401.
GSM Stock Recoveries
codename: hima_uhl - MID: 0PJA10000
SKU: 401 - CID: HTC__001, HTC__J15, HTC__102, HTC__Y13, HTC__A07, HTC__032, HTC__016, HTC__M27, HTC__002 or HTC__031
1.32.401.8
1.32.401.15
1.32.401.17
2.10.401.1
3.35.401.12
3.35.401.32
4.14.401.7
4.28.401.3 (MD5: 7673341F17568DDA0810C1CA68D580CB)
SKU: 708 - CID: HTC__622 or HTC__044
2.11.708.27
3.42.708.2
SKU: 709 - CID: HTC__621
3.36.709.3
SKU: 710 - CID: HTC__039, TELNZ001, OPTUS001 or VODAP021
4.23.710.1
SKU: 111 - CID: T-MOB101
1.32.111.6
1.32.111.15
3.35.111.14
SKU: 161 - CID: VODAP001, VODAP102, VODAP304, VODAP405, VODAPE17 or VODAPD18
1.32.161.7
1.32.161.15
2.10.161.7
3.35.161.12
4.17.161.11
SKU: 206 - CID: O2___001 or O2___102
1.32.206.6
2.10.206.2
3.35.206.13
SKU: 73 - CID: ORANG202
3.35.73.14 (MD5: 1c141f3d906ea535b9682cc73889615c)
4.23.73.1 (MD5: 819514486aca4101725ccedf1c501908)
codename: hima_ul / hima_ulatt - MID: 0PJA11000
SKU: 617 - CID: BS_US001 or BS_US002
1.32.617.6
1.32.617.30
2.8.617.4
3.35.617.12
4.14.617.6
4.19.617.1 (MD5: 49B8AA1F027E32B3615B44E492E94F9B)
4.23.617.1 (MD5: E1AFEA5C70BA0C7B5FC3C15F860BE0C6)
4.27.617.2 (MD5: 06750D1CD2F17ADE1567DCA9AB5DFD8C)
SKU: 502 - CID: CWS__001
1.32.502.31
3.38.502.17
codename: hima_ul / hima_ultmus - MID: 0PJA12000
none contributed to this thread, so far
codename: hima_uhl - MID: 0PJA13000
none contributed to this thread, so far
CDMA Stock Recoveries
codename: hima_whl - MID: 0PJA20000
none contributed to this thread, so far
codename: hima_wl - MID: 0PJA30000
none contributed to this thread, so far
Take me back to the Overview
Take me back to the Overview
OTA SectionGeneral Infos:
The OTAs (Over The Air Updates) in this section are *.zip archives provided by HTC which are needed for updating the stock rom and the firmware of your HTC One M9. Normally you would download them via "settings>about>software updates".
OTAs are incremental. That means you can't directly update to the latest firmware if your phone is two or more versions older than the latest version. You'll need to install each update that ever got distributed.
Prerequisites for being able to install them (if you're using firmware 1.x or 2.x) are a completely unmodified System partition which has never been mounted as read/write and the corresponding Stock Recovery.
In other words: You aren't able to install an OTA if you simply un-root your phone and re-flash the Stock Recovery.
You can either restore one of the TWRP Backups or flash a RUU for restoring your System partition. Make sure that you follow the instructions in the dedicated sections.
Thanks to @nkk71 and @Captain_Throwback you can install OTAs with TWRP if you're at least using firmware 3.x and the official TWRP version 3.2.2-0.
The needed information/instructions can be found here and here.
Be aware that even on firmware 3.x and newer a completely unmodified System partition is a must-have if you want to install an OTA.
Important Notes:
It's always safer to update via "settings>about>software updates".
The worst thing that might happen in that case is that the OTA aborts. If you manually flash an OTA with S-ON and the flash fails you might end up with a non-booting phone. In addition you won't be able to use RUUs for the firmware version that has been installed on your phone before you started flashing the OTA. If you're unlucky there might not be a RUU for the newer firmware version and you can't recover your phone without having to pay for help.
Things you might know from older HTC devices don't apply to the M9 since google introduced Block-based OTAs with android 5.
If you want to contribute OTAs and don't know how to extract them you might want to check out this guide.
Although it's written for the HTC 10 its instructions can be used with the M9, as well.
Re-uploading OTA files isn't needed. Just post HTC's download link in this thread.
Be aware that there have been several reports that it's not possible to receive/install OTAs while using the SuperCID (11111111). So make sure you use a CID that corresponds to the OTA you want to install.
There is no need for (re-)locking the bootloader if you want to install OTAs. I actually discourage everyone from getting back to a (re-)locked state.
Read the warning I posted in the RUU section for further information.
Download Links:
Sidenote: The SKU is part of your firmware version and located between the second and the third dot. Example: If 3.35.401.12 is your current firmware then you need to look for OTAs with SKU 401.
GSM OTAs
codename: hima_uhl - MID: 0PJA10000
SKU: 401 - CID: HTC__001, HTC__J15, HTC__102, HTC__Y13, HTC__A07, HTC__032, HTC__016, HTC__M27, HTC__002 or HTC__031
1.32.401.6 -> 1.32.401.15
1.32.401.8 -> 1.32.401.15
1.32.401.15 -> 1.32.401.17
1.32.401.15 -> 1.40.401.8
1.40.401.8 -> 2.10.401.1
2.10.401.1 -> 2.10.401.180
2.10.401.180 -> 3.35.401.12
3.35.401.12 -> 3.35.401.32
3.35.401.32 -> 4.14.401.7
4.14.401.7 -> 4.28.401.3 (Alternative Download #1)
SKU: 708 - CID: HTC__622 or HTC__044
1.32.708.15 -> 1.40.708.9
1.40.708.9 -> 2.11.708.27
2.11.708.30 -> 2.11.708.180
2.11.708.180 -> 3.42.708.3
3.42.708.3 -> 4.27.708.3
SKU: 709 - CID: HTC__621
1.36.709.3 -> 1.40.709.4
1.40.709.4 -> 1.40.709.8
1.40.709.8 -> 2.10.709.1
2.10.709.180 -> 3.35.709.3
3.35.709.3 -> 4.16.709.3
4.16.709.3 -> 4.30.709.12
SKU: 710 - CID: HTC__039, TELNZ001, OPTUS001 or VODAP021
1.32.710.7 -> 1.32.710.16
SKU: 111 - CID: T-MOB101
3.35.111.14 -> 4.18.111.2
SKU: 161 - CID: VODAP001, VODAP102, VODAP304, VODAP405, VODAPE17 or VODAPD18
1.32.161.7 -> 1.32.161.15
1.40.161.8 -> 2.10.161.7
2.10.161.180 -> 3.35.161.12
3.35.161.12 -> 4.17.161.11
SKU: 206 - CID: O2___001 or O2___102
1.32.206.6 -> 1.32.206.15
1.40.206.8 -> 2.10.206.2
SKU: 771 - CID: H3G__001, H3G__106, H3G__402 or H3G__G04
3.35.771.12 -> 4.30.771.2
SKU: 73 - CID: ORANG202
1.32.73.6 -> 1.32.73.15
1.32.73.15 -> 1.40.73.8
1.40.73.8 -> 2.10.73.3
2.10.73.180 -> 3.35.73.14
3.35.73.14 -> 4.23.73.1 (MD5: 69636c632a5d1fa9ecc03e9f22e64e93)
SKU: 75 - CID: ORANG309
1.32.75.15 -> 1.40.75.8
1.40.75.8 -> 2.10.75.2
12.10.75.180 -> 3.35.75.14
SKU: 1020 - CID: HTC__247
1.32.1020.15 -> 1.40.1020.8
1.40.1020.8 -> 2.10.1020.2
2.10.1020.180 -> 3.35.1020.12
SKU: 841 - CID: TELST001
2.9.841.5 -> 2.10.841.200
2.10.841.200 -> 3.38.841.6
3.38.841.6 -> 4.23.841.1
codename: hima_ul /hima_ulatt - MID: 0PJA11000
SKU: 617 - CID: BS_US001 or BS_US002
1.32.617.6 -> 1.32.617.30
1.32.617.30 -> 2.8.617.4
2.8.617.4 -> 2.11.617.15
2.11.617.15 -> 2.11.617.180
3.35.617.21 -> 3.35.617.31
3.35.617.31 -> 4.14.617.6
4.14.617.6 -> 4.19.617.1
4.23.617.1 -> 4.27.617.2
SKU: 669 - CID: SASKT001
3.38.669.2 -> 4.19.669.1
codename: hima_ul / hima_ultmus - MID: 0PJA12000
none contributed to this thread, so far
codename: hima_uhl - MID: 0PJA13000
none contributed to this thread, so far
CDMA OTAs
codename: hima_whl - MID: 0PJA20000
none contributed to this thread, so far
codename: hima_wl - MID: 0PJA30000
none contributed to this thread, so far
Take me back to the Overview
Take me back to the Overview
Useful Links/Further Reading
Basics about Block-based OTAs
How to "read" Firmware versions
SKU-, CID- and MID-List by Sneakyghost and Behold_this
How to "read" Serialnumbers
The Difference between Rom and Firmware
(this is an archive.org link - the original article isn't available anymore due to the Team Venom website being shut down)
Sneakyghost's Firmware Thread
This thread actually contains a lot of useful information about the firmware, CIDs, MIDs and S-OFF - you can find Full Wipe and NoWipe firmware packs in this thread, as well
Captain_Throwback's TWRP Thread
How to recover the 3 GB internal storage that get lost while getting S-OFF
Instructions are not needed if you choose to flash a RUU after getting S-OFF
My "famous" Google sheet
Recovery Flashable Radio Files
Sunshine S-OFF
If you don't own a Java Card or an XTC Clip, this is the only method for getting S-OFF at the moment!
Llabtoofer's RUU Service
The last hope if there is no publicly available RUU you could use!
Universal HTC RUU/Rom Decryption Tool
Country-/Continent-specific threads
Australia
Canada
India
Take me back to the Overview
Take me back to the Overview
FAQ Section
Q1: Everytime I flash a custom rom/restore a TWRP backup I lose my IMEI and my mobile reception and my phone stops recognizing my sim card. What's the reason for this?
A: You probably flashed a custom rom that is based on firmware 3.35.x although the firmware of your phone is 3.y (with y being any other number than 35). The boot image of 3.35.x based roms is not compatible with your firmware version. The solution of the problem depends on the question whether you are trying to install a Sense-based rom (like ICE or ViperOneM9) or a non-Sense-based rom (like CM): For Sense-based roms you just need to re-flash the stock boot image of your current firmware version. For non-Sense-based roms you need to flash thicklizard's custom kernel. There have been some reports, that this boot.img "trick" for Sense-based roms doesn't work with firmware 4.x, anymore. In addition, you might face this problem, as well, if you flash a 3.x based rom/restore a 3.x based backup and your phone is currently using a 4.x firmware.
Q2: You mentioned the term SKU several times. What is that?
A: The SKU contains between two and four digits and is part of the firmware version (x.xx.SKU.xx). It indicates which variant of the firmware you're using. Read Sneakyghost's and Behold_this' SKU-, CID- and MID-List if you want to know the meaning of a specific SKU.
Q3: I've always been looking at the CID and the MID of my HTC phones if I wanted to know which RUU I should use. Wouldn't that be easier than booting to Download Mode and looking at the line with "OS" at the beginning?
A: No, it wouldn't. If you only know the CID and the MID you still need to guess the correct RUU. If you boot to Download Mode and look at your current firmware version you know exactly which RUU you're looking for. Just look at the naming of the RUUs and you'll find out that it contains the firmware version a RUU corresponds to.
Q4: Which versions of TWRP and SuperSU are the recommended ones?
A: The answer depends on your current firmware version. If you're using firmware 4.x then you'll find your answer here in the FAQ of the TWRP thread. (Click here, if you can't find SuperSU 2.79 SR3. Version 2.79 SR1 doesn't seem to be available, anymore.) For firmware 1.x and 2.x the recommended versions are Captain_Throwback's Beta 1 of TWRP 2.8.7.1 and SuperSU 2.49. For firmware 3.x the recommended versions are TWRP 3.2.2-0 (official) and SuperSU 2.65. Using different versions than the recommended ones will probably lead to a bootloop. The M9 isn't compatible with the ramdisk changes that get executed by many flashable system-less SuperSU versions. However, updating the SuperSU app and its binaries via the Play Store after flashing one of the older versions is safe.
Q5: Are there alternative methods for gaining root?
A: Yes, you can use Magisk if you're using firmware 4.x. (Maybe a user with a lower firmware version can test whether Magisk is usable on firmware 1.x to 3.x, as well?)
Q6: I ignored Q4 and now my phone is bootlooping. How can I fix it?
A: You need to reflash the stock boot.img of your current firmware. If a backup for your version is available in this thread or if you made your own backup before flashing SuperSU you can use the instructions in TWRP section II for that purpose. Be aware that you don't need to wipe anything and that restoring "Boot" is sufficent. If this thread lacks a backup for your version and you didn't backup your stock system, either, you'll need to flash a RUU. If neither a backup nor a RUU are available you'll need to contact Llabtoofer's RUU Service.
Q7: I tried to unzip the RUU.zip files that you linked here and got an error! Looks like they're broken! Re-upload them!
A: Strictly speaking, this is not a question. However, such a situation happened that often that I have to add this point to the FAQ, as well. The RUUs are not broken. They are encrypted and not meant to get unzipped. Most unzipping programs can't open them due to the encryption. Use the Decryption Tool if you want to get one of the firmware files that are located in a specific RUU.
Q8: My Dowloand Mode is broken. How can I fix it?
A: The answer is a bit tricky. There seem to be two different states of a broken Download Mode: a Bluescreen and a black one with the red failed to boot to download mode. In addition to the black error screen, the bootloader shows a security warning and that the software status is modified if you boot to the Bootloader. According to this post you can recover the Bluescreen if you have S-OFF. However, users reported that they could flash the files with S-ON, as well. Nevertheless, I've never faced such a situation with my own M9 and therefore can't say who's right and who isn't. On the other hand, the black screen seems to be caused by a broken EMMC. (Remember that the M9 uses the SD810 processor which runs quite hot depending on your usage. All models from all OEMs that use this processor suffer from the hardware damages that result from the heat.) I therefore doubt that this variant of the broken Download Mode can get recovered without HTC's help. In other words: If you face this so called "dead nand issue" you need to send your phone to HTC's repair service if you want to keep it.
Q9: Whenever I connect my phone via USB with my PC it gets recognised as HS-USB QDLoader. How can I fix that?
A: Looks like you hardbricked your phone. This state already existed on older HTC phones. You need a JTAG device (like a RIFF Box) and the knowledge for using it if you want to recover your phone. I have neither. However, you can find further information in the fifth post of Sneakyghost's firmware thread.
Q10: I flashed a custom rom. TWRP stated the flash was successful but the rom doesn't boot. What's wrong?
A: This can happen if your phone's firmware is outdated. Get back to stock and install all available OTAs. You can flash a newer RUU (if one with a newer firmware version of your phone's SKU is available) for saving some time that would otherwise be needed for installing OTAs. Further information can be found in the RUU section.
Q11: I bought a M9 and I have no clue which variant it is. Is there a way for finding out the (original) MID whithout having to use a PC?
A: Yes, there is. Look at the bottom of the backside of your M9. There is a small engraving: Model 0PJA***. The part with the *** differs according to the variant you own. The explanation for the MIDs can be found in the opening post of this thread. Be aware that the MIDs from fastboot getvar (which I used in the opening post) have two additional zeros in comparison with the engraving. In addition, the MID from fastboot getvar may differ completeley from the engraving if the phone got converted to a different version.
Unfortunately, more and more people tend to replace the housing of their phone since the original one got damaged. The problem is that those people don't care whether the replacement housing got made for the variant they own or not. This leads to so called frankenphones which consist of parts that originally belonged to more than one variant of the One M9 (e.g. a hima_whl phone in a housing with the 0PJA100 engraving of the hima_uhl variant).
Q12: I try to enter the Stock Recovery but all I see is a red triangle and then my phone reboots. Is my phone broken?
A: No it isn't. That triangle is the Stock Recovery. HTC added this auto-reboot as a security feature so that you don't accidently factory-reset your phone. As soon as you choose "Reboot to Recovery Mode" you need to press and hold the power button. When you see the triangle you need to shortly press volume up while the power button is still pressed. The recovery's menu should appear now.
Q13: Your opening post states that the Verizon and the Sprint variants are CDMA devices. However, mine is using a SIM card so it must be a GSM device, correct?
A: No, it's still a CDMA device and as mentioned before, flashing a GSM RUU/firmware on a CDMA device may lead to unrecoverable damages. You need to be aware of the fact, that LTE is a GSM technology. Therefore, CDMA devices/carriers need to support some LTE-GSM frequencies and SIM cards if they want support LTE connections. Nevertheless, most slower connections are still based on the CDMA network of Verizon/Sprint.
Since CDMA networks are only available in the US, many people who need(ed) to travel to other countries preferred to buy GSM devices so that they are/were still able to use their phones abroad. To circumvent this loss of customers CDMA carriers started to support some GSM frequencies for G and 3G connections with their phones. That's why you might be able to use a CDMA M9 on some GSM networks but that neither means that it can be used on any GSM network nor that you can get LTE on any other network than the one that belongs to the branding of the phone.
Q14: I'm trying to install an OTA via the software update function but after ca. 25 % I see a read triangle with an exclamation mark and the update aborts. Why is this happening and what can I do?
A: That's the stock recovery and normally you shouldn't see that triangle during an update. If you do then your system partition isn't passing the security checks of the update. In other words your system partition isn't untouched but modified. You need to restore an untouched system partition for solving this problem. This can either be achieved by flashing a RUU or restoring a TWRP backup. If you never modified your phone and didn't buy it second-hand then this problem might be a precursor of the NAND death (c.f. the black download mode error screen in Q8).
Q15: My phone is modified and started bootlooping during normal usage. When I enter TWRP and try to wipe the phone or to re-flash the rom I'm currently using I face a lot of mounting errors. How can I fix this problem?
A: This seems to be another symptom of the NAND death (c.f. the black download mode error screen in Q8) even if you might still be able to access the Download Mode in this case. So far, it's not fixable without HTC's help. In other words: You need to send your phone to HTC's repair service if you want to keep it.
Q16: My phone is completely stock and during normal usage many/all apps started crashing (often but not always) followed by a bootloop. Now I can only enter the Bootloader since I face booting errors as soon as I try to enter the Download Mode or the Stock Recovery. How can I fix this problem?
A: This seems to be another symptom of the NAND death (c.f. the black download mode error screen in Q8). You might face a security warning while being booted to the Bootloader and the Software Status might be modified although you never tinkered with your phone in regard to rooting and/or custom roms. So far, it's not fixable without HTC's help. In other words: You need to send your phone to HTC's repair service if you want to keep it.
Q17: So I'm facing that dead nand issue and don't want to believe that there's nothing I can do in regard to a DIY repair. What are you hiding from us? There must be something I can do.
A: Believe it or not, there's nothing you can do, so far. Some users already said that they're going to buy spare parts and to repair the phone on their own. None of them reported back that they were successful. You have to accept that (at this moment) only HTC's repair service can fix your phone or that you need to buy a new one. If there was a working guide then it would be linked in this thread.
Q18: The ADB/Fastboot/HTC_Fastboot files you linked aren't working. Every time I try to "open" them via double-clicking on them they immediately close after some seconds. Fix them!
A: Strictly speaking, this is not a question, either. However, some seem to be not aware that not every *.exe file can be "opened" via double-clicking on it. You need to use ADB/Fastboot/HTC_Fastboot via a command window (c.f. the instructions in the sections on page 1).
Q19: I couldn't find a RUU or a TWRP backup in this thread that are flashable on my phone. What shall I do now?
A: You have two choices (none of them is for free). If you choose the second one you could help the community a lot by re-uploading the RUU on AFH.
Use Llabtoofer's RUU Service
Try to find a suitable RUU on websites that leak them (e.g. easy-firmware)
Q20: I urgently need the hosd.img for my phone. Where can I find it?
A: Download the correct RUU for your phone (c.f. step 1 of the guides in the RUU section). The hosd.img can get extracted from the RUU with the help of the Universal RUU Decryption Tool.
Q21: My phone is bootlooping and keeping the power button pressed for 10 seconds doesn't fix the situation. Am I lost?
A: No, HTC changed the button combo on one of the devices that are older than the M9. (Most probably due to the outrage of users that accidently rebooted their phone with the old key combo while simply carrying their phone in their pocket.) You need to keep the power button and the volume up button pressed for about 30 seconds.
Feel free to post a question in this thread if anything is still unclear after you read the all posts from the OP to this one.
Feel free to write a post as well if you know a common problem (and its solution) that should be added to this FAQ, too.
Take me back to the Overview
Take me back to the Overview
Credits (in alphabetical order)
Contributors - many thanks to all of you
alfredomorenoperez
Alternate_DM
Artume
Asselalf
Baalzaman
barashe
BiOMeX
Black-FR
buttie
Charwinger21
clsA
computerslayer
coolberry
cporeaux
Fain11
Golv
Handy-FAQ.de
h3ct0rx
hyperair
ivendor
jamieunit
k1ll3r8e
Krocko
lama81
lazyguyMC
mattlovell90
MegaGalan
migascalp
Mutasek24
Nima78600
nkk71
osiedacz
RikuXander
sardroid
sblonci65
stjepa90
SoLdieR9312
stifilz
Team Renovate
TechnicianX
warci
xunus
YANGHY
ziand_
Special Thanks to
aestivalisakito - for providing the Recovery flashable Radio files and the guide for recovering the whole internal storage after getting S-OFF
Asselalf, Krocko & warci - for the short but fun time we've been working together and all their little tips and advices
Behold_this - for the SKU, CID and MID list
beaups & jcase - for bringing some "Sunshine" into our lives
buko_s - for reminding me of the correct key combination that's needed for entering the stock recovery
Captain_Throwback - for his informative TWRP Thread, the RUU extraction tool and the instructions for installing OTAs with TWRP
Chainfire - for SuperSU
clsA - for his conversion guides
exocetdj - for starting the original Stock File Collection thread
fhartane - for confirming that downgrading with S-ON is still possible on firmware 3.x
Golv - for the ARUWizard method
Google - for ADB and Fastboot
HTC - for their USB drivers, HTC_Fastboot and HTCdev
Inside 4ndroid - for the RUU.zip extraction Guide
lizard2k5 - for the solution for the Blue Screen error
Llabtoofer - for his informative article about serialnumbers and his RUU Service
mike1986 - for his informative article about firmware versions
Nikolay82 - for the ARUWizard method
nkk71 - for the RUU extraction tool and making it possible to install OTAs with TWRP - Rest in Peace, mate!
nleitao - for confirming that the instructions in the TWRP section I can still be used with firmware 4.x
SaHiLzZ - for maintaining the Canadian Back to Stock thread
5m4r7ph0n36uru - for the RUU error list
Sneakyghost - for his informative firmware thread, his articles and the SKU, CID and MID list
The Open GApps Project - for Open GApps
thicklizard - for his custom kernel
topjohnwu - for his OTA extraction Guide and Magisk
Take me back to the Overview
recoveries, nands and otas for worldwide cids, O2 uk and germany cids, tmobile and vodafone CIDS added to first few posts thanks to @Asselalf and the dudes mentioned above again!!
Brilliant - thanks for bringing this to the m9.
The Great Dane said:
Brilliant - thanks for bringing this to the m9.
Click to expand...
Click to collapse
Cheers mate!
OTA 1.32.401.15 --> 1.40.401.8
modelid: 0PJA10000
cidnum: HTC__001
cidnum: HTC__J15
cidnum: HTC__031
cidnum: HTC__102
cidnum: HTC__A07
cidnum: HTC__032
cidnum: HTC__M27
cidnum: HTC__016
cidnum: HTC__002
cidnum: HTC__Y13
mainver: 1.40.401.8
Click to expand...
Click to collapse
Great Work ...
Awesome ...
Reminding me of my M8 ...
Mutasek24 said:
OTA 1.32.401.15 --> 1.40.401.8
Click to expand...
Click to collapse
Bit of a noob question can I flash this zip in twrp?
This is version on at moment.
C:\adb>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei: ****
(bootloader) version-main: 1.32.401.15
(bootloader) boot-mode: download
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__001
all:
finished. total time: 0.016s
Sent from my HTC One M9 using XDA Free mobile app
Hello Guys,
I have a U Ultra with a boot problem.
Failure: It starts, show up the logo for a short time, than it shut down.
In fastboot mode the lock status is relocked. Flashing in fastboot there is no chance. Because the OEM Unlock flag in the rom is off. The recovery does nothing, same behavior as on startup...
The only way to get the phone back to life is the sideload via OTA flash zip file on a sdcard.
Problem: I don't have such a file with os 2.21.410.1, I have only a 1.64.401.10 file.
If I try this file it shows me a Version Androis-Info Error.
Where can I get such a flash file with the version 2.21.401.1 with oreo (european version)?
On the other side I try to patch the info.bin file but , the version is easy to patch but it seems so that this file has a byte in front, that changed in a unknown way and 8 bytes in the middle of the file with the same problem, this could be a file size or checksum I don't know what it is and how it will be generated. The rest of the file is filled with zeroes.
Does somebody have information about the file structure of the info.bin in the flash file?
I heared about LeeDrOiD, that he worked a long time for HTC, maybe he could help to get this phone back to life????
Phone Info:
C:\ADB>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_oceuhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1578400000
(bootloader) serialno: ************
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) imei: ***************
(bootloader) version-main: 2.21.401.1
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PZF10000
(bootloader) cid: HTC__034
Hope someone can help me...
davii
good/bad news
hi guys,
I run thru the infos from an other post here in the forum and that I have done successfully.
https://forum.xda-developers.com/u-ultra/help/howto-unbrick-ultra-t3891033
The behaviour is now a bit different, it runs now in a boot loop, the logo has change to the normal htc logo without red text. The recovery shows a red exclamation mark, and run in the bootloop...
The main problem remains, I need a 2.21.401.1 firmware file to flash on the phone... what a m....
I can't find such a file in the internet, the exe firmaware files end up on version 1.64... and I think, this are only us version files. I need HTC__034.
Any ideas?
Is it possible to patch a lower version of a firmware rom just to get the phone running, to open the OEM unlock, and than to flash whatever? I have an twrp backup of my mobile.
The firmware.zip file from @minhnewpro in OTA, where does it come from? The OTA looks like a twrp or titanium backup file. But I can't get it in my mobile without twrp...
Were it possible to integrate the twrp.img in the firmware.zip file as recovery partion? Would it help at all without the open bootloader, can twrp write things with a locked bootloader? I'm not so firm in that matter... In my understanding of this matter it can???
davii
davi133 said:
hi guys,
I run thru the infos from an other post here in the forum and that I have done successfully.
https://forum.xda-developers.com/u-ultra/help/howto-unbrick-ultra-t3891033
The behaviour is now a bit different, it runs now in a boot loop, the logo has change to the normal htc logo without red text. The recovery shows a red exclamation mark, and run in the bootloop...
The main problem remains, I need a 2.21.401.1 firmware file to flash on the phone... what a m....
I can't find such a file in the internet, the exe firmaware files end up on version 1.64... and I think, this are only us version files. I need HTC__034.
Any ideas?
Is it possible to patch a lower version of a firmware rom just to get the phone running, to open the OEM unlock, and than to flash whatever? I have an twrp backup of my mobile.
The firmware.zip file from @minhnewpro in OTA, where does it come from? The OTA looks like a twrp or titanium backup file. But I can't get it in my mobile without twrp...
Were it possible to integrate the twrp.img in the firmware.zip file as recovery partion? Would it help at all without the open bootloader, can twrp write things with a locked bootloader? I'm not so firm in that matter... In my understanding of this matter it can???
davii
Click to expand...
Click to collapse
Well, i used to have U Ultra and now it is dead =] and i can not do anything (Hardware problem), even i tried flash RUU by CMD or SD Card.
Back to your question. Maybe you only can try to boot into DOWNLOAD MODE => Bootloader => recovery => apply ota update.zip
minhnewpro said:
Well, i used to have U Ultra and now it is dead =] and i can not do anything (Hardware problem), even i tried flash RUU by CMD or SD Card.
Back to your question. Maybe you only can try to boot into DOWNLOAD MODE => Bootloader => recovery => apply ota update.zip
Click to expand...
Click to collapse
Thx dude,
I'm already on 2.21.401.1, there is no update for 2.21.401.1 in the net, no chance to flash a stock rom... :crying:
davi133 said:
Thx dude,
I'm already on 2.21.401.1, there is no update for 2.21.401.1 in the net, no chance to flash a stock rom... :crying:
Click to expand...
Click to collapse
hey guys, I have another idea...
my wifes mobile is the same..., and that mobile is on 1.64...,
were it possible to initiate the update on 2.21..., and then it downloads the update file. Where resides this update file? Can I get this file from my wifes mobile, to flash it on my mobile?
Does anybodey know this?
In my opinion this process is the same as the RUU flash, the file must be on a special partition, I think, then the mobile goes into RUU flash mode, and the command are fired to flash this rom, thats what I think...
davii
davi133 said:
Thx dude,
I'm already on 2.21.401.1, there is no update for 2.21.401.1 in the net, no chance to flash a stock rom... :crying:
Click to expand...
Click to collapse
Try to reflash OTA.zip by using stock recovery, maybe it will works.
minhnewpro said:
Try to reflash OTA.zip by using stock recovery, maybe it will works.
Click to expand...
Click to collapse
the recovery don't comes up, it also hangs in a bootloop. Or do you mean something different?
I can go to the fastboot mode, or in the bootmode for recovery, that dosen't help, I have no OTA with 2.21.401.1, that I could flash, just a lower version (1.64.401.10), that will be rejected by the RUU flash in because of the wrong version. To change the version in the bootloader I need a open bootload and a running os with adb, all that isn't the case.
I need OTA flashable rom with the 2.21.401.1 version to run it with RUU flash, and if this works is will work, that is the next question..., I think and hope it will work...
Why does the recovery didn't comes up, maybe that is the same problem as in the boot situation, the dead boot.img or a corrupted os, I don't know the reason, my last flash was a LeDrOiD, the boot.img maybe does no fit the original boot process. On the other hand, LeDrOiD was also an Oreo rom, as I had a problem with my magisk update I put back my original boot.img from my mobile backup, and my mobile boots up normaly, then I flashed back the LeDrOiD system things and it boots up normaly and magisk was fine.
I don't know whats wrong, why the recovery was gone, why the boot.img dosen't work and so on...
where resides the recovery.img? In the same partition as the boot partition or on its own partition?
Any other ideas?
davi133 said:
the recovery don't comes up, it also hangs in a bootloop. Or do you mean something different?
I can go to the fastboot mode, or in the bootmode for recovery, that dosen't help, I have no OTA with 2.21.401.1, that I could flash, just a lower version (1.64.401.10), that will be rejected by the RUU flash in because of the wrong version. To change the version in the bootloader I need a open bootload and a running os with adb, all that isn't the case.
I need OTA flashable rom with the 2.21.401.1 version to run it with RUU flash, and if this works is will work, that is the next question..., I think and hope it will work...
Why does the recovery didn't comes up, maybe that is the same problem as in the boot situation, the dead boot.img or a corrupted os, I don't know the reason, my last flash was a LeDrOiD, the boot.img maybe does no fit the original boot process. On the other hand, LeDrOiD was also an Oreo rom, as I had a problem with my magisk update I put back my original boot.img from my mobile backup, and my mobile boots up normaly, then I flashed back the LeDrOiD system things and it boots up normaly and magisk was fine.
I don't know whats wrong, why the recovery was gone, why the boot.img dosen't work and so on...
where resides the recovery.img? In the same partition as the boot partition or on its own partition?
Any other ideas?
Click to expand...
Click to collapse
Try extract recovery from ota.zip file and flash in download mode.
minhnewpro said:
Try to reflash OTA.zip by using stock recovery, maybe it will works.
Click to expand...
Click to collapse
hey dude,
please don't be serious but have you read my starting thread?
The bootloader is locked, you can't flash anything with fastboot! The only way to flash something is over RUU flash, so I'm a bit confused about your proposals :angel:
I hope I don't missunderstand things, because you are a senior member, and I do not want to upset anyone.
There is no OTA on the mobile so that the recovery can do it's job.
Wich OTA you mean? The real OTA from HTC look like:
OZA.zip
info.bin
zip_0.zip
zip_1.zip
etc...
Your and the other OTA's look like this:
OTA.zip
[dir] META-INF
[dir] preload
contexts.bin
etc....
Your OTA's are flashable from twrp, made with (I don't know, titanium backup)
A RUU flash want me to pass a real HTC OTA with a version higher or equal to that version that is installed before...
I know, there is a possibility to extract your OTA's but what is it good for? fastboot can't flash the recovery.img because the bootloader is locked.
That's my actual understanding of this matter and that's the behavior of the mobile.
If I'm wrong with something, please let me know.
davi133
new information on my side
The recovery comes up with these special key's (wait for the red exclamation, press power + VolUp).
Ok, but the information from htc support "WIPE DATA/FACTORY RESET" leads also to no success. Everything was made fine but after reboot is the bootloop.
The new menu in the recovery offers me to flash a real OTA from a ADB process or a SDcard, hmm, ok there is controled way now for doing this but I tryed all may real OTA's without success, because of the lower version or false cid's.
I asked the support for an actual OTA update file, but I dont think that they will give me that file.
The ADB process is a very restricted version of ADB, that mean's you can't get a shell or something like that, just the sideload and print some variables...
Is it possible to extract the real OTA, change something, and repack it?
davi133
davi133 said:
The recovery comes up with these special key's (wait for the red exclamation, press power + VolUp).
Ok, but the information from htc support "WIPE DATA/FACTORY RESET" leads also to no success. Everything was made fine but after reboot is the bootloop.
The new menu in the recovery offers me to flash a real OTA from a ADB process or a SDcard, hmm, ok there is controled way now for doing this but I tryed all may real OTA's without success, because of the lower version or false cid's.
I asked the support for an actual OTA update file, but I dont think that they will give me that file.
The ADB process is a very restricted version of ADB, that mean's you can't get a shell or something like that, just the sideload and print some variables...
Is it possible to extract the real OTA, change something, and repack it?
davi133
Click to expand...
Click to collapse
Hi Davi,
check this out (don't ask me what i had to do to get it... ):
2PZFIMG_OCEAN_NOT[email protected]80307_63.34_release_522808_signed_2_4
Rename the file to "2PZFIMG.zip" and place it in root of sdcard. Boot into download mode and confirm flash with volume+ button
thank you
Siluxsept said:
Hi Davi,
check this out (don't ask me what i had to do to get it... ):
2PZFIMG_OCEAN_NOT[email protected]80307_63.34_release_522808_signed_2_4
Rename the file to "2PZFIMG.zip" and place it in root of sdcard. Boot into download mode and confirm flash with volume+ button
Click to expand...
Click to collapse
been waiting for this firmware also..i will try this hope everything works
update
the flashing was succesfull on my htc ultra and its works..hope this can help also the op..
Siluxsept said:
Hi Davi,
check this out (don't ask me what i had to do to get it... ):
2PZFIMG_OCEAN_NOT[email protected]80307_63.34_release_522808_signed_2_4
Rename the file to "2PZFIMG.zip" and place it in root of sdcard. Boot into download mode and confirm flash with volume+ button
Click to expand...
Click to collapse
Thanks for this