Not all Linux systems have sudo installed per default like for example Debian. Most Android systems are targeted for end users who don't need to know the internals of Android (i.e. each Android applications runs under it's own user), so there is no need to provide an interactive way for an enduser to run a command as system administrator.

xda-developers Android Development and Hacking Android Software Development [Q] SuperUser Commands by ilendemli XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality. How To Fix Android Phone or Tablet Stuck at Logo Screen and Won't Restart - Duration: 9:07. Jeff Baker 687,773 views I'd like to chnage it to something else but am not able to locate it anywhere… have found it in other distros like ubuntu/debian - they have it in /etc/bash.bashrc and they even have such package by name command-not-found… and I was able to replace it with desired content… so, is there a way to perform the same on centos? If you really want to dig into the Android system, you may find that some apps require root access. Rooting has become less necessary over the years, but it's still useful if you want to run certain types of apps. Here's the most widely supported method for rooting your device, and why you might want to.

If you set this variable, but use the -s option to specify a serial number from the command line, the command-line input overrides the value in ANDROID_SERIAL. The following example sets ANDROID_SERIAL and calls adb install helloworld.apk , which then installs the Android application package on emulator-5555.

I'd like to chnage it to something else but am not able to locate it anywhere… have found it in other distros like ubuntu/debian - they have it in /etc/bash.bashrc and they even have such package by name command-not-found… and I was able to replace it with desired content… so, is there a way to perform the same on centos?

Not all Linux systems have sudo installed per default like for example Debian. Most Android systems are targeted for end users who don't need to know the internals of Android (i.e. each Android applications runs under it's own user), so there is no need to provide an interactive way for an enduser to run a command as system administrator.

[FIX]Command su not working in Android terminal/shell - SuperSu problems. Here is the how to fix it. sudo command not found fix in Linux (Debian 9 GNU/Linux ) - Duration: 1:40. Nice catch, Now with command "android" just open the app, but with "sudo android" still get "sudo: android: command not found" - Aby Nov 11 '15 at 9:40. Don't use sudo for that. But to explain the behavior: Command not found when executed as sudo, but works after "sudo su" Sometimes even after you add your android_sdk/ dir path from command line it still doesn't work and gives the command not found error, in that case follow these steps. I ran through this issue myself and i tried all the above steps and none worked so i thought i should share and perhaps that might help somebody. You might wonder why sudo isn't available on Android, while every Linux distribution has it. Well, sudo is equivalent to su on Android, which you use to execute commands that require root access. SuperSU application - is NOT installed. System File Properties for Root Access: Standard Location Check Command: ls -l /system/bin/su: Result: /system/bin/su: No such file or directory Analysis: File /system/bin/su does not exist. Standard Location Check Command: ls -l /system/xbin/su: Result: /system/xbin/su: No such file or directory Analysis The sudo command runs any command as another user account and is commonly used to elevate permissions so that the command is run with elevated security privileges (which in Linux terms is known as the root user).Sudo works for a brief period of time. To run as another user for a prolonged period of time then use the su command. [root@ip-172-31-33-121 ec2-user]# yum bash: yum: command not found I've read somewhere it could be a problem with my PATH, and I remember I did changed something on the PATH variable while doing some installations but I can't remember exactly what and why, I think it was when I was trying to install node.js or npm, anyway I'm not sure how to