Hello,
I am having an issue where my phone freezes and reboots. It does not seem to have any rhyme or reason why it is doing. Sometimes it will do it while it is just sitting on my desk doing nothing. When it crashes and reboots it will go into a boot loop showing the LG logo, then black, then showing the LG again. It will cycle through this loop a few times and will boot into the ROM eventually.
I have looked through the whole Q&A thread searching for freezing, auto restart, crashing, etc but have not found a fix for this. I have flashed back to stock with the LG flash tool using the tot and dll files. It started happening right after I got into the stock rom. I have clean flashed various different ROMs as well. It started happening when I was on Cloudy G3 2.1. I then went to the Resurrection Remix Lollipop rom and it happened there as well. I pulled the battery as well following a guide from youtube. Nothing has seemed to fix the issue. I saw a thread about using Ubuntu to push some img files and openrecovery to the phone but I am not sure if that will fix it either since I flashed back to stock.
Does anyone have any ideas or can point me to a thread I might have missed? I have the D800 AT&T model running the Bliss Pop 1.7 ROM right now.
Thank you in advance for any help.
bump - Anyone?
Related
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.
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
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
Ive been running CM12 for a long time, but today I noticed I had a few missed calls and my phone hadnt rung. I rebooted the phone and it went into a boot loop. I cleared cache, but still bootlooping, dirty flashed the latest nightlie and then a full wipe - all of which resulted in the boot loop.
I restored my phone using the TOT method, but it would get to the setting up google account/wifi etc and reboot.
I used KDZ to install 30b lollipop ROM this seemed ok until reboot and then it would factory reset, optimise apps every time and be back to the setup screen.
I managed to install KK using KDZ and this seems more stable so used IOROOT and Autorec. I then flashed CM12 and GAPPS again, but it started to boot loop again.
I hadnt done anything to my phone prior to the problems - ie. no new ROMs, kernels or even apps.
Any suggestions or does it sound like something more physically wrong?
I have managed to get Cloudy G2 2.2 working without any problems except it isn't recognising my SIM. Does anyone have any thoughts or is this a dead phone?
. For the past few days my phone has been crashing and turning off randomly, when the phone is off the charger. The screen just goes black and Shuts down. When I try to reboot the phone it will get upto the boot animation and then freeze and shutdown again. I have to connect my phone to a charger and then reboot, only then does it fully boot up. My battery is 100% btw.
What I have done so far is:
1) flashed the latest build of exodus
2) cleared dalvik and cache
3) flashed an earlier build (25/07) without flashing XPOSED and SUPERSU. However problem still present.
Can someone help please and tell me what other steps I can take. My phones important to me at the moment as I'm away in Turkey for an internship. It's a really strange problem I can't figure out what to do. Thanks alot
Did you try to go bacm for stock oneplus OS? Try to do a full recovery via the tool it will wipe root twrp back to stock. It may help.
Does it happens with other roms?
hi, i solved the problem by flashing stock oxygen. i tried flashing oxyslim and cyanogen however both of them still had the same problem. Anybody have a idea of why this might have happened? it was completely random, and if it was the kernel then it would have been solved when i flashed the other roms...strange
Zeeshansafdar1 said:
hi, i solved the problem by flashing stock oxygen. i tried flashing oxyslim and cyanogen however both of them still had the same problem. Anybody have a idea of why this might have happened? it was completely random, and if it was the kernel then it would have been solved when i flashed the other roms...strange
Click to expand...
Click to collapse
It could be that te ROMs u DL were corrupted. This happens, thats why is always good yo verify HASH from your dl ROM and HASH from the developers topic
So you haven't read up on the official CM13 thread about the latest unstable builds?