[Q] Bootlooping no matter the ROM or stock - Galaxy S 4 Q&A, Help & Troubleshooting

Hi,
My Samsung Galaxy S4 (i9505) is crashing, rebooting and then bootlooping. I'll try to explain my course of actions so far.
I was running stock TW on 4.3 after the update went live for the UK provider Three. I was really tired of the TW UI so I followed the Jamal method to install the Google Play Edition ROM with 4.4. Installed the kernel too. After 24 hours the device would crash, reboot and bootloop. To get out of these bootloops I would pull the battery out, wait 30 secs, wipe cache, dalvik and sometimes even data. Whenever I used the camera app, it crashed. I then dirty flashed to the stable version of CyanogenMod 10.2, but the same thing happened, camera app killed it and bootlooped. I then tried all the CM11 nightlies, but same thing happened. I finally flashed stock TW back, and thesame thing is happening. Crashing on the first seconds. I have tried removing the SD card, I have noticed that my battery is swelling (perhaps from pulling it out, don't know if this is causing the crashes).
How do I make my phone go into it's completely original state? If I can't get a ROM that stays on, at least I'd like a stable stock.

Scarfall said:
Hi,
My Samsung Galaxy S4 (i9505) is crashing, rebooting and then bootlooping. I'll try to explain my course of actions so far.
I was running stock TW on 4.3 after the update went live for the UK provider Three. I was really tired of the TW UI so I followed the Jamal method to install the Google Play Edition ROM with 4.4. Installed the kernel too. After 24 hours the device would crash, reboot and bootloop. To get out of these bootloops I would pull the battery out, wait 30 secs, wipe cache, dalvik and sometimes even data. Whenever I used the camera app, it crashed. I then dirty flashed to the stable version of CyanogenMod 10.2, but the same thing happened, camera app killed it and bootlooped. I then tried all the CM11 nightlies, but same thing happened. I finally flashed stock TW back, and thesame thing is happening. Crashing on the first seconds. I have tried removing the SD card, I have noticed that my battery is swelling (perhaps from pulling it out, don't know if this is causing the crashes).
How do I make my phone go into it's completely original state? If I can't get a ROM that stays on, at least I'd like a stable stock.
Click to expand...
Click to collapse
If your still using a stock rom tw then try to factory reset your phone but if its still doesnt work here download the stock rom for your country http://www.sammobile.com/firmwares/2/ and flash it via odin. have a nice day.

I flashed the stock ROM. It is still happening. I just tried the CM Installer snapshot build. Lasts a few minutes, a surefire way to crash it and make it enter a reboot loop is by taking a picture.

Related

[Q] Phone will not start after first restart from a fresh flash

I have scoured the internet to find someone with the same issue as me, and I haven't found enough to fix the issue, so I'm placing a plea for help here. I have installed TWRP 2.6 recovery, and I am trying to flash OmniRom 4.4.2 nightlies. Originially I was trying to flash cyanogenmod 11, but I had this same problem. It appears to be any kit kat rom that causes the problem (I haven't tried flashing stock or any non-kitkat roms, but I was running on rooted stock before I tried to flash CM11). Anyways, When I flash I am wiping dalvik, cached, system, and data. Then flashing the rom, then flashing Paranoid android gapps. It will boot the first time fine. My phone will work just fine afterwards. However, if my battery dies or I restart, I will be unable to boot back into the rom and my phone becomes a soft brick. It will just stay stuck at the galaxy s 4 logo for as long as I leave it on. I have left it on for more than 30 minutes and there are no changes. I can't have my phone being just a dead battery away from being bricked, so I am asking for your help! Anything is much appreciated!
One other side note: I had my phone just lock up on me once in the middle of it running just fine. Afterwards it turned off on its own and tried to restart, but it resulted in the same issue. I don't know if this is related or just a bug in the rom.
schmidty455 said:
I have scoured the internet to find someone with the same issue as me, and I haven't found enough to fix the issue, so I'm placing a plea for help here. I have installed TWRP 2.6 recovery, and I am trying to flash OmniRom 4.4.2 nightlies. Originially I was trying to flash cyanogenmod 11, but I had this same problem. It appears to be any kit kat rom that causes the problem (I haven't tried flashing stock or any non-kitkat roms, but I was running on rooted stock before I tried to flash CM11). Anyways, When I flash I am wiping dalvik, cached, system, and data. Then flashing the rom, then flashing Paranoid android gapps. It will boot the first time fine. My phone will work just fine afterwards. However, if my battery dies or I restart, I will be unable to boot back into the rom and my phone becomes a soft brick. It will just stay stuck at the galaxy s 4 logo for as long as I leave it on. I have left it on for more than 30 minutes and there are no changes. I can't have my phone being just a dead battery away from being bricked, so I am asking for your help! Anything is much appreciated!
One other side note: I had my phone just lock up on me once in the middle of it running just fine. Afterwards it turned off on its own and tried to restart, but it resulted in the same issue. I don't know if this is related or just a bug in the rom.
Click to expand...
Click to collapse
Omni clearly states that it is an alpha, so you mileage may vary considerably.
Sounds kernel related. Have you tried just reflashing the kernel and seeing if it'll boot after that. Or trying a different kernel?
Thanks for the reply! I actually just fixed the problem on my own. I used Odin to flash a newer version of TWRP and then flashed omni, and it looks like everything is working just fine. I read a few people saying that they were having issues flashing kit kat roms with older versions of recovery, so I figured it was worth a shot.

Phone turns off while loading any custom rom

I was on paranoid android 4.44 and switched to art. The next day the phone restarted while I was taking panorama picture. I had never taken panorama pictures, so I don't know if it is the camera app or art. Eventually the phone would reboot and turn off. I did a wipe of data, dalvik, etc and that did nothing. I then reinstalled paranoid android ROM and reinstalled and the Same problem. I wiped again and this time I installed slimrom, and the exact same thing happens.
Tries to load ROM, for a couple of seconds it shows optimizing apps square and then turns off. If I turn device on again, the same happens. It doesn't matter which ROM I use. Any ideas? Prior to this, my paranoid android ROM ran flawless for about two weeks. Before that I was testing different roms .
Suggestions??? I searched the forum, but couldn't find this specific problem.
I have a nexus 4 and I use twrp 2.7.1
Sent from my SM-T320 using Tapatalk
Have you tried flashing factory image?
Yes. I figured what it was. If I connect the phone to the wall, it stays on. It is either the battery or something to do with getting energy from the battery.

lag, freeze, restart after 6.0.1

hey guys, today i bought a used NOTE 4 for my mother, and when i checked the version it was 6.0.1...so i wiped everything and restarted the phone to get the best performance....but the phone lags and freezes a lot, especially in the camera, and it keep restarting all the time....what should i do? should i try to flash another FW through ODIN?
You mean you used the Factory reset option? That's not a full wipe, just resetting stuffs. And yes, you know the answer, wipe everything from a custom recovery, then flash stock MM ROM (always latest) via Odin. Earlier versions did have a reboot problem though, and lags here and there, but that's expected, but the last release, PE1, has got rid of all those problems, its a very good release already, and I am sure upcoming releases will only make it better. There are no major bugs at all, I don't even find any minor bugs except the need for a separate app to clear default apps selection.
Best of luck.
ithehappy said:
You mean you used the Factory reset option? That's not a full wipe, just resetting stuffs. And yes, you know the answer, wipe everything from a custom recovery, then flash stock MM ROM (always latest) via Odin. Earlier versions did have a reboot problem though, and lags here and there, but that's expected, but the last release, PE1, has got rid of all those problems, its a very good release already, and I am sure upcoming releases will only make it better. There are no major bugs at all, I don't even find any minor bugs except the need for a separate app to clear default apps selection.
Best of luck.
Click to expand...
Click to collapse
the phone is stock, it has the stock recovery, and i have the PE1 version, the exact name is "MMB29M.N910FXXU1DPE1"...and still got a lot of lag, freeze and rebooting.....is there another version?
EDIT: ok, so i flashed another MM through odin ( first time it gave me a fail) and then done a factory reset, now it's so much better, maybe not as smooth as my S6 but really fast and smooth enough...thanks for the help
EDIT: today the phone started to shutdown completly....not reboot....and you need to press the power button 10 seconds to reboot it or turn it on...is there any advice?
Guys . Ib tead the whole thread over last few day had wake lovk runnimg last couple weeks. Lastnight used kies for reset and it crashed half way.
I then used odin 307 and went back to stock 501
It booted strarted to restore from google apps ect .
I allowed the 1st 601 update
All apps running aok no crashing freezing no wakelock .. its asking for another 601 update. Im gonna hold back
Hope this helps .. will post agian in gew days with any updates
Good luck !!
Just download and install Wake Lock from Google Play Store. I had the same problem and more. Once I installed Wake Lock (on a fresh install from Android 5 up to all the 6.0..1 builds) phone doesn't shut off or freeze. Most importantly no more Boot Loops..

Phone in a freeze+reboot loop on CM14.1, started after turning phone off for a min.

About an hour ago I turned the phone off while it was plugged in to my PC charging. I was on CM14.1 20161208 nightly and whatever the newest opengapps ARM 7.1 mini was at the time of that nightly. After 5-10 minutes I turned the phone back on and ever since then it will boot up and I can do stuff or just let it idle for maybe 15 seconds before it freezes and reboots itself. I never had any problems with it prior to this, other than auto-rotate not wanting to work in some cases.
I have tried battery pulls, dalvik/cache wipes, a reflash of that nightly, a full wipe of everything by SDCARD/USB Storage and install of latest 20161225 nightly and latest opengapps ARM 7.1 mini(tried this 3 times so far). Nothing has fixed it.
It's obviously rooted, did the dev aboot bootloader unlock method last year, is on the bok3 firmware.
Not sure what to do at this point. Is the phone trashed?
ETA: It seems the problem goes away if I do a full wipe and install of my rom, but do not install opengapps. Makes no sense, I had no problems with the phone or opengapps before turning the phone off earlier today.
ETA2: After letting it sit for a while, and configuring some settings, I decided to reboot in to recovery and try the latest opengapps arm 7.1 pico to see if that made any difference. After boot it took about 15 seconds for the phone to freeze. Why am I suddenly not able to run opengapps on my phone at all?
ETA3: Fulled wiped and installed rom again. Worked fine until I google-searched for the play store apk, viewed a thread here, clicked on the apk link, and once it should have started downloading the phone froze and rebooted. Working fine now, but it for whatever reason that download trigged the freeze/reboot. Could really use help with this before I'm forced to go out and buy a new phone before I go back to work on Tuesday.
johnnyrichter said:
About an hour ago I turned the phone off while it was plugged in to my PC charging. I was on CM14.1 20161208 nightly and whatever the newest opengapps ARM 7.1 mini was at the time of that nightly. After 5-10 minutes I turned the phone back on and ever since then it will boot up and I can do stuff or just let it idle for maybe 15 seconds before it freezes and reboots itself. I never had any problems with it prior to this, other than auto-rotate not wanting to work in some cases.
I have tried battery pulls, dalvik/cache wipes, a reflash of that nightly, a full wipe of everything by SDCARD/USB Storage and install of latest 20161225 nightly and latest opengapps ARM 7.1 mini(tried this 3 times so far). Nothing has fixed it.
It's obviously rooted, did the dev aboot bootloader unlock method last year, is on the bok3 firmware.
Not sure what to do at this point. Is the phone trashed?
ETA: It seems the problem goes away if I do a full wipe and install of my rom, but do not install opengapps. Makes no sense, I had no problems with the phone or opengapps before turning the phone off earlier today.
ETA2: After letting it sit for a while, and configuring some settings, I decided to reboot in to recovery and try the latest opengapps arm 7.1 pico to see if that made any difference. After boot it took about 15 seconds for the phone to freeze. Why am I suddenly not able to run opengapps on my phone at all?
ETA3: Fulled wiped and installed rom again. Worked fine until I google-searched for the play store apk, viewed a thread here, clicked on the apk link, and once it should have started downloading the phone froze and rebooted. Working fine now, but it for whatever reason that download trigged the freeze/reboot. Could really use help with this before I'm forced to go out and buy a new phone before I go back to work on Tuesday.
Click to expand...
Click to collapse
you are on a Beta, it is expected, if you need stability flash CM13
GeTex said:
you are on a Beta, it is expected, if you need stability flash CM13
Click to expand...
Click to collapse
I didn't think it was the rom since I reflashed a previously working version, tried the latest version, performed several full wipes, etc. I'm fetching the latest 13.0 and will get the latest opengapps mini for it and see if that helps.
GeTex said:
you are on a Beta, it is expected, if you need stability flash CM13
Click to expand...
Click to collapse
Rebooted to recovery, wiped everything but externalsd and usbstorage, installed "cm-13.0-20161013-SNAPSHOT-ZNH5YAO21M-kltevzw.zip" and "open_gapps-arm-6.0-micro-20170121.zip", rebooted, went through preparing apps which I don't think it did on the repeated 14.1 installs earlier, now I'm going through my usual setup and app installs with no freezes. Seems like it was a 14.1 issue.
Thanks GeTex.
johnnyrichter said:
Rebooted to recovery, wiped everything but externalsd and usbstorage, installed "cm-13.0-20161013-SNAPSHOT-ZNH5YAO21M-kltevzw.zip" and "open_gapps-arm-6.0-micro-20170121.zip", rebooted, went through preparing apps which I don't think it did on the repeated 14.1 installs earlier, now I'm going through my usual setup and app installs with no freezes. Seems like it was a 14.1 issue.
Thanks GeTex.
Click to expand...
Click to collapse
I figured
If you don't mind answering one more for me...
I'm on OK3. Is there any path to upgrade to a newer firmware while maintaining unlocked bootloader and root, or is it advised that I stick to OK3 and use only the DEV ABOOT roms like I have been?
johnnyrichter said:
About an hour ago I turned the phone off while it was plugged in to my PC charging. I was on CM14.1 20161208 nightly and whatever the newest opengapps ARM 7.1 mini was at the time of that nightly. After 5-10 minutes I turned the phone back on and ever since then it will boot up and I can do stuff or just let it idle for maybe 15 seconds before it freezes and reboots itself. I never had any problems with it prior to this, other than auto-rotate not wanting to work in some cases.
I have tried battery pulls, dalvik/cache wipes, a reflash of that nightly, a full wipe of everything by SDCARD/USB Storage and install of latest 20161225 nightly and latest opengapps ARM 7.1 mini(tried this 3 times so far). Nothing has fixed it.
It's obviously rooted, did the dev aboot bootloader unlock method last year, is on the bok3 firmware.
Not sure what to do at this point. Is the phone trashed?
ETA: It seems the problem goes away if I do a full wipe and install of my rom, but do not install opengapps. Makes no sense, I had no problems with the phone or opengapps before turning the phone off earlier today.
ETA2: After letting it sit for a while, and configuring some settings, I decided to reboot in to recovery and try the latest opengapps arm 7.1 pico to see if that made any difference. After boot it took about 15 seconds for the phone to freeze. Why am I suddenly not able to run opengapps on my phone at all?
ETA3: Fulled wiped and installed rom again. Worked fine until I google-searched for the play store apk, viewed a thread here, clicked on the apk link, and once it should have started downloading the phone froze and rebooted. Working fine now, but it for whatever reason that download trigged the freeze/reboot. Could really use help with this before I'm forced to go out and buy a new phone before I go back to work on Tuesday.
Click to expand...
Click to collapse
i have the same problem and no matter witch custom rom that is 7.1.1 it does the same thing (turns on for 15 seconds, freezes, then reboots, and repeat)
N0rth3rnl1ght said:
i have the same problem and no matter witch custom rom that is 7.1.1 it does the same thing (turns on for 15 seconds, freezes, then reboots, and repeat)
Click to expand...
Click to collapse
My phone ran fine on CM14.1(7.1.1) for at least a month and a half. Not sure why turning the phone off made it stop working with that version. CM13.1 is stable, have you tried that?
Been having the same issues with a 7.1.1 rom Mokee. For the time I've reverted to my S4....
Exact same steps i took. Flashing, wiping, and everything minus external SD.
There is a bootloader update which I did. There is a full update bootloader (I updated and now on PL1) which takes you to Safestrap then back yo TWRP. Others have reported just flashing a PL1 firmware in Odin under AP runs stable.
At this point I'll drop to 6.0 roms, my issues is holding cell service. I can't get any clean flashed rom to give me full data and call service.
I'd like to update firmware/radios if it's possible and won't break my unlock/root and still allow TWRP. Just not sure how to do it properly, starting with my unlocked/rooted BOK3 firmware.

S5 G900V Freezes and Crashes Every 30 Seconds

Hello all,
I recently went through the process of installing CM 14.1 on my Verizon-Unlocked Galaxy S5.
Everything was working fine until about 3 weeks ago when I started messing with the system settings.
My phone started freezing and crashing, so I attempted to reinstall CM 14.1 multiple times.
I have wiped everything on the phone multiple times through TWRP (System, Data, SD Card, Everything...) and I am still having the same issue.
The phone boots fine, and I am able to get through the first two menus in the initial setup, but then the screen freezes and the phone restarts.
I have tried replacing the battery, thinking that would fix the problem, but it didn't...
Should I revert back to the stock ROM and start from there, rooting and such, until I make my way back to CM?
Thanks everyone, Luke
If youre still having problems, try reflashing your rom and then flash an older version of opengapps, I think I used the one from 01/16/17. The new opengapps were giving me the same exact problem.
Dang, I wish I would have seen this sooner... I went ahead and flashed back to the stock Verizon ROM with root. Thanks though! Maybe this can help someone else.

Categories

Resources