[One (M9) General] Flippy498:
Take me back to the Overview​

RUU Section​

General 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

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:

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​