Related
Prerequisites have...
A:android-sdk-windows installed
B: (on your phone) go to menu>settings>applications>developement and make sure usb debugging is checked.
C: the file you are pushing must be placed in the tools folder of adb so if you are pushing file "build.prop.txt" this needs to be downloaded/copy and pasted in C:\android-sdk-windows\tools
1: go to run and type cmd (or just open your command prompt)
2: cd C:\android-sdk-windows\tools
3: adb remount
4: adb devices *if everything is set up right this should output a serial number*
5: adb push FFFFFFF.FFF /#####/###### *i hope my notes help here you need to put the file name in for the F(s) and in the pound signs you put the destination on the devices example adb push build.prop.txt /system/bin
6. repeat step 3 for multiple files
7. adb reboot this is how you finish
usadevil7193 said:
hi mate...i m new to android..i own a nexus1..hav rooted without unlockin d bootloader..i am tryin to push d track ball to wake mod...evry time i type adb remount it says permission denied..any ideas to get things workin...???????
Click to expand...
Click to collapse
Welcome to XDA and Android! Are you trying to get help for your Nexus One? This forum here is specifically for the HTC Hero CDMA.
You will probably find better and more specific help in the Nexus One forums which are here: http://forum.xda-developers.com/forumdisplay.php?f=556
Great post, very easy to follow, thank you.
yea I'm trying to do this, over and over, but with not luck. i have sdk on my pc and im running the cmd prompt to run adb remount & devices and its not picking up the phone, wth is going on, plz help
this also works for the samsung Galaxy S in recovery mode.
mikeybonez28 said:
yea I'm trying to do this, over and over, but with not luck. i have sdk on my pc and im running the cmd prompt to run adb remount & devices and its not picking up the phone, wth is going on, plz help
Click to expand...
Click to collapse
mine shows up but then says error, device offline
hi, i have adb recognizing my phone, but i still can't seem to push the files over.... every time i try, i get 'cannot stat 'su' : No such file or directory'. i have made sure over and over to put the files in the same folder where adb is.... actually i have tried placing the files in the tools folder, as well as the platform-tools folder, and i keep getting that error when i try to push anything.
any suggestions? thx
yogi2010 said:
hi, i have adb recognizing my phone, but i still can't seem to push the files over.... every time i try, i get 'cannot stat 'su' : No such file or directory'. i have made sure over and over to put the files in the same folder where adb is.... actually i have tried placing the files in the tools folder, as well as the platform-tools folder, and i keep getting that error when i try to push anything.
any suggestions? thx
Click to expand...
Click to collapse
i had the same issue with something i was trying to push. I think you need to make sure you have exactly the same file name like caps and all. i was trying to push rootexplorer.apk and i got the same message but i then changed it to RootExplorer.apk and it work.(notice the difference in caps)
just watch this and it'll explain everything.
http://www.youtube.com/xdadevelopers
Does it matter where sdk is installed my file path is
C:\Program Files\Android\android-sdk\tools
instead of
C:\android-sdk-windows\tools.
I just installed it in the default location.
I type adb remount and get the not recognised command.....
Thanks.
I don't think my phone is being picked up?
{LCD}Stelios said:
Does it matter where sdk is installed my file path is
C:\Program Files\Android\android-sdk\tools
instead of
C:\android-sdk-windows\tools.
I just installed it in the default location.
I type adb remount and get the not recognised command.....
Thanks.
I don't think my phone is being picked up?
Click to expand...
Click to collapse
Make sure your have the drivers for your phone installed first of all.....Then, in your command prompt you have to change directories to the sdk (which you made harder by not installing to C:\
Try: cd Program Files\Android\android-sdk\tools
Then type: adb devices
That should return "xxxxxxdevice" connected....Then you know you have it set up.
Look in kyouko sig he has all the commands for adb
Sent from my HERO200 using XDA App
Bierce22 said:
just watch this and it'll explain everything.
http://www.youtube.com/xdadevelopers
Click to expand...
Click to collapse
great video arse....thanks for the help donkey
Flashing fresh ROM via ADB in Linux
Hello there.
M volumeUp and VolumeDown buttons are broken on my rooted Desire HD, so I cannot go through CWM any longer.
With regard to this post, I would ask the followings:
1) can this method be used to flash a new ROM (i.e. Coredroid, Leedroid..) without the need of those 2 buttons ?
2) My PC runs Linux. How does it work with this O.S. ?
Thanks
paolo
pacut said:
Hello there.
M volumeUp and VolumeDown buttons are broken on my rooted Desire HD, so I cannot go through CWM any longer.
With regard to this post, I would ask the followings:
1) can this method be used to flash a new ROM (i.e. Coredroid, Leedroid..) without the need of those 2 buttons ?
2) My PC runs Linux. How does it work with this O.S. ?
Thanks
paolo
Click to expand...
Click to collapse
There is a thread somewhere on how to flash without a SD card and flashed using adb I believe, but don't take my word for it. Adb works fine with Linux, just have to set it up differently. Look in my sig and select the compile aosp on Ubuntu one and follow instructions on getting the USB set up.
Sent from Dorian's HTC Hero CDMA
Yes, I saw it. It's http://forum.xda-developers.com/showthread.php?t=911228
The fact is...still have to navigate through menu via VolumeUp/volumeDown buttons
Maybe through ROM manager, premium, I can install ROM direclty.
I am gonna trying
YES ! It works !
Hi I need help. I accidentally wipped my phone in CWM and now I'm trying to use adb push to push the update.zip into my phone sd everything seems to work but then in CMW it says there are no files..
any suggestions?
[Edit]
nevermind
I kept trying different locations
not sure which one did the trick but I'll list the one's I tried
so \update.zip /sdcard/
.... /sdcard/update.zip
(note I put "/update.zip" thinking maybe it needed to be reallocated to the same file/destination
Can i use adb push *.apk /system/app to push several files at once, and then repeat but using *.odex instead of *.apk? I keep ending up getting the same error, and i want to find out which app is messing with me...
rulermon said:
Prerequisites have...
A:android-sdk-windows installed
B: (on your phone) go to menu>settings>applications>developement and make sure usb debugging is checked.
C: the file you are pushing must be placed in the tools folder of adb so if you are pushing file "build.prop.txt" this needs to be downloaded/copy and pasted in C:\android-sdk-windows\tools
1: go to run and type cmd (or just open your command prompt)
2: cd C:\android-sdk-windows\tools
3: adb remount
4: adb devices *if everything is set up right this should output a serial number*
5: adb push FFFFFFF.FFF /#####/###### *i hope my notes help here you need to put the file name in for the F(s) and in the pound signs you put the destination on the devices example adb push build.prop.txt /system/bin
6. repeat step 3 for multiple files
7. adb reboot this is how you finish
Click to expand...
Click to collapse
Hey guys ...
I have also rooted my phone , everything was OK until one day i tried to write something to /system/app and i recieve this error:
in Addition , i am writing "adb shell" and it shows me $
if i am doing adb shell --> $ --> su --> it shows #
Can some1 knows what is the problem?
Hello Everyone
OK so this is a really newb question but I was confused on the syntax of the adb pull command. I know the syntax is:
adb pull <remote> <local>I am confused on the remote an local part. Which one of these is the file to copy from the phone and which is the location to put the copied file?
Being that the command says copy files from device that would lead me to think that local would be the file you want to copy and remote is where you want the file to go, but I am not certain.
How do you structure the path to where you want to copy the file to? If it is going to the computer how do you start it, if you want to copy it to the sdcard of the phone how do you start it?
Thanks
dsMA said:
Hello Everyone
OK so this is a really newb question but I was confused on the syntax of the adb pull command. I know the syntax is:
adb pull <remote> <local>I am confused on the remote an local part. Which one of these is the file to copy from the phone and which is the location to put the copied file?
Being that the command says copy files from device that would lead me to think that local would be the file you want to copy and remote is where you want the file to go, but I am not certain.
How do you structure the path to where you want to copy the file to? If it is going to the computer how do you start it, if you want to copy it to the sdcard of the phone how do you start it?
Thanks
Click to expand...
Click to collapse
If your using Mac OS you can use my app to do it
Anyway, remote is the device. Local is the computer. so it could be like ./adb pull /sdcard/img.jpg /user/you/desktop/
Edit: just re-read your post.
Are you saying you want to push files to the device???
that would be ./adb push (file on computer) location on device (i.e. /sdcard/ or /system/app, etc)
I have learned alot from this site so i figured i'd give something back. these are the the two easiest methods i have found for setting up the android debug bridge. one for windows and one for linux... these instructions should work for any version of windows.
first make sure you download the latest sdk by going to android.com and clicking on developers.
windows:
after you have download the sdk, unzip it to your desktop. rename it to sdk. cut the UNzipped folder on the desktop that you just renamed by right clicking and hitting "cut" then go to start>my computer>c: and paste the folder here. now go into the new "sdk" folder and right click on the "tools" folder and click "send to" then choose "desktop (as shortcut)" you should now have a shortcut on the desktop called "tools-shortcut"
now for the easy part: hold shift and right click on tools-shorcut, holding shift adds the option "open command window here" to the context menu that comes up so click on that. now just make sure your phone is connected to the computer and on ur phone debugging is enabled (menu>applications>development>debugging). on ur command window that came up you should see a black box with white text and the cmd should be c:\sdk\tools> just type "adb devices" and you should see your phone under "list of devices attached" if you do see it you should be able to start running adb commands
adb pull "/location to file or folder on phone" -(the pulled folder or file will be in the tools folder we created earlier which you can still access by clicking on the tools-shortcut on your desktop)
adb push "name of file or folder to be placed on the phone sdcard" -(make sure the file or folder you wish to place on the phone has been placed in the "tools" folder on the computer, again its the same folder the "tools-shortcut" opens up)
hint and examples: i have found a good way to back up and reinstall all ur apps using just adb push and pull. just experimenting and playing around with it i have found you can accomplish installing with just knowing these commands above... if you plan to data wipe and flash a new rom but you don't want to go through the tedious task of reinstalling and you have a rooted android phone then you may use this method to backup/reinstall ALL of your apps. plus this will give you good practice using adb.
backup example:
adb pull /data/app .... let it finish
adb pull /data/app-private ...let it finish
now you should have ALL of ur apps in ur tools folder on ur computer! in the tools folder, create a new folder and name it what u want, i named mine APPS4EVO because i have an evo and and epic and some apps don't work for both so i keep them seperate. cut and paste all of ur apps and put them into your newly made folder. now back to the adb window
restore example:
adb push /APPS4EVO /data/app/
this will push all of your apps in your backed up folder you made earlier to the folder where apps go when they are installed and if you wait 1-10 minutes depending on how many apps you have you should be able to see them on ur phone as if you had installed them one by one. also notice the space between /APPS4EVO and /data/app/ the space seperates the folder from inside ur tools folder you wish to install and the location you wish to put them on ur phone. please be aware that you do not need to type c:\sdk\tools\APPS4EVO because the command window is already being ran in the tools folder, so the location would just be /APPS4EVO in my case.
adb shell -opens up the terminal shell to run commands specifically for the phone, while in the shell you cannot run other "adb xxxxx" commands, you will have to exit the shell by typing "exit"
OPTIONAL: i marked this as optional bc with the above it is not necessary... i have never done this and my adb works great but i have seen it often in other tutorials around the web.... i believe its only necessary on windows 7 and maybe vista. go to start then right click on "my computer" and click on "properties" then in the left pane click on "advanced system settings" then in the window that pops up click on "environment varables" button, in the next window that pops up, under "system variables" scroll down to the "path" variable and double click it. in the "variable value" box do NOT erase anything but add ";c:\sdk\tools" (without quotations). then click ok on all the windows cuz ur done.
thats all for windows.
linux (ubuntu)
extract the sdk to your home/name/ folder and rename it to sdk. now right click on the folder and go to permissions and make sure (run as executable) is checked, now go into the folder and do the same permission change to the tools directory.
now you should be able to run adb commands in the terminal when your phone is connected. same as in windows except your commands will be preceded by your tools folder location....
FOR EXAMPLE:
/home/jay/sdk/tools/adb devices
/home/jay/sdk/tools/adb push xxxx xxx
/home/jay/sdk/tools/adb pull xxxx
EXTRA:
if your having troubles connecting ur phone to ur computer over usb, even after installing drivers, like i sometimes have with my epic, you can download "wireless adb" from the market which i found to be surprisingly easy to use, just like if u were connected by usb, except under adb devices you will show up as your gateway address not ur device name but trust it still works the same.
good luck everyone, i hope this post isn't redundant and i really hope i help someone out there just starting! adb is confusing at first.
Hi All,
I am in the process of trying to root and install a custom rom on my Nexus 4 4.4.2. I am a new linux user (Linux Mint 16) and my rooting experience is limited. When I try to do an "abd pull /sdcard/ /sdcard/" this is what it says
adb pull /sdcard/ /sdcard/
pull: building file list...
pull: /sdcard/Android/data/com.google.android.gallery3d/cache/imgcache.1 -> /sdcard/Android/data/com.google.android.gallery3d/cache/imgcache.1
cannot create '/sdcard/Android/data/com.google.android.gallery3d/cache/imgcache.1': No such file or directory
I was able to successfully do an abd backup...
USB debugging is enabled.
I get the same error whether the phone is connected as a Media device (MTP) or Camera (PTP).
any reason why the pull command wont work?
Any help is appreciated!
smokewagon said:
Hi All,
I am in the process of trying to root and install a custom rom on my Nexus 4 4.4.2. I am a new linux user (Linux Mint 16) and my rooting experience is limited. When I try to do an "abd pull /sdcard/ /sdcard/" this is what it says
adb pull /sdcard/ /sdcard/
pull: building file list...
pull: /sdcard/Android/data/com.google.android.gallery3d/cache/imgcache.1 -> /sdcard/Android/data/com.google.android.gallery3d/cache/imgcache.1
cannot create '/sdcard/Android/data/com.google.android.gallery3d/cache/imgcache.1': No such file or directory
I was able to successfully do an abd backup...
USB debugging is enabled.
I get the same error whether the phone is connected as a Media device (MTP) or Camera (PTP).
any reason why the pull command wont work?
Any help is appreciated!
Click to expand...
Click to collapse
Maybe this will help?
http://www.herongyang.com/Android/adb-push-and-pull-Command.html
Not a big fan of the CLI.
Sent from my Nexus 7 (2013)
Your problem (almost certainly) is that you don't have a /sdcard directory (folder) on your computer unless you created one (there certainly is no default /sdcard in a linux desktop system).
I also don't know how you installed ADB on your computer.
(This should work, otherwise I'll have to change what I wrote below).
Try this:
$ cd ~/Desktop
(This changes you to your desktop directory, if you are not already there)
$ mkdir sdcard
(this will make a new directory called "sdcard" on your desktop, you should see it pop up on your desktop)
$ adb pull /sdcard/ ~/Desktop/sdcard
(should pull the contents of /sdcard from your phone and put them in your newly created directory on your desktop: ~/Desktop/sdcard)
BAM
A little extra basic info for you, and welcome to linux. Soon you have the power to take over the world (ha ha ha... no, actually I'm not kidding at all).
As a basic rule, you should pretty much always be working inside of your home directory, for dealing with your personal files. Your home directory is /home/yourname. On my computers, my home is /home/kirk. My wife's home directory is /home/amy.
"~" is a shortcut for the home directory, for whomever is logged in at that moment.
If you wanted something that is on your desktop, it would be in the directory: /home/yourname/Desktop (~/Desktop). If you wanted to use your documents directory, it is : /home/yourname/Documents(~/Documents).
/home/yourname is where you usually where want to do your stuff.
"/" is the very root directory of the whole system, so you would be better off not creating and doing things like making directories like "/sdcard". That's a bad move. Leave root for system files. Not that you are necessarily going to destroy something by creating a /sdcard directory. But it'll cause you a few hassles.
So, use /home/yourname/sdcard (~/sdcard). Or if you want it on your desktop, (like I did above) use /home/yourname/Desktop/sdcard (~/Desktop/sdcard). Doing things inside of /home/yourname(~) means that you are the owner of that folder and everything in it, not root.
Otherwise you will just be causing headaches for yourself and having to grant yourself root permissions to work with those files (hassle). There's no good reason to do that to yourself. And if you did give yourself root permissions, and screwed up other stuff in the root directory like in: /etc or /dev or /bin, then you will REALLY be irritated.
Stick to your home for your personal files. /home/yourname (~)
Leave "/" or the "root" directory for system files.
You could check my little bash program for adb for Linux too. It's a program to be used in the terminal and it'll pull data off the sdcard etc. You can find it here
Sent from my Nexus 4 running Android 4.4
Thank you all for the help, I'll let you know how it goes.
Do I need drivers for my nexus 4 to work with Linux?
Sent from my Nexus 4 using Tapatalk
smokewagon said:
Thank you all for the help, I'll let you know how it goes.
Do I need drivers for my nexus 4 to work with Linux?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Try it without any installation of drivers just install adb tools and try the command line or my little tool. If it's not working, check the guides how to set up the usb-rules for adb
Sent from my Nexus 4 running Android 4.4
Thanks, will do.
Sent from my Nexus 4 using Tapatalk
iowabeakster said:
Try this:
$ cd ~/Desktop
(This changes you to your desktop directory, if you are not already there)
$ mkdir sdcard
(this will make a new directory called "sdcard" on your desktop, you should see it pop up on your desktop)
$ adb pull /sdcard/ ~/Desktop/sdcard
(should pull the contents of /sdcard from your phone and put them in your newly created directory on your desktop: ~/Desktop/sdcard)
BAM
Click to expand...
Click to collapse
BAM INDEED! It worked! I am pulling the contents now. Thanks a ton, and thanks for the other basic linux info, I will put it to good use.
Any other tips on using Linux to root android?
Shooooot....
So after the pull command finished, i opened the sdcard directory I created on my desktop, and it was empty....the pull command said this when it was done...
1733 files pulled. 0 files skipped.
2129 KB/s (995292697 bytes in 456.480s)
Any ideas?
Ok, I played with some settings and got it to work, though I don't know why it worked.
USB Debugged is enabled.
The first time I tried to 'pull' i had my USB computer connection set to "Camera (PTP)" - it didn't work.
I tried again changing the USB computer connection to "Media device (MTP)" - it didn't work.
I changed it back to "Camera (PTP)" and my computer recognized it in a different way than the first time (a dialog box popped up asking me what I wanted to do with the pictures that were on the device I had connected, this didn't happen the first time).
I am glad the pull command finally worked, I just wish I knew why.
I guess it's a tough road being a linux NOOB and a (near) Android NOOB. It's good to learn something new and keep my brain young.
So I've come across a quirk that I haven't been able to resolve and haven't noticed before getting my G5. When I run
Code:
adb devices
on my computer with my phone connected, it shows my device but says unauthorized. I cannot seem to authorize my device. I have tried:
Revoke USB Debugging Authorizations (option not available in Developer Options)
Delete adb_keys in /data/misc/adb/ (No adb_keys file in the folder)
Create adb_keys file on my computer using the computers public key (Phone deletes this file on boot)
I realize this is more of a general Android question, but as it hasn't happened to me on any other phone, I wanted to see if anyone else was having this trouble.
Same boat here, haven't been able to fix the issue. I believe there's a testboot3.img floating around that fixes it. I downloaded it awhile ago as I keep a eye on everything for this device. But I don't know if it does and if you flash a new boot.img I'd think it would override it. I've tried your method as well.
I am also having this issue. Does anyone have a solution?
To update this for those that need it; this toolkit worked to fix this issue for me in Linux. I just hit the red block in the upper left that says "unauthorized device" when the phone was plugged in. Not sure what the kit did but then my phone finally asked if I wanted to allow the computer access. After doing that I finally got "authorized" when running "adb devices" in ubuntu.
https://forum.xda-developers.com/g5-plus/development/toolkit-moto-g5-plus-toolkit-root-t3605203
A fix if you are running Windows (or Linux)
I just found a fix that worked for me.
(Although i got the "unauthorized" status with the phone running as usual, I didn't get the same problem when in recovery mode.)
I followed instructions from this site but needed to change Linux commands to simliar Windows commands: http://www.neuraldump.com/2017/05/how-to-fix-adb-unauthorized-error/
If you are using Windows, you'll need to follow the commands below:
- First things first:
- Phone: Check if you have a file called adb_keys located at: /data/misc/adb/adb_keys. If you have it, i would recommend you to backup the file. (I didn't have it.)
- Windows:You'll need to have a file called adbkey.pub located at C:\users\UserAccount\.android\
- Boot into recovery mode.
- Plug your phone into PC.
- Open cmd and run adb devices. It would show "recovery" instead "unauthorized".
- Create a new file called adb_keys file on your PC:
Code:
type NUL > adb_keys
- Now you need to copy the contents from the adbkey.pub to adb_keys, the new file you just created:
adbkey.pub is located at C:\users\UserAccount\.android\
(Needless to say you need to replace "UserAccount" when running the command)
Code:
type c:\users\UserAccount\.android\adbkey.pub > adb_keys
- Upload the adb_keys file to your phone:
Code:
adb push adb_keys /data/misc/adb/adb_keys
- Reboot and run adb devices. It should be working now.
(Thanks to Tony, the guy who posted this fix in his blog).
need help please. Cant do it. I have that problem on my moto g5 plus. Dont understand this. Windows 10 pro computer.
Edit: I solved using the adb_keys from my xperia and using root explorer on my moto g5 plus and paste on data/misc/adb/adb_keys
Awesome! You may need to change permissions like I did from using root user within a debian chroot. Just like ssh keys....
From twrp recovery console.
chmod 0644 /data/misc/adb/adb_keys
chown -u shell /data/misc/adb/adb_keys
That got me authorized and running a root shell to spoof fingerprint before getting past first Hello page of setup
Yep, it works on my side as well on a Samsung galaxy Note 3, RROS 8.6.1, very good tip!:good:
@mnoguti
thank you, this fix my Verizon Note 4 issue with Smali Patcher not detecting my phone.
Thank you! My Galaxy S4 GT-i9505 also had this issue and your guide let me succesfully use adb normally again!
mnoguti said:
A fix if you are running Windows (or Linux)
I just found a fix that worked for me.
(Although i got the "unauthorized" status with the phone running as usual, I didn't get the same problem when in recovery mode.)
I followed instructions from this site but needed to change Linux commands to simliar Windows commands: http://www.neuraldump.com/2017/05/how-to-fix-adb-unauthorized-error/
If you are using Windows, you'll need to follow the commands below:
- First things first:
- Phone: Check if you have a file called adb_keys located at: /data/misc/adb/adb_keys. If you have it, i would recommend you to backup the file. (I didn't have it.)
- Windows:You'll need to have a file called adbkey.pub located at C:\users\UserAccount\.android\
- Boot into recovery mode.
- Plug your phone into PC.
- Open cmd and run adb devices. It would show "recovery" instead "unauthorized".
- Create a new file called adb_keys file on your PC:
Code:
type NUL > adb_keys
- Now you need to copy the contents from the adbkey.pub to adb_keys, the new file you just created:
adbkey.pub is located at C:\users\UserAccount\.android\
(Needless to say you need to replace "UserAccount" when running the command)
Code:
type c:\users\UserAccount\.android\adbkey.pub > adb_keys
- Upload the adb_keys file to your phone:
Code:
adb push adb_keys /data/misc/adb/adb_keys
- Reboot and run adb devices. It should be working now.
(Thanks to Tony, the guy who posted this fix in his blog).
Click to expand...
Click to collapse
Thank you so much, you saved my life