Repacking successful but kernel doesn't boot

Question

Repacking successful but kernel doesn't boot

BlueMax opened this issue 9 years ago · 5 comments

Repacking this 5.1.1 kernel (without changing anything) works properly but it doesn't boot (just hangs at bootloader screen on Galaxy S4 LTE).

Any idea what's wrong?

Answer 1 · 2015-06-01T00:46:58.000Z

try:
cd $ramdisk; find . | fakeroot cpio -R 0:0 -H newc -o 2>/dev/null
| $zcommand > $unpacked_dir/new_ramdisk; cd $unpacked_dir
#$mkbootfs $ramdisk | $zcommand > new_ramdisk

Answer 2 · 2015-06-01T20:16:07.000Z

I guess uncommenting line 143/144 in current 'mkboot' will do the same. I can test it earliest in probably 24/48h on next kernel release. I had to temporarily fall back to older rom. Will report back as soon as possible.

Answer 3 · 2015-06-07T20:56:37.000Z

No, unfortunately still doesn't work.
Here is the source and here is the official thread on XDA. It says LZO compression for ramdisk & kernel.
'Last_kmesg' doesn't seem to be updated and i unfortunately don't have UART serial interface to get some early debug output.

Answer 4 · 2015-06-24T06:31:47.000Z

    cd $ramdisk; find . | fakeroot cpio -H newc -o 2>/dev/null \
        | $zcommand > $unpacked_dir/new_ramdisk; cd $unpacked_dir
    #$mkbootfs $ramdisk | $zcommand > new_ramdisk

@BlueMax

Answer 5 · 2015-06-24T18:01:38.000Z

👍
You were already right in the first place (2nd post). Stupid me hasn't noticed the comment sign at '#$mkbootfs $ramdisk | $zcommand > new_ramdisk' so previous line didn't have any effect indeed.
It does work properly now. I haven't tested your 2nd commandline with revised arguments yet. I guess its not necessary anymore.
Thank you very much and sorry for any inconvenience.