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
Related
Hi
for my assignment in university i need to build a custom kernel. su/busybox worked fine so far, but i'm stuck with clockworkmod. i can boot fine into recovery, but the OS boot is stuck in the bootanimation (without sound btw) and logcat isn't really helpful.
what i've done so far:
when i got the device i flashed the latest stock ROM i found (XWKJ2), got temp root with ZergRush and pushed the latest SU binary. i unpacked the initramfs from the stock kernel, repacked and flashed it for testing purposes, which worked. i got the CWM zip (4.0.1.5) for the S2, extracted into the initramfs and repack/flashed. now CWM seems to work fine, but if i want to start android it is stuck in a bootloop while waiting for media.player (says logcat).
Now i downloaded https://github.com/teamhacksung/clockworkmod_galaxys2_initramfs
from codeworkx and it obiously worked fine, but i'm not so sure what the difference is besides busybox. also i don't get how changing the recovery binary will affect the boot process. any pointers on how to resolve this issue would be nice. maybe even codeworkx himself :/
will provide more info/logs/sources if needed.
I am currently running mini cm2.2.1 atop naa's kernel.
i would like to know how to change the boot image which the kernel shows while booting up.
( the naa written when the phone boots up)
( sorry for the mistake in title, noticed it late)
Hi there!
Some days ago decided to have a go at building my own Kernel.
Followed the various guides, howto's and repos by most eminent people in here.
Downloaded latest SE sources for Mini Pro.
Tried with Linaro. Sources needed to be modified to compile (some attributes were duplicated)
Tried with Code Sourcery toolchain. No luck.
Finally settled for Google toolchain. Kernel compiles.
Added bunch of governors, couple IO schedulers, thanks to examples by DooMLoRD and others.
Now, I'm trying to include CWM in it, with the "keydown" trick.
Checked ramdisks in Panic Kernel & Mesa Kernel to find an hint.
Tried both their approaches, compiled my own CWM...
The kernel doesn't want to start CWM. It hangs when trying or reboots (depends on approach, /init vs /sbin/recovery &)
Now, kernel and CWM weren't compiled using same toolchain...
Does anyone know the secret trick? Secret procedure?
Thanks,
Ka.
I'll reply to my own question, to bore everybody or to help someone that might be in the same case.
There was actually nothing wrong with my CWM Recovery build. I checked more carefully how CWM did it.
CWM, in the joint ramdisk, uses a script to be triggered before /system/sbin/chargemon in init.semc.rc (a trick also used by many others).
Instead of carrying two ramdisks and laying out first the "Normal boot" one, cleaning up and laying out the "Recovery one" before Recovery is launched, it simply carries everything needed in one single Ramdisk.
When Recovery is invoked (either by pressing a button or rebooting into recovery), it does a little "cleanup" and finally calls /sbin/recovery&.
Just make sure the CWM Recovery resources (images in /res/images) are present and "voila", CWM Recovery starts and works.
Now I'm closer to publish my own kernel brew
Thanks,
Ka.
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?
Hi, recently I Flashed my iconia a500 with cm10 jelly bean 4.1.2 bootloader v8. After one weel of awesome performance my tab is now dead, when I try to reboot it is stopping at the first screen from the bootloader without charging the os. In the recovery menu everithing is working perfect but when I try to reboot is always showing me the same : "skrilax_cz's bootloader v8 booting primary kernel image".
Could please some body help me?
Thanks!
momotizzati said:
Hi, recently I Flashed my iconia a500 with cm10 jelly bean 4.1.2 bootloader v8. After one weel of awesome performance my tab is now dead, when I try to reboot it is stopping at the first screen from the bootloader without charging the os. In the recovery menu everithing is working perfect but when I try to reboot is always showing me the same : "skrilax_cz's bootloader v8 booting primary kernel image".
Could please some body help me?
Thanks!
Click to expand...
Click to collapse
Something is wrong with the kernel boot in your setup. It can be anything, for example a weird looping script in init.d, corruption in the kernel partitin, whatever.
What I would do (I have a Iconia a500 in my household that I don't actively flash anymore) is the nuclear option: boot to recovery, wipe everything and reflash the rom. Maybe also refash the kernel if that isn't in the rom zip.
Zatta said:
Something is wrong with the kernel boot in your setup. It can be anything, for example a weird looping script in init.d, corruption in the kernel partitin, whatever.
What I would do (I have a Iconia a500 in my household that I don't actively flash anymore) is the nuclear option: boot to recovery, wipe everything and reflash the rom. Maybe also refash the kernel if that isn't in the rom zip.
Click to expand...
Click to collapse
HI Zatta, I reflashed different time some different rom and kernel but the result is not changing, I'm still in front of the starting screen but the rom is not charged. Any other suggestion? If I try to flash a new bootloader with nvflash is stop at the half of the procedure. Also if I try to restore an hold backup is not working. How can I fully restore the tab?
Ohoh, what made you think the bootloader was the problem?
Anyway, if you can boot to recovery, use that. Else, browse the forum to find help, for example in this thread :
http://forum.xda-developers.com/showthread.php?p=28777415
Taptalked u see .. əəs n pəʞlɐʇdɐʇ
I tried to reflash bootloader different time but no way. Now the Tab is start always/just in apx mode.
Any suggestion for a full reset or restore from apx mode?
You ****ed something up. Anyway, if your really can't boot into recovery anymore, follow this guide:
http://forum.xda-developers.com/showthread.php?t=1622425
and do the manual method. I hope you have saved you CPUID and SBK somewhere.. Further questions can better be asked in that thread also as I am not fully involved in that device anymore.