Mkbootimg -kernel zImage -ramdisk -base 0x0 -cmdline 'otg_device=1 buildvariant=userdebug' -o new_boot.imgĬode: Select all adrianp BR odroidn2-4.9.y-android ~ | development | linux 1 0 diff -u. Please modify mkbootimg.c using the above values to build your image.Įxtracting root filesystem to file. This image is built using NON-standard mkbootimg! Unmkbootimg version 1.2 - Mikael Q Kuisma Ĭommand line "otg_device=1 buildvariant=userdebug" I extracted the kernel, dtb from their partitions and they look ok:īoot.img: Android bootimg, kernel (0x1080000), ramdisk (0x1000000), page size: 2048, cmdline (otg_device=1 buildvariant=userdebug)ĭtbs.img: Device Tree Blob version 17, size=74368, boot CPU=0, string block size=7632, DT structure block size=66680ĬMDLINE: 'otg_device=1 buildvariant=userdebug' with dd from android directly or offline with dd + offset) and copy over the modules. So my plan is - compile the new kernel (ideally on a c2, but I can do it on a pc if I must), dd the new kernel (is it in Image format?) and dtb to their partitions (e.g. Bytes is too small, so it's probably blocks. I'm not sure what size/offset are measured in. Code: Select all meson-mmc: mmc read partition OK!
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |