ADB issues - AT&T Samsung Galaxy S II Skyrocket SGH-I727

Hey guys, I'm new to the Sammy's (this is my first of many!) as I came from the Atrix2 forum (where I am still active).
But I can tell you after being on a locked down Moto phone, it's nice to be running official CM again. :victory:
Anyways I almost always modify some of my own APK's and the one I am after here is the Mms.apk. Normally I would just pull it via ADB and mod it afterwards. However, whenever I pull the APK, ADB says that it completed it, but the file never shows. ADB shows the phone as being attached, so this has left me scratching my head.... I never had these issues back with the A2, so I am thinking this is just some Sammy quirk that I am unaware of. I'm thinking maybe it's a driver issue? But I was able to update to the official ICS version with kies, so I'm assuming my drivers are ok? Here's what ADB is telling me:
Code:
C:\ADB>adb devices
List of devices attached
2c4d3bdb device
C:\ADB>adb pull system/app/Mms.apk C:\ADB
2994 KB/s (2152449 bytes in 0.702s)
Also tried running it interactively with root permissions and still no dice.
Thanks in advance guys.

Bump. Anyone?
Sent from my SAMSUNG-SGH-I727 using xda premium

If it's showing the phone under devices it's not a driver issue.
Have you tried running the command without the C:\ADB at the end? I've never used that and have not had any problems pulling or pushing.
Worse case just unzip the ROM and copy it over to your desktop.

hechoen said:
If it's showing the phone under devices it's not a driver issue.
Have you tried running the command without the C:\ADB at the end? I've never used that and have not had any problems pulling or pushing.
Worse case just unzip the ROM and copy it over to your desktop.
Click to expand...
Click to collapse
Well daggum sir. That was it. :good:
Although it is kinda strange as I have always been able to specify the path I wanted to pull it to before. Odd....
Thank you kind sir. :highfive:

Fall of Enosis said:
Well daggum sir. That was it. :good:
Although it is kinda strange as I have always been able to specify the path I wanted to pull it to before. Odd....
Thank you kind sir. :highfive:
Click to expand...
Click to collapse
You were trying to pull it to the same path. If you wanna pull somewhere else it needs a > i think.
Code:
C:\Users\Me>adb pull system/app/whatever.apk > C:\Users\Me\Downloads
That would drop it in my DL folder.

I always just cd to the directory I want to push or pull from before pushing or pulling. But I'm cheezy like that
Sent from my SGH-I727 using Tapatalk 2

cdshepherd said:
I always just cd to the directory I want to push or pull from before pushing or pulling. But I'm cheezy like that
Sent from my SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Me too
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

Related

Custom ROMs and Sprint Apps

