My "adb push" command is not working. When I type it in, the command prompt seems to run "adb help". No error message, just the list of possible commands. See the attached screenshot.
Does anybody know what's happening?
Computer: Windows 7
Device: Verizon Galaxy Nexus (toro)
Version: 4.2.2Kernel Version: 3.0.85-franco.Kernel-nightlyBuild: JDQ39
The "adb push" command is used to push files to your device.
Typing "adb push" won't do anything besides displaying all the adb functions.
To push something, your command must be something like "adb push whateverthefileis system/bin" the "system/bin" is the destination where it is to be pushed, for example if you want to push an app you do, "adb push android.apk system/app"
Make sure your drivers for phone is installed properly.
IF I HELPED HIT THANKS
Click to expand...
Click to collapse
Sent from my Nexus F...Fi...Fii...Ahem...*clears throat*... Five.
solution???
Did you put your phone in recovery mode first?
krishneelg3 said:
The "adb push" command is used to push files to your device.
Typing "adb push" won't do anything besides displaying all the adb functions.
To push something, your command must be something like "adb push whateverthefileis system/bin" the "system/bin" is the destination where it is to be pushed, for example if you want to push an app you do, "adb push android.apk system/app"
Make sure your drivers for phone is installed properly.
Sent from my Nexus F...Fi...Fii...Ahem...*clears throat*... Five.
Click to expand...
Click to collapse
I had typed in the correct syntax for the command, but will try updating drivers. Thanks!
ADB push just scrolls commands
I am trying to use ADB with telnet to root my Droid Maxx. I have been desperately trying to use Jcase's method. All my commands work, except the push command. I can telnet, my drivers are all up to date, my phone is on debug, install unknown sources etc...Everything seems to be in order, but the su and RockMyMoto.jar will not push, just a scrolling of commands. Any help would be most appreciated.
Thank you
Related
I recently set up Ubuntu Karmic on my laptop's second hard drive, and I finished setting up Eclipse and the Android SDK yesterday. I set up ADB to work directly from the terminal without changing to the SDK Tools directory, and it works... kind of. I can get some ADB commands working, but most others won't. The only things that really work are "adb help" and "adb devices" at the moment. "adb install", "adb push" / "adb pull", and other similar commands seem to register, but then nothing happens after that- the terminal freezes, and inputting keys shows other characters. ]]^A and stuff like that. Can anyone help?
Ubuntu 9.10x64 adb works with sudo
$ sudo adb push...
I usually make sure the first adb command I use is sudo'd so it starts the daemon as root.
adb help - does not send any data to your droid. It's internal
adb device - shows which devices are on the USB bus.
The other adb command need to talk to the devices and depending on how your udev protections, device protections, and your personal group memberships are... it may not work.
sudo works for me always.
Ehud
So I am currently in the cmd for windows and when I type the "adb push exploid /sqlite_stmt_journals" I get this message:
"Failed to copy exploid to /sqlite_stmt_journals" Read only file system.
What I am doing wrong? Bt the way I am following the post911 guide for the rogers HTC dream and currently in this directory for cmd "C:\adb\platform-tools\" (renamed the folder to adb as I thought I was supposed to do).
All help appreciated!
Update: So my phone wasn't being detected on the computer and I believe that's the reason why. I disconnected and plugged it back in, and did the sync with windows pushed the command and it went through. Followed the rest of the guide and when i typed adb shell i got a dollar sign only. Continued following the guide and I still have the dollar sign instead of "C:\adb|etc.." and the adb shell command wont work.
1. No idea what you're talking about or relating to.
2. Try using "adb remount" then try again.
Scorpia said:
1. No idea what you're talking about or relating to.
2. Try using "adb remount" then try again.
Click to expand...
Click to collapse
Title says Rogers HTC Dream. According to this guide I am trying to follow the command "adb push exploid /sqlite_stmt_journals" and i get the error message stated above.
What can i do to get past this? Adb remount didn't do anything.
Update: So my phone wasn't being detected on the computer and I believe that's the reason why. I disconnected and plugged it back in, and did the sync with windows pushed the command and it went through. Followed the rest of the guide and when i typed adb shell i got a dollar sign only. Continued following the guide and I still have the dollar sign instead of "C:\adb|etc.." and the adb shell command wont work.
I used a Super Wipe Full and my new ROM was in the internal storage (Not on SD) So I lost everything plus the new ROM that I should use to install now.
So I have nothing to install on it now. It doesn't start up, the only thing I can do is go at ClockworkMod (Vol+Down) and travel there but doing nothing very useful.
How can I copy and past my ROM to the SD?
From windows.
Thank you, sorry I am dumb, =/
You need to boot to CWM, then connect it to your PC using the charger cable.
Update the drivers to use the NakedDrivers.
Then get a copy of ADB.exe from the android SDK.
Download the ROM you want to flash and put it into the same directory as your ADB.exe file.
Open a command prompt and use the "cd" command to get to the directory with ADB.exe.
Then type this:
adb push ROM.zip /sdcard/
Assuming your ROM is called ROM.zip.
Then you can flash the ROM from CWM.
frederuco said:
You need to boot to CWM, then connect it to your PC using the charger cable.
Update the drivers to use the NakedDrivers.
Then get a copy of ADB.exe from the android SDK.
Download the ROM you want to flash and put it into the same directory as your ADB.exe file.
Open a command prompt and use the "cd" command to get to the directory with ADB.exe.
Then type this:
adb push ROM.zip /sdcard/
Assuming your ROM is called ROM.zip.
Then you can flash the ROM from CWM.
Click to expand...
Click to collapse
+1 Been there done that.
D
frederuco said:
You need to boot to CWM, then connect it to your PC using the charger cable.
Update the drivers to use the NakedDrivers.
Then get a copy of ADB.exe from the android SDK.
Download the ROM you want to flash and put it into the same directory as your ADB.exe file.
Open a command prompt and use the "cd" command to get to the directory with ADB.exe.
Then type this:
adb push ROM.zip /sdcard/
Assuming your ROM is called ROM.zip.
Then you can flash the ROM from CWM.
Click to expand...
Click to collapse
Thanks, gonna try later and edit here.
Edit. 1
So for Nakeddrivers should I download this one?
http://forum.xda-developers.com/showthread.php?t=1514942
And do what this guy says?
http://forum.xda-developers.com/showthread.php?t=2139767
Thank you.
frederuco said:
You need to boot to CWM, then connect it to your PC using the charger cable.
Update the drivers to use the NakedDrivers.
Then get a copy of ADB.exe from the android SDK.
Download the ROM you want to flash and put it into the same directory as your ADB.exe file.
Open a command prompt and use the "cd" command to get to the directory with ADB.exe.
Then type this:
adb push ROM.zip /sdcard/
Assuming your ROM is called ROM.zip.
Then you can flash the ROM from CWM.
Click to expand...
Click to collapse
I got a problem, when I type "adb push "ROM".zip /sdcard/"
It says: (by the first try)
"adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:"
(Second and other)
"adb server is out of date. killing...
* daemon started successfully *
protocol failure"
I downloaded this SDK:
http://developer.android.com/sdk/index.html
And this NakedDrivers:
http://forum.xda-developers.com/showthread.php?t=1514942
Help please =/
Did you get the ADB drivers installed?
I often get the same errors on ADB but it should eventually work.
What happens if you type:
adb devices
It should find your tablet.
frederuco said:
Did you get the ADB drivers installed?
I often get the same errors on ADB but it should eventually work.
What happens if you type:
adb devices
It should find your tablet.
Click to expand...
Click to collapse
After 3 errors with "adb devices" I got this:
"adb server is out of date. killing...
* daemon started successfully *
list of devices attached
37c624242616657 recovery"
What now?
type this:
adb shell
ls -l
see what the ouput is. Is there a sdcard directory listed?
If so, type exit so you are out of the ADB shell, then type:
adb push ROM.zip /sdcard/
frederuco said:
type this:
adb shell
ls -l
see what the ouput is. Is there a sdcard directory listed?
If so, type exit so you are out of the ADB shell, then type:
adb push ROM.zip /sdcard/
Click to expand...
Click to collapse
With "adb shell" I got few errors listed above and then this:
"adb server is out...
* daeomon started successfully *
~ #"
Thats all.
What happens if you type "ls -l" at the # prompt?
frederuco said:
What happens if you type "ls -l" at the # prompt?
Click to expand...
Click to collapse
Got a lot of suff:
http://img267.imageshack.us/img267/2112/31377010.jpg
If this helps, my deviece is a Asus Transformer TF101
I am trying to install the android revolution HD 3.6 rom
Filipebergami said:
Got a lot of suff:
http://img267.imageshack.us/img267/2112/31377010.jpg
If this helps, my deviece is a Asus Transformer TF101
I am trying to install the android revolution HD 3.6 rom
Click to expand...
Click to collapse
Perfect.
Now, download the android revolution HD 3.6 ROM if you have not done so. rename it to ROM.zip and put it in the c:\dev\adt\sdk\platform-tools directory.
Next, at the c:\dev\adt\sdk\platform-tools> prompt type:
adb push ROM.zip /sdcard/
It should then push the file ROM.zip to your internal SD card directory. It will say how many bytes were pushed succesfully when it finishes. If you get an error that it failed to start the daemon, just keep issuing the adb push ROM.zip /sdcard/ command until it works.
frederuco said:
Perfect.
Now, download the android revolution HD 3.6 ROM if you have not done so. rename it to ROM.zip and put it in the c:\dev\adt\sdk\platform-tools directory.
Next, at the c:\dev\adt\sdk\platform-tools> prompt type:
adb push ROM.zip /sdcard/
It should then push the file ROM.zip to your internal SD card directory. It will say how many bytes were pushed succesfully when it finishes. If you get an error that it failed to start the daemon, just keep issuing the adb push ROM.zip /sdcard/ command until it works.
Click to expand...
Click to collapse
YES !!!
After about 30 tries it worked, I got a bit scared when after * daemon thingy * got no answer for few minutes, but I manage to install it throught CW.
Thank you a lot.
I've been following this guide http://forum.xda-developers.com/showthread.php?t=1917237&nocache=1 to set up ADB for my phone and macbook, and when i try the "./adb devices" command to try and ID my device, it isn't working. Ive already downloaded the SDK package from the website, copied and pasted "adb" and "fast boot" into the root of my sdk file in the bundle. I included some snapshots in case I'm inputting the file path incorrectly. Any help would be awesome! My power button stopped working on my phone so I'm trying to set up ADB so i can just adb reboot whenever my phone shuts off or anything like that. The first screenshot is my current file path for the adb and fastboot files and the second is just my attempts at trying the "./adb devices" command.
Ironcheeks said:
I've been following this guide http://forum.xda-developers.com/showthread.php?t=1917237&nocache=1 to set up ADB for my phone and macbook, and when i try the "./adb devices" command to try and ID my device, it isn't working. Ive already downloaded the SDK package from the website, copied and pasted "adb" and "fast boot" into the root of my sdk file in the bundle. I included some snapshots in case I'm inputting the file path incorrectly. Any help would be awesome! My power button stopped working on my phone so I'm trying to set up ADB so i can just adb reboot whenever my phone shuts off or anything like that. The first screenshot is my current file path for the adb and fastboot files and the second is just my attempts at trying the "./adb devices" command.
Click to expand...
Click to collapse
First, it's impossible to access your phone's adbd server when it is off.
And adb needs to be in the current folder.
Use ls to see the contents of the folder you are in.
You should try ./adb first.
It's better to boot hirens boot cd.
Then use the tool in my signature.
An even better way to do this is to trust your technolust and take your phone apart and try to identify and fix the problem, or put it back to stock and send it in for warranty.
Lgrootnoob said:
First, it's impossible to access your phone's adbd server when it is off.
And adb needs to be in the current folder.
Use ls to see the contents of the folder you are in.
You should try ./adb first.
It's better to boot hirens boot cd.
Then use the tool in my signature.
An even better way to do this is to trust your technolust and take your phone apart and try to identify and fix the problem, or put it back to stock and send it in for warranty.
Click to expand...
Click to collapse
Thanks for giving such a helpful response what do you mean by adb needs to be in the current folder? and what is Is?
And I'm definitely planning on taking it apart. As soon as i can find a small enough screwdriver somewhere on campus, ill get right on it. Thanks again!
Ironcheeks said:
Thanks for giving such a helpful response what do you mean by adb needs to be in the current folder? and what is Is?
And I'm definitely planning on taking it apart. As soon as i can find a small enough screwdriver somewhere on campus, ill get right on it. Thanks again!
Click to expand...
Click to collapse
Your welcome!
I'm happy to help any time.
the . indicates the current folder(directory)
so when you type ./adb
it executes the adb file in . (the current folder)
ls is a command for listing the contents of the current folder. (Just like the dir command on windows)
Before you type ./adb you would want to make sure that adb is in . (The current folder)
Get it?
Lgrootnoob said:
Your welcome!
I'm happy to help any time.
the . indicates the current folder(directory)
so when you type ./adb
it executes the adb file in . (the current folder)
ls is a command for listing the contents of the current folder. (Just like the dir command on windows)
Before you type ./adb you would want to make sure that adb is in . (The current folder)
Get it?
Click to expand...
Click to collapse
Ahhh that makes sense.. so when I'm running terminal and since the adb file is in the sdk folder, i should make the command path (cd /Users/..etc) go up to the sdk folder in this case?
Ironcheeks said:
Ahhh that makes sense.. so when I'm running terminal and since the adb file is in the sdk folder, i should make the command path (cd /Users/..etc) go up to the sdk folder in this case?
Click to expand...
Click to collapse
Nevermind! got it to work after doing the above^. Thanks again for your help so any helpful adb commands i should know about? all i know is adb reboot and adb reboot recovery
Ironcheeks said:
Nevermind! got it to work after doing the above^. Thanks again for your help so any helpful adb commands i should know about? all i know is adb reboot and adb reboot recovery
Click to expand...
Click to collapse
adb start-server
adb kill-server
adb push file destination
adb pull file destination(>optional)
adb shell (Open a terminal on the device in your pc terminal window)
adb reboot
adb reboot-bootloader(Only useful if your device will stay at the bootloader for fastboot stuff eg: nexus and htc devices)
adb reboot recovery
examples for adb pull would be
adb pull /sdcard/dcim/
adb push doggy.jpg /sdcard/Download/doggy.jpg
There has got to be an adb guide here somewhere on Xda.
If not then go look up some common adb commands.
Have fun with adb.
(I'm anxious to see you fix your phone.)
---------- Post added at 01:48 PM ---------- Previous post was at 01:32 PM ----------
I'm also sure that you know to use the ./ before adb with all of these commands right?
adb guide for windows
Even though its an adb guide for windows, im sure you'll be able to get just as much knowledge from it.
They also might have something on xda university for this stuff.(Which you should totally check out )
http://xda-university.com/
Lgrootnoob said:
adb start-server
adb kill-server
adb push file destination
adb pull file destination(>optional)
adb shell (Open a terminal on the device in your pc terminal window)
adb reboot
adb reboot-bootloader(Only useful if your device will stay at the bootloader for fastboot stuff eg: nexus and htc devices)
adb reboot recovery
examples for adb pull would be
adb pull /sdcard/dcim/
adb push doggy.jpg /sdcard/Download/doggy.jpg
There has got to be an adb guide here somewhere on Xda.
If not then go look up some common adb commands.
Have fun with adb.
(I'm anxious to see you fix your phone.)
---------- Post added at 01:48 PM ---------- Previous post was at 01:32 PM ----------
I'm also sure that you know to use the ./ before adb with all of these commands right?
adb guide for windows
Even though its an adb guide for windows, im sure you'll be able to get just as much knowledge from it.
They also might have something on xda university for this stuff.(Which you should totally check out )
http://xda-university.com/
Click to expand...
Click to collapse
Thank you for all your help!
I downloaded adb-fastboot-latest_win_linux.zip. Using Ubuntu 12.04, unziped ”adb” and “fastboot”. Went to terminal and change directory to where adb” and “fastboot” where placed. I had no issues with ADB commands, however, I never got a reply from the following command:
Code:
ADB$ fastboot oem get_unlock_data
< waiting for device >
Have not tried from Windows yet. I know there were some issues with MTP after the 6.0 update and my version of Linux (MTP supported on Ubuntu v13 and above). Not sure if this is the issue since ADB commands seemed to work. Any recommendations?
Update: No issue using Windows
MrTooPhone said:
I downloaded adb-fastboot-latest_win_linux.zip. Using Ubuntu 12.04, unziped ”adb” and “fastboot”. Went to terminal and change directory to where adb” and “fastboot” where placed. I had no issues with ADB commands, however, I never got a reply from the following command:
Code:
ADB$ fastboot oem get_unlock_data
< waiting for device >
Have not tried from Windows yet. I know there were some issues with MTP after the 6.0 update and my version of Linux (MTP supported on Ubuntu v13 and above). Not sure if this is the issue since ADB commands seemed to work. Any recommendations?
Update: No issue using Windows
Click to expand...
Click to collapse
Did you execute 'adb reboot bootloader' first? All fastboot command need to be executed with the device in fastboot mode, and need su (sudo) privileges.
In addition to the above, by not prepending './' to your command, you were calling a(n apparently available) system-wide installation that might have been too old to detect the device. It would also help if you would post an lspci so we could see if the device is at least in the correct mode.
acejavelin said:
Did you execute 'adb reboot bootloader' first? All fastboot command need to be executed with the device in fastboot mode, and need su (sudo) privileges.
Click to expand...
Click to collapse
I did 'adb reboot bootloader first, however, I did not do "su" for fast boot command. So "adb" command does not require "su"? I will try "su" fastboot command later and report back.
MrTooPhone said:
I did 'adb reboot bootloader first, however, I did not do "su" for fast boot command. So "adb" command does not require "su"? I will try "su" fastboot command later and report back.
Click to expand...
Click to collapse
Correct, add doesn't require su, fastboot does.
Sent from my MotoG3 using Tapatalk
acejavelin said:
Correct, add doesn't require su, fastboot does.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Tried again with Linux. SU did the trick. Thanks.