Develop Bugs

"adb server didn't ack * failed to start daemon" Help!

Originally Posted by nicbennett
*Daemon not running, starting it now on port 5037*(this does successfully start the adb.exe process)
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon*
Click to expand...
Click to collapse
Originally Posted by snovvman
W7/64.
ADB worked for me for months. I used it regularly. The last thing I did was *trying* to use Wireless ADB Widget and issueing ADB TCPIP command. I have made no changes to the system.
The error occurs when no device device connected. Same error when device IS connected.
-Downloaded ADB/SDK again to a different directory, same error
-Updated USB driver and SDK components, same error
-Disabled all firewall/anti-malware/anti-virus, same error
-Rebooted multiple times, same error off boot
-Port 5037 is not bound by any app or process
-ADB, upon failed load, is not listed in Taskmgr, nothing to kill
-Deleted temp files
-Issued at prompt: ADB Disconnect, ADB USB, ADB devices: All return same error as above
-Issued at prompt: ADB kill-server, only prompt returns
Read lots of posts on the web, nothing helps.
I am really interested in a solution and would like to understand what is causing the problem. If in fact it is a configuration issue, where is the ADB config file?
Thanks.
Edit: I am running the command prompt as an administrator.
Click to expand...
Click to collapse
I originally added my post to this thread in the Nook forum. I don't think there is enough expertise in that forum to help with this problem.
The bottom line is that ADB no longer works and I can't figure out why (see quoted text above). I would imagine that someone here would have an answer for this. Please help!
Thanks.

Only thing I would try it open Task Manager and go to processes and close anything that is adb or adb.exe.

DGreen1 said:
Only thing I would try it open Task Manager and go to processes and close anything that is adb or adb.exe.
Click to expand...
Click to collapse
In this case, ADB never starts. It does not work even after a fresh reboot. It is not found in Taskmgr nor Process Explorer.

snovvman said:
In this case, ADB never starts. It does not work even after a fresh reboot. It is not found in Taskmgr nor Process Explorer.
Click to expand...
Click to collapse
Is what he meant was to kill any process that is using adb. This is not only a process that is Android related etc. My buddy had your exact same problem because he had his external hd connected to his computer before trying to run adb. Restarting and killing processes that were using adb on his computer did the trick. Hope this helps!

My problem was Windows
snovvman said:
The error occurs when no device device connected. Same error when device IS connected.
. . .
I am really interested in a solution and would like to understand what is causing the problem.
Click to expand...
Click to collapse
In my case, the problem was Windows Vista. From day one, Windows refused to successfully install the USB drivers for the EVO (with the very helpful diagnostic message: "Windows encountered an error installing..."). I have never been able to use adb, and this meant that all the rooting (and update/upgrade) guides that required adb had to be adapted to getting the file(s) onto the SD card, and then using Terminal Emulator (or similar app) to get the job done.
I've just completed a disk-wipe-and-reinstall of Windows on my laptop, and hope to find the time next week to install all the SDK goodies and make sure that the USB subsystem recognizes my EVO. I'm fed up with not being able to use adb, and that, along with Windows Update failing to install over a dozen security patches, finally pushed me over the edge into a re-install. Auuugh! The pain!

Yellowcard8992 said:
Is what he meant was to kill any process that is using adb. This is not only a process that is Android related etc. My buddy had your exact same problem because he had his external hd connected to his computer before trying to run adb. Restarting and killing processes that were using adb on his computer did the trick. Hope this helps!
Click to expand...
Click to collapse
Interesting, but I haven't been able to find any other service that is bound to adb and I have no other USB devices connected. Thanks for chiming in though.
tgi007 said:
In my case, the problem was Windows Vista. From day one, Windows refused to successfully install the USB drivers for the EVO (with the very helpful diagnostic message: "Windows encountered an error installing..."). I have never been able to use adb, and this meant that all the rooting (and update/upgrade) guides that required adb had to be adapted to getting the file(s) onto the SD card, and then using Terminal Emulator (or similar app) to get the job done.
I've just completed a disk-wipe-and-reinstall of Windows on my laptop, and hope to find the time next week to install all the SDK goodies and make sure that the USB subsystem recognizes my EVO. I'm fed up with not being able to use adb, and that, along with Windows Update failing to install over a dozen security patches, finally pushed me over the edge into a re-install. Auuugh! The pain!
Click to expand...
Click to collapse
For me, I have been able to get two Vista and one Windows 7 computer to work with ADB and HTC drivers the first time. I also have an Epic, and the Samsung drivers installed fine as well (even though they are known to have issues).
Unfortunately, ADB just "broke" one day.
I keep thinking that the Evo community has enough brains and knowledge to sort this out quickly...

