Develop Bugs

Help please...screen stuck at logo

Hello
My phone's screen is stuck at opening htc logo. I never rooted it - shall I just flash it with standard stock rom? Would you please be so kind to point me in the right direction? Bless...
My kindest regards
Pete

Try booting without the sd card.
How old is the phone? What happened / did you do (if such is the case) for it to get like that? Etc.....
Sent from a dream.

Teichopsia said:
Try booting without the sd card.
How old is the phone? What happened / did you do (if such is the case) for it to get like that? Etc.....
Sent from a dream.
Click to expand...
Click to collapse
Tried that before without result...also did a factory reset but to no avail. Phone was just over a year old when it happened, got it from my insurance policy so it's possibly a refurbished one. I can't remember doing anything to cause this...

phosphen said:
Tried that before without result...also did a factory reset but to no avail. Phone was just over a year old when it happened, got it from my insurance policy so it's possibly a refurbished one. I can't remember doing anything to cause this...
Click to expand...
Click to collapse
You Need to provide the Cid number and the Main Version. Do You know how to Get that?

glevitan said:
You Need to provide the Cid number and the Main Version. Do You know how to Get that?
Click to expand...
Click to collapse
Sorry, no idea...

phosphen said:
Sorry, no idea...
Click to expand...
Click to collapse
Ok, enable USB debugging, plug the phone to the PC and then open a CMD ON the PC and type adb reboot-bootloader and once in bootloader type fastboot getvar all. You Need to post the INFOcidnum and INFOmain

How old is your phone? Isn't there still any warranty? If so you may try to contact your reseller, service provider or the manufacturer. If not glevitan may be your hero

glevitan said:
Ok, enable USB debugging, plug the phone to the PC and then open a CMD ON the PC and type adb reboot-bootloader and once in bootloader type fastboot getvar all. You Need to post the INFOcidnum and INFOmain
Click to expand...
Click to collapse
Sorry mate, I was offline for a whole day, just managed to get back on it
How can I enable USB debugging if I can get onto HBOOT menu only? Is it possible to switch it on from there? Saludos

phosphen said:
Sorry mate, I was offline for a whole day, just managed to get back on it
How can I enable USB debugging if I can get onto HBOOT menu only? Is it possible to switch it on from there? Saludos
Click to expand...
Click to collapse
Yes, from fastboot, plug the phone (You will see fastboot USB in red) type: fastboot getvar all

sounds like a boot loop?
try removing the battery, once you have done that re boot into boot loader from there you should see an option for recovery.you may want to do a full wipe and re flash the rom.:silly: keep in mind the initial flash normally will take the longest,best to leave it be for a few minutes while the phone adjust to the new settings,that sometimes will seem like you may have an issue, but patience most times is all that is needed.hope this helps.

rdub504 said:
try removing the battery, once you have done that re boot into boot loader from there you should see an option for recovery.you may want to do a full wipe and re flash the rom.:silly: keep in mind the initial flash normally will take the longest,best to leave it be for a few minutes while the phone adjust to the new settings,that sometimes will seem like you may have an issue, but patience most times is all that is needed.hope this helps.
Click to expand...
Click to collapse
It's not rooted, so I don't think that will work.

bananagranola said:
It's not rooted, so I don't think that will work.
Click to expand...
Click to collapse
excellent point,but if that's true what is he flashing?
rooted phone=flash capable non rooted =stock rom with no admin access. am i mistaken,if so slap me and call me susan,if not box that thing up and bring it back,and if that's not an option then warranty time.because that device is chap.

rdub504 said:
excellent point,but if that's true what is he flashing?
rooted phone=flash capable non rooted =stock rom with no admin access. am i mistaken,if so slap me and call me susan,if not box that thing up and bring it back,and if that's not an option then warranty time.because that device is chap.
Click to expand...
Click to collapse
Hello susan
Sent from a dream.

Teichopsia said:
Hello susan
Sent from a dream.
Click to expand...
Click to collapse
LOL,I guess i'm susan and my face now hurt.can you please elaborate a bit so i can also understand what i am missing.

rdub504 said:
LOL,I guess i'm susan and my face now hurt.can you please elaborate a bit so i can also understand what i am missing.
Click to expand...
Click to collapse
Well....
1- over a year old bought refurbished.
2- he never rooted. We could assume that it is s-off from the previous owner but all of us failed to ask that question making another assumption that he isn't s-off.
3- he did a factory reset which didn't work (whatever that means with an s-on device / with an s-off device it really messes things up).
4- glevitan is here. If he doesn't know how to fix it (and from the few active members that tend to lend a hand in these type of posts) there may be just a handful who could help out. Hence, the OP is in good hands.
5- when someone messes up their phone without knowing what happened nor how to fix it, you need to give more detailed instructions on how to get it done.
6- I'm guessing that the info glevitan asked for is to find the correct ruu for the member to flash and to get his phone back to working conditions. If that doesn't work, chances are it's a hardware problem.
Sent from a dream.

Teichopsia said:
Well....
1- over a year old bought refurbished.
2- he never rooted. We could assume that it is s-off from the previous owner but all of us failed to ask that question making another assumption that he isn't s-off.
3- he did a factory reset which didn't work (whatever that means with an s-on device / with an s-off device it really messes things up).
4- glevitan is here. If he doesn't know how to fix it (and from the few active members that tend to lend a hand in these type of posts) there may be just a handful who could help out. Hence, the OP is in good hands.
5- when someone messes up their phone without knowing what happened nor how to fix it, you need to give more detailed instructions on how to get it done.
6- I'm guessing that the info glevitan asked for is to find the correct ruu for the member to flash and to get his phone back to working conditions. If that doesn't work, chances are it's a hardware problem.
Bullet point,impressive. now a refurb with s off would mean a root from a previous owner?
"S-ON, which means it blocks you from flashing radio images — the code that manages your data, Wi-Fi and GPS connections. Switching your phone to S-OFF lets you flash new radios. Rooting doesn’t require S-OFF, but many rooting tools will give you S-OFF in addition to root access" So hince my question if attempting to flash a rom ,it would be a safe bet he would be rooted,because without it he would have no admin access,recovery or superser access and would not be able to complete the flash process.a factory reset would normally on a stock rom not result in a loss of the entire stock rom but only a loss off data i.e contacts apps etc. and with these things in mind it would seem to be a safe to assume its a hardware issue or a rooted refurb phone from a previous owner in a bootloop becauce a factory reset there would wipe everything?
Click to expand...
Click to collapse

Factory reset resets the phone to it's "as fabricated"-condition, wich means it wipes user data and cache on the phone. With or without root the procedure is the same and should usally not affect /system or /boot.
So we have to find out, if the phone is S-On/S-Off (phosphen, more information on the topic can be read for example here, second post).

Teichopsia said:
Well....
1- over a year old bought refurbished.
2- he never rooted. We could assume that it is s-off from the previous owner but all of us failed to ask that question making another assumption that he isn't s-off.
3- he did a factory reset which didn't work (whatever that means with an s-on device / with an s-off device it really messes things up).
4- glevitan is here. If he doesn't know how to fix it (and from the few active members that tend to lend a hand in these type of posts) there may be just a handful who could help out. Hence, the OP is in good hands.
5- when someone messes up their phone without knowing what happened nor how to fix it, you need to give more detailed instructions on how to get it done.
6- I'm guessing that the info glevitan asked for is to find the correct ruu for the member to flash and to get his phone back to working conditions. If that doesn't work, chances are it's a hardware problem.
Sent from a dream.
Click to expand...
Click to collapse
rdub504 said:
Teichopsia said:
Well....
1- over a year old bought refurbished.
2- he never rooted. We could assume that it is s-off from the previous owner but all of us failed to ask that question making another assumption that he isn't s-off.
3- he did a factory reset which didn't work (whatever that means with an s-on device / with an s-off device it really messes things up).
4- glevitan is here. If he doesn't know how to fix it (and from the few active members that tend to lend a hand in these type of posts) there may be just a handful who could help out. Hence, the OP is in good hands.
5- when someone messes up their phone without knowing what happened nor how to fix it, you need to give more detailed instructions on how to get it done.
6- I'm guessing that the info glevitan asked for is to find the correct ruu for the member to flash and to get his phone back to working conditions. If that doesn't work, chances are it's a hardware problem.
Bullet point,impressive. now a refurb with s off would mean a root from a previous owner?
"S-ON, which means it blocks you from flashing radio images — the code that manages your data, Wi-Fi and GPS connections. Switching your phone to S-OFF lets you flash new radios. Rooting doesn’t require S-OFF, but many rooting tools will give you S-OFF in addition to root access" So hince my question if attempting to flash a rom ,it would be a safe bet he would be rooted,because without it he would have no admin access,recovery or superser access and would not be able to complete the flash process.a factory reset would normally on a stock rom not result in a loss of the entire stock rom but only a loss off data i.e contacts apps etc. and with these things in mind it would seem to be a safe to assume its a hardware issue or a rooted refurb phone from a previous owner in a bootloop becauce a factory reset there would wipe everything?
Click to expand...
Click to collapse
Cfhappy said:
Factory reset resets the phone to it's "as fabricated"-condition, wich means it wipes user data and cache on the phone. With or without root the procedure is the same and should usally not affect /system or /boot.
So we have to find out, if the phone is S-On/S-Off (phosphen, more information on the topic can be read for example here, second post).
Click to expand...
Click to collapse
Sorry guys, but before hijacking this thread maybe you can go and follow the discussion in the off topic thread. The idea here is to lend a hand to someone that is stuck and a noob and this for certain not helping him. Let's keep it clean....
BTW, the only solution in his case is to flash the OEM RUU or make a goldcard and flash an unbranded rom. With no s-off there´s no other way.
Click to expand...
Click to collapse

