Develop Bugs

HTC One m9 - Stock 2.10.401.1 is here!

Getting the 2.10.401.1 step by step, crystal clean instructions.
This guide is mostly for the people who are stuck on lower versions where "About" says that there are no updates and that their device is up to date. Especially users who previously did 1.32.401.17 RUU. This version is know to have some major flaws and it tends not to read any updates, accept auto and manual OTAs nor zipped RUUs.
- Alright so I saw good number of people being stuck on European 1.32.401.17, 1.32.401.15 and 1.32.401.8 and unable to grab auto OTA and unable to manual OTA install due to various errors being thrown in twrp. There are also users who are having issues with SD transfers, transfers from PC to to phone especially when they transfer zipped RUU (0PJAIMG). Do not worry, I am going to help you with this. Just follow my simple steps. Note that you can forget about custom recoveries, microsds, system dumps, zipped ruus that "wont copy" to your device and others. You won't need any of these in my procedure. Simply ignore them. Now focus on my steps.
Step 1; Download the 1.32.401.17 exe RUU from here; DO NOT RUN THIS YET.
Step 2; Download the 1.40.401.8 0PJAIMG (ZIPPED RUU). Do not open/modify this yet.
Step 3; Backup your data on the phone such as contacts, SMS and so on. I personally use Wondershare mobilego for those things.
Step 4; Navigate to temp folder by typing %temp% in the search bar or C:\Users\Username\AppData\Local\Temp\ >>
Step 5; Under that folder you may or may not delete the files you don't need for easier navigation. Now this part is very important. Focus on that folder.
Step 6; Go back to 1.32.401.17 exe you downloaded in the step 1. Right click on it and Run it as admin. Once ran, it might take several minutes to open actual installer. Let it load all they where you see next/cancel. Stay there and do not cancel it or hit next.
Step 7; Go in your temp folder under step 4. You will see two newly created folders. You only need this one. Under that folder you should see another one with few random files. Go into other subfolder and navigate to the file named rom.zip. Delete this folder.
Step 8; Now go back to the file you downloded in step 2. Name that file to rom.zip and place it where you previously deleted the zip file from temp subfolder.
Step 9; Go back to the RUU installer interface and press next and do the procedure like you did with version x.17. You should see this. Now let the RUU installer updates your phone.
Step 10; Go under Settings > About > Updates. Now if you did all right you should see the magic: http://i.imgur.com/aqR4YwD.png >> Grab this new 100% fresh and stock OTA update and enjoy.
- I tested this few times on several devices and it works for every one of them. I am not aware of the other carrier users are having issues but same procedure can be done. Do not install custom recovery or root your device before you updated your device to 2.10. If in any case updater wont pick the 2.10 update you can flash your recovery and firmware from 1.40.401.8 version (prior to the 2.10 update). Do not panic if update is taking a while, it will reboot your device few times and thats it. To be on more safe side you can always flash the firmware once device is properly updated to 2.10.
*Flashing the firmware to 2.10*
Download from here and put it where your ADB interface is;
Put your device to download mode and open up the cmd where adb interface and latest firmware is.
do the following commands:
a.) fastboot oem rebootRUU
b.) fastboot flash zip firmware.zip
c.) fastboot reboot
- Make sure the phone is not rooted or tampered with. If something is not clear feel free to ask. I hope this helped to you.
Nikola

Nikolay82 said:
*Flashing the firmware to 2.10*
Download from here and put it where your ADB interface is;
Put your device to download mode and open up the cmd where adb interface and latest firmware is.
do the following commands:
a.) fastboot oem rebootRUU
b.) fastboot flash zip firmware.zip
c.) fastboot reboot
- Make sure the phone is not rooted or tampered with. If something is not clear feel free to ask. I hope this helped to you.
Nikola
Click to expand...
Click to collapse
S-ON Users should not try to do this if they weren't able to get and install the 2.XX.XXX.X uptdate before they get to this step. The firmware pack does not update the rom and it can only be flashed on S-ON devices if the bootloader is locked or relocked. HTC introduced a new "security feature" with the 2.XX.XXX.X firmware. This "feature" blocks the Bootloader Unlock if the option "OEM unlocking" in the Developer Options isn't activated. Without an up to date rom you won't be able to activate this option because it does not exist in earlier versions. Since there are no international 2.XX.XXX.X RUUs S-ON Users who follow this part of the guide and did not install the OTA beforehand would then be stuck with the 2.XX.XXX.X firmware and a 1.XX.XXX.X rom.
Except for that missing warning it's a very nice written guide.

