yashsingh1/xdaforums huggingface dataset:
[One (M9) General] Flippy498:
As far as I know only 617 and 401 received the update, yet. You can keep an eye on Llabtoofer's twitter account. Whenever there's an update for an HTC device rolling out you'll find a tweet about that update there.

[MENTION=7215221]Ninec[/MENTION]: Is your last post incomplete?
[One (M9) General] Ninec:
How about now ?
[One (M9) General] Flippy498:
Now I can see the attached picture. :good:

Looks like someone didn't read the RUU section carefully enough. The reason and to solution of your problem are already explained there. ;)
[One (M9) General] Ninec:
I read it several times, but I'm noob with those things and don''t know where is my mistake lol
[One (M9) General] Flippy498:
First of all you ignored this:

However, you're lucky since your problem is probably not that hard to solve:
[One (M9) General] PoetraPDW:
My OTA update via SD card instead bootloop
[One (M9) General] doomscooter:
Om Poetra, u must try via sideload.

In OTA nougat, update OTA via sdcard failed.
[One (M9) General] Ninec:
Yea m8 I try that as well following the instructions step by step, but again no result. First of all I can't unzip the fail with 7zip after that when I try to convert RUU.zip (if this is correct term) start to count some numbers and nothing happens...
[One (M9) General] Flippy498:
Which file couldn't get unzipped? The RUU.zip? As explained in the FAQ section, it's encrypted and not meant to get unzipped.

The HTC_fastboot files are linked in the part that I quoted.

Which RUU do you try to "convert"? And what do you mean with "converting"? Are you talking about extracting a RUU.zip from an *.exe?
[One (M9) General] Ninec:
I try to unzip RUU file from your Thread (4.14.401.7) and I try to extract RUU.zip (same file) to .exe, also I try with the other link "the version I'm currently using." and again there was the same result like the last one (before to upload the picture)
[One (M9) General] rukia06:
I am 401 SKU with S-OFF, and had a 4.x firmware base already.

I can confirm that installing from a samsung SD card sized 128GB worked for me just fine.

Also, as another way to get the file onto the SD, I just pushed it to my phone with ADB then moved it to the removable sd card. (i didnt see the the bit about removing the '.zip' before copying until after wards.)
[One (M9) General] Flippy498:
As said before, the RUU.zip files aren't meant to get unzipped. You can find htc_fastboot files linked in the RUU section. The extraction of them from a RUU.exe is just an alternative way to get them if you don't trust the files I uploaded. However, I'll end the discussion of fastboot problems here. This method isn't supported in this thread. Despite that, people can find more than enough information on page one if they think they need to use a method that is known to cause issues.

It's technically impossible to get a RUU.exe from a RUU.zip since the *.zip file doesn't contain the executable file. It's the other way round. All RUU.exe contain a RUU.zip and some other files (like fastboot/htc_fastboot/adb) that are needed so that the fancy installer is able to flash the RUU.zip via htc_fastboot. That's why I don't support flashing RUUs via *.exe files, either. They do nothing else than a user who tries to flash a RUU.zip with htc_fastboot commands and therefore there are the same reasons for a RUU.exe to fail as for a manual flash a of RUU.zip.
[One (M9) General] Ninec:
I understand that you don't support other methods, but when I try to do NoWipe/FullWipe with your version the result is the same like on the picture i've already post.
[One (M9) General] Flippy498:
NoWipe and FullWipe aren't methods. So you can't "do" them. Those are the names of firmware packs.

Your first error is based on the fact that the RUU is too large for the normal fastboot. Sneakyghost's firmware packs are less than 500mb big so you shouldn't face the same issue when you try to flash them. Head over to Sneakyghost's firmware tread and verify whether you followed his instructions correctly. If it still doesn't work you need to ask him whether he knows a solution.
[One (M9) General] katsuya12:
Hi

Please help to guide which ROM i should use for my HTC ONE M9. I update by RUU. exe but alway show ERROR(132).

htC download mode

*** UNLOCKED ***

htc_himaulatt PYT S-OFF

CID-11111111

MID-0JPA13000

Thank a lot.
[One (M9) General] Flippy498:
Please read the RUU section. It contains the needed information.
[One (M9) General] rhy25:
excuse me guys, pls share hosd_signed_himaul img ..need it badly for my m9 currently no download,recovery mode and with S on...plsss help me

Reading information...

Using Fastboot mode...

Reading common information

(bootloader) version:0.5

(bootloader) variant:MTP eMMC

(bootloader) secure:yes

(bootloader) version-baseband:

(bootloader) version-bootloader:

(bootloader) max-download-size:	0x20000000

(bootloader) partition-type:cache:ext4

(bootloader) partition-size:cache:	0x14000000

(bootloader) partition-type:userdata:ext4

(bootloader) partition-size:userdata:	0x5e0000000

(bootloader) partition-type:system:ext4

(bootloader) partition-size:system:	0x118000000

(bootloader) serialno:FA54GYJ00254

Execution time is 140(ms)

all:

Reading secure flag information

... (bootloader)	read secure flag: 3

Execution time is 15(ms)

OKAY

Reading CID information

Execution time is 15(ms)

... FAILunknown command

FAILED (remote: unknown command)

Reading MEID information

Execution time is 15(ms)

... FAILunknown command

FAILED (remote: unknown command)

Read information failed
[One (M9) General] Flippy498:
Download the correct RUU for your current firmware version and decrypt it with the decryption tool. The hosd.img will be located in the firmware folder.
[One (M9) General] draymond1987:
Hey guys, I am sorry for the noob question here: Basically, it's gonna be, how do I convert to developer edition ?

I haven't had an HTC device in awhile, but used HTC one and M8. I'm currently waiting for my HTC m9, which is T-mobile USA. I am gonna assume its on a 3.xx.xxx.xxxxxxxxxxxx firmware.

I have read this thread so many times, that my head hurts. It says you can't flash 4.xx.xxx over 3.xx.xxx . But the Nowipe and Fullwipe would be jumping to 4.xx.xxx, right? I am "assuming" 4.xx.xxx is Nougat? So basically, I was going to unlock, root and s-off , because that's what you do in life......S-off. I have the Developer RUU, so can't I just run the program, update all the firmwares (convert) then flash a ROM (based on developer firmware) ??

It really doesn't seem difficult, especially since I am not new to flashing ROMs and all. The thing that puts me off is, how it states that encryption changed from 3.xx.xxx to 4.xx.xxx . I'm sure OP is really current, and I don't wanna just "assume" I can S-off and flash the RUU....or can I?

I am a "crackflasher" so I am not afraid to brick, but I also read before doing anything too stupid. So I need guidance, please. Have mercy on my poor, I can't remember how to flash HTC firmwares, soul. Honestly, thank you guys for any help. When I actually get the phone, I'll have a better idea of what firmware it is running, and not assume that Nougat is 4.xx.xxx.xxxxx.xxZebra.

My cat probably understands this s**t better than I do.
[One (M9) General] Flippy498:
As written on page 1 you can't use a 4.x RUU on a 3.x firmware. Due to the different encryption keys your phone won't be able to "read" the files in the RUU. (If you owned a M8 you should have faced the same situation with the update from Android 5.1 to Android 6. Since I never owned one I can't tell you the corresponding firmware versions.) S-OFF won't change this fact since S-OFF only means that your phone doesn't check whether the files you want to flash got signed properly by HTC.

Therefore you need to update your phone with the help of unencrypted files. (Especially since the T-Mobile US variant didn't receive Android N, yet, as far as I know.) This means either converting with a 3.x RUU of the SKU you want to convert to (in your case 617 for the dev edition) and installing the official OTAs via the software update function of your phone or using one of Sneakyghost's 4.x firmware packs and flash the 4.x RUU of the SKU you want to convert to, afterwards. (Be aware that you can directly flash TWRP and a custom rom if you don't want to stay on the stock rom. Flashing a RUU isn't needed in that case.) Neither OTAs nor Sneakyghosts packs are encrypted.

The meaning of firmware versions and a way to read them are explained in one of the articles that can be found in the Useful Links section. Android 5.0.2 equals major version 1 in case of the M9. That means Android 5.1 equals major version 2, Android 6.0 equals major version 3 and Android 7.0 equals major version 4.

As far as I know there aren't that many custom roms which are based on the dev firmware. Most devs use the European SKU 401 as their base. However, the only difference between the SKUs 401 and 617 that I know of are some continent-specific optimizations. That means you shouldn't face any problems if you flash a 401-based custom rom.
[One (M9) General] draymond1987:
Thanks for your reply! I didn't own the M8 during the update period, or I just can't remember. When you have a device, it's easier to track how development is going.

It's been awhile though, so I really don't remember. Well, I would definitely want to be on the latest firmware, so if WWE is better, in your opinion, I will flash that. I got the phone and it's on 3.X , so I will unlock, root, s-off and then look for the proper firmware files to flash. Thanks for being polite and patient, by the way. Also, T-mobile didn't get Nougat yet. There's an update, but its only for the last two digits. So currently I have 3.39.531.7 (it was gonna update to 3.39.531.21) .

I am going to re-read this thread, so I don't screw up!
[One (M9) General] Flippy498:
I wouldn't say that SKU 401 is "better" than 617. 617 receives new updates first (in case of the M9). My opinion is that everyone should use the SKU that suits the personal situation best*. And as long as you're flashing custom roms you won't find any differences if you compare SKU 401 with SKU 617, anyway.

* Unbranded SKUs mean faster updates but branded SKUs mean additional features like Wi-Fi calling or VoTE, just to name two differences.
[One (M9) General] draymond1987:
I think I understand what you mean. Like I said, it's been a long time since I had an HTC device, so I am unfamiliar with the lay of the land, so to speak. I am just going to go with my instinct and flash the Developer edition, since that's what I wanted to do, and think would be easy. So basically, all I need is an 3.x Dev RUU , flash it and then just accept the update to 4.x ? I promise I won't hammer you with a lot of questions. I can certainly take the time to read, as I know some people can get annoyed with people not willing to look for themselves, you know?

I'm going to attempt this in a little while. I don't think I should flash a Dev_FullStock because it's only around 150mbs, and probably just the firmware, not everything I would need.

The joys of starting over and being "the new guy". LOL
[One (M9) General] Flippy498:
That's one possible way. ;)

That's why I wrote a 4.x RUU needs to be flashed afterwards if you choose this way (and want to stay on stock rom). :p In case you want to flash a custom rom you can use this method and directly flash TWRP and the wanted custom rom afterwards. This way you should reach your goal in less time than the "traditional" method would take.
[One (M9) General] draymond1987:
I think I will do the traditional method. I always had this OCD habit of flashing stock then the ROM I want. Not that I don't trust the firmware files. Either way, I HAVE to RUU to a developer build to accept the OTA. I do know that I can then flash any ROM I like then flash the firmware file on top of whatever ROM. Ugh, so confusing LOL. I'll be home within an hour and will hunt down a 3.x RUU.
[One (M9) General] draymond1987:
I'm stuck -_-

I found an RUU for dev edition, but I got an error 155. The version I tried was 3.35.617.16 compared to MY 3.39.531.21 .

*bows head* can you point me in the right direction?

Edit: I think I did it! Changed CID (Super CID didn't work) and MID. Then I used the SD card version, and it is currently updating! I will take the OTA to 4.x and flash a ROM in the morning! Whew. I actually remember that RUU.exes never worked properly for me. Derppppp.
[One (M9) General] computerslayer:
For future reference, it will be helpful to recall that SuperCID is not useful for the M9. Your device MID & CID must match the SKU of the RUU or OTA you are attempting to install.
[One (M9) General] Ninec:
finally received the option to update, but when I tried I got an error saying "OTA is not official" and I couldn't install the said update. After I tried to reflash with RUU I get the following error:

How can I fix that ?
[One (M9) General] Frug01:
How can i get otas again?? Install twrp backup and lock bootloader??

Enviado desde mi HTC One M9 mediante Tapatalk
[One (M9) General] Flippy498:
Only lock the bootloader if you need a paperweight.

All needed information can be found on page 1. (Maybe you should re-read the rules you accepted while registering for this website. Especially rule #1. ;))

[MENTION=7215221]Ninec[/MENTION]: Please post the fastboot getvar all output of your phone (without the phone's IMEI). It looks like your MID is not the correct one for that RUU.
[One (M9) General] Frug01:
Ok, but install the backup and then what i need to do to update by ota? Only update? Or lock bootloader and then update?

Enviado desde mi HTC One M9 mediante Tapatalk
[One (M9) General] Flippy498:
As written before, all needed information are on page 1 and you shouldn't lock the bootloader unless you need a paperweight.
[One (M9) General] Ninec:
(bootloader) kernel: lk

(bootloader) product: htc_himauhl

(bootloader) version: 1.0

(bootloader) version-main: 3.35.401.32

(bootloader) boot-mode: download

(bootloader) version-baseband: 01.01_U11440792_97.00.51203G_F

(bootloader) version-bootloader: 1.0.0.0000

(bootloader) mid: 0PJA11000

(bootloader) cid: HTC__001

Here you go [MENTION=5872674]Flippy498[/MENTION]
[One (M9) General] Flippy498:
I don't know when or why you did so but you changed your MID to the one of the dev edition. If that has already been the case the last time you reported problems here then I'm not surprised that nothing worked as it should.

Get the MID that belongs to the OTA/RUU (0PJA10000).
[One (M9) General] Ninec:
Lel now I see, but to be honest I don't know how it happened... also I don't know what code I must use to change the MID
[One (M9) General] Flippy498:
It's explained in the FAQ section of this thread.
[One (M9) General] Ninec:
Ok. thank you ! I install nougat at last you are the man dude.
[One (M9) General] Frug01:
I followed all the steps, but when updating the software, the red triangle logo comes out
[One (M9) General] Flippy498:
That's the stock recovery and it shouldn't happen. What's your current firmware and which backup did you restore? Did your phone state any error outputs?
[One (M9) General] Slowman223:
Hi All

I am in need of help. i have been looking for a while now and cant find a RUU for 3.50.710.1

I just want to go back to stock recovery and get the OTA update :)

info

(bootloader) kernel: lk

(bootloader) product: htc_himauhl

(bootloader) version: 1.0

(bootloader) imei:

(bootloader) version-main: 3.50.710.1

(bootloader) boot-mode: download

(bootloader) version-baseband: 01.01_U11440801_96.01.51207G_F

(bootloader) version-bootloader: 1.0.0.0000

(bootloader) mid: 0PJA10000

(bootloader) cid: OPTUS001

Thanks Alot
[One (M9) General] phen0m2016:
Hi,

I have a question about the Stock Recovery for this HTC One M9 phone:

Codename: hima_uhl

MID: 0PJA10000

SKU: 401

CID: HTC__102

Is the Stock Recovery for Android 7.0 (Nougat) (4.14.401.7) tha same as for Android 6.0 (Marshmallow) (3.35.401.32)?
[One (M9) General] blocka:
3.35.401.32 ruu

Hi how's it going?

Don't suppose someone would have 3.35.401.32 RUU, Or Stock backup?

Thanks
[One (M9) General] Marvolo1590:
Hi there,

would anyone know if there is the latest HTC One M9 Stock-Rom Update on 7.0 (Nougat) already available for download? I feel like the update progress messed things up on my phone and I'd like to do a clean install with the latest version (4.14.401.7).

Can't find it anywhere though. Maybe it's still too new.

Does a factory reset have the same effects as downloading the 4.14.401.7 rom? Because if so, then I could just do the factory reset instead or will it bring me back down to 3.35.401.32?
[One (M9) General] Flippy498:
[MENTION=8097714]Slowman223[/MENTION]: Please re-read the OTA section. You can't install OTAs if you only unroot your phone and re-flash the stock recovery. And since no one contributed a RUU or a TWRP backup for your firmware, yet, you'll probably have to contact Llabtoofer's RUU service if you want to be able to install OTAs, again.

[MENTION=7959510]phen0m2016[/MENTION]: No, it's not.

No one contributed the latest 401 stock recovery, yet, and I didn't have the time to extract it from either the RUU or the OTA and to upload it, afterwards. However, you can extract the recovery by yourself with the help of the decryption tool. It would be nice if you could upload it afterwards and if you would post a download link here in this thread. (The prefereable file host is AFH. It's free and provides unlimited space for android related files. In addition the website states the MD5 checksum of the uploaded file. This way you can verify whether the upload was successful and others can verify whether their download is successful.) Be aware that flashing the stock recovery and un-rooting your phone is not enough if you want to restore the ability to install future OTAs.

[MENTION=5031986]blocka[/MENTION]: Did you read what got written in the RUU section? If you did you would know that you don't need a RUU for 3.35.401.32.

[MENTION=8082070]Marvolo1590[/MENTION]: Are you serious? Please re-read the first page of the thread.

A factory reset wipes the data partition (which contains i.a. your apps), the internal storage (which contains private pictures, music, etc.) and the caches of your phone. What happens if a RUU gets flashed is explained in the RUU section of this thread. And no, a factory reset won't downgrade your firmware. (If it would you had to start from the factory firmware of your phone which is 1.32.401.8 and not 3.35.401.32.)
[One (M9) General] stjepa90:
Here is OTA update Nougat Vodafone http://fotadl.htc.com/OTA_HIMA_UHL_...35.161.12_release_49631111hn382dqg1sbiev.zip; cheers.

Just one question ,for someone who knows. My m9 was rooted,and I unrooted it with installing RUU from this thread.Recieved OTA,but ,on flashing,stopped on 25%.My question is - Should I try to install it manually via stock recovery,since there is no available RUU yet?
[One (M9) General] Flippy498:
My personal opinion is that trying to install an OTA manually isn't a good decision if you can't install the same OTA via the software update function. Normally a RUU should restore your device to a state in which it's able to install OTAs, again. Therefore I'm not sure what's causing your issue.

Is your bootloader still unlocked? Can you flash TWRP and restore the stock backup for your firmware? Maybe that solves your problem.

If your phone is S-OFF you could also try to downgrade with an older RUU and see if you're able to install the update coming from an older firmware version. However, if your phone is S-OFF you should check first whether your CID and your MID are the correct ones for the OTA before you flash anything. If that isn't the case then you'll have to change them to the correct ones and your problem should be solved.

Btw, as explained in the RUU section of this thread you wouldn't be able to use a 4.x RUU for your SKU if one existed.
[One (M9) General] stjepa90:
... It just came to my mind like 3 minutes ago to check ,and it shows UNLOCKED bootloader.. I am such an noobozord,not to check that. Will try now and will reply in edit. Thanks anyway,appreciate for being helpful :)
[One (M9) General] Flippy498:
You are aware that you don't need to relock for being able to install an OTA, aren't you? I'm asking because your post sounds like you try to install the OTA with a relocked bootloader, now.
[One (M9) General] stjepa90:
No,actually didn't know that. My m9 is s-on,and I do not have my stock recovery backup,I bought it rooted,without any backup in TWRP.
[One (M9) General] Flippy498:
The backup you might need can be found on the first page of this thread.
[One (M9) General] stjepa90:
Ok,will take a look.Thank you so much! :)

Thank you [MENTION=236940]flippy[/MENTION] on your advice for twrp backup,and then update software,it worked like a charm :)
[One (M9) General] Shaifhemraj:
HELP ME

My phone is soft bricked and I'm becoming desperate.

modelid: 0PJA10000

cidnum: HTC__001

Phone Network: Three

Region: UK

Phone: HTC One M9

Software Number: 3.35.401.12

[/IMG]

[/IMG]

Bootloader is Relocked

S-On

Software Status Modified
[One (M9) General] Flippy498:
Looks like you didn't attach any picture to your post.

However, flash a RUU and all should be fine. A softbrick isn't that hard to recover.
[One (M9) General] Shaifhemraj:
I need the correct one though, I've tried several using the ruu exe files on my PC (I'm running windows 10 with the HTC Drivers). I've only managed to try two that were version 3 like mine though. I heard version 3 can't be updated to 4. I did try the sd zip method with no luck either.
[One (M9) General] Flippy498:
Did you read the RUU section? It clearly explains how to find the correct RUU and how to flash it.

And I don't know which RUU you tried to flash but there are no 3.x *.exe versions of RUUs for your SKU. I guess you just downloaded random ones from HTC's website, correct? As explained on the first page those RUUs are only for the US versions of the M9
[One (M9) General] Shaifhemraj:
Post 3 right? Wait so if theres no 3.x exe versions, is it possible for me to fix my phone? Im sorry for being ignorant but I'm new to all this, I just registered yesterday.
[One (M9) General] Flippy498:
The answer to that question can be found in the post you quoted.
[One (M9) General] Shaifhemraj:
Look, I know I'm inexperienced and slow alright? Anyways, I reread the RUU section but now I'm more worried because as you said, there are no 3.x *.exe versions of RUUs for my SKU. Is my phone fixable? It mentions that I can't update from 3 to 4.

