Acode icon indicating copy to clipboard operation
Acode copied to clipboard

Terminal not working

Open Enderman1235084 opened this issue 4 months ago • 14 comments

Check for existing issues

  • [x] Completed

Describe the bug / provide steps to reproduce it

I installed the new update and was really excited to see the built-in terminal environment but when I opened the terminal it showed this:

🚀 Installing Terminal Environment...
This may take a few minutes depending on your connection.

⬇️  Downloading sandbox filesystem...
⬇️  Downloading axs...
🐧  F-Droid flavor detected, downloading additional files...
⬇️  Downloading compatibility layer...
⬇️  Downloading supporting library...
✅  All downloads completed
📁  Setting up directories...
📦  Extracting sandbox filesystem...
⚙️  Applying basic configuration...
✅  Extraction complete
⚙️  Updating sandbox enviroment...
File written successfully
File written successfully
proot error: execve("/bin/sh"): No such file or directory
proot info: possible causes:
* the program is a script but its interpreter (eg. /bin/sh) was not found;
* the program is an ELF but its interpreter (eg. ld-linux.so) was not found;
* the program is a foreign binary but qemu was not specified;
* qemu does not work correctly (if specified);
* the loader was not found or doesn't work.
fatal error: see `libproot-xed.so --help`.
proot error: can't chmod '/data/user/0/com.foxdebug.acode/files/tmp/proot-29496-iHsKNp': No such file or directory
exit 1

Please fix

Environment

I use a Samsung Galaxy Tab A (8.0" 2019) model T-295. I once tried to root my tablet but only got as far to unlocking the bootloader.

If applicable, add mockups / screenshots regarding your vision

No response

If applicable, attach your Acode.log file to this issue.

Acode.log
[2025-08-05T00:59:50.119Z] [INFO] Started app and its services...

Enderman1235084 avatar Aug 05 '25 01:08 Enderman1235084

The only way it works is to reinstall the terminal

sebastianjnuwu avatar Aug 15 '25 23:08 sebastianjnuwu

Does it still happen after clearing data?

RohitKushvaha01 avatar Aug 16 '25 07:08 RohitKushvaha01

Just uninstalling from terminal setting doesn't work, neither does reinstalling the app, nor does clearing the data which I just tried

Enderman1235084 avatar Aug 16 '25 10:08 Enderman1235084

Just uninstalling from terminal setting doesn't work, neither does reinstalling the app, nor does clearing the data which I just tried

Are you on latest version?

RohitKushvaha01 avatar Aug 16 '25 11:08 RohitKushvaha01

@RohitKushvaha01 Well yes, it happened right after i installed the new update

Enderman1235084 avatar Aug 16 '25 12:08 Enderman1235084

I have a similar problem while installing the terminal. It works with the PlayStore version, but in the F-Droid version I get this error:

🚀Installing Terminal Environment...
This may take a few minutes depending on your connection.

⬇️  Downloading sandbox filesystem...
⬇️  Downloading axs...
✅  All downloads completed
📁  Setting up directories...
📦  Extracting sandbox filesystem...
⚙️  Applying basic configuration...
✅  Extraction complete
⚙️  Updating sandbox enviroment...
File written successfully
File written successfully
sh: /data/user/0/com.foxdebug.acode/files/init-sandbox.sh[90]: /data/app/~~Lpw2NCx9FGejuxA0uinY6g==/com.foxdebug.acode-uG24fuptUhte6JFsKxI6HQ==/lib/arm64/libproot-xed.so: inaccessible or not found
exit 127

DaniJohni avatar Sep 02 '25 09:09 DaniJohni

@DaniJohni F-droid Builds Done at F-droid were having malfunctioned APKs for terminal Functionality, in the past few releases. I have Pull Request a Fix at their F-droid Repo (on gitlab). Future Releases in F-droid should be fine.

For now, use Our F-droid Builds. You can find them in the Releases Section of This Repository (Acode).

Thanks.

UnschooledGamer avatar Sep 02 '25 09:09 UnschooledGamer

For me it looks even "worse"... ;)

Fresh installation from f-droid or apk downloaded from here (1.11.6) gives this: Screenshot_20251006-173447_Acode.jpg

Don't know why but it looks like it can't go through extraction process...