Have you updated the sdk recently?
The updated sdk moves the adb files from the tools folder to another folder called platform-tools.
I have adb working properly on both my vista machine and my ubuntu machine hosted on my vista machine.
If you have installed htc sync before uninstall it and the htc driver installer.
Redownload htc sync and the adb files (adb.exe and adbwinapi.dll is all you need). Since adb was working correctly before I'm assuming your java is installed correctly as well.
Reinstall htc sync. When that finishes I suggest a reboot. When you've rebooted uninstall htc sync but leave the htc driver installer. Reboot again.
When you've rebooted again enable usb debugging on your device and connect it to your pc choosing charge only.
This should hopefully reinstall the usb drivers correctly. On vista it installs as adb device or something along those lines.
If the drivers install correctly you should be able to run adb from the directory your two files are in (desktop for example).
If you want, send me a pm with your gtalk username and I can help you troubleshoot it.

lovethyEVO said:
Have you updated the sdk recently?
The updated sdk moves the adb files from the tools folder to another folder called platform-tools.
I have adb working properly on both my vista machine and my ubuntu machine hosted on my vista machine.
If you have installed htc sync before uninstall it and the htc driver installer.
Redownload htc sync and the adb files (adb.exe and adbwinapi.dll is all you need). Since adb was working correctly before I'm assuming your java is installed correctly as well.
Reinstall htc sync. When that finishes I suggest a reboot. When you've rebooted uninstall htc sync but leave the htc driver installer. Reboot again.
When you've rebooted again enable usb debugging on your device and connect it to your pc choosing charge only.
This should hopefully reinstall the usb drivers correctly. On vista it installs as adb device or something along those lines.
If the drivers install correctly you should be able to run adb from the directory your two files are in (desktop for example).
If you want, send me a pm with your gtalk username and I can help you troubleshoot it.
Click to expand...
Click to collapse
Thanks for replying. I had already updated ADB (in platform-tools) before started having this problem. I had also uninstalled HTC sync (reboot, launch ADB w/o HTC sync, same problem) and reinstalled HTC sync, same problem. I updated Java JVM, no change. I then re-downloaded the SDK to a different directory, no dice.
I usually open a command prompt "as Administrator" and run ADB from the directory. Even with a device disconnected, I get the same error. I test this way because if I issued "ADB devices" and it returns nothing, I know it's working. It appears that ADB doesn't even start to the point to poll for devices.
I have, just for laughs, connected my device (USB debugging/charge only), but no joy.
I won't have much time to poke around more until the weekend. If I don't come up with anything, I will take you up on the gtalk. Thanks again.

Windows Vista just makes it all that much harder to fix things...
lovethyEVO said:
If you have installed htc sync before uninstall it and the htc driver installer.
. . .
Reinstall htc sync. When that finishes I suggest a reboot. When you've rebooted uninstall htc sync but leave the htc driver installer. Reboot again.
. . .
This should hopefully reinstall the usb drivers correctly. On vista it installs as adb device or something along those lines.
Click to expand...
Click to collapse
In my case, I tried all these things and many more (lived with this problem since first getting my EVO on release date in June). No dice, as Windows Vista, once it installs a device driver, doesn't give the user the option to uninstall it (by Microsoft's expressly-stated intent -- a design decision I vehemently disagree with). At least the user could repair such problems in prior versions of Windows by simply uninstalling a device, choosing "yes" to the "remove driver files from the disk" question, and (after the obligatory and ubiquitous Windows reboot) re-connect the USB device. That would start fresh with that device's driver.
I never invested the time to learn how the USB subsystem registers devices and their drivers (in Windows Vista) in order to determine how to manually remove a driver from the Windows Registry adequately that it would treat the device as "new hardware detected" upon the next connection.
Once Windows Vista has scrambled some internals in the database/registry controlling the USB subsystem's driver knowledge, you're toast. Nothing I could find in Microsoft's Knowledge Base nor MSDN shed any light on how to tackle the removal-and-recreation-from-scratch of the USB system configuration.
Microsoft's stock answer was invariably "re-install Windows". Yeah, thanks for that. Windows, even more than 26 years later, is still not a real operating system, and still has bugs dating back to Windows 3.1.
Sigh.

Check Windows Firewall service.
In my case I just turned off the Windows Firewall and it started working.
regards
Gaurav

i had this problem.
disable any program like Proxifier and firewall

I accidently figured it out
so i was trying to find my cid number because i was flashing ICS firmware and stuff, and the adb deal in the prompt kept giving me the exact same error, and thus would'nt work. after trying everything (such as: installing drivers, killing the process, restarting my comp, reinstalling adb, etc.) for about an hour and a half, i just stumbled upon a page that was linked to in the ICS flash guide, that had a different adb folder download. this download has an entirely different effect on the command prompt and worked so i could get my cid number and rewrite superCid. here it is:
http://forum.xda-developers.com/attachment.php?attachmentid=872134&d=1327512033
Download it, click "start here", then treat it like normal

ADB server din't ACK
Please help....I was trying installing Hellkat 4.4.2 on my kindle fire by following http://forum.xda-developers.com/showthread.php?t=2570078
Downloaded all the files and flashed through TWRP and was successful. But after flashing, when it is rebooting it is getting stuck on the hellkat logo and not booting.
If I try to install TWRP again, i am getting error ADB server din't ACK *failed to start daemon*. and ADB status online and boot status unknown.
Please help......

orangeipod1gb said:
ADB server din't ACK
Please help....I was trying installing Hellkat 4.4.2 on my kindle fire by following http://forum.xda-developers.com/showthread.php?t=2570078
Downloaded all the files and flashed through TWRP and was successful. But after flashing, when it is rebooting it is getting stuck on the hellkat logo and not booting.
If I try to install TWRP again, i am getting error ADB server din't ACK *failed to start daemon*. and ADB status online and boot status unknown.
Please help......
Click to expand...
Click to collapse
your solution is
netsh advfirewall set currentprofile firewallpolicy allowinbound,allowoutbound

[TUT] ADB no device found -- Getting ADB to work

The easiest way of getting ADB to work:
Turn your phone OFF (Yes, off)
Connect it to your pc and wait for windows to finish "installing the drivers"
Try ADBing by going to ure fastboot folder (assuming it has the ADB executable inside the folder as well).
You could check if your device was recognized by firing
Code:
adb devices
If it doesn't show anything then do the following:
Grab the appropriate pc drivers from here: http://www.android-advice.com/2012/how-to-root-the-htc-one-x-and-htc-one-s/
Extract the drivers
Now go to Start menu and right click on my computer and then click manage.
Now go to device manager and there you should see your connected One X listed as being without a driver.
Right click on that entry and select 'update driver'
Now tell it that you have the driver on local disk and then browse to the folder you extracted.
Update your driver.
Disconnect and reconnect the device and try ADBing again.
Should work.

If your phone is off then Windows won't see it. Just install HTC Sync (so you get the drivers - you can uninstall HTC Sync afterwards if you're not going to use it) then plug the phone in when booted into Android. Repeat process when in FASTBOOT to get Windows to see the phone in FASTBOOT mode as well
Simples!

EddyOS said:
If your phone is off then Windows won't see it. Just install HTC Sync (so you get the drivers - you can uninstall HTC Sync afterwards if you're not going to use it) then plug the phone in when booted into Android. Repeat process when in FASTBOOT to get Windows to see the phone in FASTBOOT mode as well
Simples!
Click to expand...
Click to collapse
That is the thing -- IT DOES SEE IT! Try it yourself.
I didn't think it would but Jotha told me that it would. I tried it and it worked. I was surprised.

Yes device is seen through adb when off.
This is because as soon as you plug the USB cable, offmode comes up with charging and ADB support
Offmode is embeded in the recovery partition
PS: This needs latest clockworkmod recovery to work...

Latest ADB?
Hi!
When i was restoring my Sensation to S-ON i noticed that ADB was complaining about version out of date something....
Where can i get the latest version of ADB for using with my One X when i've decided if i should wait or use hTC bootunlocker...

Is there a way for Linux?

D0GuKaN said:
Is there a way for Linux?
Click to expand...
Click to collapse
Android SDK straight from Google should take care of that.

Also, use HTC USB cables, sometimes using non-standard USB cables can make searching for devices impossible.

DoeBoi said:
Also, use HTC USB cables, sometimes using non-standard USB cables can make searching for devices impossible.
Click to expand...
Click to collapse
No. As long as the cable is properly USB 2.0 compliant, it WILL work, otherwise HTC CANNOT certify against USB 2.0. Tried with proper Nokia, Sony Ericsson, Samsung and Google cables.

that doesn't work for me.
I tried everything, adb only recognizes my phone when its ON.

tashunke said:
that doesn't work for me.
I tried everything, adb only recognizes my phone when its ON.
Click to expand...
Click to collapse
See here a few posts back:
You have to have the latest clockworkmod recovery.

Can you help/guide me on how to install it ?
Sorry for being a dummy.

Is there any way with an adb command that we can tell what bootmode the phone is in?
I.E: hotboot or fastboot mode?
Using adb get-state they both return "unknown"?
Cheers...

RaVe-N said:
Is there any way with an adb command that we can tell what bootmode the phone is in?
I.E: hotboot or fastboot mode?
Using adb get-state they both return "unknown"?
Cheers...
Click to expand...
Click to collapse
Huh? It's OFF. My guess would be that it's not in any BOOT mode.

