Develop Bugs

[Q] HTC One M8 won't boot.

Some one please help me.
I have the HTC One M8 which I updated to Android 5.0.1 through OTA updates about 2 weeks ago.
Yesterday, I successfully unlocked the bootloader and rooted my device. I also have the TWRP Recovery v.2.7.0.2 installed.
Everything was working fine until after the root when I noticed that the internal storage had some kind of write protection on it. Like even the default "DCIM , ANDROID, Downloads etc... folders weren't there". I discovered the write protection on the internal storage when I tried to download a file using Chrome on the phone and it replied with "No SD Card".
Funny thing is apps from the Play Store were installing perfectly fine.
So I booted back into TWRP recovery and did a factory reset thinking I must've messed up while rooting.
After the factory reset when I try boot up my phone the Setup Wizard constantly crashes so I can't do anything.
My HTC One M8 is the international variant Model: 0P6B100.
Someone please help

1. Install the latest TWRP 2.8.5.0 or 2.8.4.0 (2.7.0.2 is damn too old and buggy)
2. In TWRP select Wipe - Format Data (you will lose all files in internal storage)
3. Reboot - you should be able to run the setup wizard

ckpv5 said:
1. Install the latest TWRP 2.8.5.0 or 2.8.4.0 (2.7.0.2 is damn too old and buggy)
2. In TWRP select Wipe - Format Data (you will lose all files in internal storage)
3. Reboot - you should be able to run the setup wizard
Click to expand...
Click to collapse
I installed TWRP 2.7.0.2 using All in one tool v2.0 by Hasoon2000. The tool needs usb debugging to be turned on which I can't turn on because I can't get past the setup wizard because it keeps crashing.
Is there a way to install it manualy using fastboot?

I thought so ... when I see TWRP 2.7.0.2 I can guess you use some outdated Toolkit.
Press & hold Volume up and power button until the screen turn off then quickly release both buttons and press & hold volume down button. This should get you to hboot. Press power once to go to bootloader.
If you don't have a proper ADB & fastboot installed, download Minimal ADB and Fastboot and install : http://forum.xda-developers.com/showthread.php?t=2317790
Download latest TWRP : http://techerrata.com/browse/twrp2/m8
Connect to PC and open a command prompt and run command fastboot devices and see any connection with PC, it will give your device serial no. if it does.
If yes, flash the TWRP : fastboot flash recovery NameofTWRP.img then do the above that I mentioned

ckpv5 said:
I thought so ... when I see TWRP 2.7.0.2 I can guess you use some outdated Toolkit.
Press & hold Volume up and power button until the screen turn off then quickly release both buttons and press & hold volume down button. This should get you to hboot. Press power once to go to bootloader.
If you don't have a proper ADB & fastboot installed, download Minimal ADB and Fastboot and install : http://forum.xda-developers.com/showthread.php?t=2317790
Download latest TWRP : http://techerrata.com/browse/twrp2/m8
Connect to PC and open a command prompt and run command fastboot devices and see any connection with PC, it will give your device serial no. if it does.
If yes, flash the TWRP : fastboot flash recovery NameofTWRP.img then do the above that I mentioned
Click to expand...
Click to collapse
Okay I got my serial number. Now what do I do with it?

bolajiibrahim7 said:
Okay I got my serial number. Now what do I do with it?
Click to expand...
Click to collapse
If you don't feel like installing the latest TWRP as I said above ... then -> hboot -> recovery -> wipe -> format data -> type yes -> reboot
I wrote almost everything there, but read only the last paragraph ??
Read again all of my posts here.

ckpv5 said:
If you don't feel like installing the latest TWRP as I said above ... then -> hboot -> recovery -> wipe -> format data -> type yes -> reboot
I wrote almost everything there, but read only the last paragraph ??
Read again all of my posts here.
Click to expand...
Click to collapse
I did that. Then it started the "Android is upgrading - Optimizing apps splash.
After that I'm back to the Setup Wizard which keeps crashing.

Then the only choice is to restore a stock backup or RUU.
What's your software version ?
Better post result of fastboot getvar all (minus the serial no. & imei no.)

