Develop Bugs

Can't boot into recovery/OS, only hboot/fastboot works

So..
The patient:
A completely stock HTC Desire Z.
Code:
VISION PVT SHIP S-ON
HBOOT-0.85.0013
MICROP-0425
RADIO-26.10.04.03_M
eMMC-boot
Apr 11 2011,23:36:27
What happened?
Got home, and connected the phone to my computer via USB cable to charge, as I do every time.
However this time I have also launched and forgot to exit Blizzard Authenticator app (I'm a Diablo 3 fan )), which, as I have previously noticed, causes a garbage collection extremely often (only by displaying a progress bar which is constantly moving).
There were two times previously where I left this app open and after an hour or so the phone automatically rebooted itself.
So.. it happened again: I noticed a brief vibration from the phone, as it does when it starts to boot and shows the HTC logo. So I took it in the hand to see what's happening and it was extremely hot, and after a few seconds of showing the HTC logo it rebooted, then showed HTC logo again, rebooted, and looped until I pulled the battery out.
I thought it must have some thermal protection which tries to save the phone from overheating and is constantly shutting it off. So I pulled the battery out and left it to cool-down.
After that - same thing, when you put in the battery and push the power button (or connect a USB cable), it displays the HTC logo for a few seconds and then reboots, starting a boot loop.
So, the summary:
The phone will only boot to hboot while holding down the VOLUME DOWN button.
It won't boot into recovery if I select it from the hboot/fastboot menu. It does exactly the same (boot-looping).
hboot/fasboot works perfectly fine, I am able to interact with the phone while in fastboot USB mode.
I was able to use stock RUU, it flashed everything fine, not a single error, but the result was the same - still boot-looping.
I was able to upgrade hboot and unlock the bootloader via htcdev.com and successfully flash the ClockWorkMod recovery, but still I am not able to boot to it because of boot-loop.
I tried flashing official ROM from RUU by using fastboot oem rebootRUU so that I could see what's actually happening, expecting that I ran into the same issue as a few other people on this forum (the "re-flush image immediately" issue, where the zip must have been flashed multiple times before succeeding), but no, the ROM flashed perfectly fine. And still the same result: boot loop.
So, after two days of browsing, reading, searching and trying I finally ran out of ideas.
Here goes some additional info, if it could prove useful while diagnosing the problem:
Code:
FROST:~ frost$ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 0.85.0013
(bootloader) version-baseband: 26.10.04.03_M
(bootloader) version-cpld: None
(bootloader) version-microp: 0425
(bootloader) version-main: 2.42.405.2
(bootloader) serialno: SH0*********
(bootloader) imei: ***************
(bootloader) product: vision
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PC1011000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: low
(bootloader) battery-voltage: 3570mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 81c588a7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.003s
Code:
FROST:Downloads frost$ fastboot oem boot
...
(bootloader) setup_tag addr=0xA0000100 cmdline add=0x8D0878FC
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:smi ok, size = 0
(bootloader) TAG:hwid 0x0
(bootloader) TAG:skuid 0x25209
(bootloader) TAG:hero panel = 0xF
(bootloader) TAG:engineerid = 0x4
(bootloader) MCP dual-die
(bootloader) MCP dual-die
(bootloader) TAG:mono-die = 0x0
(bootloader) Device CID is not super CID
(bootloader) CID is HTC__Y13
(bootloader) setting->cid::HTC__Y13
(bootloader) serial number: SH0*********
(bootloader) commandline from head: no_console_suspend=1
(bootloader) command line length =497
(bootloader) active commandline: board_vision.disable_uart2=0 board_visio
(bootloader) n.usb_h2w_sw=0 board_vision.disable_sdcard=0 diag.enabled=0
(bootloader) board_vision.debug_uart=0 smisize=0 userdata_sel=0 androidbo
(bootloader) ot.emmc=true androidboot.baseband=26.10.04.03_M androidboot
(bootloader) .cid=HTC__Y13 androidboot.batt_poweron=good_battery androidb
(bootloader) oot.carrier=HTC-Nor androidboot.mid=PC1011000 androidboot.ke
(bootloader) ycaps=qwerty androidboot.mode=normal androidboot.serialno=SH
(bootloader) 0********* androidboot.bootloader=0.85.0013 zygote_oneshot=o
(bootloader) ff kmemleak=off no_console_suspend=1
(bootloader) aARM_Partion[0].name=misc
(bootloader) aARM_Partion[1].name=recovery
(bootloader) aARM_Partion[2].name=boot
(bootloader) aARM_Partion[3].name=system
(bootloader) aARM_Partion[4].name=cache
(bootloader) aARM_Partion[5].name=userdata
(bootloader) aARM_Partion[6].name=devlog
(bootloader) aARM_Partion[7].name=pdata
(bootloader) partition number=8
(bootloader) Valid partition num=8
(bootloader) jump_to_kernel: machine_id(2245), tags_addr(0x4000100), kern
(bootloader) el_addr(0x4008000)
(bootloader) -------------------hboot boot time:15618 msec
* the phone reboots at this point, so naturally, USB connection is lost, causing the output below: *
Code:
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
finished. total time: 8.358s
Any ideas of what's causing this? And/or how to fix this?
Thanks in advance.

* bump *

same problem here i just rebooted my phone and now im stuck. ive tried to flash a stock rom and it flashed successfully but wont boot to it.

Do you know if you had the bad nand ship
Sent from my Xoom using xda app-developers app

Warbuff said:
Do you know if you had the bad nand ship
Sent from my Xoom using xda app-developers app
Click to expand...
Click to collapse
Bad NAND chip? How could I determine that? By serial number? If so, how can I get the serial number via fastboot?
Is there any methods/logs to actually check the NAND chip for faults? Because as I said, I didn't get a single read/write error while flashing recovery/rom or booting, other than automatic reboot.

Unfortunately you don't seem to be able to use adb. Here's more info on the nand corruption problem http://forum.xda-developers.com/showthread.php?t=1051995
Also I suspect that you weren't able to fastboot flash the recovery because you don't have true s-off. Hopefully somebody with more info chimes in
Sent from my HTC Vision using xda app-developers app

Warbuff said:
Unfortunately you don't seem to be able to use adb. Here's more info on the nand corruption problem http://forum.xda-developers.com/showthread.php?t=1051995
Also I suspect that you weren't able to fastboot flash the recovery because you don't have true s-off. Hopefully somebody with more info chimes in
Sent from my HTC Vision using xda app-developers app
Click to expand...
Click to collapse
Thanks for the info, I will follow their progress on this issue.
Yes, I am not able to use adb since I cannot boot to recovery, so all I have is fastboot.
And.. well, I was In fact able to flash the recovery, it didn't throw any errors at all, while flashing, and returned "OK".
Also I cannot boot into recovery, it keeps doing exactly the same as booting into the OS - boot looping. And it does not matter if I flash the stock recovery via RUU or try ClockWorksMod, they both flash fine, but the end result is the same - boot looping.

Just send it to HTC its makes it easier

Since it's not rooted, send it to HTC, they will fix it/ send you a new one free of charge.
Sent from my HTC Vision using xda app-developers app

Ditto
Exactly the same problem here, thought it was just me and now I find loads of people talking about it. Unfortunately being well over a year out of the 1 yr warranty I think there is effectively 0% chance HTC will do anything about it unless they have a pile of the phones laying around in a warehouse they want to get rid of. I should be so lucky.
As more and more people go to buying phone direct rather than through their carrier I think this is an opportunity for manufacturers to distinguish themselves by offering longer warranties. Yeah I know they are a volume based business so it is not in their interests for people to be holding onto phones for years and years, but I think people might actually pay attention, and there is always the resale market who might appreciate a longer warranty. Again manufacturers would probably rather you bought a new one rather than a used phone - however the ability to resell your phone does encourage people to upgrade sooner than they might otherwise have done.

I've sent mine to the HTC, they did not tell, what's exactly wrong with the phone, but they have replace the logic board.
With the warranty void/expired, I can see a couple of options:
1) Find a logic board on the net (eBay, for example) and replace it yourself (not that big of a deal, really)
2) Leave a job to some phone service shop, in case you really want to keep the phone. This could be costly, though.
After my phone was repaired, I've realized that every single HTC phone I have previously owned was flawed in one way or the other.
HTC Tornado - Windows Mobile: the joystick controller started malfunctioning and the windows mobile OS was giving me brain cancer.
HTC Magic - Android: Logic board failed after half a year of ownership. The phone won't turn on.
HTC Hero - Android: Touch screen digitizers were flawed, after some time, lower part of the screen won't register touches. Had to change two of the damn things myself.
HTC Desire Z - Android: logic board failed on 100% stock device, never been flashed, never was dropped, never got wet.
After selling Desire Z I've bought a Samsung Galaxy Nexus and I'm a happy owner of it ever since. Not a single issue with it. Very satisfied. Will try to avoid HTC, even though HTC One might look like a quality phone, I'll stick to Samsung in the future.

