Issue "Dumping & unpacking original boot image"

[ghost]

Device:

HTC One M8 with a Google Play Edition ROM (Marshmallow)

OS version (KitKat/Lollipop/Marshmallow/Nougat):

Marshmallow

Built from repo (date and build command) or downloaded from website (links):

https://github.com/lavanoid/M8GPE_Kali

Output of cat /proc/version in adb shell or NetHunter Terminal:

Linux version 3.4.0-g2830778 (throwback@QuadCore-SSD-BuildBox) (gcc version 4.9.4 20150629 (prerelease) (crosstool-NG 1.20.0 - Linaro GCC 2015.06 - Cortex-A15) ) #1 SMP PREEMPT Fri Jan 22 12:05:35 EST 2016

Issue:

Cannot dump and unpack the original boot image.

[ghost]

I manually ran the bootimg command via ADB and this was the error it was throwing out.

[jcadduono]

Looks like something really changed in the libc of Android that the TWRP was built in.
Option one is to ship with dynamic binaries for both versions of libc and check libc version to set the right bin dir in installer, option two would be to ship with our own libc.so and link it from the installer, option 3 would be to build all of our binaries static and not rely on any linkers.

[ghost]

I tried downgrading my recovery to the same version as on my One M7 (A known working version of TWRP, 2.8.7.0) and the issue still persists, so downgrading my recovery for the sake of testing my Kali NH M8 port didn't help.

So I guess any one of your suggestions should suffice 🦊

[ghost]

bump

[0xXA]

Looks like something really changed in the libc of Android that the TWRP was built in.
Option one is to ship with dynamic binaries for both versions of libc and check libc version to set the right bin dir in installer, option two would be to ship with our own libc.so and link it from the installer, option 3 would be to build all of our binaries static and not rely on any linkers.

Static in case is a good choice not sure though

[jcadduono]

I'd prefer to ship with our own libc and linker for each arch to keep the size small by continuing to use dynamic binaries but I don't have the time to work on this.

[ghost]

Is there the possibility of us compiling lazyflasher ourselves? I've been wanting to port Kali NH to the One M8 for months now, and this has been holding me back. Any work around so I can test Kali NH would be cool.

[jcadduono]

any better luck with the new binaries uploaded in latest commits?

[ghost]

YAY! That worked! No issues here. Thank you, my man!

[jcadduono]

i'm gonna try and get instructions on compiling the tools written sometime, may take a while though
the gist of it is to:

apt-get install repo openjdk-8-jdk build-essential
mkdir ~/build
cd ~/build
git clone --depth 10 https://github.com/offensive-security/kali-nethunter.git
mkdir twrp
cd twrp
repo init --depth=1 -u git://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni.git -b twrp-7.1
wget https://puu.sh/Degll/427fb93c46.sh -O build_nethunter_tools.sh
chmod +x build_nethunter_tools.sh
mkdir -p .repo/local_manifests
wget https://puu.sh/DegpE/21ed2a7f7e.sh -O .repo/local_manifests/nethunter-tools.xml
repo sync -j20

from there everything should be set up, and you can just run ./build_nethunter_tools.sh and it will compile for all arches and place them in ~/build/kali-nethunter/nethunter-installer....

you may or may not need more android build dependencies