rilorolo said:
Huh? It's OFF. My guess would be that it's not in any BOOT mode.
Click to expand...
Click to collapse
Never mind... I found the androidlib.DLL (I think that's wrong, but its a .net DLL available here on xda) and that manages to return fast boot so I can tell programatically what state it's in...

Thanks
Thats Work

.
Please - anyone have any advice as to what could be stopping me from using adb ( from my phone to my PC ) ?
I been working on this for a couple days now, and gotten nowhere. Any thoughts at all ???
Thanks
============================
.
I have been trying to get adb working on my Win10 machine for a long time and just can not figure out what is wrong.
I have adb installed in c:\adb and my USB drivers are working. I can browse the phone from the PC.
But no matter what I try when I try to adb, I get this:
.
C:\adb>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
** daemon still not running
error: cannot connect to daemon: No error
error: cannot connect to daemon: No error
C:\adb>
Click to expand...
Click to collapse
(Yes I do have USB debugging ON and OEM ON)
It is weird because it says daemon is nOT running then it tries to start
it and says daemon started Successfully ... then it says daemon still
nOT running. That makes no sense to me ?
Please any thoughts on this ???
Thanks
.
.

Thibor69 said:
.
Please - anyone have any advice as to what could be stopping me from using adb ( from my phone to my PC ) ?
I been working on this for a couple days now, and gotten nowhere. Any thoughts at all ???
Thanks
============================
.
I have been trying to get adb working on my Win10 machine for a long time and just can not figure out what is wrong.
I have adb installed in c:\adb and my USB drivers are working. I can browse the phone from the PC.
But no matter what I try when I try to adb, I get this:
.
(Yes I do have USB debugging ON and OEM ON)
It is weird because it says daemon is nOT running then it tries to start
it and says daemon started Successfully ... then it says daemon still
nOT running. That makes no sense to me ?
Please any thoughts on this ???
Thanks
.
.
Click to expand...
Click to collapse
I can understand the difficulty. This problem is pretty common because there are no official drivers for Win10. These drivers work best on XP. I also could not get the adb to work on my Win10 so I installed Ubuntu and rooting/installing ROM's from ubuntu is a breeze.. srry for not hvng a solution for this.

trouble rooting

I'm having trouble. I'm using this tutorial
http://forum.xda-developers.com/showpost.php?p=23229558&postcount=1
(if there is a better one I'm all ears), and the first command line step, where you plug in the phone and open up the command window within the designated file path and type "adb reboot bootloader", this is what I get:
* daemon not running. starting it now on port 5037 *
*daemon started successfully *
error: device offline
Any suggestions on what i'm doing wrong? Is it a driver issue?

A few things to try in no particular order: Try a different USB port. Try a different USB cable. Try typing the command adb start-server
I am not sure if the adb AIO thing installs the newer versions of adb. If it uses outdated versions, this could potentially be a problem as well. The SDK will install the newer versions.

cupfulloflol said:
A few things to try in no particular order: Try a different USB port. Try a different USB cable. Try typing the command adb start-server
I am not sure if the adb AIO thing installs the newer versions of adb. If it uses outdated versions, this could potentially be a problem as well. The SDK will install the newer versions.
Click to expand...
Click to collapse
/Yeah I didn't use the AIO app, I used the first method of downloading it from here http://developer.android.com/sdk/index.html
I've tried different ports and the start server command with no luck either......

If you are on windows it sounds like a driver issue.
Sent from my Galaxy Nexus

Indeed, this is most likely the issue. While the Android SDK package should have installed the latest drivers try this:
Run the SDK manager and make sure you're completely up to date.
You also need Android debugging enabled to be able to use adb and fastboot if you're doing it whilst logged on to the OS.
If you still have issues, I might be able to guide you through manually installing adb and fastboot drivers
Sent from my Galaxy Nexus using Tapatalk 2

iLeopard said:
Indeed, this is most likely the issue. While the Android SDK package should have installed the latest drivers try this:
Run the SDK manager and make sure you're completely up to date.
You also need Android debugging enabled to be able to use adb and fastboot if you're doing it whilst logged on to the OS.
If you still have issues, I might be able to guide you through manually installing adb and fastboot drivers
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
That's what I'm thinking, gotta be a driver issue. I'm using windows 7, and I uninstalled all drivers and got the drivers straight from the samsung website but who knows. I'll be at work tomorrow and will be working on it again there. Is it ok if I PM you tomorrow and we can go from there? I really appreciate your help!!!!

vballrkc said:
That's what I'm thinking, gotta be a driver issue. I'm using windows 7, and I uninstalled all drivers and got the drivers straight from the samsung website but who knows. I'll be at work tomorrow and will be working on it again there. Is it ok if I PM you tomorrow and we can go from there? I really appreciate your help!!!!
Click to expand...
Click to collapse
Yes that would be fine
Sent from my Galaxy Nexus using Tapatalk 2

[Q] HTC One X Driver for Android 4.2.2

Hi Guys
Do a require a specific driver for the new 4.2.2 system. I have updated my phone to run Cyanogenmod 10.1 and had some issues originally getting adb etc to identify the phone. I have since got past this and now get an unauthorised error in adb. This is normal the issue im having is that my phone does not prompt me when I connect it to my PC. I should be getting a whitelist prompt to confirm I authorise the Pc to run ADB commands.
Has anyone else had this rather than the expected whitelist prompt im getting the little android bloke asking do I want to copy files via usb. Im just trying to work out what I need to do to get my phone to prompt me when I connect via ADB. I have already enabled ROOT access to Apps and ADB, Enabled USB debugging etc
Any help would be appreciated I have tried a number of drivers but only ever get asked to copy file via usb.

Appsdroid said:
Hi Guys
Do a require a specific driver for the new 4.2.2 system. I have updated my phone to run Cyanogenmod 10.1 and had some issues originally getting adb etc to identify the phone. I have since got past this and now get an unauthorised error in adb. This is normal the issue im having is that my phone does not prompt me when I connect it to my PC. I should be getting a whitelist prompt to confirm I authorise the Pc to run ADB commands.
Has anyone else had this rather than the expected whitelist prompt im getting the little android bloke asking do I want to copy files via usb. Im just trying to work out what I need to do to get my phone to prompt me when I connect via ADB. I have already enabled ROOT access to Apps and ADB, Enabled USB debugging etc
Any help would be appreciated I have tried a number of drivers but only ever get asked to copy file via usb.
Click to expand...
Click to collapse
Do you have HTC Sync Manager?
Also, in Device manager does your Drivers have Errors (Yellow Triangle)?

Wilks3y said:
Do you have HTC Sync Manager?
Also, in Device manager does your Drivers have Errors (Yellow Triangle)?
Click to expand...
Click to collapse
Hi Mate
I have tried with HTC Sync on and again after uninstalling it both result in the same issue usb prompt rather than ADB fingerprint prompt. No in Device Manager both of the connections for the device identify and install correctly. One with the phone and another stating something like Android Interface device not on my PC at the mo to confirm the exact name but its something like
My HTC
Android Interface Device or possibly android ADB interface

Appsdroid said:
Hi Mate
I have tried with HTC Sync on and again after uninstalling it both result in the same issue usb prompt rather than ADB fingerprint prompt. No in Device Manager both of the connections for the device identify and install correctly. One with the phone and another stating something like Android Interface device not on my PC at the mo to confirm the exact name but its something like
My HTC
Android Interface Device or possibly android ADB interface
Click to expand...
Click to collapse
Hmm Very strange.
Try:
http://forum.xda-developers.com/showthread.php?t=2217396
Or if not try hasoons Root Toolkit, im sure that installs some drivers too. Hasoons got my ADB working.
Finally, to find ADB device, are you opening command prompt in Platform-tools folder?

Wilks3y said:
Hmm Very strange.
Try:
http://forum.xda-developers.com/showthread.php?t=2217396
Or if not try hasoons Root Toolkit, im sure that installs some drivers too. Hasoons got my ADB working.
Finally, to find ADB device, are you opening command prompt in Platform-tools folder?
Click to expand...
Click to collapse
Nice one cheers mate will try these drivers when I get home later. I was originally using Hasoons toolkit which is what flashed the recovery and new rom but once I updated to 4.2.2 the toolkit stopped. It was coming up as device offline. I have managed to get it working by overwritting the old ADB and fastboot files with the new ones for 4.2.2. The ones the toolkit comes with is 4.1 so was erroring as it didnt know to carry out the fingerprint check.
Yes mate I have tried various methods I have accessed the android\android-sdk\platform-tools folder and run ADB from there this identifies the phone but states its not authorised. I tried using the toolkit with the new ADB and fastboot but get the same.
Im just missing the ADB prompt on my phone for usb debugging just cant for the life of me identify why im getting the copy files from usb prompt rather than the adb fingerprint prompt. Im sure its drivers so am hopeful the ones on the link will fix it. Fingers crossed

I was having issues with adb not finding my device. These drivers worked for me...

crshd said:
I was having issues with adb not finding my device. These drivers worked for me...
Click to expand...
Click to collapse
Nice one mate will try these ones when I get in to on way home now hopeful one of the driver links sorts out the prompt for me will update later thanks guys
Sent from my HTC One X using xda app-developers app

Cheers All removed all drivers for htc one x then downloaded the 4.2 versions from the link
http://forum.xda-developers.com/show....php?t=2217396
once reinstalled adb gave unauthorised error again but then put the prompt up on the phone. So possible the 4.2 contains the info for requesting permission as i havent changed anything other than the drivers adb and fastboot have been the same since i started. Anyway cheers all

confusion about installing driver
crshd said:
I was having issues with adb not finding my device. These drivers worked for me...
Click to expand...
Click to collapse
bro i download your driver but how to install it. my htc one x just start in fastboot mode. i want to unlock bootloader but without adb i am helpless

If you have Windows 7,8,8.1 just enable automatic update and let windows install correct drivers
Sent from my HTC One X using Tapatalk 2

[Q] HTC One M8 ADB and Fastboot Device Offline After Unlocking Bootloader

Hi,
Having a few issues trying to root my phone. I have tried to follow the guide posted by Vomer using a windows 7 pc. I have successfully unlocked my bootloader but when I try to flash a custom recovery I keep getting the error device offline. I have spent some time looking into this issue and potential fixes including updating adb, disabling and re-enabling USB debugging, switched of lock screen, updating HTC drivers, uninstalling HTC sync, trying different USB port and cables and trying a different computer all to no avail. I can confirm that I am getting the Allow USB debugging request on my device. If anyone can suggest anything to help I would be very grateful.
Thanks in advance
Abir

Abir85 said:
Hi,
Having a few issues trying to root my phone. I have tried to follow the guide posted by Vomer using a windows 7 pc. I have successfully unlocked my bootloader but when I try to flash a custom recovery I keep getting the error device offline. I have spent some time looking into this issue and potential fixes including updating adb, disabling and re-enabling USB debugging, switched of lock screen, updating HTC drivers, uninstalling HTC sync, trying different USB port and cables and trying a different computer all to no avail. I can confirm that I am getting the Allow USB debugging request on my device. If anyone can suggest anything to help I would be very grateful.
Thanks in advance
Abir
Click to expand...
Click to collapse
If i'm not mistaken device offline is a message given when running an adb command.
If fastboot command doesn't find your phone gives a <waiting for device> message
Can you please post a screenshot of what you are trying to do?

stathis95194 said:
If i'm not mistaken device offline is a message given when running an adb command.
If fastboot command doesn't find your phone gives a <waiting for device> message
Can you please post a screenshot of what you are trying to do?
Click to expand...
Click to collapse
Hi,
Ok, since my last post I have managed to root my device but the issue is now with trying to get S-Off. As per the give I typed adb reboot but get the device offline error.
Abir

Abir85 said:
Hi,
Ok, since my last post I have managed to root my device but the issue is now with trying to get S-Off. As per the give I typed adb reboot but get the device offline error.
Abir
Click to expand...
Click to collapse
Did you...
- Enable USB debugging on your phone
- Turn off all security settings from Settings -> Security.
- Disable Fast boot mode from Settings -> Power/Battery Manager.
- Plug in your device to your computer.

stathis95194 said:
Did you...
- Enable USB debugging on your phone
- Turn off all security settings from Settings -> Security.
- Disable Fast boot mode from Settings -> Power/Battery Manager.
- Plug in your device to your computer.
Click to expand...
Click to collapse
yes I can confirm I have done all of the above

Abir85 said:
yes I can confirm I have done all of the above
Click to expand...
Click to collapse
Strange...you are running the command within the OS right? Not in fastboot mode.

stathis95194 said:
Strange...you are running the command within the OS right? Not in fastboot mode.
Click to expand...
Click to collapse
Yes

Abir85 said:
Yes
Click to expand...
Click to collapse
hmmmm probably an old version adb drivers....is it an x86 or x64 win7?
Edit: i don't think it matters....try this package
and toggle USB debugging first

stathis95194 said:
hmmmm probably an old version adb drivers....is it an x86 or x64 win7?
Click to expand...
Click to collapse
Im using x64 win7

Abir85 said:
Im using x64 win7
Click to expand...
Click to collapse
i edited my post above....try the adb package i attached

stathis95194 said:
i edited my post above....try the adb package i attached
Click to expand...
Click to collapse
Same error. It detects my device serial number and says offline.

Abir85 said:
Same error. It detects my device serial number and says offline.
Click to expand...
Click to collapse
"adb devices" is working? i mean does it recognize your phone?
try also "adb kill-server" and retry.
Try also to reboot phone and PC

Abir85 said:
Hi,
Ok, since my last post I have managed to root my device but the issue is now with trying to get S-Off. As per the give I typed adb reboot but get the device offline error.
Abir
Click to expand...
Click to collapse
I'm having the same issue. I ran RUU RUU_M8_WHL_K444_SENSE60_SPCS_MR_Sprint_WWE_3.30.651.2_R_Radio_1.08.20.0916_NV_SPCS_1.52_003_release_395172_signed_2 to get back to stock from ViperOne Rom, which was running off hboot 3.18 (s-on) and older firmware. After unrooting and relocking hboot, I ran the RUU which worked fine. Once I was back to stock, I then attempted to run adb command adb devices from Win7 with adb 1.0.3.1 installed. I followed all the standard steps (USB Debug on, fastboot off, lockscreen none, and I uninstalled previous HTC drivers and reinstalled when prompted to run htc sync install. Rebooted and tried again and it still says device offline. Anyone know a fix for this?

JTOLOGY said:
I'm having the same issue. I ran RUU RUU_M8_WHL_K444_SENSE60_SPCS_MR_Sprint_WWE_3.30.651.2_R_Radio_1.08.20.0916_NV_SPCS_1.52_003_release_395172_signed_2 to get back to stock from ViperOne Rom, which was running off hboot 3.18 (s-on) and older firmware. After unrooting and relocking hboot, I ran the RUU which worked fine. Once I was back to stock, I then attempted to run adb command adb devices from Win7 with adb 1.0.3.1 installed. I followed all the standard steps (USB Debug on, fastboot off, lockscreen none, and I uninstalled previous HTC drivers and reinstalled when prompted to run htc sync install. Rebooted and tried again and it still says device offline. Anyone know a fix for this?
Click to expand...
Click to collapse
Hey mate sorry for the late reply I have been away for a while. I fixed all my issues with the updated ABD file posted on this thread

Hi!
I have a similar problem. I get "error: device offline"- I already install the adb files from this post. Im on ARHD 50 and I think that I have this problem from Marshmallow on....

elpicard said:
Hi!
I have a similar problem. I get "error: device offline"- I already install the adb files from this post. Im on ARHD 50 and I think that I have this problem from Marshmallow on....
Click to expand...
Click to collapse
Is the phone in the proper mode for the command? It needs to be in bootloader-fastboot mode for fastboot commands. Needs to be booted into OS for adb commands (adb never works in bootloader, common mistake).

redpoint73 said:
Is the phone in the proper mode for the command? It needs to be in bootloader-fastboot mode for fastboot commands. Needs to be booted into OS for adb commands (adb never works in bootloader, common mistake).
Click to expand...
Click to collapse
Im not in bootloader. Im into OS. This happend since Im on 6.0. I already reinstall phones drivers and ADB
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
SHxxxxxxx09 offline

elpicard said:
Im not in bootloader. Im into OS. This happend since Im on 6.0. I already reinstall phones drivers and ADB
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
SHxxxxxxx09 offline
Click to expand...
Click to collapse
OS for adb
Bootloader-fastboot mode for fastboot
This thread refers to both fastboot and adb commands. Which are you using? You haven't specified.

elpicard said:
Hi!
I have a similar problem. I get "error: device offline"- I already install the adb files from this post. Im on ARHD 50 and I think that I have this problem from Marshmallow on....
Click to expand...
Click to collapse
ARHD 50 ? Change your kernel/boot.img
Read this : http://forum.xda-developers.com/showpost.php?p=64450308&postcount=27996