adb shell as root after device rooted

once device rooted, we must perform "su" before we get root permission in adb shell,this is not convenient in some situations,so there have a method to get permission without perform "su".

adb shell
su
mount -o remount,rw /system
chmod 4755 /system/bin/sh
exit

-rwsr-xr-x root     shell      285016 2015-02-02 20:57 sh

we set /system/bin/sh to SUID permisson,now we can get root permission directly after adb shell.

maybe this method have secure issue, so only for specific suituation used.

BAT脚本自动执行 adb shell 以后的命令

@echo off
echo su > temp.txt
adb shell <temp.txt
echo 其它命令 >> temp.txt
echo 其它命令 >> temp.txt
adb shell <temp.txt
del temp.txt

adb脚本命令之su命令被打断的问题

以抓去设备网络包为例, 将命令行统一放到一个临时文件里面，然后批次执行。

adb start-server

adb push G:\cachelog\tcpdump /data/local/tcpdump

@echo off

set p=G:\cachelog\temp.txt

echo su > %p%

echo chmod 755 /data/local/tcpdump >> %p%

echo rm -r /sdcard/capture.pcap >> %p%

echo /data/local/tcpdump -p -vv -s 0 -w /sdcard/capture.pcap >> %p%

adb shell < %p%

del %p%

pause

run commands in linux shell using batch file

I need to be able to run the following commands on a rooted Android phone connected to my PC: 

su
mount -o rw,remount /system
chmod 777 /system/app/
exit
exit

And then I need to execute the following command on my PC:

adb push ..\bin\MyApp_signed.apk /system/app/

And finally, I need to do some clean up and reboot the phone:

su
chmod 755 /system/app/
reboot
exit
exit

How can I create a windows batch file so that those shell commands are passed to the android shell?

adb shell <command> allows you to run a shell command on the device from your computer.
If your su command supports the -c option, you can do this:

adb shell su -c "mount -o rw,remount /system"
adb shell su -c "chmod 777 /system/app/"

adb push ..\bin\MyApp_signed.apk /system/app/

adb shell su -c "chmod 755 /system/app/"
adb shell su -c reboot

If your su command doesn‘t support commands, you could make a script to leave on the device that bundles the device side of it.

It appears that I was using a very simple version of su which did not accept the -c argument.

I copied another su which did work.

AndyD is totally right though, so I am accepting his answer instead of mine :)

Launch a script as root through ADB

I have created a script to mount partitions and do some stuff in my Android system. I saved the script as install.sh in the /bin folder of Android.

I want to call the script from ADB, which is itself called from a batch file on Windows, but it needs to be executed as root.

This works for me:

Create myscript.bat and put into it (note the single quotes around the commands to be executed in superuser mode):

adb shell "su -c ‘command1; command2; command3‘"

hen run myscript.bat from a DOS shell.

Note: it doesn‘t appear that the the DOS line continuation character (^) works in this situation.

In other words, the following doesn‘t work for me: This results in "Syntax error: Unterminated quoted string"

adb shell "su -c ‘^
command1; ^
command2; ^
command3‘"

This works :

adb shell echo command which needs root privileges \| su

If you need redirection:

adb shell echo ‘echo anytext > /data/data/aforbiddenfolder/file‘ \| su

For "copying" a local file to an android path needing root privileges (but alocalfile must not contain ‘):

cat alocalfile | adb shell echo "echo ‘`cat`‘ > /data/data/aforbiddenfolder/file" \| su

This works for me: 

adb shell "su -c ./data/local/tcpdump-arm -s 0 -v -w /data/local/appxpress_dump.pcap"

but it does not work as it gives me a shell access (with root permissions), but nothing is executed.

How do you know that you are given root permissions?

I assume you are attempting to execute the script on a device? Has your device been rooted?

You may need to give execute permissions via chmod to the file.

chmod ugo=rwx /bin/script.sh

Android ADB Commands Using Batch File

