I updated to 2.2 via the RUU and reflashed clockworkmod and re-rooted. Now when I try to connect via adb shell, I get the following error:
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
I've searched the forums and didn't find any answers. Anyone got any ideas on what I can do to get ADB working again?
Never mind. I had to uninstall the HTC drivers (required for the RUU) and reinstall the drivers I used when I originally rooted.
I'm getting the same error message. Mind linking to the drivers you downloaded for the fix? Thanks.
Bad Daddy said:
Never mind. I had to uninstall the HTC drivers (required for the RUU) and reinstall the drivers I used when I originally rooted.
Click to expand...
Click to collapse
"and reinstall the drivers I used when I originally rooted."
what driver is this?
Related
so i'm running Fresh .3 despite what my sig says haha
i'm having a problem running adb. i use terminal on my mac. i am fully rooted and nand unlocked. but this is my problem...
Code:
Matts-Computer:~ Matt$ cd ~/desktop/sdk/tools
Matts-Computer:tools Matt$ ./adb remount
adb server is out of date. killing...
* daemon started successfully *
error: device not found
Matts-Computer:tools Matt$
it happens every time :/
can anyone help?
thanks in advanced.
mrchu001 said:
so i'm running Fresh .3 despite what my sig says haha
i'm having a problem running adb. i use terminal on my mac. i am fully rooted and nand unlocked. but this is my problem...
Code:
Matts-Computer:~ Matt$ cd ~/desktop/sdk/tools
Matts-Computer:tools Matt$ ./adb remount
adb server is out of date. killing...
* daemon started successfully *
error: device not found
Matts-Computer:tools Matt$
it happens every time :/
can anyone help?
thanks in advanced.
Click to expand...
Click to collapse
you aren't in disk mode are you? you need to be in charge mode and usb debugging needs to be checked.
apristel said:
you aren't in disk mode are you? you need to be in charge mode and usb debugging needs to be checked.
Click to expand...
Click to collapse
i'm in charge mode and usb debugging is checked
i'm going crazy trying to fix this..
mrchu001 said:
so i'm running Fresh .3 despite what my sig says haha
i'm having a problem running adb. i use terminal on my mac. i am fully rooted and nand unlocked. but this is my problem...
Code:
Matts-Computer:~ Matt$ cd ~/desktop/sdk/tools
Matts-Computer:tools Matt$ ./adb remount
adb server is out of date. killing...
* daemon started successfully *
error: device not found
Matts-Computer:tools Matt$
it happens every time :/
can anyone help?
thanks in advanced.
Click to expand...
Click to collapse
have you tried updating your android sdk files? have you tried restarting both computer and phone? restarting the specific adb server (adb kill-server)?
i've never seen this error message before from adb. it seems very distinct though, have you tried googling this error message?
I have noticed sometimes when switching roms, even if USB debugging is checked I need to uncheck and check again to get it to work. Other than that, everything should work fine if your on OSX. hmm...
Hey, first here's some information on my phone:
Arc S
Model Number: LT18i
Android Version: 4.0.3
Build Number: 4.1.A.0.562
Bootloader Unocked: Yes
So, I unlocked the bootloader and I'm now trying to root the device; in order to install Cyanogenmod. I've tried both methods at (I can't post links =__=):
techdraginfo.blogspot.com/2012/06/root-sony-xperia-arc-arc-s-official.html
Click to expand...
Click to collapse
neither have worked for me.
Here's what I've done and what isn't working.
For method 1:
I've installed the ADB drivers, get up to step 8, put the phone in fastboot mode, enter the command fastboot boot ARC-DooMKernel-ICS-BETA-v04-lower-boot.img and I'm prompted with:
Device Waiting
Click to expand...
Click to collapse
It never gets past this point.
For the One-Click method;
I've installed the ADB drivers, extracted DooMLoRD_v1_Xperia-2011-ICS-ROOT-emu-busybox-su.zip to C:\, run the .bat script and I get a whole bunch of issues related to ADB, such as:
--- STARTING ----
--- WAITING FOR DEVICE
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- creating temporary directory
* 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
It continues like this for the rest of the script. I don't understand why it will not connected to the ADB server. I've killed any ADB processes previously running prior to running this script and turned off my anti-virus changes.
Any idea why this is?
Cheers
Slycs said:
I've tried both methods at (I can't post links =__=):
Click to expand...
Click to collapse
Use the methods from xda, you can find them in the stickys or browsing general, or what you should have done first, searching - root arc s
If you want to install CyanogenMod and you have unlocked your bootloader, then just install kernel and install ROM from it. No root necessary.
Sent from LT18i with custom firmware by myself.
Hey guys!
I've definitely missed something obvious.. and please forgive me in advance
I used to have cyanogenmod 12 installed and had some minor issues that was bugging me. I decided to update the phone with RUU GPE marshmallow.
The phone is working fine now, but I can't use adb commands through usb anymore...
it says
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
SH43BWM00xxx offline
I would like to install TWRP 3 but I can't send any commands
how can I get it to work?
phone is S-OFF
and yes.. I have activated usb debugging
check your adb version, command adb version
You need at least 1.0.31 or better 1.0.32
ckpv5 said:
check your adb version, command adb version
You need at least 1.0.31 or better 1.0.32
Click to expand...
Click to collapse
Thanks a lot... I was on my macbook and it didn't work. Tried on my PC and I had a newer version installed there.
Updated the mac adb and everything works on it too
Hello friends, I come to expose my problem, if someone can help me, I would appreciate it very much.
I have installed the latest [TOOL]Minimal ADB and Fastboot [1-6-17] in my Win 10 64bit PC, The PC recognizes me device, I can install the TWRP (.28) by fastboot and works great later flash again the stock recovery (recovery_OBT8N.img) and try to install the oficial OTA with sideload, it say "cannot read", I try:
* Re-installing the ADB drivers from others.
* With the original file name, and with the name modified "update.zip".
* Reboot my PC and device.
* Used the Ccleaner.
* With Adm CMD
* Leaving and entering the address where are the drivers and the file, with the CMD
* Typing: adb kill-server. adb root. adb sideload update.zip
* typing the file name: "update.zip" - "update" - "update.zip.zip"
* Putting the drivers in another direction
* Try differents files: ("OB10.zip" and "OOS4.zip"
* Use generic adb and nexus adb
* The lasted Stock recovery (recovery_OBT8N.img)
I know I can install OOS4 with twrp, I know because I have it, but I wanted to remove the DM-verity message and I followed this guide: [FIX] Device-Mapper-Verity fix for Oxygen OS Nougat Rom ( 4.0 and Open Beta's) And that's how I knew I can not use the sideload....
If anyone knows that I could try more, thank you very much, thank you.
ERNZT said:
Hello friends, I come to expose my problem, if someone can help me, I would appreciate it very much.
Click to expand...
Click to collapse
More info would be a pleasure ur on twrp? Boot into it type adb push Filename /sdcard/ it should push the file to /sdcard/ so you can manually flash it.
ERNZT said:
Hello friends, I come to expose my problem, if someone can help me, I would appreciate it very much.
I have installed the latest [TOOL]Minimal ADB and Fastboot [1-6-17] in my Win 10 64bit PC, The PC recognizes me device, I can install the TWRP (.28) by fastboot and works great later flash again the stock recovery (recovery_OBT8N.img) and try to install the oficial OTA with sideload, it say "cannot read", I try:
* Re-installing the ADB drivers from others.
* With the original file name, and with the name modified "update.zip".
* Reboot my PC and device.
* Used the Ccleaner.
* With Adm CMD
* Leaving and entering the address where are the drivers and the file, with the CMD
* Typing: adb kill-server. adb root. adb sideload update.zip
* typing the file name: "update.zip" - "update" - "update.zip.zip"
* Putting the drivers in another direction
* Try differents files: ("OB10.zip" and "OOS4.zip"
* Use generic adb and nexus adb
* The lasted Stock recovery (recovery_OBT8N.img)
I know I can install OOS4 with twrp, I know because I have it, but I wanted to remove the DM-verity message and I followed this guide: [FIX] Device-Mapper-Verity fix for Oxygen OS Nougat Rom ( 4.0 and Open Beta's) And that's how I knew I can not use the sideload....
If anyone knows that I could try more, thank you very much, thank you.
Click to expand...
Click to collapse
Most of the times the problem is really on the desktop configuration, ie usb drivers, adb version, usb port power, user profile permissions, etc. Note that you need a newer adb version to do stuff such as sideload. From the top of my head, I think you need 1.0.32 or newer. I know it seems overkill, but until google decides to distribute the platform tools in a separate minimal bundle, the best option is to install the android SDK. You can choose then to selectively install only the platform tools that include adb.
Sent from my ONEPLUS A3000 using Tapatalk
https://forum.xda-developers.com/showpost.php?p=69648733&postcount=47 is definitely the best fix i found, if it doesn't work reboot your PC and do it again it worked for me.
Hope it can helps
So, when entering "fastboot devices" when phone is in Download Mode, nothing.
When trying "fastboot oem get_identifier_token", it says waiting for devices.
Also, got this new error by "adb devices":
adb server version (31) doesn't match this client (39); killing...
error: could not install *smartsocket* listener: cannot bind to 127.0.0.1:5037: Only one usage of each socket address (protocol/network address/port) is normally permitted. (10048)
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
could not read ok from ADB Server
* failed to start daemon *
error: cannot connect to daemon​
If you guys need anything else, just ask.
Thanks
You need to update your adb version on your computer.
Re: The thingy
BlockOfDynamite said:
You need to update your adb version on your computer.
Click to expand...
Click to collapse
For the ADB problem or both?
Probably both. The best thing you can do is to download the latest adb and go from there. If it fixes it, great, if it doesn't, then the problem can be diagnosed further.
BlockOfDynamite said:
Probably both. The best thing you can do is to download the latest adb and go from there. If it fixes it, great, if it doesn't, then the problem can be diagnosed further.
Click to expand...
Click to collapse
Got the latest adb from Google Platform Tools and the latest fastboot from the HTC dev instructions.
ADB works sometimes, but fastboot does nothing.
absp2006 said:
Got the latest adb from Google Platform Tools and the latest fastboot from the HTC dev instructions.
ADB works sometimes, but fastboot does nothing.
Click to expand...
Click to collapse
Reboot to bootloader using adb reboot-bootloader. Then try fastboot commands.
Everybody!!!
It turns out that by updating the drivers while the phone is in download mode got fastboot to work!!!