I compiled the official 4.0 kernel, packed it up with ramdisk and flashed it into my phone, but when I tried to boot it up, the red light kept on and nothing else happend. What's wrong with my kernel?
Related
i have a rooted thunderbolt with the mr2 radio running cyanogenmod 7 with its stock kernel. i have tried 2 times flashing a new kernel that is supposedly built for it. what i did was booted into recovery and used clockwork mod to flash the zip then rebooted. after that im stuck on the first white htc screen..... am i doing something wrong?
Did you check md5 sums? Possibly corrupt download? Maybe try downloading it again...
Hi Guys!
I'm posting here because I'm not yet allowed to post to developer's thread. I have a problem with my custom kernel on archos gen8 2.4.19.
Previously I've sucessfully compiled my custom kernel from gen8-gpl-froyo.tgz, flashed it and booted up.
With 2.4.19 Christian Ulrich made the rootfs and the zImage as always. I flashed it and it worked like a charm. After adding my zImage and reflashing it won't boot up.
I just changed the FTDI drivers to be compiled in the kernel.
I was wondered if something has changed or needs to be done in a different way...
Anybody else having the same issue?
The tablet boots to logo screen than flashes once as at every boot and after that the screen goes balck with backlit on...
br sodjas
whenever i flash a kernel over cm7 it always bootloopss help what am i doing wrong i always flash the cleaning script but it just gets stuck at the cyangoenmod screens
Hi i've got second rom but can't boot into it so i've checked in cwm status of second rom and i got this:
E:unknown volume for path /secondrom_system
I know that is work with siyah kernel but i'd like to keep current one from hydra rom. Siyah keeps it in .secondrom but even when i've changed it to secondrom_system it still doesn't work.Any solution?
I finally successfully built CM13 from source for higgs2g, but after install, I rebooted, it stucks on the splash screen 3 seconds, then reboots to recovery.. :/
I think the cause of that is the outdated kernel version (3.10.17, the only available kernel for SM-G350E), but how to build a new version of the kernel?
Thanks in advance