[Q] Copy files from device to pc hdd via adb shell - Android Q&A, Help & Troubleshooting

I am having trouble finding the right command to copy a file from a device via adb shell to my pc. I tried -mv- but that just renamed it.
Code:
mv Camera c:/camera
renamed to c:camera

adb pull /path/to/Camera C:\camera

RoberGalarga said:
adb pull /path/to/Camera C:\camera
Click to expand...
Click to collapse
yeah I tried that. I think that since my phone is locked, I can't su the shell. I actually tried a single file also. No luck.

das-heftige said:
yeah I tried that. I think that since my phone is locked, I can't su the shell. I actually tried a single file also. No luck.
Click to expand...
Click to collapse
I don't have to unlock my tablet to pull files. You are doing the command from the PC, right, like in a DOS box? You should be able to see the files by doing "adb shell ls /sdcard/DCIM/Camera/". "adb pull /sdcard2/DCIM/Camera ." will pull all of the pictures on my Hisense external sdcard into the current "." windows directory on my computer.

BSODs when using usb 3.0
das-heftige said:
I am having trouble finding the right command to copy a file from a device via adb shell to my pc. I tried -mv- but that just renamed it.
Code:
mv Camera c:/camera
renamed to c:camera
Click to expand...
Click to collapse
Hi,
I have facing out weird problem. Why, when i using adb command to copy file from PC windows to android Devices using Port usb 3.0. Windows will be immediately Blue Screen. Note: in blue screen appears, Bluescreen: Physical Memory Dump
I using Windows 7 (Zotac CPU). But, when i using standart USB port in zotac. Will be running.
Anyone knows, why the problem appears?
Thanks

Android All In One Toolkit - Data Transfer Via ADB
das-heftige said:
I am having trouble finding the right command to copy a file from a device via adb shell to my pc. I tried -mv- but that just renamed it.
Code:
mv Camera c:/camera
renamed to c:camera
Click to expand...
Click to collapse
Hii
I Developed an application named "Android All In One Toolkit" With Windows GUI...
1. Data Transfer
{
"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"
}
No Need to type single command
just put path in text box & Press Pull From Device button..
It has feature for fast data transfer over adb without mounting sd card...
It also has many more features that will make your workflow much easier..
Check out my Application
Thread : http://forum.xda-developers.com/showthread.php?t=2494319

aditya.kamble said:
Hii
I Developed an application named "Android All In One Toolkit" With Windows GUI...
1. Data Transfer
No Need to type single command
just put path in text box & Press Pull From Device button..
It has feature for fast data transfer over adb without mounting sd card...
It also has many more features that will make your workflow much easier..
Check out my Application
Thread : http://forum.xda-developers.com/showthread.php?t=2494319
Click to expand...
Click to collapse
Sorry aditya, but I got an error launching the app,
It said "Could not find the main class : androidallinonetoolkit. Program will exit

Related

Nexus one bootscreen for Tattoo

Hi all,
Before you say something I just "ported" a boot screen from Nexus One to Tattoo (this included resizing the picture to our screen res). Here it is:
Nexus One Bootscreen for HTC Tattoo
Here is how you backup your old boot screens and how you set up the new one to be used (u must be root and I also think that Android 2.1 has a different location for these files, but I have only 1.6. If someone know how to do this on 2.1 tell me how and I will update my post!):
1. Unpack the zip file (a new folder named 'boot' should be created)
2.
Code:
adb shell
# cd /system/media/bootscreen
# mkdir /sdcard/bootscreen_backup
# cp /system/media/bootscreen/* /sdcard/bootscreen_backup
# rm *
# exit
3. Now perform
Code:
adb push pathtobootfolder\boot /system/media/bootscreen
That's it. If you're tired of the Nexus Onbe Bootscreen and you want the old one, do:
1. adb shell
Code:
rm /system/media/bootscreen/*
cp /sdcard/bootscreen_backup/* /system/media/bootscreen
Finito!
Have fun!
/Edit1: I have set Audio=0 in the xml-config because I'm tired of the boot sound...
/Edit2: Changed screenX to 0, thanks to coolbits for this
/Edit3: For those guys having problems understanding what to do - look at this post
Thanks for this
Also change:
screenX="0"
to not get empty first 40 pixels of the screen
Working
Good Work, it's all good on my Tattoo
to have this in my tattoo, it has to be rooted?
djhancks said:
to have this in my tattoo, it has to be rooted?
Click to expand...
Click to collapse
Yes! Root is required.
How to do this in Android 2.1? There is no /system/media/bootscreen folder.
aam.. because i'm a newbie here where do i have to unpack those files?
and where should i write those commands?
djhancks said:
aam.. because i'm a newbie here where do i have to unpack those files?
Click to expand...
Click to collapse
My dear fellow Tattoo user, you can unpack the zip file wherever you like, eg. Desktop.
djhancks said:
and where should i write those commands?
Click to expand...
Click to collapse
First, you need to have working connection from PC to your phone trough ADB. Those commands you must type in Terminal i.e. Command Line, like this (this is Terminal in Ubuntu, don't be confused - menu is localized in my native language):
{
"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"
}
thanks a lot m8
i think you should edit your first post and add this for all us newbies to understand
thanks again
dejandekic said:
My dear fellow Tattoo user, you can unpack the zip file wherever you like, eg. Desktop.
First, you need to have working connection from PC to your phone trough ADB. Those commands you must type in Terminal i.e. Command Line, like this (this is Terminal in Ubuntu, don't be confused - menu is localized in my native language):
Click to expand...
Click to collapse
Nice explanation
dejandekic said:
Yes! Root is required.
How to do this in Android 2.1? There is no /system/media/bootscreen folder.
Click to expand...
Click to collapse
Sorry, I don't have Eclair Tattoo build installed (will flash it when FM Radio and Camera are working). I have updated my 1st post with requirements and restrictions...
those commands work on windows cmd ???
sure they do, but you have to be in the same folder with adb.exe and type adb.exe instead of adb
NForce25 said:
sure they do, but you have to be in the same folder with adb.exe and type adb.exe instead of adb
Click to expand...
Click to collapse
thanks m8, i'm a lil' newbie for all that stuff, but thanks to this guide i can manage
to do this
nice bootscreen, biggest win is turning that F***ing sound off
havok123 said:
nice bootscreen, biggest win is turning that F***ing sound off
Click to expand...
Click to collapse
i like this sound
What am I doing wrong?
I've done a similar bootscreen, but I kept the proportions on the logo and it's oriented the right way (top left to bottom right: blue, red, yellow & green).
Also, I kept the green little buddy and its sound but I removed the annoying sound when the htc-logo should appear.
I attached the zip-file which contains everything (boot.gif, boot1.gif, boot2.gif, boot_bg.gif, boot_animation.xml and boot.mp3)
sheik_yerbouti said:
View attachment 319318
What am I doing wrong?
Click to expand...
Click to collapse
Did you remount RW?
worked for me great
same error by mine,
someone tell me how to "Did you remount RW?"
Greets
"adb remount"
in terminal...

[TT/RELEASE] Ubuntu for (inside of) SCH-I500

{
"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"
}
NOTES:
This version of Karmic (9.10) Ubuntu was made for desktops. It is not a mobile OS and has no phone/text apps. It runs as a completely separate OS that displays on your phone.
While this OS does run "natively", you can only see the lxde gui through a VNC viewer. The filesystem file stays on your sd card.
Installing with the install script does not fully install the OS to your phone, but rather allows you to boot and run with commands from /system/bin instead of the ones placed in /sdcard/ubuntu
Any changes made can be reversed by typing rm -rf /sdcard/ubuntu in a shell/terminal or deleting that folder from root explorer/astro. While this can do no harm to your phone whatsoever, it can freeze it and hog the cpu completely.
I can guarantee that no one will keep this on his/her phone for more than a week. It is simply proof of concept.
You can view the OS on your computer, but you must use WiFi.
Other similar ports *cough* Vibrant *cough* lack features such as many graphical apps, but this strives to be as fully featured as possible. All apps should run, but don't try to multitask. It's a phone. Not a computer.
This is a thinktank because it's not polished enough for me to flat out call it a release. There are many errors and crappy ways of doing things. If you want to help (I don't expect you to; it's futile and useless) run things from terminal and look at the bugs in the README on the desktop.
Thank you to bubs and st0101 for testing and confirming the ability of this port.
Please don't try this if you can't follow directions or are completely new to command line/linux/android/smartphones/technology
All directions and credits are hardcoded in. If you read the outputs of the commands, you will have no problem. However, a starter's guide is below.
Download ubuntu.zip and unzip it
Mount your sd card to your computer
Copy the ubuntu folder to your sd card *!THIS TAKES UP 2 GIGABYTES!* and it will take a while to copy.
Unmount your sd card, but keep your phone connected to your computer
Open an adb shell (adb shell if you have the binaries installed, ./adb shell in the tools folder of the sdk if you don't have them installed)
cd /sdcard/ubuntu
su (also grant superuser rights on the phone when it pops up)
sh ./ubuntu.sh (errors are common, but you will receive the directions to type 'bootlinux' if everything succeeded)
bootlinux
Follow the directions on screen! To use a command line, [email protected]# means that you have access. To use a gui:
cat gui (and then follow the directions)
Read every readme that you can find
cat gui will give you instructions on how to set up a localhost VNC server with no network lag.
DOWNLOAD:
http://www.megaupload.com/?d=VCVD5C95
Screenshots!
nice work!!!
I don't know why anyone would want to do this but it's a great feat. Good job!
Sent from my Dirrk overclocked/lagfixed SCH-i500
Haha, that's the point
I really want to do this so I can run this on my phone and be super cool, just for the browser alone, but I am feeling like I would get lost.
destroyerbmx said:
I really want to do this so I can run this on my phone and be super cool, just for the browser alone, but I am feeling like I would get lost.
Click to expand...
Click to collapse
Get lost? It's easy as balls
Posted from my SCH-I500 (Samsung Fascinate with Voodoo @ 1200 MHz)
Gitykins said:
Get lost? It's easy as balls
Posted from my SCH-I500 (Samsung Fascinate with Voodoo @ 1200 MHz)
Click to expand...
Click to collapse
I don't play with balls on a regular basis, so it might not be as easy as it looks to some. lol jk
Pretty neat.
it works good thanks again
bubs
Sent from my SCH-I500 using XDA App
Thanks guyz.

Cant Install custom recovery on Mac

idk what im doing wrong. I know im a little rusty at this but i did root my nexus 1 couple yrs ago and i dont remember having any problems
i followed the steps in this thread http://forum.xda-developers.com/showthread.php?t=1426377
i unlocked the bootloader but i'm getting stuck at #3. (im on a Mac)
on page 4-5 of that thread some1 else was stating they were getting stuck also. i tried to do what they did but it still not working. they also said something about choosing the option "install from SD card"...but im not seeing that option anywhere (& i do have debugging enabled)
I've put the .zip file on my sd card but when I go to fastboot on my phone, it just says keep saying "no image or wrong image"
this is what it says when i try to fastboot
{
"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"
}
any help is greatly appreciated
Try this...
Download this- http://d-h.st/Vsy
then extract the folder within the zip to your home folder.
open a terminal (it should start up in your home folder)
type sudo chmod 777 Recovery_Flasher
then type cd ~/Recovery_Flasher
once there type ./Flash.sh
Let me know if you get errors... i will try to fix them for you. also, this will reboot your phone into recovery mode when its done to test if it worked. if 4ext recovery loads then it worked
thanks!!!
but could u elaborate on what or where exactly this "home" folder is? the android folder? or is it folder on my sd card?
and i tried to enter those commands in terminal and all i got was "no such file or directory'
acjei said:
thanks!!!
but could u elaborate on what or where exactly this "home" folder is? the android folder? or is it folder on my sd card?
and i tried to enter those commands in terminal and all i got was "no such file or directory'
Click to expand...
Click to collapse
Your home directory on your mac
Sent from.... wait! where am I?
oh ok.
the commands still arent working. still says no such file or directory
im about to call it quits
where can i get the HTC drivers that im supposed to install on my mac?
I have one more idea... Will type it when I get home from school
Sent from.... wait! where am I?
acjei said:
where can i get the HTC drivers that im supposed to install on my mac?
Click to expand...
Click to collapse
Shocking I know, but Google and perhaps HTC would solve your question
Sent from my HTC_Amaze_4G using xda app-developers app
Spastic909 said:
Shocking I know, but Google and perhaps HTC would solve your question
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
already did that..im only seeing .exe files....i have a Mac
where can i get the link for this toolkit?
the link on his site is dead
http://forum.xda-developers.com/showthread.php?t=1493905
You need to find a recovery image. I think the command in fastboot is ./flash recovery.IMG. dont forget commands in mac are ./ then the command.
Sent from my HTC_Amaze_4G using xda app-developers app

[Q] Q: ZEKI 10" Tablet -- Can't get ADB to work

I have a ZEKI 10" TBQC1063B tablet. It apparently an updated version in that it now comes with Google Play Store app installed from the factory. It has Android 4.1.1.
I started to try to Root the device, but was unsuccessful.
In my quest to debug Rooting, I started trying playing with ADB directly. I quickly discovered I could not get to 'first base' with ADB.
Yes, I have USB DEBUGGING enabled, and when my tablet is plugged into my PC, the tablet shows that icon of the Android face in the status line in the lower right screen.
I started to try different drivers (reading that such might be the cause of ADB not working), even though all of the appear to be working OK when I check in Device Manager. One of the attempts I made at drivers led me to those offered as part of PDAnet. While using PDAnet's drivers didn't seem to help, I did stumble upon a CLUE. The CLUE is that while installing the PDAnet drivers, PDAnet did successfully install its own app onto my tablet. I think that such requires ADB to work, no? Could someone confirm such (or not)?
I tried a PC program called AdbDriverInstaller. When I first tried it, it reported a Device Status error of "Driver Incorrectly". So, I uninstalled that driver (I belive at that point it was the PDAnet one), and installed a new driver from a collection called UniversalAdbDriverSetup6. Now, that looked better. AdbDriverInstaller now shows:
{
"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"
}
Looking better?
My problem is that ADB DEVICES still shows no devices:
Does anyone know of anything else to try? This is about the limit of my expertise.
Try!
You can try using different port...i suggest you clean up all the Drivers and then install them correctly!:silly:
Kunal.Kene.1797 said:
You can try using different port...i suggest you clean up all the Drivers and then install them correctly!:silly:
Click to expand...
Click to collapse
Thanks, but I am not sure what you mean,
After trying each driver, I uninstalled and delete it. Is there something else I should be doing to "clean up" ?
How do you install them correctly, other than simply installed them? Device Manager seems to think the ADB device is working correctly.,
WaltA said:
Thanks, but I am not sure what you mean,
After trying each driver, I uninstalled and delete it. Is there something else I should be doing to "clean up" ?
How do you install them correctly, other than simply installed them? Device Manager seems to think the ADB device is working correctly.,
Click to expand...
Click to collapse
Unplug your tablet then reconnect it.
Type in cmd prompt:
Code:
adb kill-server (Hit ENTER)
adb start-server (Hit ENTER)
You should see your device..
Also, this is a good tool..makes adb system wide as well HERE
Also, not sure when Android implemented this, you might see a box up asking for you to grant the PC permission to use ADB, grant it
WaltA said:
Click to expand...
Click to collapse
lacoursiere18 said:
Unplug your tablet then reconnect it.
Type in cmd prompt:
Code:
adb kill-server (Hit ENTER)
adb start-server (Hit ENTER)
You should see your device..
Click to expand...
Click to collapse
I unplugged and plugged my tablet in a few times (over a course of several days while I tried to debug this on my own). Both my PC and my tablet have been powered on/off and rebooted over that time too.
I believe I showed I ready tried those commands, with no success.
TBQC1063B Zeki tablet
Zeki TBQC1063B
Any roms available? This one seems to be stuck. I can get to the boot list, but haven't found a new rom for it. Or even the factory rom.

[Q] Adb and Adb shell help

Hi,
When I start up adb and use the command "Adb devices" my device show. I want to use adb shell, so I type "Adb shell" ofc. Then, when I try "Adb devices", my device does not show :/ Anyone have a solution?
First thing first, make sure you have USB debugging on.
To do this, go into About Phone, tap the build number 7 times (this should give you a toast notification that you are now a developer).
Go back, now go into the developer options what has come up above about phone.
Tick the USB Debugging box, and then connect your phone and try to connect with adb shell.
If this doesn't work, revoke USB debugging authorisations, then try adb shell again.
gamer649 said:
First thing first, make sure you have USB debugging on.
To do this, go into About Phone, tap the build number 7 times (this should give you a toast notification that you are now a developer).
Go back, now go into the developer options what has come up above about phone.
Tick the USB Debugging box, and then connect your phone and try to connect with adb shell.
If this doesn't work, revoke USB debugging authorisations, then try adb shell again.
Click to expand...
Click to collapse
That didn't work :/ Any other suggestions?
Have you installed the ADB drivers and drivers for the board set the Z2 uses?
gamer649 said:
Have you installed the ADB drivers and drivers for the board set the Z2 uses?
Click to expand...
Click to collapse
At least flashtool says I have ADB drivers installed?
Skanin said:
At least flashtool says I have ADB drivers installed?
Click to expand...
Click to collapse
I'm not sure what to suggest then. @Envious_Data any suggestions?
gamer649 said:
I'm not sure what to suggest then. @Envious_Data any suggestions?
Click to expand...
Click to collapse
{
"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"
}
A screenshot of what happens, if that helps
you're already connected in adb mode, as your pic shows, so why would you need to use adb devices again ?
what are you trying to do ? you've successfully connected to your device in adb mode and used the su command, so what do you want to do ?
ticktock666 said:
you're already connected in adb mode, as your pic shows, so why would you need to use adb devices again ?
what are you trying to do ? you've successfully connected to your device in adb mode and used the su command, so what do you want to do ?
Click to expand...
Click to collapse
Yeh, I know.. But I want to use the command "adb remount rw /system". If use it without "abd shell" I get a permission denied error, and in "adb shell" I get error: device not found.. (see picture)
Skanin said:
Yeh, I know.. But I want to use the command "adb remount rw /system". If use it without "abd shell" I get a permission denied error, and in "adb shell" I get error: device not found.. (see picture)
Click to expand...
Click to collapse
Note, don't use any quotes for the below commands.
1) Connect device to computer.
2) Type "adb shell" in cmd, then press enter.
3) Type "su", then press enter.
4) Type "mount -o rw,remount /system", then press enter.
Congratulations, it is now remounted. ADB devices will not work on the device, as the device cannot connect to itself to itself via USB.
what gamer said, you were simply using the wrong command for mounting

Categories

Resources