Develop Bugs

HTC One X bricked or repairable?

Hey Guys,
I was wondering whether anyone would be nice enough to help me with my HTC One X? I am not sure whether the device is repairable or not in its current state, so I will just explain what I did, and hopefully someone will be able to shed some light on the situation.
1. I unlocked the device using HTC Dev
2. I installed ClockworkMod Recovery (this method)
3. I created a backup using ClockworkMod Recovery
4. I flashed this custom ROM on the device (Cool OneX v2)
5. I extracted boot.img from the Cool-ROM.zip and flashed it using fastboot
6. The device would not get past the HTC boot screen, so I decided to restore from the backup
7. Rebooted device, ROM appeared to be back to stock, battery indicator looked like it was around 70%, jumped to red icon and device turned off
8. Restarted device again whilst charger was plugged in, ROM did not appear to recognise charger, device turned off
9. Tried Cool OneX V2 ROM again and re-flashing boot.img, did not work again
10. Tried wiping battery stats in recovery
I presume that the ClockworkMod Recovery restore includes boot.img?
The device currently has no charge (permanently or not, I am not yet sure), though I can turn it on whilst it is plugged in. The red indicator is currently flashing. The device will however not stay turned on once Android has loaded. It will stay turned on whilst in fastboot and recovery.
Is it possible for me to flash another ROM on the device using fastboot or recovery? The device obviously doesn't have removable storage, and only has Cool-ROM.zip and the restore on it.
Any help would be highly appreciated. Does this sound like a hardware or a software related issue?

i think you have to reflash the original boot.img via fastboot.

N3m3515 said:
i think you have to reflash the original boot.img via fastboot.
Click to expand...
Click to collapse
Thanks for your reply, does it matter which stock ROM I get the boot.img file from? All I know is that I have the Singapore version of the HTC One X.

i would suggest the one matching your stock rom but you can try any other boot.img. but be carefull your battery wont run out of power.

N3m3515 said:
i would suggest the one matching your stock rom but you can try any other boot.img. but be carefull your battery wont run out of power.
Click to expand...
Click to collapse
I just tried flashing a boot.img file, though it did not work.
c:\fastboot>fastboot flash boot boot.img
sending 'boot' (4284 KB)...
OKAY [ 0.577s]
writing 'boot'...
FAILED (remote: battery low)
finished. total time: 0.665s

http://forum.xda-developers.com/showthread.php?t=1609190
follow this guide

Thanks for your help, though the more that I think about it, the device has a faulty battery. You can leave it plugged in for hours, though the red light will not stop flashing. The device has enough power to boot into fastboot and recovery whilst turned on and plugged in, though not Android itself.
Is it possible to damage the battery by flashing a ROM / boot.img, or is this more likely to be a fault that coincidentally popped up whilst I was flashing the device?

Hang on a minute, can the device not charge when turned off / in recovery, as a result of installing ClockworkMod recovery?
http://forum.xda-developers.com/showpost.php?p=25162439&postcount=4
Still doesn't explain why the device won't charge whilst booted into Android..
I might try installing the custom ROM again, and leave it charging whilst it is stuck on the splash screen.

The exact same thing happened to me a couple nights ago. I followed this guide:
IF YOU HAVE ANY UNSIGNED RECOVERY:
1.- GO TO RECOVERY
2.- FORMAT SYSTEM
3.- RESTART NORMALLY
4.- YOUR PHONE WILL STOPS IN "HTC QUIETLY BRILLIANT" SCREEN
5.- PUT YOUR PHONE TO CHARGE (no light notification appears)
6.- LET IT CHARGE FOR A COUPLE HOURS (i put mine to charge for a complete night)
7.- Now restore your RUU, Flash, etc...
I left it charging on the white HTC Quietly Brilliant screen for about 4 1/2 hours. There will be no light while it's charging, and no indication that charging is complete. After 4 1/2 hours I unplugged the phone, booted into CWM Recovery via Volume down + Power and restored the Nandroid I had made of my stock ROM. I was then able to let it charge fully while the device was on and proceeded to re-flash ARHD ROM.
Good luck! It's not bricked man, it's just being pissy.

If you want to get some charge in your battery, boot into fastboot and flash the stock recovery then shut down the device and leave it to charge. The led indicator should be solid red indicating the device is charging and will then turn green to indicate the device is fully charged.

nooomoto said:
I left it charging on the white HTC Quietly Brilliant screen for about 4 1/2 hours. There will be no light while it's charging, and no indication that charging is complete. After 4 1/2 hours I unplugged the phone, booted into CWM Recovery via Volume down + Power and restored the Nandroid I had made of my stock ROM. I was then able to let it charge fully while the device was on and proceeded to re-flash ARHD ROM.
Good luck! It's not bricked man, it's just being pissy.
Click to expand...
Click to collapse
Thanks for the advice, I currently have it charging on the 'HTC One / beats audio' boot screen. The red LED was flashing whilst the device was turned off and plugged in, it is now a solid red LED, which hopefully means that the device is charging.
rogersnm said:
If you want to get some charge in your battery, boot into fastboot and flash the stock recovery then shut down the device and leave it to charge. The led indicator should be solid red indicating the device is charging and will then turn green to indicate the device is fully charged.
Click to expand...
Click to collapse
I will leave the device charging on the bootscreen for a little while, then will attempt to flash stock recovery back onto the device. (which I presume is endeavoru_recovery_signed.img)

MarrkDaviid said:
I will leave the device charging on the bootscreen for a little while, then will attempt to flash stock recovery back onto the device. (which I presume is endeavoru_recovery_signed.img)
Click to expand...
Click to collapse
Yep that's the one

This sort of thing recently happened to me, it was a right ***** to sort out. Once you have enough charge you will be able to flash via fastboot and get up and running again.
Sent from my HTC One X using Tapatalk 2

nooomoto said:
IF YOU HAVE ANY UNSIGNED RECOVERY:
1.- GO TO RECOVERY
2.- FORMAT SYSTEM
3.- RESTART NORMALLY
4.- YOUR PHONE WILL STOPS IN "HTC QUIETLY BRILLIANT" SCREEN
5.- PUT YOUR PHONE TO CHARGE (no light notification appears)
6.- LET IT CHARGE FOR A COUPLE HOURS (i put mine to charge for a complete night)
7.- Now restore your RUU, Flash, etc...
Click to expand...
Click to collapse
The instructions unfortunately did not work. :/ There is still no battery when I boot into Android, and the device turns off. The device freezes at the screen just after 'HTC Quietly Brilliant', the one that says 'HTC One / beats audio'. There is a solid red LED whilst the device is stuck on this screen, which does not go away if I pull out the charger.

MarrkDaviid said:
The instructions unfortunately did not work. :/ There is still no battery when I boot into Android, and the device turns off. The device freezes at the screen just after 'HTC Quietly Brilliant', the one that says 'HTC One / beats audio'. There is a solid red LED whilst the device is stuck on this screen, which does not go away if I pull out the charger.
Click to expand...
Click to collapse
That method is designed to give you enough charge to be able to flash the stock recovery via fastboot and allow the device to charge whilst off.

rogersnm said:
That method is designed to give you enough charge to be able to flash the stock recovery via fastboot and allow the device to charge whilst off.
Click to expand...
Click to collapse
I was able to successfully flash the stock recovery, though I did a really stupid thing (I blame sleep deprivation). I thought that I had already restored from recovery, when the custom ROM was actually on the device. In other words, I have lost my nandroid backup.
I presume that it is not possible to convert .zip ROMs into .img files?
Does anyone have a nandroid that would be compatible with my device? It would be really really appreciated if you could upload it.
HTC One X S720e
MID: PJ4610000
CID: none (HTC__044 according to CID Getter)

I'm not too sure that would work, I have never heard of anyone using a nandroid from another handset. I would suggest unlocking your bootloader again then reflash touch recovery and install your rom of choice.
First thing I always do after root is a nandroid backup and save it on dropbox and pc, hindsight is pretty useless though.
Sent from my HTC One X using Tapatalk 2