cd %ANDROID_SDK%/platform-tools
cd %ANDROID_SDK%/platform-tools
adb shell su -c "chmod 777 /data"
adb shell su -c "chmod 777 /data/data"
adb shell su -c "chmod 777 /data/data/your.packagename"
adb shell su -c "chmod 777 /data/data/your.packagename/databases"
adb shell su -c "chmod 777 /data/data/your.packagename/databases/MyDB"
adb pull /data/data/your.packagename/databases/MyDB C:\Users\Pavel\Desktop

http://www.faqoverflow.com/android/5884.html

QUESTION

Is there a way for me to run Adb shell as root without typing in su?

I want to be able to have root access without going into the shell.

ANSWER

If I‘m understanding your question correctly, you‘re asking how to get root access automatically when you run adb shell,

so that you don‘t have to go into the shell and type su to execute a command as root on your phone.

This is controlled by a flag in your boot partition, which most custom ROMs have modified to allow root permission by default.

If you get dropped to a $ when you use adb shell then you have

two permanent options and one temporary one (temporary meaning that it doesn‘t stick if you reboot):

1. Flash a ROM that includes the modification
2. Create a custom boot.img and flash it to your phone
   
   
3. Restart adbd on your device with root permissions

Number 2 is actually not that difficult, but it can be somewhat dangerous if you‘re careless.

There is a wiki article here which explains the process and includes a couple of Perl scripts to help you.

These instructions assume a Linux/Unix environment.

I have personally used these instructions on Fedora Linux and can tell you that they work, but I do not know about other *nix environments like Macs.

I also do not know of any similar Windows instructions, but I could try to track some down if you are on Windows.

The exact commands will vary somewhat from phone to phone since different devices use different partition tables.

Generally speaking, though, you need to pull your current boot.img from your phone, unpack it, extract the ramdisk, and find the default.prop file.

This is a plaintext file, which you need to open in a text editor and then find the line that contains the value ro.secure.

If the line says ro.secure=1 then you need to change it to ro.secure=0.

After that you can re-pack the ramdisk and boot.img, then flash it to your phone.

Once you reboot, you will be greeted with a # prompt whenever you perform adb shell without having to run su.

Alternatively, if you are using a custom ROM but it doesn‘t have this modification,

you can just unzip the ROM and modify the boot.img that is included with it using the above steps.

Then you can zip up the ROM with the newly modified boot.img and flash the zip file as you normally would.

This probably goes without saying, but be careful when doing this.

Messing with your boot partition can quite easily wreck your phone and force you to recover via HBoot.

I would highly recommend testing Fastboot to makes sure you can use extended Fastboot commands and perform a recovery.

This varies a bit based on your model, but most phones have some sort of desktop software that can be run to reflash the phone as well.

The third option is that in many cases it may be possible to restart adbd on your device with root privileges.

One possibility is to execute adb root from a PC terminal, although this will not work on all ROM configurations
(the ROM must be built as a "userdebug" one).

You can also try Chainfire‘s adbd insecure app.

This will not persist across a reboot, so you would need to use either the app or adb root again any time you restarted your phone.

adbd Insecure v2.00

adbd Insecure lets you run adbd in root mode if your device is rooted.
(Note that if you are running a custom kernel, it is likely that it already implements this functionality)
If you are running a stock (made by the phone manufacturer) kernel on your device,
chances are adbd is running in "secure" mode, even if you are rooted.

This app lets you run adbd in "insecure" mode, which gives you root access in "adb shell",
allows access to system files and directories through "adb push/pull",
and lets you run the "adb remount" command to make your /system partition writable.

Of course, your device must already be rooted for this to work.
It may not work with "S-ON" devices and locked bootloaders. 

This app does not make any permanent changes to your device - a reboot will undo any modification.
That‘s why there is also the option to enable this feature at boot.

Note that if you have USB connected when the app activates or deactivates adbd root mode,
you may need to unplug/replug the cable
or run "adb kill-server" on your computer before adb will work again.