Hi,
Today my phone just rebooted (and failed to boot) when I was browsing. Then I manually rebooted and it succeeded.
Then after 5 minutes of more browsing, it rebooted again, and kept looping the boot up screen. I had to remove and replace the battery to get it to boot again.
Now, I'm afraid to use it much. Is this a bootloop? Do I have any recourse? (this happened around 40% battery)
__________
I'm on unrooted stock 8.0. H990ds, 2years old
are you using the oem battery?
ive realized (and lg did say this) that only oem batteries will give consistent results.
Related
My phone has been operating perfectly fine up until a video meeting I had today, where the phone went from 100% to 0% by the end. This Axon 7 has had a lot of wear and tear on the battery so that is normal. Today the phone was very very hot during shutdown.
Upon trying to reboot, I am stuck in a bootloop. I have Lineage installed, and tried Stock but that wouldnt even get to the booting animation. I uninstalled Magisk before these tests. Now I am back on Magisk, in LineageOS (latest build) and managed to get back to the booting animation.
Does anyone know any kind of damage that could occur with a hot phone during normal operation (not boot or shutdown) shutting down? A bootloop seems like a strange result.
If you can still boot to twrp, just stay there and let it charge a bit, maybe 20% + battery level. I experienced this situation twice already.
The first one I experienced this, it won't even boot or even charge while it's off. I even opened up the phone to reconnect the battery. The second time, I was able to boot to twrp. So I let it charge while in twrp. HTH
otaconremo said:
If you can still boot to twrp, just stay there and let it charge a bit, maybe 20% + battery level. I experienced this situation twice already.
The first one I experienced this, it won't even boot or even charge while it's off. I even opened up the phone to reconnect the battery. The second time, I was able to boot to twrp. So I let it charge while in twrp. HTH
Click to expand...
Click to collapse
This was the solution, however, along with something else.
The phone only charged correctly in TWRP, so I advise that. Definitely uninstall magisk so it doesnt patch other installs (I've noticed its installer gets called every time I flash a rom). I still had bootloop so I assume all my hard-resetting didnt help. I got it to fully boot on Bliss, but since I kinda miss Lineage I may return to it later today. (I love my "0% brightness" and blue light filter among other lineage features).
Hello,
My stock Verizon S7 Edge has been stuck in boot loop and won't load all the way to the OS. I even flashed it via Odin and it is still looping. What do you think is wrong with it? Thanks for your help.
Condition of the phone is great except one day it was in a bag in direct sun and got very hot. 2 days later I started having problems. Always had stock ROM.
More detailed version of events:
June: in hot weather, the phone would randomly turn off and show 0% battery. This happened just a handful of times then it was OK.
August: 2 days after getting quite hot in my bag that I left in the sun, it randomly rebooted and got in a boot loop. I tried troubleshooting guides and eventually had to do a factory reset. This fixed the problem for 5 days, but then it started boot looping and wouldn't load to the OS. Factory reset didn't work.
Today: finally got around to installing stock Verizon Oreo ROM via Odin. Started setting up the phone but now it is boot looping again.
I did a relatively normal flash of both TWRP and root with Magisk, no issues booting. However this message came and after 5 minutes didn't go away so I fiddled around and tried to turn it off (couldn't). The phone takes no input and nothing I do allows it to enter fastboot or recovery. ADB and Fastboot do not recognize it since it's basically in a pre-boot state. I waited 20 hours for the battery to finally drain just to get this message right after I got it charged enough to boot again.
Any help? I just got this phone yesterday hahahha.
chikabrika said:
I did a relatively normal flash of both TWRP and root with Magisk, no issues booting. However this message came and after 5 minutes didn't go away so I fiddled around and tried to turn it off (couldn't). The phone takes no input and nothing I do allows it to enter fastboot or recovery. ADB and Fastboot do not recognize it since it's basically in a pre-boot state. I waited 20 hours for the battery to finally drain just to get this message right after I got it charged enough to boot again.
Any help? I just got this phone yesterday hahahha.
Click to expand...
Click to collapse
Hold down the power and volume up buttons.
This is a known issue when running Magisk, etc. The phone is not bricked.
Do not attempt to charge with the phone off.
my p10 plus got got bricked and it is always going to eRecovery without going to home screen after update. my phone is BOOTLOADER LOCK, NOT ROOTED THOUGH. and i want to fix this . i need help . ps : i hope theres a method that could fix this without unlocking bootloader.
mongs said:
my p10 plus got got bricked and it is always going to eRecovery without going to home screen after update. my phone is BOOTLOADER LOCK, NOT ROOTED THOUGH. and i want to fix this . i need help . ps : i hope theres a method that could fix this without unlocking bootloader.
Click to expand...
Click to collapse
hi, do you dolve your problme? i guess i have the same problem XD
regards
My P10 plus started this exact problem today. Always stock, never rooted or boot unlocked.
I was playing a game and it rebooted. Started again and lasted a minute but then constant bootloop to eRecovery screen.
Did the erecovery image download and didn't do anything brought me back to the same screen
Tried to factory reset on the ecovery screen and then booted, but during setup it rebooted.
Went to fastboot screen (pwr+vol down while attached to usb) and rebooted after. I was able to go through setup.
After letting it for sit for only 2 minutes as I type this message, it randomly started rebooting on its own.....and now back to recovery screen.
FACKKKKKKK
UPDATE: Took my phone in to a cell repair shop after exhausting all my troubleshooting options.
They said they took the phone apart to disconnect the battery and do a full power drain. Then after reconnected they installed EMUI 9.1 again via USB and got the phone up and running.
Been working for me for the past 6 hours, but the phone just rebooted on me once, so i'm sure they're still an unsolved demon in it. but no idea what it is right now.... May be time to start phone shopping.
maybe just battery broken, install app accu battery or any other to check batery
The phone rebooted by it self, no firmwareupdate going on, just random reboot.
Got stuck on redmi logo.
Could reboot and get fastboot, but could not flash original fastboot rom, got errors. a normal reboot gave only redmi logo.
Now the phone is out of power, not taking charge, not powering on.
Anyone have any solution for this problem? Or any tips? The phone is stone dead
Not sure if this will help...
here's my random reboot thread and fix
Well, i have no simcards or sd-cards inserted.
And its not charging or turning on. volume up and down + power is not making any results.
The weird thing is that it said "redmi" on the display for about 24 hours draining the power, and after it died out of power i'm unable to do anything with it. its basically a brick.
This happened totally random. just a spontaneous reboot into a never ending redmilogo.
During redmilogo i had the posibility to get it into fastboot by rebooting it, but mi flash would not accept the phone. so another reboot into regular boot ended in infinite redmilogo again :|
Your phone's bootloader unlocked?
Nope
Did you try keeping it charged for a while? Device might not show any sign (charging indication) but the battery will get charged eventually (I guess).
Charge it well and try to SIDELOAD that FASTBOOT IMAGE via PC..
It loooks like its bricked all by itself. i left it in charger for days.
I got contact with the phone with mi flash, but it has gone into some authentication mode with the flashing, so i'm not possible to reflash rom without authorization.
Read about this on reddit, and it seems like a dealer has to look at it.