I originally posted what's written below over in reddit but then the next day it rebooted randomly one time. It was then that I realised that the camera had begun causing reboots.
It started bootlooping before I tried to boot into recovery. It then got stuck on "installing new software" and got pretty hot before going blank with the blue light on.
S7 Edge Nougat Exynos unrooted
Not sure if relevant or not but I recently installed the Bixby apk that was on here and it screwed up the standard launcher. I set it Nova and it seemed to be working. I'd also recently removed greenify.
Edit - Fixed.... I let the battery run flat, rebooted into recovery and did factory reset. All good now.
Exynos unrooted Nougat
If anyone has ideas, I'd be very appreciative.
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?
Experienced a really annoying problem today. My phone was in my pocket and I heard the LG boot up sound, so I figured the phone just randomly rebooted (happens about once a month, so very rate). When I checked the phone, I was at the LG initial setup screen, and all my days was gone.
I was running KitKat D80220b, with root and twrp installed. Since G2 xposed was just updated, I tweaked for custom navigation buttons and bleed immersive mode. Has this happened to anyone ?
For now, I reinstalled D80220c and will only root, and probably wait till G2 xposed becomes more stable on KitKat. Thoughts, anybody ?
ganja_guru said:
Experienced a really annoying problem today. My phone was in my pocket and I heard the LG boot up sound, so I figured the phone just randomly rebooted (happens about once a month, so very rate). When I checked the phone, I was at the LG initial setup screen, and all my days was gone.
I was running KitKat D80220b, with root and twrp installed. Since G2 xposed was just updated, I tweaked for custom navigation buttons and bleed immersive mode. Has this happened to anyone ?
For now, I reinstalled D80220c and will only root, and probably wait till G2 xposed becomes more stable on KitKat. Thoughts, anybody ?
Click to expand...
Click to collapse
I also have the "G2 Xposed" and I've never had any problems ... probably the hard reset is enough to solve the problem
ganja_guru said:
Experienced a really annoying problem today. My phone was in my pocket and I heard the LG boot up sound, so I figured the phone just randomly rebooted (happens about once a month, so very rate). When I checked the phone, I was at the LG initial setup screen, and all my days was gone.
I was running KitKat D80220b, with root and twrp installed. Since G2 xposed was just updated, I tweaked for custom navigation buttons and bleed immersive mode. Has this happened to anyone ?
For now, I reinstalled D80220c and will only root, and probably wait till G2 xposed becomes more stable on KitKat. Thoughts, anybody ?
Click to expand...
Click to collapse
I think the same crap happened to me. Check THIS Post I made back at the AEON thread. I haven't been able to boot my phone correctly this last two days.It keeps rebooting after a minute or so after booting. Very annoying and even worse that I don't what caused this crap. If you got any possible solution and can help me get out of this reboot loop it would be very appreciated.
Kenepo said:
I think the same crap happened to me. Check THIS Post I made back at the AEON thread. I haven't been able to boot my phone correctly this last two days.It keeps rebooting after a minute or so after booting. Very annoying and even worse that I don't what caused this crap. If you got any possible solution and can help me get out of this reboot loop it would be very appreciated.
Click to expand...
Click to collapse
Maybe it's a stuck power button? If not, have you tried going back to stock using the LG flash tool?
So, I've been trying to root my Galaxy s5 for a while now and I just got it to work successfully a few hours ago. With that, I installed CWM and everything was fine.
Now, I downloaded the latest nightly of CM12 for the S5 and I threw it on my SD card and ran my phone with the up volume home and power thing, selected the zip and it's now looping. It's been looping for maybe 25-30 minutes. It stopped and said it was upgrading apps for optimization, rebooted and is now stuck on the loading screen for CM12.
I literally know nothing about CM12 or rooting or any of it, I just successfully did it today, so I'm extremely new and know nothing. I didn't factory restore my device, I didn't do anything fancy like that, the tutorial didn't say that I needed to, I just selected it and installed and rebooted.
I tried taking the battery out, and it's still doing the same thing.
Any help is appreciated.
Sir,
Please wait until mods will move this thread to the device specific forum for more relevant answers.
Stand by
Good luck
Hey all! I'm having a strange issue regarding boot looping that I can't seem to find an answer to on here or anywhere else, I hope you guys can help.
So my T-Mobile Samsung Galaxy S5 (SM-G900T), purchased in May 2014, while perusing Facebook the other day, randomly shut down in the middle of perfectly normal use and started bootlooping. I had never had the problem before. The device had been rooted for months (I forget what method I used) but it was running a stock Lollipop rom. The first thing I did was factory wipe and cache wipe through Android stock recovery. It worked!... for a couple hours. Then the bootloop started again.
I went and sought a new stock rom, believing that somehow mine had been corrupted, and flashed it via Odin. I also flashed TWRP. Clean wipes, new rom, dalvic/etc. wipes, and booted into stock Marshmallow. It worked!... for a couple hours. Then it started bootlooping again. I went into TWRP and tried to wipe just caches and whatnot, but it wouldn't start again. Long battery pulls sometimes allowed the phone to boot, but it started looping again after ~5-10 minutes.
So I installed the Twisted Lollipop but couldn't even get that to boot. I went back and found the earliest available firmware for my device (as I bought mine right after it came out) and flashed it. Wipe wipe flash wipe whatever, and a succesful boot. It was looking good! I was able to install a number of OTA updates. I was at Android 5.1 when I decided to call it a night and hold off on the further OTAs for today. Today I got up and got ready for work, all's well. As I'm getting ready to leave, I allow Google to update some apps, and begin installing Facebook, Spotify, Cap Metro (for my area's public transit system) and maybe something else, I don't remember. Anyway, as the updates are downloading or installing and I'm checking my email, boom, crash, bootloop.
What's going on here? I've never heard of hardware causing boot loops, but could it be that? I dropped my phone (although protected by a Spigen case) earlier this summer and it cracked the screen-- could it have messed with the motherboard in some substantial way? I had noticed it getting hotter and the battery lasting less than usual, but I attributed that to the device's age.
Any help, any advice, any direction you could give would be extremely appreciated. I don't have the capital to replace the phone right now, and I use it all the time. Thanks folks!
Hi, recently, I wanted to download the Xposed Framework. Everything turned out to be fine until I rebooted my phone. Based on the last step, it states that it might take longer than usual (10-20 min). Well, my phone ran on for about half an hour on the screen that says Samsung Galaxy S5 and so I decided to reboot it by taking out the battery. The same thing happened and I retried it a few times before one of the tries managed to go past the Samsung Galaxy S5 Screen and showed the Samsung icon. I thought everything was alright and let it run. It ran on for about 2 hours before I decided I had did something wrong. I wiped off all my data and of course, when I rebooted it on TWRP recovery, it states No OS installed. I decided to take this chance to upgrade my OS to 7.1.1 Nougat. Right now it is still downloading and I would like advice on what to do next. Thanks in advance!
P.S Since this is my first post, i am unable to provide the link in this message, if there is a need to, I can provide it in the chat.