[Moto G Android Development] yvodelaere:
Using android kitchen

---------- Post added at 07:12 PM ---------- Previous post was at 06:57 PM ----------

Boot image tools

----------------

Enter a choice:

s = Show boot.img information

w = Extract kernel+ramdisk from boot.img

c = Convert boot.img into NAND boot folder

p = Change 'command line' parameter in boot.img

a = Extract kernel+ramdisk from boot.img/recovery.img in any folder

x = Exit

NOTE: Other options may not be shown in this menu *until* a specific

action above is selected or a specific working folder is created.

(A working folder is created with Option 1 of the kitchen main menu!)

e.g. You won't see the option to re-pack a boot.img unless you unpack

the boot.img first! For re-packing you also need a working folder

with the original boot.img so that the kitchen can use its header

information to construct the new boot.img.

? w

Working folder found

Kernel found at offset 2048 in boot.img

Making folder BOOT-EXTRACTED ...

Extracting kernel ...

Extracting ramdisk ...

Press Enter to continue

Boot image tools

----------------

Enter a choice:

s = Show boot.img information

b = Build boot.img from BOOT-EXTRACTED folder (for working folder)

n = Build NAND's boot folder from BOOT-EXTRACTED (for working folder)

r = Remove BOOT-EXTRACTED folder (don't build anything)

a = Extract kernel+ramdisk from boot.img/recovery.img in any folder

x = Exit

NOTE: Other options may not be shown in this menu *until* a specific

action above is selected or a specific working folder is created.

(A working folder is created with Option 1 of the kitchen main menu!)

e.g. You won't see the option to re-pack a boot.img unless you unpack

the boot.img first! For re-packing you also need a working folder

with the original boot.img so that the kitchen can use its header

information to construct the new boot.img.

? b

---------------------------------------------------------------

Ensure your BOOT-EXTRACTED folder has the kernel and ramdisk

files that you need.

Kernel = zImage (sometimes referred to as boot.img-kernel)

Ramdisk = boot.img-ramdisk folder

---------------------------------------------------------------

These files will be re-packed into a boot.img that will be

copied to your current working folder.

---------------------------------------------------------------

<Press ENTER>

Found BOOT-EXTRACTED folder, checking contents ...

Found boot.img-ramdisk

Found zImage

Working folder found

Kernel found at offset 2048 in boot.img

Compiling mkbootfs ...

mkbootfs successfully compiled

Compiling mkbootimg ...

mkbootimg successfully compiled

Creating ramdisk cpio archive ...

Attempting to determine kernel base address ...

Using base address of 0x00000000

Using ramdisk load address of 0x01000000

Attempting to determine command line parameter ...

Using cmdline: console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x37 vmalloc=400M utags.blkdev=/dev/block/platform/msm_sdcc.1/by-name/utags androidboot.write_protect=0 zcache androidboot.selinux=permissive

Building new boot.img ...

newBoot.img created

Moving to working folder as boot.img

boot.img size

Old: 6.0M

New: 5.0M

Removing BOOT-EXTRACTED folder ...

Press Enter to continue

This is when just unpacking and repacking the boot.img.

What comes out is a boot.img which falls direct into bootloader