Its an asus zenfone 2, its just an generic x86 phablet with blinkboot instead of a full bios/uefi.
https://marketplace.windriver.com/index ... =76&cat=18i found it on the device at the mmcblk0boot0 partition.
the bootloader is unlocked so android custom kernels work.
I disassembled the second.bin file and it contains a function that jumps to the kernel entry point including strings for verbose booting.
Code:
aBootstubVersio db 'Bootstub Version: 1.4 ...',0Ah,0
db 'capfreq=',0
db 'Using bzImage to boot',0Ah,0
aJumpToKernel32 db 'Jump to kernel 32bit entry',0Ah,0
align 4
aFatalErrorTocS db 'FATAL ERROR: TOC size is too large for IMR',0Ah,0
aFatalErrorVxeF db 'FATAL ERROR: VXE FW image size is too large for IMR',0Ah,0
align 4
aFatalErrorSpsI db 'FATAL ERROR: SPS image size is too large for IMR',0Ah,0
align 4
aFatalErrorXenI db 'FATAL ERROR: Xen image size is too large for IMR',0Ah,0
align 4
aRelocatingInit db 'Relocating initramfs to high memory ...',0Ah,0
align 4
aWonTRelocateIn db 'Won',27h,'t relocate initramfs, are you in SLE?',0Ah,0
align 2
aUsingMultiboot db 'Using multiboot image to boot',0Ah,0
align 2
aBootstubSfi_ad db 'Bootstub: sfi_add_e820_entry failed',0Ah,0
align 4
aBootstubSfi_se db 'Bootstub: sfi_setup_mmap failed',0Ah,0
align 4
aBootstubSfiMma db 'Bootstub: SFI MMAP table not found',0Ah,0
aBootstubMapSfi db 'Bootstub: map SFI MMAP to e820 table',0Ah,0
align 4
I just need to know how to link a generic c/asm binary to a vmlinux bzImage to get the device in a mode where the vmem is already set up which is what the second.bin file seems to do.