I've tested this on S-ON device. I've successfully flashed 2.x for the sake of testing, both s-off and s-on. That part is probably not something many people will need, but its there just to be on safe side. The RUU itself will throw an error if there is a CID conflict anyway. Personally, I am not a fan of tampering with CID unless it is a must. User should be able to find proper RUU/OTA to match their CID.
I am working with the phones and I often have people who likes to tamper with their device. Good number of them will even write different CID, or even "universal" one just so they can go through RUU process and update. However, later they stuck on "no mobile data" unable to fix things. 99.9% of them failed to update their current model to latest so they resort to changing CID and putting in different country ROM just because it is newer. As for HTC introducing new security feature I wont go much into detail about it because it falls under hacking and reverse engineering in order to benefit from said action. Let's just say they never got around some crucial elements which pretty much made their security feature vain. Apple claimed similar thing. One day I sat down and put in the windows OS just because "tiles" were trend back then. I am yet to see a safe and totally secure update. Apple was the closest with their icloud and findmyphone but I decided for droid mostly because i wanted more freedom for what I pay. Cheers.

Nikolay82 said:
I've tested this on S-ON device. I've successfully flashed 2.x for the sake of testing, both s-off and s-on.
Click to expand...
Click to collapse
I never said that you won't be able to flash the firmware with S-ON. And please don't get me wrong. Your guide is very good.
The problem is that there is a special kind of xda readers which tends to skip some of the important steps that are described in instructions. If those people flash the firmware without installing the OTA beforehand they will be stuck with an unlockable, (re-)locked bootloader and a 1.XX.XXX.X rom on a 2.XX.XXX.X firmware. There are already plenty of threads which describe similair scenarios here on xda. That's the reason for the warning in my last post.

help

friends would you help me my htc one m8 it stuck of a htc logo with 4 error signs and wont work .i attached pictures of the error and the bootloader

Was it you trying to update the firmware ? Reinstall firmware.zip again to fix that.
Or .. run the official RUU from here : http://www.htc.com/us/support/htc-one-m8-att/news/
(one thing to note : there is no need to relock bootloader to do anything when your device is S-Off)

how to do that my friend iam a nowbie in these thing also i dont want an at&t thing also for your notice i dont have a recovery in it , its simply empty

You just need to install that AT&T RUU to bring it back to life.
Once it is working normally, you can install other ROM on it.
What you need is a Windows PC with USB 2.0
Latest HTC USB drivers installed on PC. Read this : http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4
Download the RUU that I gave link earlier.
Connect to PC
Right click the RUU exe and select run as Administrator and follow the intructions

my friend do you have a youtube link showing how to do all this

No ... no idea as I never rely anything on youtube.
What I gave you, you don't need youtube.
Just download and install those three items.
1. ADB/Fastboot - when you install, it asks to install adb/fastboot, type Y
then it asks to make it system wide - type Y
then it ask to install drivers - type N
2. Install the HTC Sync Manager as it will install the drivers. Once completed, uninstall HTC Sync Manager but leave all other things
3. The RUU.exe, right click on it and in select run as administrator then follow the pop-up instructions accept - next - next - blablabla until it says completed.
Most important your PC must have USB 2.0

i did what you said but then i get this error
The ROM Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again.
it says on the bootloader

I was away due to not feeling well (down with high fever .. still recovering ..)
Your problem here is mainly wrong MID... your current MID is 0P6B17000 (which I believe is the GPE MID)
To run the RUU, the MID must change to 0P6B12000
Can you unlock the bootloader again ? If not .. I give to give you other alternative.

ckpv5 said:
I was away due to not feeling well (down with high fever .. still recovering ..)
Your problem here is mainly wrong MID... your current MID is 0P6B17000 (which I believe is the GPE MID)
To run the RUU, the MID must change to 0P6B12000
Can you unlock the bootloader again ? If not .. I give to give you other alternative.
Click to expand...
Click to collapse
Yeah my friend i realized this and install the gpe ruu and its now working fine with 6 thanks alot hope you feel much better

M9 unlocker issues

Hi,
This morning I woke up to my beautiful m9 with a message saying my data is corrupt and I had to perform a factory reset. At this point it would repeatedly reboot every 10 seconds many times until it eventually landed on the message telling me it was corrupt.
After trying a cache wipe (unsuccessful) I attempted the factory reset from the special boot menus and it wouldn't complete. There was an error about failing to mount /cache, /preload, and some others. But it seemed to be able to clear some partitions because at this point it would sit on the white HTC load screen (different behaviour).
I then moved to trying to flash. After mucking around with various procedures I finally absorbed enough information to find a suitable image and procedure. The issue is that I can't load it because I wasn't aware of the OEM unlock option in dev options in the phone so it's locked at the moment.
The phone is s-on and locked, so I'm wondering if I've missed any options to recover this.
I can't flash recovery.img or boot.img because it's locked.
I can't set s-off because I can't boot into OS (and sunshine people said it requires Android OS to be running).
Factory reset doesn't seem to work because of the mounting issues.
Have I missed something? Is there some way to unlock without having access to dev options? Is there another way to set s-off? Anything else anyone can think of?
And if the answer to all that is no; what are the chances an approved repairer can fix this? Would they have some method to getting around the above blocks?
Thanks.

You may need to send it in to HTC - it sounds like a physical corruption. But before you go that route, I wonder if a RUU is available for your model. S-ON/Locked status won't matter as long as the RUU matches your CID/MID.

computerslayer said:
You may need to send it in to HTC - it sounds like a physical corruption. But before you go that route, I wonder if a RUU is available for your model. S-ON/Locked status won't matter as long as the RUU matches your CID/MID.
Click to expand...
Click to collapse
thanks for the reply.
yeah that was my conclusion as well. it may have happened due to power issues with the place I'm staying at whilst the phone was charging from socket. Due to the amount of difficulty I've been having in general with things not working I have a feeling it's not going to be a software fix, but that doesn't stop me from trying.
from fastboot getvar:
version-main: 3.35.401.12
mid: 0PJA10000
cid: HTC__J15
(this prompt is missing a few expected lines like battery voltage which prevent me from running .exe RUUs; never figured that out).
I found the following online:
OTA_HIMA_UHL_M60_SENSE70_MR_HTC_Europe_3.35.401.12-2.10.401.180_release_464237.zip
which has a firmware.zip in there, and in that is android-info.txt with following extracts:
modelid: 0PJA10000
cidnum: HTC__J15 (with a bunch of others)
mainver: 3.35.401.12
in download mode with fastboot from htcdev running cmd.exe with admin privileges, 'fastboot.exe flash zip firmware.zip' gives the following:
fastboot-win>fastboot.exe flash zip firmware.zip
sending 'zip' (74641 KB)...
OKAY [ 5.275s]
writing 'zip'...
(bootloader) HOSD CL#671758
FAILED (remote: 9 RU_SECURITY_FAIL zip from usb command in download mode)
finished. total time: 6.433s
I also found another zip called 3.35.401.12-Firmware.zip which again has android-info.txt with same extracts (but a lot of missing options in the txt file compared to firmware.zip). Ran same command and received same error.
Am I doing everything correctly?

Hi Skitzor,
Sorry for the late reply - been away from the computer lately.
Using an executable RUU in Windows isn't option? I'm not sure I understand what you mean about the prompt & battery voltage. But that may not matter if the zip file method can work for you.
Heavy disclaimer here: I don't know anything firsthand about applying a RUU via zip file. However, Flippy498's Google Sheet is easily the best resource to guide you through that process. Check out the 'RUU' tab for a step-by-step walkthrough.
(Checking your MID & CID against the SKU-, CID- and MID-List by Sneakyghost and Behold_this identifies your phone as the Europe WWE model on the HTC-GCC carrier. I would agree that the HTC WWE RUU is the right one for your phone)

computerslayer said:
Hi Skitzor,
Sorry for the late reply - been away from the computer lately.
Using an executable RUU in Windows isn't option? I'm not sure I understand what you mean about the prompt & battery voltage. But that may not matter if the zip file method can work for you.
Heavy disclaimer here: I don't know anything firsthand about applying a RUU via zip file. However, Flippy498's Google Sheet is easily the best resource to guide you through that process. Check out the 'RUU' tab for a step-by-step walkthrough.
(Checking your MID & CID against the SKU-, CID- and MID-List by Sneakyghost and Behold_this identifies your phone as the Europe WWE model on the HTC-GCC carrier. I would agree that the HTC WWE RUU is the right one for your phone)
Click to expand...
Click to collapse
No, I cant' seem to get the EXE method to work. For whatever reason when I take the fastboot getvar all command it doesn't show the battery voltage. And the EXE application seems to attempt to get the same battery-voltage value, and nothing is returned so it assumes the battery is dead or something and tells me I need 30% battery. It may be that I'm not running in the correct mode (recovery, bootloader, download, etc), but I have tried to get into every mode I can see and none of them give me output for the voltage parameter.
Thank you for the link to that sheet, haven't come across it yet. I believe I have tried some firmware.zips of the correct format, but don't think I have a full 0PJAIMG for the correct version. I will download and try this. Rather than trying to rely on fastboot I will also probably try to track down an SD card and use that method. Let's hope one of those options work.
If that doesn't work the place I purchased it from seem willing to honour the warranty (well they said they would test, so I'm guessing there's still a chance they could deny), which is good.
Thank you again for the assistance computerslayer.

skitzor_a said:
No, I cant' seem to get the EXE method to work. For whatever reason when I take the fastboot getvar all command it doesn't show the battery voltage. And the EXE application seems to attempt to get the same battery-voltage value, and nothing is returned so it assumes the battery is dead or something and tells me I need 30% battery. It may be that I'm not running in the correct mode (recovery, bootloader, download, etc), but I have tried to get into every mode I can see and none of them give me output for the voltage parameter.
Thank you for the link to that sheet, haven't come across it yet. I believe I have tried some firmware.zips of the correct format, but don't think I have a full 0PJAIMG for the correct version. I will download and try this. Rather than trying to rely on fastboot I will also probably try to track down an SD card and use that method. Let's hope one of those options work.
If that doesn't work the place I purchased it from seem willing to honour the warranty (well they said they would test, so I'm guessing there's still a chance they could deny), which is good.
Thank you again for the assistance computerslayer.
Click to expand...
Click to collapse
It seems likely that the voltage issues are related to the corruption issues....though how is beyond me. I hope the sd card method bears fruit - or that the warranty route works!
Peace,
Computerslayer

Does the phone show its charging while powered off?
Have you tried going into stock recovery and letting it charge?

Tachi91 said:
Does the phone show its charging while powered off?
Have you tried going into stock recovery and letting it charge?
Click to expand...
Click to collapse
yes, there is no issue with charging. when EXE method was complaining about lack of charge it was sitting at 100%. it's been able to charge when off, and I think when it's been on as well.

Help For Old Guy Reverting TWRP M8 To Stock

Hey guys. Need some help remembering how to do this stuff and what info i need to get some real help sorting out my misses phone.
Ive not done this for a very long time...since i re did my old HTC HD2.
So...the misses has had her HTC One M8 for over a year now. Bought off Ebay and all is good. An update needed to be done about 6 months ago but the wife said it failed all the time. I had a look and found it had a TWRP boot loader on and a custom ROM installed (i guess). The phone will not even connect to sync manager (my original M8 will) but is seen by Windows and can view the internal storage and SD storage.
So, want to revert it back to a stock M8 image but am confused about what i need to get to make this happen.
I know my M8 is on version 6.12.401.4 and have downloaded a recovery image with that number. Also, the TWRP version on the misses phone is v2.8.6.1.
Please can someone with a lot more brain power help me to revert her phone back to stock and save me from a moaning wife (and not moaning in the good way )
Thx in advance for any help

What's the OS- no. written on bootloader ?
If that is blank, post the fastboot getvar all result without serial & imei no.
If there is OS- with no. and it's a GSM device, check the thread linked in my signature for how-to and the files needed.

Hi ckpv5 and thx for the reply
Well i have no idea whats going on with this phone or what the misses has been playing around with.
So after i come home from work to day..she shoved the phone in my hand and said "its broke...go fix it". So had a look........and now it stops on the HTC screen and will go no further. When i connect it to the PC...i can see the internal storage and the SD card. There seems to be not much on the internal storage....so not sure if she has deleted the actual OS on the phone and thats why it will not boot through. There is 10.5GB free of 10.6GB
Im sorry for being really dumb but i cant seem to get the info from the fastboot getvar all results. Not sure if its me or the phone but tried what was posted and got nothing :/
So...not sure if this helps but this is whats on the bootloader screen:
*** software status: Modified ***
*** UNLOCKED ***
M8_UL PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.25.214500021.0GG
OpenDSP-v48.2.2-00567-M8974_FO.1211
OS-
eMMC-boot 2048MB
Jan 15 2015,22:51:08.290
TWRS is on version 3.0.2.0
I dont know if that helps you to point me in the right direction or help me out but please let me know as now have a moody wife :/
Thx again in advance