Update on my exchange with HTC
I reported my problem to HTC and after a couple of messages each way I got this:
I'm sorry to hear that your G2 is still not powering on properly. Where this is the case, I have to be the bearer of bad news. This phone is classified as an End of Life device. This means that we no longer have the means to repair this phone.
I apologize that I am unable to help you further with this Simon. There may be a local repair shop in your area that may be able to help you with this.
Thank you again for being a valued part of the HTC family. Have a great day!
Click to expand...
Click to collapse

Eureka
I'm pleased to report that today I grabbed my G2 as I was clearing off my desk where it has been languishing for 18 months now. I'd had the exact same problem detailed in this report and failed in all attempts to get it going again. Emails with HTC also drew a blank since they told me the G2 was end-of-life and could do nothing to help me.
On a whim instead of throwing it in the trash along with the two Li-ion batteries I decided to try booting it. Too my surprise it did boot and I was able to recover the device, update all the apps and it is now fully functional. Unbelievable! Maybe there was some capacitor that needed to drain completely, or maybe something weird happened in the last 18 months. Either way I don't care, it's good to have my G2 bac and it is still a great phone. I love that keyboard even if I loved the G1 keyboard even more!
So I'm not keeping it for use without a SIM as the remote for my TV, DVR and a Chromecast client. All the apps I need for Chromecast work perfectly on it - NetFlix, YouTube, Google Music, etc. etc.

