android2gnulinux

That sounds familiar, I used <https://github.com/Cloudef/android2gnulinux> to reverse one libjiagu program in past. The deobfuscated code eventually ends up in the ram, and you can then extract it.

The project seems to be built on top of my android2gnulinux project from way back. Nice to see someone picking up the pieces and making it more functional. https://github.com/Cloudef/android2gnulinux

Some android malware also checks TracerPid in /proc/*/status https://github.com/Cloudef/android2gnulinux/blob/master/src/...

The tool moves runs the application and all of its dependencies in a container for compatibility, but on Android with bionic that would probably imply moving all of libc with the app. I don't think that'll go down as easily, as the entire bionic framework is integrated quite deeply with the rest of the system. For "simple" bionic libc calls, an LD_PRELOAD shim might be enough for many binaries, though. You'd need to translate all the bionic libc calls to your system's libc calls, but that might just be easier than it seems because the level of compatibility between the two. Bionic is actually a subset of POSIX libc, so you should be able to map all calls to your normal system calls. I don't know how well-maintained the project is, but https://github.com/Cloudef/android2gnulinux might just do the trick for you.

I actually have written bionic -> glibc compatibility layer. https://github.com/Cloudef/android2gnulinux If it's a native binary, there's good chance you can run it with this. JNI/Java stuff is mostly unity and even that's very proof of concept.

https://github.com/Cloudef/android2gnulinux There's also this clean-room implementation of android apis and bionic->glibc translation layer that I worked in past. It can launch some unity games, and cli tools usually work. I used this mainly to reverse engineer chinese DRM in some android apps.