yashsingh1/xdaforums huggingface dataset:
[One (M9) General] Flippy498:
It's not my intention to sound rude but the guides on the first pages are absolutely noob-friendly. There is no easier way to describe what you need to do. If you can't follow those guides then you aren't capable of fixing your phone. You can feel free to ask follow-up questions but I won't post, again, what already got posted on the first pages.
[One (M9) General] gioyocho:
hey please anyone help me. i have no rooted, btl locked, s-on. i have system version 4.14.401.7, when i am going to update, ota says that it is available to 4.28.401.3 and when i am trying to update, it stucks 25% and then red triangle. htc support told me wipe cache/factory data reset but no helped for me. please tell someone solution :( thanks
[One (M9) General] Flippy498:
Please read the FAQ.
[One (M9) General] gioyocho:
i read Readme but i did not understand what to do. flash exactly same system what i have and then update ota or flash updated version? also i do not know what is ruu. i have no adb files, no rooted, no twrp, no unlocked bootloader, also i have s-on. i have everything stock. there are so many flash zip files and .exe ruu. also i do not know s-on or s-off is better on flash ruu files

can someone create video of this? thanks
[One (M9) General] Flippy498:
You need to flash the same system that you're currently using. All needed files and instructions can be found at the beginning of this thread. There's a post about setting up ADB and (HTC_)Fastboot correctly and another one that gives you basic infos about RUUs and explains how to flash them.

S-OFF isn't needed as long as there is a RUU with the same version as your phone or as long as there is a RUU with a newer version.

Edit: If you use the SD card method for flashing the RUU you don't even need ADB/(HTC_)Fastboot and the method itself takes less than 5 minutes.
[One (M9) General] Tetragrammazoid:
Looks like a lot of people are having that problem:

https://forums.androidcentral.com/ask-question/787804-ota-update-freezes-25-how-can-i-fix.html?amp

I'd just wait until HTC fix it.
[One (M9) General] Flippy498:
Please read the FAQ. It's not an issue with the OTA. It's an issue with the hardware of your phone.
[One (M9) General] gioyocho:
Maybe i have refubrished version, but why wipe cache partition or factory data reset is not solution?
[One (M9) General] Flippy498:
Because your system partition got corrupted (either due to a hardware issue or because the previous owner tinkered with it). This way it doesn't pass the security checks of the Block-based OTAs that Google introduced with android 5. Wiping the cache or the data partition (aka factory reset) has no influence on the system partition.
[One (M9) General] gioyocho:
That is so bad. My phone is not even rooted, how can do damage previous owner? It is all stock. Idk what means google block based otas android 5
[One (M9) General] Flippy498:
I linked the official explanation written by google in my last post.

To summarize what is written there: Old android versions only checked some important files of the system. If those files were available and not modified you could install an OTA. All versions since android 5 check the whole system. Therefore, the tiniest modification results in the inability to install OTAs. That's why system-less root is such a big thing, nowadays. Older rooting methods modified the system partition so that root was always equal to "no OTAs" on android 5 devices.

However, even if the root-method you use is system-less you can still modify the system with root apps (e.g. Titanium Backup for uninstalling system apps). If you do so even unrooting won't restore the ability to install OTAs. You need to reflash the whole system partition. Either with a TWRP backup of an untouched system or with a RUU.
[One (M9) General] gioyocho:
Thanks for reply but i do not know much about root, twrp, bootloader and etc. Early years when i tried 3 or more times to change rom manually, phone stucked at logo. And then hardly survived. So from few years for me it's ok using everything stock. No more going to change something on stock and ota builds. It is safe and everything works
[One (M9) General] Marko Indaco:
Hi, nowdays it's quite different form the past. I understand and respect you're decision but I think it's more saftey to try a custom rom today's (of course depend on what you're are goin to modify). Usually a simple long press Vol.Up/Down + Power reboot the phone as well, also when bootloops occours. It's only my impression about the more safety, [MENTION=5872674]Flippy498[/MENTION] ?
[One (M9) General] gioyocho:
yes it is safe, but there are so much errors and so much options. also if you make mistake, it will be dangerous for you
[One (M9) General] Marko Indaco:
Yes, errors occours, but you follow the guide, also asking in Forum, you can do it without hassle (Flippy498 help was awesome).

Important is (assuming you're already unlock the bootloader) Install TWRP for Nandroid backup's, but you can also ADB sideload it and using it without install (for the very first approach). At least, if you change you're mind you can try when the phone warranty expires :D

Anyway, if you don't feel fine it's ok. I don't want to force you, only encourage ;)

Greetings
[One (M9) General] gioyocho:
well. i hate this part, rooting, set twrp, unlock bootloader, install big size ADB applcation in computer, change rom... i prefer do not touch stock android. some roms have bugs, then you must do downgrade or international rom and etc. so much work, which is not safe
[One (M9) General] TechnicianX:
Latest RUU image for SKU 709

Hi team/Flippy498,

I ended up purchasing the latest RUU image for my SKU 709 HTC One M9 so I'd like to share it via AFH. Could this please be added to the main RUU post as well? I've used the image twice now to recover my fully stock phone after it got stuck in a boot-loop.

0PJAIMG_HIMA_UHL_N70_SENSE80_MR_hTC_Asia_TW_4.30.709.12_Radio_01.01_U114401011_117.00.61117G_2_F_release_506540_combined_signed_2_4.zip

https://www.androidfilehost.com/?fid=673791459329055285
[One (M9) General] clsA:
A [MENTION=5872674]Flippy498[/MENTION] quick question

whats the quickest route to 4.30.617.12 from 3.35.617.12

the 4 phones were all AT&T on 1.x.502.x and I have them all unlocked /s-off and CID changed to BS_US001

I was able to htc_fastboot / RUUflash 3.35.617.12 but all the 4.x.617.x RUU I have found seem to fail
[One (M9) General] Flippy498:
Since you have S-OFF, use any of Sneakyghost's 4.x firmware packs for updating the firmware and then flash the latest 617 RUU.

The encryption keys got changed between firmware 3.x and 4.x (that happened on the M8, before). Therefore, you can only use unencrypted files for updating from 3.x to 4.x (= OTAs for S-ON or Sneakyghost's packs for S-OFF).
[One (M9) General] clsA:
OK Thanks for the reply

I ended up just letting the phones all download all the OTA updates one by one until they were done
[One (M9) General] gioyocho:
Flippy498

hallo. can you help me to rewrite my system. i have 4.14.401.7 and red triangle after update

i have no root, no twrp, s-on, locked bootloader, no sd card. what i must do? thanks

please help me it says error. trying 3 times but again same
[One (M9) General] Flippy498:
Are you trying to flash a RUU from this thread or a firmware package from Sneakyghost's thread? The latter is impossible with S-ON.

Please link the file that you're trying to flash.
[One (M9) General] gioyocho:
i was doing it with fastboot cmd and zip file 4.14.401.7....... is ruu file safe? but i have 4.14.401.7 version now. there is new version 4.28.401.3 and oficially htc site written 4.30.617.12

also i have s-on

i am flashing first page download zip file 4.14.401.7 (MD5: 148A8AF99EBDC7B26B4B14C09179D6E0)

this https://docs.google.com/uc?id=0B4oyO3CwWup3S052Q0l0bTdQd00&export=download
[One (M9) General] Flippy498:
As said before, please link the file you tried to flash. According to the naming in your screenshot it looks like you're trying to flash a custom made firmware package which isn't possible with S-ON. Looks like you edited your post.

Being S-ON only means that you can't use RUUs that are older than your current firmware or use a different SKU. It has nothing to do with the "safety" of RUUs.

SKU 617 RUUs can't be used with S-ON on a SKU 401 phone. The latest version for your SKU is 4.28.401.3.

All flashing methods that can be used for RUUs are explained in the RUU section of this thread.

Edit: I've successfully used the RUU that you linked, in the past. So the uploaded file is most probably fine. Nonetheless, I haven't seen that error 9, before. Does the MD5 checksum of your downloaded file match the desired value?
[One (M9) General] gioyocho:
Flippy498

yes i understand, but you said need reflash same system what i had.

i am not using ruu.exe files. i just downloaded firmware exactly what i had and trying reflash with cmd fastboot mode and there is error. i must flash next version 4.28.401.3? and not same system 4.14.401.7? i have s-on
[One (M9) General] gioyocho:
maybe i must flash next version, i have 4.14.401.7 and next is 4.28.401.3

or there is damaged zip file, because when i am trying to open .txt file or "extract here" it says me error, yellow sign. corrupt. see attachment

i do not know how to check md5
[One (M9) General] Flippy498:
If the MD5 checksum of the file on your harddisk matches the desired value then yes, please try the 4.28.401.3 RUU. If it gets flashed successfully it will update your phone directly without the need of the OTA that failed in the past.

Edit: The RUUs are all known to be working. If they got damaged the MD5 checksum wouldn't match.

In regard to that unzipping error, I need to ask you to read question 7 of the FAQ.
[One (M9) General] gioyocho:
Flippy498

yes md5 check was correct same. i am downloading 4.28.401.3 firmware

is it safe with s-on?

also look at this. there is written that error 90 is normal, but second time it must flash, but there were again errors. error 9 for me
[One (M9) General] Flippy498:
As said before, S-ON has nothing to do with the safety of RUUs.

Yes, error 90 is normal. Error 9 isn't, though. And as posted before, I haven't seen that error ever before. Therefore, the whole situation is for me as much trial and error as it is for you.
[One (M9) General] gioyocho:
Flippy498

check these. maybe just s-off need

https://www.reddit.com/r/htcone/comments/4frjxu/can_i_revert_my_m9_back_to_stock/

https://xdaforums.com/sprint-one-m9/development/ruu-sprint-htc-one-m9-1-32-651-17-t3073355/page80

people have same problem
[One (M9) General] Flippy498:
I don't think that error has something to do with S-ON/S-OFF. You don't try to flash an older version and you don't try to change the SKU, either. In addition, I know that the files got successfully flashed on S-ON devices, in the past.

If the 4.28.401.3 RUU doesn't get flashed via htc_fastboot, either, I'd try to get an SD card for the SD card method if I were you.
[One (M9) General] gioyocho:
it is the same error 9. i have no sd card. so sad. i have first time htc and i guess never will buy anymore
[One (M9) General] gioyocho:
second way try it shows again another error
[One (M9) General] Flippy498:
You used the normal fastboot in your last post. That one isn't capable of flashing RUUs. The flash is expected to fail in this case.

It's most likely something in your setup that causes the error since the RUUs already got flashed successfully by several users, in the past. In addition I haven't faced that error 9 in my entire time on xda, until I read your posts. So the cause for your issue isn't that common and therefore finding the fix is everything else than easy.

Flashing files via fastboot can be a pain sometimes since there are many variables that can make it fail. That's why I said that I'd try to get an SD card if I were you. (And that's why the SD card method is the recommended method in this thread.)
[One (M9) General] ziand:
[MENTION=4626334]gioyocho[/MENTION], I see you try to use a fastboot flashing method of RUU: https://xdaforums.com/showpost.php?p=73241261&postcount=1367

It is a very good method too but this method works when you have unlocked bootloader ONLY !!!

So, for you there is a single way: to flash RUU using extSD card method.. you need to find extSD card at exFAT formated.
[One (M9) General] kazzxtrismus:
Hello from Canada

can someone help me get confident i have the right supersu for rooting MM please.

I'm unlocked soff factory rom & twrp 3.1.1.

.

the problem is ive read through this thread enough and others to turn my brain potato.

i was previously only systemless rooted

.

i would like an exact supersu version number and mounts list to get full root so i can properly backup.

sys rw + system checkboxed before backup?

or sys ro + system checked?

.

im a very long drive from a computer to pull apart the backups and check their contents.

.

i do not want ota's (or nougat) in future...just a nice little aosp/cyannogen 6MM rom...

.

thanks!
[One (M9) General] Flippy498:
The correct SuperSU version depends on your current firmware version (c.f. Q4 of the FAQ in this thread). Your firmware is stated in the line with "OS" at the beginning if you boot the M9 to download mode.

If you tinkered with your phone (what you probably already did according to the facts that TWRP is installed and the phone is S-OFF) then you can't backup the system in an untouched state, anymore. In other words it doesn't matter how you backup the system partition. It won't restore the ability of installing OTAs if you restore it, later.

As soon as the system gets mounted as read/write or modified in any other way (e.g. by uninstalling system apps) its checksum changes and this can only get fixed by restoring an untouched backup of the same system version or by flashing a RUU. Aside from that, the stock recovery is lost if you didn't back it up before flashing TWRP. This is, again, only fixable with a RUU.

If you want an untouched system backup (that includes the corresponding stock recovery) you need to find a RUU for your phone, to flash it and to follow the instructions in TWRP section I of this thread. You'll need a PC for being able to do so, though. Since you have S-OFF you can use older RUUs that have the same SKU as your phone, too. You only need to re-install the updates that lead to your current firmware version if you use an older RUU.

If you want to backup the system partition and don't care whether that backup is able to install OTAs or not then you only need to backup the system image and the boot partition. The state of the system partition (read-only or read/write) doesn't matter due to what I wrote above.
[One (M9) General] gioyocho:
I unlocked bootloader but again same problem. 9 ru_security_fail :(
[One (M9) General] ziand:
If not to learn your problem with PC... You haven't to unlock bootloader just to update stock ROM. The best way now: you need to find extSD card at exFAT formated to flash the RUU.zip 4.14.401.7 from extSD.
[One (M9) General] sconly:
Has anyone got/found the 3.35.401.32 RUU?

Can I still Unlock Bootloader and Root without it?

Thanks
[One (M9) General] Flippy498:
Please read the first "important note" in the RUU section of this thread. You don't need a 3.35.401.32 RUU. ?
[One (M9) General] jhoni King:
Search 3.39.531.41 firmware. Someone can help?
[One (M9) General] Flippy498:
[MENTION=7548312]jhoni King[/MENTION]:

Download the RUU for that version from the RUU section and extract the firmware files with the RUU decryption tool that is linked in the further reading section. That's the easiest method for getting the firmware for that version, at the moment.
[One (M9) General] jhoni King:
I'm sorry, I meant just RUU for that version. On the official site of HTC the link to this version is broken.

P.S. Sorry fo my bad English.
[One (M9) General] Flippy498:
The download link in the RUU section is still working, though...
[One (M9) General] Donnie267:
Hey, I have a question. I recently found out that if your kernel and android version don't match, you can't upgrade normally. My question is... How would I find out which android version do I need to flash to he able to get ota updates/update through ruu without error. Here's the screenshots of my software info.
[One (M9) General] Thabto:
Hi guys.

How or where can I get hosd_signed.img for my htc one m9?
[One (M9) General] Marko Indaco:
[MENTION=4694003]Thabto[/MENTION] It's not clear what you're going do to with that file. Furthermore you didn't provide any info about you're phone...

In the meantime did you read the ReadMe Thread?
[One (M9) General] paolocorpo:
I extracted it from OTA\firmware of my actual version

I used it with success to restore the download mode that disappeared on my HTC M9

Fastboot flash hosd hosd_signed.sign

Inviato dal mio VTR-L09 utilizzando Tapatalk
[One (M9) General] jhoni King:
There is the following problem:

OS on my phone 3.39.531.31

BUT

(bootloader) mid: 0PJA10000

(bootloader) cid: HTC__A07

Altogether when I install 3.39.531.41 and OTA to 4x, I get an error 10.

Help, I do not know what to do
[One (M9) General] Thabto:
HI. I've got an HTC M9. My device is in a boot loop. S-ON, Locked, Software Status: Official. I was on android 7.0 before the boot loop issue. I received an update request over WiFi the other day, the update was around 620mb in size. When the update finished downloading, I was prompted to plug in the charger to begin installation, which I did. After a few minutes, my HTC M9 was stuck in a boot loop. From an off state, I can only access the fastboot by pressing vol up, vol down & power. While there, if I select Download mode or Recovery mode, the phone restarts and resumes the boot loop.

So I was hoping that if I flash hosd_signed.img I may regain access to recovery mode or even download mode. I do not know more about the software variant that was in my phone before this happened. I just know I was running android 7. I do have the box of the phone, don't know if the serial number or the part number may tell more about my device. Please help. Region of the phone s South Africa. Let me know
[One (M9) General] paolocorpo:
My ex M9 was running Android 6

I used the relevant hosd file extracted from relevant OTA

It fixed the problem very similar to your

I have the Firmware for Android 7 Nougat

I will try to extract the file for you

If I have success I will upload it for you

Please let give me a couple of hours ... Now I am seeing my football team in Championship :)

Stay tuned

Paolo

Inviato dal mio VTR-L09 utilizzando Tapatalk
[One (M9) General] Thabto:
Awesome. Thanks I will be waiting.
[One (M9) General] paolocorpo:
Extracted from:

Full_Stock_firmware__4.28.401.3_(with_wipe)_signed.zip (NOUGAT)

HOSD_SIGNED.img

Here:

https://www.sendspace.com/file/4sa1gy

PS

Are you sure that you had Android 7 ? Or are you confusing with HTC SENSE 7 ?
[One (M9) General] Thabto:
Thanks
[One (M9) General] NeonicZyfr:
Have a problem finding a file.

So the problem I'am having is that in order to update to version/OS 3.38.502.41 to get to the 4.27.502.7 version/OS I need the 3.38.502.31 version/OS and I cant find it. My phone is an HTC M9 ATT Version/OS 3.38.502.17 (S-Off) . Would I have to use the LlabTooFeR service to get the 3.38.502.31 version/OS.

When I download the 0PJAIMG_HIMA_UL_M60_SENSE70_ATT_MR_Cingular_US_3.38.502.41.zip and try to read the .txt file in it, it will say that it is corrupted. It also won't let me move it from my downloads folder to my phone the .zip that is.

I read the Ruu part but the ruu for 3.38.502.31 is not there only 3.38.502.41. Which makes it hard to update it.

Thanks for the help.
[One (M9) General] paolocorpo:
You are wellcome

Have you fixed your issue ?

Paolo
[One (M9) General] Flippy498:
As written in the RUU section, you can use newer RUUs, as well, as long as they use the same encryption keys as your phone. Therefore, you can use the 3.38.502.41 RUU, too. Alternatively, since you have S-OFF, you could search in Sneakyghost's firmware thread whether he has a custom firmware pack for your SKU that contains firmware 4.x. This way you would update your phone's encryption keys and could directly flash the latest 4.x RUU, afterwards. Using llabtoofer's RUU Service would be a waste of money in your case, though.

The reason for the RUUs not being able to get unzipped is mentioned in the FAQ. They're encrypted. Your unzipping program doesn't "know" the encryption keys and therefore "thinks" the archive was corrupted. That's why I suggest in the first post to check the MD5 checksum of downloaded files.

The problem with the copying process is mentioned in the guide for the SD card method. You either need to connect the card directly with your PC (so that it's not put into your phone while copying the RUU) or to delete the *.zip extension before you try to copy the file (don't forget to re-add the extension after the file got copied). I don't know why the copying process fails otherwise, though.
[One (M9) General] Thabto:
Hi

I did flash the hosd_signed.img with htc_fastboot, but still I cant access download or recovery modes. What else should I try?
[One (M9) General] paolocorpo:
Ciao

I am sorry about your unsucces

I want try to help you but I have a couple of questions:

1. Are you sure that you had Android 7 ? Or are you confusing with HTC SENSE 7 ?

2. What does it mean " with htc_fastboot" ?

3. Have you received back some error message ?

P
[One (M9) General] Thabto:
1. Yes I had android nougat

2. htc_fastboot.exe

3. No error while flashing hosd_signed.img
[One (M9) General] paolocorpo:
Do you want try with a different version of fastboot exe file ?

You can try the files provided by Flippy in this thread at post #3

Inviato dal mio VTR-L09 utilizzando Tapatalk
[One (M9) General] gioyocho:
do i need s-off for flashing custom rom?

i mean root, unlock btl, set twrp, install custom rom. can i do it with s-on?
[One (M9) General] Flippy498:
Yes, you can.
[One (M9) General] gioyocho:
Flippy498

thanks. i have installed new custom rom "ice" and it is cool. problems solved. i am s-on again. new system 4.28.401.3

there are no errors now
[One (M9) General] NeonicZyfr:
Hey, Thanks I got it to work and got nougat installed. The main problem was that I had to use the sd card and flash the ruu.zip in recovery instead of fastbooting it from the computer because that would give errors.
[One (M9) General] Flippy498:
Are you sure that you flashed a RUU? It's not possible to flash them via a recovery.
[One (M9) General] NeonicZyfr:
I downloaded the ruu from the GSM Ruu Section and flashed the zip in recovery after renaming the zip to 0PJAIMG.
[One (M9) General] Flippy498:
Ah, ok. That's not the recovery. That's the download mode. Neither the stock recovery nor TWRP can handle RUUs.
[One (M9) General] NeonicZyfr:
Yah sorry mixed up the names.
[One (M9) General] chromosome91:
i've tested that rom (0PJAIMG_HIMA_UHL_M60_SENSE70_MR_hTC_Asia_TW_3.36.709.3_Radio_01.01_U11440792_97.00.51203G_F_release_464289_signed.zip)

not as a volunteer cuz my phone stopped and i needed it and this was about 6 months ago and it did run smoothly one annoying thing was the phone couldn't get upgraded to nougat and stopped in the middle of the install but now i got the same problem and the phone stopped again and now the same ROM that saved me before does not install properly and that grey htc logo keeps popping up and vibrating.
[One (M9) General] Flippy498:
If the MD5 checksum of the downloaded file is matching the desired value then it's most likely a hardware issue that you're suffering from.

The post that you quoted got written in July 2016. In the meantime, there have been reports that the RUU is working fine and that installing OTAs is possible after flashing it.
[One (M9) General] Thabto:
Hi

My htc m9 is stuck in a boot loop after failing to complete an OTA update.

Here are the facts:

1. I don't have access to download mode, if I select this mode or recovery mode, my phone restarts and resumes the boot loop

2. I have successfully flashed hosd_signed.img but that has not restored my recovery and download modes.

3. My M9 was stock, S-ON, locked. And usb debugging was not enabled I think.

So is my phone affected with the dead nand issue? Let me know. Thanks