MarrkDaviid said:
I was able to successfully flash the stock recovery, though I did a really stupid thing (I blame sleep deprivation). I thought that I had already restored from recovery, when the custom ROM was actually on the device. In other words, I have lost my nandroid backup.
I presume that it is not possible to convert .zip ROMs into .img files?
Does anyone have a nandroid that would be compatible with my device? It would be really really appreciated if you could upload it.
HTC One X S720e
MID: PJ4610000
CID: none (HTC__044 according to CID Getter)
Click to expand...
Click to collapse
Have you checked to see if there is a RUU available for your region/carrier?

I am currently downloading a few different ROMs from here:
http://www.filefactory.com/f/7cc7b2fbdd03c031/
Trying to flash boot_signed.img and system.img, though I am running into more difficulties.
c:\fastboot>fastboot flash boot boot_signed.img
sending 'boot' (4278 KB)...
OKAY [ 0.583s]
writing 'boot'...
(bootloader) Format partition LNX done
OKAY [ 0.374s]
finished. total time: 0.957s
c:\fastboot>fastboot flash system system.img
sending 'system' (974140 KB)...
FAILED (remote: (00000006))
finished. total time: 0.044s
The error apparently means that the file is too big, based on what I have been reading at least. Will see if any of the others work, otherwise I will have to look into flashing another custom ROM.
I like the look of Android Revolution HD, though the firmware package required, is apparently not compatible with my devices CID. Whatever that means.

MarrkDaviid said:
I like the look of Android Revolution HD, though the firmware package required, is apparently not compatible with my devices CID. Whatever that means.
Click to expand...
Click to collapse
If you installed the 1.28 OTA update when you were on the stock rom then afaik you don't have to install the firmware package.
Btw, if you still have the Cool OneX V2 rom installed, try flashing the rom's boot img back on with fastboot and then enter the command "fastboot erase cache". After that reboot and see if the rom loads.

[Q] htc one x bricked. not charging. not booting. only bootloader

usual story.
got an htc one x. flashed unlocked all going well. installed a bad rom (did not make a back up)
froze at splash screen. only late last night i found disaster recovery, so i put it to download and shut off the phone. boot back up this evening and tried to install recovery re-lock bootloader, clear cashe etc but. i got a low battery warning when trying to flash.
i didn't have the latest clockwork mod for charging installed; and battery is too low to flash to it.
this is where things get different. i used the boot loader to power down. i plugged it in to the wall to charge and i got this strange flashing red led(not orange) after about an hour it went solid red. had it charging from the wall socket for well over 4 hours now with the solid red led.
then all of a sudden the led starts to flash red again. so i disconnect the phone and try to boot.... nothing happens. try bootloader mode(power + vol.dwn) nothing.
i had to hold the two buttons then plug in the wall charger. then it went into bootloader. problem is it says relocked AND security warning....... and still after all that time charging. i still get low battery warning @ flash.
so i tried to turn off the device again using the power down option. two things happen here. 1)if the charger is in the screen goes black and instantly restarts to fastboot usb menu. 2)if it isnt in it will turn off and wont turn back on (splash screen or bootloader) until the charger is back in.
so what ive done as of now is plug it in to charge over night and hope this thread can shed some light.
additional info:
ruu version: 'RUU_ENDEAVOR_U_ICS_40_hTC_Asia_WWE_1.28.707.10_Radio_1.1204.103.14_release_257076_signed.exe
os version: 1.28.707.10
clockwork mod version: 5.8.2.7
plz any help would be invaluable
EDIT: just turned on phone about ten minutes after i plugged it back in to the charger (held power button alone) splash screen is back (yay!!) but still battery low when trying to flash in
fastboot usb. ima try in the morning after a full night to the charger. fingers crossed

http://forum.xda-developers.com/showthread.php?t=1598336
no need to spam xda with two threads !!!

kasalamite said:
http://forum.xda-developers.com/showthread.php?t=1598336
no need to spam xda with two threads !!!
Click to expand...
Click to collapse
srry posted last night but would not show the thread... so i figured i couldn't so i tried to post in an existing thread. now i dont know how to delete that other one...

FIXED
well never mind the fact that i loaded a plethora of info onto this post and nothing.
but besides that i got it working. in the disaster recovery tut it only lists using the ruu through a flash... never stating that you can just run the file directly and not go in %temp% and get the rom.zip(excepting for the recovery_signed.img). simply find your version of the ruu that you need, flash back to the stock recovery image (within the rom.zip) relock bootloader place device in fastboot and run from pc.
the only hard part is getting it to charge... dont know how mines took charge but i pluged it into the sockets @ my school (long story read this thread: http://forum.xda-developers.com/showpost.php?p=26156147&postcount=20).
when i pluged it in the light went solid red instantly no blinking. after about an hour of charge i pressed the power button and it went to the splash screen (still was on a older CWM which doesn't support charging) left it at the splash screen for the remainder of the class (about another hour) unplugged entered bootloader.
@ this point i had no security warning under relocked. but i used the power down option, took it home and tried to unlock/flash to the latest version of CWM so i could charge. it worked without a hinge.
anyone know why it took charge on an older CWM?
note i got the phone back up and running and the first thing i did was make a nandroid back up

hi i dont have an answer to your question but i have a question to your answer am curently suffering the same problem i can flash the stock cwm because of low battery, and i know when in boot mode it doesnt charge so i rebooted the phone it took me to the htc logo and its displaying a solid red light does this mean its charging or what (the boot loader is re-locked so i can flash stock cwm but cant due to low charge)

Noob badly. But I think it should be charging. Could b wrong. Leave it there for a couple of hours and try again. Mayb fixed. Give it time and try again.
Sent from my HTC One X using XDA

Same thing is happening to my phone. and its bootloader is locked and cannot be unlocked because of the charging. its usb debugging wasnt turned on either before it went down.

Please help anyone?
Guys I have Htc One X. I rooted it then I thought to install a custom rom (resurrection remix) and gapps. so when I was in the CWM recovery I installed the mod while it was installing it said error no file contents but it installed successfully anyway. after that I installed Gapps but it got an error and said Installation aborted. I then started panicking and I tried to restore the backup but nothing happened, then I re-locked the bootloader with battery below 30% then I used the batch file to charge it then I unlocked it again. Now I want to download a stock rom I tried 2 one was a newer version than what my phone actually is and the other one was a lower version than what my phone actually is. I then tried alooooooooooot to search for the appropriate one for my phone but I didn't find it so I thought to continue with installing custom rom anyway but the problem is that I need to get the new mod zip file and new gapps zip file into my phones sdcard but I can't do that/I don't know how. My phone isn't recognized by my pc ( I can't browse it's files) and I tried using adb in command prompt which is very complicated for me however I searched on the internet and tried to do the same but then it says "adb server is out of date killing" then I found one adbFix.exe that said that the adb in HTC sync manager folder is causing a conflict but then the Fix file said that its ok and no problems are there. Now I need to put custom rom and gapps zip files to my phone's sdcard but I can't. Please I would be very grateful to anyone who would help me and guide me and If I'm posting in the wrong forum or thread then please forgive me for this is my first time I made an account on XDA and my first ever comment/

[Q] What exactly is on the emmc and what should not work when it is fried ?

After self rebooting while trying out vlc beta et freezing:
My DZ refuses to (symptom is I end stuck on green HTC logo on white screen for each of these possibilities):
* boot to OS
* boot to recovery (through bootloader) (So no adb possible)
* factory reset from bootloader
It will however:
* boot to bootloader (Vol-+Power) and go to fastboot
* accept flashing via fastboot (Ive flashed various recoveries and finally even reflashed stock RUU hoping it could help)
I've notice that when I tuen it on normally, I vibrates then I get HTC logo than after a few seconds it vibrates once and stays on HTC logo
For the record this has allready happend once in the past... and I eventually got it to reboot by leaving the DZ batteryless for a hole weak (I tried 24h, 48h and eventually a weak) before putting the battery back in and seeing it let me boot it to recovery... My reasonning behind this wait was that there might be accumulated static somewhere and that leaving it out batteryless would drain all juice out and the static with it (based on computer motherbaord issues allready encountered)... Since then I have been on Virtuous Unity, Affinity, Quatro and lately Andromadus Audacity Beta1-4 and lastly mimicry whithout any problems.
So right now It is again sitting out battery less for several days as 24h has not sufficed...
As I wait (I'm suffering o an old iPhone 2g...) I have been going through all the forums looking for information... And have found tons of issues concerning the emmc and its "fryability". However everytime people talk about fried emmcs they seeem to be booting to recovery without an issue...
If the phone never boots, I'm guessing there are 3 possible explanations:
* emmc
* motherboard
* cpu
Now I've found that all can be repurchased (yeah warranty gone for me as I'm S-Off and unless I can boot one last time permroot and revert gfree I will stay S-Off) at http://www.parts4repair.com/htc-desire-z/
But the real question is: Is there a way to determine if emmc is fried (I'm booting to bootlader which seems to be on emmc from my understanding)
Finally I've allways assumed that it is useless to leave the phone at HTC logo more than 30 seconds... is this a mistake ?
Thanks in advance for any help/answers
P.S. Does the battery charge when in bootloader or fastboot ? If not I might not be able to reccharge it once it is drained...

http://forum.xda-developers.com/showthread.php?t=1039504
http://forum.xda-developers.com/archive/index.php/t-1456036.html
http://forum.xda-developers.com/showthread.php?t=1051995
http://forum.xda-developers.com/showthread.php?t=1456036
first see what chip you have, you can use adb commands within your bootloader
have you been able to get fastboot to work at all?

Thanks for all the links, I had allready read those threads and those are what generated my questions.
Yes fastboot seems to work (flashing ends with OK every time)
I have tried to adb to the phone when in bootloader but that is a no go (From my research I thought the phone had to be either booted normally or in recovery to be able to adb to it and since I can do none of those two...)

When I reflashed stock 1.34 ROM from fastboot it overwrote the bootloader and replaced the engineering one with the stock one (I can see that when in bootlader)... So am I correct in assuming that the emmc is not fried and that all flashboot flashes are therefor working ?

to my understanding some blocks in the emmc get corrupt and others don't, just being able to rewrite hboot or recovery doesn't mean everything is fine it may just mean this block is ok. where you able to write a new recovery and boot into it?
Sent from my HTC Vision using xda premium

Flashing a recovery seems OK (i.e. according to command line it worked) but booting to it does not work...
I've tried cwm and 4ext (used to be on 4Ext).
I'll wait out my week with the battery pulled out and see what happens when I put it back in... But if it does boot I'm S-Oning it and send it in for warranty because this behavior isn't normal...

dwardo said:
Flashing a recovery seems OK (i.e. according to command line it worked) but booting to it does not work...
I've tried cwm and 4ext (used to be on 4Ext).
I'll wait out my week with the battery pulled out and see what happens when I put it back in... But if it does boot I'm S-Oning it and send it in for warranty because this behavior isn't normal...
Click to expand...
Click to collapse
Well no luck...
I've reflashed it with HTC 1.34.405*RUU.exe --> Seemd to go fine but didn't reboot after
I've reflashed using the corresponding PC10IMP.zip on /sdcard and booting into bootloader:
where I got
BOOTLOADER ok
BOOT ok
RECOVERY ok
SYSTEM ok
etc...
Everything said OK... but still won't boot to OS or to recovery stays on green HTC logo on white background.
I've noticed 2 things:
* that on booting it vibrates once then a few seconds (~5) it vibrates once again while on HTC green on white logo and just stays there after...
* that when it is off and I plug the usb, the led does not turn on... (indicator of mobo problem ?)

Well tonight I tried reviving the phone again... 10 days without touching the phone...
Lets' back up here... 10 days ago I flashed a modified Stock PC10IMG of 1.34.405.5 RUU - modified because I repalced bootloader with DZ engineering one and recovery with 4ext-touch-recovery-1.0.0.3-RC3. But the phone would not:
* boot to recovery
* fastboot boot 4ext-touch-recovery-1.0.0.5-RC3.img
* fastboot boot boottosd.img
So back to tonight... I tried
fastboot boot 4ext-touch-recovery-1.0.0.5-RC3.img
and it booted to recovery right away (less than 10 seconds... in the past I have left it for more than 10 minutes without succes...) and complained that cache partition needed wiping... (This is odd to me I thought the PC10IMG flashing would do that...)
So anyways I did just that and then went for the emmc version and got:
#cat /sys/class/block/mmcblk0/device/name
SEM04G
So normally the good emmcs...
Then I rebooted to recovery from Nand flash (not fastboot) worked and finaly rebooted to stock 1.34.405.5 (i.e. rooted for now)
So now I'm just wondering WHAT HAPPENED ?
I did nothing in between 2 series of similar boot tests... except wait 10 days.
I'm leaning more and more towards static electricity problems...
So now I'm wondering... Get back to S-on ? but I'ts working so servicing will not be accepted... Or going back to Andromadus mimicry (I have a backup I can apply )
Well going for andromadus as I allready bought a phone with broken lcd for parts !
If anyone has commands he would like me to run I'm more than willing to do it...

Help: hard bricked from Stock Rom?

Hello,
I ran into some serious problems with my OneX about an hour ago...
here's my problem:
I flashed Ice Cold Jelly about a week ago with the provided boot.img. Everything worked fine until now. My Phone started to not turn back on after I turned off the screen so I turned it off using the 8sec powerbutton. After this it booted up and after around 5 mins the same thing happenend again.
So I wanted to go back to stock with a cwm recovery img I made just before I flashed the ICJ-Rom. I booted into the bootloader > fastboot and flashed the stock boot.img via the OneX AIO kit. After that I went into the cwm recovery and restored my stock rom.
The phone was plugged into the Pc during the whole process!
After the recovery finished I rebooted the phone and the stock boot animation greeted me so I plugged it off the Pc and just as I wanted to type in my pin the touchscreen didn't react. As I tried to figure out what happened the auto-lock kicked in and turned the screen off. Tried to turn it on again but it failed. Tried to power it off and on again pressing power for 8sec and rebooting it but no response.
Now I'm sitting here with my OneX which does not react to any button, is not recognized by the Pc and no powerLED when I plug it into the Pc or wall.
Some further information:
power was at 70% when I started
Cid is HTC__002
hboot was 0.95 (I'm not sure about that but it was before v 1.0)
Security was S on
I'm really helpless and a bit afraid right now... so if anyone could help me it would be just awesome!
Atm it's plugged into the wall, as I read in some other threads that after several hours this might help reviving it.
Thanks for any help!

Forunke said:
Hello,
I ran into some serious problems with my OneX about an hour ago...
here's my problem:
I flashed Ice Cold Jelly about a week ago with the provided boot.img. Everything worked fine until now. My Phone started to not turn back on after I turned off the screen so I turned it off using the 8sec powerbutton. After this it booted up and after around 5 mins the same thing happenend again.
So I wanted to go back to stock with a cwm recovery img I made just before I flashed the ICJ-Rom. I booted into the bootloader > fastboot and flashed the stock boot.img via the OneX AIO kit. After that I went into the cwm recovery and restored my stock rom.
The phone was plugged into the Pc during the whole process!
After the recovery finished I rebooted the phone and the stock boot animation greeted me so I plugged it off the Pc and just as I wanted to type in my pin the touchscreen didn't react. As I tried to figure out what happened the auto-lock kicked in and turned the screen off. Tried to turn it on again but it failed. Tried to power it off and on again pressing power for 8sec and rebooting it but no response.
Now I'm sitting here with my OneX which does not react to any button, is not recognized by the Pc and no powerLED when I plug it into the Pc or wall.
Some further information:
power was at 70% when I started
Cid is HTC__002
hboot was 0.95 (I'm not sure about that but it was before v 1.0)
Security was S on
I'm really helpless and a bit afraid right now... so if anyone could help me it would be just awesome!
Atm it's plugged into the wall, as I read in some other threads that after several hours this might help reviving it.
Thanks for any help!
Click to expand...
Click to collapse
Okay, did you flash the ruu's stock boot.img and system recovery the relock the bootloader before flashing the ruu?
---------- Post added at 02:37 AM ---------- Previous post was at 02:24 AM ----------
sorry i misread it. You flashed a backup of your stock rom and flashed the boot.img. i would recommend trying to flash the original ruu if youre getting errors. The fails to turn it on sounds like it out of battery. If you can find the thread there is a batch file you can run to start it charging through your pc

XxJibblesxX said:
The fails to turn it on sounds like it out of battery. If you can find the thread there is a batch file you can run to start it charging through your pc
Click to expand...
Click to collapse
I hope that's the problem, but I can't imagine my phone using up 70% of the battery plus the usb hub power in about half an hour.
...this all seems to me like there's a hardware fail (which I really don't want to) as the system booted and then crashed into brick mode.
I'm not home tonight but the phone is on usb and tomorrow I'll try the tool and report my findings
Edit:
Ok, the phone spent 6 hours plugged into the pc and until now it was plugged into the wall but nothing. It seems to be completely dead -.-
Tried the batch file but there's nothing much to try when I can't even get into fastboot. The phone simply won't react to anything...
I will send it back as it's only about a month old and hope the warranty will fix it.
There is a stock rom with stock kernel on it so I hope they don't bother about the bootloader beeing unlocked.
But what I think is that there is a serious hardware problem. As I continued to read through other posts I realized that I had the same audio problems (stuttering and slowing down of the music) like some others...
If HTC tells me something about what caused the problem I'll post it here.
So far thanks for your help

Soft Brick from bad cable?

So earlier today I plugged in my charger into the phone, and it gave me an error messaging saying something about the cable being damaged, and System UI crashed. I unplugged it and made a mental note to buy another charger.
The device was having some issues with SystemUI properly rebooting, so I restarted the phone and got caught into a boot loop.
The device will not go past the HTC splash screen, just rebooting every few seconds.
It doesn't reboot when I go into the white screen bootloader, nor does ADB or fastboot oem detect it.
If I select download or recovery mode, one of two things happens:
1) It displays the monochromatic HTC logo for a few seconds and then reboots back into the normal bootloop.
2) It stays in the monochromatic HTC logo without doing anything else.
ADB does not work in any state, nor does trying to flash an RUU.
I've tried sticking an RUU with an SD Card and going into download mode, but nothing happens.
The device was running Leedroid at the time.
The bootloader is unlocked, and it is S-ON. It is a T-Mobile device with the Marshmallow Firmware installed.
I would very much appreciate help for this as I've been searching for solutions the entire afternoon.
I don't quite understand how a faulty cable would cause a bootloop but not completely fry the device.
Thanks.

Lohboh said:
So earlier today I plugged in my charger into the phone, and it gave me an error messaging saying something about the cable being damaged, and System UI crashed. I unplugged it and made a mental note to buy another charger.
The device was having some issues with SystemUI properly rebooting, so I restarted the phone and got caught into a boot loop.
The device will not go past the HTC splash screen, just rebooting every few seconds.
It doesn't reboot when I go into the white screen bootloader, nor does ADB or fastboot oem detect it.
If I select download or recovery mode, one of two things happens:
1) It displays the monochromatic HTC logo for a few seconds and then reboots back into the normal bootloop.
2) It stays in the monochromatic HTC logo without doing anything else.
ADB does not work in any state, nor does trying to flash an RUU.
I've tried sticking an RUU with an SD Card and going into download mode, but nothing happens.
The device was running Leedroid at the time.
The bootloader is unlocked, and it is S-ON. It is a T-Mobile device with the Marshmallow Firmware installed.
I would very much appreciate help for this as I've been searching for solutions the entire afternoon.
I don't quite understand how a faulty cable would cause a bootloop but not completely fry the device.
Thanks.
Click to expand...
Click to collapse
So you can't even get to download mode by holding power+vol down for several seconds?

Tarima said:
So you can't even get to download mode by holding power+vol down for several seconds?
Click to expand...
Click to collapse
No, it just brings up the same issue of it getting stuck on the monochrome HTC logo.

no idea as i've never had this happen, but when i've had issues in the past i'd let the battery drain completely, then charge it a little, then try booting to download mode. maybe you could try that? did you have twrp or any custom recovery installed?

ffuser1 said:
no idea as i've never had this happen, but when i've had issues in the past i'd let the battery drain completely, then charge it a little, then try booting to download mode. maybe you could try that? did you have twrp or any custom recovery installed?
Click to expand...
Click to collapse
I've tried that, and I have the latest TWRP.