The screenshot is from SGS7E with Android 8...

manieKMP avatar Oct 06 '25 16:10 manieKMP

For me it looks even "worse"... ;)

Fresh installation from f-droid or apk downloaded from here (1.11.6) gives this: Screenshot_20251006-173447_Acode.jpg

Don't know why but it looks like it can't go through extraction process...

The screenshot is from SGS7E with Android 8...

The APK downloaded from GitHub releases gives that too? Also, Acode expects Android 10+ I guess.

UnschooledGamer avatar Oct 06 '25 16:10 UnschooledGamer

Also, Acode expects Android 10+ I guess.

It works on all android versions, only android 10 has storage access issue

RohitKushvaha01 avatar Oct 06 '25 16:10 RohitKushvaha01

@manieKMP

Install the "Eruda" plugin and see if it shows any errors while running the terminal install

RohitKushvaha01 avatar Oct 06 '25 16:10 RohitKushvaha01

This is what eruda gave:

Error: Installation failed: tar: exec gunzip: Permission denied tar: read error

tar: read error
at t.value (https://localhost/__cdvfile_files-external__/plugins/sebastianjnuwu.acode.eruda/main.js:2:26084)
at new t (https://localhost/__cdvfile_files-external__/plugins/sebastianjnuwu.acode.eruda/main.js:2:21249)
at t.value (https://localhost/__cdvfile_files-external__/plugins/sebastianjnuwu.acode.eruda/main.js:2:41381)
at https://localhost/__cdvfile_files-external__/plugins/sebastianjnuwu.acode.eruda/main.js:2:43015

Error: Failed to create terminal: 

Error {}


at t.value (https://localhost/__cdvfile_files-external__/plugins/sebastianjnuwu.acode.eruda/main.js:2:26084)
at new t (https://localhost/__cdvfile_files-external__/plugins/sebastianjnuwu.acode.eruda/main.js:2:21249)
at t.value (https://localhost/__cdvfile_files-external__/plugins/sebastianjnuwu.acode.eruda/main.js:2:41381)
at https://localhost/__cdvfile_files-external__/plugins/sebastianjnuwu.acode.eruda/main.js:2:43015

Error: Failed to create terminal: 

Error {}


at t.value (https://localhost/__cdvfile_files-external__/plugins/sebastianjnuwu.acode.eruda/main.js:2:26084)
at new t (https://localhost/__cdvfile_files-external__/plugins/sebastianjnuwu.acode.eruda/main.js:2:21249)
at t.value (https://localhost/__cdvfile_files-external__/plugins/sebastianjnuwu.acode.eruda/main.js:2:41381)
at https://localhost/__cdvfile_files-external__/plugins/sebastianjnuwu.acode.eruda/main.js:2:43015

On the device there's no other permission options for Acode, than already turned on permission for memory. That "permission denied" sucks... ;)

manieKMP avatar Oct 06 '25 16:10 manieKMP

The APK downloaded from GitHub releases gives that too? Also, Acode expects Android 10+ I guess.

Yes, the difference is that the GH version with "fdroid" word has the prompt "f-droid flavor detected..." which isn't present in version from f-droid repo.

Edit: Well, it looks like the issue is (probably) with the device itself...

I've tried f-fdroid version and GH one (both 1.11.6) on moto g85 with Android 15 and GH version is working on that phone (the one from f-fdroid repo has the same problem as that from OP...).

Looks like Samsung sucks, user can give the permission to the memory for Acode but the phone still blocks something and don't give ability to run a terminal... And I can install Acode plugins without a problem, weird.

I wonder where terminal "stuff" is extracting to... Maybe the path for that is locked on some devices?

manieKMP avatar Oct 06 '25 16:10 manieKMP

The APK downloaded from GitHub releases gives that too? Also, Acode expects Android 10+ I guess.

Yes, the difference is that the GH version with "f-droid" word has the prompt "f-droid flavor detected..." which isn't present in version from f-droid repo.

Regarding that is mentioned in conversation of this issue (https://github.com/Acode-Foundation/Acode/issues/1477#issuecomment-3244490641), Upcoming Stable Releases should have those differences Resolved.

UnschooledGamer avatar Oct 06 '25 17:10 UnschooledGamer