Develop Bugs

[Q] HTC M8. Phone boots only in fastboot and I can't do anything (factory reset etc)

Hi guys. I have a problem with my M8 (international).
Start topic was here http://forum.xda-developers.com/att...-boots-fastboot-factory-t2952954#post57042833 but I took an advice and open the same topic in general theme.
Hi everyone. I got a problem with my HTC M8.
First of all, I didn't make with it any changes (as unlock bootloader, root or installing any custom OS or recovery etc.) Week ago I left device, connected to PC for all night, and, I gess, with "bad" micro-USB cable.
Next day I couldn't boot this phone. I connected it to charger and after little time it was loaded to fastboot. But up today I can't do anything with phone: I can't unlock it, can't factory reset, can't boot to recovery etc...
I tried to find any same simptomes in google, but found nothing
As you can see on screenshots, I made steps for unlock bootloader but on device I didn't see notification about unlocking.
Click to expand...
Click to collapse
Could you help me with advices? Thanks.

I'm taking a bit of a guess but some how system has got wipe but that seems a bit off for a locked phone but since it's locked I would take it back to where you got it from and get them to sort it.
Sent from my One M8 using Tapatalk

Darknites said:
since it's locked I would take it back to where you got it from and get them to sort it.
Click to expand...
Click to collapse
I would normally say the same. But the OP mentioned in another thread posted in the wrong forum section (linked in his post) that he bought from Canada but lives in Ukraine, so I think warranty is not valid. It would have been helpful for the OP to give all the relevant details in this new post.
I agree, it looks like his OS and possibly recovery have somehow become wiped, corrupted, or damaged. Not common for a stock device, but not unheard of, either.

MaggiMag363 said:
Hi guys. I have a problem with my M8 (international).
Start topic was here http://forum.xda-developers.com/att...-boots-fastboot-factory-t2952954#post57042833 but I took an advice and open the same topic in general theme.
Could you help me with advices? Thanks.
Click to expand...
Click to collapse
Hi
I had a similar problem to you where I was stuck in fastboot mode and the only command it would execute was POWER DOWN and when switched back on it returned to fastboot mode. However I ended up in that state due to making a mistake in trying to unlock and root my phone. Also I believe my display showed the RADIO and OpenDSP details rather than the INVALID_VER_INFO that your's is showing.
I thought I had deleted the rom and recovery on my device and I had bricked my phone however I was able to recover my phone by getting a new unlocktoken from HTC and flashing it.
Once I had successfully unlocked my phone I had access to my rom and recovery.
I see from your first image that you tried to unlock your phone and it shows that 'unlock token check successful' but images 2 and 3 show that the phone is still 'LOCKED' so it may be worth going to the HTC site, get a new unlock token and try again.
If it doesn't work, it shouldn't do anymore harm either!
Best of luck.

I see from your first image that you tried to unlock your phone and it shows that 'unlock token check successful' but images 2 and 3 show that the phone is still 'LOCKED' so it may be worth going to the HTC site, get a new unlock token and try again.
Click to expand...
Click to collapse
Yes, I did this And in consol I saw that everything was fine, but on device I didn't see standart notification about unlocking.
A found some topics about "INVALID_VER_INFO" - and they said that it can be ok for some devices (guys checked this on their worked devices, booted to fastboot and saw the same).
http://forum.xda-developers.com/showthread.php?t=2715056 here is the topic about "INVALID...".
btw - I tried unlock phone after another man. He did the same - receive .bin from dev. HTC site etc. I did the same, but from another HTC dev. account and result was the same Phone didn't unlock.

It could be that the recovery has got messed up because I believe recovery is used to do it since unlocking will wipe data. The only things I can think of is a real ruu as in it full rom and firmware exe (good luck with that) or you could try just firmware ruu, riff box or HTC themselves.
Sent from my One M8 using Tapatalk

