Is anyone having problems with adb and vista?
When I start the adb shell I can type about 2 or 3 commands and then it stops responding. When I type the 3rd command or so instead of it going back to # at the command prompt it just goes to the next line with out a prompt.
Also when this happens I go to task manager and try to shut down the adb.exe but it won't I have to reboot my computer.
I have a laptop and a usb keyboard when I start have the problems with adb my key board wont work ether. So I have tried it with out the usb key board but have the same problem.
I have also tried running adb and xp compatible but still have the same problem. Is there anything else I can use other than adb?
I am having problems as well. I flashed my custom boot image yesterday and now today it is saying that it cannot find my device. It has worked since December and then today, nothing. In Need of Help.
What version of vista are you using??,,, additionally this should be moved to the "Dream" Section
I have Ultimate x64, have no issues. I assume you have the proper drivers as you can do a couple commands, yes??
Vista 32 Ultimate here and I've never had an issue. Go to the Device Manager and see what it shows when ADB stops working. Sounds like your USB controllers are taking a ****.
I'm using vista 32 bit. I think I'm haveing a usb conflict.
Sorry for posting in the wrong forum
I have Ultimate x64 and no problems.
I had a problem with the driver that was configured to G1. Maybe..
I have Vista Home Premium x64. On Vista SP1 I had no problems. After upgrading to SP2 the adb will connect once and in Eclipse I can get a few commands through, then it hangs. After that I cannot kill the adb process, nor get any response from an adb command.
When I roll back to SP1 it works again. Though under SP1 it is still not completely stable, however it is always possible to kill the adb process and connect the device again.
Related
Does anyone else have to jump through hoops to get ADB to recognize the Vogue? It seems just like a collosal mess of drivers, which is even worse because different Android builds (2.01 vs 1.5 vs 1.6 vs 2.1) all behave differently.
I'm running Win7 and android via Haret and it is a complete cluster-xxxx of USB drivers. I have the android sdk usb drivers installed, but windows wants to install mass storage and/or usb composite. Then, there is a driver called HTC Dream Composite ADB interface. ADB works for me most of the time when this driver gets installed.
Earlier, I had adb working. Then I accidentally unplugged my usb cable. Plug it back up and I'm back in driver hell.
AARGH! Is this just my problem?
Similar problem
Nope...I've got a similar problem...windows recongnizes my Android ADB device...then when i try to use ADB or ADB explorer...it just won't connect and says their are no devices present. If i leave the hardware screen open...it will put an ! over my device when I try to access it via ADB. Still haven't gotten it to work...gonna try a differnt comp. I'm trying to push the new GPS libs.
are either of you running x64?
No
Windows XP 32 bit.
wasn't it said plenty of times that adb currently doesn't work in windows on nand?
Who said nand? I count one haret and one no comment.
im supposing if it doesn't work in nand, i doubt it would in haret.
I've had ADB working successfully in the past, but now nothing is listed after an "adb devices" command, and a "device not found" error for other commands. I was on Royal Ginger 2, and just updated to the latest CM7 nightly - then wanted to use ADB to tweak a few things and found out something was wrong. What else do I need to do to get adb to recognize my device?
I haven't changed anything on my laptop, which is Win7 64bit, and I've updated everything in SDK Manager. Device Manager on the laptop shows T-Mobile myTouch4g USB Device under Disk drives on the Device Manager, and I believe I have the latest mt4g drivers installed. I'm connecting via USB with debugging turned on, and without turning on USB storage.
Any ideas?
I was finally able to get adb to recognize my device again. FYI, I tried a few different things, but I think what finally got it working was tweaking the *.inf file in the usb_driver folder in SDK, the uninstalling/reinstalling the drivers - as outlined here:
http://forum.xda-developers.com/archive/index.php/t-881324.html
I am having issues with adb getting to work. I have tried every tutorial under the sun. I have uninstalled, reinstalled and stopped windows from automatically updating the driver yet it keeps installing the stupid mass storage driver for it. Any help on this would be greatly appreciated.
Thanks
You didn't mention what version of windows. It is fine for me with XP sp3.
However,if I have virtual box running then I get the driver install dialog.
I am running win7 64 bit I think I might end up trying virtual box with xp on it and if I don't get it then I will be back it seems no one has responded to any of my threads. Any ideas would be great though.
I can't get adb on Ubuntu under virtual box on XP to work. Stop virtual box and adb on XP is fine. Leave virtual box running and adb fails - windows insists on trying to install the virtual box (or other) driver when I connect the NC.
For me, the Nook Color has always be troublesome to get the ADB to connect and work.
I seem to find that the app adbWireless works all the time for me. Instead of trying to connect adb through the USB port which always seems to have driver issues for me, it connects it through the wireless connection. No drivers needed.
bytte said:
I can't get adb on Ubuntu under virtual box on XP to work. Stop virtual box and adb on XP is fine. Leave virtual box running and adb fails - windows insists on trying to install the virtual box (or other) driver when I connect the NC.
Click to expand...
Click to collapse
Hope this help
http://forum.xda-developers.com/showthread.php?t=1329983
Hello folks,
I had a WinXP computer, and I installed android SDK, and I was able to connect to my nook via ADB. As it was aging and having fan problem, I bought a new Dell (i5, win7, 4Gb RAM, 500 Gb HD). I installed android SDK, but never tried to ADB my nook. Yesterday I tried it, and whenever I try to connect via IP, or use adb devices, nothing shows up. I tried messing with the firewall, but it was not working at all.
Does anybody have any idea to help me? And also on how to get my firewall back (removed Norton, which I believe is a bloating spyware, and installed avast antivirus, but firewall was not released either, and it gives a 0x80070424 error).
Try this
Attach the usb cable to the NST and see if it is visible in device manager. Ideally if no driver is installed, you would just see it there with an exclamation mark.
Then follow ros87's instructions here. If adb_usb.ini doesnt exist create it.
Then from device manager, update device drivers for the unrecognized nook and point it to the i386/amd folder within the android drivers folder.
once that is done, restart adb, run "adb usb", then try "adb devices". If it worked it should show you the device.
ADB wifi was easier. In fact, it was such a long time since I last used it (before 1.1.1), that I forgot to add the adbwireless button to turn it on.
But thanks anyway. I've never dared to use USB due to inner messiness of the process.
I can't access my N7 with adb (when booted) or fastboot (while in the bootloader). It's connected via a USB cable. This is both with a Mac and WUGS. Commands like fastboot devices or adb devices return nothing as the device isn't seen. I can connect my N4 and use those commands without problem. I just tried doing the same with my 2013 N7 and it's not being seen, either. Strange. I don't think I've had this problem before on the Mac. I have on Windows, which I can sometimes resolve by installing and reinstalling drivers until something works.
I'd wanted to update the 2012 N7 to Lollipop.
Thoughts, anyone?
maigre said:
I can't access my N7 with adb (when booted) or fastboot (while in the bootloader). It's connected via a USB cable. This is both with a Mac and WUGS. Commands like fastboot devices or adb devices return nothing as the device isn't seen. I can connect my N4 and use those commands without problem. I just tried doing the same with my 2013 N7 and it's not being seen, either. Strange. I don't think I've had this problem before on the Mac. I have on Windows, which I can sometimes resolve by installing and reinstalling drivers until something works.
I'd wanted to update the 2012 N7 to Lollipop.
Thoughts, anyone?
Click to expand...
Click to collapse
Crazy as it sounds, try another USB cable. Reboot everything, plug in fresh, and try again. Failing that, use WUGS to reinstall all your USB drivers. Use the stock Google.
The cable was the culprit. I tried another and it worked. Thanks so much!
I'm having a similar problem that's driving me insane.
Nexus 7 wi-fi version
I've loaded every driver on the planet and in recovery mode it simply will not show up. And I'm not talking won't show up using ADB, I get absolutely nothing in device manager. So before anyone tells me to point to the device and manually change the driver, there is no device to try and point a driver to.
In "normal" mode, it shows up perfectly fine in Device Manager as Android ADB Composite Device. ADB will list it in devices with no problem. It will accept the "adv reboot recovery" command perfectly and reboot the tablet into stock recovery. The minute it does that, the device disappears from the Device Manager list and nothing takes it's place. I've tried to have it search for new hardware, I've tried the Google USB drivers kit, I've used Koush's Universal Driver install. I've used 3 different cables on 2 different USB ports.
This is a completely stock N7 running 4.4.4 plugged into a Windows 8.1 64 bit PC.
The last thing I'm wondering is do I have to unlock the bootloader at all? I don't want to because it'll wipe the tablet. If so I guess I'll just wait out the actual OTA rather than try to sideload it.
Any suggestions would be appreciated.
Yaz75 said:
Any suggestions would be appreciated.
Click to expand...
Click to collapse
Any suggestions at all?
Ummm... does the Stock Recovery actually run "adbd" by default? If it doesn't (or it doesn't start adbd until you execute the sideload menu item), then you wouldn't normally see anything on the other side of the cable with a stock Recovery. (I don't have my tablet with me to check)
Here's an extra "any suggestion at all":
Get rid of Windows and use Linux; there are no drivers to screw with in the latter case.
No, seriously. But probably not what you are thinking.
If you can get a "live CD" to boot** on your PC, you can (as root) run the "lsusb" command to see what devices are enumerated on the USB bus, port by port.
In conjuction with the decoder ring at the end of this post, you can determine from inspection of the USB VID/PID identifiers whether or not all the hardware is behaving, and whether or not the tablet is in the mode you think it is supposed to be in.
The reason this is valuable is that it allows you to take drivers completely off the table; if everything is as it should be, then you know that all the hardware and cabling are functioning correctly, the tablet is behaving correctly, your PC hardware is behaving correctly, and that 100% of the problem is Windows driver issues.
If you want to go the extra 1/4 mile, you can put a copy of (Linux) fastboot & adb plus your flashables on a USB key, and run adb or fastboot from the Live CD boot. It won't matter that the live CD doesn't have them preinstalled, they will be on your USB key. It will be easier on you if you can find statically-linked fastboot and adb binaries; if not you will have to copy one or two supporting shared libs (.so files) along with the binaries, and find out what LD_LIBRARY_PATH is all about.
suppose the USB key mounts at /media/usb1; then
$ sudo /bin/bash
# mkdir /tmp/tools
# cp /media/usb1/fastboot /media/usb1/adb /media/usb1/*.so /tmp/tools/
# chmod 755 /tmp/tools/*
# export LD_LIBRARY_PATH='/lib:/usr/lib:/tmp/tools:.'
# cd /tmp/tools
# ./fastboot devices
OR
# ./adb devices
Good luck; as you are using Windows you are going to need it. Hahaha LOL
**depending on whether your BIOS on your win 8.x PC can be toggled between UEFI and Legacy modes or not, this can be either trivial (Legacy boot mode) or complicated (UEFI) requiring a "Trusted Computing" crypto boot shim from MisterSoftie.
Ok this works for me
Use USBDeview (http://www.nirsoft.net/utils/usb_devices_view.html)
delete all the associated drivers like Google, Samsung, etc for ADB, etc
Restart Computer
Reconnect N7 without MTP and USB debugging
Wait for PC to recognise device and install driver
*If you see something like PC unable to recognise device, go into device and Update Driver and choose "Automatic....."
Disconnect and Reconnect with MTP and USB Debugging
Wait for PC to recognise device and install driver
Restart N7 in bootloader
Wait for PC to recognise device and install driver
Profit
* My PC OS is Win 8.1 Pro 64bit
make sure mtp is switched off, i couldnt get adb or fastboot on my nexus just now . switched off mtp and works fine