Boot Loop when Wifi or Radio Turned On - AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin

Yesterday I noticed my phone sitting on a desk spontaneously reboot, it kept doing this continually and started to get hot and drain the battery.
Through hours of trouble shooting I noticed if I turned Airplane mode on, the reboot loop would stop. If I then turned on either Wifi or the Cellular radio, it would reboot as soon as it connected.
I have cleared cache/dalvik, deleted the wpa_supplicant.conf file, checked the battery (its not bulging nor does it spin if set down), and safe mode.
Oh and its stock 4.4.2 rooted, no mods.
It does not boot loop in recovery.
I have also removed the SD card and the SIM, but it continues to boot loop.
I have no new apps or updates, I believe the last app I updated was over a week ago.
Searching here and elsewhere found nothing close to this. Anyone have any idea what this is or a possible fix?

Related

Charging issues (solved)

purchased a new Galaxy S4, from sprint.
rooted using auto-root and installed teamwin recovery. all good. kept using the phone flawlessly for three days.
was going to flash CM10.2 through the recovery when i noticed the big button in the CyanogenMod home advertising the installer.
since this phone is compatible, then decided to try that.
CM11 installed right away and worked great, charged the phone, took a couple pictures, great.
then an update was requested to the ROM, so i installed it.
that update resets all my settings, so i started downloading all my apps and applying the settings again.
when the phone was around 18% of charge, i plugged the phone and nothing happened.
tried another phone with stock android in the same charger and everything went well fine so, i turned off the
SGS4 and plugged it again.
it vibrated once, (like it was about to start charging) but nothing happened. a few seconds later, it vibrated again, and that went on and on...
turned back on the phone in recovery, i noticed that TeamWin was replaced by ClockWorkMod recovery.
wiped Dalvik, cache and did a factory reset. turned phone back off and plugged the charger.
now it vibrates once, the screen lights up, a drained battery shows up and nothing happens, (just like it froze there).
the phone is not taking charge and its dead jim. doesn't have enough charge to power on.
havent tried anything else.
any clues or workarounds?
please and thanks.
EDIT: downgraded to CM10.2.1 and installed chronic kernel for CM10.2, problem solved.

Flight mode messed up phone

I dont often use flight mode, but when I did recently, about an hour later I noticed the phone was dimly lit and on. It was on the Samsung logo, like it rebooted and stuck on boot. The blue LED was on and the 'kernel not seandroid enforcing' in the corner. Could not turn it off without removing battery. Even when I put battery back in, again stuck on boot.
Eventually managed to get into recovery and wiped dalvik and cache, but still same problem. This is on MM 6.01 stock debloated (either xXx 2.1 or _andr 3.3 devbase). Restored a full backup and managed to boot and seemed to work OK, but it again froze after 10-15 min.
Problem was only fixed when I restored an older LP backup (xXx 1.6). 2 days later works fine even in flight mode. Anyway, googling this issue, seems a few others experienced same, but on LP. Havent seen instances of it happening on MM, but not sure I want to go back to MM so soon.
Anyone else experienced similar issue? And what could have caused this to happen when in flight mode?
Same thing happened to me with the BTU modded MM 6.0.1 ROM G900FXXU1CPDF-BTU, but nothing to do with flight mode, I just noticed the phone dim and stuck trying to boot
I went back to G900FXXU1CPD7-BTU and it's been fine since

Probably bricked LG G2 running SlimSaber

So basically this rom is awesome but it had only one problem. When I plugged my phone in the charger while it was turned off, it bootlooped until I restarted with the cable off. It was no big deal and nothing bad ever came out of it.
Yesterday my batter ran out while I was asleep and when I woke up it was already turned off. I, absentmindly, tried to turn it on, LG Logo, off again. Did it one more time, nothing happened, realized it's out of battery. Plugged in charger, try to turn it off/on, usual bootloop happens. Say ok and proceed with what I always did, phone gets past LG Logo, goes into SlimLP boot animation and for the first it has just stayed there. No restarts, just endless loading. Longest i Left it on to load was about 45 minutes. Never got back on.
Apart from that, I think that for some reason my recovery got uninstalled somehow, by itself, a few weeks ago. I only noticed this because before, when I wanted to get into recovery, I pressed the usual buttons and it went straight into TWRP. Now the same buttons take me to the "Factory reset screen". I know that everyone says to just go ahead and press power, but I am afraid, since I am not sure if TWRP is still functioning. This happened to me another time on the same phone, and when I confirmed the factory reset, it factory resetted.
My problem here is that I want to get my music and photos. I'm only able to enter that factory reset screen and download mode. Can I "flash" twrp safely from download mode? Should I use Flash Tool 2014 and Normal flash(which says it keeps the data) a stock g2 rom? Can I mount my phone to the computer in download mode to copy my files? I want the most risk-free approach.
Thanks in advance.
giorgos123 said:
So basically this rom is awesome but it had only one problem. When I plugged my phone in the charger while it was turned off, it bootlooped until I restarted with the cable off. It was no big deal and nothing bad ever came out of it.
Yesterday my batter ran out while I was asleep and when I woke up it was already turned off. I, absentmindly, tried to turn it on, LG Logo, off again. Did it one more time, nothing happened, realized it's out of battery. Plugged in charger, try to turn it off/on, usual bootloop happens. Say ok and proceed with what I always did, phone gets past LG Logo, goes into SlimLP boot animation and for the first it has just stayed there. No restarts, just endless loading. Longest i Left it on to load was about 45 minutes. Never got back on.
Apart from that, I think that for some reason my recovery got uninstalled somehow, by itself, a few weeks ago. I only noticed this because before, when I wanted to get into recovery, I pressed the usual buttons and it went straight into TWRP. Now the same buttons take me to the "Factory reset screen". I know that everyone says to just go ahead and press power, but I am afraid, since I am not sure if TWRP is still functioning. This happened to me another time on the same phone, and when I confirmed the factory reset, it factory resetted.
My problem here is that I want to get my music and photos. I'm only able to enter that factory reset screen and download mode. Can I "flash" twrp safely from download mode? Should I use Flash Tool 2014 and Normal flash(which says it keeps the data) a stock g2 rom? Can I mount my phone to the computer in download mode to copy my files? I want the most risk-free approach.
Thanks in advance.
Click to expand...
Click to collapse
Hi, first If you can enter download mode I think you can flash kdz (Kitkat) file to stock using Flash Tool 2014. But I had this problem once and the keep data flashing didn't work (stucked at 50%), I ended up flashed it with other option (erased all data).
2. You can try the "Factory reset" nice and easy.
I think you can't see files on the device unless you enter Twrp.
It's wise to backup your phone on the computer montly or so, thank you.
I went ahead and nuked my download mode using the SRK tools. Then got access to fastboot, through which I booted to twrp and then I could move my files. All's fine, flashed my ROM again and it's going better than ever.

Stuck in Boot Loop (Recovery mode doesn't work)

Hi, I replaced the battery in my Moto X Pure edition and when I tried to power it on it just kept restarting. The phone would not power on before the battery was replaced and was basically bricked. Anyway, I can't get it to boot into recovery mode or show the exclamation point. I can open the bootloader but it seems to just ignore it and after I exit it nothing changes. I don't know what to do. If any of you know please help!
P.S. I never reflashed the ROM or anything everything is stock.
Similar issue
I am unable to get TWRP to load on my phone, I woke up two days ago and had seemingly powered off overnight despite it being on a charger and the notification light was still on (I'm using lineageOS 14.1 so the light under speaker grill is functional) after powering the phone on I started getting Google play services stopped working messages. Trying to fix it I cleared the cache for the app and rebooted, the issue persisted so I decided to load a back up through TWRP but it will not load for me. It just loops the loading screen for TWRP. Any useful ideas or insights would be greatly appreciated.

Boot loop issues on stock phone

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.

Categories

Resources