[Q] Unable to re-compile boot.img

Search This thread

shanmukhateja

Member
Jan 30, 2013
34
8
Secunderabad
Hello everyone, I have been trying to decompile boot.img and re-pack it without modifying anything. I have the boot.img from the cm11-nightly zip file. It turns out that size of the new_boot.img file I compile is not equal to that of the original boot.img I used to decompile.
The original boot.img file is 6.0MB whereas the new_boot.img I compile is at 4.7MB
My mobile is XT1022 [Indian Dual SIM variant] and I'm on CM11-Nightly-7 by percy_g2

The tools I used:
http://xdaforums.com/showthread.php?t=2319018
https://github.com/newhor1z0n/mkboot-tools-condor

The command I issued to compile:
./mkbootimg --kernel boot.img-zImage --ramdisk boot.img-ramdisk.gz --pagesize 2048 --base 0x00000000 --cmdline 'console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x37 utags.blkdev=/dev/block/platform/msm_sdcc.1/by-name/utags vmalloc=400M androidboot.write_protect=0' -o new_boot.img

I have checked whether if the command I am issuing are wrong but NO they are correct.
Can someone help out here!

UPDATE: By changing the compiling command to:
mkbootimg --kernel boot.img-dt --ramdisk boot.img-ramdisk.gz --second boot.img-zImage --pagesize 2048 --base 0x00000000 --cmdline 'console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x37 utags.blkdev=/dev/block/platform/msm_sdcc.1/by-name/utags vmalloc=400M androidboot.write_protect=0' -o finalboot.img

improved the condition a little bit and now the mobile flashes the Motorola Logo kinda like; I power on the phone, it shows the M Logo and then a black screen appears and again the M Logo appears. I am stuck in this bootloop for a while. Anyone, can you help me regarding this??
 
Last edited:

shanmukhateja

Member
Jan 30, 2013
34
8
Secunderabad
Problem solved

I have solved the problem by using another mkbootimg from "https://github.com/goutamniwas/android_kernel_motorola_msm8610"

The final command I used to re-compile is:
mkbootimg --kernel boot.img-zImage --ramdisk boot.img-ramdisk.gz --dt boot.img-dt --pagesize 2048 --base 0x00000000 --cmdline 'console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x37 utags.blkdev=/dev/block/platform/msm_sdcc.1/by-name/utags vmalloc=400M androidboot.write_protect=0' -o finalboot.img :laugh:
 
  • Like
Reactions: rajit and kailashrs

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    Problem solved

    I have solved the problem by using another mkbootimg from "https://github.com/goutamniwas/android_kernel_motorola_msm8610"

    The final command I used to re-compile is:
    mkbootimg --kernel boot.img-zImage --ramdisk boot.img-ramdisk.gz --dt boot.img-dt --pagesize 2048 --base 0x00000000 --cmdline 'console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x37 utags.blkdev=/dev/block/platform/msm_sdcc.1/by-name/utags vmalloc=400M androidboot.write_protect=0' -o finalboot.img :laugh: