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.
Related
So today for the first time tried to mess around with my phone, but i failed miserably. I rooted my phone with Kingo ROOT, and then followed the instructions on the wiki page, but at step 4 things got messed up, my phone got stuck at the SONY logo with the blue light turned on and it wouldnt do anything, so i removed the battery, now it boots up at the cyanogen recovery but i cant do anything from there , everytime i close the device when i boot it , it boots to this menu. I have tried everything to get it back to normal but nothing seems to work. I will tell exactly what i did in order to reach in this state. I downloade the nicki nightly cm, and moved the boot.img to my platform-tools folder in which i run on command prompt the following commands :
fastboot flash boot boot.img
fastboot reboot
After that my phone gets stuck and i can only access Cyanogen Recovery, does anyone have any idea what to do?? :crying: :crying:
Have you tried flashing the rom using cyanogen recovery?
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.
I just upgraded my rooted and bootloader unlocked Robin to Nougat last night by installing the official upgrade files from the Razer Community forum. I've tried installing TWRP several times through fastboot, and each time I can get the phone into recovery, but the phone will never boot into the system. It hangs on the black "Nextbit by Robin" screen, and never goes past it. If I turn off the phone by holding down the power and volume down buttons, and then turn it back on, it still won't get past that screen. I can always get into TWRP, though, but no matter what I do, the phone won't boot. I've been using TWRP 3.1.0. Is there a different version that's required for Nougat?
Saaber said:
I just upgraded my rooted and bootloader unlocked Robin to Nougat last night by installing the official upgrade files from the Razer Community forum. I've tried installing TWRP several times through fastboot, and each time I can get the phone into recovery, but the phone will never boot into the system. It hangs on the black "Nextbit by Robin" screen, and never goes past it. If I turn off the phone by holding down the power and volume down buttons, and then turn it back on, it still won't get past that screen. I can always get into TWRP, though, but no matter what I do, the phone won't boot. I've been using TWRP 3.1.0. Is there a different version that's required for Nougat?
Click to expand...
Click to collapse
My guess is you messed up the boot.img, or worse you corrupted some partition. If it's the boot.img, go get the latest factory image, unzip it, and move the file 'boot.Img' onto where your adb and fastboot files are located. Then go into fastboot on your Robin, and run this command on your PC:
Fastboot flash boot boot.img
If you corrupted something, you basically need to go into fastboot and use the flash-all.bat in the already unzipped Robin_nougat_88 folder to bring your phone back bone stock.
Hope that helped
Had this issue with my phone at first, but eventually just fixed it anyway by flashing the decrypted boot.img.
I ended up fixing it the same way you did. No matter how many times I took it back to stock by flashing the files in the Robin_nougat_88 folder and then flashing TWRP, no matter which version of TWRP I used, it would never boot. I finally flashed TWRP, then booted back into recovery, wiped the phone, loaded and flashed the decrypted boot image and SuperSU, and then the phone booted fine. I should have just done that in the first place since it was always my intention to unencrpyt it and rooted it again, anyway.
I just noticed after doing a clean install of the C3 factory image using -w that I am unable to boot to the stock recovery. It seems to be missing from my installation. Any ideas why I may be unable to boot to recovery? All I get is a dead Android logo with "No command" or it boots up my system after restarting. I've tried booting from the bootloader numerous times and never seems to work. Is it possible that the stock recovery was never installed? I did no perform a --slot all when installing Android 10 so maybe that's the issue? Any suggestions would be great as I can't seem to find a solution to this in the forums or Google searching. Thanks.
You have to go one step beyond the no recovery screen to see the recovery commands. If presented with an image of a broken Android with “No Command” printed on the screen, press and hold the Power button. Press the Volume Up button once. Then release the Power button.
Seems I can't even get to the broken Android screen now. In the bootloader if I select boot recovery it just boots my system and never shows the broken Android anymore. Very odd. I'm stumped.
rspkt said:
Seems I can't even get to the broken Android screen now. In the bootloader if I select boot recovery it just boots my system and never shows the broken Android anymore. Very odd. I'm stumped.
Click to expand...
Click to collapse
I am not sure what you are referring to "boot recovery." Are you entering the bootloader in some way other than volume down +power? The option when using the up/down in bootloader is Recovery mode. That will get you to the broken android and no command. At worst though, you can flash boot.img and get your stock recovery/kernel back/unroot.
sliding_billy said:
I am not sure what you are referring to "boot recovery." Are you entering the bootloader in some way other than volume down +power? The option when using the up/down in bootloader is Recovery mode. That will get you to the broken android and no command. At worst though, you can flash boot.img and get your stock recovery/kernel back/unroot.
Click to expand...
Click to collapse
I can enter the bootloader via adb or with the power + volume down no problem. When I select recovery from the bootloader it boots to the Google logo then blank screen and seems to reboot again straight to my system. I may have to try to revert to the stock boot.img like you suggested and see if that solves the issue.
rspkt said:
I can enter the bootloader via adb or with the power + volume down no problem. When I select recovery from the bootloader it boots to the Google logo then blank screen and seems to reboot again straight to my system. I may have to try to revert to the stock boot.img like you suggested and see if that solves the issue.
Click to expand...
Click to collapse
I get the same thing where it won't boot to recovery from the bootloader, but goes back to booting to system. It's because I'm rooted. Flash the stock boot image and you'll be fine.
rspkt said:
I can enter the bootloader via adb or with the power + volume down no problem. When I select recovery from the bootloader it boots to the Google logo then blank screen and seems to reboot again straight to my system. I may have to try to revert to the stock boot.img like you suggested and see if that solves the issue.
Click to expand...
Click to collapse
OK, that makes better sense. You are pretty clearly in a bootloop. Just confirming the terminology. Flashing stock boot might get you out of the loop, but after rereading your initial message it sounds as if some info is missing. After the flash-all, did it ever get to the setup screen where you enter your gmail account name, etc. Did it get through that to the actual OS, and if so what else did you do that got you into the bootloop? Root attempt?
sliding_billy said:
OK, that makes better sense. You are pretty clearly in a bootloop. Just confirming the terminology. Flashing stock boot might get you out of the loop, but after rereading your initial message it sounds as if some info is missing. After the flash-all, did it ever get to the setup screen where you enter your gmail account name, etc. Did it get through that to the actual OS, and if so what else did you do that got you into the bootloop? Root attempt?
Click to expand...
Click to collapse
Ya my phone setup fine through all the initial setup steps as if it was a new device and the system works perfectly. I did root and install Kirisakura kernel but only after few days of using stock. Just noticed after setting everything up the recovery seems to be missing when I tried to boot into it. I may try and start from scratch again cuz obviously something got broken during the factory image installation using -w.
rspkt said:
Ya my phone setup fine through all the initial setup steps as if it was a new device and the system works perfectly. I did root and install Kirisakura kernel but only after few days of using stock. Just noticed after setting everything up the recovery seems to be missing when I tried to boot into it. I may try and start from scratch again cuz obviously something got broken during the factory image installation using -w.
Click to expand...
Click to collapse
I missed the post by @jd1639 while I was replying. It doesn't sound like anything got messed up as a result of the -w. Because stock recovery is part of boot now, you just need to stay out of there unless you flash boot.img first. Not doing the --slot all wouldn't have any impact unless you install a custom ROM, an OTA or do a manual slot change. Since it was the first time I had done a completely clean wipe in a while when I flashed 10 (after custom ROMs, OTAs, etc), I actually did flash-all (with -w) to both slots. I did a flash-all on B and finished setup, and then booted back to BL, changed slots manually to A and did a second flash-all. Only after that did I start gettin gthe phone ready for daily function. Not sure it helped anything but my OCD, but it was fun to watch the fastbootd thing run a few times. :silly:
jd1639 said:
I get the same thing where it won't boot to recovery from the bootloader, but goes back to booting to system. It's because I'm rooted. Flash the stock boot image and you'll be fine.
Click to expand...
Click to collapse
I never would have assumed having root could cause this issue.
So I loaded Lineage OS 19.1 just fine, but it caused a few issues so I decided I'd flash it back to a global stock ROM.
My first step after factory resetting the phone was going into the bootloader and wiping user data. Now I just get the boot screen and restarts when it usually would go past it.
The phone is not responding to any button press combinations as well as not loading into the bootloader when a usb is inserted while the volume down button is being help in the brief off time between restarts.
Am I stuck, do I just need to put a new motherboard in the phone? Should I not have wiped user data from the bootloader, and instead used the recovery to do so?
I do have another motherboard from a working parts phone except its Google locked, but I've heard and seen that there are ways around that.
do you have boot.img flashed without errors? on some devices, you need to add fastboot flash:raw boot_a boot.img
SurvivalHorror said:
do you have boot.img flashed without errors? on some devices, you need to add fastboot flash:raw boot_a boot.img
Click to expand...
Click to collapse
Well I did. But now it won't accept inputs. I've already swapped the motherboard. It works, but I decided to go back to Lineage AGAIN, as the stock ROM is has WAY too many issues, and now it has a similar issue after sideloading the zip from lineage. Although the recovery partition booted just fine after I flashed it with the lineage recovery img.