Boot loop after flashing CM9 until Semaphore kernel flashed - Galaxy S I9000 General

Can someone explain why this happens:
1. I flash CM9 nightly or latest release
2. Phone goes into boot loop
3. I power the phone up into the yellow boot loader screen and flash the Semaphore ICS kernel with Heimdall
4. The phone boots and runs OK
Why does the phone go into a boot loop until I flash the Semaphore kernel? How can I stop this behaviour?

Sounds like a big error... don't sound good. You flashing cm9 or cm10? nightly builds are really good. i recommend getting a cm10 nightly build and try that. otherwise, try and find a way of flashing roms and kernels a different way...

Related

Defy not booting after installing CM9

Hi! I just changed my rom from MIUI to CM9(ICS, 4.0.3) but after i install using recovery mod it stays on the booting screens and doesn't want to start normally. I noticed that clockwork mod has dissapeared and it will only show the "stock" recovery. Is there any chance to make my current rom work? or can I install another rom using the stock recovery?
Please help
Looks like i managed to make the phone work by full wiping from custom recovery. I'll definitely go back to CM 7.1...
kernel
i think u'll need to flash the cm9 kernel for CM9 work. otherwise flash the cm9 builds from Epsylon or Quarx - http://forum.xda-developers.com/showthread.php?t=1432100

Stuck after flashing kernel

Hello, i have a problem after flash ROM MS2Ginger 4, there are no problems but after flashing a kernel with RSD Lite, it's not boot to android..... Just when I power on phone i have yellow page with logo google and ms2ginger kernel and then black screen, nothing happens. Motorola recovery and bootloader works fine, but what i have to do to boot to system ?
I flash back to last GB kernel from MS2Ginger 4 threat and works fine, but what i have to do to boot with newer flash ?
Try to flash the kernel again, or try the previous version if you had tried the latest one. I had the same issue when the first time I flashed the custom kernel. And flashing the kernel again did help.

[Q] no so called safe kernels will boot

Ok so i want to put CM rom onto this S2 I have but trying to put a safe kernel on first so dont brick it with that wipe bug.
Problem is whenever I flash dream kernel, skfire etc. the device doesnt boot, only boots again when I flash cf-root back.
Its ICS 4.0.3
I am flashing via install frim zip file on CWM as instructions arent given on the kernel threads.
siyah flashed via odin, the logo appears very briefly at boot then black, nothing.
CWM with siyah logo in background works.
Ok I flashed cm9 now anyway.
It was confusing to me but incase anyone else is confused in the same way, cf-root is still safe as long as the stock isnt 4.0.4. I thought its possible cf-root used a 4.0.4 kernel on 4.0.3 and so was heistant.
I got no idea why none of the custom kernels would boot tho so that still has nme curious, CM has booted fine.

[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

Fastboot logo after flashing custom kernel

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.

Categories

Resources