I have a question, when custom ROMs are available and we flash them to our Hero does that mean we will lose the Sprint apps that came with our phone? If so is there a way to back them up and restore them on the new ROM? I am most concerned about the GPS app.
Can you just
adb pull /system/app/Sprint_Navigator.apk C:\
and then install that apk?
nelson8403 said:
Can you just
adb pull /system/app/Sprint_Navigator.apk C:\
and then install that apk?
Click to expand...
Click to collapse
That would definitely work but there is no reason the apps should not be included. It's all up to the rom dev. But that would definitely work. That's how the Dream developers got the Sprint apps on the Dream.
chuckhriczko said:
That would definitely work but there is no reason the apps should not be included. It's all up to the rom dev. But that would definitely work.
Click to expand...
Click to collapse
This is what got Cyanogen in trouble and the C&D order. He was including Google licensed apps into his ROM.
Chances are custom ROM devs will not have the apps included for the same reasons.
Treefallingquietly said:
This is what got Cyanogen in trouble and the C&D order. He was including Google licensed apps into his ROM.
Chances are custom ROM devs will not have the apps included for the same reasons.
Click to expand...
Click to collapse
That is true, however Sprint has done no such thing yet. My theory is do until you get caught
nelson8403 said:
Can you just
adb pull /system/app/Sprint_Navigator.apk C:\
and then install that apk?
Click to expand...
Click to collapse
So, could i 'pull' the NFL app from my phone and email it to my friend with a G1 so he could use it too?
Negrito said:
So, could i 'pull' the NFL app from my phone and email it to my friend with a G1 so he could use it too?
Click to expand...
Click to collapse
Yep. The only one that did not work for me and my dream was the Sprint tv app.
chuckhriczko said:
Yep. The only one that did not work for me and my dream was the Sprint tv app.
Click to expand...
Click to collapse
Seriously? Dude i think you just made my best friends day!
Little help?
Ok, so i have a Mac and everything seems to be working ok but when i do this:
96-26-56-112:tools brynehobbs$ ./adb pull /system/app/Sprint_NFL.apk desktop
1185 KB/s (288423 bytes in 0.237s)
96-26-56-112:tools brynehobbs$
There is nothing new on my desktop. I'm not too sure what the 'local' path should be though...
Negrito said:
Ok, so i have a Mac and everything seems to be working ok but when i do this:
96-26-56-112:tools brynehobbs$ ./adb pull /system/app/Sprint_NFL.apk desktop
1185 KB/s (288423 bytes in 0.237s)
96-26-56-112:tools brynehobbs$
There is nothing new on my desktop. I'm not too sure what the 'local' path should be though...
Click to expand...
Click to collapse
Im not quite sure how the folder structure is for Mac OS but since it is unix this command will work:
Code:
./adb pull /system/app/Sprint_NFL.apk .
The dot basically says extract it right here. You can then look in the directory where adb is located and the file should be there.
Negrito said:
Seriously? Dude i think you just made my best friends day!
Click to expand...
Click to collapse
Yeah man. I was pretty psyched to have these apps (which personally, I like) on my Dream. The only complaint is the fantasy option in the NFL apk doesnt work on the Dream but then again, it currently does not work on my Hero so I dont know what gives there.
chuckhriczko said:
Im not quite sure how the folder structure is for Mac OS but since it is unix this command will work:
Code:
./adb pull /system/app/Sprint_NFL.apk .
The dot basically says extract it right here. You can then look in the directory where adb is located and the file should be there.
Click to expand...
Click to collapse
Awesome bro! That worked like a charm.
I just pulled this little move.
adb pull /system/apps c:\androidsdk\Stockapps
Backed up all of the apps... just incase...
Small correction
justpastfinish said:
I just pulled this little move.
adb pull /system/apps c:\androidsdk\Stockapps
Backed up all of the apps... just incase...
Click to expand...
Click to collapse
One small correction, it's "/system/app" (no plural s).
adb pull /system/app <wherever>
So i emailed my friend the Sprint_NFL.apk trough Gmail but when he tried to open it on his G1 he got: "there was a problem parsing the package"
Do i have to root his G1 and use adb to 'push' the file to the G1 for it to work properly?
justpastfinish said:
I just pulled this little move.
adb pull /system/apps c:\androidsdk\Stockapps
Backed up all of the apps... just incase...
Click to expand...
Click to collapse
Thats a good idea, i just did that as well.
5tr4t4 said:
One small correction, it's "/system/app" (no plural s).
adb pull /system/app <wherever>
Click to expand...
Click to collapse
Thank you... my bad...
I also am an Android/Linux noob. I dabble because I like to..
Negrito said:
So i emailed my friend the Sprint_NFL.apk trough Gmail but when he tried to open it on his G1 he got: "there was a problem parsing the package"
Do i have to root his G1 and use adb to 'push' the file to the G1 for it to work properly?
Thats a good idea, i just did that as well.
Click to expand...
Click to collapse
Well it should work. I just checked the dream forum and the mods were forced to remove the links so you cant get them from there anymore either. I dont think root is necessary but maybe it is. I would try adb or make sure he has install apps from unknown sources checked in settings->applications.
chuckhriczko said:
Well it should work. I just checked the dream forum and the mods were forced to remove the links so you cant get them from there anymore either. I dont think root is necessary but maybe it is. I would try adb or make sure he has install apps from unknown sources checked in settings->applications.
Click to expand...
Click to collapse
Yeah he has it checked, but he is across town so i cant quite adb it right this second. Next time i see him i'll see it i can get it going for him. Thanks for all your help!
Thanks for everyone's input I successfully backup up all my apps. Just in case. It was interesting to see the size of each app.
Just incase no one has stumbled upon it yet...
http://android.modaco.com/content/h...-modaco-custom-rom-core-featuring-wavesecure/
CDMA Rom - Modaco

[Temp] Fix for missing apps on froyo

