Help to change the execution rights on a Galaxy Tab

[regressist]

Hi all,
I apologize in advance for my post but I guess there is no better place to ask on this web site.
I have written some programs in Pascal to make some computations: no input or interactions, just run and after a long time some integers are output on the display and in a file: no apk, just an executable. Since I need processing power I thought to take (little but not negligible) advantage of an old Galaxy tab 10.1 GT-P7510 (10 years old) where with substantial help 3 years ago I installed a non-native OS (Android 7) with partial success, practically it is handicapped in many ways but I do not enter in detail.
With heavy help from someone in another forum we compiled one program and transferred it to the Galaxy, where I installed the Terminal emulator https://play.google.com/store/apps/details?id=jackpal.androidterm. Now I am stuck because I am not able to change the rigths so that it can be executed. If it was a pc I would have just to run it but apparently with Android it is not like this!
The Galaxy is rooted. Unfortunately the guy in the other forum is not replying any more (I hope he is not sick) and since I should be just one hopefully small step from the solution, I ask if someone is willing to help solve this problem taking into account that I am a monkey, I do not know linux and android, and it's unlikely I am able to fix this issue if it implies complex operations, etc.
Thanks in advance to whomever will reply, even telling that it is unsolvable is usefull for me.

Sergio

 

[Hadron]

I'm not 100% sure what it is that you want to change the rights of, or how the terminal emulator comes into this.

But if I am running a terminal on a *nix box (Unix/Linux/MacOS/etc) and want to make a file executable the command I would use is

chmod ugo+x filename

where "chmod" is the command to change the file's permissions, "ugo" refers to all 3 classes of user (user, group, other) and "+x" means "add execution permission". With that anyone done could then execute the file in question from the command line (assuming it is actually executable - won't get you anywhere if it isn't).

If you (the user logged in to the command line/terminal) do not own the file you will need admin (root) permission to do this. Again the Linux format for that would be to preface the command with "sudo", as in "sudo chmod ....". Of course that assumes that the user has the right to use the sudo command. Whether that's relevant to an android terminal emulator is a different question (I hope it isn't, as the sudo command probably doesn't exist by default and I'm not even sure whether an android busybox installation includes it), but I thought I'd mention it for completeness.

Of course if your problem isn't that you are trying to run this thing from the command line inside the terminal emulator then none of this will be relevant.

 

[Taqras]

If your device is rooted and flashed with something that doesn't quite work, and you can't otherwise make it do what you want, it may help to "factory reset" it by flashing it with the original Samsung firmware. I'm not sure if you can get that from Samsung, but lots of sites claims to have it:
https://www.qwant.com/?q=samsung+firmware

Here is one such site, which also has a procedure for how to go about it:
https://samfw.com/firmware/GT-P7510/ROM
It's old stuff and the link they have to the Odin tool is gone, but I think this is it:
https://www.ydfile.com/file/odin/Odin3_v3.14.4.html

If it doesn't kill your device, it might get it working again

 

[regressist]

I'm not 100% sure what it is that you want to change the rights of, or how the terminal emulator comes into this.

But if I am running a terminal on a *nix box (Unix/Linux/MacOS/etc) and want to make a file executable the command I would use is

chmod ugo+x filename

where "chmod" is the command to change the file's permissions, "ugo" refers to all 3 classes of user (user, group, other) and "+x" means "add execution permission". With that anyone done could then execute the file in question from the command line (assuming it is actually executable - won't get you anywhere if it isn't).

If you (the user logged in to the command line/terminal) do not own the file you will need admin (root) permission to do this. Again the Linux format for that would be to preface the command with "sudo", as in "sudo chmod ....". Of course that assumes that the user has the right to use the sudo command. Whether that's relevant to an android terminal emulator is a different question (I hope it isn't, as the sudo command probably doesn't exist by default and I'm not even sure whether an android busybox installation includes it), but I thought I'd mention it for completeness.

Of course if your problem isn't that you are trying to run this thing from the command line inside the terminal emulator then none of this will be relevant.

Thanks for your reply, yes, I typed chmod 755 ./file , I got no message but upon ls -al the rights of the file are not changed and if I type the name of the file (in order to execute it) I get

tmp-mksh:filename: not found

In practice I understand that I can not change the right even though I am superuser. Probably he does not see the owner as me, it was transferred with the pc

 

[regressist]

If your device is rooted and flashed with something that doesn't quite work, and you can't otherwise make it do what you want, it may help to "factory reset" it by flashing it with the original Samsung firmware. I'm not sure if you can get that from Samsung, but lots of sites claims to have it:
https://www.qwant.com/?q=samsung+firmware

Here is one such site, which also has a procedure for how to go about it:
https://samfw.com/firmware/GT-P7510/ROM
It's old stuff and the link they have to the Odin tool is gone, but I think this is it:
https://www.ydfile.com/file/odin/Odin3_v3.14.4.html

If it doesn't kill your device, it might get it working again

Thanks, the links are useful, but in this case the issue is not that the system does not work at all, there are some quirks but overall it's ok. As I said in the other reply there is probably a problem of file ownership