Soft Brick from bad cable? - HTC 10 Questions & Answers

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.

Related

[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] Odd issue, trapped in bootloader.

Basically my issue is, bootloader works, nothing else does, anything that causes a reboot (rebootRUU) will instantly turn off the phone, the phone will obviously not boot into RUU mode.
I did a factory reset while under a custom ROM, it seems that won't boot either, I can flash recoveries, but surprise surprise, they won't boot.
Battery is at about 10%, seems to charge VERY slowly if I manually restart the device with the charge scripts (basically, the issue is anything that turns the device off, whether to boot into recovery or OS, or to simply reboot to bootloader, simply will turn off the device.
How can I fix this issue?
CID: HTC__621
Black 32gb One X, if it at all matters, hboot 0.95
ShadowOfScales said:
Basically my issue is, bootloader works, nothing else does, anything that causes a reboot (rebootRUU) will instantly turn off the phone, the phone will obviously not boot into RUU mode.
I did a factory reset while under a custom ROM, it seems that won't boot either, I can flash recoveries, but surprise surprise, they won't boot.
Battery is at about 10%, seems to charge VERY slowly if I manually restart the device with the charge scripts (basically, the issue is anything that turns the device off, whether to boot into recovery or OS, or to simply reboot to bootloader, simply will turn off the device.
How can I fix this issue?
CID: HTC__621
Black 32gb One X, if it at all matters, hboot 0.95
Click to expand...
Click to collapse
charge the battery, it will continue to just loop and not boot up until it has enough charge.
power it off completely then plug it into a wall charger and leave it for at least 3 hours, more if possible. DO NOT use a pc or laptop to charge, must be wall charger.

Need some help - possible defective hardware?

First off, S-off phone
So, I've been running the GPE rom posted by Joel for a while now with no issues... Today a friend wanted to see the phone, so I pulled it out of my pocket; hit power; nadda...
So I held power down for a while; got teh HTC screen; then nadda.
So we then attempted to get into recovery, power + vol down then selected recovery... Nadda, just a black screen.
I then redownloaded TWRP and fastboot flash recovery recoveryname.img, it tries to push it then it'll throw an error saying: "remote: image update error"
I looked around and found a thread with full directions with an RUU.. So I tried doing that, hwoever after clearing the cache via fastboot, when I try to do fastboot oem rebootRUU nothing happens.... sometimes teh screen goes blank, sometimes not.
Anything else I can try? I'm really wondering if it isn't defective hardware... .only had it 2 weeks too...
You are sure the phone is fully charged right ?
Sent from my Nexus 7 using Tapatalk 4
dottat said:
You are sure the phone is fully charged right ?
Click to expand...
Click to collapse
i was going to say the same thing. not sure how but i sometimes pull the phone out of my pocket with the screen on... so who knows which programs could have been tapped and running if it's bumping around in your pocket.
This is one of the reasons Verizon requires locked bootloaders now on all their phones. If the phone isn't even turning on, your first step should never be to try flashing a custom recovery or RUU (?!). If the phone has no charge and dies in the process, you could potentially brick it for good.
Sorry if that came across harsh, but... honestly, try charging your phone overnight first.
wireroid said:
This is one of the reasons Verizon requires locked bootloaders now on all their phones. If the phone isn't even turning on, your first step should never be to try flashing a custom recovery or RUU (?!). If the phone has no charge and dies in the process, you could potentially brick it for good.
Sorry if that came across harsh, but... honestly, try charging your phone overnight first.
Click to expand...
Click to collapse
Guess I should have put more details in the first post... when I got it into TWRP the first time it showed an 88% charge. I attempted to restore a backup and inside the recovery it would say it failed reading the memory and then it couldn't browse anything.
If I attempted to simply factory reset inside the recovery it would just lock up. If I tried to flash a rom via zip, it would lock up...
After a few times of rebooting it into the recovery I couldn't even click anything inside it without locking up.
it was at that point I tried to flash a different recovery and started getting the errors...
Anyways, more I researched it simply was a bad phone with defective hardware.
all good...

US Unlocked stuck in bootloop. Unable to boot into recovery/download.

Okay, I have never had to create a thread for this kind of thing. I have always been able to solve these issues. This time around, I have ran out of ideas. I have been searching and searching Google, Xda and any other Android forum. I have seen multiple threads with this problem, some cases exactly like mine. Not one thread with this problem ends with a solution, they're all just dead ends. My HTC 10 started doing this a couple days ago after a notification popped up saying that I was using an incompatible charger after using a Samsung USB cable on a Quickcharge 3.0 car charger. 30 minutes later, my capacitive touch buttons were not responding. So, I just figured that I would reboot and everything would be fine. Now, my phone is stuck in a bootloop with no signs of recovery. The only thing it will boot into is the white bootloader screen. Trying to boot into recovery or download just throws it back into a bootloop. When its powered off and I put it on a charger, the charging animation will show for about 15 seconds then, back into a bootloop. Trying to use a RUU.exe doesnt work, just a message shows up saying that my phone is below 30% charge. The device will show up in fastboot devices when its in the bootloader but, its useless. Trying to flash anything in fastboot fails or does nothing. The bootloader doesnt recognize 2PS6IMG.zip in the sd card. I really need my phone for work and cant afford to wait for HTC to repair it, especially since Hurricane Harvey hit their repair center in Houston. I've taken out the Sd Card and sim to see that would help but nothing. I let it die completely and still nothing.
My bootloader screen shows
Status: Official
***Unlocked***
***S-OFF***
I have been running Viper 3.5.0 for awhile.
This is my last option to see if anyone else has got through this problem without sending it off.
Thank you
bmx4lfe said:
Okay, I have never had to create a thread for this kind of thing. I have always been able to solve these issues. This time around, I have ran out of ideas. I have been searching and searching Google, Xda and any other Android forum. I have seen multiple threads with this problem, some cases exactly like mine. Not one thread with this problem ends with a solution, they're all just dead ends. My HTC 10 started doing this a couple days ago after a notification popped up saying that I was using an incompatible charger after using a Samsung USB cable on a Quickcharge 3.0 car charger. 30 minutes later, my capacitive touch buttons were not responding. So, I just figured that I would reboot and everything would be fine. Now, my phone is stuck in a bootloop with no signs of recovery. The only thing it will boot into is the white bootloader screen. Trying to boot into recovery or download just throws it back into a bootloop. When its powered off and I put it on a charger, the charging animation will show for about 15 seconds then, back into a bootloop. Trying to use a RUU.exe doesnt work, just a message shows up saying that my phone is below 30% charge. The device will show up in fastboot devices when its in the bootloader but, its useless. Trying to flash anything in fastboot fails or does nothing. The bootloader doesnt recognize 2PS6IMG.zip in the sd card. I really need my phone for work and cant afford to wait for HTC to repair it, especially since Hurricane Harvey hit their repair center in Houston. I've taken out the Sd Card and sim to see that would help but nothing. I let it die completely and still nothing.
My bootloader screen shows
Status: Official
***Unlocked***
***S-OFF***
I have been running Viper 3.5.0 for awhile.
This is my last option to see if anyone else has got through this problem without sending it off.
Thank you
Click to expand...
Click to collapse
Hold down the power button and vol down until your phone reboots. It'll take 20 seconds or so, and the capacitive button lights should flash until it reboots.
That should take you to download mode where the RUU.zip on your SD can be flashed.
If that doesn't work, try power + vol up + vol down, then switching to power + vol down when the screen goes black. I think I remember having to do that once when I first got the 10 for a different problem, but it could have been a different device

Stuck in boot loop even after factory reset. Able to get into bootloader and recovery

Hoping for some help or alternatives to fix my fiancee's Pixel XL. Last night the phone just kept flashing the 'G' logo on for 10 seconds, off for 10 seconds. She said the phone was close to dying before it happened, and I imagine it probably ended up draining the battery afterwards with the constant bootloop. Plugged it in all night but the charging screen didn't come up and would just stay in the bootloop. I could get it into the boot loader (power button and volume down), but it wouldn't go into recovery mode and instead would go right back to the boot loop.
So I tried a battery pack to charge it and it still didn't show charging, but I was able to get it into recovery mode eventually, but still boot loop afterwards. At one point, after leaving it on boot loader menu while attempting to charge, it eventually just tried to start itself and made its way to the second Google splash screen after the main G logo. Looked like it froze there though and I couldn't get it to that point again.
On my way to work this morning I tried plugging it into my car's USB port after powering off from the boot loader, and this time I kept flashing that it was charging (looked like it was 3/4 charged but not sure how accurate that is). So I got into recovery again and tried 3 factory resets consecutively. Still bootloop after attempting a startup afterwards. There was a similar issue a couple weeks ago where it looked like it was stuck in a bootloop, but it turned out the phone actually was dead that time and the charger wasn't working. Once we switched chargers it booted right up.
Any other suggestions or possibilities? I don't have much troubleshooting experience otherwise. Phone is fully stock, Google Fi. Any other info I can provide please let me know!
well, i'm not sure if it makes a difference, but now for some reason i can't get into recovery mode again. just goes into the boot loop. It also goes into the boot loop as soon as I plug the phone in to charge.
cgibsong002 said:
well, i'm not sure if it makes a difference, but now for some reason i can't get into recovery mode again. just goes into the boot loop. It also goes into the boot loop as soon as I plug the phone in to charge.
Click to expand...
Click to collapse
I assume you can't get into the bootloader using power and volume down buttons?
I have always been about to get into the boot loader. Actually i can get into recovery again as well. Seems if i let it sit for a while it'll go to recovery again. Maybe heat related.
My OG Pixel did the same thing to me one morning. I tried everything to revive my pixel but nothing worked. I did some digging and it turns out there is an issue with the storage on the phone. It's just a old fancy paper weight.
cgibsong002 said:
I have always been about to get into the boot loader. Actually i can get into recovery again as well. Seems if i let it sit for a while it'll go to recovery again. Maybe heat related.
Click to expand...
Click to collapse
If you can get into recovery, have you tried to sideload a full ota.zip (not an update)?
mozhno said:
If you can get into recovery, have you tried to sideload a full ota.zip (not an update)?
Click to expand...
Click to collapse
I haven't. I see that Google has all the ota's on their site. Is there a specific one that i might want to try? The same one? Go back a few? Will i even be able to sideload if my phone is fully stock?
Edit: sideload adb successfully but no change. I loaded the 6-5 ota which was what i already had.
cgibsong002 said:
I haven't. I see that Google has all the ota's on their site. Is there a specific one that i might want to try? The same one? Go back a few? Will i even be able to sideload if my phone is fully stock?
Edit: sideload adb successfully but no change. I loaded the 6-5 ota which was what i already had.
Click to expand...
Click to collapse
Sounds as if it's time to just try stuff and see what sticks. Regarding using an ota, it works if you are stock, and I sideload it even if I have installed majisk or installed another kernel. It typically works for me with fewer chances of blowing things up than flashing a stock image. Regarding what to try next, you may have already gone into recovery to check the install function to see if your storage still appears and try to flash anything that worked in the past; if you have a backup in twrp you could try to restore it; you could wipe cache and dahlvik; or even sideload an earlier ota version that worked. Since the 6-5 ota did not work nothing really jumps out to me as obvious. One final caveat, I once had to reboot a sideloaded ota a second time before my pixel booted properly. If I think of something else I'll post again.
I took it to ubreakifix and they told me that this is indeed a known issue with pixel xl's that they all suffered from a faulty motherboard and that is indeed the cause here. Said he thought there was actually a class action about it so I'll have to look into it. Really pisses me off that Google repeatedly told me it's not a known issue when their authorized repair center says it is.
Anyway i have a warranty with Upsie that I'm hoping to get this replaced with. We'll see.
cgibsong002 said:
I took it to ubreakifix and they told me that this is indeed a known issue with pixel xl's that they all suffered from a faulty motherboard and that is indeed the cause here. Said he thought there was actually a class action about it so I'll have to look into it. Really pisses me off that Google repeatedly told me it's not a known issue when their authorized repair center says it is.
Anyway i have a warranty with Upsie that I'm hoping to get this replaced with. We'll see.
Click to expand...
Click to collapse
Good luck
I'm assuming you tried booting into twrp recovery, going to reboot, and picked slot A ( or B if already in A) to reboot to and then rebooted system? A lot of the times simply switching slots from recovery and then rebooting is the fix. At least for me.
手机早期经历的情况得说明一下。root没有?Twrp是谁的?
Also, for anyone else having this issue, try rebooting into the bootloader. Connect to PC, and try fastboot --set-active=a
If this doesn't work, try booting back into your recovery image using fastboot boot *whatever you named your TWRP recovery image* and then flashing your twrp.zip again in recovery, and when rebooting if you're in slot B choose slot A in recovery to boot into.
Also keep in mind in Windows 10, it uses Powershell, so commands have to be typed in .\fastboot not just fastboot or it won't take it.

Categories

Resources