ckpv5 said:
Then the only choice is to restore a stock backup or RUU.
What's your software version ?
Better post result of fastboot getvar all (minus the serial no. & imei no.)
Click to expand...
Click to collapse
My software version is 5.0.1 Lollipop.
I don't have a stock backup. RUU is my only option.
Here's my fastboot getvar all
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.214500021.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ************
(bootloader) imei: ***************
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.125s
C:\adb>

I do have backup for your device version here : http://forum.xda-developers.com/showpost.php?p=58499803&postcount=4076
but there is also RUU for your device.
Just follow @EddyOS thread discussion : http://forum.xda-developers.com/showthread.php?t=2735235

ckpv5 said:
I do have backup for your device version here : http://forum.xda-developers.com/showpost.php?p=58499803&postcount=4076
but there is also RUU for your device.
Just follow @EddyOS thread discussion : http://forum.xda-developers.com/showthread.php?t=2735235
Click to expand...
Click to collapse
Also for some reason. I don't have S-off. But I managed to unlock and bootloader and root.

bolajiibrahim7 said:
Also for some reason. I don't have S-off. But I managed to unlock and bootloader and root.
Click to expand...
Click to collapse
You don't need S-Off to run RUU, relocked bootloader before run RUU. Read thru that thread, there are many discussion.
Read this, this guy also doesn't have S-Off device : http://forum.xda-developers.com/htc-one-m8/help/one-m8-htc001-cid-firmware-wifi-problem-t3031656 and he managed that.
Or just restore backup that linked to you if you don't feel to relock bootloader.
You need to read all those thread. Without reading, this is going no where .. good luck

ckpv5 said:
I do have backup for your device version here : http://forum.xda-developers.com/showpost.php?p=58499803&postcount=4076
but there is also RUU for your device.
Just follow @EddyOS thread discussion : http://forum.xda-developers.com/showthread.php?t=2735235
Click to expand...
Click to collapse
What does RUU mean? and how do I use it?
Also does applying RUU restore my phone to the way it was before root as in With Android 5.0.1 and Sense 6.0?

RUU is ROM Update Utility released by HTC.
Read the thread on how to use it. Basic is put your device on bootloader/fastboot mode and relock your bootloader with command fastboot oem lock.
Then run the RUU exe in Administrator mode (select run as Administrator) from your Windows explorer.
This will wipe everything on your device and replace with new stock ROM with no root.
That RUU is lollipop 5.0.1 and Sense 6.0
Read the thread.. you will understand what it does. Good night.