stuka69 said:
When i connect it to the PC...i can see the internal storage and the SD card. There seems to be not much on the internal storage....so not sure if she has deleted the actual OS on the phone and thats why it will not boot through. There is 10.5GB free of 10.6GB
Click to expand...
Click to collapse
10.6 GB internal storage is just the user accessible part. This means its the 16 GB version, and the balance (5.4 GB) is reserved for the OS (and that partition is not viewable in Windows).
It doesn't prove whether the OS has been deleted or not (it still may be - but doesn't prove so).
stuka69 said:
Im sorry for being really dumb but i cant seem to get the info from the fastboot getvar all results. Not sure if its me or the phone but tried what was posted and got nothing :/
Click to expand...
Click to collapse
Are you in bootloader, and have fastboot mode selected (FASTBOOT highlighted in red near the top of screen)?
Is so, try another cable, or another USB port on the PC. Does the command work on your phone?
stuka69 said:
HBOOT-3.19.0.0000
RADIO-1.25.214500021.0GG
Click to expand...
Click to collapse
The radio number corresponds to Lollipop (version number 5.xx). The stock nandroid you mention in the first post 6.12.401 is Marshmallow, and therefore won't work.
stuka69 said:
TWRS is on version 3.0.2.0
Click to expand...
Click to collapse
I'm confused, the top post say TWRP 2.8.6.1 is installed?
---------- Post added at 11:15 AM ---------- Previous post was at 10:38 AM ----------
stuka69 said:
I know my M8 is on version 6.12.401.4 and have downloaded a recovery image with that number.
Click to expand...
Click to collapse
Be careful, I think you have your terminology mixed up here.
A recovery image is not a ROM or OS. Recovery image refers to a custom recovery (like TWRP) or stock recovery (stock analogue of TWRP), which is only the tiny stock/official application which installs OS updates, etc.
A TWRP backup or stock ROM (OS) is typically around 1.5 GB (for Sense ROMs). Stock recovery image is around 10 MB.
In any case, as already mentioned, the version number 6.12.401 (even if you are referring to stock TWRP backup) won't work on your wife's phone (mismatch the current LP firmware).

Hi redpoint
Thx for your reply and trying to help me.
Yes you are correct...it is 16GB storage. Just goes to show how long i have been out of the loop with these sorts of things and probably why im having trouble sorting this out
Thx for clearing up that the radio version is for a Lollypop version and for setting me straight on on recovery and ROM terminology.
Now...can i post the phone to some one to sort out for me lol

OK....managed to get the fastboot getvar all result
INFOversion: 0.5
INFOversion-bootloader: 3.19.0.0000
INFOversion-baseband: 1.25.214500021.06G
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main:
INFOversion-misc: PVT SHIP S-ON
INFOserialno:
INFOimei:
INFOimei2: Not Support
INFOmeid: 00000000000000
INFOproduct: m8_ul
INFOplatform: hTCBmsm8974
INFOmodelid: 0P6B10000
INFOcidnum: HTC__001
INFObattery-status: good
INFObattery-voltage: 0mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 3aa067db
INFOhbootpreupdate: 11
INFOgencheckpt: 0
Does that help you guys. If it does....please can you point me in the right direction on what files i need and how to go about setting the phone back to its stock image.
Once again....im really thankful for all the help you guys have given so far and any thats to come.

That's a EU device.
To get back to stock and directly to the latest Marshmallow, you can follow this
http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6

thx ckpv5...ill give it a try when i get home from work

stuka69 said:
thx ckpv5...ill give it a try when i get home from work
Click to expand...
Click to collapse
ckpv5's advice is excellent, as always. But one thing I'd add, is that the RUU update method he linked will wipe all data on the phone. If there is anything on the phone your wife wants to retrieve/keep (that isn't backed up to removable SD or off the phone - such as PC or cloud), you might try to restore the stock TWRP backup (restore Lollipop) and corresponding stock recovery, retrieve the data, and from there either see if the update installs properly, otherwise update to MM using the RUU method linked by ckpv5 above.
To restore stock TWRP backup for Lollipop, use ckpv5's thread (also linked in his signature) and install the stock TWRP backup and stock recovery for 4.16.401.10 or 4.16.401.13 (can't tell which exactly, I just know its one of those from the radio number). Necessary files and instruction in the thread: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Now, we don't exactly know what caused the phone to stop booting in the first place, so I'd suggest to make it clear to your wife up front, that you may or may not be able to retrieve any data. But its certainly worth a try.
Of course, if there isn't any data your wife wants to keep, you can go ahead with ckpv5's original advice to update by RUU.

Yeah there is nothing on the phone that she wants to keep now
So, tried it out but when i go to flash it says it cannot open the zip file. Below is the cmd string:
Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.
C:\Users\st00kz>cd desktop
C:\Users\st00kz\Desktop>cd ruu
C:\Users\st00kz\Desktop\RUU>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ -0.000s]
finished. total time: -0.000s
C:\Users\st00kz\Desktop\RUU>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.000s]
finished. total time: 0.000s
C:\Users\st00kz\Desktop\RUU>htc_fastboot flash zip RUU.zip
error: preprocess_file : Cannot open file RUU.zip
C:\Users\st00kz\Desktop\RUU>
After typing the "fastboot oem rebootRUU" the phone reboots and has HTC on a black screen and stays there. Is that correct?
I also tested the files in the zip and it looks like some are corrupted:
C:\Users\st00kz\Desktop\RUU\RUU.zip.zip: The archive is corrupt
C:\Users\st00kz\Desktop\RUU\RUU.zip.zip: Checksum error in dzdata_32g.img. The file is corrupt
I tried downloading it on all the mirrors from this link in your other post https://www.androidfilehost.com/?fid=24369303960687057
Am i doing it right??? if so...is there another place that i can find the zip file???
Thx for all your advice again guys

1. The zip is not corrupted but it is encypted so you can't open it.
2. Read the above when you tested the zip. It seems your windows extension is hidden, when you rename the file to RUU.zip, you actually rename it to RUU.zip.zip, that's why you have the error (read that warning in the guide). Rename the file to RUU and do the test again, can you see now it is read as RUU.zip ? If yes, retry the procedure but this time run the flashing part with :
fastboot oem rebootRUU
htc_fastboot flash zip RUU
3. Don't skip the upper part in the guide, to relock bootloader if current bootloader status is unlocked.

stuka69 said:
So, tried it out but when i go to flash it says it cannot open the zip file.
Click to expand...
Click to collapse
There is nothing in ckpv5's instructions that say to open the RUU zip. I don't know why folks are always trying to do this.
The command "fastboot flash zip xx.zip" expects exactly that, an unaltered zip file to flash. Download, rename, and flash it, that's all. The zip file doesn't need to be unzipped or anything like that.
Once you mess with the zip, (which isn't actually possible without the HTC encryption key - and trust me you can't do it) you make the zip unsigned, which also means you then can't flash it with s-on, by definition.
So moral of the story, leave the zip alone (aside from renaming it) and flash it.
stuka69 said:
C:\Users\st00kz\Desktop\RUU>htc_fastboot flash zip RUU.zip
error: preprocess_file : Cannot open file RUU.zip
Click to expand...
Click to collapse
I can see how this part may have led you to believe something was wrong with the zip, and to further examine it (possibly leading you to try to unzip it). But as ckpv5 mentioned, this error is almost always a result of folks not having the zip file in the right location: either simply not in the right folder (same folder as htc_fastboot.exe) or more commonly you unwittingly named it "RUU.zip.zip" due to Windows defaults.
Do yourself a favor, and turn off the Windows setting to hide file extensions (which is usually enabled by default): Control Panel>Folder Options>View tab, and deselect the option "Hide extensions of known file types".

ckpv5 said:
1. The zip is not corrupted but it is encypted so you can't open it.
2. Read the above when you tested the zip. It seems your windows extension is hidden, when you rename the file to RUU.zip, you actually rename it to RUU.zip.zip, that's why you have the error (read that warning in the guide). Rename the file to RUU and do the test again, can you see now it is read as RUU.zip ? If yes, retry the procedure but this time run the flashing part with :
fastboot oem rebootRUU
htc_fastboot flash zip RUU
3. Don't skip the upper part in the guide, to relock bootloader if current bootloader status is unlocked.
Click to expand...
Click to collapse
Ahh ok got you now. Sorry ...must have missed the part about the windows extension (misses bleating in my ear about getting this sorted and other nonsense ) Ill go back and have another look with out her around.
And yes I did the upper part of the guide. I relocked the bootloader.
Thx again for your help. I will owe you a lot of beers soon

