I've looked online, especially on here, for solutions to my problem but they all seem to assume that I can access fastboot. Here is my specific problem:
I was using my phone and suddenly the screen went black. It rebooted once into the OS but immediately restarted and has been stuck in bootloop for 4.5hrs thus far. I have tried to wipe cache, enter fastboot, power down the phone but nothing worked and it kept looping. Even when I powered off. It's like the power button signal is malfunctioning because it doesn't always reboot at the same exact point in the boot cycle.
My phone is stock, no custom anything, and is encrypted. My only thought right now is to let the battery drain fully and try to boot again after that. I have not tried to enter fastboot while connected to a PC, but I have tried to do it just on the phone.
I have not been home yet so I do not have access to a PC I can actually do things with at the moment. Any help is much appreciated. Thanks!
EDIT: I am home now. Going on 6hrs of looping and nothing has changed.
EDIT 2: The battery was drained. It starts to charge but instantly tries to enter the boot loop again so the battery never gets enough charge to do anything; thus, I can do nothing to save the phone, I don't think.
If its some malfunction with power button, try to abuse the button gently. I used to do that with my Nexus 5 when its power button gets stuck inside causing bootloops.
nirmalkurienmathews said:
If its some malfunction with power button, try to abuse the button gently. I used to do that with my Nexus 5 when its power button gets stuck inside causing bootloops.
Click to expand...
Click to collapse
The button itself is fine, it works as it should and is not pressed down; however, there might be some sort of internal problem causing the phone to think that it's being pressed.
Related
Dont know if any one is facing the same problem.
Installed Lollipop in my S4 over the air, 2 weeks ago.
A week back, my phone entered into BootLoop mode. Phone gets re-started. I can see Samsung logo and it gets restarted again. I tried removing the battery and kept it back. Started working fine then.
Since today after noon, my S4 is in complete boot loop. Tried removing the battery and kept it back. Yet it is in bootloop.
Unable to enter into Developer options also. Please help
I hit the Power Button against a Flat Surface. It Vibrates and shows the Samsung Logo. But then it turns off.
Is the battery empty maybe?
My guess is that your power button is faulty. Either try to wiggle it lose or replace it. It's really cheap
If it reboots in download mode and/or your recovery then it's your power button.
Lennyz1988 said:
My guess is that your power button is faulty. Either try to wiggle it lose or replace it. It's really cheap
If it reboots in download mode and/or your recovery then it's your power button.
Click to expand...
Click to collapse
I tried it again with wiggling and hitting it a little bit.
it turns on automatically and then it turns off after some second again
My S4 started acting weird a couple days ago. It would occasionally self-reboot when I woke the phone by the home button or the power button. During those self-reboots, the AT&T logo seemed to stay longer (probably a couple minutes) than a normal reboot but everything was fine afterwards (could still use the phone for hours without triggering another self-reboot).
The situation went downhill quickly today and now it always gets stuck at the AT&T logo. Press and hold the power button will reboot the phone until the AT&T screen and the only way to turn it off is removing the battery. I can still charge the phone but sometimes instead of showing a charging battery icon, the phone will power on when I press the power button.
I've tried a few tricks (remove SIM and microSD card, pull battery, boot into recovery and wipe cache partition) but none worked. In the beginning, I did manage to boot past the AT&T logo a few times (self-reboot with home/power button still persisted) but no luck since this afternoon.
Since I haven't made any changes to the phone in the 2-3 weeks before the above problem occurred, can this be hardware-related (like a bad battery)?
And at this point, is it still possible to unbrick the phone without wiping the data?
Thanks for helping!
steppenwolf1014 said:
My S4 started acting weird a couple days ago. It would occasionally self-reboot when I woke the phone by the home button or the power button. During those self-reboots, the AT&T logo seemed to stay longer (probably a couple minutes) than a normal reboot but everything was fine afterwards (could still use the phone for hours without triggering another self-reboot).
The situation went downhill quickly today and now it always gets stuck at the AT&T logo. Press and hold the power button will reboot the phone until the AT&T screen and the only way to turn it off is removing the battery. I can still charge the phone but sometimes instead of showing a charging battery icon, the phone will power on when I press the power button.
I've tried a few tricks (remove SIM and microSD card, pull battery, boot into recovery and wipe cache partition) but none worked. In the beginning, I did manage to boot past the AT&T logo a few times (self-reboot with home/power button still persisted) but no luck since this afternoon.
Since I haven't made any changes to the phone in the 2-3 weeks before the above problem occurred, can this be hardware-related (like a bad battery)?
And at this point, is it still possible to unbrick the phone without wiping the data?
Thanks for helping!
Click to expand...
Click to collapse
It could be battery. However, most reboot caused by bad battery occurs when you run the apps not in the idle condition.
It could also be conflict in the rom (OS).
I do not think there a way to unbrick the phone without wiping the data (factory reset) unless the unbrick was caused by the battery failure.
sway8966 said:
It could be battery. However, most reboot caused by bad battery occurs when you run the apps not in the idle condition.
It could also be conflict in the rom (OS).
I do not think there a way to unbrick the phone without wiping the data (factory reset) unless the unbrick was caused by the battery failure.
Click to expand...
Click to collapse
Thanks! I'll get a new battery and see if it can work miracles.
I just encountered a very strange and worrisome issue today. I successfully rooted my OnePlus 6T and installed Magisk with TWRP following these instructions.
After reinstalling my apps, installing the AdAway apk, and rebooting (using the system dialog) after I was prompted to, my phone refuses to start.
The screen is all black with no signs of any activity. I tried holding the power button for 10+ seconds in various combinations with the volume buttons. None of them worked. The phone is definitely not battery dead because I clearly remember the phone was plugged into my computer and at 83% at the time it shut off. I hardly believe I bricked my phone because the rooting process was 100% successful.
Any help would be greatly appreciated.
Plugging in your phone have any signs of activity? Might be in qcom mode. Worked for me to hold power and volume Up for like 30 seconds.
I've had this issue a few times, I was always able to get it to turn on by holding vol up + power for an extended period of time.
mang0 said:
Plugging in your phone have any signs of activity? Might be in qcom mode. Worked for me to hold power and volume Up for like 30 seconds.
Click to expand...
Click to collapse
my op6 got bricked.....and when using MSM tool it shows ....."downloading op2.img failed" after an error "SHA256 not matching /or something like that" ! anyone help please !
I have a similar problem. I tried to convert my op6t to a an international phone. I held the volume up and down buttons, then plug it in to the computer. Nothing happened so I figured I would redo it. I tried to turn it on but nothing happens
I am sorry if this is a dumb thread I am just worried. I was watching my Poco M3 update up to 60%(my battery was on 68% before starting the update) then I started to watch TV and didn't pay much attention to the phone. When I looked at it it was off and i thought that maybe it is just in the process of rebooting or its already on the lock screen .Because I thought it may still be rebooting I just placed my finger on the fingerprint reader because I didn't want to risk turning it of by pressing the power button. My phone didn't respond at all. I haven't tried to hold the power button because I'm worried that its still in the process of updating. What should I do ?
Never mind. I had to hold the power button for 10 seconds and it turned on. I am sorry for wasting your time. I was so worried since it was a new phone and I couldn't afford a new one. I am sorry again.
This post was usefull, it happened to me too. The phone wouldn't even show an image when connected to a charger. I waited for a while, entered Fastboot succesfully and then, after the second (on the first one remained stuck on the MIUI screen) 10s power button push, it succesfully booted
It happened also to me during update to 12.0.8.0, but I used Power and Vol+ and then Reboot to System.
It was a moment of anxiety.
It happened to me to. It is a branch new phone and I got so worried that I might just have bricked it. Fk Xaomi.
just happended with me right its on MIUI Screen hope its get on
Update: Just Booted In Fastboot Its on Screen now
Same thing just happened to me too. My phone is not turning on at all. I tried holding the power button for 10 seconds as discussed here, tried fast booting, tried connecting charger and starting. Nothing is working. Going into panic mode.
**UPDATE***
After leaving the phone alone for 24 hours in which time it was completely unresponsive to anything I tried, I connected the charger and just pressed power button and it decided to just start normally. POCO needs to address this situation.
**UPDATE***
Phone is not responding again after restrating. I give up on this phone.
I discontinued using my X Compact in mid-2020 when I got a new Pixel 4a. It's been sitting in a drawer since. It was rooted but working fine.
Recently I pulled it out to try charging it up to use as a spare. What I found was, upon plugging it in to charge, I'd get the "Your devices has been unlocked and can't be trusted" splash screen, then after the 5 seconds it would vibrate and bootloop back into the same screen, etc. I tried booting into recovery with power button / volume down and got only a blank screen. I booted it into fastboot with power button / volume up and left it to charge in that state.
Today I got all the drivers set up on my laptop and was able to access fastboot. I tried installing two different versions of TWRP for kugo (twrp-3.3.1-0-kugo and twrp-3.6.2_9-0-kugo). In both cases, subsequently attempting to boot into recovery, I got the SONY screen followed by the TWRP splash screen and then... hang.
Certainly seems like something got corrupted in there. Should I just call it a brick and leave it alone, or are there any further bright ideas on what to try?
Is the battery good? It may not be able to sink enough current otherwise.
blackhawk said:
Is the battery good? It may not be able to sink enough current otherwise.
Click to expand...
Click to collapse
Hard to judge in this state, but if I immediately plug it into charge after launching recovery mode, it still hangs.