in your build.prop replace the current text with this: you can get things like tv.com back
Code:
ro.build.description=passion-user 2.2.1 FRG83 60505 release-keys
ro.build.fingerprint=google/passion/passion/mahimahi:2.2.1/FRG83/60505:user/release-keys
i would upload one for people to flash but as some many people are on diff roms/kernels it would just cause more issues then its worth best way to go about fixing it is pulling the file from your phone (or the zip from teh rom your on). swapping out the text and pushing it back to /system
all credit goes to Decad3nce for the fix
Didn't s work for me...
Sent from my SPH-D700 using XDA App
you may have to reboot
Worked for me! Thanks.
Sent from Froyo!
Thanks worked great!!
shabbypenguin said:
in your build.prop replace the current text with this:
Click to expand...
Click to collapse
Wouldn't you like to be more specific? Your current instructions technically mean to replace the entire file with just those three lines...
Sent from my SPH-D700 using XDA App
Please note that users of Quantum Rom already have this fix applied, since 1.3
(Used the epic 2.1 key in 1.3, 1.4+ use the nexus one key)
Thanks shabby xD
Sent from my SPH-D700 using Tapatalk
Here's what I did from my PC with adb. (I have adb in my PATH so adjust the commands for wherever you might have adb.exe)
adb pull /system/build.prop
Then I edited the 2 lines on my PC with notepad++ and saved. Then I put it on my sdcard, remounted /system readwrite and copied it over to /system/build.prop and then rebooted.
adb push build.prop /sdcard/build.prop
adb shell
su (if your ROM didn't already drop you in to root, and check your phone for the superuser popup)
mount -t rfs -o remount,rw /dev/block/stl9 /system
cat /sdcard/build.prop > /system/build.prop
reboot
Sent from Froyo!
didnt work for me. I been trying to get the PayPal 2.2 to show up on the market but its a no go.
Im using Froyo also.
anyway we could just get the paypal.apk??
This didn't work for me either. Trying to get Pocket Blu installed, but it isn't working. TV.com isn't showing either. FWIW I have the new Market app if that means anything.
Any ideas?
Milkman00 said:
This didn't work for me either. Trying to get Pocket Blu installed, but it isn't working. TV.com isn't showing either. FWIW I have the new Market app if that means anything.
Any ideas?
Click to expand...
Click to collapse
Did you reboot your phone?
yes, and after rebooting a rechecked my build.prop file to make sure it took, and it was correct
Nevermind, I got it to work...
The end of the second line was missing the s. Put the s in, and it works perfect.
Can I get some clarification on this? I am using Mammon 1.0.3.1 and cannot get my sprint football ap to work.
Would this be an example of what this would fix?
Could the MSID number in my phone being different from my phone number be the reason it doesn't think this is a SPrint phone?
Thanks for posting a fix but it also didn't seem to work for me. I have been trying to load a program called Laser Appraiser from maket with no avail. Can anyone find it in their market?
worldlyinquirer said:
Thanks for posting a fix but it also didn't seem to work for me. I have been trying to load a program called Laser Appraiser from maket with no avail. Can anyone find it in their market?
Click to expand...
Click to collapse
Laser Appraiser shows up for me.
Milkman00 said:
Laser Appraiser shows up for me.
Click to expand...
Click to collapse
Thanks, Hmm I think I'll just wait for the latest froyo release and see if that helps
I tried downloading it and saving it to my SD card, but it's a protected app. I use AppMonster, which backs up all the apps for when I do flashing, but it doesn't do protected ones. Sorry man, I tried.
sorry i havent replied, most of the roms out there SHOULD have this baked in... i know acs and quantum do and the cm rom should but ill ask noob just to be sure.

[q] [xoom 2] i think it's bricked

Uhm, I have a XYBOARD 10.1 inch (WIFI ONLY) And I edited something in Build.PROP. I then restarted at to my surprise it goes completely black after it shows the Motorola DUAL CORE screen. I can get into the recovery. I even Factory Resetted thinking that might help but, Nothing. Is there anything I can do to restore it? Because I'd rather not have an expensive XYBOARD paper weight.
BUMP? I really need help.
if you can get to recovery, you should be able to push stock OS via ADB.. there is a guide in the Xoom development section.
pinoiryder said:
if you can get to recovery, you should be able to push stock OS via ADB.. there is a guide in the Xoom development section.
Click to expand...
Click to collapse
And this is for XYBOARD? Anyway, I can't find the topic...
is there not maybe a way you can pull the build.prop file via adb edit change what you editied, then push it bk via adb???
just outta curiosity, what did you change in the build.prop, also remember, ALWAYS MAKE A BACKUP FIRST!!!! lol
[email protected] said:
is there not maybe a way you can pull the build.prop file via adb edit change what you editied, then push it bk via adb???
just outta curiosity, what did you change in the build.prop, also remember, ALWAYS MAKE A BACKUP FIRST!!!! lol
Click to expand...
Click to collapse
...
How do you make a BackUp on a XYBOARD?
Anyway, Can someone just link me to the needed programs and topic?
ok well since you know, you cant make backups on an XYBOARD then why muck about with it????
[email protected] said:
ok well since you know, you cant make backups on an XYBOARD then why muck about with it????
Click to expand...
Click to collapse
If one doesn't muck around with things, Nothing will ever be discovered.
But I should of waited until someone better at things like this paved the way.
*Beats self with XYBOARD*
SUperFatCatNine said:
If one doesn't muck around with things, Nothing will ever be discovered.
But I should of waited until someone better at things like this paved the way.
*Beats self with XYBOARD*
Click to expand...
Click to collapse
Lol can you not download the original image from motorola and flash it somehow ?? There must be a way surely
Sent from my Xoom using XDA Premium App
Does anyone have the stock build.prop for XYBOARD 10.1 Wifi only?
Also, How do you push it on using ADB?
I think there is no way to solve the problem. Send it to Motorola and will fix it for you.
Sent from my XOOM 2 ME using Tapatalk 2
As the XOOM2/Xyboard has a locked bootloader and no bootstrap for a recovery so your stuck right now until Motorola decides to care about the Android community. Also adb is not possible from what I heard when it can't boot. If you want some help then contact the not many Xyboard devs here "Bricks" as they are always happy to help bricked people.
luke.arran said:
As the XOOM2/Xyboard has a locked bootloader and no bootstrap for a recovery so your stuck right now until Motorola decides to care about the Android community. Also adb is not possible from what I heard when it can't boot. If you want some help then contact the not many Xyboard devs here "Bricks" as they are always happy to help bricked people.
Click to expand...
Click to collapse
It's More of a soft brick. I can get into recovery.
(It's Still Makes a Nice Frisbee or Paper Weight. xD)
SUperFatCatNine said:
It's More of a soft brick. I can get into recovery.
(It's Still Makes a Nice Frisbee or Paper Weight. xD)
Click to expand...
Click to collapse
I'm in the same situation as you as of today (But I have the Verizon Droid Xyboard 10.1). Messed around with the Build.prop and now its not working. I have a copy of the original Build.prop but don't know how I can push it to my tablet.
Adb is not working but fastboot is.
I don't think my original build.prop would be any help to you since I have the 4G version but if you want it let me know and I will send it to you!
Looks like I may have to send it to Motorola :-(
OK guys, no worries... I think I know the solution.
1 - enter in recovery
2 - open cmd on your PC
3 - go to adb and fastboot folder via cmd
4 - type:
Code:
adb devices
adb shell
su
cd /system
rm build.prop
exit
5 - copy original build.prop to this folder (adb one)
6 - type:
Code:
adb push build.prop /system/build.prop
adb reboot
exit
Hope that helps you guys it already helped me (I have the Origina Xoom)
Sent from my MZ601 using XDA Premium HD app
Just one more little thing, I presume you guys have su, as you changed build.prop and recovery (because to install super user recovery is needed!) If you guys don't have them, I'm sorry but don't know a solution...
Sent from my MZ601 using XDA Premium HD app
XxLordxX said:
OK guys, no worries... I think I know the solution.
1 - enter in recovery
2 - open cmd on your PC
3 - go to adb and fastboot folder via cmd
4 - type:
Code:
adb devices
adb shell
su
cd /system
rm build.prop
exit
5 - copy original build.prop to this folder (adb one)
6 - type:
Code:
adb push build.prop /system/build.prop
adb reboot
exit
Hope that helps you guys it already helped me (I have the Origina Xoom)
Sent from my MZ601 using XDA Premium HD app
Click to expand...
Click to collapse
And where might I find CMD?
It's a Windows thing... just search a little on it... try using the menu option to show up everything and search for cmd... Which OS are you using?
Sent from my MZ601 using XDA Premium HD app

[Q] How To, If Possible, Root With Bad Volume Keys

So, I'm attempting to root a Charge that the volume keys do not work. Apparently, 1 and 2 year olds who have great throwing ability is something the Charge, well, anything really, doesn't exactly appreciate. Normally, I root by going into the download mode, and flashing CWM, then installing the ROM. Obviously, not happening here.
My question is, has someone with more knowledge than I figured out how to accomplish this? Its running stock FP5. I really don't want to send it in because of the contract timing and wasteful of money. I'm also willing to experiment replacing parts, if someone knows anything about it...
Thanks.
Sent from my SCH-I510 (Tweaked 3.0) using xda premium
Yep. There's a jig that will force the phone into dl mode. IIRC it's branded for the gnex but it's confirmed to work on the Charge as well. http://forum.xda-developers.com/showthread.php?p=27533069
Sent from my SCH-I535 using Tapatalk 2
Hey, I had a thought of using ADB to root, and somehow forcing CWM on it, then using an app to boot it into dl mode. I've never used and before and don't know if it's possible, although, from what I read, it seems plausible. Can you offer any insight on this idea?
Sent from my SCH-I510 using xda
edji-x said:
Hey, I had a thought of using ADB to root, and somehow forcing CWM on it, then using an app to boot it into dl mode. I've never used and before and don't know if it's possible, although, from what I read, it seems plausible. Can you offer any insight on this idea?
Sent from my SCH-I510 using xda
Click to expand...
Click to collapse
If you have adb all set up and it properly recognizes your phone (something comes up when putting in the adb devices command) you can boot into download mode with
adb reboot download
Actually it's something I looked into recently for another member. I'm not saying it's not possible but I don't think we have the right tools for it. Originally ginger root was used via adb to root the charge but that's not going to work with our version of gb (assuming you could still find it). I'm not sure the format of cwm will work either. I'm not really proficient with adb so someone with more expertise might be able to get you going.
Sent from my Nexus 7 using Tapatalk 2
Awesome. I don't have it installed yet, but it doesn't look like it takes much to make it work. Plus, I have nine that isn't screwed up, so I think I'll see what I can come up with later.
On a side note, I can't post a reply to your tweaked 3.1 thread, but I ran into somewhat of a problem... run tweaktools, did the tweaks thing, phone BARELY would run. I also couldn't get a shell to run to get back in to uninstall. What I ended up doing to fix was a reinstall of SuperSU and installing a bash shell off a different emulator to get back into tweaktools. This was after I played in /system/etc/init.d awhile trying my hand at fixing it. Thought you may want/need to knoknow.
Sent from my SCH-I510 using xda
By the way, thanks for the tip. I'll report one way or another in a day or 2.
Sent from my SCH-I510 using xda premium
edji-x said:
On a side note, I can't post a reply to your tweaked 3.1 thread
Click to expand...
Click to collapse
You need 10 posts minimum to post in the Dev forums, XDA's rules.
Sent from my Droid Charge running [email protected] 3.2a enhanced by dSlice's Scripts & Tweaks
edji-x said:
Awesome. I don't have it installed yet, but it doesn't look like it takes much to make it work. Plus, I have nine that isn't screwed up, so I think I'll see what I can come up with later.
On a side note, I can't post a reply to your tweaked 3.1 thread, but I ran into somewhat of a problem... run tweaktools, did the tweaks thing, phone BARELY would run. I also couldn't get a shell to run to get back in to uninstall. What I ended up doing to fix was a reinstall of SuperSU and installing a bash shell off a different emulator to get back into tweaktools. This was after I played in /system/etc/init.d awhile trying my hand at fixing it. Thought you may want/need to knoknow.
Sent from my SCH-I510 using xda
Click to expand...
Click to collapse
Sorry to hear of the troubles - not sure what would have caused the issue with tweaktools. You weren't able to su, or you weren't able to open terminal emulator? What were you messing with specifically in the tweaks?
dwitherell said:
If you have adb all set up and it properly recognizes your phone (something comes up when putting in the adb devices command) you can boot into download mode with
adb reboot download
Click to expand...
Click to collapse
:banghead:
Sigh, I don't know why I didn't think of that lol. And I was Ninja'd. Double whammy lol
Sent from my SCH-I535 using Tapatalk 2
Okay, Found it in ADB, and am able to reboot into download, so all is well, I think.
On the tweaktools issue, I kinda did something like this...One tweak does okay, so lets install ALL of them....after that, performed the reboot, and everything went very sloooow. So, I tried to get into a term emulator, and nothing happened, the shell wouldn't even start. Blank screen. So, I tried a different outside of ROM toolbox. Nothing. So, I played around with the settings here and there, and still nothing. I then went into root browser, and started trying to manually move the tweaks out, nothing different. So, I downloaded another term emulator, "Better Terminal Emulator" and got a bash shell to at least open, was able to get into tweaktools, erase all tweaks, clear downloads. But the shells still weren't operating right. They'd open and run, but nothing would show on screen. So, a erase/reinstall of SuperSU, everything good....LOL
Well, maybe it'll help, maybe not, but here's the path I used to do this:
Visit samsung's site for the ADB download and install to c:\android-sdk\ (default)
Put USB Debugging on in phone
Start up command line and Odin 1.82
issue following in command line (notably in the c:\android-sdk\platform-tools)
Code:
adb reboot download
Odin up some Tweaked 2.2 with recovery and kernel for root
once rebooted, issue the following in ADB shell:
Code:
adb shell
su (Checked phone to be sure root was granted)
cd /data
rm -R *
cd /cache
rm -R *
cd /dbdata rm -R *
reboot, then adb reboot download.
Flashed EP4 Stock, updated,
Updated to FP5E
Once again, USB debug, adb reboot download, and Odin Tweaked 3.1 with 0302,
follow above code again, reboot, and I think I have it right....
Since the volume keys don't work on here, is there a way to screw around in the recovery mode via ADB rather than only the keys? I see ADB sees the phone in recovery, and seems to want to connect with it....Second is, is there a way to play with this in the *nix enviroment? I also have been searching for the Gingerbreak, etc to root this thing on stock, but haven't been able to do it....and last, is there a way to do a data wipe other than what I did, and think i accomplished with ADB?
Thanks
With the CWM that I am using, you can use the hard buttons at the bottom of the phone to navigate.
Sent from my SCH-I510 using Xparent Red Tapatalk 2

Help me please to restore data.

Hi! Can I retore data from my bricked TF300T from internal memory somehow? I was storing photos on device memory on my Asus TF300T and now its bricked. I need to restore these photos, my girlfriend has something like 1000 of them from her trip to Caracas. Its very important for her. I already managed to connect the device through fastboot and I launched adb in cmd. What should I do next? Please help me guys
koperkowy said:
Hi! Can I retore data from my bricked TF300T from internal memory somehow? I was storing photos on device memory on my Asus TF300T and now its bricked. I need to restore these photos, my girlfriend has something like 1000 of them from her trip to Caracas. Its very important for her. I already managed to connect the device through fastboot and I launched adb in cmd. What should I do next? Please help me guys
Click to expand...
Click to collapse
As you have adb access, you can use adb pull to retrieve the files:
adb pull device_path local_path
For example:
adb pull /sdcard/photos/photo001.jpg photos/
You probably need to do that file-by-file, though I never tried a directory. Some shell scripting might help.
Sent from my TF300T using Tapatalk
Is there an easier way to copy them all? It will be pretty hard to copy 1000 photos one by one ;/
koperkowy said:
Is there an easier way to copy them all? It will be pretty hard to copy 1000 photos one by one ;/
Click to expand...
Click to collapse
How's THIS?
koperkowy said:
Is there an easier way to copy them all? It will be pretty hard to copy 1000 photos one by one ;/
Click to expand...
Click to collapse
Well, the trick is to use shell scripting, like mentioned. For example on Linux, something like:
Code:
adb shell ls /sdcard/photos/ >filelist.txt
for p in $(cat filelist.txt); do adb pull /sdcard/photos/$p photos/; done
There should be similar scripting capabilities in Windows, but never used those.
Or you can use Cygwin with above lines.
Sent from my TF300T using Tapatalk
Or better
adb pull /storage/sdcard/photos/. ~
Sent from my iPhone using Tapatalk
enedil said:
Or better on GNU/Linux
adb pull /storage/sdcard/photos/. ~
Click to expand...
Click to collapse
Oh, true, with an up-to-date adb you can indeed pull a directory. Either older versions didn't support that, or I never noticed.
Should work on Windows as well.
Sent from my TF300T using Tapatalk
f69m said:
Oh, true, with an up-to-date adb you can indeed pull a directory. Either older versions didn't support that, or I never noticed.
Should work on Windows as well.
Sent from my TF300T using Tapatalk
Click to expand...
Click to collapse
On Linux cuz there's ~ instead of something like
C:\Users\Admin\
Wysłane z mojego GT-P5100

Categories

Resources