whenever i use adb in ubuntu it just says this:
Code:
[email protected]:~# cd /sdk/platform-tools
[email protected]:/sdk/platform-tools# adb devices
No command 'adb' found, did you mean:
Command 'cdb' from package 'tinycdb' (main)
Command 'gdb' from package 'gdb' (main)
Command 'dab' from package 'bsdgames' (universe)
Command 'zdb' from package 'zfs-fuse' (universe)
Command 'mdb' from package 'mono-debugger' (universe)
Command 'tdb' from package 'tads2-dev' (multiverse)
Command 'pdb' from package 'python' (main)
Command 'jdb' from package 'openjdk-6-jdk' (main)
Command 'ab' from package 'apache2-utils' (main)
Command 'ad' from package 'netatalk' (universe)
adb: command not found
doesnt make sense.. works in windows but im tired of rebooting to use adb
any ideas?
Make sure adb in is your PATH: echo $PATH
If not, add it: export PATH=$PATH:/path/to/sdk/platform-tools
ikon8 said:
Make sure adb in is your PATH: echo $PATH
If not, add it: export PATH=$PATH:/path/to/sdk/platform-tools
Click to expand...
Click to collapse
I think you mean in your bash file. Go into your home folder and hit control-h. It should show hidden files. Open your bash and put the above-mentioned.
If you don't want to go that far you can always navigate to that directory and punch in the commands.
Sent from my ADR6400L using Tapatalk
thanks for the replies guys but ive already done that as well..ugh this is frustrating
You run an executable binary with a ./ before it in linux.
./adb devices
Like that.
But it's really best to add the directory to your path, so you can run adb from any directory easily.
Add this line to your .bashrc file (which is in your home directory) at the end:
export PATH=/sdk/platform-tools:$PATH
Then close and open a new terminal. Then you should be able to run adb without the ./ from any directory.
If that still doesn't work, type "echo $PATH" and make sure it shows the directory there. If not, you did something wrong saving that line in your .bashrc file, or it's not being loaded properly.
Nikolai2.1 said:
whenever i use adb in ubuntu it just says this:
Code:
[email protected]:~# cd /sdk/platform-tools
[email protected]:/sdk/platform-tools# adb devices
No command 'adb' found, did you mean:
Command 'cdb' from package 'tinycdb' (main)
Command 'gdb' from package 'gdb' (main)
Command 'dab' from package 'bsdgames' (universe)
Command 'zdb' from package 'zfs-fuse' (universe)
Command 'mdb' from package 'mono-debugger' (universe)
Command 'tdb' from package 'tads2-dev' (multiverse)
Command 'pdb' from package 'python' (main)
Command 'jdb' from package 'openjdk-6-jdk' (main)
Command 'ab' from package 'apache2-utils' (main)
Command 'ad' from package 'netatalk' (universe)
adb: command not found
doesnt make sense.. works in windows but im tired of rebooting to use adb
any ideas?
Click to expand...
Click to collapse
I know exactly what this is. Get out of hard root and stay in your regular home folder. There are two things that will make this simple for you. 1. take the adb executable and place it in your users bin. so that would be something like /usr/bin...once again make sure you are in nautilus as the regular user and not root! 2. Now go back into your terminal and invoke it by typing sudo adb start-server...then sudo adb devices...the key thing here is that ubuntu's permissions are a bit screwy so you have to use adb in this manner. once again sudo everthing ("sudo adb" etc.)...do not become hard root in ubuntu (sudo su)
EDIT: btw if you use this method you will not have to worry about paths as long as it's in your user bin...you dont have to ./adb devices either if you do it this way
Javis
GrdLock said:
You run an executable binary with a ./ before it in linux.
./adb devices
Like that.
But it's really best to add the directory to your path, so you can run adb from any directory easily.
Add this line to your .bashrc file (which is in your home directory) at the end:
export PATH=/sdk/platform-tools:$PATH
Then close and open a new terminal. Then you should be able to run adb without the ./ from any directory.
If that still doesn't work, type "echo $PATH" and make sure it shows the directory there. If not, you did something wrong saving that line in your .bashrc file, or it's not being loaded properly.
Click to expand...
Click to collapse
trendsetter37 said:
I know exactly what this is. Get out of hard root and stay in your regular home folder. There are two things that will make this simple for you. 1. take the adb executable and place it in your users bin. so that would be something like /usr/bin...once again make sure you are in nautilus as the regular user and not root! 2. Now go back into your terminal and invoke it by typing sudo adb start-server...then sudo adb devices...the key thing here is that ubuntu's permissions are a bit screwy so you have to use adb in this manner. once again sudo everthing ("sudo adb" etc.)...do not become hard root in ubuntu (sudo su)
EDIT: btw if you use this method you will not have to worry about paths as long as it's in your user bin...you dont have to ./adb devices either if you do it this way
Javis
Click to expand...
Click to collapse
Thank you both for the advice! Both things worked very well and i appreciate the advise!
1.Get root permission.
2.Install x32 libs if you are running on a x64
Code:
apt-get install ia32-libs
3.Install sun JDK - Aprox 25 mins in 56k line
Code:
apt-get install sun-java6-jdk
4.Install eclipse -Aprox 1hr in 56k line
Code:
sudo apt-get install eclipse
5.Now open up Eclipse, and go to:
Help Menu -> Install New Software
* Add:
Code:
https://dl-ssl.google.com/android/eclipse/
http://download.eclipse.org/datatools/updates
http://download.eclipse.org/webtools/updates/
http://download.eclipse.org/modeling/emf/updates/releases/
http://download.eclipse.org/tools/gef/updates/releases/
http://dl.google.com/eclipse/plugin/3.5
Install these packages, and then you can install adt plugin as well.
6.Download Android SDK from
http://developer.android.com/sdk/index.html
7.Now open a terminal again and go to the directory where you've saved the Android SDK
Code:
cd /home/*username*/Desktop
8.Uncompress it.
Code:
tar xvfz android-sdk_r12-linux_x86.tgz
9.Delete the archive file to save some space
Code:
rm android-sdk_r12-linux_x86.tgz
10.Move extracxted file to your home directory.
Code:
mv android-sdk-linux_86 /home/*username*
11.Make and edit /etc/udev/rules.d/##-android.rules
Code:
sudo gedit /etc/udev/rules.d/##-android.rules
## = 50 if you are running Gusty/Hardy/Dapper (50-android.rules) or with the number 70 if you are running Karmic Koala/Lucid Lynx/Maverick Meerkat(70-android.rules)
12.in ##-android.rules Add line as follow
For Gusty/Hardy:
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
For Dapper:
Code:
SUBSYSTEM=="usb_device", SYSFS{idVendor}=="0bb4", MODE="0666"
For Karmic Koala:
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
For Lucid Lynx:
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
For Maverick Meerkat:
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666"
**NOTE: In the above lines the code ”0bb4″ refers to a HTC device. If your phone is from a different manufacturer, replace the code with the appropriate
Code:
Acer - 0502
Dell - 413c
Foxconn - 0489
Garmin-Asus - 091E
HTC (Older Phones) - 0bb4
HTC (Newer phones) - 18d1
Huawei - 12d1
Kyocera - 0482
LG - 1004
Motorola - 22b8
Nexus One/S - 18d1
Nvidia - 0955
Pantech - 10A9
Samsung - 04e8
Sharp - 04dd
Sony Ericsson - 0fce
ZTE - 19D2
**NOTE: If you copy one of the lines mentioned above, make sure you replace the quotation marks with the ones in your keyboard, as these have different display code and it might give you a “no permissions” error.
13.Execute ##-android.rules:
Code:
sudo chmod a+rx /etc/udev/rules.d/70-android.rules
14.Reboot
**To run ADB you need to add an environment variable to your bashrc file.
15.Open a terminal window and type:
Code:
sudo gedit .bashrc
16.Add the following line at the end of the page:
Code:
export PATH=$PATH:/home/grainier/android-sdk-linux_x86/Platform-tools
17.Save and close
18.To make sure everything works perfect, type adb devices in a terminal window with your phone plugged in.
If you see a serial number pop up that means you are done. Should look something like this:
List of devices attached
HT99PHF***** device
**If for some reasons when running adb devices gives you a “no permissions” error, try typing the following in terminal
adb kill-server
adb start-server
18.Finally open up Eclipse and Go to Window > Preferences. Select Android, and add the SDK Location: /home/*username*/android-sdk-linux_86
19.Click the Apply and then OK.
**Everything is ready to go.. rest is up to you**
I hope you realize that Debian and Debian-derivatives aren't the only Linux based operating systems in the entire universe.
With Ubuntu's recent decision to no longer include Sun Java SDK in their repositories, this post needs an update. I've just completed an install of the Android Dev Environment following this guide, but as the Sun Java SDK has been removed from the Ubuntu Respositories, is installed the Open Java JKDK. It seems to work OK, although only time will tell as I do more Android development.
To download and install the Open Java SKD on a variety of Linux distros follow the instructions appropriate to your Linux Distro on the following link (add dots to replace the spaces in the following address. Sorry as a new poster, I can't post external links.)
openjdk java net
Hi all,
Today i will tell you about ADB.
1. What's ADB?
ADB (Android Debug Bridge) is a versatile COMMAND LINE TOOL that lets you communicate with an emulator instance or connected Android-powered device. It is a client-server program that includes three components:
* A client, which runs on your development machine. You can invoke a client from a shell by issuing an adb command. Other Android tools such as the ADT plugin and DDMS also create adb clients.
*A server, which runs as a background process on your development machine. The server manages communication between the client and the adb daemon running on an emulator or device.
*A daemon, which runs as a background process on each emulator or device instance.
2. How Can i Get it?
For Windows...You can Download the Attachment...For Other OS you Have to Install SDK and After go to <SDK>\platform-tools to get the same file of Windows but now for Linux or Mac!
NOTE: SOMETIMES ADB DON'T WORK TO BE SURE IT WORK INPUT IN CMD adb devices (no caps) ---> If After "List of..." You Get a Code with Device is all Ok.
0123456789ABCDEF device
But if You don't Get the code you have to install HTC SYNC for Android....
And After Retry with "adb devices" and if you get the code you can Use Adb..
In my Opinion you can Put the folder in C:\Android and made a link on Desktop...
3. Command to Use ADB and Their Function:
Android Debug Bridge version 1.0.26
(**MOST USED**)
Code:
adb push <local> <remote> - copy file/dir to device
Code:
adb pull <remote> <local> - copy file/dir from device
Code:
adb sync [ <directory> ] - copy host->device only if changed (see 'adb help all')
Code:
adb shell - run remote shell interactively
Code:
adb shell <command> - run remote shell command
Code:
adb emu <command> - run emulator console command
Code:
adb logcat [ <filter-spec> ] - View device log
Code:
adb install [-l] [-r] <file> - push this package file to the device and install it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data)
Code:
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories)
Code:
adb version - show version num
Code:
adb -w - wipe the data partition
Code:
adb -d - flash the data partition
Code:
adb wait-for-device - block until device is online
Code:
adb start-server - ensure that there is a server running
Code:
adb kill-server - kill the server if it is running
Code:
adb get-state - prints: offline | bootloader | device
Code:
adb get-product - prints: <product-id>
Code:
adb get-serialno - prints: <serial-number>
Code:
adb status-window - continuously print device status for a specified device
Code:
adb remount - remounts the /system partition on the device read-write
If You Need Help Ask Here.
I Hope This Thread will Be Usefull...
Hello there people,
I am lucky enough to be in possession of a newly un-released HTC One Mini (proof seen below).
I am your loyal servant so let's get this thing rooted. Tell me what to do and I will do anything I can to help. :good:
guywithdesire1992 said:
Hello there people,
I am lucky enough to be in possession of a newly un-released HTC One Mini (proof seen below).
I am your loyal servant so let's get this thing rooted. Tell me what to do and I will do anything I can to help. :good:
Click to expand...
Click to collapse
would you mind getting in touch with me so i can assist in full system dump
thanks bud
Check your PMs mate.
Sent from my Evita
timmaaa said:
Check your PMs mate.
Sent from my Evita
Click to expand...
Click to collapse
Yeah
Sent from my HTC One S using xda premium
https://github.com/zarboz/android_vendor_htc_m4
https://github.com/zarboz/android_device_htc_m4
Just need to grab his zImage and should be set
How u like that mini bro?
Sent from my HTC One XL using Tapatalk 4 Beta
Moved To Q&A
Please do not open question threads in a dev section
https://mega.co.nz/#!Q4Q2CIBY!bLmngjjawQueqw3_y_WTPl5BqGVChnIj2MHGXvPgQ6Q
HTC One mini dump
OP,
Could you run the following commands and then post the file and zip up the folder they make? (Run the first from terminal emulator, second from computer)
Single file (will be in sdcard)
Code:
dd if=/dev/block/mmcblk0p32 of=/sdcard/boot.img
Folder (will be on computer, zip up and upload please)
Code:
adb pull /data/preload
Sent from my buttered S3
CNexus said:
OP,
Could you run the following commands and then post the file and zip up the folder they make? (Run the first from terminal emulator, second from computer)
Single file (will be in sdcard)
Code:
dd if=/dev/block/mmcblk0p32 of=/sdcard/boot.img
Folder (will be on computer, zip up and upload please)
Code:
adb pull /data/preload
Sent from my buttered S3
Click to expand...
Click to collapse
the boot partition is read protected and so is /data without root
we need temp root to dump the boot partiion for me to build him a working recovery
CNexus said:
OP,
Could you run the following commands and then post the file and zip up the folder they make? (Run the first from terminal emulator, second from computer)
Single file (will be in sdcard)
Code:
dd if=/dev/block/mmcblk0p32 of=/sdcard/boot.img
Folder (will be on computer, zip up and upload please)
Code:
adb pull /data/preload
Sent from my buttered S3
Click to expand...
Click to collapse
Cannot run, permission denied.
C:\Users\Dan>cd c:\android
c:\android>dd if=/dev/block/mmcblk0p32 of=/sdcard/boot.img
'dd' is not recognized as an internal or external command,
operable program or batch file.
Click to expand...
Click to collapse
c:\android>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:/ $ adb pull /data/preload
adb pull /data/preload
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
1|[email protected]:/ $ ^C
c:\android>adb pull/data/preload
Android Debug Bridge version 1.0.31
-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <specific device> - directs command to the device or emulator with
the given
serial number or qualifier. Overrides ANDROID_S
ERIAL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices [-l] - list all connected devices
('-l' will also list device qualifiers)
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number
is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number
is specified.
Using this command with no additional arguments
will disconnect from all connected TCP/IP devic
es.
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(-l means list but don't copy)
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] [--algo <algorithm name> --key <hex-encoded key> --
iv <hex-encoded iv>] <file>
- push this package file to the device and instal
l it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
('-s' means install on SD card instead of inter
nal storage)
('--algo', '--key', and '--iv' mean the file is
encrypted already)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.
adb backup [-f <file>] [-apk|-noapk] [-shared|-noshared] [-all] [-system|-nosy
stem] [<packages...>]
- write an archive of the device's data to <file>
.
If no -f option is supplied then the data is wr
itten
to "backup.ab" in the current directory.
(-apk|-noapk enable/disable backup of the .apks
themselves
in the archive; the default is noapk.)
(-shared|-noshared enable/disable backup of the
device's
shared storage / SD card contents; the defau
lt is noshared.)
(-all means to back up all installed applicatio
ns)
(-system|-nosystem toggles whether -all automat
ically includes
system applications; the default is to inclu
de system apps)
(<packages...> is the list of applications to b
e backed up. If
the -all or -shared flags are passed, then t
he package
list is optional. Applications explicitly g
iven on the
command line will be included even if -nosys
tem would
ordinarily cause them to be omitted.)
adb restore <file> - restore device contents from the <file> backup
archive
adb help - show this help message
adb version - show version num
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb get-devpath - prints: <device-path>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on th
e specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be u
pdated.
- If it is "system" or "data", only the corresponding partition
is updated.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list
of the following values
1 or all, adb, sockets, packets, rwx, usb, sync
, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes prior
ity over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these de
bug tags are printed.
c:\android>
Click to expand...
Click to collapse
You didn't type the second command correctly...there should be a space between "adb" and "/data/preload".
For the first command, run this instead (from your computer)
Code:
adb shell
dd if=/dev/block/mmcblk0p32 of=/sdcard/boot.img
exit
adb pull /sdcard/boot.img
And then upload the boot.img that should be in your current folder on your computer
If still nothing, please PM me so we can set up a team viewer and I can try to pull those files and I can also try to root your phone (safe, nothing bad will happen if it fails)
Sent from my buttered S3
Deodexed dump
Thank OP
http://www.androidfilehost.com/?fid=23060877489997282
Hi,
scine some days I own a htc one mini and I need to "root" it.
What is the best place to get started?
I'm very firm with linux, so I think i can do something
(I switched back from ios after some years of using iphone)
fvdaak said:
Hi,
scine some days I own a htc one mini and I need to "root" it.
What is the best place to get started?
I'm very firm with linux, so I think i can do something
(I switched back from ios after some years of using iphone)
Click to expand...
Click to collapse
PM me so we can set up teamviewer and try to root your phone
What's in it for me is that I really need the One mini's boot.img
CNexus said:
PM me so we can set up teamviewer and try to root your phone
What's in it for me is that I really need the One mini's boot.img
Click to expand...
Click to collapse
Would be great if you could get the recovery.img also.
Flyhalf205 said:
Would be great if you could get the recovery.img also.
Click to expand...
Click to collapse
If I can dump the boot.img then he can dev unlock and I'll pass him an insecure boot.img through which he can gain root.
Or if he gains root through another method, then we can still dump everything.
After that, life is good.
Anyway, still waiting for a response.
Hi,
I can confirm, what guywithdesire1992 said:
There is no permission to open the device.
When I do "dd if=/dev/block/mmcblk0p32 of=/sdcard/boot.img", I get the following error:
/dev/block/mmcblk0p32: cannot open for read: Permission denied
Do you have any suggestions?
btw:
There is no "su" on the device.
I've tried to install static linked su from "SuperUser.apk" and also from "CWM-SuperSU" - without success.
I have stored the su executables to /data/local/tmp and gained executable-rights (chmod 777). After that I was able to execute it, but i does nothing.
No error, just nothing
PM me so we can set up teamviewer and try to get you rooted.
i got a new qubo big one and wanted to root it
Your phone's Android OS is rooted as soon as the cmdlet named su - what by default is left off - is present in Android's file system and executable.
Hence add a suitable version of su to Android OS: can be done via ADB.
Please can I get a step by step
xXx yYy said:
Your phone's Android OS is rooted as soon as the cmdlet named su - what by default is left off - is present in Android's file system and executable.
Hence add a suitable version of su to Android OS: can be done via ADB.
Click to expand...
Click to collapse
Instruction?
Please I need a step by step guide
A: To run Android shell commands with super-user right from within the shell on desktop computer ( AKA Command Prompt ) you have to run within desktop computer shell
Code:
adb devices
adb push <LOCATION-OF-SUITABLE-SU-BINARY-ON-PC-HERE> /data/local/tmp/
what will 1. connect the Android device to your desktop computer and 2. upload the su binary in the Android device temporary directory always available for the user.
B: Then, in desktop computer shell type
Code:
adb shell "cd /data/local/tmp & chmod 776 su"
what makes the su binary executable: its ownership by default is set to shell.
C: Then in desktop computer shell type
Code:
adb shell "ls -l"
what will show you content and permissions on recently uploaded files.
D:
To apply a series of Android shell commands what require super-user rights you now would run
Code:
adb shell
export PATH=/data/local/tmp:$PATH"
su -c "<SHELL-CMD-HERE>"
....
su -c "<SHELL-CMD-HERE">
exit
.
xXx yYy said:
A: To run Android shell commands with super-user right from within the shell on desktop computer ( AKA Command Prompt ) you have to run within desktop computer shell
Code:
adb devices
adb push <LOCATION-OF-SUITABLE-SU-BINARY-ON-PC-HERE> /data/local/tmp/
what will 1. connect the Android device to your desktop computer and 2. upload the su binary in the Android device temporary directory always available for the user
xXx yYy said:
A: To run Android shell commands with super-user right from within the shell on desktop computer ( AKA Command Prompt ) you have to run within desktop computer shell
Code:
adb devices
adb push <LOCATION-OF-SUITABLE-SU-BINARY-ON-PC-HERE> /data/local/tmp/
what will 1. connect the Android device to your desktop computer and 2. upload the su binary in the Android device temporary directory always available for the user.
B: Then, in desktop computer shell type
Code:
adb shell "cd /data/local/tmp & chmod 776 su"
what makes the su binary executable: its ownership by default is set to shell.
C: Then in desktop computer shell type
Code:
adb shell "ls -l"
what will show you content and permissions on recently uploaded files.
D:
To apply a series of Android shell commands what require super-user rights you now would run
Code:
adb shell
export PATH=/data/local/tmp:$PATH"
su -c "<SHELL-CMD-HERE>"
....
su -c "<SHELL-CMD-HERE">
exit
Click to expand...
Click to collapse
B: Then, in desktop computer shell type
Code:
adb shell "cd /data/local/tmp & chmod 776 su"
what makes the su binary executable: its ownership by default is set to shell.
C: Then in desktop computer shell type
Code:
adb shell "ls -l"
what will show you content and permissions on recently uploaded files.
D:
To apply a series of Android shell commands what require super-user rights you now would run
Code:
adb shell
export PATH=/data/local/tmp:$PATH"
su -c "<SHELL-CMD-HERE>"
....
su -c "<SHELL-CMD-HERE">
exit
Click to expand...
Click to collapse
Thanks