ckpv5 said:
RUU is ROM Update Utility released by HTC.
Read the thread on how to use it. Basic is put your device on bootloader/fastboot mode and relock your bootloader with command fastboot oem lock.
Then run the RUU exe in Administrator mode (select run as Administrator) from your Windows explorer.
This will wipe everything on your device and replace with new stock ROM with no root.
That RUU is lollipop 5.0.1 and Sense 6.0
Read the thread.. you will understand what it does. Good night.
Click to expand...
Click to collapse
I did everything as outlined and I ended up with:
C:\Download\HTC One M8 Toolkit 2.0.2.1\adb>fastboot flash zip ruu.zip
target reported max download size of 1826418688 bytes
sending 'zip' (1536838 KB)...
OKAY [ 42.728s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 98.981s

bolajiibrahim7 said:
I did everything as outlined and I ended up with:
C:\Download\HTC One M8 Toolkit 2.0.2.1\adb>fastboot flash zip ruu.zip
target reported max download size of 1826418688 bytes
sending 'zip' (1536838 KB)...
OKAY [ 42.728s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 98.981s
Click to expand...
Click to collapse
Did you do fastboot oem rebootRUU before fastboot flash zip ruu.zip ?
Let's do a different way, the simplest one.
1. Re-unlock your bootloader
2. Make sure you have TWRP 2.8.4.0 or 2.8.5.0 installed (I mentioned many times about this version, right ?)
3. Download a flashable stock ROM One_M8_4.16.401.10_stock_system_dump.zip from : http://forum.xda-developers.com/showthread.php?t=2694994
4. Boot to recovery and connect to PC, In TWRP recovery select Mount and enable MTP, you should be able to open internal storage or MicroSD on your PC
5. Transfer the downloaded One_M8_4.16.401.10_stock_system_dump.zip to Internal Storage or MicroSD
6. In recovery, select Install and select One_M8_4.16.401.10_stock_system_dump.zip then swipe to install
7. Reboot

Thank You.
ckpv5 said:
Did you do fastboot oem rebootRUU before fastboot flash zip ruu.zip ?
Let's do a different way, the simplest one.
1. Re-unlock your bootloader
2. Make sure you have TWRP 2.8.4.0 or 2.8.5.0 installed (I mentioned many times about this version, right ?)
3. Download a flashable stock ROM One_M8_4.16.401.10_stock_system_dump.zip from : http://forum.xda-developers.com/showthread.php?t=2694994
4. Boot to recovery and connect to PC, In TWRP recovery select Mount and enable MTP, you should be able to open internal storage or MicroSD on your PC
5. Transfer the downloaded One_M8_4.16.401.10_stock_system_dump.zip to Internal Storage or MicroSD
6. In recovery, select Install and select One_M8_4.16.401.10_stock_system_dump.zip then swipe to install
7. Reboot
Click to expand...
Click to collapse
Thank you so much for your help. My phone is now on Lollipop and rooted and working fine.

Kinda in the same problem...
Hi ckpv5, I wonder if you can help me...having the same problems...but I need some guidance.
I'll try to give you all the info:
fastboot getvar all:
version: 0.5
version-bootloader: 3.16.0.0000
version-baseband: 1.16.21331931.LA11G
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: HT43TWM0xxxx
meid: 00000000000000
product: m8_ul_ca
platform: hTCBmsm8974
modelid: 0P6B12000
cidnum: CWS__001
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: c3d94491
hbootpreupdate: 11
gencheckpt: 0
TWRP 2.7.0.1 - I know it's old and buggy but flashing a newer one, even though it flashes ok, it wont load.
The phone is Tampered - Unlocked with S-On
After unlocking and flashing TWRP, I flashed custom ROM MaximusHD, it worked but as I didnt that it needed newer firmware, wifi wasnt working, tried to restart the phone and it entered in a boot loop.
Then flashed: http://forum.xda-developers.com/showthread.php?t=2699186
But it wont boot...
Could you please help me?
Thanks in advance

macdo said:
Hi ckpv5, I wonder if you can help me...having the same problems...but I need some guidance.
I'll try to give you all the info:
fastboot getvar all:
version-bootloader: 3.16.0.0000
product: m8_ul_ca
modelid: 0P6B12000
cidnum: CWS__001
Click to expand...
Click to collapse
You have a AT&T device.
Just relocked bootloader - fastboot oem lock
Then run RUU (select run as administrator in Windows context menu) : http://dl3.htc.com/application/RUU_...40.34.C35006.02_F_release_407726_signed_2.exe
This will update your device with stock 3.42.502.1 (4.4.4)

Thanks for the fast answer, I'll it and report back!
---------- Post added at 02:20 PM ---------- Previous post was at 02:16 PM ----------
ckpv5 said:
You have a AT&T device.
Just relocked bootloader - fastboot oem lock
Then run RUU (select run as administrator in Windows context menu) : http://dl3.htc.com/application/RUU_...40.34.C35006.02_F_release_407726_signed_2.exe
This will update your device with stock 3.42.502.1 (4.4.4)
Click to expand...
Click to collapse
After fastboot oem lock, I got this:
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) turn off fd8c2308 failed 1 times. Try again...
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = 536739196 (0x1FFDFD7C)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id = 0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id = 0, error
(bootloader) = 4
(bootloader) [INFO] Rebooting device
FAILED (status read failed (No such file or directory))
finished. total time: 1.139s
And rebooted to bootloader now, it says:
Tampered
Relocked
Security Warning
Is it ok? (btw, im downloading ruu)
Thank you so much!

HTC One M9 stuck on fastboot bootloader

Hi !
One of my friend ask me to try to save his One M9 phone, that seems to be bricked.
Here is the context :
- I absolutely don't know what he did, and it seems he don't either...
- The phone state is : Software status : Modifed, S-ON, and LOCKED
- I can't have another screen that Fastboot bootloader
The only options in the bootloader menu are :
REBOOT : it works
REBOOT TO BOOTLOADER : it works
BOOT TO DOWNLOAD MODE : does not work (Failed to boot to download mode)
BOOT TO RECOVERY MODE : does not work (Failed to boot to recovery mode)
POWER DOWN : it works
I tried a lt of things, and read a lot of threads before posting this one.
What i can say for the moment is :
- RUU flash using exe : does not work, i get an error saying the battery is too low
- RUU flash using SD card (extract rom.zip, renamed 0PJAIMG.zip, and put on the root of SD card) : zip is not detected at boot
- Getting bootloader unlocked : does not work, because fatboot oem get_token_identifier command seems unknown (probably because oem commands only work in download mode for this phone)
- Getting S-OFF : seems impossible without OS, as it needs Sunshine app installed...
- Few fastboot commands are OK (devices, getvar all, ...) but most of it are refused because of S-ON
- No adb commands are working
Here is the output of fastboot getvar all :
Code:
D:\ANDROID\RUU\RUU>htc_fastboot getvar all
(bootloader) version: 0.5
(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: FA56GYJ01267
all:
finished. total time: 0.094s
htc_fastboot finished. total time: 0.718s
So, from your experts point of view, is this phone definitely bricked, or is there a way to save it ?
Thanks for your precious help guys !

Hey! I have the exact same problem. Anyone knows how to fix that?
I unrooted, stocked and relocked the bootloader. Everything went fine first, was using the phone about two days. But after a restart I'm stuck in bootloader and can't boot to download nor recovery mode.
Phone is only working with fastboot commands.
I also tried these steps OP tried and everything is the same.
I tried to flash hosd file and this works, but still not able to boot to download mode.
The HTC One is an unbranded EU model with 3.35.401.12 (<- but I think there's nothing on the phone right now)

i am also facing same problem with 2 htc one m9 which i have, i also have XTC2CLIP box which is professional tool for all htc devices, i can S-off with this box of all htc phone even no os needed, but phone should accept bootloader mode & ftm mode, & in this case where we can only goto fastboot mode, S-off command not working in state... i spend lot of time but no luck... but i still believe its only software bug & can be solve with fastboot commands. because i aslo read about same problem on htc X model. & they use fastboot command for this problem. but these commands not working on m9 case.

no solution for this? I have one m9 here exatly with the same situation, already did all your debuging with the same results

Hi there! I'm new here, created an account specially for replying to this thread:
So I'm having the same problem, phone (EU M9) died on it's own. Everything is stock.
Tried all of the above, also no results...
Here is my log from "fastboot getvar all"
Code:
C:\Android>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:HT54NYJ04596
all:
finished. total time: 0.147s
If anyone has any ideas left, I'm happy to try them. For now, it's an ugly paperweight

If it died on its own and in a stock state then you can safely assume it's dead. Most likely nand failure.
Ps, dont all m9 serials start with an "F"?.
Beamed in by telepathy.

thank you

My guess is it tried to do an OTA update overnight, don't know exactly where it went wrong.
By the way, I do get some ADB communication:
First reboot to bootloader (so it doesn't say "Security Warning"), then select 'boot to Recovery Mode' and wait for the red triangle.
If it doesn't reach that point, reboot to bootloader once more. If it does reach the red triangle: hold the Power button and press the Volume Up button once. You can then release the Power button and Recovery Mode should become visible. Note that I tried several options in this menu including "Install from ADB" and "Install from SD Card", but both gave errors.
Hope someone can use this information.

I have exactly this same issue. Sounds like NAND failure? Nothing to be done about it?

KaiLoi said:
I have exactly this same issue. Sounds like NAND failure? Nothing to be done about it?
Click to expand...
Click to collapse
If it's spewing failed to mount errors then yes, dead phone. Only htc will be able to fix it.
Beamed in by telepathy.

Soft brick, signature error when flashing rom

Hi there ,
I'm having some troubles with flashing a new rom into my HTC M9.
Last week HTC "tried" to install android 7 via the automatic update in my phone. For some reason (might be because I bought my phone abroad) the installation failed and my phone booted back to its OS. I paid no attention to it (Wasn't that eager to upgrade)
a few days later after I tried to restart my phone, it decided to brick (just like that) and now I can only get as far as the boot menu when turning on my phone on.
My phone is S-on , and the bootloader it locked (quite inconveniently as I came to realize) and I am able to get to Download\Recovery\bootloader mode.
I found my CID and MID and double checked that the "androind-info" file in the RUU I downloaded suits them. But I keep receiving the message "footer is wrong signature verification failed".
To add to my enormous sorrow (I'm quite attached to my phone), I am not able to mount my internal SD even after performing "factory reset" and "cache format". At first I suspected the card is damaged but when I write "fastboot getvar all" in bootloader mode I can see that the partitions exist and have an address.
For some reason "adb" doesn't recognize my phone in "adb devices" unless I'm in "sideload mode" and I'm unable to launch "adb shell" or any "adb" function that is not "adb sideload"
Also I'm not able to update my firmware (OTA) because the phone keeps complaining that the firmware version doesn't match (I searched all over the web for "more fitting" firmware but couldn't fine one that would satisfy my phone).
I searched this forum (and the web) for an answer to my problem but couldn't find a solution to my problem.
To sum things up: S-on , bootloader locked + not able to unlock it with HTC's guide , can change to Bootloader\Recovery\Download mode but that's all (No custom recovery mode) , internal sd wouldn't mount though external sd would, "signature verification error" when trying to update my RUU.
Here is what "fastboot getvar all" gives me:
In bootloader mode:
(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:FA563YJ00838
in Download mode:
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei:
(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: 0PJA10000
(bootloader) cid: HTC__032
And this is the RUU and OTA I tried to flash (via fastboot, adb sideload , external sd):
RUU:
0PJAIMG_HIMA_UHL_N70_SENSE80_MR_HTC_Europe_4.14.401.7_Radio_01.01_U114401011_117.00.61117G_2_F_release_490768_signed_2_4.zip
OTA:
OTA_HIMA_UHL_M60_SENSE70_MR_HTC_Europe_3.35.401.12-2.10.401.180_release_464237

sagros said:
Hi there ,
I'm having some troubles with flashing a new rom into my HTC M9.
Last week HTC "tried" to install android 7 via the automatic update in my phone. For some reason (might be because I bought my phone abroad) the installation failed and my phone booted back to its OS. I paid no attention to it (Wasn't that eager to upgrade)
a few days later after I tried to restart my phone, it decided to brick (just like that) and now I can only get as far as the boot menu when turning on my phone on.
My phone is S-on , and the bootloader it locked (quite inconveniently as I came to realize) and I am able to get to Download\Recovery\bootloader mode.
I found my CID and MID and double checked that the "androind-info" file in the RUU I downloaded suits them. But I keep receiving the message "footer is wrong signature verification failed".
To add to my enormous sorrow (I'm quite attached to my phone), I am not able to mount my internal SD even after performing "factory reset" and "cache format". At first I suspected the card is damaged but when I write "fastboot getvar all" in bootloader mode I can see that the partitions exist and have an address.
For some reason "adb" doesn't recognize my phone in "adb devices" unless I'm in "sideload mode" and I'm unable to launch "adb shell" or any "adb" function that is not "adb sideload"
Also I'm not able to update my firmware (OTA) because the phone keeps complaining that the firmware version doesn't match (I searched all over the web for "more fitting" firmware but couldn't fine one that would satisfy my phone).
I searched this forum (and the web) for an answer to my problem but couldn't find a solution to my problem.
To sum things up: S-on , bootloader locked + not able to unlock it with HTC's guide , can change to Bootloader\Recovery\Download mode but that's all (No custom recovery mode) , internal sd wouldn't mount though external sd would, "signature verification error" when trying to update my RUU.
Here is what "fastboot getvar all" gives me:
In bootloader mode:
(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:FA563YJ00838
in Download mode:
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei:
(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: 0PJA10000
(bootloader) cid: HTC__032
And this is the RUU and OTA I tried to flash (via fastboot, adb sideload , external sd):
RUU:
0PJAIMG_HIMA_UHL_N70_SENSE80_MR_HTC_Europe_4.14.401.7_Radio_01.01_U114401011_117.00.61117G_2_F_release_490768_signed_2_4.zip
OTA:
OTA_HIMA_UHL_M60_SENSE70_MR_HTC_Europe_3.35.401.12-2.10.401.180_release_464237
Click to expand...
Click to collapse
Download the 4.14.401.7 ota from flappy's thread and drop in on your external sd card.
Reboot your phone in to recovery and choose the option to apply the ota from external.
My missus's m9 wouldn't move from the splash screen after the official ota tried to install and this is how I fixed it.

squ89r97 said:
Download the 4.14.401.7 ota from flappy's thread and drop in on your external sd card.
Reboot your phone in to recovery and choose the option to apply the ota from external.
My missus's m9 wouldn't move from the splash screen after the official ota tried to install and this is how I fixed it.
Click to expand...
Click to collapse
Thanks for the quick reply. When I try to update the OTA from SD card I receive the message
"system partition has unexpected contents"
"E:Error in /sideload/package.zip"
I used the OTA
OTA_HIMA_UHL_N70_SENSE80_MR_HTC_Europe_4.14.401.7-3.35.401.32_release_490770.zip
that corresponds to my MID and CID
Any ideas ?

Fastboot is bootloader and download mode. Adb is recovery mode.
Rename the update to 0PJA10000 (zero, p, j, a, one, zero, zero, zero, zero). Transfer it to your phones internal sd via adb while the phone is in recovery mode (not download mode or bootloader), at the very first level of the memory (not in any folders at all, just in the sd itself) and reboot again to recovery.
It should auto flash.
Beamed in by telepathy.

shivadow said:
Fastboot is bootloader and download mode. Adb is recovery mode.
Rename the update to 0PJA10000 (zero, p, j, a, one, zero, zero, zero, zero). Transfer it to your phones internal sd via adb while the phone is in recovery mode (not download mode or bootloader), at the very first level of the memory (not in any folders at all, just in the sd itself) and reboot again to recovery.
It should auto flash.
Beamed in by telepathy.
Click to expand...
Click to collapse
Hi, thanks for the reply. I am unable to access my internal memory in "recovery mode" (or in general) and my only indication that it still works is the "fastboot getvar all" I posted in my root comment. adb doesn't recognize my phone in any mode other than "sideload mode" so I cannot "push" the file into my sd card. Renaming the file on my computer doesn't provoke auto flash when entering "recovery mode" but maybe it's because I cannot restart into recovery mode, only boot into "bootloader mode" and there use the "Boot To Recovery Mode" option.
Sorry for being so difficult, kinda tried not to mess up with it but it bricked nevertheless 0_o

Remove the pc adb drivers, put the phone into recovery mode and THEN connect it to the pc. Hopefully it should install the correct drivers. Failing that google "manually adding physical addresses to drivers". This involves editing the .cat file prior to installing the driver.
Your only other option other than that is the ruu.exe and I'm not sure if one exists yet.
Beamed in by telepathy.

shivadow said:
Remove the pc adb drivers, put the phone into recovery mode and THEN connect it to the pc. Hopefully it should install the correct drivers. Failing that google "manually adding physical addresses to drivers". This involves editing the .cat file prior to installing the driver.
Your only other option other than that is the ruu.exe and I'm not sure if one exists yet.
Beamed in by telepathy.
Click to expand...
Click to collapse
Hi , thanks for the reply. I tried to do what you suggested but neither my Windows nor my Ubuntu recognize my HTC when in recovery mode (outside "sideload" mode), guessing it's because I never enabled "USB debugging".
Moreover, I searched one more time for any Rom that could fit my phone , unfortunately I cannot find any .exe rom that fits my CID + has a version higher than 2.*
Wrote to HTC (though I doubt it would do anything) ... Are there any motivational words about not throwing out this phone and buying a new one ? I'm am quite convinced that the problem is in the software, but the way I see it now , HTC locked the phone quite strong \=

sagros said:
Thanks for the quick reply. When I try to update the OTA from SD card I receive the message
"system partition has unexpected contents"
"E:Error in /sideload/package.zip"
I used the OTA
OTA_HIMA_UHL_N70_SENSE80_MR_HTC_Europe_4.14.401.7-3.35.401.32_release_490770.zip
that corresponds to my MID and CID
Any ideas ?
Click to expand...
Click to collapse
Try taking the sd card out and putting it on the sd card that way?

squ89r97 said:
Try taking the sd card out and putting it on the sd card that way?
Click to expand...
Click to collapse
Hi , thanks for the reply. Not sure what you mean. I don't have any access to my internal sd card , so to apply your suggestion I had to pull out my ext. sd card and move the file to it via my computer, and only after that connect the ext. sd back it. The message I receive from my phone when trying to install the firmware is what I wrote earlier

sagros said:
Hi , thanks for the reply. Not sure what you mean. I don't have any access to my internal sd card , so to apply your suggestion I had to pull out my ext. sd card and move the file to it via my computer, and only after that connect the ext. sd back it. The message I receive from my phone when trying to install the firmware is what I wrote earlier
Click to expand...
Click to collapse
You do have access to an sd card, physically. Apologies if I wasn't clear, but I've not come across any instance of anyone taking out their built in storage! So you did indeed apply my suggestion correctly.
And if that's the message you get, I can't help any further. All the best.

Failed to boot download mode

Please help, very, very need firmware 4.16.118.3, or the file itself pulled "hosd.img".
Sorry for my english, but I read better than I write.

As far as I know HTC haven't released the nougat ruu for any M9's.
Beamed in by telepathy.

The 118 SKU doesn't seem to have a Nougat (4.x.xxx.xx) update. Where are you getting that version number?
If your goal is getting Android Nougat: Assuming your phone boots to Android, you may be able to achieve S-OFF via Sunshine, change your SKU and update to Nougat.
If your goal is fixing the download mode issue: a RUU associated with your SKU & OS version should set your phone straight. Could you post the output of the "fastboot getvar all" (be sure to remove the IMEI information)?

Android does not start, only works Bootloader and Recovery. Phone is T-mobile Poland.
First was Android 6.0 Marshmallow version number 3.35.118.12, then on February 25 she appeared update Android 7.0 Nougat version number 4.16.118.3.
After a week when I turn on the phone appeared application errors, then I made Wipe cache, after the phone hung up on the HTC logo and constantly reboot.
When I entered the Bootloader I saw that changed status ***Software status Modified**, phone all the time was ***Locked*** and ***S-ON***
C:\fastboot>fastboot getvar all
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(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:************
all:
finished. total time: 0.146s

That getvar all is the response from bootloader. You need to do that in download mode.
To save you the hassle I can tell you that your nand is corrupt and beyond repair. Only HTC can fix it.
"status modified" on a totally stock phone that wont boot means corrupt nand and as dead as a door stop.
Dead nands are becoming more and more popular it seems..
Beamed in by telepathy.

Thank you for your help, phone sent to the service.

shivadow said:
That getvar all is the response from bootloader. You need to do that in download mode.
To save you the hassle I can tell you that your nand is corrupt and beyond repair. Only HTC can fix it.
"status modified" on a totally stock phone that wont boot means corrupt nand and as dead as a door stop.
Dead nands are becoming more and more popular it seems..
Beamed in by telepathy.
Click to expand...
Click to collapse
What about a stock m9 which shows "status modified", does boot to Android, but does not boot to download or recovery modes (black screen with red text - "Failed to boot to download mode ..."). Is this also the sign of a corrupt NAND?
-Tim

LindwurmPL said:
Thank you for your help, phone sent to the service.
Click to expand...
Click to collapse
what problem about your phone? i have same problem too

TimR1 said:
What about a stock m9 which shows "status modified", does boot to Android, but does not boot to download or recovery modes (black screen with red text - "Failed to boot to download mode ..."). Is this also the sign of a corrupt NAND?
-Tim
Click to expand...
Click to collapse
Yes Tim, it can very well be a corrupt nand. The problem you have there is without download mode you can't flash any stock firmware to reset the device to what i call "stock stock". Only htc would be able to repair that.

[Solved] Bootloop issue on Stock phone. Possible to fix without loss of data?

Hi Everyone
Newbie here so please be gentle. I have a HTC One M9 that has gone into a permanent bootloop for no apparent reason. It happened yesterday. Noticed that my phone was a bit sluggish so I decided to restart it but it didnt completely restart and went into the boot loop. The only significant change that I can think of was that I updated HTC Senses via the play store a few days ago and this was the first time I have restarted the phone after that update.
I have not modified the phone in any way and has the stock rom installed. I can access the bootloader and recovery mode. Here is a dump of fastboot getvar all command:
With the phone in Bootloader screen
C:\Temp\AndroidApp>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
all:
finished. total time: 0.149s
With the phone in download mode:
C:\Temp\AndroidApp>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) version-main: 3.35.401.12
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440792_97.00.51203G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__001
all:
finished. total time: 0.047s
I do not have developer mode or USB debug enabled (wish I had enabled these before this happend!! )
I have tried to install an OTA update via the the 'Apply Update from SD card' method (from recovery mode) and tried to use the OTA_HIMA_UHL_M60_SENSE70_MR_HTC_Europe_3.35.401.32-3.35.401.12_release_487250.zip but I get an error after the 'verifying current system...' message which says:
System partition has unexpected contents E:Error in /sideload/package.zip
(Status 7)
Installation aborted.
Considering that I have not modified the phone in anyway, not sure why I am getting this error message as I was hoping that applying the OTA might fix the bootloop issue. If I was able to update using the OTA, would that have solved my issue? Is there any way of overcoming the Status 7 error?
Considering that I dont have developer mode enabled and USB debug enabled, is there any posibility to accessing the system files and flashing the system partition with a stock image without having to wipe personal data or do I have no choice but to do a factory reset, loose all my data and hope for the best? Any advice and step by step guide would be appreciated. Even if I can access my personal data on the internal drive and copy it somewhere else, that would be a result!
Many thanks
Rob

There is a very strong chance the nand has failed and the phone is dead.
How big is the file you're flashing?. It should be at least 2Gb. If it is less than 2Gb then it's the ota.
If the file is 2Gb or more then rename it to 0PJAIMG.ZIP,
copy it to the "external" sdcard,
boot the phone into download mode and you should see "press vol up to flash" in yellow at the bottom of the screen.
Press vol up and it will flash. (make sure your phone is plugged into a charger).
When it is complete it will auto reboot. Do not turn the phone off even if it looks 'frozen'. The process should take 5-10 minutes.

shivadow said:
There is a very strong chance the nand has failed and the phone is dead.
How big is the file you're flashing?. It should be at least 2Gb. If it is less than 2Gb then it's the ota.
If the file is 2Gb or more then rename it to 0PJAIMG.ZIP,
copy it to the "external" sdcard,
boot the phone into download mode and you should see "press vol up to flash" in yellow at the bottom of the screen.
Press vol up and it will flash. (make sure your phone is plugged into a charger).
When it is complete it will auto reboot. Do not turn the phone off even if it looks 'frozen'. The process should take 5-10 minutes.
Click to expand...
Click to collapse
Thanks you very much!!!
Phone is alive again thanks to your instructions. I had given up after trying different things. I tried flashing the RUU via fastboot but kept getting an error 9 (something to do with security). Even the factory reset option from the recovery menu wasnt working (it formatted, unpackaged and then rebooted into the boot loop) hence I gave up hope and bought a Nokia 8 as a replacement (Still prefer the M9 but I'll give the Nokia some time). If you had responded towards the begining of the week, you could have saved me £300
Any ideas why the factory reset option did not work considering that I had not modified the phone in any way? (S-ON, bootloader locked, no custom ROMS or recovery mods)
Thanks again for your help. :good:

Unfortunately I don't have time to monitor the forum and answer immediately, even if it saves someone a few quid.
Under the consumer rights act (UK) you can return the phone within the 2 week grace period for a no quibble money back. You don't need a reason. After 2 weeks the device must be faulty.
The factory reset didn't work because android is inherently broken. There is no real valid explanation at this stage but the android developers know about it but do not know how to fix it.
In all circumstances where issues are encountered flashing stock the ruu via zip should be on the cards as it fixes many things on htc phones.

I've got a
22 RU_HEADER_ERROR
22 RU_HEADER_ERROR
FAIL22 RU_HEADER_ERROR
.... Help ?

shivadow said:
There is a very strong chance the nand has failed and the phone is dead.
How big is the file you're flashing?. It should be at least 2Gb. If it is less than 2Gb then it's the ota.
If the file is 2Gb or more then rename it to 0PJAIMG.ZIP,
copy it to the "external" sdcard,
boot the phone into download mode and you should see "press vol up to flash" in yellow at the bottom of the screen.
Press vol up and it will flash. (make sure your phone is plugged into a charger).
When it is complete it will auto reboot. Do not turn the phone off even if it looks 'frozen'. The process should take 5-10 minutes.
Click to expand...
Click to collapse
Thanks. Do you know any other way to do that without sd card?