Thadeu Lima de Souza Cascardo <[email protected]> writes: > On Sat, Jan 21, 2017 at 04:35:22PM +0000, Rodolfo Medina wrote: >> From Android root, I did: `ls -R /' and could read all - I think - the >> Android >> filesytem. I found busybox within /system/bin, but there doesn't seem to be >> any zImage. Besides, the only *.img file is: >> /system/etc/firmware/modem_1_wg_n.img. I ran extract-ikconfig on to it, but >> the output was: >> >> extract-ikconfig: Cannot find kernel config. >> >> . To continue going through the tutorial, I still need the following: >> >> 1) base system address, i.e. `where the RAM begins'; >> 2) zImage file; >> 3) what the author calls my-boot.img. > > As I said, try: > > adb ls /dev/block/platform/ > $XXX=directory_you_found_that_likely_ends_at_0 > adb ls /dev/block/platform/$XXX/ > adb dd if=/dev/block/platform/$XXX/boot | dd of=boot.img > file boot.img
$ adb ls /dev/block/platform/ 000041ed 00000050 58830898 . 000041ed 000001cc 58838bb7 .. 000041ed 0000003c 58838bb7 mtk-msdc.1 000041ed 00000104 58830761 mtk-msdc.0 $ adb ls /dev/block/platform/mtk-msdc.0 000041ed 00000104 58830761 . 000041ed 00000050 58830898 .. 0000a1ff 00000017 58830761 mmcblk0boot1 0000a1ff 00000017 58830761 mmcblk0boot0 0000a1ff 00000014 58830761 mmcblk0p7 0000a1ff 00000014 58830761 mmcblk0p6 0000a1ff 00000014 58830761 mmcblk0p5 0000a1ff 00000014 58830761 mmcblk0p4 0000a1ff 00000014 58830761 mmcblk0p3 0000a1ff 00000014 58830761 mmcblk0p2 0000a1ff 00000014 58830761 mmcblk0p1 000041ed 000000b4 58830761 by-num 0000a1ff 00000012 58830761 mmcblk0 Thanks, Rodolfo