[Q] [Q&A]How big is this issue?

I'll start with a little background, then I'll get to the point. I got a "Verizon" HTC One M7 from ebay. It had a cracked screen, but it was in pretty fine working condition. I took it to a shop to have the screen replaced because it looked a little too complicated for me. Got it back and noticed it didn't have any reception when I charged it back up. Flashed a new ROM and radios, but still no reception.
My problems multiplied once I attempted to downgrade to see if that would revive the reception. I ended up sending it to jtag because I bricked it in the process. Fast-forward to today where I have my phone back, in working condition, somewhat, but no reception. I'm told that it has a GSM board, not CDMA. It was advertised as a Verizon phone and had a signal when I got it. Possibly switched at shop...I don't know.
Now, all I want to do is get a working phone. How do I proceed to get it working so that I can, at the very least, sell a working phone to get one that I can flash to PagePlus?

Go to about phone and check the software information. Post a screenshot of that.

Ok...here's what I have...

Go into fastboot mode and use the fastboot get-var all command and post that as well. That might be able to tell for sure if it is gsm or not. If it is you won't be able to get a signal at all with Verizon. On the plus side you should be able to flash the correct firmware for that board and sell that phone to someone else as a gsm phone. It should work just fine on gsm as long as the correct firmware is flashed.

C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.13.41.0421
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA**********
(bootloader) imei: 99000**********
(bootloader) meid: 9900**********
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: 22222222
(bootloader) battery-status: good
(bootloader) battery-voltage: 4094mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.062s
C:\adb>

Fastboot flash this firmware and you might be good to go again. http://www.androidfilehost.com/?fid=23329332407570630

disconnecktie said:
Fastboot flash this firmware and you might be good to go again. http://www.androidfilehost.com/?fid=23329332407570630
Click to expand...
Click to collapse
Are these the commands i need?
fastboot oem rebootRUU (this puts the device in RUU mode)
fastboot flash zip firmware.zip (rename file to firmware.zip)
Just want to make sure I don't flub this up...

Yes and you can find those instructions in the stock Rom radio thread of santods for future reference.

disconnecktie said:
Yes and you can find those instructions in the stock Rom radio thread of santods for future reference.
Click to expand...
Click to collapse
Ok...still no signal. I used an active PagePlus sim card and there is no change. I'd like to try a gsm rom to see if it works...again, I don't want to mess this phone up again...

trojanbrutha said:
Ok...still no signal. I used an active PagePlus sim card and there is no change. I'd like to try a gsm rom to see if it works...again, I don't want to mess this phone up again...
Click to expand...
Click to collapse
Try ViperOne 7.0.1 it has all the apns you would need.
Sent from my HTC6500LVWBLU using XDA Free mobile app

Can a cdma ROM be flashed onto a gsm board?
Sent from my DROID BIONIC using Tapatalk

Question...I noticed the problem that I have started after I had my screen replaced...could this be an issue with the lack of cell reception?
Sent from my HTC6500LVW using Tapatalk

repair shop may have not connected the antenna cables.

