Database Info

[Q] Help with Phone Stuck Booting

I'm usually pretty good at following instructions but I have a problem. I am rooted with TWRP, stock kernel. I successfully applied the 4.4.1 update and used the phone for awhile no probs. Tried re-applying the 4 way reboot menu mod that I'd used successfully on 4.4.0. TWRP says flash was successful. I rebooted and am stuck at the spinning google colored circles. I cant get into recovery mode by holding the volume up/down and power buttons. The phone vibrates briefly when I hold all three but the logo keeps spinning. Pressing power button only does the same. Tried connecting to PC but mac says can't read device and to reboot it. ?help?

Update - Got her to reboot with volume down/pwer, into TWRP, and restored from backup, Back up and running...

Unusual bootloop - can't access recovery OR fastboot but loops on "optimzing apps"

Unusual bootloop - can't access recovery OR fastboot but loops on "optimzing apps"
I had my US version OpO 64GB working with CM12 for quite a while, rooted and bootloader unlocked with TWRP (possibly 2.8.6) installed, then some months ago I tried upgrading to CM12.1 through CM updater. This failed miserably - The phone started bootlooping on "Optimizing apps n of N" - as soon as it finished optimizing apps, the phone would reboot and start optimizing again. Booting to safe-mode (Power + VolUpDown) also fails in the same way (though optimizing fewer apps).
I tried rebooting to recovery mode holding Power + VolDown but it just gives a quick buzz (vibration motor) at the "1+" screen and reboots. The same thing happens when I try to boot to fastboot mode with Power + VolUp. So I'm completely stuck. All the guides show being able to boot either to fastboot or recovery (soft-brick) or else the screen being completely black/unresponsive (hard-brick). My phone is neither of these!
I got frustrated enough that I've let it sit on the shelf for the past 6 months, but now I'd like to fix this. All help appreciated.
---danq989

Did you try clearing the cache and doing a factory reset ?

SpectreFang said:
Did you try clearing the cache and doing a factory reset ?
Click to expand...
Click to collapse
That's impossible for me to do since I can't get to launcher or recovery.

No acess to recovery?? Then better take it to service center... Atleast can u boot to fastboot mode or adb accesible then use oneplus one toolkits
---------- Post added at 11:34 AM ---------- Previous post was at 11:31 AM ----------
Install oneplus tool kit, while optimising apps it gets dectected by pc, just make it reboot mode & do reset.... Dnt worry this can be fixed, if all these seems messy then take it to service center

danq989 said:
I had my US version OpO 64GB working with CM12 for quite a while, rooted and bootloader unlocked with TWRP (possibly 2.8.6) installed, then some months ago I tried upgrading to CM12.1 through CM updater. This failed miserably - The phone started bootlooping on "Optimizing apps n of N" - as soon as it finished optimizing apps, the phone would reboot and start optimizing again. Booting to safe-mode (Power + VolUpDown) also fails in the same way (though optimizing fewer apps).
I tried rebooting to recovery mode holding Power + VolDown but it just gives a quick buzz (vibration motor) at the "1+" screen and reboots. The same thing happens when I try to boot to fastboot mode with Power + VolUp. So I'm completely stuck. All the guides show being able to boot either to fastboot or recovery (soft-brick) or else the screen being completely black/unresponsive (hard-brick). My phone is neither of these!
I got frustrated enough that I've let it sit on the shelf for the past 6 months, but now I'd like to fix this. All help appreciated.
---danq989
Click to expand...
Click to collapse
while things are loading, have u tried to hold vol up + power for 10 seconds or until the screen turns off and then hold vol down + power button until the oneplus logo?

Bradl79 said:
while things are loading, have u tried to hold vol up + power for 10 seconds or until the screen turns off and then hold vol down + power button until the oneplus logo?
Click to expand...
Click to collapse
Yes, just tried it. Same thing as described in my original post. When I hold power+volup the screen goes blank. I switch to power+voldown until the 1+ logo. At that point:
1. If I continue to hold the power+voldown key through the 1+ logo, the screen goes blank briefly, the phone vibrates once and reboots. If I continue to hold the power+voldown key, the vibrate&reboot cycle continues indefinitely
2. If I let go of either the power button, the voldown button, or both at or before the 1+ logo, the phone boots normally and goes to "Android is starting... Optimizing app n of 119). When the optimization finishes, the phone instantly reboots.
It's like the phone recovery is gone or inaccessible. Could this have to do with the phone tampering setting? As I said, I had this phone rooted and bootloader unlocked, working fine with CM12 for some time before trying an in-place upgrade to 12.1. That's when things went south.
---danq989

bricked, can't get to bootloader or recovery, adb doesn't see phone either

Hello, I just unlocked bootloader, flashed custom recovery (clockwork 6.0.4.8), and gained root on my HTC One S. I then attempted to install a custom ROM, (cyanogen 12.1).
After installing and telling Clockwordmod to reboot, I believe I am in a boot loop. The white HTC screen pops up and then goes to black and stays there. When I plug my phone into my computer, I get the connection and chime, and a new device appears in Device Manager called "HTC MTP Device." When I am in fastboot mode, my phone is shown as "Android ADB Interface" in device manager, so this is different. This leads me to believe that my phone is not dead or off, it is on with a blank screen. I do not believe my computer will recognize a device that is not powered on.
I have HTC Sync Manager and I have the option for it to automatically pop up when a device is connected. It pops up, but with an error saying HTC Sync Manager could not connect to your phone.
I am able to hard-reset the phone, by holding down the Power button for several seconds. However, this just repeats the process (White HTC logo screen, then black screen). I am not able to enter bootloader or recovery by holding down Volume and Power. I have tried Volume Up + Power, Volume Down + Power, and Volume Up + Volume Down + Power.
Also adb no longer recognizes my device, so I can not interact with the phone that way either.
Currently, my only idea is to allow my phone to die so I can try booting it into recovery from power off. But if there are any other ideas that would be great.
Right before I rebooted, after installing the ROMs, I got a message saying something like "Root possibly lost, do you want to fix root." I said yes, could this be part of the issue?
I am on Windows 10.

t1j said:
Hello, I just unlocked bootloader, flashed custom recovery (clockwork 6.0.4.8), and gained root on my HTC One S. I then attempted to install a custom ROM, (cyanogen 12.1).
After installing and telling Clockwordmod to reboot, I believe I am in a boot loop. The white HTC screen pops up and then goes to black and stays there. When I plug my phone into my computer, I get the connection and chime, and a new device appears in Device Manager called "HTC MTP Device." When I am in fastboot mode, my phone is shown as "Android ADB Interface" in device manager, so this is different. This leads me to believe that my phone is not dead or off, it is on with a blank screen. I do not believe my computer will recognize a device that is not powered on.
I have HTC Sync Manager and I have the option for it to automatically pop up when a device is connected. It pops up, but with an error saying HTC Sync Manager could not connect to your phone.
I am able to hard-reset the phone, by holding down the Power button for several seconds. However, this just repeats the process (White HTC logo screen, then black screen). I am not able to enter bootloader or recovery by holding down Volume and Power. I have tried Volume Up + Power, Volume Down + Power, and Volume Up + Volume Down + Power.
Also adb no longer recognizes my device, so I can not interact with the phone that way either.
Currently, my only idea is to allow my phone to die so I can try booting it into recovery from power off. But if there are any other ideas that would be great.
Right before I rebooted, after installing the ROMs, I got a message saying something like "Root possibly lost, do you want to fix root." I said yes, could this be part of the issue?
I am on Windows 10.
Click to expand...
Click to collapse
Just in case anyone stumbles on this. You can boot into the bootloader by Holding down the Power Button for several seconds, the soft buttons will blink, indicated ensuing reboot, when they stop blinking, hold Volume Down until you get to the bootloader menu. The phone does not need to be powered off for this. From there, adb/fastboot will recognize your phone, and you can factory reset if needed.
However, I figured out my problem. On older HTC models, including the HTC One S, you have to manually flash the boot.img file that is included in the zip for your ROM.
But now I've made it to the cyanogenmod boot screen and am stuck there. sigh. i've been at this literally all day.

In the end, I just flash a different rom, specially Candy5 as found here: http://forum.xda-developers.com/htc-one-s/development/rom-t2964931 and it worked.
It's possible I accidentally flashed a rom that was incompatible with my device, not sure.
EDIT: I also switched from CWM to TWRP. Not sure if that helped.

t1j said:
Just in case anyone stumbles on this. You can boot into the bootloader by Holding down the Power Button for several seconds, the soft buttons will blink, indicated ensuing reboot, when they stop blinking, hold Volume Down until you get to the bootloader menu. The phone does not need to be powered off for this. From there, adb/fastboot will recognize your phone, and you can factory reset if needed.
However, I figured out my problem. On older HTC models, including the HTC One S, you have to manually flash the boot.img file that is included in the zip for your ROM.
But now I've made it to the cyanogenmod boot screen and am stuck there. sigh. i've been at this literally all day.
Click to expand...
Click to collapse
I have broken volume down button, what can i do? face the same problem
What does it mean by manually flash boot.img? After flashing a custom rom, do not reboot first but flash the boot.img via twrp which can be found in zip for the rom?

Stuck in boot animation. Can't get into recovery or fastboot.

I recently updated Magisk from 16.0 to 17.1. The installer asked to reboot after finishing up. After rebooting, however, the phone gets stuck on boot animation. I've tried to let it run all night and I've tried charging/discharging a few times. The bootloader is still unlocked (the opened lock icon shows up under the Google logo on boot). I can't get into recovery/fastboot mode: Holding power+volume down turns on the phone but gives a black screen with backlight on. My computers also don't recognize the phone. I haven't found any similar issues here while searching so I am at a loss on how to fix it.
Possibly related: Charging the phone has been weird for a few months: the charging LED indicator only turns on when the phone screen was on. It seemed to charge slower compared to previously and the OS doesn't recognize that the phone is charging.

With the phone off, hold the volume down button and connect the phone to your computer. This may force the phone into fastboot mode.

Thanks for the advice! Although that didn't immediately work (it still booted to a black screen w/ backlight on), I tried one or two more times to boot holding down volume down + power with the phone unplugged. I got lucky somehow and it finally booted to Fastboot. From there, still neither my MacBook nor my Windows computer recognized my phone (nothing in device manager). I booted to TWRP, and saw that Magisk had .zip's of previous versions stored in /sdcard/MagiskManager. I flashed the last working version, 16.0, wiped Cache and Dalvik, rebooted and finally got through boot animation.
Time to backup!

Help! Stuck on TWRP loading. I can't even turn off the phome!

So I have Galaxy S7 (Flat). It had installed TWRP with Magisk on stock Android. I decided to install LineageOS (https://forum.xda-developers.com/t/rom-q-s-lineageos-with-microg-for-samsung-s7-flat-edge.3921094/) (clean install using TWRP) and it installed successfully, everything was fine, I've turned my phone off and on few times and system was booting without any problems.
But then I decided to boot into TWRP (using key combination) to install magisk and... it's stuck on loading screen forever.
I can't even turn it off ! And my phone is getting hotter and hotter. Please help !
I can't turn it off, because simply holding power button doesn't do anything.
I can restart it by holding power + volume down ,but it just opens TWRP again.
I've read I could boot into Maintenance Boot Mode ,but it requires to turn off a phone, which I'm unable to do.
Only thing I am able to do is to boot into Download Mode, but it doesn't change anything (still cant turn off phone in this mode)
Should I try to disassembly the phone and take out the battery manually? I don't really see any other option.
Did I bricked my phone ?
@edit
I have backup of stock system made by TWRP, but it doesn't change anything as I cant use TWRP.
I didn't install LineageOS custom recovery.

Ok, so I left phone overnight to deplete the battery. And it didn't work ! I thought that battery is dead and phone is off, but the moment I've plugged the power cord it automatically turned on into TWRP screen, like a zombie !
However I've solved the problem. As I was able to get phone into Download Mode (by holding power+volume down+home) I used Odin. I've installed newest Odin on PC, Samsung USB drivers and flashed the newest TWRP tar. Although it was scary, I was almost sure I've bricked my phone. Adb/fastboot were not detecting the phone.
And after re-flashing TWRP everything works fine. Also LineageOS booted like a charm, it stay intact.
So, it seems that installing LineageOS somehow corrupted my TWRP, despite that I un-ticked the option to install LineageRecovery ,so technically it shouldn't mess with it at all.
Anyway, problem solved.