Heres the images by the way

https://postimg.cc/image/av8lb2g7p/ (It does not say modifed anymore)

https://postimg.cc/image/lw3qg38gl/

UPDATE: I am starting to understand it more. I didn't know this before but what you said about SKU really explains a lot ( If 3.35.401.12 is your current firmware then you need to look for RUUs with SKU 401.) I was using random ones before.
[One (M9) General] Flippy498:
I don't know why you're so fixated on RUU.exe files.

Everything you need to know and all files you might need are posted in the RUU section. You just have to read what got written there. And the post I was talking about and that you quoted tells you already that the RUU section contains instructions how to find the correct RUU and how to flash it. I don't know what other answer you expect...

This is a ReadMe thread and therefore it requires people to read. It's ok to have no experiences and it's ok to ask questions if things are still unclear but it's not ok if you skip the reading and directly ask things that are already explained on the first page.
[One (M9) General] Shaifhemraj:
I FINALLY FIXED IT!! Flashed one of your zip files, renamed it to OPJAIM.zip and my phone is finally back to normal!!! Im sorry for not noticing that section telling me how to associate version numbers. I'm just so relieved that its finally back to normal. Stayed up all night trying to desperately fix the phone using a variety of different methods. At one point, I thought I had to change my bootloader from relocked to unlock but then I found this thread today and saved my phone thanks to you.