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.
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
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:
EDIT: the problem is solved, see my last post
Hey guys,
I'm not new to installing roms, as I did with my SGS 2 before. But I haven't done it for a long time and it's the first time I do it on my SGS 5... with no success at all.
The problem is that, out of all the roms I've tried, none of them boot up entirely without crashes. I've followed the instructions to the letter and I'm not sure what I'm doing wrong.
Here's what I had before starting to fiddle:
SGS 5 G900F, no specific carrier, bought in Europe
stock android/touchwiz 5.0, never rooted or anything
Here are the roms I have tried:
cynaogen 5.1.1 12.1 20150508 for klte + these gapps http://teambliss.x10host.com/BlissStalk/Gapps/ --> stays blocked on the samsung logo forever
BlissPop 5.1.1 v3.3 20150515 for klte + pa_gapps-stock-5.1-20150418-signed or pa_gapps-modular-full-5.1-20150418-signed --> google newstand and another google app are crashing in a loop during the setup, I can't tap any button
PAC 5.1.1 20150503 for klte + pa_gapps-stock-5.1-20150418-signed or pa_gapps-modular-full-5.1-20150418-signed --> the install wizard application itself is crashing in a loop
THe kernels I've tried:
KT-SGS5-LP5.1-AOSP-G900-05.02.2015
boeffla-kernel-2.0-beta8-CM12.1-g900f.recovery
My recovery:
twrp-2.8.6.0-klte (flashed with Odin, it works fine, and I could boot the stock rom without problems with it)
Any idea about the cause of the problem?
Thanks
I guess if you are not new to stuff like this, you have 100% wiped everything before flashing in TWRP recovery, and factory reset / wiped caches after flashing the ROM and Gapps?
*Detection* said:
I guess if you are not new to stuff like this, you have 100% wiped everything before flashing in TWRP recovery, and factory reset / wiped caches after flashing the ROM and Gapps?
Click to expand...
Click to collapse
Yes, before and between installing different roms, I wiped everything: system, cache, dalvik, internal storage
I've also flashed twrp previous version 2.8.5.0, and philz touch recovery. They all work fine, but still can't boot any rom
Strangely, I now works using this version of CM 12.1: http://forum.xda-developers.com/gal...ent/rom-cyanogenmod-12-1-android-5-1-t3066252
I have no idea why I had all these crashes and boot problems with the other 3 roms.
Cheers
Odd.
Hey guys,
I have a little problem with my new OP2.
I unlocked the bootloader and rooted etc.
I installed Paranoid Android and I wanst sure which kernel works on it.
So I tried flashing one for CM13 and one for OOS3, but both of them wouldnt work.
Now Im trying to get back to stock or atleast flash the boot.img from the Paranoid ROM.
I can boot, access the recovery and bootloader. I flashed different boot.imgs (Stock and Paranoid) and recoverys. But none of them helped.
The touchscreen wont react at all. If I boot, if I am in the recovery. It just wont work. Hardware button seems to be fine though.
Any ideas how to fix that?
Try wiping system partition and flash the PA ROM again (and Gapps of course) and it will restore system and kernel back to PA default.
If touch still doesn't work, then you'll probably have to wipe userdata partition as something you installed with the kernels not supporting other than official latest CM13 sources is messing with your system.
You need to flash full stock using fastboot from unbrick guide.
Sent from my ONE A2005 using Tapatalk
google megaunbrick guide oneplus2 and follow that!
didn't got your logic behind flashing custom kernel that too on paranoid android, I can understand that for cm13 as the battery life sucks there but pa easily gives 6+ hrs of sot which any other rom or even a custom kernel can't even come closer to it in my personal experience.
meaning you can try to flash the whole rom through fast boot or use unbrick guide to go full stock.
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