I suspect I may have done something wrong with my phone and ADB drivers.
No matter what PC I try this on and no matter what ROM I'm on, I can only do ADB in the Android system. Not in a bootanimation, not when on a kernel logo, only inside Android.
So doing any porting, ROM debugging and so on is useless since, for example, if a ROM is in a bootloop, I cannot determine what's wrong, since I can't get a logcat.
I have the FlashTool drivers installed, my phone is an Xperia S (nozomi).
If anyone has any idea what may be wrong, please, suggest it.
So far, I've tried it on a 32 and 64 bit WinXP PC, on a 32-bit Vista PC and a 32-bit W7 PC. And also on 64-bit W8.
Thank you.
My friend had a similar problem.. What he did was reinstall drivers before connecting the phone in adb in recovery
It worked but he had to reinstall every time he wanted to connect adb that way
So it's a temporary fix
Sent from my LT26i using Tapatalk 4
Temporary is better than nothing, but alas, I have already tried it.
Reinstall drivers in recovery, but then it's only visible inside recovery and inside Android...
Thank you, still, for your help. If you have any more ideas, keep 'em coming.
Related
I have been searching for several hours, and I am absolutely unable to get ADB to recognize my phone using Windows XP 64 bit. I have uninstalled and re-installed the Unrevoked modified drivers several times to no avail. All I get is "Error: Device Not Found". Does anyone know a trick to getting ADB working on XP 64? I appreciate any and all help.
Thanks!
EVO HW 0003
HBOOT 2.10
MIKFROYO 4.4
Make sure the rom your using has adb functionality included/enabled in the rom.
And make sure usb debugging is enabled under settings/applications
Swyped from a galaxy far far away......
I have connected to the same phone with another computer. All settings are confirmed correct on the phone itself.
I know a trick, but I haven't tried it with the Evo or XP! I bet it works though. I used it to get my hero working with win7 last march, and it worked great.
install PDAnet.
It is a tethering program and has the ADB drivers, should set them up for you.
Also installing HTC sync is supposed to get the drivers working.
Thanks I will give that a shot and report back.
PDANet didn't work but I found an HTC driver for 64 bit windows 7 that did the trick.
Thanks for your help.
Windows sucks and 64 bit XP is a pain in the ass. You need a usb driver or linux.
sixspeeder said:
PDANet didn't work but I found an HTC driver for 64 bit windows 7 that did the trick.
Thanks for your help.
Click to expand...
Click to collapse
can u post the driver.?
Here it is. Be sure to uninstall any other drivers. I used USBDeview to uninstall the old drivers. Extract this zip and use the driver inside for Android 1.0 when prompted. It will not show up as Android ADB in Device Manager (showed up as My HTC Phone or something on mine) but ADB connected immediately once I installed this driver.
I doubt that it will work
Works for me!
Been looking at this for two hours now...
Running 64-bit XP - Installed the drivers manually by connecting the device, then selecting not now.... navigated to the drivers, installed BOTH .ini files - not sure if was really two different drivers or not - restarted, reconnected and device showed up.
The name my device function says "Desire" but it seems to work so far (only one sync)
Guys, I need a little help here. I've rooted my share of phones, and even some tablets, but the Evo i bought a few days ago has been a nightmare.
For some reason, and I can't tell why, this thing will not be recognized by Windows.
It always shows up as "Unknown Device" under the USB catagory on Device Manager.
I've tried different OS versions (Windows 7 64Bit, Vista 64bit, Even Mac). I've also pulled down every form of driver I can think of (SDK Orginal version, HTC Sync, Hboot Versions, etc.)
I just cannot get this thing to be recognized. And if I manually try to update the driver and point it to one that I've downloaded, Windows tells me that the most current driver is already installed.
The bottom line is that I need to be able to connect to the phone from the comp in order to push stuff via ADB and throw commands at it. The same unknown device situation happens when the phone is in bootloader or actually booted into Stock Froyo (2.2)
Has anyone ever seen anything like this? I know i haven't, and it's buggin me out.
buster3845 said:
Guys, I need a little help here. I've rooted my share of phones, and even some tablets, but the Evo i bought a few days ago has been a nightmare.
For some reason, and I can't tell why, this thing will not be recognized by Windows.
It always shows up as "Unknown Device" under the USB catagory on Device Manager.
I've tried different OS versions (Windows 7 64Bit, Vista 64bit, Even Mac). I've also pulled down every form of driver I can think of (SDK Orginal version, HTC Sync, Hboot Versions, etc.)
I just cannot get this thing to be recognized. And if I manually try to update the driver and point it to one that I've downloaded, Windows tells me that the most current driver is already installed.
The bottom line is that I need to be able to connect to the phone from the comp in order to push stuff via ADB and throw commands at it. The same unknown device situation happens when the phone is in bootloader or actually booted into Stock Froyo (2.2)
Has anyone ever seen anything like this? I know i haven't, and it's buggin me out.
Click to expand...
Click to collapse
I've never seen that before. Wish I had something for ya. Is the Evo brand new or used? Are you sure the usb cable is good? I've seen a bad cable cause some headaches before. Wish I had more for ya, sorry man.
Sent from my PC36100 using XDA App
EVO is not new. I bough it from cragslist a few days ago. It seems to work fine otherwise. Not rooted for sure, and running Sprint original 2.2.
I did try a couple of different USB cables just to be sure, and had the same results.
The funny thing is that even though I was never able to get it "recognized" on any of my machines, I was able to get ADB so "see" it for a while. I started the rooting process by pushing files to it via ADB and even sent a reboot command to it.
Once it rebooted, that's when it all went bad. It was still showing as unrecognized (just like before), but now ADB can't see it at all. Keeps telling me no devices are connected.
Even my friend's Mac Air (which supposedly doesn't need any kind of drivers to see the phone) can't see it either.
It's just weird...
perform a hard reset, maybe a rogue app or setting got messed up,
fastboot screen>clear storage>yes
Tried that as well. Sorry i didn't mention it in the original post.
I think I've pretty much tried everything that's somewhat logical at this point.
Now I'm looking for the "illogical" ideas.
Make sure usb debugging option is turned on in settings>applications>development and the phone is in charge only mode. Then it should be recognized and you should be able to use adb.
Debugging was turned on already. I made sure of that.
As for the mode of connection I've tried them all with mixed results.
Here's what I've seen so far...
Charge only - unrecognized device in Device manager, and ADB can't see it.
HTC sync - unrecognized device in Device manager, and ADB can't see it.
Disk Drive - unrecognized device in Device manager, and ADB can't see it.
Internet Sharing - never tried it.
Here's the weird part. If i uncheck Debugging and set the phone to HTC Sync, I am sometimes able to get ADB to see it.
This is just confusing...
What happens if you uninstall HTC Sync and just leave the drivers installed? Could work I suppose. I know unrevoked says to make sure you uninstall HTC Sync and install the ADB drivers.
try this. connect your evo to a machine running xp. i had the same problems rooting one evo using windows 7. connected to a machine running xp ,zipped right through without a hitch.
HOPE THIS HELPS YOU IN YOUR QUEST
Thats what I tried on the Vista box.removed HTC sync, and left the HTC drivers.when that failed I removed the drivers too and replaced them with several different ones I found online.none seemed to work.
The strangest part is that all guides seem to say that MAC OS should just see it without any drivers.
I borrowed friends MAC air and it didn't see it either.
I'm not sure which USB drivers you are using, but these work for me. Uninstall the drivers first, then install this. I hope it is legal to put these here and if not I am extremely sorry.
PS you could try a Linux Live CD and it will see it without drivers or go with Wubi which installs Ubuntu on your Windows hard drive and can be uninstalled just like any other program. It gives you the option to boot into Ubuntu or Windows on bootup. Neat little program and it is faster than using the live CD. Go to this link Wubi and click the Start Download button to download Wubi.
Those seem to be the same drivers I've tried (well those and a ton of others as well).
I'm gonna give that LiveCD idea a shot. Burning it now.
If not, I'm gonna try to find an XP machine somewhere.
I've got a couple of VM's on my machine running XP, but since the main Win7 Machine doesn't see it, it can't seem to pass the USB connection over to the XP VM.
Man, I have to say, this is just the most complicated rooting process I've ever seen. If this was my first root attempt, I'm pretty sure I'd leave Android forever
It usually is a painless operation to root the Evo. For some reason you are having a difficult time with driver installation. It seriously has to be something simple that has been missed, because I have rooted mine and several friends Evo's and it was very easy. I had a MyTouch 3g 3.5mm before this Evo and talk about a pain. Before the Universal Auto root app you had to make a gold card first and that in itself took over an hour. It was my first root and it was very difficult and time consuming, so to see how easy the Evo was no matter which way I do it made me very happy.
buster3845 said:
Thats what I tried on the Vista box.removed HTC sync, and left the HTC drivers.when that failed I removed the drivers too and replaced them with several different ones I found online.none seemed to work.
The strangest part is that all guides seem to say that MAC OS should just see it without any drivers.
I borrowed friends MAC air and it didn't see it either.
Click to expand...
Click to collapse
yes the mac doesn't require additonal drivers to run adb however u need to make sure the directory is properly set in terminal so adb knows where to pull commands from... on windows did u try uninstalling everything phone related? SDK, HTC Sync, the whole nine yards then try reinstalling only the sdk and the usb drivers? I know with the lastest SDK the usb driver is not included for some reason or at least it wasn't with mine... then one day my adb just randomly stopped working and a uninstall/reinstall cleared up everything... try this usb driver and see where it gets u. Don't know if it's any different that wat the guy above posted but worth a shot. Reinstall the appropriate SDK first then i would recommend plugging the evo into the pc with no usb drivers installed then when it cant automatically find the drivers direct it to the file u downloaded and it should pull the necessary drivers from there and see if that does the trick...
View attachment android-usb-driver.zip
No dice so far guys...but i have made progress in identifying the issue (sort of).
So here's the deal - the ONLY way the phone is recognized is if i toggle the "debugging" setting.
If i plug the phone in with the switch set on (meaning USB Debugging enabled) the phone is not recognized. Pointing the unknown device to the drivers (any drivers) does nothing.
However, if i plug the phone in with the switch set off, it finds a usb mass storage device. Then i turn the debugging switch on, and it finds the ADB Android phone with no issues. Then i can push commands via ADB without any problems.
The problem i have is that I cannot toggle that switch if i boot into HBOOT menu. So the comp never see's the phone.
I've tried this experiment on Win7-64bit, Vista-64bit, XP 32bit, and even MAC.
The same situation seems to apply everywhere, and with all of the drivers I've tried. None of them seem to allow the phone to be plugged in and automatically be found. The only way for the comp to see the phone is if i toggle the debugging switch off, then on.
At this point, I'm ready to put out a bounty on this. $20 via PayPal to anyone who can walk me through it. Bottom line is that I need to be able to see the phone without having to toggle the debugging switch. That will allow me to boot into HBOOT and still send commands to the phone via ADB.
Thanks for all the help guys. Hopefully, we can get this resolved.
**BUMP**
Anyone care to take a shot??
I need help! FKU 0.9.5. Drivers set. Kindle is seen by the system (Windows) as Android Phone\Android Composite ADB Interface . When you run status of the ADB is offline, the status of unknown boot. FKU ustonovlena in C / FKU. What is the problem?
Thanks in advance for your help.
sergei pan said:
I need help! FKU 0.9.5. Drivers set. Kindle is seen by the system (Windows) as Android Phone\Android Composite ADB Interface . When you run status of the ADB is offline, the status of unknown boot. FKU ustonovlena in C / FKU. What is the problem?
Thanks in advance for your help.
Click to expand...
Click to collapse
Ustonovlena? What is that? Serbian? Nevertheless. Even when Windows says the drivers are installed, if adb doesn't connect, it's a driver issue. Uninstall and delete your current drivers then reinstall with the device turned off. When you turn the device back on, KFU should recognize it.
If not, try to issue the command you need anyway. Sometimes it will work anyway. Either way, it is a driver issue. Keep working at it. You may have to reboot your computer to get it to work but as long as you understand that it's the drivers causing problems, you should be able to get it working.
try to change to another user,or worst still use another pc.
Not sure if this can work,but its worth a try since mine work this way.
Sorry. I am writing through Google. Russian. Already endured, and once again put the driver. It did not help.
What rom are you using?
Rom?
If I understand you correctly, a native Amazon 6.3.
The reason I ask is that some custom roms have USB debugging turned off by default and others have trouble with adb to begin with.
But, considering that is not the case, it is a driver issue, plain and simple.Just keep trying. Uninstall/delete/reinstall your drivers. It may help to get the Android SDK and configure them yourself.
It has been repeatedly reinstalled the driver. It does not help. Tried on two computers (XP and Vista). The result is the same. The question-whether the Kindle can be seen in My Computer? I have Windows does not see it.
Programmes at the request of the developer to KFU (Vashypooh) to help. Write in the subject can not have enough rights-http://forum.xda-developers.com/showthread.php?t=1399889.
I beg to inform him of my request for help.
Im having the same issue
I cant tell you how many times i have re installed the drivers. Reboots in between.. u name it
One time i did get adb to see my device. But it still wouldn't fast boot
Im on 2.2.. its a brand new refurb..got it today
Sent from my DROID RAZR using XDA
So guys I feel so very stupid right now because I completely did this to myself and I realized what I did after the fact and now I am stuck with a KF that is booting up and then crashing and rebooting after about 20-30 seconds.... I decided that I wanted to have a stock ROM on the fire backup up if for some reason I wanted to go back to that UI. I made a nandroid and then flashed the 6.3.1.zip file that i downloaded from amazon's website. Have you spotted the mistake already? that's right, i forgot to wipe the cache and system and now I have a broken KF.... does anyone know what I can do to recover from this horrific boot loop? perhaps a hard reset of some sort that will erase everything so I can start from scratch? or at least have a stock fire?? thanks in advance for any help, such a n00b mistake....
If you think it helps, I CAN access the "SD" memory but I haven't had success with ADB
If you can reach the sdcard then you should have adb..... AFTER reinstalling the drivers.. try that..
fiddlefaddle said:
If you can reach the sdcard then you should have adb..... AFTER reinstalling the drivers.. try that..
Click to expand...
Click to collapse
Disconnect KF, shut it off, reinstall driver and finally connect the KF to the computer.
Gửi từ Kindle Lửa của tôi qua Tapatalk 2
fiddlefaddle said:
If you can reach the sdcard then you should have adb..... AFTER reinstalling the drivers.. try that..
Click to expand...
Click to collapse
Two odd things: I rooted the kindle using this computer, so you would think that the drivers would be fine but for some reason it is not working. I ran the install_drivers.bat from KFU and it installs fine but then if i go back to device manager it says that these drivers "WPD FileSystem Volume Driver" is installed and when I try to install the adb drivers it says that the best driver for the device is already installed which is the WPD FileSystem Volume Driver and if I try to uninstall the drivers, it seems like it doesn't do anything at all. I will uninstall the drivers, disconnect and then reconnect the kindle and then it shows up with the same drivers again! any suggestions? I would really like to be able to use my kindle again...
nschiwy said:
Two odd things: I rooted the kindle using this computer, so you would think that the drivers would be fine but for some reason it is not working. I ran the install_drivers.bat from KFU and it installs fine but then if i go back to device manager it says that these drivers "WPD FileSystem Volume Driver" is installed and when I try to install the adb drivers it says that the best driver for the device is already installed which is the WPD FileSystem Volume Driver and if I try to uninstall the drivers, it seems like it doesn't do anything at all. I will uninstall the drivers, disconnect and then reconnect the kindle and then it shows up with the same drivers again! any suggestions? I would really like to be able to use my kindle again...
Click to expand...
Click to collapse
Uninstall the drivers from device manager first, then run install_drivers.bat
sent from my Nokia 5110
Thought I saw someone else with this problem a bit ago. Found this link. Maybe it will help a bit.
http://forum.soft32.com/windows/Microsoft-WPD-FileSystem-Volume-Driver-bootup-ftopict347023.html
pbailey212 said:
Uninstall the drivers from device manager first, then run install_drivers.bat
Click to expand...
Click to collapse
It's very strange, the install_drivers.bat seems to be installing drivers for a device that it is not associating with my kindle so every time I try to uninstall, it just comes back. It's really strange too because ALL of my computers are doing this... would I be better off if i tried from a linux machine rather than windows? from what I've gathered this default driver is a windows/microsoft substitute for mass storage that it doesn't know what else to do with. Is it possible that even though android is clearly running (even though it is only for a little while) that it is unable to communicate with the computer at all?
this is mostly a bump, not sure if it will work but I still haven't had any luck. I was grounded on my XP machine when it wouldn't install the drivers because they were unsigned... saw a tutorial on how to fix that but it was very confusing and unclear. But if anyone has had this problem or has ANY suggestions I am all ears. The kindle was a christmas gift from my parents and I really wish I had just left it alone now. ("if it ain't broke, don't fix it")
It is really much harder on xp to sort out the driver issue acesss to a machine running at least windows 7 would help you out alot. Otherwise go through the process of downloading the Java development kit and using sdk manager to acquire the platform tools for android 2.3 make sure you grab the Google driver this one is signed .
I have no problem putting the jdk and sdk on my personal computers but the xp machine is my mom's so I'm not going to put those on. I thought there would be no problem if i could have used the install_drivers.bat but that turned out to be a bust. Besides that, I wasn't able to find the kindle in the device manager...
nschiwy said:
I have no problem putting the jdk and sdk on my personal computers but the xp machine is my mom's so I'm not going to put those on. I thought there would be no problem if i could have used the install_drivers.bat but that turned out to be a bust. Besides that, I wasn't able to find the kindle in the device manager...
Click to expand...
Click to collapse
Your last sentence tells me that you might not be sure what you are looking for in the device manager.
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
kinfauns said:
Your last sentence tells me that you might not be sure what you are looking for in the device manager.
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
Click to expand...
Click to collapse
I really appreciate your help. I've actually been trying to use your guide to see if there was anything I missed. Unfortunately I've not had very much luck. Honestly I've gotten to the point that I would be willing to pay someone if they were confident that they could fix it and I would even pay the shipping both ways. I just want to try to use a linux box to fix it and if I am still unable to communicate with the device through ADB I would be willing to employ anyone from these forums with enough knowledge that they are confident that they could fix it to do it for me. As long as the price was reasonable, of course, keeping in mind that I could buy a refurbished one from amazon for $160 so paying 70-100 would be outlandish... I bought a new HDD for my pc so I could boot linux (I hate dual boots) and after that comes and I still have no luck I will be seeing if anyone would be interested. It's probably a great learning opportunity as well and would be a great addition to the forums if we know what to do when something like this happens.
What OS were you basing this guide from out of curiosity?
http://forum.xda-developers.com/showthread.php?p=26491884
soupmagnet said:
http://forum.xda-developers.com/showthread.php?p=26491884
Click to expand...
Click to collapse
Thank you so much, this will certainly come in handy! I've actually used Ubuntu 11.04 before and I really liked it aside from a few bugs that I didn't feel like dealing with that eventually led me to switch back to windows. So, hopefully this will be the end all in terms of android/kindle fire issues.
okay so, I finally got a hard drive today for my laptop. Booted up Ubuntu 12.04 and used andadb.sh to install all of the necessary software. However, I am not able to connect to my kindle through adb, even on linux. Is there something I may have done wrong somehow? I used the adb_usb.ini from KFU, I don't know for sure that was correct but soup didn't put a link up on his guide so I made an educated guess. I am amazed that nobody has had this problem before, it seems like a very easy mistake to make, at least it was for me! as always, any suggestions will be greatly appreciated!
Try sudo fastboot devices
I'm sorry is this a command? I'm not very familiar with linux you might need to hold my hand on this one. and I tried to adb devices and nothing was listed, will using sudo fastboot devices make a difference? again, sorry for the ignorance, I will try it, I am just addressing concerns.
What bootloader are you using just give me a refresh of your situation so I don't have to read I'm at work but I can still help ya.
okay so basically I don't have a bootloader or recovery because I was planning on rerooting after reinstalling the stock amazon android, only problem is that I forgot to wipe before installing the OS and now I have a Frankenstein amazon gingerbread which is competing with the ICS i had previously installed on the device and continues to crash after about 20 seconds being on and reboots. I am able to access the sd memory, even when it is rebooting but I haven't had any successful connection using adb. If I had, I would imagine I could just reflash twrp and fff and I would then wipe and install a ROM and be good to go but as of now I just have a constantly bootcycling KF that for some reason has no precedent for repairing.
Shutdown and reboot the phone
Hi,
I have an HTC One X which is in a soft bricked state, it boots but has no ROM on it. I was going to flash a new ROM by using adb push, but for some reason the phone is not fully recognized as ADB. When I connect it it is recognized as "Other Devices->One" and ADB does not recognize any connected devices.
I've installed HTC Sync, the universal ADB drivers, all don't work.
My PC has Windows 8.1 64-bit.
Now I can't use the phone as I have no means to push the .zip files to it.
Problem solved by using Ubuntu 14.10 which detected my phone perfectly. It was very easy to install ADB and fastboot on it and I didn't even need ADB, Ubuntu detected my phone as a removable device and I just copied the zips.
An example why Linux can be better than Windows.
smash_07 said:
Problem solved by using Ubuntu 14.10 which detected my phone perfectly. It was very easy to install ADB and fastboot on it and I didn't even need ADB, Ubuntu detected my phone as a removable device and I just copied the zips.
An example why Linux can be better than Windows.
Click to expand...
Click to collapse
I love it when people take the time and post how they solved the problem themselves, in case anybody else in the future has the same issues. Kudos to you! :good: