You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some Android bootloaders start with BOOTLDR! and contain other images used in the boot process. The format is pretty straightforward, and at least on modern Qualcomm devices, the images contained are just strings (e.g. version strings) or ELF images.
Currently, Binwalk may find the ELFs by magic, but may not extract them perfectly -- and may extract internal resources separately (rather than in a second stage of recursion).
Which has the ability to extract the names of the partitions, as well as their contents. Hopefully you can integrate this into BinWalk :)
You can get example images by downloading a Google Pixel (or Nexus) factory image ZIP from here and looking at the bootloader .img file (e.g. walleye-opd3.170816.012/bootloader-walleye-mw8998-002.0059.00.img).
For that image, my script will generate the following output (contents truncated to be reasonable), which should hopefully be easy to integrate into Binwalk.
Some Android bootloaders start with
BOOTLDR!
and contain other images used in the boot process. The format is pretty straightforward, and at least on modern Qualcomm devices, the images contained are just strings (e.g. version strings) or ELF images.Currently, Binwalk may find the ELFs by magic, but may not extract them perfectly -- and may extract internal resources separately (rather than in a second stage of recursion).
I've written an extremely simple parser in ctypes here: https://gist.github.com/zachriggle/4d78433cd93dbb8fb0858dc7a98e0d5e
Which has the ability to extract the names of the partitions, as well as their contents. Hopefully you can integrate this into BinWalk :)
You can get example images by downloading a Google Pixel (or Nexus) factory image ZIP from here and looking at the bootloader
.img
file (e.g.walleye-opd3.170816.012/bootloader-walleye-mw8998-002.0059.00.img
).For that image, my script will generate the following output (contents truncated to be reasonable), which should hopefully be easy to integrate into Binwalk.
The text was updated successfully, but these errors were encountered: