I have used ADB in the past on my G1 and am now running into a problem on my G2. When I try to push a file to the SD card I get "permission denied". Any ideas?
example:
C:\android-sdk-windows\tools>adb shell
$ adb push su /sdcard/su
adb push su /sdcard/su
adb: permission denied
You need to go to the VISIONary when it show "permission deniedArrow", it will pop up something, choose "allow"
Are you sure I need root to push a file? In this guide to perm root (http://forum.xda-developers.com/showthread.php?t=834228) the first step is to disable or uninstall visionary.
I figured it out. You don't need to "adb shell" first
When I try to adb remount , I get a return of "remount failed: operation not permitted" does anyone no how to get adb to remount, I firtst run adb devices , and my phone serial number comes up but cant remount, can someone please help me get past this.
Lol u need to Su first after adb shell I see that u don't have a #
Sent from my HTC Vision using XDA App
The solution is to start ADB in root mode in command prompt...
Steps I did with my Galaxy S to add an App:
1. Connect phone to computer via USB in Debug Mode
2. Load command prompt and type: adb root
3. set read/write for system folder:
adb shell
su
Then type mount and find the location of system folder, in this case for me it's /dev/block/stl9
mount -o remount,rw /dev/block/stl9 /system
exit
exit
4. set your cmd prompt to folder where you have files to push/move onto phone i.e. f:\app or etc using f: and cd app for example
5. then to copy files to system/app folder by typing type: adb push <appfilename>.apk /system/app
Voila!
To remove an app do the following: adb shell rm /system/app/YourApplicationHere.apk
Simples
As a noob it took some time to figure this out with some help here and reading the help info after typing adb in prompt and the Eureka! moment came...
Hope this helps
Peter
ADB or term emu on device
HTC Vision 1.8 OC, CM7 RC1==HAPPY!!
OK...I'm beginning to think that rooting is not for me!!!! Getting a bit frustrated!!!
OK, so I installed SDK on my pc (Win XP Ver 2002 SP3), and I cannot get it recognize the device.
I tried the guide for dummies here on XDA, and I follow all the indications, server starts up, I can kill it too....but every time I try to run it I get:
"error: device cannot be found"
The line that I am writing is as follows:
Code:
c:\android-sdk-windows\tools>adb shell
and I get the error above.
When I try to see if devices are connected, and Use this:
Code:
c:\android-sdk-windows\tools>adb devices
I get:
"List of Devices attached", but there is no list!!!!!
But I can see the SDCARD from my computer....I can access the files...
Maybe I can try to pull instead of push, but I'm not sure how that would be written (line wise), not if will work.
BTW...I have never done anything like this on android....very new to this!!!!
umm.. HELP!!!
OK changed pc's,....on this one it does recognize the device, but does not allow me to push anything.....when i try:
Code:
adb push su /sdcard/su
I get adb: permissions denied
------
I tried su +, and that got me to the # prompt. So I tried typing
Code:
# adb push su /sdcard/su
and I get adb: not found???
Running out of options here!
...
Thanks!
I think you are mounting the sdcard. You don't want to do that. Just connect your phone to the computer and run ADB. Don't click "USB Connected. Select to copy files to/from your computer" on your phone.
funkeee said:
I think you are mounting the sdcard. You don't want to do that. Just connect your phone to the computer and run ADB. Don't click "USB Connected. Select to copy files to/from your computer" on your phone.
Click to expand...
Click to collapse
Funkeeeeeee thank you for the reply.
OK...I am not getting an option when I connect to the pc..on the one I get it, I shose do nothing. I have also disabled mass storage on the device once loaded, adn I get the same error. Here is some of the code that I get thorught the PC's terminal:
C:\>cd android-sdk-windows\tools
C:\android-sdk-windows\tools>adb devices
List of devices attached
HT09YR200737 device
C:\android-sdk-windows\tools>adb shell
$ adb push su /sdcard/su
adb push su /sdcard/su
adb: permission denied
$ adb kill-server
adb kill-server
adb: permission denied
$
Click to expand...
Click to collapse
Notice that once I get the initial permission denied, the terminal seems to get locked up on that no matter what I type....see above...
Anything else to try??? AM I missing something here?
That's fine. There are a few things I can suggest for you to try..
First, I want you to enable USB debugging on your phone by going to Settings > Applications > Development and check that first option.
Then connect the phonoe, but don't use 'adb shell' before pushing files. It should look like this:
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Funkz>cd c:\g2
c:\g2>adb pull /system/build.prop
501 KB/s (3596 bytes in 0.007s)
c:\g2>
Click to expand...
Click to collapse
If you are trying to run it from within adb shell, it will spit back 'adb: not found.' That should do fix it for you.
If it does not, go to Control Panel > System > Advanced > Environment Variables. Then click on Path and Edit, then ";C:\android-sdk-windows\tools\" at the very end and try again.
By the way, you don't have to run adb from the installation directory. After adding the path I just mentioned, you should be able to run it from anywhere.
funkeee said:
That's fine. There are a few things I can suggest for you to try..
First, I want you to enable USB debugging on your phone by going to Settings > Applications > Development and check that first option.
Then connect the phonoe, but don't use 'adb shell' before pushing files. It should look like this:
If you are trying to run it from within adb shell, it will spit back 'adb: not found.' That should do fix it for you.
If it does not, go to Control Panel > System > Advanced > Environment Variables. Then click on Path and Edit, then ";C:\android-sdk-windows\tools\" at the very end and try again.
By the way, you don't have to run adb from the installation directory. After adding the path I just mentioned, you should be able to run it from anywhere.
Click to expand...
Click to collapse
Thanks.....I finally can run it without having to type the entire path!!!! That was great help!!!
AS for the permission denied.....still having that issue! The one thing I didn't understand was when you changed the path to >g2.....what do you mean???? path to be g2?
Thanks again for the help!
Just a note...I am trying to do this post OTA, which I downloaded, never got the push...Would having the OTA have any effect on this? DO I need to consider reverting to stock and trying from there? If so how? run recovery?
Dude thanks for the help!
did you try typing SU? IMO you cant tamper with ADB Shell if you dont have su access so try typing down SU to ask for permission.
Alright first things first. ADB requires special drivers to work. Which is probably why it didn't work on the original PC. If you download the PDANet client on the PC that you need to do adb it will install the necessary drivers and you can uninstall the program without losing the drivers.
Another ADB requirement is to enable USB Debugging. MENU>Settings>Applications>Development and check the USB Debugging Box.
I don't know about anyone else but with my phone will automount the card. It is recommended to pull down the notification bar and make sure that your SD card isn't mounted.
You need to navigate your command prompt to whatever folder you keep ADB.exe for me
Code:
C:\Users\etnie>cd C:\Users\etnie\Downloads\G2\Android\tools
for me this returns
Code:
C:\Users\etnie\Downloads\G2\Android\tools>
to confirm this
Code:
C:\Users\etnie\Downloads\G2\Android\tools>adb devices
I won't post all the code but it should start the daemon successfully and list your device.
to be able to push files to your phone they also need to be in the same folder as the ADB.exe ie the tools folder. of course you can push it from any folder if you type the full path
Code:
C:\Users\etnie\Downloads\G2\Android\tools>adb push C:\Users\etnie\Downloads\G2\bootanimation.zip /data/local
the above code would push the bootanimation.zip from my G2 folder located in my Downloads folder to /data/local on the phone. changing the boot screen animation when you turn on the phone. I actually have the BIOS one. Because I am huge nerd lol. Moving on...
I think I covered everything necessary....If you are still having problems either PM me or reply here.
Thanks guys for the replays...here are some comments...
Acid_Wir3 said:
did you try typing SU? IMO you cant tamper with ADB Shell if you dont have su access so try typing down SU to ask for permission.
Click to expand...
Click to collapse
I have tried SU, and it does grant access, BUT!!!! so here is what happens...
I get to .....\tools> adb shell ... then i get.... the $ prompt. At this point I type $su .... then my prompt changes from $ to #. I understand that it should be $ # In any case once I get to # it says adb: not found code looks like this:
Code:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\carlos>cd\
C:\>adb shell
$ su
su
# adb push su /sdcard/su
adb push su /sdcard/su
adb: not found
#
BTW, the path has been predfined to C:\android-sdk-windows\tools\
Not sure how to navigate from #prompt
RuncaProfundus said:
1Alright first things first. ADB requires special drivers to work. Which is probably why it didn't work on the original PC. If you download the PDANet client on the PC that you need to do adb it will install the necessary drivers and you can uninstall the program without losing the drivers.
2Another ADB requirement is to enable USB Debugging. MENU>Settings>Applications>Development and check the USB Debugging Box.
3I don't know about anyone else but with my phone will automount the card. It is recommended to pull down the notification bar and make sure that your SD card isn't mounted.
4 You need to navigate your command prompt to whatever folder you keep ADB.exe for me
Code:
C:\Users\etnie>cd C:\Users\etnie\Downloads\G2\Android\tools
for me this returns
Code:
C:\Users\etnie\Downloads\G2\Android\tools>
to confirm this
Code:
C:\Users\etnie\Downloads\G2\Android\tools>adb devices
I won't post all the code but it should start the daemon successfully and list your device.
to be able to push files to your phone they also need to be in the same folder as the ADB.exe ie the tools folder. of course you can push it from any folder if you type the full path
Code:
C:\Users\etnie\Downloads\G2\Android\tools>adb push C:\Users\etnie\Downloads\G2\bootanimation.zip /data/local
the above code would push the bootanimation.zip from my G2 folder located in my Downloads folder to /data/local on the phone. changing the boot screen animation when you turn on the phone. I actually have the BIOS one. Because I am huge nerd lol. Moving on...
I think I covered everything necessary....If you are still having problems either PM me or reply here.
Click to expand...
Click to collapse
Runca thanks for the detailed reply....going in order here:
1 - I did and I still have pdanet isntalled
2 - it's been like that since the first day I got the phone.
3 - How do I ensure??? you are talking about from the phone....I should turn off USB Storage? Will try this one.
UPDATE: tried unmounting and re running without success....
Code:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\carlos>cd\
C:\>adb shell
$ adb push su /sdcard/su
adb push su /sdcard/su
adb: permission denied
$
4 - It's pretty much what I have. Other that I'm not running su before doing so......
Any thoughts?
Crey23 said:
AS for the permission denied.....still having that issue! The one thing I didn't understand was when you changed the path to >g2.....what do you mean???? path to be g2?
Click to expand...
Click to collapse
The "g2> " bit is just his command prompt. He's changed directory to one called "g2" on his phone but that's nothing to do with how adb works etc (just that if he pushes or pulls files then that'll be the current directory on the PC for that).
Crey23 said:
Code:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\carlos>cd\
C:\>adb shell
$ su
su
# adb push su /sdcard/su
adb push su /sdcard/su
adb: not found
#
Click to expand...
Click to collapse
Those "adb push" commands should be done from your PC's command prompt, not from within an Android shell prompt on your phone.
"adb shell" starts a command shell on the phone. Which is fine for doing some stuff. But "adb" commands won't work because now you're issuing them to your phone, not your PC.
steviewevie said:
Those "adb push" commands should be done from your PC's command prompt, not from within an Android shell prompt on your phone.
"adb shell" starts a command shell on the phone. Which is fine for doing some stuff. But "adb" commands won't work because now you're issuing them to your phone, not your PC.
Click to expand...
Click to collapse
Thanks Steve.....that makes a lot of sense, and in part why i am a bit lost here....but knowing that....how can I get to "push" things to my phone?
Don't run the adb shell command. That takes you into the phone's prompt. Any commands you run from adb shell with $ or # are run within the phone. You want to run adb push from command prompt. Look at my previous post. It should look like:
C:/>adb push ...
not
#adb push...
Sent from my HTC Vision using XDA App
Funkeee,x thank you I will try that as soon as I can.
funkeee said:
Don't run the adb shell command. That takes you into the phone's prompt. Any commands you run from adb shell with $ or # are run within the phone. You want to run adb push from command prompt. Look at my previous post. It should look like:
C:/>adb push ...
not
#adb push...
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Sent from my T-Mobile G2 using XDA App
Finally progress
Guys thank you for your help!!!!!
I was finally able to push all the files to the phone. Now my problem has changed..., still dealing with Permission denied....when executing rage I get a buch of errors, please see image:
Code:
$ $su
# /data/local/tmp/rage
I get this.....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I then figured that since I was temp rooted through Visionary r10, that was the reason for the errors above. I then proceeded to reboot without temp-rooting.
When I come up to the terminal I get:
Code:
export PATH=/data/local/bin:$PATH
$ $su
su: permission denied
$
SO if I understand this correctly, I need NOT be temp-rooted in order to run rage, but if I'm not temp-rooted, I don't have permissions to get to execute rage....there a chicken and egg story here somewhere! lol
Can I use a hybrid of the visionary temp root and perm root in that post?
From what I recall you need to uninstall visionary and reboot prior to using the rage method.
Sent from my HTC Vision using XDA App
Thanks funkeee...I will try in the morning.
But part of the problem is that without visionary I cannot get su access to run any of this. I'll backup VIS r10 before removing, and try again.
I post my results...goodnight and thanks!
funkeee said:
From what I recall you need to uninstall visionary and reboot prior to using the rage method.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Sent from my T-Mobile G2 using XDA App
I looked at the rage instructions and the prompt is misleading. You may forgetting to use chmod to change permssions. I've put my version of the instructions (just the start).
Uninstall visionary, reboot and from command prompt on your pc, navigate to the folder where you have these files and run:
c:/> adb push su /sdcard/su
c:/> adb push Superuser.apk /sdcard/Superuser.apk
c:/> adb push rage /data/local/tmp/rage
c:/> adb push busybox /data/local/tmp/busybox
c:/> adb push root /data/local/tmp/root
c:/> adb shell chmod 0755 /data/local/tmp/*
Don't forget the last entry, which changes the permissions.
Then on your phone, open terminal and put in:
$ /data/local/tmp/rage
It will say Forked Childs...
Then Menu > Reset Term. It will close, then launch terminal again, it will force close and then launch it again and you will have rage root.
If you get to there, you're in good shape. You can then follow those instructions to to push hboot and wpthis. Be careful with the dd command and be sure you have it exactly right. There are no do-overs with 'dd'.
http://forum.xda-developers.com/showthread.php?t=834228
Thanks man I will try it shortly.
funkeee said:
I looked at the rage instructions and the prompt is misleading. You may forgetting to use chmod to change permssions. I've put my version of the instructions (just the start).
Uninstall visionary, reboot and from command prompt on your pc, navigate to the folder where you have these files and run:
c:/> adb push su /sdcard/su
c:/> adb push Superuser.apk /sdcard/Superuser.apk
c:/> adb push rage /data/local/tmp/rage
c:/> adb push busybox /data/local/tmp/busybox
c:/> adb push root /data/local/tmp/root
c:/> adb shell chmod 0755 /data/local/tmp/*
Don't forget the last entry, which changes the permissions.
Click to expand...
Click to collapse
Up to here I am fine.
funkeee said:
Then on your phone, open terminal and put in:
$ /data/local/tmp/rage
It will say Forked Childs...
Then Menu > Reset Term. It will close, then launch terminal again, it will force close and then launch it again and you will have rage root.
If you get to there, you're in good shape. You can then follow those instructions to to push hboot and wpthis. Be careful with the dd command and be sure you have it exactly right. There are no do-overs with 'dd'.
http://forum.xda-developers.com/showthread.php?t=834228
Click to expand...
Click to collapse
But is with this part that I have issues with......
I uninstalled VISONary as suggested, and I got the same result as before.....error, error, error.....permission denied! Basically without visionary and su I cannot get access to the run rage. I gave me this error:
Code:
$ /data/local/tmp/rage
/data/local/tmp/rage: /data/local/tmp/busybox: permission denied
mount: Operation not permitted
mkdir failed for /system/xbin, Read-only file system
/data/local/tmp/rage: /data/local/tmp/busybox: permission denied
Unable to chmod /system/xbin/busybox: no such file or directory
/data/local/tmp/rage: /data/local/tmp/busybox: not found
cp: Permission denied
cp: Permission denied
Unable to chmod /system/xbin/su: no such file or directory
Mount: Operation not permitted
$
SO as i interpret this as I dont have the rights or permission to run the rage script. What puzzles me is the fact the it cannot "mount" the sdcard...after running this, I cannot take a picture (screenshot) bcs it does not recognize the sdcard. I have to Reboot.
Any ideas?
Thanks!
Crey23 said:
Up to here I am fine.
But is with this part that I have issues with......
Code:
$ /data/local/tmp/rage
/data/local/tmp/rage: /data/local/tmp/busybox: permission denied
mount: Operation not permitted
mkdir failed for /system/xbin, Read-only file system
/data/local/tmp/rage: /data/local/tmp/busybox: permission denied
Unable to chmod /system/xbin/busybox: no such file or directory
/data/local/tmp/rage: /data/local/tmp/busybox: not found
cp: Permission denied
cp: Permission denied
Unable to chmod /system/xbin/su: no such file or directory
Mount: Operation not permitted
$
Click to expand...
Click to collapse
I think there's something majorly wrong here. Funny, I saw someone else with a similar problem recently. It looks like when you're running "rage" it's actually running the "root" script that you use at a later stage, and not "rage" at all. Double check what you've got, I think "rage" is a binary and not a script. Are you sure you didn't push "root" to "rage" ?
Please help, I've searched around and can't find the solution to my issue, I'm rooting following the XDA wiki for Gfree and using the Android SDK....I've managed to get the ADB to recognize my phone and I "think" that the ADB has been able to push the first 5 files to the SD....but I'm stuck on the last command line.
$ adb push su /sdcard/su
$ adb push Superuser.apk /sdcard/Superuser.apk
$ adb push rage /data/local/tmp/rage
$ adb push busybox /data/local/tmp/busybox
$ adb push root /data/local/tmp/root
$ adb shell chmod 0755 /data/local/tmp/*
when I run $ adb shell chmod 0755 /data/local/tmp/*
I get the following:
Usage: chmod <MODE> <File>
so then I go to terminal emulator on the phone and type
$ /data/local/tmp/rage
I get: /data/local/tmp/rage: not found
Where have I screwed up?
G2_Gordon_G1 said:
Please help, I've searched around and can't find the solution to my issue, I'm rooting following the XDA wiki for Gfree and using the Android SDK....I've managed to get the ADB to recognize my phone and I "think" that the ADB has been able to push the first 5 files to the SD....but I'm stuck on the last command line.
$ adb push su /sdcard/su
$ adb push Superuser.apk /sdcard/Superuser.apk
$ adb push rage /data/local/tmp/rage
$ adb push busybox /data/local/tmp/busybox
$ adb push root /data/local/tmp/root
$ adb shell chmod 0755 /data/local/tmp/*
when I run $ adb shell chmod 0755 /data/local/tmp/*
I get the following:
Usage: chmod <MODE> <File>
so then I go to terminal emulator on the phone and type
$ /data/local/tmp/rage
I get: /data/local/tmp/rage: not found
Where have I screwed up?
Click to expand...
Click to collapse
looks like you screwed up the last command ... didnt write the syntax properly thats why it showed its usage.....
(adb shell chmod 0755 /data/local/tmp/*) this command that is.....
also the last thing showing file not found means the files were never pushed to the phone..... connect your phone to your pc in chagre only and usb debigging connected mode and in command prompt in the adb folder write "adb devices"
it should show somehting like this.....
adb list of devices attached
SH034N34GF
this number over here (SH034N34GF) is an example ... it will show your phone ID... which would be different....
if you see list of devices attached and an empty line below and no serial number as shown in example....
than it means your android usb drivers for adb shell are not set up correctly
in that case ... get the drivers set up properly....
check with adb devices command to confirm your phone is recognized....
than start over with the commands
I've started over and have typed VERY CAREFULLY...
On each of the first five command prompts I get a 40 or so line message that starts with:
Android Debug Bridge version 1.0.26
.......
(list of commands)
.......
and ends with
bug tags are printed.
OK so I guess that's good
So then I type C:\> adb shell chmod 0755 /data/local/tmp/*
and NOW I get
adb server is out of date. killing...
*daemon started successfully*
Bad Mode
Clearly, I'm a noob.....
Now what?
read this guide .... on it search for .... "out of date" author explains how to tackle it
G2_Gordon_G1 said:
I've started over and have typed VERY CAREFULLY...
On each of the first five command prompts I get a 40 or so line message that starts with:
Android Debug Bridge version 1.0.26
.......
(list of commands)
.......
and ends with
bug tags are printed.
OK so I guess that's good
So then I type C:\> adb shell chmod 0755 /data/local/tmp/*
and NOW I get
adb server is out of date. killing...
*daemon started successfully*
Bad Mode
Clearly, I'm a noob.....
Now what?
Click to expand...
Click to collapse
hispeedworm said:
read this guide .... on it search for .... "out of date" author explains how to tackle it
Click to expand...
Click to collapse
In the ADB guide it says:
"By the way, the first adb command that you type may well also come up with some lines similar to "adb deamon out of date" etc, but don't worry, that's normal, just check the rest of the output."
So apparently that's not a problem?
G2_Gordon_G1 said:
In the ADB guide it says:
"By the way, the first adb command that you type may well also come up with some lines similar to "adb deamon out of date" etc, but don't worry, that's normal, just check the rest of the output."
So apparently that's not a problem?
Click to expand...
Click to collapse
im uploading my adb... its minimal with just adb fastboot and few other files.... unzip into a folder on your pc.....use these instead of the android sdk and all..
make sure that folder is linked in windows..... Step 4 of the adb for noobs guide..... reinstall the android usb drivers again following the guide.....
when thats done restart and press F8 ... disable signature verification ... when windows loaded... go to command prompt.... do into the adb directory.....than write adb devices....if it shows you device than start over with the commands.... you should not get the error saying out of date... as i just used this adb shell 2 days back to root my desire Z.....
hope this helps
Thanks! Will try again soon!
So I am trying to manually root my S3 without flashing a rom. I am able to get through most of the steps in these instructions up to the point where it requires you to put phone into download mode. I get phone into download mode, but when I connect to the PC, it doesn't see the phone.
This step worked:
To confirm your device is properly detected, in the command prompt, run
Code:
adb devices
Now copy busybox, su, superuser.apk to /data/local/tmp/ using adb.
Code:
adb push busybox /data/local/tmp adb push su /data/local/tmp adb push Superuser.apk /data/local/tmp
These steps worked:
Now run adb shell
Code:
adb shell
Note that you see a "$" sign in the command prompt. That means you are not rooted.
Next run the following commands in the shell to change permissions and get some limited privileges for the Superuser files:
Code:
chmod 6755 /data/local/tmp/su chmod 755 /data/local/tmp/busybox chmod 644 /data/local/tmp/Superuser.apk
Note that the names of the files are case sensitive.
Files are there and are verified when I ls /data/local/tmp. All three files are there.
This is where I have a stumbling block:
Once in download mode, connect the Android device using the microusb cable to the computer.
Now using the open Nautilus window, navigate to /UserData/local/tmp/ folder and verify that you have the files you sent to the device viz. su, busybox and Superuser.apk
So if I am able to push files to the phone, why won't it recognize it when in download mode?
Using Fedora Linux and have the full Android SDK installed.
Hi all, I have the following strange behavior when I want to use ADB:
(my device is Desire HD with 4.0.4, usb deb. is enabled, OS is win7 x64, Android Phone driver in dev manager is "My HTC" but I tried changing it with "ADB composite interface" or something like that but with the same result...)
When I start CMD (adb is registered in "Environment variables") and type "adb devices", my device is listed, but right after that when I type ""ADB shell" (daemon is restarting at this point) followed by "adb devices", my device is listed as empty entry (no device name) and some adb shell commands give me trouble (they don't work, push doesn't work and install apk is working fine).....
Main problem is that I want to use androidscreencast but I'm unable to execute
adb shell
su
chmod 777 /data/dalvik-cache
cd /data/dalvik-cache
chmod 777 ./
No errors, no results?
Any ideas?
chmod 777 /data/dalvik-cache/*
Is right
Sent from my HTC Desire X using xda premium