First flash this:
http://forum.xda-developers.com/lg-g3/development/kernel-optimized-sm-4-9-3-kernel-t2976049
I know what you're thinking, it says it's for d855 only...
What you do is immediately dirty flash your Rom afterwards, then gapps and voila, custom kernel goodness! Tested and working on validus and cm12
I'll add, before the dirty flash I had to attempt a boot which obviously didn't work. Then I bored into recovery, dirty flashed the Rom and gapps and I kept all the governors and tweaks.
Related
My Nexus 4 has been unable to flash most kernels without giving me a boot loop. I was on the Purity rom for a while and tried to flash Hellscore, Hellsdoctor, and Matr1x kernels but each would give me boot loops. However franco kernel flashed just fine. I then tried the Nexus 5 Experience rom with the CAF kernel packaged into the zip file and that flashed just fine. I now am trying C-Rom v5.6 and trying to flash the AK kernel v103 and it of course gives me a boot loop as well. I tried to flash Hellsdoctor to see if that would work, it did not. But franco kernel still flashed just fine for this rom as well. I did wipe data, cache, and dalvik and flashed the rom, then gapps, then the kernel. Unless I am missing something really stupid I do not understand why I cannot use most kernels. Any help would be greatly appreciated. Thanks!
SilentBlade27 said:
My Nexus 4 has been unable to flash most kernels without giving me a boot loop. I was on the Purity rom for a while and tried to flash Hellscore, Hellsdoctor, and Matr1x kernels but each would give me boot loops. However franco kernel flashed just fine. I then tried the Nexus 5 Experience rom with the CAF kernel packaged into the zip file and that flashed just fine. I now am trying C-Rom v5.6 and trying to flash the AK kernel v103 and it of course gives me a boot loop as well. I tried to flash Hellsdoctor to see if that would work, it did not. But franco kernel still flashed just fine for this rom as well. I did wipe data, cache, and dalvik and flashed the rom, then gapps, then the kernel. Unless I am missing something really stupid I do not understand why I cannot use most kernels. Any help would be greatly appreciated. Thanks!
Click to expand...
Click to collapse
i was on AOKP when i flashed franco and this happened... then i flashed FAUX123 and also happened.. but not the kernel with ROM....
until i figure out that most of those kernels only works on AOSP based kernels
Hello, I had some issues with my LG G2 while attemping to flash a new rom, here's my problem:
I checked for the latest crDroid 6.x rom and the gapps, everything went fine, I flashed the rom with no problems at all and then continued with the gapps. But here's the problem, when I tried to boot it, nothing popped out from the display, just the LG logo, then it was completely black. After trying to install another custom rom (cm 13 nightly), nothing happened. Then, I tried to go back to my AICP rom. I had to use ADB installer since I didn't have any zips avaiable, but when I tried to install tk gapps (downloaded from the AICP forum), Error code: 20 came out. I did a research, and this looks weird, because that error only pops when the gapps are not compatible with the current rom, but clearly they were. Any ideas on how to fix this up?
Avrammm said:
Hello, I had some issues with my LG G2 while attemping to flash a new rom, here's my problem:
I checked for the latest crDroid 6.x rom and the gapps, everything went fine, I flashed the rom with no problems at all and then continued with the gapps. But here's the problem, when I tried to boot it, nothing popped out from the display, just the LG logo, then it was completely black. After trying to install another custom rom (cm 13 nightly), nothing happened. Then, I tried to go back to my AICP rom. I had to use ADB installer since I didn't have any zips avaiable, but when I tried to install tk gapps (downloaded from the AICP forum), Error code: 20 came out. I did a research, and this looks weird, because that error only pops when the gapps are not compatible with the current rom, but clearly they were. Any ideas on how to fix this up?
Click to expand...
Click to collapse
for your rom to boot you need hybrid bootstacks
wipe all/flash hybrid/ go to main menu/ then reboot into recovery from recovery/ once in recovery again proceed to flash rom and gapps.
use the one for your variant
http://forum.xda-developers.com/lg-g2/development/boot-g2-hybrid-bootstacks-t3183219
I've had many roms flashed on my op2 through twrp, but now whenever i try to flash any rom(cm, exodus, aicp etc.) I get error 7. I tried deleting asserts line on "updater-script" but no luck...
Current rom: Resurrection remix 5.6.9
shahark86 said:
I've had many roms flashed on my op2 through twrp, but now whenever i try to flash any rom(cm, exodus, aicp etc.) I get error 7. I tried deleting asserts line on "updater-script" but no luck...
Current rom: Resurrection remix 5.6.9
Click to expand...
Click to collapse
Hi, If you already have twrp recovery and you can boot into twrp recovery, then you need to download stock oxygen os 2.2.1 ota.
when you download oxygen os 2.2.1 ota, flash it via twrp recovery, after that wipe factory data reset, then you flash your custom roms later. this will bypass the error 7 and you will have to resume enjoying your custom roms.
Here's what happens, when u totally erases the system, data, and formats everything with twrp recovery, custom roms don't run again, i think they kinda need some basic files from the stock rom to enable them to run. i experienced this myself with aicp and this is how i fixed it. so go on, look for the oxygen 2.2.1 ota.zip, download, flash, then wipe data fastory reset, then you can now have your custom roms flashed and working. again.
Right!! but oos 3.0 official is also working
shahark86 said:
I've had many roms flashed on my op2 through twrp, but now whenever i try to flash any rom(cm, exodus, aicp etc.) I get error 7. I tried deleting asserts line on "updater-script" but no luck...
Current rom: Resurrection remix 5.6.9
Click to expand...
Click to collapse
It's there to protect you from flashing a ROM incompatible with your current bootloader (there's two of them, pre oos3 and oos3 bootloader/fastboot).
So if you want to flash a ROM which is Lollipop (or using Lollipop bootloader like easier versions of Graraks and Seraph08s builds) you will have to restore your phone to oos2.x.x first. Same goes the other way around, and also your recovery system must be compatible with respective bootloader.
This info should be force-feeded to every noob checking in on this forum hoping for an easy swapping of ROMs on this phone, which is not gonna happen because of this.
I haven't unlock my phone yet. I used the qpst tool to flashed the rom to zui 0.9. Then I flashed the offical twrp.
Offical cm13, cm14 and some aosp rom(slim etc.) can boot and work well on my device after flashing, but cm based rom such as nuclearom and bliss cannot boot. They always stuck on the boot screen and fail to boot into desktop after a clear flashing. Have I missed something?
You have to unlock bootloader and do clean flash otherwise you may encounter such problems with custom roms
Everytime I try flashing custom kernel (Cherry Kernel or LOLZ) after rebooting I only see fastboot logo, the phone doesn't boot. I'm currently using Nusantara rom based on Android 12L, but this situation also has been happening on other roms. Can someone help me with this?
Edit: I am able to install LOLZ kernel, but only when clean flashing a rom, still not able to install it after already booting into the system. No luck installing Cherry Kernel either way tho.