I couldn't resist.
Maybe it's good practice for him to read through all to learn to discern right info from wrong.
Sent from a dream.

Teichopsia said:
I couldn't resist.
Maybe it's good practice for him to read through all to learn to discern right info from wrong.
Sent from a dream.
Click to expand...
Click to collapse
Yeah, that is right, but with the phone stuck in the splash I don´t think is a good time to think about learning. This experience will definitely be worth for him in the future. :victory:

M9 bricked (doesn`t POWER On) after flashing a wrong ZIP-file via TWRP...Please HELP

Good morning
I`ve got a really big problem and don`t know if I`m able to solve it or if I have to send my phone to HTC..
I rooted the m9 and got S-Off through the sunshine app. Then I wanted to flash a custom splash-screen via cmd but it didn`t work.. I tried something else and that turned out to be really stupid:
I flashed the zip-file from here android-hilfe.de/thema/how-to-splash-screen-aendern.433411 which normaly was created for the m7 only with my m9 through TWRP and did a reboot..now my phone went OFF and I couldn`t start it again...till today. That means that I`m unable to start anything. Off course there is no connection between phone and computer, too. The phone is still OFF and I have tried many different things to restart it but without success
As I said before, the phone was rooted and S-Off. Everything else is still on stock. I think it `s the unbranded version from Taiwan. The CID was HTC__621 but I`ve changed it to 11111111.
If there is no way to fix this, where should I send the phone? Directly to HTC or back to the online-store where I bought it a few weeks ago?
Hope to hear from you soon..
Thx in advance and best regards!
bikk.b

I'd have to look at the partition maps to know exactly what you did, but those recovery flashable zips for the M7 used the dd command to write the splash partition directly. Problem is that it's in a different location on the M9. It sounds like you overwrote something critical doing this.
So yes, your phone is likely dead. Only HTC or a repair shop can fix this.
Sent from my HTC One M9 using Tapatalk

iElvis said:
I'd have to look at the partition maps to know exactly what you did, but those recovery flashable zips for the M7 used the dd command to write the splash partition directly. Problem is that it's in a different location on the M9. It sounds like you overwrote something critical doing this.
So yes, your phone is likely dead. Only HTC or a repair shop can fix this.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
I agree with this, never flash ZIPS not meant for the M9 at all.....now you should take your phone to the vendor, but then they will take phone to HTC anyways and delay more time to replace/fix..........
My recommendation is to take phone underwater for 30 so it can get impregnated with water in all the inside and if available for your vender or HTC directly, use the Uh-Oh warranty available for the device....i live in mexico and i know of many people have used this methos to replace the phone whenever they have f****** the phone by flashing..... heres the link for more info:
http://www.htc.com/us/uh-oh-protection/

LLegion said:
My recommendation is to take phone underwater for 30 so it can get impregnated with water in all the inside and if available for your vender or HTC directly, use the Uh-Oh warranty available for the device....i live in mexico and i know of many people have used this methos to replace the phone whenever they have f****** the phone by flashing..... heres the link for more info:
http://www.htc.com/us/uh-oh-protection/
Click to expand...
Click to collapse
That's not a good idea. The Uh-Oh protection only exists in the US. He said it's a taiwanese model. So how should he be able to use the Uh-Oh protection under these circumstances?
Edit: Sorry. Didn't want to sound rude. Corrected my post.

Flippy498 said:
That's not a good idea. The Uh-Oh protection only exists in the US. He said it's a taiwanese model. So how should he be able to use the Uh-Oh protection under these circumstances?
Edit: Sorry. Didn't want to sound rude. Corrected my post.
Click to expand...
Click to collapse
Yes, dont you worry didnt read that "taiwanese" part of the post, and yes, the Uh-Oh protection is only available in America I guess, also available in my country Mexico and my Carrier Telcel, hope evreyone may enjoy this opportunity as well.

I'm sure OP has disposed of his phone by now, but I finally looked at the maps to see what happened here, and hoo boy was this a goof. The M7 recovery script writes the splash to p13. Guess what p13 is on the M9?
aboot
:crying:
So yeah, you're going to hardbrick your phone trying this. Going to add a big nasty warning to my M7 splash thread.

iElvis said:
I'm sure OP has disposed of his phone by now, but I finally looked at the maps to see what happened here, and hoo boy was this a goof. The M7 recovery script writes the splash to p13. Guess what p13 is on the M9?
aboot
:crying:
So yeah, you're going to hardbrick your phone trying this. Going to add a big nasty warning to my M7 splash thread.
Click to expand...
Click to collapse
Any chance you could change your updater script to do by partition name instead of a static block number? It's not common, but HTC has in fact added partitions over the course of OTA updates that can renumber the existing ones.

dottat said:
Any chance you could change your updater script to do by partition name instead of a static block number? It's not common, but HTC has in fact added partitions over the course of OTA updates that can renumber the existing ones.
Click to expand...
Click to collapse
With over 100 splash files in that thread, it would be a lot of work. People should know not to flash things written for other phones, not that it seems to stop them from trying. There are and have been warnings in the OP about doing it.
It's not an issue for the M9 since splashes have to be changed in fastboot unless you use scotty's mod to remove the write-protect on the splash partition (something I don't recommend for anyone other than advanced users).

Recover on from bootloop on H815 EU

Hi guys,
Yesterday I got sweaty hand palms.
My EU 815 G4 is unlocked, the official way, and I had rooted it.
Then I tried to install xposed from twrp and I did something wrong, and ended up in bootloop...
I have just updated to v20b before, and forgot to connect the phone to the PC, and allow the PC debug access before installing xposed, so i could see the phone in ADB mode, but couldn't access it.
Of course I hadn't made a backup before this - I like to cry
Just as a desperate try, when everything else had failed, i thought about using the new tool provided by shakeyabooti LG UP to flash the factory KDZ all over
I put the phone in SW. update mode by:
1. Turning off the phone
2. connecting USB cable to the PC
3. Press and hold vol. up while connecting the USB cable to the phone
Then i downloaded the v20b KDZ file, provided by Autoprime (since this was what i where allready running)
Opened LG UP, loaded the H81520B_00.kdz, marked REFURBISH
Lastly i pressed "Start" and waited for about 15-20 minutes and "TADAAAA"
The phone where up and running again... only things lost where root and TWRP
- Sharing since I'm properly not the only one ending up in this kind of mess :laugh:

Just tried it no luck :/
So just to confirm...unlocking bootloader official way does void warranty and we can not send it in for repairs?

rakinisbat said:
Just tried it no luck :/
So just to confirm...unlocking bootloader official way does void warranty and we can not send it in for repairs?
Click to expand...
Click to collapse
Indeed. Maybe you'll find a cool employee at your vendor who will still do it, but your warranty is definately void and they don't need to do anything. Depends on how acommodating the employee is. If you're stuck in a bootloop @rakinisbat just follow the steps in this thread.
And please keep in mind that there's a way to get out of bootloops 99% of the time (in fact 100% if it's a software related problem), you just have to do a good search on xda. Furthermore there's an uninstaller app for xposed in the official rovo89 thread, which you can flash via recovery and it which undos the xposed installation and your phone will boot fine (if you can access TWRP - just flash it). If you have further questions you can PM me, always happy to help

Follow_and_Feel said:
Indeed. Maybe you'll find a cool employee at your vendor who will still do it, but your warranty is definately void and they don't need to do anything. Depends on how acommodating the employee is. If you're stuck in a bootloop @rakinisbat just follow the steps in this thread.
And please keep in mind that there's a way to get out of bootloops 99% of the time (in fact 100% if it's a software related problem), you just have to do a good search on xda. Furthermore there's an uninstaller app for xposed in the official rovo89 thread, which you can flash via recovery and it which undos the xposed installation and your phone will boot fine (if you can access TWRP - just flash it). If you have further questions you can PM me, always happy to help
Click to expand...
Click to collapse
Thanks Mate, I guess ill have to try my luck with LG,
I have that batch of H815 with the faulty motherboard, unfortunately I'm in that 1% *Sigh* :crying:
Tried literally everything i could with the software, pretty much confirmed it is the motherboard.
It looks like the KDZ is flashing properly, as LGUP shows whichever kdz i put on, but the actual hardware is not capable of booting into the OS.

rakinisbat said:
Thanks Mate, I guess ill have to try my luck with LG,
I have that batch of H815 with the faulty motherboard, unfortunately I'm in that 1% *Sigh* :crying:
Tried literally everything i could with the software, pretty much confirmed it is the motherboard.
It looks like the KDZ is flashing properly, as LGUP shows whichever kdz i put on, but the actual hardware is not capable of booting into the OS.
Click to expand...
Click to collapse
Ugh, okay that's bad luck. Sorry to hear. If it's a motherboard problem I can't help you unfortunately Sorry for that. What is exactly happening when you try to flash via LGUP? Just curious

Follow_and_Feel said:
Ugh, okay that's bad luck. Sorry to hear. If it's a motherboard problem I can't help you unfortunately Sorry for that. What is exactly happening when you try to flash via LGUP? Just curious
Click to expand...
Click to collapse
It flashed perfectly fine, once completed it reboots and just literally sits on the LG logo.....FOREVER or till the battery dies.
So much disappointment in LG

rakinisbat said:
It flashed perfectly fine, once completed it reboots and just literally sits on the LG logo.....FOREVER or till the battery dies.
So much disappointment in LG
Click to expand...
Click to collapse
Oh yeah that really sounds like a hardware problem. Damn it LG! But is your bootloader still locked? You might have a chance to get a new one if it is And if it's a hardware prob you still have your warranty, haven't you?

Follow_and_Feel said:
Oh yeah that really sounds like a hardware problem. Damn it LG! But is your bootloader still locked? You might have a chance to get a new one if it is And if it's a hardware prob you still have your warranty, haven't you?
Click to expand...
Click to collapse
Nope, my bootloader is unlocked, im a flash-a-holic, longest i have lasted without rooting or unlocking a bootloader is about 2 weeks. I would have never imagined such a massive hardware issue with a flagship phone. I'll probably get a nexus 6P atleast it has better support than a LG. I'm in Australia, I imported this phone when it was released, so i have to send this phone overseas if i want it repaired, which they will most likely deny.
Sooooo over LG now! There are like hundreds if not thousands that are effected they are not even acknowledging it or providing a viable solution.

rakinisbat said:
Nope, my bootloader is unlocked, im a flash-a-holic, longest i have lasted without rooting or unlocking a bootloader is about 2 weeks. I would have never imagined such a massive hardware issue with a flagship phone. I'll probably get a nexus 6P atleast it has better support than a LG. I'm in Australia, I imported this phone when it was released, so i have to send this phone overseas if i want it repaired, which they will most likely deny.
Sooooo over LG now! There are like hundreds if not thousands that are effected they are not even acknowledging it or providing a viable solution.
Click to expand...
Click to collapse
Haha! I can completely subscribe to the flash-a-holic :laugh: Well ok. So it's even worse than i thought Sorry for ya. At least you live on a continent everyone here desires to go to :laugh: Going to Australia is very popular in germany But sorry that you're experiencing trouble with your LG. Good luck with that nexus - it's an awesome phone, too. Bye bye

I've got the bootloop issue. Phone was turning on or not, just vibrating etc. I've dissassembled it, assembled again and it started working don't know why...Now I've flashed CM I was on Genisis ROM earlier maybe that was the issue

zwodziarz said:
I've got the bootloop issue. Phone was turning on or not, just vibrating etc. I've dissassembled it, assembled again and it started working don't know why...Now I've flashed CM I was on Genisis ROM earlier maybe that was the issue
Click to expand...
Click to collapse
Hi sir
I decide to buy lg g4.
If i flash cm ,bootloop not happend again?
Thank you

It doesn't matter what firmware you have got. Bootloop is happening because of hardware failure.
Odesláno z mého LG-H815 pomocí Tapatalk

Damn...just made a huge mistake. phone bricked?

My son wanted to root his brand new phone. i have rooted 8 phones from different phones before with success..... but this time i f***d up...
Accedently installed this on his phone.
http://wccftech.com/flash-and-root-nexus-5-on-android-6-0-1-mmb29k/
executed flash-all.bat and it flashed the bootloader.
For the wrong phone...
It should have been this one..
http://wccftech.com/flash-and-root-nexus-5x-android-6-0-1/
Missed the X......
Now the phone will not even boot any more at all....cant enter bootloader.......does not power up at all.!!!
Jesus...what have i done.......
It here any chance at all to fix this somehow?

Hello and thank you for using Q/A,
because you can't enter bootloader, you can't do anything. You can try to send the phone to Google. Say: It didn't boot after OTA Update.
Kind regards
Trafalgar Square

Yeah it's most likely a paperweight. Try sending it to Google. Flashing the wrong firmware destroys a phone as you probably already know

well
hopesrequiem said:
Yeah it's most likely a paperweight. Try sending it to Google. Flashing the wrong firmware destroys a phone as you probably already know
Click to expand...
Click to collapse
I am totally aware of that....
but somehow one must be able to flash the bootloader from scratch....
Normally via special software etc.
That´s what i was hoping for....

Only thing I know to use is a riff box to jtag it. Not sure if they have one for 5x.

crowhater said:
I am totally aware of that....
but somehow one must be able to flash the bootloader from scratch....
Normally via special software etc.
That´s what i was hoping for....
Click to expand...
Click to collapse
Your use of the period seems rather condescending. And no, you as the end user cannot fix that. You did one of the few things that is unrecoverable unless you manage to get the bootloader to accept adb commands somehow.

crowhater said:
I am totally aware of that....
but somehow one must be able to flash the bootloader from scratch....
Normally via special software etc.
That´s what i was hoping for....
Click to expand...
Click to collapse
Didn't you say the phone won't turn on? The above scenario is not possible.

Well
bobby janow said:
Didn't you say the phone won't turn on? The above scenario is not possible.
Click to expand...
Click to collapse
Well. the bootloader is flashed into the phone from the beginning aswell during manufacturing. I work with electronics and software and i know there is always a way to reflash the bootloader. All the electronics comes in the beginning with no software at all, one only needs the proper software/hardware. Most probably by jtag....or if they have some other special tool for snapdragon 808.
Stupid of me not to see that the version i flashed was not for nexus 5X...and only for nexus 5
sight...

Good luck. Will Google not rma it?

Modified, Locked, S-on, Security warning. Bricked?

So it seems I'm in a very similar situation to people in other posts, and it's looking like my phone could be broken beyond repair.
UK, 02, stuck in a boot loop, Bootloader shows: Modified, S-On, Locked, Security Warning. I cant get into download mode (Download Mode failed to launch) but I can get into recovery mode (I get the red triangle with exclamation mark, Power+Vol Up gets me in). However, from what I read here in most other posts S-On + Locked + Modified means I wont be able to do anything. I have not flashed anything before I encountered this problem, merely let my battery run flat.
Is there anything I can do? I almost gave up, but this post here
HTML:
https://forum.xda-developers.com/one-m9/help/m9-locked-s-bootloader-download-mode-t3547560
gives me hope, as they seem in a similar situation with the exception of being able to get into download mode. Gives me hope I might be able to get into that and at least find out what firmware version I'm running.
Is there anything I can do or should I give up now and save my energy for sending HTC an angry email since this seems to be quite a common fault that's left quite a few people with bricks through (seemingly) no fault of their own?

Try "fastboot oem rebootRUU", if this isn't working you have a dead nand.

Strictly speaking, it's not an HTC specific problem. All phones with the Snapdragon 810 sooner or later suffer from similar issues. The heat of the processor kills the rest of the phones' hardware.
lucyr03 said:
Try "fastboot oem rebootRUU", if this isn't working you have a dead nand.
Click to expand...
Click to collapse
That command only works if the phone is booted to download mode which isn't possible according to the OP.
Sent from my HTC One M9 using XDA Labs

Ah! Thanks for that. I was scratching my head wondering how to get my pc to recognise my phone!
Dead NAND it is then?

blzbob said:
Dead NAND it is then?
Click to expand...
Click to collapse
Most likely. Sorry for the bad news.
Sent from my HTC One M9 using XDA Labs

Flippy498 said:
Most likely. Sorry for the bad news.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Ah don't mention it. Thank you both for your quick replies. Last question (big long shot) is there any hope of recovering any of the files on there? I don't mind long projects and I'm quite handy with a soldering iron. Prise it open, try to locate something resembling a flash drive, try to remove that without further damage and find a relevant adaptor? I'm assuming even if i were to attempt this I'd be in for a lot of headaches and probably wasted time, but figured I'd try to explore all avenues.
Obvious even if there were ways to do this, the NAND problem is probably going further hinder any remote chances of success.