Develop Bugs

Problem with my HTC One M8 with ROMs?

I have tried to install a new custom ROM on my HTC One M8.
It has a unlocked bootloader, it's unlocked, rooted, and i've had InsertCoin and Paranoid Android, and CyanogenMod on it.
My device is S-ON.
However, lately I have not been able to update to any of the newer roms.
The ROMs that I have tried to install are:
HTC_One_(M8)_-_MaximusHD_11.0.0
insertcoin-m8_5.0.3_ART
ViperOneM8_4.2.0_v2
And none of them work except for
pa_m8-4.45-20140729
which is always my go-to ROM right now when the others fail so I don't soft brick it.
I do have a Nandroid in case everything goes to hell.
But my question is, what is wrong with my device and why can't I update to another ROM? It gets stuck at the HTC White Logo screen every single time with every ROM that fails.
Thanks!

technocrat7 said:
But my question is, what is wrong with my device and why can't I update to another ROM? It gets stuck at the HTC White Logo screen every single time with every ROM that fails.
Thanks!
Click to expand...
Click to collapse
You have old hboot and firmware version.
All the newer Sense based ROM require hboot no less than 3.19.0000
What's your fastboot getvar all - post here minus serial no. & imei no.
Maybe lollipop OTA already available for your device region.

(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331931.LA24G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.57.531.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: T-MOB010
(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: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Here is my information on my phone, so it would seem that I am outdated. How would I get back up to date?

Here is the RUU for your device version : http://forum.xda-developers.com/showpost.php?p=58771521&postcount=4593
This will update your device to the latest lollipop 4.20.531.4
1. put your device in bootloader/fastboot mode and connect to PC
2. run command to relock bootloader
fastboot oem lock
fastboot reboot-bootloader
3. Right click the RUU exe that you downloaded, select "run as administrator" .. wait for it to run, later there is a dialog box, accept, next, next, update, blablabla until it finish and your device rebooted... done.
Note : this will wipe everything on your internal storage. Make a backup of important files before you proceed.
Then if you want to install custom ROM again, re-unlock bootloader & install any custom recovery that you like.

Thanks! I did what you said, then this happened:
C:\adb>fastboot oem lock
...
(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 (Too many links))
finished. total time: 1.127s
Is this supposed to happen?
it says RELOCKED at the top though

technocrat7 said:
Is this supposed to happen?
it says RELOCKED at the top though
Click to expand...
Click to collapse
Yep ... just proceed to install RUU (step 3)

Okay thank you, Also I wanted to ask you, how exactly did you find my RUU?
I saw the cidnum was TMOBO010 or whatever it was, but how exactly did you use that to find my RUU?
Thanks again for the help, much appreciated

(bootloader) version-bootloader: 3.16.0.0000
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: T-MOB010
These are the 3 items that important to check what you need.
I don't really need to search for it because I'm always around in this thread : http://forum.xda-developers.com/showthread.php?t=2701376
and it happens that I just helped other person there with more or less same problem as yours.
BTW ... please remove those sensitive data (serial no. & imei no.) from your post above.

I did what you asked.
And okay I will keep that in mind
**EDIT**
Also, do I need to "re unlock" my phone? Or can I just do "fastboot oem unlock" because I have once before unlocked it?
This IS a relock right?

technocrat7 said:
Also, do I need to "re unlock" my phone? Or can I just do "fastboot oem unlock" because I have once before unlocked it?
This IS a relock right?
Click to expand...
Click to collapse
No .. you need to unlock it with the unlock_code.bin that you received from HTCDev when you first unlock your device.
If you don't have it, reapply a new one.

I see, okay I unlocked it again.
While I'm at it, I wanted to ask one final question that's been bugging me for a while now.
When I got to my Philz recovery and do "factory wipe" why doesn't it actually wipe my data?
I want ALL of my data, ROM, apps, everything to be gone, but it doesn't do that.
Is there an alternative?
Is there no way to remove all user data/apps?

I don't use Philz recovery so not sure how to help you. Maybe try an older version 6.26.6
I use only TWRP and now your device already updated to 5.0.1; you need to use TWRP 2.8.4.0 or the latest 2.8.5.0

Okay I am on TWRP, how do I do a factory reset on TWRP?
and what exactly will it do?
I just hope it'll actually wipe everything when I factory reset it. Or else I don't see a point of even having a factory reset option

It's all depends on what you want to do.
Factory reset - to prepare your device to install next ROM, it wipes user data, cache, dalvik cache
I always prefer - wipe menu - advance - select data, cache, dalvik, system - this wipe everything except internal storage.
To wipe data and internal storage - wipe menu - advance - format data - yes
I got to go now ... bed time

Thank you that's all I needed to know.
I appreciate the help, goodnight!

technocrat7 said:
Thank you that's all I needed to know.
I appreciate the help, goodnight!
Click to expand...
Click to collapse
No problem ... and it's already good day here

Haha I see.
Do you know any information on the OnePlus?
I made a post there, however it's not a very active forum.
Sent from my HTC One_M8 using XDA Free mobile app

No idea about any other brand phone ... I use only HTC since 2008 when I first registered with XDA with my first HTC Elf

Haha interesting, I started with the Droid DNA being my first HTC device, and that thing was so bad it almost never make me want to go HTC again. But I got my M7
And staying on topic... If you have a different kernel on your device, would you still be able to RUU it? Or would you have to revert the kernel back?
Sent from my HTC One_M8 using XDA Free mobile app

RUU - no need
OTA - need to revert to stock kernel/modules if modules are changed. If modules are stock, then no need

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.

M9 s-on/bootloader unlocked bricked

Hello, today i saw a good deal for a HTC M9. In advertisement photos were showing that it's stuck on bootloader, i thought nothing hard to rewrite stock rom and use it again, but now im facing some problems:
***Software status: Modified ***
***Unlocked ***
***S-ON ***
REBOOT
REBOOT TO BOOTLOADER
BOOT TO DOWNLOAD MODE
BOOT TO RECOVERY MODE
POWER DOWN
That is all I can see in this phone, previous owner said that it started rebooting while installing official update via usb cable, i cant tell if its true, but now i cant get in fastboot mode, if i choose BOOT TO RECOVERY or DOWNLOAD MODE phone only starts rebooting with black screen and HTC silver letters in that screen and some red words in the bottom of the screen.
Cant tell what CID or MID it is, but i found a blackfire research sticker on the original its box, so i guess it was sold in USA, and thats all.
fasboot getvar all shows only this:
C:\Users\Vartotojas\Desktop\Minimal ADB and 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:FA568YJ00385
all:
finished. total time: 0.158s
Can you guys tell me what to do to get this perfect aluminium bar working?

Send it to HTC and let them repair it. That's the dead nand issue (c.f. the FAQ of the ReadMe thread) - a hardware issue.
Sent from my HTC One M9 using XDA Labs

Flippy498 said:
Send it to HTC and let them repair it. That's the dead nand issue (c.f. the FAQ of the ReadMe thread) - a hardware issue.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Dont know if Lithuania has HTC repair center.. So you telling me that there is no DIY repair? Only way to do it myself is to find a cracked screen working m9 motherboard and to replace it?

There haven't been any reports about successful repairs of such dead nand phones, yet, aside from those cases in which the owners sent their phone to HTC.
However, that doesn't mean that a DIY repair is impossible. Therefore, if you successfully repair your phone it would be nice if you contribute a little guide to the community.
Sent from my HTC One M9 using XDA Labs

M9 is hanging in a bootloop

Hi all,
I'v really a big problem , my M9 is hanging in a bootloop.
My last installed ROm was a ViperOneM9 6.1.0. I used it for around 2 month. But from one day to the next my phone is in a bootloop.
Now it won't boot into the download boot (TWRP 3.0.2 is installed ), it won't boot into recovery mode (bootloop) ant it won't boot.
The only mode that is possible is the Bootloader mode.
I tried to flash with the fastboot command. I tried different 0PJAIMG files but I got allways the same error message:
C:\adb>htc_fastboot.exe flash zip 0PJAIMG_HIMA_UHL_L50_SENSE70_Vodafone_CH-DE_1.32.166.6_R1_Radio_01.01_U11440261_56.01.
50303G_3_F_release_425117_signed.zip > error.txt
sending 'zip'... (126768 KB) OKAY
writing 'zip'... FAILcannot flash this partition in s-on state
FAILED (remote: cannot flash this partition in s-on state)
Software status is modified
*** Unlocked ***
*** S-ON ***
*** Security warning ***
and fastboot getvar all:
C:\adb>htc_fastboot.exe 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:FA58XXXXX
all:
Execution time is 146(ms)
It'll be great if someone could help me
thx

That's the dead nand issue (c.f. the FAQ of the ReadMe thread).
Sent from my HTC One M9 using XDA Labs

I have the same problem.Its just restart,i didnt have any problems before .I cant now go in download ,or recovery mode.I had twrp recovery installed. When try downoad mode,its just says to me failed to boot to download mode . Any solutions for that NAND issue ,how Flippy498 says ?

As said before, read the FAQ of the ReadMe thread. It's already explained there.

Same problem but I'm not rooted...
HTC One M9 Sprint, stuck in boot loop
I just checked the Dead NAND post in the FAQ... matches my issue too.
Q17: My phone is completely stock and started bootlooping during normal usage. Now I can only enter the Bootloader since I face booting errors as soon as I try to enter the Download Mode or the Stock Recovery. How can I fix this problem?
A: This seems to be another symptom of the NAND death (c.f. the black download mode error screen in Q8). So far, it's not fixable without HTC's help. In other words: You need to send your phone to HTC's repair service if you want to keep it.

HTC M8 eye with official rom stuck in fastboot

Hey guys
Last night my phone(HTC m8 eye 5.07.401.1) slowed down badly, after a while it restarted automatically and fastboot screen showed up.
Things I've tried:
1-Restarting the phone after fully charging it for 1 billion times (worked once but the phone was frozen and restarted automatically again)
2- Trying to unlock the boot loader(Got the unlock_code.bin file, tried to load it to the phone using adb, it said success or done or something like that but nothing changed)
3-Trying to flash the official rom , didn't work
4-removing the SIM and SD card and restarting the phone, didn't work
by the way, usb debugging was not active last time the phone was working normally, Also the phone have not experienced any unusual activity like rooting or flashing custom roms or...
What can I do?
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: INVALID_VER_INFO
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.07.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA00000000000
(bootloader) imei: 3580000000000000
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: mels_tuhl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B81000
(bootloader) cidnum: HTC__J15
(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: 5c9466dd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.039s
------------------------------------------------------------------------------------------- fastboot results----------------------
C:\fastboot>fastboot devices
FA57LY901038 fastboot
C:\fastboot>fastboot oem rebootRUU
...
(bootloader) Error: Command never completed
(bootloader) Error: Command timeout error
(bootloader) Error: Command completed with errors
(bootloader) Failed Reading block @ 786432
(bootloader) [SD_ERR] sd_read_sector: read sector failed (786432 256)
(bootloader) [ERR] partition_read_emmc(589): error -1
(bootloader) Start Verify: 3
(bootloader) Error: Command never completed
(bootloader) Error: Command timeout error
(bootloader) Error: Command completed with errors
(bootloader) Failed Writing block @ 786432
(bootloader) [SD_ERR] sd_write_sector: write sector failed (786432 256)
OKAY [ 10.041s]
finished. total time: 10.041s
C:\fastboot>fastboot flash zip update.zip
target reported max download size of 1826332672 bytes
sending 'zip' (1687274 KB)...
OKAY [ 57.179s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 118.969s
---------------------------------------------------------------------------------------

I don't have the "eye", only the "standard" M8, but I'll try to help as much as I can, as far as anything that I believe is common between the two M8 versions (unlocking bootloader, flash RUU, etc.).
bahmaniq said:
2- Trying to unlock the boot loader(Got the unlock_code.bin file, tried to load it to the phone using adb, it said success or done or something like that but nothing changed)
Click to expand...
Click to collapse
So the bootloader screen says LOCKED? I assume that is what you mean by "nothing changed", but I want to be clear on this.
bahmaniq said:
3-Trying to flash the official rom , didn't work
Click to expand...
Click to collapse
What is the exact file name? It's best to provide specific file name/version info when asking for help. I've seen a lot of cases where the person "thought" they were flashing the right RUU, but in fact, it was not even the right one.
But based on what you've described so far (bootloader will not unlock, RUU will not run, emmc error) it sounds like a hardware emmc failure.

redpoint73 said:
So the bootloader screen says LOCKED? I assume that is what you mean by "nothing changed", but I want to be clear on this.
Click to expand...
Click to collapse
Yes, *****LOCKED***** it says, I guess it is very serious on this one. Based on knowledge I gathered in these 2 days, I think it should show a black confirmation screen after I try to unlock it (using *.bin file), but it simply does not.
redpoint73 said:
What is the exact file name? It's best to provide specific file name/version info when asking for help. I've seen a lot of cases where the person "thought" they were flashing the right RUU, but in fact, it was not even the right one.
Click to expand...
Click to collapse
Yes you are right, RUU is the most important part and I did not elaborate. There is a big chance that the RUU is the Achilles Heel!! Exact file name is: 0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed
redpoint73 said:
But based on what you've described so far (bootloader will not unlock, RUU will not run, emmc error) it sounds like a hardware emmc failure.
Click to expand...
Click to collapse
So, that's it, I'm gonna play "One last goodbye" and let the history judge. 2 years of EMERGENCY CALLS ONLY, 2 years of zero antenna...
After a silent peaceful night
You took my heart away
oh I wish, I wish you could have stayed

bahmaniq said:
Yes you are right, RUU is the most important part and I did not elaborate. There is a big chance that the RUU is the Achilles Heel!! Exact file name is: 0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed
Click to expand...
Click to collapse
That is not the RUU for the M8 eye. It's the RUU for the "regular" Euro M8. That is why you have signature error. Not sure where you can find the RUU for the "eye".
One more questions, is the phone going to fastbootRUU mode after running the command: fastboot oem rebootRUU
The error "command never completed" would suggest NO. But I'm curious whether the phone actually goes to RUU mode or not. RUU mode is signified by a black screen with large HTC logo. A progress bar will also appear below the logo, when the RUU starts to install. But in your case, you my have not gotten far enough for the progress bar to appear.
If the phone does not in fact even go to RUU mode due to emmc error, then it is probably irrelevant whether you have the right RUU or not. You will not get the RUU to run, if you can't even enter RUU mode.

redpoint73 said:
That is not the RUU for the M8 eye. It's the RUU for the "regular" Euro M8. That is why you have signature error. Not sure where you can find the RUU for the "eye".
One more questions, is the phone going to fastbootRUU mode after running the command: fastboot oem rebootRUU
The error "command never completed" would suggest NO. But I'm curious whether the phone actually goes to RUU mode or not. RUU mode is signified by a black screen with large HTC logo. A progress bar will also appear below the logo, when the RUU starts to install. But in your case, you my have not gotten far enough for the progress bar to appear.
If the phone does not in fact even go to RUU mode due to emmc error, then it is probably irrelevant whether you have the right RUU or not. You will not get the RUU to run, if you can't even enter RUU mode.
Click to expand...
Click to collapse
It has been a long time since the last time I was here but the problem is not solved. Sorry for the delay, and No the black screen with HTC logo does not appear.
Is there anything I can do to get rid of this fastboot screen? or the phone is useless