okay, yesterday i got the jt super clean rom and stupidfast 1.54 kernel and it's been great. no problems at all...well i just plugged it up to my computer and it froze...i pulled the battery and rebooted it's just frozen and stays that way...i've rebooted multiple times and it's still happening. i can move around for maybe a minute or two, then its frozen again...i've reflashed a lower kernel and the kernel that came with superclean and still the same thing...what's going on? can someone help? thanks
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.
So I have been running CM11 since January and finally got around to updating to KitKat to see what was new and because CM11 wasn't using the kitkat kernel which I assume is what caused all the SoDs and instabilities in all the ROMs. Well now I'm on stock and I'm suffering horrible battery life in comparison (17 hours with 4 screen on vs 36 hours with 8 screen on). I tried flashing CM11 and it worked but after a day or two I wanted to try a new ROM. Carbon was one that I saw near the top of one of the G2 development forums so I decided to try that. Went through the normal process to flash a ROM and it bootlooped when I rebooted. My backup also boot looped and I had to use some method to go back to 12B since I had no ROM or anything on my phone. Got back to 24A and I tried flashing Malladus to see if a stock based ROM would work and it looped. Restored my backup and tried CM11 and it also looped. Now I'm sitting on stock with Verizon's bloat hogging resources and battery and a phone that won't flash and boot successfully. Is there any way I can fix this? Has anyone seen this before?
TLDR: phone won't flash a ROM without bootlooping since 24A update
Only gonna bump this once but I really hope the right person sees this. Really confused as to why my phone won't properly boot after a clean ROM flash
Hi, I'm sorry if I put this in the wrong sub forum or whatever but I'm new on this website.
Soo here is my problem that I have tried to fix for over a week now.
Ever since I flashed stock 6.0.1 Android firmware and the 6.0 bootloader, I've been having problems with my battery level indicator jumping from 93% straight to 100% when charging...Soo basically when the phone is charging and when it shows 93% and is about to go to 94% instead it goes to 100% straight away and when I reboot the phone to TWRP Recovery it shows 94% soo if I boot up into the OS, it charges up those 6% normally. Soo since that was happening I decided to try this on a custom ROM cause I thought this was only an issue with stock but it turns out that the same thing happens on Resurrection Remix ROM. After that I decided to try a custom Kernel and the same thing still happens...now I don't know if my device or my battery is faulty. Thanks to everyone that helps, again I'm sorry if I did something wrong.
Sent from my SM-G900F using XDA-Developers mobile app
Lately since i flashed the dirty unicorn 6.0 rom on my sgh-i337m its been giving alot of problems like overheating an constantly rebooting an i decided to revert back to other custom roms made for my phone but the ui keeps on freezing an the system apps keep crashing too ,an rebooting whenver the screen goes dark. ive reverted back to the stock rom an im still getting the problems any help would be apprreciated thank you.
Rebooting and overheating happens on the latest stock rom too? If it does, it could be a motherboard failure.
I had a phone that would overheat when connected to a charger when it was powered off. I could only fix the problem by replacing the motherboard.