So, after thinking about this whole thing for a while, I decided to call Verizon to find out if the cell shop pulled a switch-a-roo on me with the motherboard. The guy tells me that my IMEI is not compatible with the vzw network. Now I want to know what HTC has to say about it. I call them and I'm told it's a vzw phone...and IT'S STILL UNDER WARRANTY!:highfive: Of course, he walks me through a factory reset and questions me about htcdev account. I'm mostly truthful about it and explain about the replacement screen...he's undeterred about that...asks if I can relock my bootloader...I say yes :good: So, now I'm thinking faux bootloader, but I think I should just ruu down...

trojanbrutha said:
So, after thinking about this whole thing for a while, I decided to call Verizon to find out if the cell shop pulled a switch-a-roo on me with the motherboard. The guy tells me that my IMEI is not compatible with the vzw network. Now I want to know what HTC has to say about it. I call them and I'm told it's a vzw phone...and IT'S STILL UNDER WARRANTY!:highfive: Of course, he walks me through a factory reset and questions me about htcdev account. I'm mostly truthful about it and explain about the replacement screen...he's undeterred about that...asks if I can relock my bootloader...I say yes :good: So, now I'm thinking faux bootloader, but I think I should just ruu down...
Click to expand...
Click to collapse
Don't forget to fastboot oem writecid VZW__001 (two underscores). Your cid is all 2s.
Sent from my One using XDA Free mobile app

Uzephi said:
Don't forget to fastboot oem writecid VZW__001 (two underscores). Your cid is all 2s.
Sent from my One using XDA Free mobile app
Click to expand...
Click to collapse
Done...do I need to go S-On or does it matter much?

trojanbrutha said:
Done...do I need to go S-On or does it matter much?
Click to expand...
Click to collapse
I did when I did my screen replacement. Be sure you are completely stock and **locked** not **relocked**.
Sent from my One using XDA Free mobile app

Uzephi said:
I did when I did my screen replacement. Be sure you are completely stock and **locked** not **relocked**.
Sent from my One using XDA Free mobile app
Click to expand...
Click to collapse
I'm in the process of going back to stock and while I was running the ruu that was somewhat successful, the following is what I saw that failed...
(bootloader) start image[sbl1-1] unzipping & flushing..
(bootloader) [RUU]UZ,sbl1-1,0
(bootloader) [RUU]UZ,sbl1-1,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) start image[sbl1-2] unzipping & flushing..
(bootloader) [RUU]UZ,sbl1-2,0
(bootloader) [RUU]UZ,sbl1-2,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) start image[sbl1-3] unzipping & flushing..
(bootloader) [RUU]UZ,sbl1-3,0
(bootloader) [RUU]UZ,sbl1-3,100
(bootloader) signature checking...
(bootloader) [RUU]WP,sbl1-3,0
(bootloader) [RUU]WP,sbl1-3,100
(bootloader) ...... Successful
(bootloader) start image[sbl1-4] unzipping & flushing..
(bootloader) [RUU]UZ,sbl1-4,0
(bootloader) [RUU]UZ,sbl1-4,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) start image[cir] unzipping & flushing...
(bootloader) [RUU]UZ,cir,0
(bootloader) [RUU]UZ,cir,100
(bootloader) ...... Successful
Click to expand...
Click to collapse
Now it's just stuck trying to activate. All I need to do now is a factory reset and lock the bootloader and s-on. I was just curious about what didn't work or what failed in the ruu...

trojanbrutha said:
I'm in the process of going back to stock and while I was running the ruu that was somewhat successful, the following is what I saw that failed...
Now it's just stuck trying to activate. All I need to do now is a factory reset and lock the bootloader and s-on. I was just curious about what didn't work or what failed in the ruu...
Click to expand...
Click to collapse
Normal for secondary bootloaders to not update. Especially when s-off.

HTC One M8 bootloop after RUU

Hi, I just got HTC One M8 stuck on black HTC logo with four triangles. To solve this I flashed official RUU but phone was still on bootloop. Now It's on white htc screen, I can boot recovery and bootloader. Flashed firmware and RUU - nothing changes.
BOOTLOADER : LOCKED
S-ON
I add my getvar :
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.401.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__002
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Could it be hardware issue? Thanks in advance!

What RUU did you flash (full file name) and did it run to completion, and were there any error messages?

I flashed RUU : 0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4 _Radio_1.29.214500021.12G_20.72.4196t.01_release_4 64360_signed.zip
There was no errors, only FAIL90 hboot pre-update! please flush image again immediately. Please help me to find solution. Thanks in advance!

