I have a D801, nothing terribly unusual about my setup. But every time I flash a CM 12.1 nightly it gets stuck on the CM boot anim on the subsequent boot. I'm using @blastagator's TWRP 2.8.7.1 and I make sure to wipe cache & dalvik every time. A reboot doesn't help but reflashing SuperSU via TWRP seems to fix it. Anyone have any ideas?
Related
I did a clean wipe, regular recovery procedures and flashed the latest 0819 nightly of CyanogenMod 10.2 yesterday, but after restart, my phone is just stuck with the Google logo loop. I did go from CM 10.1 with the latest TWRP.
What should I do to solve the problem?
Restore your nandroid backup, or flash another rom thru recovery. I had the same problem franco's kernel was causing the boot looping issue
Hey guys,
I'm not a total scrub at flashing roms and there's still a bunch of things that I don't understand. I'm pretty positive that I flashed Slimrom correctly but here's the situation.
Started on 4.2.2 Slimrom
Reboot to TWRP recovery
Format factory reset/format data, system, cache, dalvik cache
Flash Slimrom 4.3 stable build 1
Successfully reboots into 4.3
Okay now here's the weird part.
The first time I rebooted back into recovery to flash gapps. After I flashed gapps and tried to reboot into the rom, the phone freezes at the screen with "google" and the unlock sign on the bottom. The only way I can get it to boot into the rom again is if I reformat/reset EVERYTHING (including format data) and reflash 4.3. After a few tries of messing around with not wiping dalvik/cache and stuff I realized that even if I don't flash gapps it still freezes on the google screen. So here's my main problem
After flashing 4.3 slimrom, the phone boots into the rom only once. If I try restarting my phone it freezes on the "google" screen.
Anyone know what I'm doing wrong?
Just to clarify it's a LG Google Nexus 4 mako.
Sorry if I'm being redundant. I just want to give as much detail as possible. If you need anymore info let me know!
Thanks
ms3195 said:
Hey guys,
I'm not a total scrub at flashing roms and there's still a bunch of things that I don't understand. I'm pretty positive that I flashed Slimrom correctly but here's the situation.
Started on 4.2.2 Slimrom
Reboot to TWRP recovery
Format factory reset/format data, system, cache, dalvik cache
Flash Slimrom 4.3 stable build 1
Successfully reboots into 4.3
Okay now here's the weird part.
The first time I rebooted back into recovery to flash gapps. After I flashed gapps and tried to reboot into the rom, the phone freezes at the screen with "google" and the unlock sign on the bottom. The only way I can get it to boot into the rom again is if I reformat/reset EVERYTHING (including format data) and reflash 4.3. After a few tries of messing around with not wiping dalvik/cache and stuff I realized that even if I don't flash gapps it still freezes on the google screen. So here's my main problem
After flashing 4.3 slimrom, the phone boots into the rom only once. If I try restarting my phone it freezes on the "google" screen.
Anyone know what I'm doing wrong?
Just to clarify it's a LG Google Nexus 4 mako.
Sorry if I'm being redundant. I just want to give as much detail as possible. If you need anymore info let me know!
Thanks
Click to expand...
Click to collapse
Are you flashing the right Gapps package? Be sure you are flashing the latest 4.3 one.
abaaaabbbb63 said:
Are you flashing the right Gapps package? Be sure you are flashing the latest 4.3 one.
Click to expand...
Click to collapse
Yep I'm positive. I redownloaded both the 4.3 rom and gapps package multiple times just to make sure. Also it doesn't reboot even if I don't flash gapps. Doesn't boot at all if I flash both the rom then gapps at the same time.
bump
then, wipe data/factory reser and flash the stock rom. the rom might be the problem
davinnwilliam said:
then, wipe data/factory reser and flash the stock rom. the rom might be the problem
Click to expand...
Click to collapse
It works for everyone else though. It's Slimrom 4.3 stable build 1.
Rom isn't the problem.Slim rom beta 1(4.3) is super stable. Use any version of twrp recovery other than 2.6.1.0 and wipe system+data,flash slim rom,flash slim gapps,reboot.
Note: if you flashed franco kernel then this may be the issue for your bootloop also you may want to upgrade your bootloader and radio to 4.3 versions(bootloader more important)
Was on cloudy's latest gpro2 rom with dorimatrix 4.8.1, updated to 4.9 and wiped cache and dalvic cache and upon first boot everything I would click force closed after a minute or so so I attempted rebooting. It would then go into a bootloop. I adb rebooted into recovery, wiped the caches, and flashed 4.8.1. It now did the same thing as it did before, followed by a bootloop when I rebooted it. Decided to try flashing to a different rom, so I did a complete backup and sent over the latest CM11 nightly. Wiped all and flashed, and now I'm bootlooping at the CM screen with no recovery access.
I remembered when I was already bootlooping that I needed to flash the 4.2.2 partitions to use an AOSP roms. A little too late huh. Now I'm stuck at the CM bootanimation and no ADB. Are my only options to use mobile odin and start over from or can you guys come up with something else?
mejorguille said:
Was on cloudy's latest gpro2 rom with dorimatrix 4.8.1, updated to 4.9 and wiped cache and dalvic cache and upon first boot everything I would click force closed after a minute or so so I attempted rebooting. It would then go into a bootloop. I adb rebooted into recovery, wiped the caches, and flashed 4.8.1. It now did the same thing as it did before, followed by a bootloop when I rebooted it. Decided to try flashing to a different rom, so I did a complete backup and sent over the latest CM11 nightly. Wiped all and flashed, and now I'm bootlooping at the CM screen with no recovery access.
I remembered when I was already bootlooping that I needed to flash the 4.2.2 partitions to use an AOSP roms. A little too late huh. Now I'm stuck at the CM bootanimation and no ADB. Are my only options to use mobile odin and start over from or can you guys come up with something else?
Click to expand...
Click to collapse
Fixed it... realized I still had recovery active, booted into it with the button combo, wiped, installed cloudy pro, all is good.
I have noticed a few people including myself who have had TWRP or the recovery partition some how corrupted after flashing a 5.1/5.1.1 kernel or rom.
Usually what seems to happen is that a 5.1 kernel/rom is flashed (data/cache f2fs for me) which leads to a bootloop. Restarting to bootloader and on to recovery ends up with twrp not loading.
I've noted that this has happened for me with mkernel a75, and also to a user flashing the latest phantom alpha, and to someone who flashed optipop which uses the latest lean kernel.
Flashing twrp again did not fix for me, had to flash the latest factory image.
I have only noticed this after android 5.1 and only on grouper. Anyway, I was just wondering if others are running into this issue. Maybe we can figure out what going on.
I had the same issue when I fully reset the device, it wouldn't even load stock recovery. Flashing TWRP again solved my issue so I can't speak to why it would not flash for you.
Hello,
I have a lg g2 d800. I was trying to flash the latest cyanogenmod 13.0 snapshot. I was on cyanogenmod 12.1 the older june snapshot. I booted into recovery and stupidly did not make a backup because I am an idiot. I did a reset before I flashed the rom ( system, cache, dalvik). I flashed the rom and gapps and there were not any problems. I try to reboot the phone and it is just stuck in a boot loop. I have twrp installed. I can access twrp fine. I just need some tips on getting a different nightly or snapshot (I will probably use an older 12.1 snapshot) onto my phone to flash it.
Thanks in advance.