[Q] ADB device not found - One (M7) Q&A, Help & Troubleshooting

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

Related

Windows 7 G1 Drivers

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.

[Drivers] MS Windows x86 and x64 USB Drivers for Samsung Galaxy S

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.

Windows 8 drivers

I am running Windows 8 at work to test some compatibility with a few applications we use. I'm having difficulty getting drivers for my i9000 though. I've tried the 1.5.5.0 for Windows 7 drivers, as well as 1.5.9.0 that I found elsewhere on the forum, meant for Windows 8, but the device shows up as i9000-GT in error state in device manager. I even installed the latest version of Kies hoping it would pick up some drivers.I can mount the storage fine, but I cannot ADB to the phone (nothing listed with adb devices).
I know there are probably very few people running Windows 8, but does anyone have any ideas?
Kops said:
I am running Windows 8 at work to test some compatibility with a few applications we use. I'm having difficulty getting drivers for my i9000 though. I've tried the 1.5.5.0 for Windows 7 drivers, as well as 1.5.9.0 that I found elsewhere on the forum, meant for Windows 8, but the device shows up as i9000-GT in error state in device manager. I even installed the latest version of Kies hoping it would pick up some drivers.I can mount the storage fine, but I cannot ADB to the phone (nothing listed with adb devices).
I know there are probably very few people running Windows 8, but does anyone have any ideas?
Click to expand...
Click to collapse
Try downloading the android sdk..might help...there is a usb drive that could solve your issue.
erpurohit said:
Try downloading the android sdk..might help...there is a usb drive that could solve your issue.
Click to expand...
Click to collapse
I do have the SDK downloaded, installed, and updated. Is there a generic driver in there somewhere?
Kops said:
I do have the SDK downloaded, installed, and updated. Is there a generic driver in there somewhere?
Click to expand...
Click to collapse
yes there is a usb driver...
Kops said:
but I cannot ADB to the phone (nothing listed with adb devices)?
Click to expand...
Click to collapse
you can download drivers from My Android Collections and or a solution for USB connection problems from My Android Solutions
Kies on windows 8 did the trick for me, it's strange your phone isn't detected that way. Are you using a x86 or a 64bits version ?

ADB on Windows 8

Some time ago, I went from stock Amazon OS to Chameleon OS. After that, I lost ADB connection on my family's laptop running Windows 7. Now I'm running CM10.2, and I'm trying to figure out how to enable ADB on my Windows 8 laptop. For a while I could do it over Wi-Fi using ADB Wireless, but now it's having issues. Is there anyway to get ADB over USB on Windows 8?
Ph0enix_216 said:
Some time ago, I went from stock Amazon OS to Chameleon OS. After that, I lost ADB connection on my family's laptop running Windows 7. Now I'm running CM10.2, and I'm trying to figure out how to enable ADB on my Windows 8 laptop. For a while I could do it over Wi-Fi using ADB Wireless, but now it's having issues. Is there anyway to get ADB over USB on Windows 8?
Click to expand...
Click to collapse
You'll want to read the OP and the second post from OP. They are both pertinent http://forum.xda-developers.com/showthread.php?t=1583801 Good ole windows and their signed drivers...
Edit - Stunts ADB drivers here just in case http://forum.xda-developers.com/showthread.php?t=2477379
LinearEquation said:
You'll want to read the OP and the second post from OP. They are both pertinent http://forum.xda-developers.com/showthread.php?t=1583801 Good ole windows and their signed drivers...
Edit - Stunts ADB drivers here just in case http://forum.xda-developers.com/showthread.php?t=2477379
Click to expand...
Click to collapse
Thanks! The thread you linked me to didn't work for me. I did disable driver signature enforcement though, something I've been meaning to do for a while. I ended up just using stunt's ADB drivers. They work when I'm in the root of the folder where I keep them, but if I add the folder to the PATH statement, it acts like I'm using the old ADB drivers. :silly:
Oh well. Again, thanks!

[Q] HTC vivid AT&T drivers not recognised

My vivid mobile when it is connected in fastboot mode , drivers are not recognised. I need to root my mobile
Is it recognized when not in fastboot? What os are you using, and so you run into the save issue on a different PC?
Sent from my Vivid 4G using XDA Free mobile app
projectisaac said:
Is it recognized when not in fastboot? What os are you using, and so you run into the save issue on a different PC?
Sent from my Vivid 4G using XDA Free mobile app
Click to expand...
Click to collapse
It is recognized when the phone is ON. I'm using windows 8.1 64bit OS.
when it is connected in fast boot mode my OS does not detect drivers for it
It is recognized when the phone is ON. I'm using windows 8.1 64bit OS.
when it is connected in fast boot mode my OS does not detect drivers for it
saiviru said:
It is recognized when the phone is ON. I'm using windows 8.1 64bit OS.
when it is connected in fast boot mode my OS does not detect drivers for it
Click to expand...
Click to collapse
Hmmm.... I'll have to test this with my girlfriends comp first, as I'm using win7x64 myself.
Sent from my Vivid 4G using XDA Free mobile app
test as fast as you can .I want to root my mobile
fastboot doesn't work on windows 8.1
using a virtual machine also doesn't work as the vm reads the host system's usb
you'll have to find a different machine to use fastboot
or you could try using a linux live cd (but i haven't done this myself, so i don't know if it works)
stuffed_tiger said:
fastboot doesn't work on windows 8.1
using a virtual machine also doesn't work as the vm reads the host system's usb
you'll have to find a different machine to use fastboot
or you could try using a linux live cd (but i haven't done this myself, so i don't know if it works)
Click to expand...
Click to collapse
I just saw this post today.
adb, fastboot works on my windows 8.1 64 bit machine though.
Win 8.1 has command prompt program. You have to run that command prompt "run as administrator".
sway8966 said:
I just saw this post today.
adb, fastboot works on my windows 8.1 64 bit machine though.
Win 8.1 has command prompt program. You have to run that command prompt "run as administrator".
Click to expand...
Click to collapse
Everything works fine but when I give fastboot command in cmd it says waiting for device and it never detects my device.
and in the windows notification area it shows USB device not recognised.
please help me
saiviru said:
Everything works fine but when I give fastboot command in cmd it says waiting for device and it never detects my device.
and in the windows notification area it shows USB device not recognised.
please help me
Click to expand...
Click to collapse
In the development settings... Make sure that you've granted root to adb and try again...
Sent from my Vivid 4G using Tapatalk
any solution yet?
saiviru said:
Everything works fine but when I give fastboot command in cmd it says waiting for device and it never detects my device.
and in the windows notification area it shows USB device not recognised.
please help me
Click to expand...
Click to collapse
same problem here... wondering if you could solve your problem...
I guess I wasn't clear enough.
Windows 8.1 doesn't load the driver for the Vivid while it is in fastboot mode because of a change in the way Windows handles USB devices. ADB and fastboot may work on Windows 8.1, but you'll never be able to "fastboot flash" anything because the device isn't recognized while the phone is in fastboot mode. It is not a phone driver problem, it is a USB controller driver problem.
Also, like I said before, you can't use a virtual machine becuase the the vm reads from the host system's usb.
You will have to use an operating system other than Windows 8.1 to do any fastboot flashing.
Trust me, I've dealt with this problem since 8.1 was released.

Categories

Resources