clocklock said:
There was no errors, only FAIL90 hboot pre-update! please flush image again immediately. Please help me to find solution. Thanks in advance!
Click to expand...
Click to collapse
This is common, and means you should flash the RUU again (pretty sure its supposed to say "flash image again immediately" - even though it says "flush"). Did you try to do so?

After that error it flashes image again by itself. After 8-10 min it says that everything is ok. Then i restart and get same bootloop. Maybe I'm using wrong RUU? My HTC is European version

clocklock said:
After that error it flashes image again by itself. After 8-10 min it says that everything is ok. Then i restart and get same bootloop. Maybe I'm using wrong RUU? My HTC is European version
Click to expand...
Click to collapse
It should be the right RUU. You're using htc_fastboot to flash? Maybe try downloading the RUU again, and flash again.

I flashed with htc_fastboot and used image from : https://www.androidfilehost.com/?fid=24369303960687057. Tried two times, same results. Don't know what to do next.

clocklock said:
Hi, I just got HTC One M8 stuck on black HTC logo with four triangles.
Click to expand...
Click to collapse
How exactly did this happen, where you doing something at the time? Was there any significant type of update to the phone recently? Or you just picked up the phone and it was stuck this way?

I bought it with the note that motherboard is faulty. But I thought that It's only bricked somehow. Previous owner said that he saw an error and phone shut down itself. No water damage or etc. Maybe really It is faulty logic board?

clocklock said:
I bought it with the note that motherboard is faulty. But I thought that It's only bricked somehow. Previous owner said that he saw an error and phone shut down itself. No water damage or etc. Maybe really It is faulty logic board?
Click to expand...
Click to collapse
Its the correct RUU, and I don't see any other reason why the RUU wouldn't work. Correct RUU not getting a stock device to run is a good indication that its a hardware failure. Especially since it seems the previous owner was just using the phone (assuming no recent updates or other major changes), and it shut down, and hasn't worked since; again that to me would point to hardware failure.
If you've got nothing to lose, you can try to unlock the bootloader, install TWRP and flash a ROM, and see if the condition improves at all. But my guess would be no.

How to unlock bootloader with developer options disabled? I tried to do it but it still shows that bootloader is locked. I used htcdev webpage. Any other solutions?

clocklock said:
How to unlock bootloader with developer options disabled? I tried to do it but it still shows that bootloader is locked. I used htcdev webpage. Any other solutions?
Click to expand...
Click to collapse
You don't need developer's options (debugging) enabled to unlock the bootloader. Its done by fastboot, which doesn't require debugging.
If you went through the full process at HTCDev.com with obtaining an unlock bin token, and flashed the token with fastboot per the instructions, and its still locked; then its another indication that you are looking at a hardware failure (like bad emmc).

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.

Bricked M9?

Hello to all. I've read many similar issues but I could not solve my problem.. I have a problem with a m9 no brand .. a technical taker has done damage and now I have expensive paperweight in my hands. there is no valid bootloader, no download mode, no recovery mode .. by fastboot i tried getvar all and i
C: \ adb3> 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) serial: FA578YJ00870
all:
finished. total time: 0.153s
I do not know if it is European, American or other, I don't know where to look .. I tried dozens of RUUs but they all blocked saying that the battery was less than 30%, the phone is connected but the LED does not turn on.
I only see:
*** Softeare status: Modified ***
*** Locked ***
*** S-ON ***
(...)
reboot
boot to bootloader
boot to download mode
boot to recovery mode
power down
if i try to go download mode i read
"Failed to boot to download mode
Press volume up or down to back to menu
This build is only for development purposes
Do not distribute outside of HTC without HTC's written permission.
Failure to comply may lead to legal action. "
where can I find information about cid? and especially what ruu to use? did the NAND die? should I try to change the battery and try again with the RUUs?
thanks

It's impossible to find the correct RUU if the download mode isn't working or you don't know at least the CID/MID* of the phone and the android version of the stock rom it was running before the issue arised. In addition, without a working download mode you aren't able to flash any RUUs. Sorry for the bad news.
* If you didn't buy the phone second hand or didn't repair the backside of the phone on your own then you will find the correct MID engraved on the bottom of the backside of the phone. The CID would still be unknown, though.

thank you for the reply.. i read "opja100 nm80pja100 m9u" on the back..i don't know other details..so i have an HTC for door stop

Unfortunately, yes.
The MID belongs to the international GSM version (0PJA10000), btw.
Sent from my HTC One M9 using XDA Labs