I do "adb devices" and nothing shows up anymore... Running Windows 7, running "cmd" in Run As Administrator. Phone USB Ddebugging is on.
Any help would be appreciated. Thanks you.
are you mounted?
I tried both mounted and unmounted...
I had this problem on Windows 7 64bit as well. I have a laptop running Win 7 64 and it's never had the issue. I used my laptop to use ADB for a while but I ended up reinstalling W7 on my desktop (for an unrelated reason), which somehow solved the problem. I think it's probably a driver thing.
Yup, it's a driver thing, happened to me on both Win XP and Win 7. Just re download the newest drivers and install.
...............nvrmnd............
It happens randomly to me too, but I'm on Win XP. Sometimes killing the adb.exe process and restarting it works. Other times I have to reboot my desktop to clear it up (without having to reload the driver).
Related
Any chance anyone knows where to find some or has made any drivers for the G1 and win 7?
what do you mean? the G1 works perfectly fine with windows 7. Using the old drivers i used with Vista.
Vista drivers worked fine with me on the Windows 7 RC, have not tried on the final yet cause I dont have it
android 1.5r3 drivers confirmed working on win7 7600 x86 & x64.
Yesterday I connected my G1 to my Win 7 Pro laptop and after updating the driver, yes, the old driver from Vista worked (dunno why at first Win 7 didn't see it).
One issue I ran into that renders my laptop useless for working with my G1 though is that the Command Prompt launches and closes immediately. Asides from that, it sees the G1 as an ADB device with the proper driver.
xyrcncp said:
One issue I ran into that renders my laptop useless for working with my G1 though is that the Command Prompt launches and closes immediately. Asides from that, it sees the G1 as an ADB device with the proper driver.
Click to expand...
Click to collapse
That's no fun, does it still do that if you: Winkey+r, type "cmd" + enter ?
AdamPI said:
That's no fun, does it still do that if you: Winkey+r, type "cmd" + enter ?
Click to expand...
Click to collapse
Don't have the laptop with me right now, but I'll give it a shot.
SDK 1.5r3 works perfectly for me on windows 7. Just make sure you run command prompt as administrator
Of course, I don't set my personal machines as anything else other than Admin.
The Winkey + r, cmd, enter worked just fine. Stupid Start menu...
Thanks guys.
I have been useing Windows 7 and the G1 for around a month now with no problems, i didnt have to update any drivers, just plugged it in and it worked. Unless your talking about the Android ADB sdk tools. then read above.
Yeah it works Fine now.. It ended up being an issue with the usb port driver.
Team,
For those of you having trouble finding drivers here are some links.
64bit:
http://drivers.softpedia.com/get/MOBILES/Samsung/Samsung-Galaxy-S-USB-Driver-for-Windows-x64.shtml
32bit:
http://drivers.softpedia.com/get/MOBILES/Samsung/Samsung-Galaxy-S-USB-Driver-for-Windows-x86.shtml
For Linux and Mac the Android SDK drivers should work fine.
The standard Samsung USB driver that PDAnet had listed for the Samsung Moment worked for me as well, will give these new ones a try on my other system.
thank you
I added a link to this thread in the sticky
EDIT: Nevermind the n00b question. I was able to get the drivers installed and I am good to go.
cant get my cpu to recognize my phone after installing drivers... im on windows 7 64 bit any ideas??
skater4690 said:
cant get my cpu to recognize my phone after installing drivers... im on windows 7 64 bit any ideas??
Click to expand...
Click to collapse
have the same problem. i'm on 7, 32bit
did you enable USB debugging?
Gunnman from Galaxy S
yes of course. first thing I did after I rooted
I'm drunk so bear with me. go into device manager and browse for the driver manually ,include subdir. point to programfiles\samsung.
if that don't work use the 64bit drivers on 32bit windows. don't run setup just browse to the extracted dir from the unknown device in device manager. it worked for me at work. good night
Gunnman from Galaxy S
since i had issues w/ the 32bit driver exe, i extracted it and zipped it up incase others have the same issue.
http://rapidshare.com/files/408470448/Samsung_Usb_Drivers_x32.zip
this thread should be stickied since W7 doesn't come with the drivers, it seems.
How exactly do you update the drivers with win7? It keeps saying my drivers are up to date but I still can't get adb to recognize my vibrant
Beast84 said:
How exactly do you update the drivers with win7? It keeps saying my drivers are up to date but I still can't get adb to recognize my vibrant
Click to expand...
Click to collapse
Anyone?? I can't get get adb to recognize my device for the life of me
Try both 32bit and 64 bit drivers. At work I have 32bit win7 and the 64bit drivers fixed it up. Dont run setup just go through device manager chosse the unknown device and point it to the 64bit driver directory and check include sundirs.
Try using correct drivers for your win version but turn the phone off, connect and then power up while connected....worked fine for me after messing with both lots of drivers first and no luck
Make sure you select "USB debugging" for ADB to work folks.
Where can I get the mac driver..i looked everywhere please help
this thread is legit!
thanks for all of your help so far guys.. BUT i still cannot get my laptop to sync up with the phone properly (win xp pro, sp3)...
I've downloaded and installed both drivers and the computer is recognizing the external drives, but they are showing as removable disks E: and F:. when i double click to open, it is telling me to insert a disk? i feel like i'm almost there, but there is somethign i'm missing!
usb is mounted and usb storage is off. usb debugging enabled.
any help would be appreciated.
Windows drivers issue
Have you tried mounting the drives. Same thing happened to me when you have it connected to the computer drop down the usb notification and mount. The your drives should be accessible.
Just made the switch from ubuntu 10.10 to windows 7, didnt have issues using my cappy as a mass storage device on ubuntu
On win7 x64 if I try to transfer a file thats just more than a few mb's either from the cappy to the pc or vice versa, the transfer just gets stuck, the loading bar is flashing but it doesnt get anywhere. I have to unplug my phone from the computer in order for it to go away, this causes windows explorer(not the internet browser) to restart as well.
-my other usb devices work without a problem
-have tried all six usb ports on my computer, same thing
-even weirder, i reformatted, installed win7 x86 just to see, transfers work fine on it. Reformatted again and installed x64 with fingers crossed, transfers didnt work on it again.
-I have tried transferring files with no windows updates installed on x64 as well as all updates installed, file transfers still get stuck both ways.
-im using the x64 captivate drivers from the odin3 thread on xda. running andromeda3 ROM.
anyone know what this could possibly be?
JBLogic said:
Just made the switch from ubuntu 10.10 to windows 7, didnt have issues using my cappy as a mass storage device on ubuntu
On win7 x64 if I try to transfer a file thats just more than a few mb's either from the cappy to the pc or vice versa, the transfer just gets stuck, the loading bar is flashing but it doesnt get anywhere. I have to unplug my phone from the computer in order for it to go away, this causes windows explorer(not the internet browser) to restart as well.
-my other usb devices work without a problem
-have tried all six usb ports on my computer, same thing
-even weirder, i reformatted, installed win7 x86 just to see, transfers work fine on it. Reformatted again and installed x64 with fingers crossed, transfers didnt work on it again.
-I have tried transferring files with no windows updates installed on x64 as well as all updates installed, file transfers still get stuck both ways.
-im using the x64 captivate drivers from the odin3 thread on xda. running andromeda3 ROM.
anyone know what this could possibly be?
Click to expand...
Click to collapse
sounds like bad drivers from samsung or windows is not using the newest driver version, maybe downloading drivers from samsung and manually installing would help
32 bit version of windows will have different drivers
I installed .net 4 and that seems to have fixed my problem, if that makes any sense.
makes sense. i keep forgetting about that but it is something you should have for alot of things in windows, thought it was one of the required things for adb and odin as well. not sure though
JBLogic said:
Just made the switch from ubuntu 10.10 to windows 7
Click to expand...
Click to collapse
I'm lucky enough to have a roomate with a dual boot ubuntu/windows so I can keep my Ubuntu and borrow his windows machine when I need it. Definately sounds like driver/ .net 4 issues though.
Keep getting this message in Command Prompt when trying to install CM9 on my touchpad.
Yes I have cd to the right directory in command prompt
Yes it does show up in Device manager as Palm Novacom (bootie) under the tab Palm Novacom Modules.
Yes drivers are installed
Yes I did re install all drivers after removing them.
Tried different USB cables
Will not show up in Adb either.
My computer does recognize it, in both WebOS Recovery mode, and in Mass storage mode.
What does this message mean? Am I missing something?
Appreciate any help.
Thank you.
Edit: Solved!
Thanks to Scifan on IRC for his help!
I've got the same exact issue... i have a feeling it has something to do with win 7 64bit, im seeing alot of people with the same issue with that setup.
Reinstall novacom using this this installer
http://universal-novacom-installer.googlecode.com/files/UniversalNovacomInstaller.jar
Than in your type this (services.msc) in your windows start bar. Look for Palm Novacom in the services.
If its not there, try installing novacom drivers again while looking at the services menu. It worked for me like that, not sure why. But this was my problem.
I had reinstalled novecom drivers a few times trying to get it to work, and that some how did the trick for me. Was pretty weird.
My net book is running windows 7 32bit. Dont know if 64bit is going to have problems as I cannot test.
Good luck!
My ADB is not working... So basically I messed up my HTC ONE by formatting the whole device including system... I'm not sure what to do now. My ADB isn't working. Ive updated the ADB drivers, and updated SDK for Google. My device is not detected by my computer. When i'm in fastboot mode my phone is detected. Is there any other way of pushing a file to my device?
exactly where im at, my windows 8 cant detect but my windows 7 can detect once i move the thing down to fastboot. Shows "Android 1.0"
sasaphrazz said:
exactly where im at, my windows 8 cant detect but my windows 7 can detect once i move the thing down to fastboot. Shows "Android 1.0"
Click to expand...
Click to collapse
I dunno cause I'm on Windows 8.1... I was on Windows 7 but upgraded due to a feature for my gfx card being limited on Windows 7... Havent got ADB working on my Mac either.
PeterZhao478 said:
I dunno cause I'm on Windows 8.1... I was on Windows 7 but upgraded due to a feature for my gfx card being limited on Windows 7... Havent got ADB working on my Mac either.
Click to expand...
Click to collapse
try this, im currently sideloading a rom on my phone right now: http://forum.xda-developers.com/showthread.php?t=2139767