[Q] [HELP]Best Kernel for CM12 - Nexus 4 Q&A, Help & Troubleshooting

I was using CM12 nightly with AK kernel. Everything was fine until my phone starts giving Error "SIM card registration failed". Initially i thought its some hardware fault but when i flashed Factory image it started working fine. But for me Stock ROM with stock kernel, mobile data and WIFI tethering is not working properly.
I am back to CM12 with default kernel. But now battery backup is horrible. Any suggestion which kernel should i use?
Even I am OK with stock ROM. Please suggest combination of ROM and Kernel? I am tired of flashing and flashing :crying::crying:

Related

[Q] Boot loops after flashing kernels

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

[Q] TWRP error: This package is for device: d800, g2

I'm on the AT&T D800 LG G2 on the stock ROM. Whenever I try to flash a new ROM it gives me that error. What do I do?
What I've done to get here:
Use my G2 for a good while (back in Q3 2013)
Install Mahdi 4.4 on it after taking a backup - everything's good.
Fast forward to today
Now I want to update it to 5.0+
After taking a backup I wiped the caches, data and system partitions while keeping the internal storage, where I keep the ROMs and backups.
Attempted to install Blisspop, CM12 or Resurrection Remix - Every one of those gave me that error. EXCEPT when I tried to update to a newer version of Mahdi. No problem at all. This leads me to think Mahdi has somehow managed to only allow Mahdi ROMs to be installed.
Found the old backup before I flashed Mahdi, restored that. Now I'm back on an ancient stock ROM. (D800 10d)
Attempting to flash a new 5.0+ ROM gives me the same error. What is going on?
I thought it was something Mahdi had changed in the build.prop file, so that's why I restored to this old version but it's still not working.
Made a duplicate thread by mistake - How do I delete this one?

Custom Kernal Not booting

I have a Galaxy note 4 SM- N910V, i just recently updated my bootloader to the CPD1. I rooted, installed TWRP, and CyanogenMod 13 beta. It works flawlessly, but ive always had an issue with bluetooth sound that was fixed when i installed a custom kernel on BPA1. Now that i am updated to CPD1, i installed CyanogenMod13, and the emotion kernel, But now my Phone wont boot pass the CyanogenMod logo at the beginning. I did wipe cache and dalvik after in installed the Kernel. Any help is greatly apprecieted.
Thanks,
Deershoot3r
EDIT: Also i forgot to mention, i did a clean restore in odin, rooted, reflashed twrp. But this time i installed the Emotion Kernel first, THEN installed CyanogenMod/Gapps, and it booted perfectly BUT in settings my kernel doesnt say emotion it says "3.10.40-ga6f06c0 [email protected] #1"
When you flashed the kernel, then the ROM, the ROM overwrote (not sure what you think you installed the kernel to if the OS wasn't there?) the kernel, is my guess.
In any case, it simply sounds like you don't have a compatible kernel for the ROM. Ensure you have a kernel that's compatible with the ROM and your hardware.

trying to flash frank kernal --> bootloop

Alright, so I'm thinking my problem was that i initially had supersu installed when attempting to install this kernel, and thus causing that bootloop.
Can anyone provide insight as to whether this is true. I had a nandroid backup of my stock rom and even though I "restored" it, it was still stuck in bootloop regardless :/. I don't want to keep restarting and reinstalling everything over and over without knowing what the problem is.
I currently run Resurrection Remix with xposed. I'm fearing if I make another nandroid backup for this and try to flash the rom again, it won't work and I have to start again.
FYI: I was on RR when I attempted the kernel install.
Try downloading the kernel again and dirty flash it. If that doesn't work try dirty flashing some other kernel. And if that doesn't work dirty flash your rr rom. And if still not working then restore your backup
billamin said:
Try downloading the kernel again and dirty flash it. If that doesn't work try dirty flashing some other kernel. And if that doesn't work dirty flash your rr rom. And if still not working then restore your backup
Click to expand...
Click to collapse
well what i did was following:
round 1. RR rom already installed
wipe cache and delvik, install kernal, bootloop
attempt to restore nandroid., still bootloop,
attempt 2:
wipe everything and install RR, SU, Gapps
did setup
installed franko r25
attempt 3.
wipe and factory reset
restore nandroid
bootloop
attempt 4
DONT install franco and install ak. after everything
works
Franco kernel needs to be installed twice to work. flash kernel, dont restart, just flash again
feis said:
Franco kernel needs to be installed twice to work. flash kernel, dont restart, just flash again
Click to expand...
Click to collapse
omg thanks! that worked perfectly. Now a new problem is specifically when I'm using tugapower, while typing on my swiftkey into the xda forum. I'm noticing a lag. I've made it so then both apps are operating on performance with franco. Not sure what's causing the lag. Is it possibly the theme?
Dunno whats the problem, but im pretty sure if you just flashed franco, didnt change anything and used those apps, they wouldnt lag
didn't figure out what caused the lag but its gone now

No communication working on Custom ROMs, No wi-fi, bluetooth, SIM signal, IEMI etc.

I was using Nougat 7.0 Android Ice Cold Project (AICP) -12.0 was working well,
Made complete backup of this ROM/OS then booted from backup, Stuck on boot up screen, then did a clean flash of
this ROM again stuck at finally boot screen,
Then flashed ED300 CM13 MM but found no communication devices working, There might b kernel issue, I don't know.
Now I'm able to flash and use all other custom MM and LP ROMs except Nougat 7.0 and all having No communication means
no wi-fi, bluetooth, SIM card detection and signal, IEMI etc
I'm using Lenovo A6000 8GB.
Tried to install terminal emulator to change SIMs IEMI using thread by #zround, but was not able to do so bcz unknown source blocked and not working.
Setting not working and crashing,
I just needed Wi-Fi to work at least now.
Could anyone help or provide flashable kernel or firmware to fix these issues?
Or anything to revert back communication modem, or On stock ROM from recovery, Or stock recovery.
Fixed by myself. Flashed stock ROM which failed but patched the firmware
And efs, then without wiping data, dalvik cache/cache dirty flashed MM ROM and found everything working properly again.

Categories

Resources