I completely drained a OnePlus 6 (6 gb) running Lineage OS 18.1 with Magisk root. When I plugged it into the OnePlus charger that came in the box, it started to boot loop, showing the 1+ logo, the unlocked bootloader warning, then "Battery is too low" warning (red text, different languages), then shutting off to repeat that. Sometimes it would not do the "Battery is too low" warning.
I've left it to charge for 2 hours now with no luck. After a while it stops boot looping then just stays black. When I click the power button once it shows a charging screen, a circle with a lightning symbol and shows a charge going into the circle.
It does not boot when not plugged in.
When I try to boot it and it goes onto the 1+ logo screen or any screen, then I unplug it, the screen will completely turn off.
I've tried to access fastboot mode and change chargers but both don't work. Holding the volume button and power button just starts the boot loop from a black screen.
Is there anything I can do to fix this problem? Or another forum that might have a solution? Thank you.
Edit:
I am able to get it into fastboot mode, but I cannot boot into twrp through "fastboot boot" or from the recovery mode option.
When I use "fastboot getvar battery-voltage" I get either 4329 or 1802.
Related
what am I supposed to do in this instance?
matt2k12 said:
what am I supposed to do in this instance?
Click to expand...
Click to collapse
Ok when I leave it there to charge after about 5 minutes it tries to boot up again on its own... its like a boot loop but it stays turned off for about 5 mins in between.
Now I believe its officially stuck at the CM logo screen after the data only back up and restore. It stopped turning off which I think was due to battery and when I plugged it into the PC it turned on and has been at the CM logo screen for about an hour now.
It also refuses to boot into recovery now. Stock or Open Recovery. It only shows the green charging LED and when I do a force shut down it blinks on and back on in about 1 second. I have no clue what the deal is. I'm going to try and flash a stock image with RSD Lite and try it all again.
Click to expand...
Click to collapse
Your battery is empty. You can't flash anything via fastboot in such state.
When the battery is empty while starting the phone, the bootloader charges it a bit first (that green LED). Only when the battery is charged a little, it switches to boot.
What you want to do is to catch the moment when it starts to boot and hold the volume-up to get to OpenRecovery. OR supports charging so you can let the battery charge more there.
kabaldan said:
Your battery is empty. You can't flash anything via fastboot in such state.
When the battery is empty while starting the phone, the bootloader charges it a bit first (that green LED). Only when the battery is charged a little, it switches to boot.
What you want to do is to catch the moment when it starts to boot and hold the volume-up to get to OpenRecovery. OR supports charging so you can let the battery charge more there.
Click to expand...
Click to collapse
Thank you again for your responses.
I was thinking along those lines... But it seems like as soon as it gets a charge that it goes right into the boot logo. There doesn't seem to be any middle ground to go to any recovery mode. I was stuck in a similar situation before but it wasn't constantly trying to boot.
Here is what happened:
When I flashed data only, I selected "reboot after" option so it is constantly trying to do that re-boot but since it cant boot it stays at the CM logo I guess until the phone dies. Then it charges for a while with the green LED and then it tries to boot again. I have tried to access all kinds of recovery and fastboot and everything at the usual intervals and I cant get it to start any recovery mode because it is still following the re-boot command from Open Recovery.
I will keep trying but this time seems different than when I had low battery/no recovery in the past instances. Something is overriding my recovery and I think it has to do with the Open Recovery reboot after flashing command.... I even opened up the back of the phone and disconnected the battery and its still not working.
kabaldan said:
Your battery is empty. You can't flash anything via fastboot in such state.
When the battery is empty while starting the phone, the bootloader charges it a bit first (that green LED). Only when the battery is charged a little, it switches to boot.
What you want to do is to catch the moment when it starts to boot and hold the volume-up to get to OpenRecovery. OR supports charging so you can let the battery charge more there.
Click to expand...
Click to collapse
matt2k12 said:
Thank you again for your responses.
I was thinking along those lines... But it seems like as soon as it gets a charge that it goes right into the boot logo. There doesn't seem to be any middle ground to go to any recovery mode. I was stuck in a similar situation before but it wasn't constantly trying to boot.
Here is what happened:
When I flashed data only, I selected "reboot after" option so it is constantly trying to do that re-boot but since it cant boot it stays at the CM logo I guess until the phone dies. Then it charges for a while with the green LED and then it tries to boot again. I have tried to access all kinds of recovery and fastboot and everything at the usual intervals and I cant get it to start any recovery mode because it is still following the re-boot command from Open Recovery.
I will keep trying but this time seems different than when I had low battery/no recovery in the past instances. Something is overriding my recovery and I think it has to do with the Open Recovery reboot after flashing command.... I even opened up the back of the phone and disconnected the battery and its still not working.
Click to expand...
Click to collapse
I got fastboot working by plugging the phone into a dedicated AC power charger, not one with a USB adapter. Then I let it sit on the boot screen for a couple hours. This way it fully charged the battery and I could bring up fastboot.
What was happening with the USB adapter was that it would try to boot, die, and refuse to go to fastboot, over and over again. I would not have got it working without a dedicated AC power charger.
That literally happened to me a few days ago. Fastboot will say a warning on the screen, somewhere around the middle, "Battery Low" or something along those lines, I paid it no attention, as I knew it was plugged in and should've been charging through my processes. Well, the battery has to be at least 50%+ charged before fastboot will allow any connectivity or communication with ADB or Fastboot on pc. Facepalm.
Always double check battery charge at least 60% or more to be in the safe side, or you risk to soft-brick to even hard-brick your phone.
So last night I had booted into fastboot mode and was going to boot into recovery (TWRP) and I fell asleep while I was on the fastboot menu. The battery was already pretty low so I assume it just died from there. I put it on the charger today and it's blinking the charging batter logo on and off. It won't charge. I am still able to (while on the charger) boot it into fastboot mode so I flashed factory images, but that hasn't done anything different. So it's just sitting here on the charger flashing the battery with the lightning bolt. I've tried all combinations of holding the power button down but it will vibrate, show "Google" on screen for a second, then go back to the battery logo. I've tried powering down from fastboot, but it does the same thing. It won't boot into recovery either. Suggestions?
Hello guys, hope someone could help me.
I have a Moto G that has a bootloop, I cannot get into bootloader menu either. I've tried combinations that worked for me previously (Power + Vol Down, Power + Vol Up + Vol Down) in different time intervals (Up to 2 minutes) and when I release the buttons the screen blinks and it starts again with the looping, like it tries to enter and fails. When I plug the charger it shows the battery logo and 0% and it loops in that screen too, it just won't charge. I was able to charge the battery externally and it's still bootlooping and no bootloader menu. What could have happened? I didn't install anything new, the last thing I did was plugged it with a car charger it was like 20% and it restarted and started looping. I've tried everything I could find on the Internet but I couldn't find someone with my same problem. Please help.
unable to power off phone (down vol+power), stuck at logo "Fastboot Mode" screen
Unable to power off phone (down vol+power), stuck at logo "Fastboot Mode" screen, tried installing Android 10, stuck in a boot loop to fastboot, went to fastboot twrp 3.3.1-70 and now hung completely. Any suggestions my fingers are getting marked from holding buttons with no results. Luckily the phone is at 99% battery right now (I did not mean that as draining battery could take days not good for teh screen either), I hate not having a battery to pull to fix these issues, not getting worried right now.
ERIC
Apparently vol+ + power does work took maybe 40 seconds, not sure why searching returned vol-
ERIC
Hello, I flashed this phone from CN to WW using the `flashall_AFT.cmd` script. It worked fine except the battery indicator at the top would stay pinned at 100%. I ignored this and eventually let the phone die the next day while playing games on it. After that, the phone has been semi-bricked.
The phone does not turn on at all unless it is plugged into the charger.
If I plug the charger into the bottom port on the phone:
1. Android logo flashes for .2 seconds
2. Phone shuts off for 5 seconds
3. Steps 1-2 repeat until I unplug it again
If I plugin the charger to the side port on the phone:
1 The green charging circle with the lighting bolt shows up for a few seconds
2. It changes to the main boot screen
3. Phone shuts off for 5 seconds
5. Steps 1-3 will repeat until I unplug it again
I can still boot the phone into fastboot mode when it is charging from the side port. I used this to re-flash the phone using the `flashall_AFT.cmd` script again, but that did not solve the boot loop problem. What else can I try now to get the phone working again?
Update: I tried to flash it one more time using `flashall_AFT.cmd` with the 1.1.92 WW raw image. It completely froze while on `Sending sparse 'super' 6/14`. The phone no longer boots at all and does not connect to my computer. I just see a solid red light at the top of the screen when it is plugged in. If I hold both volume buttons and the power button all at the same time for about 10 seconds, the red light will briefly turn off, but that is all I can make the phone do at this point.
you'll probably need to use a 9008 rescue tool to have any chance at saving it at this point.... I'd say just sent it back to ASUS for a RMA to see if they'll do it for you