[Galaxy S II Android Development] ol1ver:
@rINanDO your current HEAD of your kernel repo is not the one in use right? As there are some things in that don't seem to work (causing init exit errors)

e.g. `busybox cd /` doesn't make sense, `cd` is a shell built in, so doesn't need busybox prefixed. Also `exec >>boot.txt` I don't even know what's that supposed to do, as `exec` normally swappes out the current process (and pid) with the new process, but no process is listed there ...

edit: must be fine though; because that part of the script was not touched for almost 10 years, and now with everything fixed it's working ...

I managed to compile and run a shell however :) I did use alpine's latest static busybox, because the 2010 android one lacks some stuff. I'll actually be cleaning the init up a bit, and want to enable some more features (you can call it isorec2 :p) as the latest twrp's don't work anymore due to size, so want to change that too, to either squashfs and/or to xz.

Anyway, I've run out of all options on trying to fix my lost partition, dd-ing it now to a microSD card to see if I can recover some files (you'll see it'll turn out to be nothing of value there :p) and then mkfs.ext4 it. I think f2fs is a great FS and is super stable, but not on the 3.0 kernel series ...

edit: So i finally have everything working again :) after re-installing the ROM, i got the kernel that's part of the build back, and with everything wiped, it should all be perfect.

However, for whatever reason, I keep having the serial console enabled (with a pop up from android) and it's all really slow (probably caused by the console).

I do see

[ 0.000000] c0 Linux version 3.0.101-lineage-g24b4dc225265 (nobody@android-build) (gcc version 4.9.x 20150123 (prerelease)
i9100:/ # cat /proc/cmdline
console=ttySAC2,115200 consoleblank=0 androidboot.hardware=smdk4210 loglevel=3 console=ram androidboot.serialno=0009e7990bcc4f sec_debug.enable=0 sec_debug.enable_user=0 c1_watchdog.sec_pet=5 sec_log=0x100000@0x4d900000 s3cfb.bootloaderfb=0x5ec00000 ld9040.get_lcdtype=0x2 consoleblank=0 lpj=3981312 vmalloc=144m

hah, actually console is set twice, once as per bootloader, and once from somewhere else. So is this something that needs to be fixed? I do notice quote some choppiness and slowness ... probably turning off animations might help significantly ...

btw, doing a strings om PARAM (/dev/block/mmcblk0p4) I do see something resembling the SBL environment ...

I9000XXIL
loglevel=3 console=ram
/ttySAC2,115200

(I did set the loglevel lower) but console, as you can see is set to ram ... I'll tripple check to make sure, but i'm very certain i did set things up properly, maybe I should put some garbage in the CMDLINE first to ensure it's properly wiped/empty and that I see is just some left-over stuff.

Here's the env;

SBL> printenv
PARAM Rev 1.3
SERIAL_SPEED : 7
LOAD_RAMDISK : 0
BOOT_DELAY : 0
LCD_LEVEL : 50
SWITCH_SEL : 1
PHONE_DEBUG_ON : 0
LCD_DIM_LEVEL : 1
LCD_DIM_TIME : 6
MELODY_MODE : 1
REBOOT_MODE : 0
NATION_SEL : 0
LANGUAGE_SEL : 0
SET_DEFAULT_PARAM : 0
FLASH_LOCK_STATUS : 0
PARAM_INT_14 : 0
VERSION : I9000XXIL
CMDLINE : loglevel=3 console=ram
DELTA_LOCATION : /mnt/rsv
PARAM_STR_3 :
PARAM_STR_4 :
SBL> setenv BOOT_DELAY 1

So is there anywhere in the ROM that sets the console to something else? I cannot find it in your kernel img and I doubt its in the boot.cpio ...