I have the T-Mobile variant of the LG G2. I was using the latest CM11 nightly with no issues whatsoever then all of a sudden my device bootlooped. Now it keeps showing "LG" then the Cyanogen logo and then "LG" again etc. Sometime it says "upgrading apps" then "finishing boot" but then it goes back to the bootloop. I can get into recovery and tried sideloading the new nightly. It side-loaded correctly but the phone still bootloops. I tried with CM10, same issue. I tried with stock, same issue. What the hell is going on? It was working fine up until now!
I even tried installing these roms after wiping data and cache and it still doesn't work. Help me please!
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.
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?
First of all, hello all!
I'm a new member here.
So, what's the problem? Well, I recently rooted my Galaxy Tab 4 SM-T530 (WiFi only version) with Kingroot. Then I installed Cyanogenmod from the thread listed at the ROM section. All was working fine up until I decided to flash the GApps.
I chose the newest versions (both Zero and Mini for 6.0) but none of them worked.
Flashing went well. The problem was after booting.
After the first boot, I'd get caught in an endless loop of errors stating that "Unfortunately, Setup Wizard has stopped working". I couldn't do much other than rebooting. But then, I was greeted with yet another problem: it was stuck in a boot loop. Basically, after saying that it "Prepared Google App" and some others, the tab would repeat the process in an infinite loop. I left it for half an hour to do so, but the problem persisted.
Keep in mind the fact that I installed the newest version of Mini GApps package provided from that thread.
If any of you can help me out with this, I'd be very thankful, since this is the same time I install a custom ROM, and I really don't want to come back to the old Samsung ROM
http://forum.xda-developers.com/tab-4/development/rom-slimrom-5-0-1-alpha-0-7-t2963906
This is from where I installed all things needed.
Try again, this time flash both zips at the same time and not doing anything in the middle of both flashes. The usual cause of the same error in my other s3 is booting the ROM up, going back to recovery, then flashing GApps.
I never did anything else. Now I wiped data/dalvik/system/cache, reflashed the ROM and now just finished reflashing both zips in TWRP (first Mini then Zero, can't do them at the same time).
Now, I'm pretty much 'fingers crossed', as this is what an error told me. Pretty much tried to flash the zips without wiping anything/reflashing the ROM. That's why I went for a clean install.
EDIT: it didn't work at all. Still caught in the same "Preparing app x" boot loop. Now I'll let it run for 6 hours and see if not my own impatience is the problem.
EDIT 2: For some reason it took ages to boot up. Now, when I finished booting, I saw that the Play Store, Quick Search Bar and the Google Services weren't working at all. I tried to manually update them, but ended up in an agonizing loop of "Unfortunately, Google Services Framework has stopped" errors. Again, this leads me into thinking that the GApps from that thread aren't working.
The phone hasn't been rooted or otherwise tinkered with and is currently on android 5.0,.
Recently the phone has started boot-looping (never gets past the black S5-Active screen), though it strangely works fine while on the charger. This seems to have started when it tried to download an ota update from att a few days ago and the install failed.
I've tried using odin to flash it back to stock and start over, but odin seems to always fail, i can boot into stock recovery just fine and it will stay there once you get there.
Any help would be greatly appreciated.
Thanks in advance.
Tried clearing the caches from recovery?
yes, have cleared caches, and wiped data/Factory reset. neither seemed to have any effect.
Hey,
I have been using the ColtOS rom based on Oreo 8.1.0 for quite sometime now. I had it rooted with Magisk too. I have the latest version of TWRP installed (version 3.3.0). I had no problem until now where it just randomly tried to reboot after I ended a call. It did reboot fine once, but it was when i ended a second call that it got stuck in a bootloop.
I have tried everything, clearing the cache/Dalvik , wipe data and system and flashed three different Oreo ROMs, uninstalling Magisk. However, I can only go as far as the set-up screen after the new ROM boots, after which it goes back to rebooting itself endlessly.
I seem to have exhausted all my options, any kind of help to restore my phone will be greatly appreciated.
Thank you.
I have found out that I can flash new ROM and even set up the phone by logging into Google, only when I connect my phone to my laptop. It even installs all the previous apps and data and thats it. It reboots to the lockscreen and when I try to unlock it, it reboots again. And this is all only when I keep the phone connected to my laptop, otherwise,it keeps looping into the bootscreen logo.
AndroGuy18 said:
Hey,
I have been using the ColtOS rom based on Oreo 8.1.0 for quite sometime now. I had it rooted with Magisk too. I have the latest version of TWRP installed (version 3.3.0). I had no problem until now where it just randomly tried to reboot after I ended a call. It did reboot fine once, but it was when i ended a second call that it got stuck in a bootloop.
I have tried everything, clearing the cache/Dalvik , wipe data and system and flashed three different Oreo ROMs, uninstalling Magisk. However, I can only go as far as the set-up screen after the new ROM boots, after which it goes back to rebooting itself endlessly.
I seem to have exhausted all my options, any kind of help to restore my phone will be greatly appreciated.
Thank you.
I have found out that I can flash new ROM and even set up the phone by logging into Google, only when I connect my phone to my laptop. It even installs all the previous apps and data and thats it. It reboots to the lockscreen and when I try to unlock it, it reboots again. And this is all only when I keep the phone connected to my laptop, otherwise,it keeps looping into the bootscreen logo.
Click to expand...
Click to collapse
Flash crdroid nougat