search

xiaolu / mkbootimg_tools

Unpack and repack boot.img,support dtb(dt.img).
530 stars 365 forks source link

Repacking successful but kernel doesn't boot #10

Closed BlueMax closed 9 years ago

BlueMax commented 9 years ago

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?

xiaolu commented 9 years ago

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

BlueMax commented 9 years ago

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.

BlueMax commented 9 years ago

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.

xiaolu commented 9 years ago 
    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

BlueMax commented 9 years ago

:+1: 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.