Been having this problem with the latest 4.4 kitkat roms, (GE & AOSP)
when i was back on my old bootloader (whatever it shipped with) and modem (XXUEMJ5) i would always get a random force shutdown when just using my phone through daily use, it would either:
A) Boot for a short time with several apps having lost all their data (such as usernames and passwords). Then shortly after shutdown again into a constant bootloop. (Upon entering Recovery the phone would display 0% battery)
B)Shutdown into a bootloop only recoverable by wiping the /data partition or reflashing the rom (or any other rom).
So then i heard good news from the new bootloader and modem from the XXUFNA5 Leaks throughout the forums and decided to flash them and also test the leaked TW rom. Being me the rom was laggy as hell and i quickly reverted back to Jamal's 4.4 RC 1.1
Unfortunately the force shutdown bootloop problem continued but when it would shutdown i could plug the phone into a power source and boot without problems? not very convenient if you ask me.
just recently i flashed Brood's AOSP pre-RC4 which was working fine until i was signing into some apps then it force shutdown and as i tried to boot the phone went to "Updating apps 1 of 1" and then instantly shut down again.
I went into recovery and wiped /data, /cache and Dalvik then rebooted, the phone would reach the final stage of booting (just before the lockscreen shows) and would reboot and repeat the process all over again.
I went to flash a different rom so i could atleast have a working phone for the day and upon fully wiping, etc. the phone would not boot and continue the reboot process. i suspected a bootloader problem so i reflashed the bootloader and roms now boot. im guessing the bootloader was corrupted somehow and i think the process will just repeat itself.
Anyone got any ideas? I'm stumped and frustrated as the process of setting my phone back up every day is getting extremely boring.
Related
Hey there! I was updating my version of Paranoid Android and my kernel and it seemed fine at first but It yield some odd problems. I went into Clockworkmod recovery and Flashed my rom and kernel I then proceeded to wipe my cache and dalvik cache. I have done this many times before on many devices. I encountered a problem when I rebooted for the second time, I got the Android is updating apps display and I continued to get it every time I booted. The device would also randomly turn off when the screen dimmmed. I proceeded to set out and fix it. Here are the steps I took and the problems it caused.
Flashed stock rom-would not boot properly
Flash RESET kernel-I messed up and though this was a real kernel, my problems escalated from here.
Flashed stock rom and recovery.
Flashed reset kernel and then real kernel-Still had problems.
Flashed stock rom
My problems from all this accumulated somewhat and I can barely boot into fastboot. I get weird static screens and weird white noise sounds. It does not always let me boot into android and will get to the google logo 1 out of ten tries.
These is really unnerving and I have no clues whats what.
Note: I am using Faux123's kernels and his reset kernel.
Thanks a lot for any help!!!
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
The last few days I had an experience that I want to share. Maybe it helps somebody else.
Last week I upgraded my Defy from Quarx's CM10.2 to CM11 version 20140724.
It ran for about two days. It was stable and the performance looked better than before.
Then, when I was outside, my battery was empty. I always have another battery with me, so I exchanged the battery.
Then, two seconds after I inserted the battery, a black screen with the following white text appeared spontaneously, without pressing a button:
Bootloader
09.10
Code Corrupt
Ready to Program
connect USB
I could not enter recovery, or anything else.
So, I decided to go back and flash the original Motorola Android 2.2 version.
On earlier occasions this worked perfectly when I bricked my phone, but this time, after flashing the SBF with RSDlite, the phone hang while booting with the android logo on the screen. Only after a few hours of trying different SBF systems, the idea popped up, that the problem was not in the SBF, but in the combination of the old Motorola system and the new CM11 data partition. So, I entered recovery and wiped the data partition.
Then the system booted normally and I could proceed with rooting the system, installing custom recovery and restoring the backup.
Everything is back to normal again.
Now, I wonder what could have caused this problem.
I am a bit suspicious about the backup method I used. I create backups with the online nandroid app. The CM11 system installed the TWRP 2.7 recovery. The first time I tried to restore a backup, I noticed that the TWRP recovery had a problem with the old (CM10) and the new (CM11) backups, because they contained files for partitions and-sec and recovery, that it could not handle. In later attempts to restore the backup I unticked these partitions and the restore seemed to work well. I rebooted it several times. Could it be that these attempts damaged the system in such a way, that only when inserting a battery, the corruption was detected?
Or should I assume that there was a hardware glitch when the battery was replaced?
F.Zwarts said:
.
Then, when I was outside, my battery was empty.
Click to expand...
Click to collapse
iirc this was one of the bugs of cm11. if you let the battery runs completely down, it may not boot again. not sure if this has been fixed with the latest cm11.
Ended up "solving" this by doing a stock restore via Odin, after which TouchWiz would never load an icon (crash loop). Reinstalled TWRP via Odin, then flashed ViSiON X N3 via TWRP.
--
Morning guys,
I've had some reboots lately and a weird situation last week where I had to do operating system surgery to get the thing to boot at all.... HOWEVER things were going quite well for some time, and it's been rooted and non-stock for months.
Nevertheless I woke up this morning and it was off, I figured the battery had died so I swapped batteries... It boots, it gets to the launcher and it loads the app icons then freezes and reboots... over and over again.
edit: to be clear, as soon as the slider bar touches the right-hand side the phone freezes, the vibration holds for several seconds, and then the device reboots. obviously not what one expects from this operation (having done it before). I was able to wipe the Cache separately... trying to wipe the Dalvik cache all by itself in an advanced wipe does this reboot thing.
OK I said, i will just clear and reflash this.
Going into TWRP, attempting to do a factory reset wipe just freezes, buzzes, and reboots immediately (to the not working OS)... in order to make this all stop I pull the battery, because now the button on the side won't seem to do a hardware poweroff for anything. Just ends up resetting the current reboot.
--
Any advice would be helpful now. I was just going to say forget it and grab the tiniest ROM i could find and ride it out until I upgrade the device, but now I'm just concerned with getting it active. The rebooting in recovery when trying to do a wipe does not make me feel too great. First and only problem I've had with android roms.
Thanks,
Chris
Recently bought a new out-of-the box Galaxy S4 I337 from Amazon. Had i known how much trouble it would give me, i would have picked something else. When i first turned the device on, it was almost totally unusable due to lag and random reboots. Software version was 4.4.2. I used Odin to flash a rootable NB1 onto the device. Still had lag and random reboots. Upgraded to lollipop using this guide: https://forum.xda-developers.com/galaxy-s4-att/help/guide-att-samsung-galaxy-s4-sgh-i337-t3383078 and still have lag and random reboots. Also, the first time i upgraded to lollipop, i installed safestrap not knowing it wouldn't work on lollipop. Obviously, my recovery disappeared. When i figured out what was going on, i did a fresh install of lollipop. I got recovery back, but today when i tried to boot into recovery to wipe the cache, i discovered it had mysteriously stopped working again. If i attempt to boot into recovery, it just skips to the Samsung logo. I didn't install safestrap or any other custom recovery this time.
When i turn the phone on, either it hangs at the AT&T white splash logo and refuses to load at all, or advances to the lock screen. I have disabled animations and every widget i could on the lock screen and yet when i attempt to unlock the phone, it usually freezes. If i repeatedly swipe the phone for thirty seconds or so, it unlocks but it is still frozen and i have to continue swiping to prevent it from locking again. Eventually i'm able to navigate the phone normally, until it randomly reboots or freezes. Sometimes i see an error message that Touchwiz home, Process System, or SystemUI has stopped working or is not responding. This is always accompanied by a freeze. Also, choosing an option in the dialogue that comes up when i press the power button (shut down, reboot, etc) invariably causes the device to soft reboot. Other times a soft reboot happens totally at random, even if i'm not doing anything. Anybody have any idea what's going on or did Amazon just sell me a dud? All of these issues have been happening since before i rooted the device or upgraded it, except for the disappearing recovery mode.
Thanks in advance for your help.
Sounds like a data factory reset is in order. First you need recovery back so I would odin the latest firmware for the phone that can be flashed in odin. If it's still messing up then get Amazon to replace it.
Since you have safe strap though, try booting a TW based rom like Thor ROM or Golden eye ROM. That may fix some things.
StoneyJSG said:
Sounds like a data factory reset is in order. First you need recovery back so I would odin the latest firmware for the phone that can be flashed in odin. If it's still messing up then get Amazon to replace it.
Since you have safe strap though, try booting a TW based rom like Thor ROM or Golden eye ROM. That may fix some things.
Click to expand...
Click to collapse
Just wanted to bump this to thank you for your reply. Never got the phone to work but i was able to get it back to stock and return it. I got a refurbished S5 instead.