Darknites said:
It could be that the recovery has got messed up because I believe recovery is used to do it since unlocking will wipe data. The only things I can think of is a real ruu as in it full rom and firmware exe (good luck with that) or you could try just firmware ruu, riff box or HTC themselves.
Sent from my One M8 using Tapatalk
Click to expand...
Click to collapse
I have the riff box but without needed pin-outs (http://i01.i.aliimg.com/wsphoto/v0/...x-Flex-font-b-cable-b-font-for-Samsumg-LG.jpg I'm talking about these pin-outs). And my previous experience with riff box and Samsung S3 was not very good)))) I had been fixing it during 2 months

https://www.dropbox.com/s/oqygsy7ku7o37j5/M8-DEBUG.doc?dl=0
Pin out.

i have the same problem my device is htc m8_TL
and it still in fastboot
but i have cwm
can anyone help me ?

elawady.2014 said:
i have the same problem my device is htc m8_TL
and it still in fastboot
but i have cwm
can anyone help me ?
Click to expand...
Click to collapse
Does cwm boot?
Sent from my One M8 using Tapatalk

[/COLOR]
Darknites said:
Does cwm boot?
Sent from my One M8 using Tapatalk
Click to expand...
Click to collapse
yes it's boot
and now i install stock rom via it
i think it's for inernational
so camera not work and wifi not work ??
please help me i can't find any solve

elawady.2014 said:
yes it's boot
and now i install stock rom via it
i think it's for inernational
so camera not work and wifi not work ??
please help me i can't find any solve
Click to expand...
Click to collapse
Not sure of good place for stock roms sorry.
Sent from my One M8 using Tapatalk

Darknites said:
Not sure of good place for stock roms sorry.
Sent from my One M8 using Tapatalk
Click to expand...
Click to collapse
but how can i work wifi and camera ?

elawady.2014 said:
but how can i work wifi and camera ?
Click to expand...
Click to collapse
Not sure but you could give twrp a try to wipe and flash.
Sent from my One M8 using Tapatalk

Darknites said:
Not sure but you could give twrp a try to wipe and flash.
Sent from my One M8 using Tapatalk
Click to expand...
Click to collapse
ok thanks but i can't install other custom recovery
i have 3 backup by cwm and nandroid to my old rom
but when i restore it it not restore
do u know why ?
if other way to restore backup ?

elawady.2014 said:
i have the same problem my device is htc m8_TL
and it still in fastboot
but i have cwm
can anyone help me ?
Click to expand...
Click to collapse
Hey man. Sorry but your problem not the same. You installed custom OS and it could be the reason of this. I install nothing. I have full stock device. And my problem not the same with your problem. Could you create new topic please?

Venomtester said:
https://www.dropbox.com/s/oqygsy7ku7o37j5/M8-DEBUG.doc?dl=0
Pin out.
Click to expand...
Click to collapse
Thanks. But my skill too low for soldering these small parts I talked about completed pin-out connectors for JTAG. I tried to find them on EBAY and other JTAG stores, and failed (look at screenshot with these pin-outs higher).

Could anyone help with RUU process? What information I should have for correct RUU update? I found this post http://forum.xda-developers.com/showthread.php?t=2729173 but I'm not sure that I have SPRINT device.
I need an information, how I can be sure, that I use correct file for RUU my HTC? Is it bootloader version, or operator version (Sprint, Verison etc.) or something else? As I wrote, I can open information about my phone in Fastboot (I can check my SN, CID, bootloader version etc.)

MaggiMag363 said:
Could anyone help with RUU process? What information I should have for correct RUU update? I found this post http://forum.xda-developers.com/showthread.php?t=2729173 but I'm not sure that I have SPRINT device.
I need an information, how I can be sure, that I use correct file for RUU my HTC? Is it bootloader version, or operator version (Sprint, Verison etc.) or something else? As I wrote, I can open information about my phone in Fastboot (I can check my SN, CID, bootloader version etc.)
Click to expand...
Click to collapse
For a ruu to work it needs to have matching cid, guess mid and has to be same version or higher than what's on the phone. You can't flash the wrong one it won't let you.
Edit, also the one you linked to won't work.

Darknites said:
For a ruu to work it needs to have matching cid, guess mid and has to be same version or higher than what's on the phone. You can't flash the wrong one it won't let you.
Edit, also the one you linked to won't work.
Click to expand...
Click to collapse
Ok. And Can I flash version with unlocked bootloader and custom recovery, for example? (I said that there are a lot of recovery but they are custom. Is it ok for me or I should find pack with all stock?)
guess mid
Click to expand...
Click to collapse
It's unknown letters for me. Would you describe what did you mean? Thanks.

red text

hi guys just wanted to know if any one has seen this text just after factory reset,,,(notwithstanding the above statement, this is a test device and is the htc property. by using this device you understand and agree that htc will collect aforementioned data such setting is automatically enabled and cannot be disabled, is this how it should look.) i bought my device for cash have i done something wrong when flashing twrp or roms. unlocked boot loader and s-off. thanks for any advice regard's Joe... red text....

joecool666 said:
hi guys just wanted to know if any one has seen this text just after factory reset,,,(notwithstanding the above statement, this is a test device and is the htc property. by using this device you understand and agree that htc will collect aforementioned data such setting is automatically enabled and cannot be disabled, is this how it should look.) i bought my device for cash have i done something wrong when flashing twrp or roms. unlocked boot loader and s-off. thanks for any advice regard's Joe... red text....
Click to expand...
Click to collapse
That sounds like a developer version, no issues at all hopefully a good price

joecool666 said:
hi guys just wanted to know if any one has seen this text just after factory reset,,,(notwithstanding the above statement, this is a test device and is the htc property. by using this device you understand and agree that htc will collect aforementioned data such setting is automatically enabled and cannot be disabled, is this how it should look.) i bought my device for cash have i done something wrong when flashing twrp or roms. unlocked boot loader and s-off. thanks for any advice regard's Joe... red text....
Click to expand...
Click to collapse
That shows up with s-off. Nothing you can do.

iElvis said:
That shows up with s-off. Nothing you can do.
Click to expand...
Click to collapse
hi, will it go if i went s-on again. regards

johnerz said:
That sounds like a developer version, no issues at all hopefully a good price
Click to expand...
Click to collapse
hi, will it go if i went s-on again. regards Joe...bought it from carphonewarehouse. and i found new menu's ddr test / tools but cant remember what button's i uses lol.

joecool666 said:
hi, will it go if i went s-on again. regards
Click to expand...
Click to collapse
Yes, but going back to s-on after all the modding you've done is dangerous. If you don't do it right, you can easily brick your phone. I would leave it alone if you're just trying to get rid of that text. Not worth the risk IMO.

iElvis said:
Yes, but going back to s-on after all the modding you've done is dangerous. If you don't do it right, you can easily brick your phone. I would leave it alone if you're just trying to get rid of that text. Not worth the risk IMO.
Click to expand...
Click to collapse
thanks buddy that's all i wanted to know very best regard's Joe.. MOD'S can close thread if you wish. regards.

Constant crashing

Hi all,
My phone keeps crashing and rebooting. Every time it comes back, it needs to resign on to wifi (retype in WPA), downloads a file calle "how-to" (which I can't find), and have to resign into Google. By the time it accomplishes all this, it crashes and restarts the whole shabang again. Tried recovery mode and clearing, no difference.

It might be worth mentioning it boots into extreme power saving mode too.

Is the phone modified (unlocked bootloader, root, custom ROM, etc.) or is it stock?
On the bootloader screen, what is the OS number?

redpoint73 said:
Is the phone modified (unlocked bootloader, root, custom ROM, etc.) or is it stock?
On the bootloader screen, what is the OS number?
Click to expand...
Click to collapse
It is stock. Tried to root it but it didn't take. Don't know which version as it is stuck in a loop currently. It seems to me this is a hardware problem though.

carljames0603 said:
It is stock. Tried to root it but it didn't take.
Click to expand...
Click to collapse
Need more details on that. How did you try to root, what exact steps did you perform, where did you get stuck and why, etc.
Always provide as many details as possible when asking for help and answering our questions.
carljames0603 said:
Don't know which version as it is stuck in a loop currently.
Click to expand...
Click to collapse
If its stuck in a loop (rebooting) then simply hold volume down, and don't let go. The next time it reboots, it will go to bootloader (then you can let go of vol down).
From there, tell us what OS number it says on the bootloader screen, near the top.
carljames0603 said:
It seems to me this is a hardware problem though.
Click to expand...
Click to collapse
What makes you think that? You haven't provided any details or evidence that would support the statement.
Its possible its a hardware issue. But based on what little you've said, its perfectly possible its a software issue. So be optimistic, unless you have specific evidence to think otherwise.

When it gets stuck in a loop, holding down VOL DOWN does nothing. The only way to get to the boot loader is to go to SETTINGS>POWER OPTIONS and disable fast boot. Then hopefully it shuts down fully and doesn't crash and reboot in the process. Pain in the ass.
The OS is 3.28.605.4

carljames0603 said:
When it gets stuck in a loop, holding down VOL DOWN does nothing. The only way to get to the boot loader is to go to SETTINGS>POWER OPTIONS and disable fast boot. Then hopefully it shuts down fully and doesn't crash and reboot in the process.
Click to expand...
Click to collapse
This is false. That setting only applies when the phone is powered off; since in that condition the phone was not truly powered off (just a deep sleep mode). A reboot is always a reboot.
I know this for fact, because back when I was on KitKat (and on past devices - the "fast boot" power setting was removed after KitKat) I never ever bothered to turn off the "fast boot" feature. I was able to get to bootloader whenever I wanted by rebooting (not power off) and then holding vol down. Worked every time.
Hold down the vol down button during the next reboot cycle, and it will go to bootloader. It may be that some set of conditions is just making you think what you posted is true. But try not to get the "timing" right. Just hold the vol down, and don't let go. It will go to bootloader, if its actually bootlooping.
---------- Post added at 01:58 PM ---------- Previous post was at 01:56 PM ----------
Also, you never answered my previous question, how far you got with the rooting, and what steps you performed exactly. Is the bootloader LOCKED, UNLOCKED, or RELOCKED?
When you do go to bootloader, it stays there (doesn't reboot)?

redpoint73 said:
This is false. That setting only applies when the phone is powered off; since in that condition the phone was not truly powered off (just a deep sleep mode). A reboot is always a reboot.
I know this for fact, because back when I was on KitKat (and on past devices - the "fast boot" power setting was removed after KitKat) I never ever bothered to turn off the "fast boot" feature. I was able to get to bootloader whenever I wanted by rebooting (not power off) and then holding vol down. Worked every time.
Hold down the vol down button during the next reboot cycle, and it will go to bootloader. It may be that some set of conditions is just making you think what you posted is true. But try not to get the "timing" right. Just hold the vol down, and don't let go. It will go to bootloader, if its actually bootlooping.
---------- Post added at 01:58 PM ---------- Previous post was at 01:56 PM ----------
Also, you never answered my previous question, how far you got with the rooting, and what steps you performed exactly. Is the bootloader LOCKED, UNLOCKED, or RELOCKED?
When you do go to bootloader, it stays there (doesn't reboot)?
Click to expand...
Click to collapse
It's not false, because that's what is happening. I hold down the button the whole time and it will go through the whole process and never go to the bootloader.
Either way, sorry I missed the question. Not very far, it crashes before to long. I tried downloading the SU app as prescribed in the site, but can't get it on the device itself.
The bootloader is locked, and it stays there until I push it to reboot.

carljames0603 said:
Either way, sorry I missed the question. Not very far, it crashes before to long. I tried downloading the SU app as prescribed in the site, but can't get it on the device itself.
The bootloader is locked.
Click to expand...
Click to collapse
Nowhere will you find a guide for this device, that tells you to use an SU app. That isn't the proper way to root this phone. You need to flash SU/SuperSU, and you need custom recovery to do that. And for that, you need an unlocked bootloader, which for your device (Verizon version M8) requires s-off.
Or there is the kingroot method, which has some mixed results.
In any case, locked bootloader is good. Since my recommendation would be to RUU to full stock image, and see if that fixes your reboot problem. If not, then you are probably correct that its a hardware issue.
You can get the RUUs from here: https://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
Not only will this get you on a full stock image (which if its a software problem, will fix it) but you can get to a more updated version (yours is really outdated).
You may need to find and flash the Marshmallow 6.21.605.3 firmware (not sure where to find that, offhand), before you can falsh the Marshmallow RUU. But otherwise, you can certainly flash the Lollipop RUU.
---------- Post added at 02:26 PM ---------- Previous post was at 02:22 PM ----------
carljames0603 said:
It's not false, because that's what is happening. I hold down the button the whole time and it will go through the whole process and never go to the bootloader.
Click to expand...
Click to collapse
Maybe its not actually rebooting, then; but doing something like just rebooting the Android shell? But that would be interesting, and not something I've seen before.

redpoint73 said:
Nowhere will you find a guide for this device, that tells you to use an SU app. That isn't the proper way to root this phone. You need to flash SU/SuperSU, and you need custom recovery to do that. And for that, you need an unlocked bootloader, which for your device (Verizon version M8) requires s-off.
Or there is the kingroot method, which has some mixed results.
In any case, locked bootloader is good. Since my recommendation would be to RUU to full stock image, and see if that fixes your reboot problem. If not, then you are probably correct that its a hardware issue.
You can get the RUUs from here: https://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
Not only will this get you on a full stock image (which if its a software problem, will fix it) but you can get to a more updated version (yours is really outdated).
You may need to find and flash the Marshmallow 6.21.605.3 firmware (not sure where to find that, offhand), before you can falsh the Marshmallow RUU. But otherwise, you can certainly flash the Lollipop RUU.
---------- Post added at 02:26 PM ---------- Previous post was at 02:22 PM ----------
Maybe its not actually rebooting, then; but doing something like just rebooting the Android shell? But that would be interesting, and not something I've seen before.
Click to expand...
Click to collapse
Sorry, app as the wrong word. I tried several different methods but none was an actual app. I did try using something that came from the HTC website (RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4), but the phone would crash every time. It said to use the program while it was on bootloader, but I don't think I did it write because it still couldn't find the phone via USB.

carljames0603 said:
Sorry, app as the wrong word. I tried several different methods but none was an actual app. I did try using something that came from the HTC website (RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4), but the phone would crash every time. It said to use the program while it was on bootloader, but I don't think I did it write because it still couldn't find the phone via USB.
Click to expand...
Click to collapse
did you read the post you quoted ?
redpoint73 said clearly what you need and where to find
you used a different RUU and it will not accepted by your device ( in red above )

carljames0603 said:
Sorry, app as the wrong word. I tried several different methods but none was an actual app.
Click to expand...
Click to collapse
Complete lack of correct terminology or any meaningful details, means you haven't provided any actual information on what "methods" you tried to root. You say you tried several different methods, but don't provide any information on what those were. You say an SU app, when you don't mean an SU app (SU zip? SuperSU zip? - which is not the same).
Further, you posted that you "downloading the SU app as prescribed in the site". What website? How are we supposed to have any idea what you are talking about? Please understand, that your posts are vague to the point, that they don't actually provide any real information.
If you want proper help on this website, in general, you need to be specific, provide proper details, and user the right terminology.
carljames0603 said:
(RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4), but the phone would crash every time. It said to use the program while it was on bootloader, but I don't think I did it write because it still couldn't find the phone via USB.
Click to expand...
Click to collapse
As the previous response indicated, this isn't the right RUU for your device. Why would you try to use this? Especially since the proper RUU for your Verizon version M8 was already provided in one of my previous responses? It seems you are just guessing around for solutions (which is a recipe for disaster). You have no reason to think the RUU you listed would work on your device. The version number is all wrong, and it says Brightstar US (which is the US Developer's Edition of the M8). It isn't intended for your device, won't work, and if you flashed it successfully, it would cause your phone's SIM to stop working (radio brick - possibly permanent).

redpoint73 said:
Complete lack of correct terminology or any meaningful details, means you haven't provided any actual information on what "methods" you tried to root. You say you tried several different methods, but don't provide any information on what those were. You say an SU app, when you don't mean an SU app (SU zip? SuperSU zip? - which is not the same).
Further, you posted that you "downloading the SU app as prescribed in the site". What website? How are we supposed to have any idea what you are talking about? Please understand, that your posts are vague to the point, that they don't actually provide any real information.
If you want proper help on this website, in general, you need to be specific, provide proper details, and user the right terminology.
As the previous response indicated, this isn't the right RUU for your device. Why would you try to use this? Especially since the proper RUU for your Verizon version M8 was already provided in one of my previous responses? It seems you are just guessing around for solutions (which is a recipe for disaster). You have no reason to think the RUU you listed would work on your device. The version number is all wrong, and it says Brightstar US (which is the US Developer's Edition of the M8). It isn't intended for your device, won't work, and if you flashed it successfully, it would cause your phone's SIM to stop working (radio brick - possibly permanent).
Click to expand...
Click to collapse
Alright, clearly I'm not knowledgeable in this type of repair. I apologize for using the wrong terminology, I'm scatter brained and names often elude me. Yes, I apparently used the wrong program to flash my ROM, either way it didn't work. In the end it doesn't matter, I'm throwing in the towel and getting a new phone. Go ahead and delete this thread as I won't be using this forum anymore. You're a ****.

carljames0603 said:
Alright, clearly I'm not knowledgeable in this type of repair. I apologize for using the wrong terminology, I'm scatter brained and names often elude me. Yes, I apparently used the wrong program to flash my ROM, either way it didn't work. In the end it doesn't matter, I'm throwing in the towel and getting a new phone. Go ahead and delete this thread as I won't be using this forum anymore. You're a ****.
Click to expand...
Click to collapse
That's unfortunate, as your issue is probably completely fixable. All you need to do is follow the instructions already provided. Myself and others have taken our time, at no benefit to ourselves, in order to try to help you and others.
Any critique given by me was not mean to insult or attack, and if you read my post there is nothing in there that constitutes a personal attack or flaming (I even said "please") - while you on the other hand can't claim such a statement to be true. A constructive criticism of your posts is not the same as attacking a person (which you did). The intent was for us to obtain the proper information so that we can better understand what you did, in order to help; and hopefully to improve the quality of your subsequent posts (but that didn't happen).
You can try to learn from your mistakes and expand your knowledge; or you can complain and continue to be ignorant. Your choice.

[SOLVED] Can't get download mode working

Okay, I'm giving up, I need someone to help me.
I was given my neighbours HTC One M9. It was working just fine. After he gave it to me, first thing I did was a factory reset because he didn't delete anything.
After that, the problems began. When I boot up the phone, even directly after resetting and even before the setup, I get an error "Google App stopped working". And after that, all couple of seconds another "com.google.process.gapps stopped working".
I tried several of the fixes out there on the web, but it didn't go away. I did another factory reset, and again even when I setup the phone I get those errors.
There is still Android 6.0 on the phone, so I wanted to update to 7.1
During install, I got the red triangle screen, on both attemps. Well, f*ck.
So, I went on to install a new OS. Never did this before, so I though this is a good chance to learn some more about Android.
It just got even more strange. When I'm in the bootloader, I saw
***Software status: Modified***
S-ON
LOCKED
***Security Warning***
Especially the modified software was very strange, since my neighbour has neither a clue nor any interested of fiddling with phones.
When I tried to go into Download Mode, it said "failed to boot into download mode".
Recovery mode worked just fine.
Therefore, I couldn't do anything to install a new OS.
Next I bought the Sunshine App and S-OFFd my phone, which worked just fine.
Now I'm S-OFF, unlocked and the Security Warning has gone. The software is apparently still modified.
But when I go into download mode, I get the black screen with the silver logo and red text for a while, then the phone proceeds to boot normally.
What the f*uck? I'm just out of idead what to do now. Please don't let it be a dead nand... it's such a nice phone, and apart from the google app errors, it works perfectly. I used it for some surfing around today and it works really well. I can't imagine it being broken.
Thanks for your help!

What variant do you have? Firmware version?

side_flip15 said:
What variant do you have? Firmware version?
Click to expand...
Click to collapse
Firmware is 3.35.166.12
I don't know exactly about the variant, this is what the IMEI checker says:
SKU , VF , German , CHE , HTC , CH , Swisscom , Bootloader Lock , Dark Gunmetal/Dark Gunmetal , w/o SIM Lock , HIMA#UHL-D1
I have a bug report of the gapps-Error. Would that be helpful?

I have some bad news for you:
According to everything that you describe in the opening post it's the dead nand issue. There's nothing you can do. And if you send the phone to HTC they will change the motherboard which means that you have to buy sunshine, again, after they send the phone back to you.

@Flippy498 Is the "failed to boot into download mode"? error a sign of dead nand? This happened to me before. I flashed hosd.img via bootloader to fix this. Still using my M9.

It's the combination of several things that make me think it's a dead nand:
The security warning indicates that there is no OS installed. If that happened without manually deleting the OS via a custom recovery like TWRP then chances are high that the nand died.
The software status is modified although the phone is locked and S-ON. The only other explanation for this combination would be that the owner failed while using one of the 100% stock guides that convert S-OFF back to S-ON, Unlocked back to Locked and modified back to original. However, the dead nand issue is quite common during the recent months and the guides are hidden somewhere in the Genereal section (in other words: not located on the first page). Therefore, I think that chances are higher that it's the dead nand issue.
Last but not least: The black download mode error screen in combination with the other two symptoms.
Did you report about your tries to revive your phone somewhere here on xda? Do you have a link? What kind of symptoms did you face aside from the black error screen? Has your phone been S-ON or S-OFF?
If you really faced a dead nand issue and could repair your phone by your own that would be a game-changing and I could finally overhaul the FAQ of the ReadMe thread. However, discussions like the one that starts with this post make me think that you might have faced a different problem with your download mode since it really looks like the dead nand isn't fixable without changing the hardware.

Flippy498 said:
I have some bad news for you:
According to everything that you describe in the opening post it's the dead nand issue. There's nothing you can do. And if you send the phone to HTC they will change the motherboard which means that you have to buy sunshine, again, after they send the phone back to you.
Click to expand...
Click to collapse
Flippy498 said:
It's the combination of several things that make me think it's a dead nand:
The security warning indicates that there is no OS installed. If that happened without manually deleting the OS via a custom recovery like TWRP then chances are high that the nand died.
The software status is modified although the phone is locked and S-ON. The only other explanation for this combination would be that the owner failed while using one of the 100% stock guides that convert S-OFF back to S-ON, Unlocked back to Locked and modified back to original. However, the dead nand issue is quite common during the recent months and the guides are hidden somewhere in the Genereal section (in other words: not located on the first page). Therefore, I think that chances are higher that it's the dead nand issue.
Last but not least: The black download mode error screen in combination with the other two symptoms.
Did you report about your tries to revive your phone somewhere here on xda? Do you have a link? What kind of symptoms did you face aside from the black error screen? Has your phone been S-ON or S-OFF?
I didn't have to revive it, except that Google-error it works beautifully. That' broken download mode the only symptom I have. The phone is (meanwhile after Sunshine) S-OFF
If you really faced a dead nand issue and could repair your phone by your own that would be a game-changing and I could finally overhaul the FAQ of the ReadMe thread. However, discussions like the one that starts with this post make me think that you might have faced a different problem with your download mode since it really looks like the dead nand isn't fixable without changing the hardware.
Click to expand...
Click to collapse
Well, there are two things that leave me hoping it's not a dead nand.
• Apart from that com.google.process.gapps-error, it works like a charm. No crashes, no sudden reboots. I really can't imagine a broken part of a motherboard making no trouble, wouldn't that render the part
useless? And is that Google-App Error really relatable?
• After letting the Sunshine App do its job, I don't get an error message in the download mode (well, it just boots normally after a while), the security warning has gone as well. Only the modified software is
suspicious.
side_flip15 said:
@Flippy498 Is the "failed to boot into download mode"? error a sign of dead nand? This happened to me before. I flashed hosd.img via bootloader to fix this. Still using my M9.
Click to expand...
Click to collapse
I've heard of that as well. I didn't really find any tutorial on that and I'm a bit afraid to experiment with that. Do you mind sharing how you achieved that?

Instructions are linked in the FAQ of the ReadMe thread. They're the solution for the blue download mode issue.
The thing is that the download mode can't just break without either you actively manipulating it or the hardware of the phone dying. The same applies to that security warning. Either you manually delete the OS or the hardware fails and the phone isn't able to read the installed OS correctly, anymore. Therefore, I wouldn't put my hopes too high if I were you. Of course I could be wrong but I've read a lot of reports of dead nand phones since last year's summer and my feeling tells me that this is another one.
As a sidenote: You're the first user that tried to S-OFF/successfully S-OFFed his phone after such errors occurred since sunshine can't unlock the bootloader on firmware 4.x and hasn't been able to do so on older firmware versions when the issue appeared the first time. Therefore, I don't know which influence sunshine has on the whole situation.
Sent from my HTC One M9 using XDA Labs

Flippy498 said:
Instructions are linked in the FAQ of the ReadMe thread. They're the solution for the blue download mode issue. Great, thanks!
The thing is that the download mode can't just break without either you actively manipulating it or the hardware of the phone dying. The same applies to that security warning. Either you manually delete the OS or the hardware fails and the phone isn't able to read the installed OS correctly, anymore. Therefore, I wouldn't put my hopes too high if I were you. Of course I could be wrong but I've read a lot of reports of dead nand phones since last year's summer and my feeling tells me that this is another one.
Click to expand...
Click to collapse
Yes, I know. Maybe I just don't want to accept that fact to keep my motivation to try to save the phone...
So what my optimism suspects is that somewhere deep in the firmware there is something corrupted. That leaves the System modified and the Google app confused.
After all, recovery mode works just fine. If you check what other people experience with a dead nand, it's got to do with sudden reboots, bootloops, failed download AND recovery modes et cetera.
As a sidenote: You're the first user that tried to S-OFF/successfully S-OFFed his phone after such errors occurred since sunshine can't unlock the bootloader on firmware 4.x and hasn't been able to do so on older firmware versions when the issue appeared the first time. Therefore, I don't know which influence sunshine has on the whole situation.
Click to expand...
Click to collapse
A little more hope rised in me...

sechsgangschakter said:
I've heard of that as well. I didn't really find any tutorial on that and I'm a bit afraid to experiment with that. Do you mind sharing how you achieved that?
Click to expand...
Click to collapse
You can try this...
Get the firmware.zip matching your current firmware @Flippy498 's thread here. Links are in the spreadsheet in post #2. Extract the hosd.img from the zip and flash in bootloader mode .
Code:
fastboot flash hosd hosd.img
then try to reboot to download mode. If it does not work, try other firmware.zip but should be in the same build number at least X.XX.

SAME HERE PROBLEM PLEASE HELP
I HAVE HTC ONE M9 OPJA100 JUST GO ON LOCKED SCREEN WHEN REBOOT TO BOOTLOADER ITS RESTART AGAIN EVEN NOT GO DOWNLOAD MODE OR RECOVERY MODE.
I WAS JUST MAKE ROOT THEN ITS STUCK ON LOGO
NOT GO FASTBOOT MODE TO CHECK CID OR FIRMWARE
WHAT I DO ?????
ITS LOCKED
S-ON ALSO

side_flip15 said:
You can try this...
Get the firmware.zip matching your current firmware @Flippy498 's thread here. Links are in the spreadsheet in post #2. Extract the hosd.img from the zip and flash in bootloader mode .
Code:
fastboot flash hosd hosd.img
then try to reboot to download mode. If it does not work, try other firmware.zip but should be in the same build number at least X.XX.
Click to expand...
Click to collapse
THANK YOU!!!!
It finally works!
Edit: I installed resurrection Remix. Working perfectly, I really don't think there is anything dead in that phone. It's great, thank you for your help!

sechsgangschakter said:
THANK YOU!!!!
It finally works!
Edit: I installed resurrection Remix. Working perfectly, I really don't think there is anything dead in that phone. It's great, thank you for your help!
Click to expand...
Click to collapse
Glad I helped you:highfive:

side_flip15 said:
Get the firmware.zip matching your current firmware @Flippy498 's thread here. Links are in the spreadsheet in post #2. Extract the hosd.img from the zip and flash in bootloader mode .
Click to expand...
Click to collapse
Just for the record, that's not my thread. It's owned by Sneakyghost.
@sechsgangchakter: I'm glad to hear that your phone is working, again.

Flippy498 said:
Just for the record, that's not my thread. It's owned by Sneakyghost.
Click to expand...
Click to collapse
Oh god! Sorry
Credits to @Sneakyghost :highfive:

Hello, I am having a very similar issue. I am looking for the hosd.img file for Verizon. I dont see it at https://docs.google.com/spreadsheets/d/1ZaiJ3F_f76sVa4daU5H62OYi5Bj23LEBBv4xDTQ8y-M/pubhtml. Please help. Thanks

You won't find any CDMA files in that spreadsheet because the xda thread that sheet belongs to only supports GSM devices and clearly states that it'll never support CDMA.

Flippy498 said:
You won't find any CDMA files in that spreadsheet because the xda thread that sheet belongs to only supports GSM devices and clearly states that it'll never support CDMA.
Click to expand...
Click to collapse
So no one knows of one available for Verizon m9? What would happen if I used a GSM one?

You would probably damage your phone unrecoverably. GSM and CDMA are not compatible with each other due to the different partition layouts.
However, why don't you extract the needed file from a RUU that matches your current firmware version? That's how those firmware packs in the linked thread got made, as well. There's a thread with a RUU extraction tool linked in the RUU section of the ReadMe thread.
Sent from my HTC One S using XDA Labs

Flippy498 said:
You would probably damage your phone unrecoverably. GSM and CDMA are not compatible with each other due to the different partition layouts.
However, why don't you extract the needed file from a RUU that matches your current firmware version? That's how those firmware packs in the linked thread got made, as well. There's a thread with a RUU extraction tool linked in the RUU section of the ReadMe thread.
Sent from my HTC One S using XDA Labs
Click to expand...
Click to collapse
Good idea, ill give that a try. Thanks

Root on Unlocked Version?

Hello,
So I bought the HTC 10 directly from their store a few months ago, and have been considering to root it. The thing is that when I look up the Model Number on the HTC, it say "HTC 10" as well, no info. Is there a way to find it's actual MN if it's hidden (as I assume)?
Let me know if there's any other info needed. Thank you in advanced.

Junito72 said:
Hello,
So I bought the HTC 10 directly from their store a few months ago, and have been considering to root it. The thing is that when I look up the Model Number on the HTC, it say "HTC 10" as well, no info. Is there a way to find it's actual MN if it's hidden (as I assume)?
Let me know if there's any other info needed. Thank you in advanced.
Click to expand...
Click to collapse
You'll need fastboot.
Reboot into download mode (hold volume down and restart the phone), and from your computer type
Fastboot getvar all
Your model number will be listed as MID.
Or, if you bought it from HTC directly and haven't modified anything you'll be able to tell by the software number in the phone's settings. It'll be something like 2.x.y.z. The three digit y number will be something like 617 (u.s unlocked, model ID 2PS65000) or 401 (wwe, model id 2PS62000), for example.
But you don't really need to know that to root. You just need to unlock your bootloader using HTCdev website and then follow instructions for root on xda.

Tarima said:
You'll need fastboot.
Reboot into download mode (hold volume down and restart the phone), and from your computer type
Fastboot getvar all
Your model number will be listed as MID.
Or, if you bought it from HTC directly and haven't modified anything you'll be able to tell by the software number in the phone's settings. It'll be something like 2.x.y.z. The three digit y number will be something like 617 (u.s unlocked, model ID 2PS65000) or 401 (wwe, model id 2PS62000), for example.
But you don't really need to know that to root. You just need to unlock your bootloader using HTCdev website and then follow instructions for root on xda.
Click to expand...
Click to collapse
Alright, will give it a shot, thanks.

Tarima said:
You'll need fastboot.
Reboot into download mode (hold volume down and restart the phone), and from your computer type
Fastboot getvar all
Your model number will be listed as MID.
Or, if you bought it from HTC directly and haven't modified anything you'll be able to tell by the software number in the phone's settings. It'll be something like 2.x.y.z. The three digit y number will be something like 617 (u.s unlocked, model ID 2PS65000) or 401 (wwe, model id 2PS62000), for example.
But you don't really need to know that to root. You just need to unlock your bootloader using HTCdev website and then follow instructions for root on xda.
Click to expand...
Click to collapse
I have the ADB files and fastboot together, but won't show up within the cmd window. Anynthing I'm doing wrong? OEM's unlocked and USB debugging's enabled

Junito72 said:
I have the ADB files and fastboot together, but won't show up within the cmd window. Anynthing I'm doing wrong? OEM's unlocked and USB debugging's enabled
Click to expand...
Click to collapse
Honestly I'm not very good at troubleshooting adb issues. I would suggest you follow instructions on the HTCdev website for bootloader unlocking, they tell you how to install fastboot. Else there are tons of guides on xda or YouTube.
Also make sure you disable HTC Sync Manager on your pc, if you have it.

Also make sure you disable HTC Sync Manager on your pc, if you have it.
Click to expand...
Click to collapse
Is it necessary, or just an optional program in this case?

Junito72 said:
Is it necessary, or just an optional program in this case?
Click to expand...
Click to collapse
No you don't need it. Just make sure you have htc drivers. One way of doing that is, I believe, is to install htc sync manager but then remove it while keeping the drivers.

Tarima said:
No you don't need it. Just make sure you have htc drivers. One way of doing that is, I believe, is to install htc sync manager but then remove it while keeping the drivers.
Click to expand...
Click to collapse
Alright, I found an individual driver installer, got it set up. Thanks for the help.

Tarima said:
No you don't need it. Just make sure you have htc drivers. One way of doing that is, I believe, is to install htc sync manager but then remove it while keeping the drivers.
Click to expand...
Click to collapse
I successfully got the bootloader unlocked, installed latest TWRP, but upon installing the supersu the forums made to bypass dm_verity and the forceencrypt, it went into a bootloop.
There was a red message saying something among the lines of, "This is for developers only..." and whatnot, and simply kept looping.
Thankfully I made the backup, so I restored it. But I'm stuck at the SuperSU part.
If anyone knows why it is doing this, please let me know.
I should also point out, twrp was able to decrypt my phone's data when creating the backup, so not sure if this would mean I need to intentionally install an older TWRP, just so with that version, they fail decryption.

Sorry for bothering, got it working. Have Nougat, so I didn't knew I needed another different SuperSU

Junito72 said:
Sorry for bothering, got it working. Have Nougat, so I didn't knew I needed another different SuperSU
Click to expand...
Click to collapse
Good, glad you got it working.

Tarima said:
Good, glad you got it working.
Click to expand...
Click to collapse
Yeah, thank you for your help, btw.
Only current issue I'm having is trying to set up Adaway, since it requests S-Off. (Which I'm concerned of, since idk if doing so and letting the app do it's thing would unencrypt the data) So wondering it it's wise to do so.

Junito72 said:
Yeah, thank you for your help, btw.
Only current issue I'm having is trying to set up Adaway, since it requests S-Off. (Which I'm concerned of, since idk if doing so and letting the app do it's thing would unencrypt the data) So wondering it it's wise to do so.
Click to expand...
Click to collapse
Why is Adaway asking for S-Off? Not even sure it should be able to see your s-on/s-off state. Root access is all that it should be requesting.
S-off with sunshine won't touch your data partition. But I wouldn't pay for S-Off just because Adaway is asking you to.

Tarima said:
Why is Adaway asking for S-Off? Not even sure it should be able to see your s-on/s-off state. Root access is all that it should be requesting.
S-off with sunshine won't touch your data partition. But I wouldn't pay for S-Off just because Adaway is asking you to.
Click to expand...
Click to collapse
Oddly, it went and started working now, at first it requested to create something that required S-Off. Hmm, perhaps I must of tweaked something for it to no longer need that.
I have one more doubt, but I feel this one may be better to be done as a new thread instead.