It's happened to me before, but eventually gets solved by itself. Now, however, with the advent of the Stock Oreo release I want to backup my phone ASAP.
I have tried with several different versions of TWRP and I also tried leaving it overnight and it still didn't boot. Any hints on what's going on?
Related
TL;DR: I have flashed the stock 4.2.1 image through fastboot, and yet my n7 wifi still reboots continuously at the google screen with the little unlocked lock.
Background: I have had the device for about 3 months, no real problems with it before this. I was reading yesterday night and i fell asleep, and thus instead of being on my desk all night the device was under a blanket. When i woke up, I opened the cover and found it on the google screen with the lock. It was warm, but not incredibly so. I thought it was weird that it had rebooted and apparently frozen, but i held down the power to turn it off. when i turned it back on, it started the google screen, then went black, then started the google screen again. Seems like there may be some sort of a kernel issue that is keeping it from booting. The next thing i did was to go into recovery (had CWM at this point, and it was rooted as well but that's a moot point if i can't get into the system.) and i did a backup, then wiped data and did a restore from the backup that i had just made. after rebooting, it made it all the way into the system, and seemed ok. I set it down, and a few moments later it turned off and started doing the loopy google screen thing again. Next, I went into recovery and wiped data/factory reset, and tried to boot up. no luck, still looping. Next, i grabbed the 4.0 toolkit from the dev section and tried to flash the stock recovery from that, but it was proving troublesome so i just downloaded the image myself and fastbooted then replaced cwm with the stock recovery, wiped everything, and flashed the 4.2.1 image. that should have worked, from what i understand, but no, still being loopy. I re-wiped and flashed, tried 4.1.2 instead, that didn't work, and i re-did 4.2.1. after flashing 4.2.1 and then leaving it boot looping for a little while, i noticed that it sometimes made it into the boot animation and then the animation froze and it rebooted and looped more. after a few more tries, powering it off, leaving it for a few min, and powering it on again, it booted all the way to the welcome screen to pick a language and then froze. some number of loops later, it made it all the way to picking a wifi network and froze. I have yet to make it past that point. Thinking it may help, i fastbooted CWM onto the device, so i have a more capable recovery now. I am now going to look into pushing a non stock rom to the device to see if that will help at all.
Any ideas on what on earth could have caused this? Was it just that the device was a little warmer than usual for a while?
Any ideas on how i can fix this? Much appreciated!
Lastly, should i consider looking at sending it back to google? I didn't think there was anything wrong with the hardware, but i'm not sure.
Thanks!
Update: After leaving the system repeating it's loopy boot thing for about 45 min, it seems to have finally booted into the system, and has yet to reboot again. I have no idea why this happened in the first case, nor why this finally worked in the end, but so far it seems ok.
More: Ok, so it still seems to be looping a lot. I have no idea why still. I'm having trouble getting it to boot back into the system, so hopefully something helps fix this.
Ok, so a day later it seems to have settled down such that there's very little looping on the google logo screen any more; now it just tends to randomly reboot when in use. this is quite frustrating, but seems more similar to what others have reported to be the case with 4.2.1. oddly, i never had these reboot issues before it decided to fail the first time, so i'm not sure if this is just because ii'm on 4.2.1. I may look at flashing back to 4.1.2 and staying there, i suppose it can't hurt. does anyone else have any ideas as to what could be going on?
So this issue has persisted throughout wiping data/factory resetting. I'm really not sure what this is.
Basically what happens is that my phone will gradually get slower and slower until it freezes and then reboots. However, after it reboots, it will go into a boot loop. What I will then need to do is basically wait it out by shutting it off. Then, I wait for an hour (maybe more) before I try turning it back on again, at which point it returns to normal.
Any idea? I thought it might be a memory leak? But how would that affect rebooting? I'd like to also mention that at one point my recovery somehow disappeared as well. I managed to re-flash TWRP using Flashify, but I haven't dared going back into the recovery, because last time when I had lost my recovery, I ended up thinking that I had to wipe my phone completely (because even Download Mode wasn't working correctly).
By the way, I'm running an AT&T LG G2 d800, on the "d80010q" firmware 4.2.2. I'm rooted, with Xposed modules running, as well as the camera mod flashed. No other modifications have been made except for buildprop and systctl (kernel) changes through android tuner.
Same issue
Hello,
I am having this exact same issue. Did you ever find a fix for this? I have been searching for hours. I have tried numerous things, flashing back to stock with lg flash tool, installing different roms, it happens on all roms.
Thanks
Hi, I was using my phone on 5.0.4 I believe (either that or 5.0.2) and then an app crashed unexpectedly, so I restarted my phone. While restarting it never got past the red dot with white circle animation, so I did a factory reset through the stock recovery and that didn't work either. I then did all kinds of stuff I found from other forums and finally flashed the stock 4.5.14 Nougat OOS from another thread using the MSM downloader tool, which let me start up the phone past the bootloop. However, the Wifi doesn't turn on at all, and every time I try to use any version of OOS beyond Nougat it bootloops again. I tried installing a few custom ROMs and they bootloop as well. What can I do? I would like to fix the Wifi on my nougat version of OOS, as a first priority, but if I can somehow fix the bootlooping issue on Oreo OOS then I'm sure the wifi will be fixed as a side-effect.
I also tried a bunch of things to fix the wifi, including deleting modemst files (didn't work) and flashing modem firmware which ended up causing the animation bootloop again. Please help!
Hey everybody, I need help. I have a J320P that is stuck in a boot loop, when it was found like this by my friend they came to me and asked if I could help. I have no information on how this happened other than they took a shower and when they came back it was like this. I have tried installing stock firmware 3 times to no luck. I might have an sd card somewhere with the backup for this phone but finding it would take some time so in the mean time I am turning to the forums. If anyone could help that would be amazing. I will provide more information and answer questions as they come.
Steps I have taken:
1. dirty flash of stock latest firmware
1. wiping the phone completely
2. Installing latest stock firmware
3. Still bootlooped
Not solved
So after triple wiping through TWRP and installing the stock firmware again it was still looping so i left to run to the store quickly and when I returned I tried powering it on and it loaded normally and I am still setting it back up.
Leaving the original comment. After coming home from work my friend said it had started doing it again, and it is. This time there was no root and no system anything messed with, does this mean there is a hardware problem?
So tl;dr version - i was using my tablet, saw an update to magisk, installed it, now it boots to black screen while running sambones rom
[SM-P580] [BQK1] SaMBoNeS
TWRP 3.2.3.0 --> 3.3.1.0
longer story:
i was trying to get a game to run, it wasnt...and realized it has been a while for a restart, so i checked to see if anything needs to be updated and saw magisk needed an update. i didnt note what version it was before but it was a version or two earlier than what it was trying to install.
rebooted to blackscreen no samsung logo
have tried restarting a dozen times, booted to TWRP, tried to force normal system boot through the UI, nothing.
I tried installing a new kernal [SiriKernel], it made it to the samsung logo, waited 15 - 20 minutes and it never made it past. restored a backup using TWRP
updated TWRP to 3.3.1.0, still no luck.
i had this problem a long time ago, and cannot figure out how i fixed it....it may have fixed itself but it isnt this time. any advice would be appreciated. I am trying to avoid wiping and starting again if at all possible because the problem seems familiar. also trying to stick to a rom for use with adaptive storage. if i do have to wipe if that can be done on a newer stock OS that's fine as well but last time i messed with this tablet it wasnt