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.
My m9 randomly turned off and went into a boot loop. I have read many many posts and I am trying to best understand the issue/solution. Device is:
Software status: official
Locked
S-On
It wont boot into recovery or download mode, I just get an HTC screen where the background is black and the HTC letters are silver/white (there are no errors on that page, just the logo). Basically the normal boot screen with different colors. Tried connecting via adb and that doesnt work. The only thing I can get into is the bootloader menu.
Thanks
I was able to get it to boot twice (by letting the battery die). But it went back into a boot loop. Ideas?
Hey!
My P8000 (running Cm12.1, Twrp) is stuck in a bootloop because of xposed. I know how to fix this, if I could enter recovery, but I can't because my battery is to low. I only can enter the bootloader (where you can choose recovery mode, fastboot mode or Normal boot). But if I choose one of these nothing happens and the screen turns off. If I plug it to the charger it boots and is stuck in the bootloop, and draining the battery.
Anyone an idea how to get my elephone charged?
If a factory reset is necessary, that's no problem, just tell me how to get there!
Tie
Hello everyone! My One M9 has been stuck on boot screen after it's battery drained completely. It runs AICP 8.1 and adb does work, but I get booted into system every time I try to boot or reboot into bootloader, recovery, or download mode. The htc splash screen also takes longer before trying to boot the system. I tried unplugging the battery but it didn't have any effect. Does anyone have any tips or ideas?
Faulty button?. If it bypasses download mode you might have a stuck vol- button.
Hey guys,
I started having this issue randomly start occurring a few hours ago and so basically the phone keeps boot looping. This is not a normal boot loop as I can get into fastboot but it still keeps restarting once I'm in it; as if the power button is stuck. I have tried to power down the phone but couldn't so I just let it drain itself over night. I have tried to charge it and I have noticed that the charging icon is in a sort of loop where it tries to turn on then goes to the warning page of an unlocked bootloader and then boot loops. I have no idea what caused this and I can't follow any of these other solutions as I can't stay in fastboot long enough to use adb.
Edit 1:
Just tried to quickly flash the stock bootloader while simultaneously holding power+down to stay in fastboot but still boot loops. I cannot even toggle through the settings of the fastboot mode and the screen just keeps 'refreshing' every half a second so I can't really do much.
Edit 2:
It has just fixed itself overnight and I am able to boot normally after flashing the magisk_patched boot.img
OS: Android 10 stock
Rooted: Magisk latest
Custom Kernel: ElementalX