Related
ok so I got adb working fine .. but apparently I have NO idea on how to properly pull and anything from the phone or push to the phone what I saw was something about adb pull system/sd/app app and then I have seen adb pull system/sd/app/app which BOTH give me the adb: not found
then I have created a folder named android on my C:
then I tried the cd C:\android adb pull /system/sd/app/app and that gives me a bad substitution
I have also tried the adb pull system/sd/app/app cd C:\android .. this also gives me that bad substitution error
so what I NEED is SOMEONE to give me SPECIFIC examples of this
so i am asking for 2 exapmles
one to pull the calcultor from the phone to the comp
second is to pull an installed app like chompsms from the phone to the comp
I am doing all of this from the #
I have searched google and cannot find ANYTTING on this
I have searched here and found nothing
I have read the adb for dummies and the adb useful commands
any help on this would be great
also I have done the cd data then cd app and then when I get to the cd ls is says cannot cd into ls
But when I just ls I get the apps list
I am using vista 64 too
BTW I am using the 1.5MOD from lucid and I do have my apps to the sd card by using his lucid script
Strapt said:
BOTH give me the adb: not found
Click to expand...
Click to collapse
Put the path to your folder with adb in it in your system path directory. Instructions from the android dev site:
Optionally, you may want to add the location of the SDK's primary tools directory to your system PATH. The primary tools/ directory is located at the root of the SDK folder. Adding tools to your path lets you run Android Debug Bridge (adb) and the other command line tools without needing to supply the full path to the tools directory.
On Linux, edit your ~/.bash_profile or ~/.bashrc file. Look for a line that sets the PATH environment variable and add the full path to the tools/ directory to it. If you don't see a line setting the path, you can add one:
export PATH=${PATH}:<your_sdk_dir>/tools
On a Mac, look in your home directory for .bash_profile and proceed as for Linux. You can create the .bash_profile if you haven't already set one up on your machine.
On Windows, right-click on My Computer, and select Properties. Under the Advanced tab, hit the Environment Variables button, and in the dialog that comes up, double-click on Path (under System Variables). Add the full path to the tools/ directory to the path.
Click to expand...
Click to collapse
then I have created a folder named android on my C:
then I tried the cd C:\android adb pull /system/sd/app/app and that gives me a bad substitution
Click to expand...
Click to collapse
Adb push/pull requires two arguments, the source and the destination. E.g. on windows:
adb push \completely_legit_apps\gamelofd-monopolizing.apk /data/app/mono.apk
-or-
adb pull /system/app/Mail.apk \roflmao_i_ripped_exchangemail.apk
Notice that on the Android side, the path delimiter is the forward slash (/), whereas on the Windows side it's backslash (\).
Edit: also, on windows if you don't specify an absolute path, it is taken as being relative to your usr directory:
adb push \app.apk <-- pushes c:\Documents and Settings\username\app.apk, NOT c:\app.apk
^above^
But this is also in the wrong forum! This belongs to Q&A.
jashsu said:
Put the path to your folder with adb in it in your system path directory. Instructions from the android dev site:
Adb push/pull requires two arguments, the source and the destination. E.g. on windows:
adb push \completely_legit_apps\gamelofd-monopolizing.apk /data/app/mono.apk
-or-
adb pull /system/app/Mail.apk \roflmao_i_ripped_exchangemail.apk
Notice that on the Android side, the path delimiter is the forward slash (/), whereas on the Windows side it's backslash (\).
Edit: also, on windows if you don't specify an absolute path, it is taken as being relative to your usr directory:
adb push \app.apk <-- pushes c:\Documents and Settings\username\app.apk, NOT c:\app.apk
Click to expand...
Click to collapse
ok so I am trying to pull the Mms.apk to the comp into my C: documents
So I got
# adb pull /system/app/Mms.apk ... then what exactly would I need to finish the rest? how would that look whole?
My Mms.apk is in system/app in my phone and I do have apps to sd if that makes a diff
also .. if I pull this does that completely remove it from the phone? assuming it would
I keep getting adb not found But I can type lucid and it shows the lucid comands and reboot and it reboots ... so i am connected ...
Strapt said:
ok so I am trying to pull the Mms.apk to the comp into my C: documents
So I got
# adb pull /system/app/Mms.apk ... then what exactly would I need to finish the rest? how would that look whole?
My Mms.apk is in system/app in my phone and I do have apps to sd if that makes a diff
also .. if I pull this does that completely remove it from the phone? assuming it would
I keep getting adb not found But I can type lucid and it shows the lucid comands and reboot and it reboots ... so i am connected ...
Click to expand...
Click to collapse
adb pull /system/app/Mms.apk temp/
Of course, you can substitute temp with any folder you want (by default, you will save it under the folder that adb is located in,
so the command above would push the file to /adb directory/temp
Like that.
Its might be saying that its not there, because its not there, with apps2sd it should be located under /system/sd/app_s/Mms.apk (but of course this differs from build to build)
and no, I don't think it will remove it, it should still be there, to remove it you have to type:
adb shell rm /system/sd/app_s/Mms.apk
h.nocturna said:
adb pull /system/app/Mms.apk temp/
Like that.
Its might be saying that its not there, because its not there, with apps2sd it should be located under /system/sd/app_s/Mms.apk (but of course this differs from build to build)
and no, I don't think it will remove it, it should still be there, to remove it you have to type:
adb shell rm /system/sd/app_s/Mms.apk
Click to expand...
Click to collapse
ok so I tried both the
/system/app/Mms.apk temp/
and the adb pull /system/sd/app_s/Mms.apk temp/
BOTH I get adb not found
Do i need to add something like cd C:\Documents adb pull /system/app/Mms.apk ??? (which If I do that I get a bad substitution error or a directory not found .. which it is in there)
when I go thru astro the path is system/app then I see all the stock apps and the odex files
EDIT: some I have seen have been adb pull /system/app/Mms.apk/Mms.apk OR adb pull /system/app/Mms.apk Mms.apk .. those I still get adb not found
EDIT EDIT: hell even adb remount gets me adb not found ... and the cd ls gets me cant cd into ls
EDIT EDIT EDIT: ok so i tried to change the dir to where the file goes. So I created a Documents folder in root of my C drive. Then I used the adb pull /system/app/Mms.apk Documents\ and I got a > and nothing is in my folder I changed the direction of the last \ after Documents
I got it!!! this worked!!!
adb pull /system/app/Mms.apk \Documents WORKS!!! NOT FROM THE#!!!
Strapt said:
I got it!!! this worked!!!
adb pull /system/app/Mms.apk \Documents WORKS!!! NOT FROM THE#!!!
Click to expand...
Click to collapse
I think you should learn more about command prompts and linux shell commands
other than that, good for you.
glad it worked for you. If i wasn't clear, I meant that you should've cd to the location of adb on your computer through command prompt, then from there run the commands that I outlined above.
h.nocturna said:
glad it worked for you. If i wasn't clear, I meant that you should've cd to the location of adb on your computer through command prompt, then from there run the commands that I outlined above.
Click to expand...
Click to collapse
ok so like what ya mean?
from the
C:\Users\Owner
I do then "cd C:\android-sdk-windows-1.5_r2\tools"
and that takes me to the plain C:\android-sdk-windows-1.5_r2\tools
so from here what would you type in to cd and cd into what?
apparently the problem what that I typed adb shell and then was doing everything from the comand prompt and that didnt work.
ok so I think I figured out what you mean.
I did type the cd C:\Documents then I get the C:\Documents> and from there I can run just the adb pull /system/app/Mms.apk Mms.apk
now that I have that working I have to try the push now
so with the same example above I would:
again cd C:\Documents
then
adb push Mms.apk /system/app/
is that right or should that be different?
ok so here is a question
I did mange to find where my downloaded apps are going by mounting the volumes onto ubuntu. which is /media/disk-1/app and this is in my ext2 partition
but I cant seem to be able cd to the /media/disk-1/app everytime it says cant cd to /media/disk-1/app
trying to do two things
one is trying to cd into that path so I can ls
and also trying to see how I would be able to pull apps that I have downloaded
I have kinda figured out the other pull but now would like to know why this isnt working.
Strapt said:
ok so I think I figured out what you mean.
I did type the cd C:\Documents then I get the C:\Documents> and from there I can run just the adb pull /system/app/Mms.apk Mms.apk
now that I have that working I have to try the push now
so with the same example above I would:
again cd C:\Documents
then
adb push Mms.apk /system/app/
is that right or should that be different?
Click to expand...
Click to collapse
adb should only work from whatever location you put the adb.exe, so for instance, I'm assuming that you put adb in c:\Documents. Then you would type cd c:\documents and run your adb commands there, and adb will treat c:\Documents as your root folder (which is why everything transfers to c:\Documents by default for you). Therefore, the push commands will also treat c:\Documents as your root folder, so you can only push whatever is in c:\Documents. So transfer whatever file you want to be pushed to c:\Documents and then adb push file within c:\Documents /wherever you want it on the phone
h.nocturna said:
adb should only work from whatever location you put the adb.exe, so for instance, I'm assuming that you put adb in c:\Documents. Then you would type cd c:\documents and run your adb commands there, and adb will treat c:\Documents as your root folder (which is why everything transfers to c:\Documents by default for you). Therefore, the push commands will also treat c:\Documents as your root folder, so you can only push whatever is in c:\Documents. So transfer whatever file you want to be pushed to c:\Documents and then adb push file within c:\Documents /wherever you want it on the phone
Click to expand...
Click to collapse
well actually I made the Documents folder and its completely empty
the actual adb.exe is in the C:\android-sdk-windows-1.5_r2\tools\adb.exe
I think that I have copied and pasted that and some win something .dll into system32 folder. not sure if that makes a difference or not.
from my understanding I can now change it to whatever folder I want to move the files to on my comp just by typing the location and folder name and not just to the Documents folder.
also when I am at the C:\android-sdk-windows-1.5_r2 in cmd what is that line called or the commands that you do from that line called? and the pull push has to be from this line right?
Im guessing that the adb shell is the linux shell commands which is the # right?
also I would to really like to say thank you for your continued help on this!!
Its no problem, placing it in system32, allows you to use adb.exe straight from the console so its alright. But instead of cd(ing?) to whatever location the adb.exe is located, just cd to wherever you want to pull the files or wherever the files you want to push are and then just run the commands outlined above for pushing/pulling files.
the # denotes that you have entered the phone's terminal with root permissions. Yes, it is linux.
Yes the commands must be typed from the command prompt so:
C:\Documents>adb pull /system/sd/app_s/Mms.apk C:\Documents
or wherever you want, just replace C:\Documents with whatever you want.
I'm running Fresh 2.1.1 and I have quite a few texts built up on my phone but every time I try to delete a thread it just doesn't. I press delete, the menu disappears, and the thread just stays there. Any thoughts? If I need to put more info I can, or if anybody can tell me where I can go in adb to delete them? Thanks in advance!
this does it. i had to do this to my gf's hero last week
this will make a backup of your texts on your pc before.
Code:
mkdir c:\temp
adb pull /data/data/com.android.providers.telephony/databases/mmssms.db c:\temp (this will backup the database to your computer at c:\temp, just in case)
adb remount
adb shell
rm /data/data/com.android.providers.telephony/databases/mmssms.db
reboot
Thank you very much!
In short,
I want to be able to
1) have a shell script which will connect via wireless to my local linux server and sync a directory
2) call this shell script from an icon on my home screen
3) see the output in window that popped up
Is this possible?
http://digitizor.com/2010/03/24/how-to-sync-nexus-one-with-rythmbox-music-player/
Not sure if a similar method works with Amarok
To kick it off from your phone.. vnc into your machine and start the process.
btw...this is a question and should have gone to the Q/A section.
I had a set of scripts on my Zaurus pda some years ago that, when a connection to my home network was detected, would try a rsync with my rsync server. It allowed me to have a always updated backup of my data. I have to look it up, even if only to set it up as a script, without a nice interface... It looks like a nice way of backing up my photos as soon as I am on my home wifi network.
there is app called Fsync that can do that for you.
Been doing this for months. Here is how.
Install Ampache on your Linux box. www.ampache.org
Configure Ampache and make sure you password protect! Open ports on your router/firewall.
Install Amdroid or Lullaby from the Market on your Android. Both apps will connect to your ampache server. I have been using Lullaby and prefer it.
Connection over 3G has almost no delay between songs and works well in the car
Thanks to both of you guys, but...
I don't know if that is will be enough for what the OP had in mind, but I wasn't talking about music/video streaming, I was talking of configurable automatic sync of directories, so ampache doesn't help me. Also, Fsync seems to need a ftp server, and all I need is a rsync server. I don't want to go around configuring ftp shares, etc, when rsync is way more suited to keeping two (or more) directories in sync.
I found out what I used on the zaurus: zNetBackup. Now is time to look at the sources, and if android runs scripts when setting up interfaces...
ruineraz said:
In short,
I want to be able to
1) have a shell script which will connect via wireless to my local linux server and sync a directory
2) call this shell script from an icon on my home screen
3) see the output in window that popped up
Is this possible?
Click to expand...
Click to collapse
You should already have everything you need, which is just rsync on the phone and ssh on the Linux box. Just run ssh on the box, set up keys, then figure out your rsync command and run it from GScript on the phone. GScript allows you to create a shortcut to a command or script on your home screen.
I use this general ssh/scp command to recursively transfer a directory to my sdcard all the time. Should be easy to adjust for rsync.
scp -i /path/to/keyfile -P port_number -r [email protected]:/path/to/directory /sdcard
fubaya said:
You should already have everything you need, which is just rsync on the phone and ssh on the Linux box. Just run ssh on the box, set up keys, then figure out your rsync command and run it from GScript on the phone. GScript allows you to create a shortcut to a command or script on your home screen.
I use this general ssh/scp command to recursively transfer a directory to my sdcard all the time. Should be easy to adjust for rsync.
scp -i /path/to/keyfile -P port_number -r [email protected]:/path/to/directory /sdcard
Click to expand...
Click to collapse
Thanks. Just can't seem to get ssh keys set up... dunno where to put them (don't seem to be .ssh folder anywhere)
ruineraz said:
Thanks. Just can't seem to get ssh keys set up... dunno where to put them (don't seem to be .ssh folder anywhere)
Click to expand...
Click to collapse
Good point. You can put the key anywhere, but you need a .ssh directory for the known_hosts file. It should be simple on a Linux based device, but... it's not really.
There is a Cyanogen wiki page about setting up ssh using dropbear, and you can probably get rsync working in a terminal with that.
However, trying to ssh with the normal ssh binary using GScript (to launch the script from home screen) gave me "Unknown own user" errors. To fix it, I replaced the ssh binary (maybe it was a link to busybox or dropbear, I dunno) with a link to the ssh binary from Better Terminal Emulator Pro. I've been doing that through several roms over the past few months and the BTEP ssh always works flawlessly. I run this every time I install a new rom:
rm /system/xbin/ssh
ln -s /data/data/com.magicandroidapps.bettertermpro/bin/ssh /system/xbin/ssh
I checked, and BTEP creates it's own home and .ssh directories at /data/data/com.magicandroidapps.bettertermpro/home/.ssh and the ssh command uses the known_hosts file from there, so basically, BTEP might be the best way to do all this but it costs a few bucks in the market.
This inspired me to start using rsync and I did successfully get it working with the below command:
Code:
rsync -rltDv -e "ssh -l USER -i /data/dropbear/dropbear_rsa_host_key -p XXXXX" --port=XXXXX [email protected]:/home/me/test /sdcard
rltDv is used to get around an rsync bug that gives chgrp errors. The -e command specifies the ssh command to use when connecting and I had to specify the user with "-l username", -i is the key to use which can be anywhere. You don't need the ssh option "-p XXXXX" unless you use something other than 22 for ssh. The same is probably true of the rsync --port=X option, but I didn't test it.
This worked successfully with GScript which is exactly what you're wanting. Here's the only downside.. Better Terminal Emulator Pro costs a few bucks so I don't know if it's worth it to you to get it for a replacement ssh binary that works with GScript.
EDIT: it's 2am and im half asleep so i hope all this makes sense. Can clarify tomorrow if needed
Thanks for the update, just got some time to pick this back up
sent from my nexus one from the future...
http://forum.xda-developers.com/showthread.php?p=8917482&highlight=rsync#post8917482
I read up on guides to fixing it, ordered a fastboot cable.
Back story: I stupidly wiped my entire KFHD, OS and all
Still can access TWRP, my question is, can it be fixed? Can i just plug my fastboot cable in and transfer CyanogenMod 10.1 and flash it?
Thank you for you help.
I think i can help you a little bit , did you try the adb sideload option?
if not , the only thing you need to do its send the .zip file via adb sideload and you are done
Use the factory/fastboot cable only to get into fastboot, but don't use it to enter commands or transfer files. Switch cables and use adb to transfer a new ROM to your sdcard
ThatLatinGuy said:
I think i can help you a little bit , did you try the adb sideload option?
if not , the only thing you need to do its send the .zip file via adb sideload and you are done
Click to expand...
Click to collapse
no. my kindle is wiped and I cannot connect it to my pc. It's detected but I can't find the empty folder to put stuff in
EDIT: Googled adb sideload and tried it out, my kindle isn't detected when i use the adb devices command. That's probably why it isn't working.
EDIT2: Fixed, many thanks to ThatLatinGuy.
RaptorYeshua said:
no. my kindle is wiped and I cannot connect it to my pc. It's detected but I can't find the empty folder to put stuff in
EDIT: Googled adb sideload and tried it out, my kindle isn't detected when i use the adb devices command. That's probably why it isn't working.
EDIT2: Fixed, many thanks to ThatLatinGuy.
Click to expand...
Click to collapse
You are welcome , and if you need something else just tell me
Can You Help Me?
I have a similar issue. It looks like the OS has been wiped from my Kindle Fire HD 7. My PC does detect it and I can see folders. They are empty, mostly. On start up I get "Kindle Fire". Then I get to a welcome screen with an android icon. I press start and it sits for a bit then a window pops up saying that there was an error. My PC does not detect my Kindle as ADB and it will not boot up in fastboot.
Rednival said:
I have a similar issue. It looks like the OS has been wiped from my Kindle Fire HD 7. My PC does detect it and I can see folders. They are empty, mostly. On start up I get "Kindle Fire". Then I get to a welcome screen with an android icon. I press start and it sits for a bit then a window pops up saying that there was an error. My PC does not detect my Kindle as ADB and it will not boot up in fastboot.
Click to expand...
Click to collapse
I think we need a little more information.
1. What were you trying to do when the OS disappeared?
2. Do you have a fastboot cable?
3. Did you back-up your Kindle stock images?
4. What do you want to achieve at the end? Stock OS or modified OS or what?
Did you follow the instructions for putting the kindle into ADB mode before the OS disappeared?
calkenneth said:
I think we need a little more information.
1. What were you trying to do when the OS disappeared?
2. Do you have a fastboot cable?
3. Did you back-up your Kindle stock images?
4. What do you want to achieve at the end? Stock OS or modified OS or what?
Did you follow the instructions for putting the kindle into ADB mode before the OS disappeared?
Click to expand...
Click to collapse
as calkenneth said we need more details if you want help , tell us what happened and who did you get wipe your os , then i will do my best to help you
Hi, I have a similar problem and was not sure whether to start a new thread or not.
I had tried rooting the 7HD and it only kind of worked.
It is still working for some things but not Netflix and Amazon video streaming so I would like to go back to the stock ROM. I have tried everything I have found online, and nothing is working. Unfortunately, the root I used did not include adding TWRP.
I just tried adb sideload as mentioned above but the instructions call for v1.0.029 or later and mine is 1.0.026 and I can't find a download link to that later version.
I have a fastboot cable and after four or five tries starting the 7hd, it will boot and stop at the Fatsboot but I can't do anything with it as it appears locked up.
With the standard cable I can see the Kindle on my win7pro-x64.
I have Superuser showing on the 7hd carousel.
When I plug the 7hd in, windows tries to install the drivers and then says, "drivers were not installed correctly. The Device Manager shows Kindle under "Other devices" but it has a yellow question mark.
...and when I run abd shell, it gets started OK, but hen says "Device not found," even though I can see the Folders with Windows Explorer.
Thanks for anything you can offer to get this unrooted.
Harry
I have the exact same problem as the OP, I tried sideloading but all I get is a bunch of gibberish adb related in the cmd window whenever I enter anything, i.e. adb push, adb device, adb sideload same stuff comes up in the cmd window but nothing is sideloaded onto the device. What am I doing wrong ? I was attempting to install paranoid android port, was wiping everything and in my eagerness I wiped the system/OS, can still enter twrp.... a bit of help would be appreciated!
CreamEggKing said:
I have the exact same problem as the OP, I tried sideloading but all I get is a bunch of gibberish adb related in the cmd window whenever I enter anything, i.e. adb push, adb device, adb sideload same stuff comes up in the cmd window but nothing is sideloaded onto the device. What am I doing wrong ? I was attempting to install paranoid android port, was wiping everything and in my eagerness I wiped the system/OS, can still enter twrp.... a bit of help would be appreciated!
Click to expand...
Click to collapse
It would he helpful to know exactly what messages you are receiving...
soupmagnet said:
It would he helpful to know exactly what messages you are receiving...
Click to expand...
Click to collapse
this is the message I recieve, a bunch of commands and explanation as to what adb commands do. :good:
I think either my xda app is glitching or that photo got resized so small the text is unreadable. But I am throwing a guess that the command syntax was wrong so adb threw up its default usage text. BTW here's a tip, instead of screen-shotting your PC, right click in the command prompt and press mark, it will let u highlight the text, when done highlighting, tap enter on the keyboard to copy, then you can paste the text here, preferably in code brackets if there is a lot. I find it funny most people don't know this considering how often most people use copy and paste now days, then again Microsoft didn't exactly label it very well. What exactly did you type into the command prompt?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
I think either my xda app is glitching or that photo got resized so small the text is unreadable. But I am throwing a guess that the command syntax was wrong so adb threw up its default usage text. BTW here's a tip, instead of screen-shotting your PC, right click in the command prompt and press mark, it will let u highlight the text, when done highlighting, tap enter on the keyboard to copy, then you can paste the text here, preferably in code brackets if there is a lot. I find it funny most people don't know this considering how often most people use copy and paste now days, then again Microsoft didn't exactly label it very well. What exactly did you type into the command prompt?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
the pic came up small because it is a thumbnail to the larger pic which is in photobucket, didnt want to flood he page with an overly large photo, thanks for the pro tip! didn't know that but it shall come in handy in future.
I typed in adb sideload /pa_tate-3.90-20130801.zip and then got the following:
hope it helps! yes I'm aware my first name is in there, not bothered! )
C:\Users\Wil>adb sideload pa_tate-3.90-20130801.zip
Android Debug Bridge version 1.0.29
-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <serial number> - directs command to the USB device or emulator w
ith
the given serial number. Overrides ANDROID_SERI
AL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number
is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number
is specified.
Using this command with no additional arguments
will disconnect from all connected TCP/IP devic
es.
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(-l means list but don't copy)
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] <file> - push this package file to the device and i
nstall it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
('-s' means install on SD card instead of inter
nal storage)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.
adb backup [-f <file>] [-apk|-noapk] [-shared|-noshared] [-all] [-system|-nosy
stem] [<packages...>]
- write an archive of the device's data to <file>
.
If no -f option is supplied then the data is wr
itten
to "backup.ab" in the current directory.
(-apk|-noapk enable/disable backup of the .apks
themselves
in the archive; the default is noapk.)
(-shared|-noshared enable/disable backup of the
device's
shared storage / SD card contents; the defau
lt is noshared.)
(-all means to back up all installed applicatio
ns)
(-system|-nosystem toggles whether -all automat
ically includes
system applications; the default is to inclu
de system apps)
(<packages...> is the list of applications to b
e backed up. If
the -all or -shared flags are passed, then t
he package
list is optional. Applications explicitly g
iven on the
command line will be included even if -nosys
tem would
ordinarily cause them to be omitted.)
adb restore <file> - restore device contents from the <file> backup
archive
adb help - show this help message
adb version - show version num
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on th
e specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be u
pdated.
- If it is "system" or "data", only the corresponding partition
is updated.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list
of the following values
1 or all, adb, sockets, packets, rwx, usb, sync
, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes prior
ity over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these de
bug tags are printed.
Click to expand...
Click to collapse
do I need to provide more detail ? because I'm pretty sure everything you need to know is right there. The OP solved his issue, would of been helpful if he said how?
Everything we need is right there, I'm trying to figure out why its doing that be cause the syntax looks correct to me. I'll do some checking on mine, have to ask, u did put the file your trying to side load in the same folder as the adb command right?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Everything we need is right there, I'm trying to figure out why its doing that be cause the syntax looks correct to me. I'll do some checking on mine, have to ask, u did put the file your trying to side load in the same folder as the adb command right?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
doh!
Its always the simple things we forget to do! Will try it in the morning and let you know! Cheers bub.
I placed the file in the android sdk folder at C:/Android SDK still no joy, keep getting the same message pop up..... is there a specific folder within android sdk it needs to be in ? build tools ? temp ? platform-tools ?
On a side not Amazon has agreed to send me another one. Theyve asked that I return this one after I get the new one, question, would they be bothered if I didn't ? Or would they try to charge me for the price of a second one ? latter option seems more likely imho...
The adb command I believe is in the platform tools folder, put it in there and try it. Also just call amazon and ask them to cancel it and tell them you got it working, I doubt there would be any problems.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
yeah I figured it was the platform tools folder, still nothing, I have tried various syntax entries followed the guidelines laid out by twrp for sideloading, still no joy, same bunch of adb commands are displayed after enter.... I do not know what I am doing wrong, this is not my first time working adb or with rooted devices.....
I need to push a certificate my university requires to connect to it's wi-fi in a way that it would be considered a system one so I won't need to set a security lock (something android requires for login storage).
I've done it before on my LG O2X but it was running ICS and in JB the method I used doesn't work (at one point I managed to wipe ALL certificates ). It used to be as simple as installing it, copying a folder, wiping storage login data and then pasting that folder back and rebooting. Now I've found at least 4 possible locations in which the certificate file can be stored .
So, anyone have an idea how to do it? And also which exact files should I copy (so I can create a zip to automate the process).
xswistaqx said:
I need to push a certificate my university requires to connect to it's wi-fi in a way that it would be considered a system one so I won't need to set a security lock (something android requires for login storage).
I've done it before on my LG O2X but it was running ICS and in JB the method I used doesn't work (at one point I managed to wipe ALL certificates ). It used to be as simple as installing it, copying a folder, wiping storage login data and then pasting that folder back and rebooting. Now I've found at least 4 possible locations in which the certificate file can be stored .
So, anyone have an idea how to do it? And also which exact files should I copy (so I can create a zip to automate the process).
Click to expand...
Click to collapse
I just figured this out yesterday with my 4.3 JB android phone. I have my own root CA that I use to secure my personal server that I wish to access from my phone, and some of the apps I use require a trusted (shows up green in your browser) SSL cert. Being a cheap b*@$ard, I decided to make my own instead of buying one - also, I can be fairly sure the FBI / NSA haven't messed with my own.
Anyway, here's what I did:
You need first to create the file in the format that android wants. In my case, the certificate file is simply named "ca.crt," so I'll use that in my examples. You'll need openssl installed on whatever computer you're using for this.
First, we need to create the file that's formatted right for the phone:
Code:
$ cp ca.crt ca_phone.crt
$ openssl x509 -in ca.crt -text -fingerprint -noout >> ca_phone.crt
This gives you a file that looks kind of like this:
Code:
-----BEGIN CERTIFICATE-----
(bunch of gobbledegook)
-----END CERTIFICATE-----
(bunch of info about your certificate)
SHA1 Fingerprint=(SHA1 fingerprint of your cert)
Now, the hard part. If you take a look at your phone, under /system/etc/security/cacerts, you will see there are a bunch of files in there that have weird-looking names like 216caf34.0 and such - basically an 8 byte hex name with a .0 extension. Each one of those is a factory-installed trusted certificate! In order for them to be recognized by your phone, they have to be:
1. located in /system/etc/security/cacerts
2. have the proper permissions
3. have the proper file name
I'll show you how to do all that, assuming you have a rooted phone and adb working.
First, the name has to be a "hash" of the certificate contents itself. I found this out from reading this page: http://blog.kylemanna.com/android/2013/06/02/android-ca-certificates/
The article is slightly wrong, though, because at least in the openssl install I have, there is no option called -subject_hash_old:
Code:
$ openssl x509 -in ca.crt -subject_hash -noout
(8 hexidecimal characters, i/e: deadbeef)
The (8 hexidecimal characters) that command spits out is to be your file name. Yours should be unique. For my example, I'll use deadbeef.
Code:
$ mv ca_phone.crt deadbeef.0
Now, lets look in your phone to make sure there isn't already a deadbeef.0 in /system/etc/security/cacerts. There shouldn't be, but if there is, we can do something about it.
Code:
## First, make sure you're running adb as root:
$ adb root
## Next, remount /system as read-write:
$ adb remount
## Now, go in:
$ adb shell
## You're now in your phone's file system. Check to see
## if there's already a cert there with your filename:
~> ls -la /system/etc/security/cacerts/dead*
If there is, you'll have to rename your file to deadbeef.1 .. the extension is there for the unlikely event that 2 different certs have the same subject_hash. Increment the extension until you have a file that doesn't exist in the phone's folder.
Now, get out of adb shell:
Code:
~> exit
Now that you're back in your certificate folder, you can push your cert to the phone:
Code:
$ adb push deadbeef.0 /system/etc/security/cacerts/deadbeef.0
## Now, lastly, we need to go back into the phone and make
## sure the permissions are right on that file:
## First, go into your phone:
$ adb shell
Now fix the perms:
~> chmod 644 /system/etc/security/cacerts/deadbeef.0
## Note that the file should also be owned by root and root. If it's not, do this:
~> chown root:root /system/etc/security/cacerts/deadbeef.0
And now you should be done. All that's left is to disconnect the USB cable and reboot your phone. Now your cert should be installed and recognized without having to lock your screen.
Hopefully I've given you enough information that you can create a flashable ZIP file with your cert in the right place so you can just flash that after flashing a new ROM and have everything work great.
Good luck!