MD5 Errors (x86_64) about termuxarch HOT 4 CLOSED

@Seriell thank you for posting. You addressed an important error. This should be fixed now with 12b9315 this commit. I have tested, and installation seems to work fine now. However, I do not have an x86_64 to do a complete test with login. Image download, md5 check and extraction should work for you fine now. Enjoy.

from termuxarch.

from termuxarch.

It's not an md5 issue anymore, now I get this:

from termuxarch.

@Seriell sorry to hear that you are still having trouble. Make sure termux-exec is installed. This should take care of script startup issues. See "Why do I keep getting '/bin/sh bad interpreter' error?" for more information. Running setupTermuxArch.sh should do this for you.

The script is now self-updating, so see if running it again helps. Your version is self-updating, so you do not need to grab a fresh copy from here and try again. Just run it again. You should have gotten a login in your first screenshot, but for some reason you got a startArch.sh not found! How did you do that? setupTermuxArch.sh is supposed to create startArch.sh.

I have not a clue why PRoot says it only runs on 32bit. This might be x86_64 specific in as far as it doesn't work, but it should work. This screenshot is from an aarch64 device and fortunately PRoot does not complain. Your PRoot error confirms the startup script is setup correctly on your device. It found env, but why it says it will not run on 64bit is beyond scope here. This is a PRoot issue. Please reference this issue should you post at https://github.com/termux/proot/issues while seeking your solution. There is active development at termux-proot and new versions of PRoot are being published and tested. Good luck.

from termuxarch.