I flashed black reactor kernel v5 over percy cm#2 and now it has been stuck to tis boot splash for about 15 mins, I was on minirom touchwiz ux inspired.
now it enters recovey but cannot enter system it self< any help to fix this???
PS : suggest solution doesnt contain odin and PC
1 - flash previous kernel (percy cm#2)
2- flash a different kernel compatible with your rom (stock kernels for stock based roms & cm kernels for cm roms)
3- format system data cache mount system data cache & flash a rom compatible with installed kernel
Note if you were on percys #2 you will need a kernel that supports ext4 system partitions
if using stock based roms use hells fusion #50
if using cm7 roms use percys #2
both support ext4 system partitions
Related
Hi, I'm currently running stock rooted 4.22 rom and franco kernel r134 with ClockWork Recovery and I want to flash the ParanoidAndroid, what should I do? Should I just download PA and GAPPS, flash it with factory reset, dalvik and cache, and I will still have my franco kernel? Or should I flash kernel reset first and then flash PA?
When you flash the Rom you will lose the kernel and it will install the one included with the Rom if you want Franco kernel back you have to refresh it.
Flash ROM gapps Franco kernel and reboot done
Sent from my Nexus 4
I'm currently running CM10.2 by Engle_Mars but I would like to try MS2Ginger 5. ( http://forum.xda-developers.com/showthread.php?t=1931968 )
I've read the thread but can't really find some concrete information as to the installation steps. Do I need to install both the rom and the kernel listed in that thread?
I have the latest kernel: SPKernelR6+UP.7z (16.05 - New Revision! <Rev6>) and the v5 Rom.
In cm10.2 Do I just reboot to recovery, install the kernel, install the rom, wipe data/cache, reboot?
Thanks.
norgar00 said:
I'm currently running CM10.2 by Engle_Mars but I would like to try MS2Ginger 5. ( http://forum.xda-developers.com/showthread.php?t=1931968 )
I've read the thread but can't really find some concrete information as to the installation steps. Do I need to install both the rom and the kernel listed in that thread?
I have the latest kernel: SPKernelR6+UP.7z (16.05 - New Revision! <Rev6>) and the v5 Rom.
In cm10.2 Do I just reboot to recovery, install the kernel, install the rom, wipe data/cache, reboot?
Thanks.
Click to expand...
Click to collapse
You dont need to install kernel from MSGinger thread. It is working with stock one without any problem
0. Extract rom to /sdcard/clockworkmod/backup
1. you must format data and cache to ext3 - you can do that from bootmenu
2. boot to recovery and flash this recovery: http://www.mediafire.com/?i1rcie7tf4y6rmu
because CM10.2 has TWRP recovery and it cant recover CWM nandroid backups
3. Boot to CWM based Recovery.
4. Restore the ROM.
5. Reboot , boot again to CWM
6. Now Wipe Data & Cache.
Thank you!
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 am on carbon rom converted to full-f2fs.When i am flashing AK kernel v255 it gets stuck on boot animation.Then i have to flash Hells doctor r11 which boots perfectly.Also if i flash AK kernel,when i try to wipe cache and dalvik cache in TWRP recovery,it gets stuck on 'wiping dalvik cache''.Recently hells doctor has f2fs fixes.i have also tried AK's v254.same thing happens.Can AK look into it
avinab said:
I am on carbon rom converted to full-f2fs.When i am flashing AK kernel v255 it gets stuck on boot animation.Then i have to flash Hells doctor r11 which boots perfectly.Also if i flash AK kernel,when i try to wipe cache and dalvik cache in TWRP recovery,it gets stuck on 'wiping dalvik cache''.Recently hells doctor has f2fs fixes.i have also tried AK's v254.same thing happens.Can AK look into it
Click to expand...
Click to collapse
Post your comments in AK's forum thread that way the right people can get the bug fixed.
Ive run into a problem and need some help.
im running stock 5.0 with multi-boot and have autodroid 1.2 as a secondary rom for nethunter.
all was running well untill i used the "flash image gui" while booted into autodroid to flash the m4xx3dout .img
now my internal 5.0 rom will not boot it just loops at the circular-wavy-dots lol, i can still boot autdroid however. so still have access to storage and all my data (thanks multi-boot). autodroid rom is still showing as kangaroo kernel.
ive tried flashing the kexec_50_final zip in the "flash img gui app as well as in multiboot recovery to no avail.
any ideas?
No one?