Related
why when i write in CMD adb devices it returns me this
C:\Users\Niki>adb devices
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
Click to expand...
Click to collapse
Try entering task manager and killing all instances of adb.exe
If not possible reboot pc and phone.
If still not working have a look at this: http://groups.google.com/group/android-developers/msg/dfae5da4a3c80aa8
When it works come tell me I am cool and press thanks button.
it works that way
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
[HOW TO] ADB Sideload/Push if you Wipe Internal Storage & No ROM to Flash [19 May 15]
How to Sideload in TWRP if you erase your Internal Memory and don't have a ROM to Flash or Restore
Warning!
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, 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.
*/
Requirements
Code:
#include
/*
* Unlocked Phone @ HTCDEV
* Custom Recovery
*/
Before You Start - Update Android SDK - How to set up Android SDK (ADB)
Instructions
MAKE SURE YOU BACK UP YOUR SD CARD FIRST!!!!!!!!
Make Sure HTC Drivers are installed and ADB is already working
1. Reboot into TWRP
2. in TWRP, Hit andvanced and find Sideload
3. Swipe to start Sideload
4. Open a CMD Prompt window and Change Directories to where your adb.exe is
5. type adb devices and it should show your device conntected and say sideload
6. Your ZIP file should already be in your adb folder - See Example Below
{
"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"
}
7. You are now ready to push the zip.....
8. type adb sideload nameofzip.zip <------------See Example Below
9. Wait until it says 100% and reboot back into recovery to flash the ROM
10. If hitting power does not make the screen come one, type adb reboot recovery
11. if adb reboot recovery does not work, hold power and volume down until it reboots to fastboot then go to recovery
ADB Push from Recovery - If Sideload Fails For You
adb push rom.zip /data/media/0/
Click to expand...
Click to collapse
If You have any Troubles with ADB
Koush Universal ADB Driver - Works on Windows 8 - Thanks xeroxide
YouTube Video for ADB Help
How to install ADB Drivers for any Device
FAQ
If your Output looks similiar to this below, then you are not in sideload mode or you typed the command incorrectly
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\William>cd Downloads\ADB
C:\Users\William\Downloads\ADB>adb sideload Slim-nozomi-4.2.2.build.6-OFFICIAL
Android Debug Bridge version 1.0.26
-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
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] [-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 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 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.
C:\Users\William\Downloads\ADB>-d
'-d' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\William\Downloads\ADB>-d\
'-d\' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\William\Downloads\ADB>-d: \
'-d:' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\William\Downloads\ADB>:-d
C:\Users\William\Downloads\ADB>-d\
'-d\' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\William\Downloads\ADB>-d
'-d' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\William\Downloads\ADB
DO THE FOLLOWING - (Refer to Post 1 Before you start for Picture Example)
1. Run sdk manager and update all the 4.1.2 - 4.4.2 binaries, you will see installed if you have done so
2. Reboot into TWRP
3. Go to advanced
4. Touch ADB Sideload
5. Swipe To start sideload
6. in command promt example: cd c:\android\sdk\platform-tools (that is where my adb files are at)
7. Once you have navigated to where your adb is at in command promt type adb devices
8. When you type adb devices, it should show your HTCxxjxihdjiw (whatever yours is) and Sideload which indicates you are set up properly
9. Once you see the above type adb sideload nameofzip.zip
bdorr1105 said:
Reserved if needed
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
get em greezemeister!!!!
I have never had to do it... but if I do I know there are easy to understand directions.. Thanks
slimc84 said:
get em greezemeister!!!!
Click to expand...
Click to collapse
Lol thanks greezemeister
Sent from my HTC One using xda premium
Wow amazing that you posted this on the very day like an idiot I bricked my new HTC one. I followed your directions with no luck however. What I did to get in this mess was to wipe the phone before realizing I forgot to put the viper rom in internal storage. (I have an OTG cable on the way but wont be here for a few days.) So I open an adb command window and when I type in adb devices it does show my device with the following text:
"List of devices attached
FA345S900209 host"
I have the rom zip file in the correct directory on my desktop but when I type adb sideload it just brings up the entire adb help menu.FWIW on the phone it shows "starting ADB sideload feature" but it never does anything after that. ANy thoughts would be greatly appreciated!
Thanks!
I have not ran into this for a while, but I thought you could just adb push the Rom to the phone and flash as normal.
Sent from Taptalk on HTC One on some awesome custom Rom!
avwheeler said:
I have not ran into this for a while, but I thought you could just adb push the Rom to the phone and flash as normal.
Sent from Taptalk on HTC One on some awesome custom Rom!
Click to expand...
Click to collapse
Is there any trick to doing that ? I tried adb push and the rom name but is there something I'm missing ?
pitchristian said:
Wow amazing that you posted this on the very day like an idiot I bricked my new HTC one. I followed your directions with no luck however. What I did to get in this mess was to wipe the phone before realizing I forgot to put the viper rom in internal storage. (I have an OTG cable on the way but wont be here for a few days.) So I open an adb command window and when I type in adb devices it does show my device with the following text:
"List of devices attached
FA345S900209 host"
I have the rom zip file in the correct directory on my desktop but when I type adb sideload it just brings up the entire adb help menu.FWIW on the phone it shows "starting ADB sideload feature" but it never does anything after that. ANy thoughts would be greatly appreciated!
Thanks!
Click to expand...
Click to collapse
Try using the tool kit and relocking boot loader and run the RUU
Sent from my HTCONE using xda app-developers app
pitchristian said:
Is there any trick to doing that ? I tried adb push and the rom name but is there something I'm missing ?
Click to expand...
Click to collapse
It has been a while, just remember that the paths/location need to be right. Might have to mount storage or something like that too. Lots of threads on adb. Wish you luck, that sucks.
Sent from Taptalk on HTC One on some awesome custom Rom!
thanks guys I fixed it after relocking the bootloader and running the stock RUU from toolkit as mentioned! I really appreciate it. (FWIW I could never get sideload through TWRP to work)
Added you guide HERE Q14 Thanks OP
pitchristian said:
thanks guys I fixed it after relocking the bootloader and running the stock RUU from toolkit as mentioned! I really appreciate it. (FWIW I could never get sideload through TWRP to work)
Click to expand...
Click to collapse
Glad you got it back up and running. You really should read up on adb. And how to get your paths correct. The toolkits are great but its always good to know ADB just in case you.
Sent from my HTCONE using xda app-developers app
Sorry guys I am 6hrs behind east coast. I live in Hawaii
You can use adb push if the phone is picked up in recovery but a lot of times my phone isnt recongnised. You have to go in advanced and swipe to start adb sideload...You literally dont have to pick a path because by default side load pushes to the root of your sd card...All you have to do is have the zip in the right place on your computer and type the command as instructed and it will push the zip to your sd card
pitchristian said:
Wow amazing that you posted this on the very day like an idiot I bricked my new HTC one. I followed your directions with no luck however. What I did to get in this mess was to wipe the phone before realizing I forgot to put the viper rom in internal storage. (I have an OTG cable on the way but wont be here for a few days.) So I open an adb command window and when I type in adb devices it does show my device with the following text:
"List of devices attached
FA345S900209 host"
I have the rom zip file in the correct directory on my desktop but when I type adb sideload it just brings up the entire adb help menu.FWIW on the phone it shows "starting ADB sideload feature" but it never does anything after that. ANy thoughts would be greatly appreciated!
Thanks!
Click to expand...
Click to collapse
Hey man I think you already fixed your phone but in the future you have to be booted into TWRP already then what you do next is go to Advanced and then Sideload then you swipe to enable sideload on the phone...After you have done that the phone will say starting adb sideload...It's important you update Adnroid SDK so you have the latest binaries....Once sideload is enabled on your phone then you you type the adb devices and it shouls show your device and say sideload, if it does you are solid...
After that then you type adb sideload nameofzip.zip and it will start pushing to the root of your SD card and then you just flash like normal...
Glad locking the bootloader and using the toolkit worked for you bro
bigdaddy619 said:
Added you guide HERE Q14 Thanks OP
Click to expand...
Click to collapse
Thanks man appreciate it. Thanks for the heads up
avwheeler said:
I have not ran into this for a while, but I thought you could just adb push the Rom to the phone and flash as normal.
Sent from Taptalk on HTC One on some awesome custom Rom!
Click to expand...
Click to collapse
You can use adb push but if your phone is in recovery adb didn't recognize my phone, it did when I was booted in my ROM but this is worst case or upgrading and you wipe the internal memory before you flash and your sd is blank and you can't flash adb sideload is different than regular adb commands...
When I wiped my SD on accident a few days ago I managed to adb push while in recovery.
I think it has to do with which drivers you have installed. I just use the ones that come with the Android SDK ( /sdk/extras/google/usb_driver/android_winusb.inf ), and I have the driver set to "Android Composite ADB Interface".
Always good to have options though. :good:
Harfainx said:
When I wiped my SD on accident a few days ago I managed to adb push while in recovery.
I think it has to do with which drivers you have installed. I just use the ones that come with the Android SDK ( /sdk/extras/google/usb_driver/android_winusb.inf ), and I have the driver set to "Android Composite ADB Interface".
Always good to have options though. :good:
Click to expand...
Click to collapse
Yeah it is good to have options, there is no need for paths pretty much sideload puahes to the root of your sd card automatically so it's easier in my opinion. Anyway thanks for the info
Sent from my HTC One using xda premium
bdorr1105 said:
Yeah it is good to have options, there is no need for paths pretty much sideload puahes to the root of your sd card automatically so it's easier in my opinion. Anyway thanks for the info
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
So what happens when all the abve has occurred and now in TWRP it states, Sideload failed?
I have tried:
##2846579## which does nothing
Removed the line of code in /system/etc/init that says:
rm /dev/log/main
I have usb debugging enabled, I have tried resetting ADB in devices, and I have the following error still that states
"Unable to open log device '/dev/log/main'": No such file or directory"
I would appreciate ANY help to get this resolved...
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