Apologies if this has been repeated but I have spent the last 30mins looking through this site and can not find a similar problem.
I am currently going through the process of overclocking my Nexus one.
I am running Cyanogen and have flashed the image file needed.
I am now trying to push the bcm4329.ko file to the system modules folder.
I have updated my USB drivers sand the phone appears to have liked that.
However when I try to perform an ADB remount command it takes a while thinking about it, tells me that "daemon is not running" and is "starting it now"
ADB server didnt ACK
* failed to start daemon *
error: can not connect to daemon.
Any suggestions as to how I can resolve this issue please?
adb kill-server
adb start-server
I have a rooted and unlocked bootloader on my N1 running CM7.2, I'm trying to install black rose, but every time I time I try and do so, I keep getting the error "adb server is out of date... killing". Also another message that it can't connect to the device. I've read that some people are suggesting I get the adb fix for users with HTC Sync, but I have NEVER installed HTC Sync. I'm not sure how to get around this. I've update my SDK so I'm not sure what to do.
pm2gonzales said:
I have a rooted and unlocked bootloader on my N1 running CM7.2, I'm trying to install black rose, but every time I time I try and do so, I keep getting the error "adb server is out of date... killing". Also another message that it can't connect to the device. I've read that some people are suggesting I get the adb fix for users with HTC Sync, but I have NEVER installed HTC Sync. I'm not sure how to get around this. I've update my SDK so I'm not sure what to do.
Click to expand...
Click to collapse
Apparently that error is most commonly seen when there is another version of ADB on that machine. Are you running HTC Sync?
EDIT -- Sorry, i re-read your OP and you've already stated you aren't running HTC Sync. In any case that error still suggests another version of ADB is around somewhere.
pm2gonzales said:
I have a rooted and unlocked bootloader on my N1 running CM7.2, I'm trying to install black rose, but every time I time I try and do so, I keep getting the error "adb server is out of date... killing". Also another message that it can't connect to the device. I've read that some people are suggesting I get the adb fix for users with HTC Sync, but I have NEVER installed HTC Sync. I'm not sure how to get around this. I've update my SDK so I'm not sure what to do.
Click to expand...
Click to collapse
Hmm... Even though you don't have HTC Sync, there must be another instance of adb running around in your system.
Are you using tools for other android phones on your system? If they are installed, then they could be running a version of adb which could cause your problem. So if that's the case, find those processes and kill those.
Check your SYSTEM PATH (Environment variable) to see if there is another path to your adb.exe ( Just use one )
I probably should have mentioned, but I am running Windows 7 64-bit. Also, I've tried uninstalling and reinstalling the android SDK and I got the same result. To visualize, there is a screenshot of the error:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have USB Debugging enabled, the phone says FASTBOOT USB. So the phone recognizes the connection at least.
Are you able to run adb commands? Again, are there SDKs for other android phones in your PC?
If you want, try putting adb and fast boot in a fresh directory, add that you path as an env variable, remove the other adb env variable paths(if any), and try again.
Reboot system too just to be sure
Sent from my Nexus One using xda app-developers app
pm2gonzales said:
I probably should have mentioned, but I am running Windows 7 64-bit. Also, I've tried uninstalling and reinstalling the android SDK and I got the same result. To visualize, there is a screenshot of the error:
I have USB Debugging enabled, the phone says FASTBOOT USB. So the phone recognizes the connection at least.
Click to expand...
Click to collapse
You're doing it wrong. You need to be booted into android, not fastboot.
race55 said:
You're doing it wrong. You need to be booted into android, not fastboot.
Click to expand...
Click to collapse
I'm still getting issues. I'm booted in to the system, USB debugging is enabled. I can use adb commands, like if I do adb devices, it shows my device connected. But throughout the installation, it keeps showing errors:
Code:
-------------------------------
| Nexus One BlackRose 120421 |
| Made by Lecahel(XDA-dla5244) |
| Dok-Do belongs to KOREA |
-------------------------------
Do at your own risk
Don't flash any unsigned radio image
Don't flash eclair rom(eg.EPF30), if you are SLCD Nexus One user
If you are using sense rom, please install HTC Sync and turn off that now
Your N1(USB Debugging ON) should be connected to PC
If your device has already installed latest BlackRose, it will enter into Blac
ose menu
Otherwise, BlackRose will be installed or updated automatically
* Waiting for device...
adb server is out of date. killing...
* daemon started successfully *
* Getting device information...
adb server is out of date. killing...
* daemon started successfully *
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
adb server is out of date. killing...
* daemon started successfully *
adb server is out of date. killing...
* daemon started successfully *
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
adb server is out of date. killing...
* daemon started successfully *
remote object '/data/local/tmp/ro.build.version.release_tmp' does not exist
adb server is out of date. killing...
* daemon started successfully *
1 KB/s (10 bytes in 0.007s)
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
adb server is out of date. killing...
* daemon started successfully *
* Installing BlackRose
adb server is out of date. killing...
* daemon started successfully *
1461 KB/s (4194304 bytes in 2.802s)
adb server is out of date. killing...
* daemon started successfully *
638 KB/s (26172 bytes in 0.040s)
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
adb server is out of date. killing...
* daemon started successfully *
adb server is out of date. killing...
* daemon started successfully *
error opening /data/local/tmp/go.lol: No such file or directory
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
adb server is out of date. killing...
* daemon started successfully *
< waiting for device >
At which point it boots in to recovery (4EXT).
pm2gonzales said:
I'm still getting issues. I'm booted in to the system, USB debugging is enabled. I can use adb commands, like if I do adb devices, it shows my device connected. But throughout the installation, it keeps showing errors:
Code:
-------------------------------
| Nexus One BlackRose 120421 |
| Made by Lecahel(XDA-dla5244) |
| Dok-Do belongs to KOREA |
-------------------------------
Do at your own risk
Don't flash any unsigned radio image
Don't flash eclair rom(eg.EPF30), if you are SLCD Nexus One user
If you are using sense rom, please install HTC Sync and turn off that now
Your N1(USB Debugging ON) should be connected to PC
If your device has already installed latest BlackRose, it will enter into Blac
ose menu
Otherwise, BlackRose will be installed or updated automatically
* Waiting for device...
adb server is out of date. killing...
* daemon started successfully *
* Getting device information...
adb server is out of date. killing...
* daemon started successfully *
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
adb server is out of date. killing...
* daemon started successfully *
adb server is out of date. killing...
* daemon started successfully *
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
adb server is out of date. killing...
* daemon started successfully *
remote object '/data/local/tmp/ro.build.version.release_tmp' does not exist
adb server is out of date. killing...
* daemon started successfully *
1 KB/s (10 bytes in 0.007s)
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
adb server is out of date. killing...
* daemon started successfully *
* Installing BlackRose
adb server is out of date. killing...
* daemon started successfully *
1461 KB/s (4194304 bytes in 2.802s)
adb server is out of date. killing...
* daemon started successfully *
638 KB/s (26172 bytes in 0.040s)
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
adb server is out of date. killing...
* daemon started successfully *
adb server is out of date. killing...
* daemon started successfully *
error opening /data/local/tmp/go.lol: No such file or directory
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
adb server is out of date. killing...
* daemon started successfully *
< waiting for device >
At which point it boots in to recovery (4EXT).
Click to expand...
Click to collapse
open terminal, in which you run a random adb command. keep that window open and now try running the installer
Verstuurd van mijn GT-I9000 met Tapatalk
race55 said:
open terminal, in which you run a random adb command. keep that window open and now try running the installer
Verstuurd van mijn GT-I9000 met Tapatalk
Click to expand...
Click to collapse
Same result :/. I don't understand what the problem could be, I can push apps and run adb commands just fine.
pm2gonzales said:
Same result :/. I don't understand what the problem could be, I can push apps and run adb commands just fine.
Click to expand...
Click to collapse
Blackrose installer is terrible. Try using the manual method, worked for me back in the day
Verstuurd van mijn GT-I9000 met Tapatalk
race55 said:
Blackrose installer is terrible. Try using the manual method, worked for me back in the day
Verstuurd van mijn GT-I9000 met Tapatalk
Click to expand...
Click to collapse
With the manual method, I get this:
Code:
C:\blackrosemanual>fastboot flash hboot hboot_blackrose.nb0
sending 'hboot' (512 KB)...
OKAY [ 0.087s]
writing 'hboot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.229s
C:\blackrosemanual>
To confirm, I am in Fastboot mode as per README instructions.
pm2gonzales said:
With the manual method, I get this:
Code:
C:\blackrosemanual>fastboot flash hboot hboot_blackrose.nb0
sending 'hboot' (512 KB)...
OKAY [ 0.087s]
writing 'hboot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.229s
C:\blackrosemanual>
To confirm, I am in Fastboot mode as per README instructions.
Click to expand...
Click to collapse
Did you fastboot boot the .lol file?
Verstuurd van mijn GT-I9000 met Tapatalk
race55 said:
Did you fastboot boot the .lol file?
Verstuurd van mijn GT-I9000 met Tapatalk
Click to expand...
Click to collapse
Yes, received the EXACT SAME error message.
Okay, I finally got it to work. I just kept trying and trying repeatedly until it actually worked. I think it had something to do with my android sdk or maybe the adb drivers because adb commands only work like 50% of the time. The 50% that it doesn't work, I keep getting those "adb server out of date" errors. But I finally got it at least.
try running Blackrose with other ROM, or you should install HTC Sync for your PC, i can't run Blackrose with CM7.2 too
Hello guys today I am going to show you how to use a program called quick adb pusher, it is a great starting point for new android users who want to copy modified system files, without flashing update Zip’s all the time, it will also let member do things manually instead of relying on update ZIP's all the time. Besides of explaining how to use a simple program such a quick ADB Pusher, i will also explain in depth the commands of ADB through the actual command line interface, so here we go:
Code:
#include
*
* Your warranty is now void.
*By you using my Mods, Roms etc...
* I am not responsible for bricked devices, or dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
First of all we will start with The command line ADB, the quick adb pusher tutorial is further down the post.
Before we start explaining some of the code what is used in ADB, it is important you know what it is, it is called the Android-Debug-Bridge.
In order to even get ADB to wokr you need to follow these procedures:
Settings -> Developers options -> USB-de bugging
Then check that box, it will make you feel like a boss.
Now once you have done that your android device, is now setup for both development and ADB. Next you are going to plug your device into your computer, via a usb cable.
Once you have done that you need to go to the directory of your ADB interface, this is where you have the android SDK installed too, on a linux or mac based system this could be:
Code:
cd /home/yourusername/android-sdk-mac/tools
Once you have the ADB interface loaded into your terminal, if you type help it will show something similar to this:
Code:
Android Debug Bridge version 1.0.25
-d - directs command to the only connected USB device
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 running.
-s <serial number> - directs command to the USB device or emulator with
the given serial number. Overrides ANDROID_SERIAL
envivornment 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
disconnect <host>:<port> - disconnect from a TCP/IP device
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
(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] <file> - push this package file to the device and install it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data)
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 help - show this help message
adb version - show version num
DATAOPTS:
(no option) - don't touch the data partition
-w - wipe the data partition
-d - flash the data partition
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 specified device
adb remount - remounts the /system partition on the device read-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the bootloader or recovery program
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 the 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 updated.
- If it is "system" or "data", only the corresponding partition
is updated.
Now that you have ADB running here are some simple commands on how to use it:
How identify that your device is being recognised by ADB:
Code:
adb devices
Once this has been typed it should show something like this:
Code:
C:\Users\Daniel\Android development\ADB, Fastboot\adt-bundle-windows-x86_64\adt-
bundle-windows-x86_64\sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
HT26GW507639 device
C:\Users\Daniel\Android development\ADB, Fastboot\adt-bundle-windows-x86_64\adt-
bundle-windows-x86_64\sdk\platform-tools>
If there is a line what says "HT26GW507639" with "device" at the end your devices is successfully recognised by ADB!
How to pull data from your device:
Code:
adb -s [yourdeviceADBNUMBERHERE] pull /system /the directory you want it saved too
This command will pull all the files from your devices system directory, to the directory you told it to be saved too.
I did the pull command on a PC and I was able to get all the data from following directories on my Desire C:
/data
/system
How to push data to your device:
Code:
adb -s [yourdeviceserialnumberhere] push /system/app/whatever.apk
This command will push the files you wish to your phone, though this command.
The most basic ADB commands
ADB push, as explained before this command is used to send files to your device
Code:
adb push
ADB pull, as explained before it pulls files from your phone, and makes a copy of them.
Code:
adb pull
ADB Install and example of this code would be "adb install c:\users\app.apk"
Code:
adb install c:\users\app.apk
ADB Shell, this command begins a shell connection to the device on the other end.
Code:
adb shell
ADB reboot, it does what it says
Code:
adb reboot
ADB reboot recovery, this also does what it says
Code:
adb reboot recovery
ADB reboot bootloader, this also does what is says, like the ones above.
Code:
adb reboot bootloader
ADB remount, this remounts the devices file system for editing etc...
Code:
adb remount
ADB Shell commands:
cd, this command changes directories in your devices filesystem.
Code:
cd /system/app
is, this command listes all of the file present in the directory you are at.
Code:
is /system/app
rm, this command removes file from your device.
rm /system/app/whatever.apkcp, this command copies files, and is very similar to the cat command below.
Code:
cp /system/app/whatever.apk /sdcard/whatever.apk
cat, this command is also used to copy files to your device.
Code:
cat /system/app/whatever.apk > /sdcard/whatever.apk
exit, this command exits the ADB shell.
Code:
exit
If any of you are having any problems, read the FAQ first before posting a question in this thread, happy pushing!
If you think any other commands should me added to this section, PM me about it.
As explained above, the quick ADB pusher is an interface over the code based ADB. I will be a much easier approach for new user of android to get to grips to, that is why I am including it.
Hello guys today I am going to show you how to use a program called quick adb pusher, it is a great starting point for new android users who want to copy modified system files, without flashing update Zip’s all the time, so here we go:
First of all you want to download the quick adb pusher program, this is in both this thread and the revolution Rom thread on XDA, the link for the program is listed below:
Quick ADB Pusher
Now you want to make sure your phone is plugged into your computer, but do not put it into USB storage mode. Make sure your USB de-bugging option is enabled it is located at:
Settings --> Developer options --> USB De-bugging
Now you will start the quick ADB pusher program, once it has started it should detect your phone. If it does not then post a comment in the thread below and we will resolve the issue.
Watch the video below to clarify a few things, such as how to copy system apps etc...
Again I hope this tutorial helps some people out, remember to read the FAQ first before posting,, to prevent the same questions being asked time and time again.
FAQ
Brilliant guide thanks russell . Time to learn how to do it properly .though in fairness I do use it a bit
ps used all my thanks up again this morning !
haha already, you like smashing that thanks button, right in the face lol.
Re: [GUIDE] How to Push files using ADB
Great guide Russell.
To moderators: please move the this thread to sticky section.
Thanks, TheRedHunter.
If you guys think this thread should be stickied, them click the report button at the top of the first post, and ask it to be moved.
On another note the first post is updated with new ADB shell commands.
Thanks, I really love you threads, I will read later, i has got school now
Hi Guys,
Been having a bit of trouble connecting phone via ADB. I can get the connection to work, but it takes a bit of TLC and sometimes a sledgehammer.
Thought we could compile a list of ADB troubleshooting techniques?
If you have any further suggestions, please share.
c:\Fastboot>adb reboot recovery
* daemon not running. starting it now *
* daemon started successfully *
error: device offline
Click to expand...
Click to collapse
Resolution: Reboot device
c:\Fastboot>adb reboot recovery
adb server is out of date. killing...
* daemon started successfully *
error: device not found
Click to expand...
Click to collapse
Resolution: Reboot device
c:\Fastboot>adb reboot recovery
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
Click to expand...
Click to collapse
Resolution: Kill all adb.exe processes from task manager and rerun the command. May need to do this a few times.
Edit: I should mention that I'm using adb.exe on Windows 8.1