32-bit binaries causing issues on 64-bit only devices

[ep1cman]

The following binaries are shipped as 32-bit:

• e2fsck
• mke2fs
• pkgdetails
• qemu-i386-static (Not sure this one matters)

This means the creation of the loopback img and installation fail on devices that cannot execute 32-bit (e.g Samsung S24 series)

[gitmanbloggus]

The following binaries are shipped as 32-bit:

• e2fsck
• mke2fs
• pkgdetails
• qemu-i386-static (Not sure this one matters)

This means the creation of the loopback img and installation fail on devices that cannot execute 32-bit (e.g Samsung S24 series)

I don't think it's going to get fixed any time soon... for now it's fine

[Sir-MmD]

The following binaries are shipped as 32-bit:

• e2fsck
• mke2fs
• pkgdetails
• qemu-i386-static (Not sure this one matters)

This means the creation of the loopback img and installation fail on devices that cannot execute 32-bit (e.g Samsung S24 series)

You can fix this by compiling a static version of these binaries for aarch64:

• dd
• e2fsck
• mke2fs
• pkgdetails

and place them inside /assets/bin/arm_64.

I already compiled these binaries for myself and it did work without any issue on my S24 FE running android 15:

Binaries:
https://drive.google.com/drive/folders/1QQNXoo6mGZkqNA_aPs_5xzBP0V1kToUT?usp=sharing
New apk with fixed 64bit binaries:
https://drive.google.com/file/d/1ktTpotcEi1jndCkLsiXuj49xvXRKSNR7/view

Of course if you care more about your security, you should compile it yourself !