Discover the internal workings of android bootstrap. find out how to reveal and modify a boot image.. On android systems the kernel, the ramdisk, and some metadata are stored in a binary disk image that's handled by the bootloader. images are built with the mkbootimg utility. examining the mkbootimg. This article shows how to split a boot.img file into kernel and ramdisk parts. in android systems kernel and initial ramdisk filesystem are usually joined into an only file, named boot.img, and flashed into the device. recover image files have same structure too. mkbootimg is the tool which builds a boot.img file from its kernel and ramdisk parts..
This is not android with chroot, but a full-blown debian installation. all android stuff including recovery is wiped. hint: this firmware may work on other mt6589-based devices with at least 4gib emmc.. Also, another way of looking at it is this, and this is dependent on the android version - the usb otg functionality is fully brought up within the android environment, i.e when the familiar home screen appears, then otg's functionality is enabled. unfortunately not the case when looking at it from lk's perspective.. An obvious difference in your two hexdumps is the word stored starting 20 bytes into the image - 0x81200000 in yours vs 0x81700000 in the original - this stands out because 0x20 is a space while 0x70 is a printable "p" appearing in the right column..
