Ok trying to learn a little about adb. and im trying to push a file to my phone.
cd c:\android-sdk-windows\tools ( done this to change the directory)
c:\android-sdk-windows\tools>adb push screengrab.apk .\sdcard.
failed to copy screengrabber.apk to .\sd card: Read-only file system
how do i change it to a write only file system also. i tryed adb shell i granted it SU permissions. then i done something and its telling me daemon still not runningerror cannot connect to daemon. what exactly does this mean it will start up successfully then it will stop and that message will come up
your sdcard is not read only. make sure you do not have it mounted at all on your computer and verify you are using PROPER command
adb push screengrab.apk /sdcard/
Pirateghost said:
your sdcard is not read only. make sure you do not have it mounted at all on your computer and verify you are using PROPER command
adb push screengrab.apk /sdcard/
Click to expand...
Click to collapse
there is nothing mounted in my pc not internal or sd card when i used the PROPER command. It brings up a whole lot of stuff like the different commands and stuff.
Related
I seem to be having trouble using the same commands I used to use on my G1.
I used to be able to copy via terminal (cp) and I was able to mount with a simple declaration "mount system" and "mount sdcard". Is that something that was created later on during the life of the G1 and still has yet to make it to the N1 or is it just a whole different set of commands?
I know the move command works in terminal (mv), but I haven't been able to use anything else. I couldn't even use ADB to pull something, is this correct?
(after su and mounting, mount -o rw,remount /dev...etc...)
adb-windows pull /system/build.prop c:/
I keep getting an error, no such file or directory. What am I doing wrong?
do you get a response with adb device? if not, then you don't have a bridge. if you don't have a bridge, you can't give commands
I get a response. "adb-windows devices" detects the device and I can mount the system folder as well as being able to enter adb shell, I just can't seem to get the usual commands (ones I would use with the G1 and adb/terminal) to work.
Hey Boys and Girls,
where i can find an manual to root the tattoo with a mac?
sorry, i have search for this, but i cant find information for this
I don't thing that there is a difference.
As soon as you have SDK installed and adb works, the commands are the same.
hi,
i'm also doing all the rooting process from mac, just put the directory contain 'adb' shell into your home/user places and executing it with 'terminal'..
Same here, using a Mac ever since and also using it for Android development. Due to the underlying Unix core of OS X you just have to follow the steps as described for Linux. If it's just adb commands it's the same on every platform anyway.
You might want to add a
Code:
export PATH=${PATH}:/Users/yourusername/android.sdk/tools
to your .bash_profile file in your home folder so you don't have to cd to the SDK tools folder everytime. Happy rooting!
Mod. edit: not dev related, moved to general
Okay thanks for yours answers but i'm a newbie.
the background story is, I want to edit the boot.mp3. Because the startsound is really annoying
So i have download SDK, open the terminal and switch to usb-debbugging mode on my tattoo.
And now? sorry, I'm still missing a few knowledge
thanks for your help
well just use the various adb commands in Terminal Just type in "adb", press enter and you'll get a list of all possible commands. Assuming you've added the path to your sdk tools folder to your bash profile. Otherwise just drag & drop the adb binary from the tools folder onto your Terminal window, et voila.
The most used commands are probably push and pull where you can, well, push stuff to your phone or pull it to your computer.
So if you want to modify the boot.mp3 you would pull the original from the phone to your computer, modify it and push it back, overwriting the original file. In Terminal speak: ;-)
adb pull /system/media/bootscreen/boot.mp3
adb push /path/to/boot.mp3 /system/media/bootscreen/boot.mp3
Please note depending on the ROM you're using the paths may be different. To browse the device via Terminal type in "adb shell" and make a simple "ls" to list the directories, "cd" to change directories etc.
Or if you just want to use another mp3:
adb push /path/to/whatever.mp3 /system/media/bootscreen/boot.mp3
Again, on the Mac you can just drag & drop files onto the Terminal to get their full Unix paths like to your custom mp3
Thanks a lot. i love it its really simple
and now i have load and edit the the boot.mp3. But i can't push it to my tattoo, because i can only read but not write
I have tried to root my phone with "adb root" but it is the message "adbd cannot run as root in production builds"
Terminal: "adb remount", then push again
damn the next bad message "remount failed: Operation not permitted"
You need to root your phone first.
http://forum.xda-developers.com/showthread.php?t=637927
Okay i have executed the instructions. But I've stop at this part:
You should get something like this:
Code:
# id
uid=0(root) gid=1000(shell) groups=1003(graphics),1004(input),1007(log),1011(adb),1015(sdcard_rw),3001(net_bt_admin),3002(net_bt),3003(inet)
uid=0(root) is important.
Click to expand...
Click to collapse
Yes i've root but i'cant download the "su binary" because its doesnt exist.
But its absolute essential to need the "su binary" to only copy the boot.mp3 to my phone? Or there is an other way? What are the commands to push the boot.mp3 back to may tattoo then i'm in the root mode like >> "#".
okay hope you understand me
You need "su" to do root stuff... no other way.
Download the package from 1 click root thread and find "su" there...
http://forum.xda-developers.com/showthread.php?t=644279
now, i have install the su binary. Then i does this command
user:~ user$ /Users/user/android-sdk-mac_86/tools/adb shell
$ /data/local/bin/su
#
Click to expand...
Click to collapse
And now? Is there a comand to push the boot.mp3 back to the phone in this mode >> "#" ?
I have try to open an new terminal window and type
adb push /path/to/boot.mp3 /system/media/bootscreen/boot.mp3
Click to expand...
Click to collapse
but the answer is
failed to copy '/Users/android-sdk-mac_86/boot.mp3' to '/system/media/bootscreen/boot.mp3': Permission denied
Click to expand...
Click to collapse
and adb remount doesnt work to
You also need tattoo-hack.ko file and do insmod tattoo-hack.ko to make /system writable.
Or even better... flash custom amon_ra recovery image and then a custom rom with all this already included.
Mine for example http://forum.xda-developers.com/showthread.php?t=702401
It doesnt have boot sound enabled
Okay thank you very much.
now it was successful
Ok. So im touching up on my ADB. Messing around trying to transfer files and what not. Now when I try and push and file from my pc to my sdcard it errors me out saying Read-Only File System.
Command im doing is
adb push C:\Android\android.jpg /sdcard/android.jpg
Any ideas where im going wrong here? I have full root access, When I:
adb shell
su
I do not get permission denied... So dont get why this is happening.
Edit: Just looked more into it. I can push to the phone. Just not to the sdcard. I pushed to /data/local for giggles and it worked. Only gives me read only when pushing to the /sdcard.
Thanks for any info.
just tried mine and it worked fine. I first tried it with pushing a file from my sdk dir, and tried it with pushing a file from another directory on the drive. worked both times, not sure what to tell you.
p.s. I'm running the desire z rom
Yeah for some reason its only on the sdcard I cant write to.. USB Debugging is checked. Anyone have the slightest idea as to why I'm unable to write to my sdcard with this Read-only File system error?
Anyone know the shell command to mount the sd card as rw? Been trying to figure this thing out but it has me in a puzzle.
[G2/HTC Vision]
luis86dr said:
Anyone know the shell command to mount the sd card as rw? Been trying to figure this thing out but it has me in a puzzle.
[G2/HTC Vision]
Click to expand...
Click to collapse
Are you making sure that you don't have media mounted? That would screw up /sdcard. For me, it's "umount /media/*; eject /dev/sde" then on the G2 disable USB storage, wait for it to remount the SD card.
If that still doesn't work, what does "adb shell mount" tell you?
Normally, like with /system, it's "busybox mount -o remount,rw /system", but I've never seen /sdcard mounted readonly, unless there are I/O errors (it's mounted to remount ro on failure). Have you tried rebooting your phone?
luis86dr said:
Ok. So im touching up on my ADB. Messing around trying to transfer files and what not. Now when I try and push and file from my pc to my sdcard it errors me out saying Read-Only File System.
Command im doing is
adb push C:\Android\android.jpg /sdcard/android.jpg
Any ideas where im going wrong here? I have full root access, When I:
adb shell
su
I do not get permission denied... So dont get why this is happening.
Edit: Just looked more into it. I can push to the phone. Just not to the sdcard. I pushed to /data/local for giggles and it worked. Only gives me read only when pushing to the /sdcard.
Thanks for any info.
Click to expand...
Click to collapse
Is it possible that you are writing the command wrong? I noticed the slash is opposite on the second half of your command code.
C:\Android\android.jpg /sdcard/android.jpg
Click to expand...
Click to collapse
Figured it out. Had usb storage on. So it wouldn't push turned it off and I was able to push. Thx foe the info
[G2/HTC Vision]
I rooted my Shift sucessfully but I can't seem to backup my WiMAX keys. I adb shell and su work just fine, but both:
dd if=/dev/block/mmcblk0p25 of=/sdcard/WiMax/wimax.bin
and
dd if=/dev/block/mmcblk0p30 of=/sdcard/WiMax/udata_wimax.bin
come back with an error saying ...wimax.bin cannot open for write, no such file or directory. Am I forgetting a step, or doing something wrong? I tried this in both charging and usb drive modes.
Thanks in advance
EmptyCloud said:
I rooted my Shift sucessfully but I can't seem to backup my WiMAX keys. I adb shell and su work just fine, but both:
dd if=/dev/block/mmcblk0p25 of=/sdcard/WiMax/wimax.bin
and
dd if=/dev/block/mmcblk0p30 of=/sdcard/WiMax/udata_wimax.bin
come back with an error saying ...wimax.bin cannot open for write, no such file or directory. Am I forgetting a step, or doing something wrong? I tried this in both charging and usb drive modes.
Thanks in advance
Click to expand...
Click to collapse
Are you sure you have the sdcard mounted for writing? Also, make sure you have a directory called /sdcard/WiMax - the guide states to put it in /sdcard/Shift, but I guess you could just put it anywhere.
I think the SD card is mounted for write. I can throw stuff on it using my computer, but I don't know how to check if adb can write to it as after I enable su in the shell, I don't know the syntax for using adb push or pull.
EmptyCloud said:
I think the SD card is mounted for write. I can throw stuff on it using my computer, but I don't know how to check if adb can write to it as after I enable su in the shell, I don't know the syntax for using adb push or pull.
Click to expand...
Click to collapse
Make sure you don't have it mounted via USB on your PC while you are trying to do this - you should have USB as "Charging Only." Otherwise, you can't write to the SD card from your phone using adb because it is mounted on your PC.
Just rebooted my phone twice and it worked after second boot. Thanks for the heads up that it only works in charge mode as I'd been trying in both modes
To start off I want to say, I am NOT claiming to have created this exploit, I am merely letting people know that it works on the arc.
All credit for this goes to Chainfire and The Android Exploid Crew
The origional thread is here: http://forum.xda-developers.com/showthread.php?t=1044765
Download here
Install the APK and run it.
For people getting "could not extract assets" error execute
adb shell rmdir /data/local/tmp
and then
adb shell mkdir /data/local/tmp
Click to expand...
Click to collapse
Quote posted by jassired
works for me
So just push the apk to the phone, install and you're done?
no need to "push", just stick it on your sd card and install
diggedy said:
no need to "push", just stick it on your sd card and install
Click to expand...
Click to collapse
I get the error thing...and I can't find the effing map where I need to remove stuff....
where do I find the god damned map to remove the files I need to remove when it only fails to install?????
I've checked every single map on the memory card, going nuts here...
Cim_XII said:
where do I find the god damned map to remove the files I need to remove when it only fails to install?????
I've checked every single map on the memory card, going nuts here...
Click to expand...
Click to collapse
What do you mean?
double post :s will use this later
I have put the .apk in my download map on the sd card of the phone, installed the apk and run it and I get the: "could not extract assets" error execute
and then when I get that I am supposed to remove some files from a map on the sd card, and I cannot find said map....I hava rebooted the phone, and I still cannot find data/local/tmp or what ever map I need to find.....
Cim_XII said:
I have put the .apk in my download map on the sd card of the phone, installed the apk and run it and I get the: "could not extract assets" error execute
and then when I get that I am supposed to remove some files from a map on the sd card, and I cannot find said map....I hava rebooted the phone, and I still cannot find data/local/tmp or what ever map I need to find.....
Click to expand...
Click to collapse
you need to execute the commands in the origional post via ADB with USB debugging enabled, because the location is in the system and ironicly you dont have the root privelages to delete them
I don't even know what ADB is....that's how much I know...
Cim_XII said:
I don't even know what ADB is....that's how much I know...
Click to expand...
Click to collapse
I have attached it to this post. ADB is the Android Debug Bridge. It is used to excecute commands on android devices. Just extract the zip, then open a command prompt and change to the directory of ADB, then excecute the commands.
if you get the error for esset you need to remove all the files inside to /data/local/tmp/
press: adb shell
press ls /data/local/tmp
and remove one by one the files as my example:
$ ls /data/local/tmp/
ls /data/local/tmp/
Superuser.apk
Gingerbreak
runscript
sysrun
$ rm /data/local/tmp/Superuser.apk
rm /data/local/tmp/Superuser.apk
$ rm /data/local/tmp/Gingerbreak
rm /data/local/tmp/Gingerbreak
$ rm /data/local/tmp/runscript
rm /data/local/tmp/runscript
$ rm /data/local/tmp/sysrun
rm /data/local/tmp/sysrun
and now try again with app and may it works (in my case, works)
dh2311 said:
I have attached it to this post. ADB is the Android Debug Bridge. It is used to excecute commands on android devices. Just extract the zip, then open a command prompt and change to the directory of ADB, then excecute the commands.
Click to expand...
Click to collapse
maybe I should've mentioned I'm on a Mac computer with no access to windows....damn, this is so frustrating....
Ah... Its still possible you just have to get the android sdk for mac.
Get the SDK from here
Then in the tools folder ADB should be there
Then its commands as normal I think... not sure tho, don't have a mac.
Search around on here for tutorials, I'm sure someone has put up a tutorial on setting up adb on mac
dh2311 said:
Ah... Its still possible you just have to get the android sdk for mac.
Get the SDK from here
Then in the tools folder ADB should be there
Then its commands as normal I think... not sure tho, don't have a mac.
Search around on here for tutorials, I'm sure someone has put up a tutorial on setting up adb on mac
Click to expand...
Click to collapse
kewl, and the exact commands is in post #1 right?
so this root's the OS, title is confusing, does it enable fastboot? allow you to flash custom roms?
should be....
dh2311 said:
you need to execute the commands in the origional post via ADB with USB debugging enabled, because the location is in the system and ironicly you dont have the root privelages to delete them
Click to expand...
Click to collapse
did exactly what you said, but get the message
adb: permission denied
No does not enable fastboot