ok so i downloaded the SDK and the windows drivers. i downgraded the phone to rc29 and have just enabled adb on the phone using the command <enter>setprop persist.service.adb.enable 1<enter> and <enter>telnetd<enter>. i opened up CMD in windows and changed the directory where i needed and tried to run adb and it gave me this error: "* daemon not running. starting it now *
* daemon started successfully *
error: device not found"
why did it give me this error? and alo im stuck at the part where im supposed to "copy a busybox binary" using adb push. i dont know exactly what im supposed to do to do that step. i am a noob at this stuff so please be kind and use noob terms and steps.
Thanks
PS: i did connect the phone to the pc with the data cable and the add new hardware thing popped up and i installed the drivers like i was supposed to. it said something about they were installed correctly but may not be working properly, whatever that means.
Try this....
Unplug the phone.
Reboot the computer.
When fully rebooted, plug the phone back in and see what the computer does.
Did it say, "Found new hardware" or some such message?
Did it say that it couldn't find a driver?
Okay - after the OTA updates, I'm now having the same problem! Ouch!
Plugging in, running DOS Command...
c:\> adb devices
Reports that there are no devices attached!
BUG!!!!!!!!!!!!!!!
Related
I was following the guide over at cyanogen's wiki to install the sdk and I haven't been able to get it working.
I added the tools directory to the environmental variable, ran the setup, tried to install the usb driver, and turned on usb debugging but it wont install. Windows gives me a failed to install driver notice and when I type adb devices in the console it says "List of devices attached".
I've uninstalled the drivers with USBDeview and plugged my phone back in several times, but it still wont work.
Using Win7 and a Nexus One, anyone know what I'm doing wrong?
Nevermind, got it working. Went too far into the usb_drivers directory when I was trying to install it..
so my tf300 is rooted and unlocked bootloader, im trying to do the disabling journaling
im already at twrp and my tablet is connected to my pc
but everytime im trying the adb shell it says:
daemon could not start, starting at port 5037
daemon started succesfully
error: device not found
what seems to be the problem here? i tried to install my sdk, still no luck.
Using USBDeview (suggested here - comment 7 : http://code.google.com/p/android/issues/detail?id=2676 ) helped me get my TF300 to appear under 'adb devices'.
Still can't seem to access the device via localhost though.
(I'm trying to get access for web-dev purposes - see here : http://forum.xda-developers.com/showthread.php?t=1966358 )
i feel useless... after i run the batch file from the extracted motochopper folder, it starts in terminal and says not found followed by daemon started and nothing happens.. i checked usb debug and the unknown source security boxes on the tablet and since im running windows 7, i ran the batch file as administrator. please anything will help kind of afraid to pull usb cable out of laptop what do i do now??
beahrr77 said:
i feel useless... after i run the batch file from the extracted motochopper folder, it starts in terminal and says not found followed by daemon started and nothing happens.. i checked usb debug and the unknown source security boxes on the tablet and since im running windows 7, i ran the batch file as administrator. please anything will help kind of afraid to pull usb cable out of laptop what do i do now??
Click to expand...
Click to collapse
Sounds like your ADB is not working. Can you connect to your device thru ADB from a PC?
Code:
adb devices
Should echo your S/N. If it says "List of devices attached" followed by blank (nothing) then your ADB is not working and you need drivers for W7, W8. You also have to add the path to platform tools to your Windows system environment variables path so the system can find it.
Code:
which adb
Should echo "/system/bin/adb" otherwise you don't have the adb binary installed on your device.
Code:
adb version
Should echo 1.0.29 for 4.1.1
Should echo 1.0.30 or 1.0.31 for 4.2.1 (secure adb)
elfaure said:
Sounds like your ADB is not working. Can you connect to your device thru ADB from a PC?
Code:
adb devices
Should echo your S/N. If it says "List of devices attached" followed by blank (nothing) then your ADB is not working and you need drivers for W7, W8. You also have to add the path to platform tools to your Windows system environment variables path so the system can find it.
Code:
which adb
Should echo "/system/bin/adb" otherwise you don't have the adb binary installed on your device.
Code:
adb version
Should echo 1.0.29 for 4.1.1
Should echo 1.0.30 or 1.0.31 for 4.2.1 (secure adb)
Click to expand...
Click to collapse
Thanks man, btw how do you thank on here to make ur thank meter grow
I ran into the same problem with win7. When I plugged in my tablet, it seemed like it would lose the connection shortly after connecting it. I eventually got it to root by running motochopper, and then plugging in my tablet. This was the only thing that worked, even after installing every Asus USB driver know lol.
Hope this helps
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Hey everyone, I keep getting a "adb out of date...killing" whenever I try and use ADB with my Motorola Moto G.
I think I somehow have messed up the ADB files or something, I want to start an ALL new installation of ADB to see if I can get my computer to get it working correctly.
How do I go about completely removing ADB from my computer so I can redownload it and reinstall it ?
ikillechewbacca said:
Hey everyone, I keep getting a "adb out of date...killing" whenever I try and use ADB with my Motorola Moto G.
I think I somehow have messed up the ADB files or something, I want to start an ALL new installation of ADB to see if I can get my computer to get it working correctly.
How do I go about completely removing ADB from my computer so I can redownload it and reinstall it ?
Click to expand...
Click to collapse
Install THIS and you're fine again
LS.xD said:
Install THIS and you're fine again
Click to expand...
Click to collapse
I downloaded that and installed it....I still get problems with my adb.
Here are more examples of the problems I am getting :
"adb server is out of date. killing..."
"adb server didn't ACL"
" * failed to start daemon *
error:
uninstall Android Phone or Android composite ADB interface from the device manager
Hello, I hope that this topic can be opened here, if not please move it or let me know and I will delete it.
In adb I am getting the error "failed to check server version: protocol fault (couldn't read status): No error" and I cannot see my device when I use the command "adb devices". Moreover, it seems like my phone is not letting me authorize my laptop for USB debugging despite trying different options to getting it to work. I have tried different trouble shooting methods that I have found online, but nothing has worked so far. If anyone has any ideas, it would be greatly appreciated.
I am using a POCO F2 Pro that has had its bootloader unlocked and I am running Xiaomi.eu version 12.0.4 (stable) and using a Windows 10 machine to connect with my phone. I did not have much problems with the flashing off TWRP, using ADB commands, or flashing the ROM when I did all of these things last month.
Now, however, I have been having some problems. I believe it started when I tries to update the System FW a few days ago in the phone instead of flashing it manually. Because it was the stable version, and because the option existed in my system settings, I thought that I would be able to update it without going through those steps. The update downloaded and I got the correct file, but when I hit install, I did not get the new FW, despite the phone rebooting. I've been having problems with adb since this time, I believe.
Try restarting adb server:
Code:
adb -d kill-server
adb -d start-server
Try re-enabling USB debug stuff in Dev Options too.
Saratoga79 said:
Try restarting adb server:
Code:
adb -d kill-server
adb -d start-server
Try re-enabling USB debug stuff in Dev Options too.
Click to expand...
Click to collapse
Hello, thanks for your reply. I tried that yesterday, but I gave it another try today. This was the error that I received when I ran the command in Powershell:
Program 'adb' failed to run: No application is associated with the specified file for this operationAt line:1 char:1
+ adb -d kill-server
+ ~~~~~~~~~~~~~~~~~~.
At line:1 char:1
+ adb -d kill-server
+ ~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ResourceUnavailable: ) [], ApplicationFailedException
+ FullyQualifiedErrorId : NativeCommandFailed
When I ran the command in Command Prompt, I got the error "failed to read response from server".
Trying to start the server also lead to an error "protocol fault (couldn't read status): No error
---------
Part of my issues may be coming from the fact that I no longer get the authorize USB debugging on my phone, even after I have revoked the authorizations. I've tried different ports, different USB cables, and even factory resetting my phone, to no luck.
Try using the latest platform tools from Google.
batuken said:
Try using the latest platform tools from Google.
Click to expand...
Click to collapse
From what I know, I am using the latest SDK platform tools. I initially downloaded from that site either in late July or early August, and yesterday I deleted the old files and re-installed them from the website. Is there an additional step that I might have missed in removing the old files from my computer?
Additionally, the .android folder in my user profile is now empty (no adb_key file(s) inside).