In case the above not working for you, here is the easier one ...
1. Download the RUU_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10_Radio_1.25.214500021.06G_20.68.4196t.01_F_release_417003_signed.exe from http://androidruu.com/?developer=M8
2. Connect the device to PC (in fastboot/bootloader mode)
3. Right click the exe and select run as administrator, follow all the instructions, accept/agree, next, update, next, blablabla until it complete. (You need PC with USB2.0 and HTC USB drivers installed - I believe you already have these)
4. After reboot, setting up everything, go to settings - about - software update - do the checking, download, install OTA update.
There are many methods to fix your phone. Just try these two options first. I'll be travelling back to home in the morning (I won't be able to reply to any question that you may have during that time) and I'll be home in the evening and will check your progress.

Its alive...its alive i tell you
Guys...you have mine and the wifes greatest appreciation of what you have helped with. Thx for all your time and patience with me. It was just that damned file extension
If you guys are ever in the south UK at any time...let me know and ill buy you some beers
Thanks once again guys
Joe

Great :good::good:

Nice work; and happy to help.
Hey, how old is "old" anyway, if I may ask? I'm 43.

LOL ok not as old as you then...but even thats not old
Im 38...just feel a lot older when trying to remember this stuff...and my 4 girls dont help either

stuka69 said:
LOL ok not as old as you then...but even thats not old
Im 38...just feel a lot older when trying to remember this stuff...and my 4 girls dont help either
Click to expand...
Click to collapse
4 girls, yikes!
I have 2 young daughters at home myself. And that is why I'm rarely on XDA at home, lol.

No Download-Mode__Possible Fix

Ok Guy's
In the last few weeks there are more and more people struggling
with their devices so I decided to make a thread about a POSSIBLE fix.
It seems nobody knows what happens exactly.. but at some point the
download mode is no more accessible and you can only enter booloader mode with the white screen.
And once more this is only a Possible fix....no magical repair for your defective emmc or something like that.
This should only be a little help for some of you guys I´m not responsible for anything.
You do this on your own.
If it works, a hit on the thanks button would be nice, if not sad to say but I think you have to
go to the repair center.
We are starting at the point that you are familiar with fastboot and have a correct setup with drivers etc. on
your PC. (If not... search the forum and read how to set it up)
Files are signed so they should be also flashable with s-on.
Steps:
1. Download the Package for your Android-Version :
Lollipop:
https://www.dropbox.com/s/ts8tur5tkzv1o4l/0PJA_HIMA_L51_service_hosd_collection_900002.zip?dl=0
Marshmallow:
https://www.dropbox.com/s/pgw3hslknajl9kc/0PJA_HIMA_M60_service_hosd_collection_900001.zip?dl=0
Nougat:
https://www.dropbox.com/s/2azzxi9q65iilsj/0PJA_HIMA_N70_service_hosd_collection_9000033.zip?dl=0
2. Unzip it and take the CORRECT hosd.img for your version. (best is... you know wich version you have)
3. Connect M9 in bootlader mode and flash with fastboot:
fastboot flash hosd <filname>.img
4. MAYBE now you can enter download mode again.
5. If you don't know what version you have you can try one file after another..
fastboot outputs only okay when the right hosd.img is flashed.
(try to boot to download after every file)
6. If no one work it's pretty sure that your emmc is broken.
There is nothing more I know or I can do for you
so I can't give more support after this point.
Good Luck

broken link
You can reload the files

finitura said:
broken link
You can reload the files
Click to expand...
Click to collapse
This link will be around for a while... https://drive.google.com/folderview?id=0B4vTiHTBB629bFBtd3FUS01Ia1U
Beamed in by telepathy.

thank you

Thank you for this post which already the last hope for many people but please if you have to the files for Android Nougat please upload it many phone are broken after nougat update
thank you in advance

puede volver a subir el enlace

To everyone whos's searching for alternative/new download links:
You can find the hosd.img inside of the RUUs that are posted in the ReadMe thread. The decryption tool that is linked in its RUU section will help you to extract the needed file from the encrypted RUUs.
For being on the safe side you should only use files from RUUs that are matching your current firmware version. You can try to use the files from other RUUs with a similar version if there's none available for your current firmware/your SKU, though. However, never flash a CDMA file on a GSM phone or vice versa.

Hi guys,
maybe you can help me, otherwise I will open a new thread.
I got a M9 here from a friend that i wanted to fix.
Mode: Modified
S-ON
Bootloader: Locked
It began, that the Phone and SMS/MMS apps on the phone dissapeared until one day it didn't even boot up.
Can't flash anything because i can't access download mode or recovery mode, both say:
"Failed to boot to download/recovery mode" in red warning font...
I downloaded all signed htc one m9 firmwares from:
handy-faq.de/forum/htc-one-m9-firmware-ruus-otas-backups-stock-recoveries-t314182/#comment-2885828 and tried to flash every hosd.img file from the firmwares via fastboot. always got back "OKAY", rebootet but still didn't work...
Also tried to follow this tutorial:
handy-faq.de/forum/geloest-htc-m9-wiederbeleben-t320617/?page=1 and tried to flash the other files as well, but they always say "FAILED, cannot flash this partition in S-ON state" for example for aboot or other .img files...
Could you help me? Also read that some M9 have Storage Failures or problems.
I can't give you info of getvar all command in fastboot, because that doesn't work without download/recovery mode.
Thanks in advance!
Chris

There's probably nothing you (personally) can do. That looks like faulty hardware. The main problem of the M9 is the same that every smartphone with the snapdragon 810 is suffering from. Depending on the usage of the phone the soc is roasting the phone's internals. The latest firmware version fixes the overheating but it won't repair damages that got created while the phone was used with one of the older firmware versions.
If the warranty is still valid you can send the phone to HTC for letting them change the motherboard. The data on the phone is lost, though.
Sent from my HTC One M9 using XDA Labs

Hey,
woah that reply came fast, didn't expect that.
Much thanks for the info!
Yeah the app dissapearence and then the complete failure of the phone made me think of that too... but thanks for clarification!
That a subsequent update of the firmware does not make the board functional again makes sense, haha...
I will have a look if I/he can still get a change of the motherboard by warranty, if not i will gonna just put it into the trash bin.

Well, there's no reason not to answer if I'm around and have the time to write a post. (On the other hand it might happen that I don't have enough time for several days.)
It's a bit funny that Handy-FAQ is back online. That guest account that answered in the second thread you linked is mine. I left the site over a year ago and as far as I heard from my former fellow team members the site got shut down some months ago...
Sent from my HTC One M9 using XDA Labs

Can you please re upload the files i wan't to try them out?

joostnl said:
Can you please re upload the files i wan't to try them out?
Click to expand...
Click to collapse
c.f. what I wrote on page 1 of this thread:
Flippy498 said:
To everyone whos's searching for alternative/new download links:
You can find the hosd.img inside of the RUUs that are posted in the ReadMe thread. The decryption tool that is linked in its RUU section will help you to extract the needed file from the encrypted RUUs.
For being on the safe side you should only use files from RUUs that are matching your current firmware version. You can try to use the files from other RUUs with a similar version if there's none available for your current firmware/your SKU, though. However, never flash a CDMA file on a GSM phone or vice versa.
Click to expand...
Click to collapse

Flippy498 said:
There's probably nothing you (personally) can do. That looks like faulty hardware. The main problem of the M9 is the same that every smartphone with the snapdragon 810 is suffering from. Depending on the usage of the phone the soc is roasting the phone's internals. The latest firmware version fixes the overheating but it won't repair damages that got created while the phone was used with one of the older firmware versions.
If the warranty is still valid you can send the phone to HTC for letting them change the motherboard. The data on the phone is lost, though.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Hey there,
I will get a broken m9 (already paid for it) for less money which doesn´t start anymore after the update (to nougat?) but had no issues since 2 years like she told me.
I hope it´s only a bootloop, got not more information about that problem (owner has no clue about it).
I may need those files...
I think the newest firmware is installed so if i can´t access the bootloader, could you upload me this file?
I don´t want to restore stock, i want to unlock the bootloader and flash LineageOS and use it as daily driver.
My One M8 is a great phone but a cheap upgrade isn´t bad

D:\HTC M9\L51>fastboot getvar all
(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:HT55CYJ00237
all:
finished. total time: 0.125s
i am stuck on bootloader mod doesn't go on download mod nor to recovery mod.
can't boot to Android as well,
All the other values for CID, MID and other stuff is blank when I do indivdual fastboot getvar command.
can I bring my M9 to life with any stock image flashing with Fastboot command.
If yes please let me know which stock image I use and how to flash?
Thanks

Files reuploaded + nougat hosd if somebody need good luck