this driver problem is driving me crazy. it's the same story in XP as well.
i think it stems from the fact i've messed around with so many different drivers that my 7x64 and XP machines just don't know what to install anymore.
it has worked in the past. first time i rooted this phone i had to mess around with win7 drivers (to the point of almost giving up) to get windows to recognise the device at each stage of the root. this was done using a combination of HTCSync 2.0.33 and PDAnet's drivers.
since then i've had to flash to stock for an RMA, then went through the whole nightmare process again a second time. i mistakenly assumed that it would be easy the second time..
I've just accidentally flashed back to stock again, and this time it doesn't matter what i do, i just can't get these f*****g drivers working! same story on XP (which has also had numerous drivers installed over and over again).
i've even taken the phone apart to check nothing's damaged and tried a different usb cable, and un/modded google drivers.
one thing i noticed is that after rooted and flashing cymod, the previously working drivers no longer detect my phone.
has anyone had a similar experience?
Related
possibly silly question, seeing everyone is saying the rooting problem is something different(drivers(htc/pdanet/android sdk), sdcard, computer(OS)). you guys that have gotten ADB to successfully get the phone recognized in recovery mode:
Did the phone show up in the device manager for windows?
i feel like windows has to register the phone under a certain driver in order for ADB to pick it up(otherwise the OS doesn't recognize it like any other piece of hardware). maybe part of the problem is some people don't have a recovery driver?
just throwing it out there since I have tried every method on the forum except using the original sdcard that came with the phone(it's my my gf's phone at the moment and i haven't been able to get it from her)
also, does anyone know what eugene's setup is? OS, drivers, sdk version? or eugene if you see this, it would be wonderful if you could chime in.
Im in the process of trying to root my buddy's phone after successfully rooting mine, and this was the same thing I was thinking. Using USBDeview, there is a device in recovery mode called "Android 1.0".
When my phone is connected, it says "Connected: Yes" on that device, however when his is plugged in it won't recognize it.
I kept thinking it had to do with drivers too... but I'm not sure where to go with it now...
chrisinaz said:
Im in the process of trying to root my buddy's phone after successfully rooting mine, and this was the same thing I was thinking. Using USBDeview, there is a device in recovery mode called "Android 1.0".
When my phone is connected, it says "Connected: Yes" on that device, however when his is plugged in it won't recognize it.
I kept thinking it had to do with drivers too... but I'm not sure where to go with it now...
Click to expand...
Click to collapse
What OS are you using? 32 or 64 bit? Do you have HTC Sync installed?
i've used winxp pro 32bit, win7 pro 64bit, win7 ultimate 64bit. i tried the htc drivers, the pdanet drivers and the sdk drivers. i just made a ubuntu boot drive, i think im going to try that later tonight.
and i think chrisinaz is trying to root his friends phone on the same computer he did his on if i'm not mistaken.
Using xp 32 bit and fedora 13. Neither work for his, both work for mine.
-------------------------------------
Sent via the XDA Tapatalk App
chrisinaz said:
Im in the process of trying to root my buddy's phone after successfully rooting mine, and this was the same thing I was thinking. Using USBDeview, there is a device in recovery mode called "Android 1.0".
When my phone is connected, it says "Connected: Yes" on that device, however when his is plugged in it won't recognize it.
I kept thinking it had to do with drivers too... but I'm not sure where to go with it now...
Click to expand...
Click to collapse
Where it says android 1.0 this is the driver that you need to update. I used the PDANet driver to update it.
Hello Guys...GretoVerno here fellow Samsung Galaxy S Vibrant Owner...
I have this phone and everytime i connect it to usb i Get the Message
"USB Device Not Recognized" error message...I have installed all the drivers i could possible find on the internet and the error still pops up...i ahve tried using the phone in USB Debugging mode to no avail what so ever...
Someone Please help if there's a genius out there...I really love this phone
Uninstall the Samsung drivers off your computer. Then reinstall make sure that have the correct version windows 32 bit or 64 bit for the correct operating format. Make sure you give admin rights to it. you can find these drivers in the Noob bible by S15274N in the Gen section. I am assuming there is not a problem with your phone. If you have a friend, check it on their computer, that's an easy way to rule out phone issues. That should resolve what ever problem you have.
There ia another way to check, that is have a friend with odin (or you) and see if Odin recognizes, if it does, then you got it solved or at the very least Odin back to stock and reinstall a new rom, this will solve all these issues as well.
Hope you get it, good luck
Had an issue with my brother in laws comp not recognizing his vibrant. Took an hour or two to get his phone recognized. I think we ended up using the drivers from pdanet instead of the official danny drivers. First try getting your phone to work on another comp. Will help narrow down the issue by 50%
Sent from my SGH-T959 using XDA App
Windows cannot recognize my vibrant!
Hopefully someone can help me out as I am having the
same problem with my computer not recognizing my phone.
The thing is that I am already running Froyo stock 2.2
and at the time I was able to update it to 2.2 my
computer recognized my phone without a problem. I have
been reading the forums for a while now and the only
time anyone had this problem was when they first bought
the phone when it was released but here is my problem.
After updating Kies mini and installing the official
Samsung drivers from the Samsung website I plug in the
phone and i get the error that windows does not
recognize the device. I have tried this on Windows Xp
and Windows 7 on 2 different laptops and got the same
error everytime. So what I did was while on Windows Xp I
uninstalled the unknown driver and I kept plugging and
unplugging the phone and uninstalling the unknown driver
until I got my computer to finally recognize my phone.
Once my computer recognized my phone I Then started
downloading the recent update, when the download was
done as soon as my phone went into download mode my
computer kicked out my phone and gave me the error that
windows does not recognize the device and at that time
Kies mini gave me the emergency recovery notice which I
didnt have to use because the phone booted fine without
fail.
You should also know that prior to the recent
update from tmobile for minor bug fixes I tried to root
my vibrant using the superoneclick root program. Upon
doing this after fighting with my vibrant and my laptop
to communicate with each other my computer recognized
the phone and I attempted to root. Then I got the
looping message and at that time windows did not
recognize my device which then messed up my modem and I
had to do a system restore. So after weeks of fustration
trying to root and now not able to downlaod the recent
update I am now asking for your help as XDA has been
there for us all. I have tried samsung drivers, kies mini
drivers and pdanet drivers and get the same windows
doesn't recognize my device everytime. Does anyone have
any ideas as what I can do to get my computer to
recognize my phone as I can not do anything until my
computer and my vibrant get along. Your help is greatly
appreciated XDA thanks for all that you do!
do you guys have Samsung kies installd??
Sent from my SGH-T959 using XDA App
I do and its been updated for the new update for thee recent bug fixes.
can you try a different USB chord?
Sent from my SGH-T959 using XDA App
You know that's the only thing that I haven't tried should I pick one up from T-Mobile or were should I get one?
I am getting the same error and i tried a buddy's cord and it still did the same thing. Not really sure what happened. My phone was working fine just a few days ago. I am wondering if it has anything to do with the large amount of Windows Updates that just happened.
Try uninstalling your drivers and install these. I had the same problem and then I used this and it has worked on every computer. Heck even worked when I hooked up my SGS2
http://www.multiupload.com/FUL878MTJH
I had the same issue. It is a phone problem and I had to get a warranty replacement. No combo of cables or drivers would fix mine.
Well after uninstalling and reinstalling, trying new drivers, restarting countless number of times, troubleshooting through the device manager, I had the genius idea to restart my phone in a last ditch effort before i gave up and it worked.
Now i feel somewhat like a dodo. Rule #1 - Restart
GretoVerno said:
Hello Guys...GretoVerno here fellow Samsung Galaxy S Vibrant Owner...
I have this phone and everytime i connect it to usb i Get the Message
"USB Device Not Recognized" error message...I have installed all the drivers i could possible find on the internet and the error still pops up...i ahve tried using the phone in USB Debugging mode to no avail what so ever...
Someone Please help if there's a genius out there...I really love this phone
Click to expand...
Click to collapse
Have you rebooted since you installed the drivers?
Well I tried those drivers from that link you provided and no dice. Im going to pick up a new usb cord from Tmobile tomorrow and see if that might be the problem. I can always use a 2nd cord for charging I guess.
djrysk said:
Well I tried those drivers from that link you provided and no dice. Im going to pick up a new usb cord from Tmobile tomorrow and see if that might be the problem. I can always use a 2nd cord for charging I guess.
Click to expand...
Click to collapse
That would be the logical next step.. just to verify, you have restarted the phone and computer since installing the drivers right? If you have then its most likely the cord. Its weird these cords seem to have been giving me problems more than any previously owned ones ie regular usb or even my amp cord which I step on and rip out the amp more than i'd like to admit
Sent from my SGH-T959 using XDA Premium App
Makes sure that when you uninstall your drivers to restart your PC then reinstall and give a shot. Of course, also make sure you are using the right 64x or 86x driver.
madguitarist63 said:
Try uninstalling your drivers and install these. I had the same problem and then I used this and it has worked on every computer. Heck even worked when I hooked up my SGS2
http://www.multiupload.com/FUL878MTJH
Click to expand...
Click to collapse
omg thank you! I was having the same problem! /me bows to madguitarist63 :victory:
Hi guys,
I want to go back to stock since 4.4 is coming. However, when I try to flash the stock rom+ with Nexus Root Toolkit 1.7.3, I get stuck at the whole fastboot part. Fastboot IS working on my Nexus, but the drivers cause a lot of trouble. Installing the drivers when my device is running normally ( so no fastboot mode or whatsoever) works fine.
I have followed the Full driver installation guide where I tried options 1 till 4 but they all get stuck at the point where my device reboots into fastboot mode. At this point, my computer doesn't recognize my device and gives me an error. My nexus is shown in the device manager as unknown device and updating the drivers manually by redirecting my computer to the NRT drivers does not work. It says it cannot find drivers for the device. Does anyone know what I might have done wrong?
Or is it possible to flash a stock rom through twrp? like this one? http://forum.xda-developers.com/showthread.php?t=2376881
TL;DR: use a machine with Windows 7 installed. Or boot ubuntu from a usb stick.
I've researched a lot about this, I had to downgrade my dad's phone with Flashtool (for Xperias), and after trying about every tutorial I encountered (removing drivers, installing different drivers, changing ports, disabling driver signature verification in Windows, I installed android studio, adb separately, running everything in administrator mode), I remembered I have a W7 machine on the other desk, it worked like a charm.
W8 (or 8.1, it's the same thing) is bad for flashing, I don't know when they're going to fix it.
issak42 said:
TL;DR: use a machine with Windows 7 installed. Or boot ubuntu from a usb stick.
I've researched a lot about this, I had to downgrade my dad's phone with Flashtool (for Xperias), and after trying about every tutorial I encountered (removing drivers, installing different drivers, changing ports, disabling driver signature verification in Windows, I installed android studio, adb separately, running everything in administrator mode), I remembered I have a W7 machine on the other desk, it worked like a charm.
W8 (or 8.1, it's the same thing) is bad for flashing, I don't know when they're going to fix it.
Click to expand...
Click to collapse
Yeah, I tried the same things you did, including disabling driver signature verification but it won't work. I'll try a windows 7 machine.
Thanks for your answer!
My problem is basically getting my nexus 7 to connect to the pc... This is what I've done. and what happends...
When I first connected it, I got no message at all, and nothing happened, then I changed the cables around, I changed the USB Pports... and by some mysterious wounder I found a combo of pad, port and cable that made my nexus go your connected as MEdia Device... BUT my computer wont see it.. hmm.. changed it to camera mode, and still nothing. Then I turned off USB Debug. Still nothing, but wen I turned it back on, I got the message that I was connected, and I got to install some drivers, and NExus popped up as a camera in windows 8... Started up the nexus toolkit thingy (I love simplicity) And there it popped up.. rebooted to fastboot, and no luck... windows wont recognize the damn driver. And I have done everything I can think of except install linux and try it there... IT wont connect in Fastboot mode, Not a chance... I've tried to unindatll all the drivers, and their files. everything I can think of... I've followed like 20 diffrendt howto s on the same problem, and no luck...
So how would a guy like me go about doing this in linux... is there a tool made for it? Do I need to do it all by commands? Is there a howto?
In my win8 64bit the nexus 7(2012) does show up as a portable device, but MTP works and there's no issue with sending or pulling files. currently it's running stock kitkat 4.4 (KRT16S).
like you I suspect it's a driver issue with windows. If you could locate the device on device manager (try View\Devices by connection and look under PCI Express Root Complex and comb for USB Host Controller\USB Root Hub\Generic USB Hub), delete the entry for Nexus7 and scan for hardware changes again. This forces the system to look for correct driver(s) for your nexus.
Some guides on updating drivers are in fact concerned with the ADB interface, which is needed for USB debugging. In your case, if it's just accessing the internal storage of your Nexus you want to solve, those info may not be relevant.
krrasmuss said:
My problem is basically getting my nexus 7 to connect to the pc... This is what I've done. and what happends...
When I first connected it, I got no message at all, and nothing happened, then I changed the cables around, I changed the USB Pports... and by some mysterious wounder I found a combo of pad, port and cable that made my nexus go your connected as MEdia Device... BUT my computer wont see it.. hmm.. changed it to camera mode, and still nothing. Then I turned off USB Debug. Still nothing, but wen I turned it back on, I got the message that I was connected, and I got to install some drivers, and NExus popped up as a camera in windows 8... Started up the nexus toolkit thingy (I love simplicity) And there it popped up.. rebooted to fastboot, and no luck... windows wont recognize the damn driver. And I have done everything I can think of except install linux and try it there... IT wont connect in Fastboot mode, Not a chance... I've tried to unindatll all the drivers, and their files. everything I can think of... I've followed like 20 diffrendt howto s on the same problem, and no luck...
So how would a guy like me go about doing this in linux... is there a tool made for it? Do I need to do it all by commands? Is there a howto?
Click to expand...
Click to collapse
Installing fresh SDK won't hurt.
holynoob said:
Installing fresh SDK won't hurt.
Click to expand...
Click to collapse
The USB drivers are available in a zip file here: http://developer.android.com/sdk/win-usb.html
and instructions are here:http://developer.android.com/tools/extras/oem-usb.html#InstallingDriver
For drivers and devices on your system browse http://www.nirsoft.net/ for the free utilities
DriverView
USBLogView
DevManView
USBDeView
Update
peterk-1 said:
The USB drivers are available in a zip file here: http://developer.android.com/sdk/win-usb.html
and instructions are here:http://developer.android.com/tools/extras/oem-usb.html#InstallingDriver
For drivers and devices on your system browse http://www.nirsoft.net/ for the free utilities
DriverView
USBLogView
DevManView
USBDeView
Click to expand...
Click to collapse
Basically I would like to have ¤.¤ installed on my Tablet. Right now I have 4.2.2 SmoothROM installed, and whilst this works for me, I'd like to get the update.
In the past, I used the Toolkit to root and install stuffies... Until the last update to SmoothROM wheres I used GooManager thingy...
When I started this I got the Tablets to connect using PTP whilest in Android, but not in Fastboot mode. So I downloaded the 4.4.kitkat Offisial ROM and tried to install that in recovery, after a full wipe, BUT that ended in me having to install SmoothROM again. And now the Tablet wont connect at all... I have deleted all drives, and reinstalled them... I've tried 3 diffrent Wondows USB driver, but no luck there... I've tried like 5 diffrent USB data cables, in all 4 of my USB ports, on 2 diffrent machines, both win 7 and win 8... AND still no luck... now all the machine says that it cannot identfy the device...
Tomorrow, I will end up installing linux, and try there... At the moment I loathe all things called windows drivers...!!!!
EDIT:
Great news... I found a cable, I havent used in a long time. THis is the original cable that came with the Nexus, and I havent used it in a long time because it had some bad connections. Felt like the plug was loose, but now it made the whole thing work without any problems at all...
So I found the cable, used USBDeView to delete all drivers assossiated with the nexus. plugged it in while in fastboot, and BANG installed. rebooted it, and BANG installed.
I know what your thinking another newb not installing drivers properly or hasn't changed to file transfer mode.... This is not the case. I been installing adb and USB drivers since the og droid.
I have a real problem here....
I been on custom ROMs and wanted to fastboot back to stock however none of my computers are detecting my phone... Tried on 2 windows 10 x64 and one windows 7 x64 with same result. None even pop up a notification or ding a sound that the phone has been plugged into it. Nothing in device manager either. The phone charges at least I have also tried 4 different cables granted 3 came in a bundle pack that I do not trust but reviews state although not full speed they should do data....
Now here is the kicker:
If I turn off my phone and boot to the bootloader my 3 computers detect a device has been connected but the drivers fail and say something about the device signature can't be recognized. I have tried disabling the device signature validation in windows 10 with no luck and also windows 7....
Tried manually installing the drivers but says not compatible with device hardware
At this point I'm baffled luckily I'm rooted twrp and can download files to install directly but I rely heavily on fastboot as my goto if something goes wrong I'll be hosed!
I did factory reset and even flashed another custom rom to see if it was the ROM I was using.
Please help if you have any ideas to try. I have yet another cord coming Friday just in case the offchanse the main went bad and the other three from the bundle pack are ****
Sending back to google I hope they don't mind the custom rom, unlocked bootloader and twrp recovery lol