Hey guys,
Don't usually have to post but after searching all day I can't find a way out of this loop. My 10 is currently flashing the white HTC splash and rebooting endlessly. That's no big deal, but I ALSO have no recovery or download mode access.
The ONLY thing I can do to interrupt the loop is access fastboot by holding Vol UP + Vol Down on restart. Unfortunately trying to "reboot to recovery" only flashes the dark HTC Logo then immediately restarts to the original bootloop. Attempting to "reboot to download mode" simply resumes the boot loop.
The device is recognized in fastboot on my PC but unfortunately I cannot flash or erase anything because I'm in S-ON, so practically none of the fastboot commands work. I have been using TWRP recovery and Viper10 Rom.
Any help getting out of this loop is greatly appreciated. I was going to give up and pay the deductible and replace it, until I found out that the phone is backordered until October and my alternative is an LG, which I can't stand.
S O S!
Currently experiencing the exact same thing myself:
http://forum.xda-developers.com/htc-10/help/htc-10-bootlooping-t3441710
Valandil11 said:
Currently experiencing the exact same thing myself:
http://forum.xda-developers.com/htc-10/help/htc-10-bootlooping-t3441710
Click to expand...
Click to collapse
The only difference being that I let mine loop for a solid hour and it didn't successfully boot at all. In the past I was having issues sometimes when I restarted, but I would just create a backup and restore from it and it would work, which made me think the boot file was just either corrupt or non existent. I've never been locked out of recovery AND download mode, however.
Related
Hi,
I've attempted the JB update
http://forum.xda-developers.com/showthread.php?t=1737899..
fastboot flash boot boot.img etc.. which said all was well..
But now find that my phone will not boot up, doesn't get past the Google and unlock screen.
I've tried all combinations of volume buttons, I can get to the fasboot menu where I can choose either Recovery Mode, Power Off, Start or Restart bootloader.
None of these appear to do anything, recovery goes to the google a screen followed by an Android on it's back with an exclamation mark over it.. then goes to the Google and unlocked icon screen and stays there...
I fear my phone is bricked... Please help..
bevnet said:
Hi,
I've attempted the JB update
http://forum.xda-developers.com/showthread.php?t=1737899..
fastboot flash boot boot.img etc.. which said all was well..
But now find that my phone will not boot up, doesn't get past the Google and unlock screen.
I've tried all combinations of volume buttons, I can get to the fasboot menu where I can choose either Recovery Mode, Power Off, Start or Restart bootloader.
None of these appear to do anything, recovery goes to the google a screen followed by an Android on it's back with an exclamation mark over it.. then goes to the Google and unlocked icon screen and stays there...
I fear my phone is bricked... Please help..
Click to expand...
Click to collapse
1.) Your phone is far from bricked at all. You have access to the boot loader (i.e. the screen with the options). The recovery you're seeing is stock recovery. All you need to do is go into boot loader and fastboot flash recovername (CWM) and you will have your custom recovery back to wipe data and reinstall a rom or restore a nandroid backup
Mine is doing the same thing, weird thing is, it was working since yesterday on jellybean, it just randomly froze this morning and and now won't boot..
im currently at work so i don't have admin rights to do a fastboot flash..
any idea why it would randomly stop working when i havn't flashed anything on it besides the jb rom?
Sorted..
Thanks for the comments.. yeah i was over-reacting a bit there..
I downloaded the Galaxy Nexus Toolkit, got a stock rom form gopogle, flashed it.. back to normal, well, it will be after i restore the CWM backup i took.. phew..
Thanks again
Ian.
Still stuck
I'm also stuck in the same situation(google with the unlock screen). I fear I'm a little more stuck. I also can see the recovery/restartbootloader screen. However, everything I try still comes back to that same google screen and gets hung up. Need some help!
this has happened twice today and i think it from using volume+
Steelbully said:
I'm also stuck in the same situation(google with the unlock screen). I fear I'm a little more stuck. I also can see the recovery/restartbootloader screen. However, everything I try still comes back to that same google screen and gets hung up. Need some help!
Click to expand...
Click to collapse
Boot into recovery, wipe cache, Reboot
Hi all,
I've been running PA 4.6 (KK 4.4.4) smoothly for a few weeks now, then suddenly a few days ago it started to reboot to the OPPO logo and is now stuck in a bootloop showing only OPPO logo. Only way to stop it is to power down. Sometimes it won't even power up, then after I leave it for a few hours, it'll power up, but again OPPO logo bootloop. I'm able to boot into fastboot (that's finicky, too - it happens if I'm lucky). When I do "adb devices", nothing shows up, but when I do "fastboot devices", I can see my device.
I tried to flash a recovery through fastboot, and it says flashed successfully, but when I try to reboot, it still does the OPPO logo bootloop. Can you please help me figure this out?
At one point, while I was pressing this button and that in the middle of doing fastboot stuff, somehow it booted up to my homescreen successfully, but after like 30 seconds, it rebooted, and it's been on OPPO logo bootloop ever since. Please help.:crying:
raddatt said:
Hi all,
I've been running PA 4.6 (KK 4.4.4) smoothly for a few weeks now, then suddenly a few days ago it started to reboot to the OPPO logo and is now stuck in a bootloop showing only OPPO logo. Only way to stop it is to power down. Sometimes it won't even power up, then after I leave it for a few hours, it'll power up, but again OPPO logo bootloop. I'm able to boot into fastboot (that's finicky, too - it happens if I'm lucky). When I do "adb devices", nothing shows up, but when I do "fastboot devices", I can see my device.
I tried to flash a recovery through fastboot, and it says flashed successfully, but when I try to reboot, it still does the OPPO logo bootloop. Can you please help me figure this out?
At one point, while I was pressing this button and that in the middle of doing fastboot stuff, somehow it booted up to my homescreen successfully, but after like 30 seconds, it rebooted, and it's been on OPPO logo bootloop ever since. Please help.:crying:
Click to expand...
Click to collapse
Are you unable to boot into recovery too? Try booting into recovery and factory resetting the phone.
Thank you for replying. Yes, unable to boot into recovery I can only boot into fastboot. From there, when I do the reboot to recovery command, it says successful in cmd, but the phone goes back into the OPPO logo bootloop.
Bump.. anyone, please?
Sounds like you're gonna have to download the N1 ADB drivers and fix your phone that way. There should be a tutorial for that on XDA here somewhere
IAmOmicron said:
Sounds like you're gonna have to download the N1 ADB drivers and fix your phone that way. There should be a tutorial for that on XDA here somewhere
Click to expand...
Click to collapse
I know this is super late, but thank you for your reply. I did that and was able to flash the stock recovery via fastboot (cmd said Writing, then successful at 0.182 seconds), but when I reboot (doesn't reboot via buttons, had to do "fastboot reboot") the same problem returns - boot loop at Oppo logo. Any ideas please? Thanks again.
Hello guys,
A few months ago, I rooted my phone using kingroot. After a few weeks, i tried to install TWRP custom recover to unlock bootloader. I accidently downloaded a wrong version of it and flashed it using flashify app, after which i booted into recovery to check the new recover mode. But, something awkward happened. THE BOOT MODE DIDN'T OPEN AND THE SCREEN GOT STUCK AT "Booting into recovery". I read on the internet and realised that my device has got soft-bricked. Also, phone wasn't rebooting. So, i found a solution atleast start my phone. I took out my battery, pressed the buttons for download mode and then placed the battery back in and pressed the buttons for download mode and somewhow rebooted my phone (i read about this technique in xda forums). Now, although my phone works but i cannot access the recovery mode as it has got soft-bricked. Thus, i cannot perform a hard reset as it gets caught in that "recovery booting stuck cycle". So, can anyone tell me how to fix this? PLS QUICKLY. aLSO, i don't know much about ADB, so pls explain that too as my friend suggested me to use ADB to fix softbrick but im not sure!!
:crying:
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.
Hey guys, been a hot minute since I've been around these parts but I've got a weird one for you.
I'm stuck in a boot loop. I can get into the bootloader using pwr+vol up, but thats it. If I try to enter recovery it boot loops.
Using fastboot commands and I can get things to flash (so it says), but am still stuck in this bootloop.
Tried loading TWRP using fastboot boot twrp.img and it says it succeeded but then loops without ever getting the TWRP splash
Tried extracting the img files from the most recent OTA downloaded from google from the payload.bin and flashing those with no success.
Tried flashing the boot.img out of LineageOS and it still loops afterwards... I'll admit that this was a last ditch effort and I hope I didn't screw myself, but I figure I can just reflash if needed since I can still access fastboot.
I feel like since I can get into the bootloader that there's got to be SOMETHING I can do, but nothing seems to be working. Is this old phone truly bricked? Any ideas??
A little extra info. I was on a stock rom, it was rooted for a while and eventually after some of the ota's I lost it and didn't bother getting it back. the bootloader unlocked, though, so there's that.
ridethisbike said:
Hey guys, been a hot minute since I've been around these parts but I've got a weird one for you.
I'm stuck in a boot loop. I can get into the bootloader using pwr+vol up, but thats it. If I try to enter recovery it boot loops.
Using fastboot commands and I can get things to flash (so it says), but am still stuck in this bootloop.
Tried loading TWRP using fastboot boot twrp.img and it says it succeeded but then loops without ever getting the TWRP splash
Tried extracting the img files from the most recent OTA downloaded from google from the payload.bin and flashing those with no success.
Tried flashing the boot.img out of LineageOS and it still loops afterwards... I'll admit that this was a last ditch effort and I hope I didn't screw myself, but I figure I can just reflash if needed since I can still access fastboot.
I feel like since I can get into the bootloader that there's got to be SOMETHING I can do, but nothing seems to be working. Is this old phone truly bricked? Any ideas??
Click to expand...
Click to collapse
As a rule of thumb
-- A 'bricked phone' is usually unresponsive, won't power on, and doesn't function normally.