I just got my Gtab today and can already find things I just cant live with so im trying to prep for a new ROM when there are some stable ones out there.
I have downloaded everything from the CWM recovery and root threads but i cant seem to get a driver to work... I have tried section #2 multiple times over on both XP pro x86 & Win7 pro x64 but i end up with the same 3 unknown devices on both *neither have SDK*. When i try to install the unknown USB device with the drivers supplied in nvflash it cant find anything suitable *even pointing to sub-directories*. I downloaded the drivers mentioned in the rooting thread and installed those, I went back to the DM and tried every single directory in the newly unpacked location "C:\Program Files\Samsung\etc.." which had quite a few different ones but i havent gotten anywhere.
I remember this being almost identical to the problems i had trying to root my phone so I finally found linux directions and worked from my mac. Does anyone have a clue whats going on and how to get MS FAIL OS to work?
I guess im the only person having this problem... ohh joy another android that is going to be a pain in the as to root
on your computer, uninstall ALL the samsung drivers (for any previous samsung device/phone). Then connect the tab to your computer and let it search on its own. on your tab the usb debugging should be turned off.
I think the tab is designed to let windows recognize it as usb, but if you have any previous drivers they get into the way.
Related
Hello
I have a stock Vodaphone Magic and I'm looking to root it, but to do this I need to get adb to see it, which I'm having problems with.
When I plugged it in first to charge it used window's default drivers for the SD card etc. Trying to update the drivers with the ones included in the SDK dosn't seem to work as Windows says that they're less recent.
Also, I can't see any sort of "ADB" section in the device manager, even with USB debugging turned on in the phone.
Any help? I'd really like to root my phone so I can use WPA Enterprise!
Edit: Already read the wiki page, no help.
I remember having this problem when I first set up the Android SDK.
However in my device manager I did have a device, it wasn't called Android or Magic or anything similar. From what I remember it was a bunch of random letters and numbers.
From there I right clicked it, went to Properties, Update Driver and then pointed it to the directory with the drivers.
Thats how I did it in Windows 7, if that doesn't work for you then I'm not sure sorry.
Hi,
I recently had the same problem as you. The first time you plug in your phone sometimes Windows will assign USB drivers to the device instead of the ADB interface. To correct this, I uninstalled the drivers and pointed the computer to the ADB files as the new drivers. After those install it should be labelled correctly and work.
Heres the gyst of things real quick:
Currently Running CM7 and I want to ODIN back to stock, however every time i plug my phone to my PC the screen prompts on the lower right task bar "Installing Drivers", then i get a notification saying can't install drivers. I've tried almost everything, installing the nexus s drivers, samsung kies, and the AIO vibrant toolbox. I just can't seem to get my phone to install on my pc. Without my phone being able to plug into my PC, I can't odin back to stock because the computer doesn't read the phone. Can anyone help me with this problem?
Have you tried downloading the SDK manager and loading them from there?
same thing happened to me, first you have to find out what kind of op system ur pc is using (32 bit, 64 bit, or 86) then reinstall the driver and that should fix ur problem
samsung vibrant usb driver for windows 7 problem
I need help. I have tried to connect my PC which runs windows 7 but I couldn't install driver for w7. I have tried with lies mini but it didn't work. By the way I am using ics on my phone. Could you help me find driver for t mobile Samsung vibrant sgh t959 for windows 7. Thanks anyway.
You should be able to go into device manager and find your drivers that are already installed. "Forget" or delete them. Reboot your phone (just in case) and your computer and once both are booted up, plug your phone into the USB and W7 should be able to pull the correct drivers on-line. Has worked for me in the past.
i did what you said but windows 7 couldn't install driver. i am not sure what problem is but so annoying. i need to find some solution!
Have you tried to install the drivers before connecting the phone? Have you first tried to uninstall any old drivers? Also which drivers are you using?
go to Samsung website --> search for t959 and select it from the results --> support on the upper right --> Manuals and Downloads tab --> Software tab --> Drivers are first item
Well guys I've been trying for hours now, whenever I try to install the USB drivers in order to unlock my bootloader, when I plug in my Nexus it installs the MTP drivers on it's own, if I try to install the google drivers downloaded from ADB all I get is a message saying the best drivers for my device are already installed and it doesn't let me overwrite them.
If I go with the use disk option it doesn't let me choose the usb_drivers folder because it just wants to use a .inf file, whener I follow the instructions the toolkit dictates I read the dead end with the "The best drivers for your device are already installed"
I'm so angry right now.... Please help me.
Are you on a Windows XP operating system by any chance? There are major issues with MTP mounting on WinXP regardless of the service pack you're on. Some people claim they've gotten things working by updating WMP, via a Naked Driver and even by installing the Android SDK. Let me know if you are indeed on WinXP & I'll get you some links
Did you try following Wug's Nexus Root Toolkit to install the drivers? That helped me. I cannot post a link so look around for it.
I'm running Windows 7 64 bit, thanks guys, I just gave up and did it in my sister's laptop, it worked on the first damn attempt, maybe the drivers of my N10 were screwing something up, that's my best guess.
Glad you got that sorted--just for future reference, a common recommendation for people having driver issues with their Nexus devices is to simply go into Win Device Manager, uninstall all your current Nexus & ADB drivers and restart. Then plug your phone in via USB and let the auto installation do its thing. Usually this fixes all issues w conflicting device drivers
I have no idea in which section to write this, so General seams like the best choice.
I have a Galaxy Y testing device with a broken boot.img. I am trying to get Odin working in Windows 7 in order to flash a new boot.img to this device, but I can't get the Samsung USB drivers to work and my Windows knowledge is now that great as I mostly work on Linux computers, but no fastboot on Samsung devices.
There are two drivers listed in the Device Manager. The Regular Samsung USB drivers, and something called Samsung USB CDC. It's the CDC I seam to have issues with. It just shows an error message that states "The device could not start (Code: 10)". I have already talked to Samsungs online support, but there is not much support to find there. They know nothing about Windows or how to get anything working on it. And google's search engine, which usually is the best friend for something like this, did not come up with much either.
I should mention that I run Windows in VirtualBox. However, I already have HTC Sync Manager fully working with an older HTC device, so this is not a VBox issue. Also, Windows do find the device just fine, it just can't start one of the drivers.
I have tried installing Kies. I have also tried installing other separate driver versions. Nothing is working.
Search the forums for Naked Drivers, its a complete driver package for a lot of android devices.
Give em a try.
I would post a link but my post count is as such that I cannot at this time.
WooHooGuy said:
Search the forums for Naked Drivers, its a complete driver package for a lot of android devices.
Give em a try.
I would post a link but my post count is as such that I cannot at this time.
Click to expand...
Click to collapse
I love the idea of a multi driver for all devices, much like on my linux boxes, so thanks for that. However, I get the same issue and same error message. I will try to reinstall windows and see if that will work. It has been many many years since I ran windows as my daily OS, but I do remember that formatting was the best way of fixing issues with it. If this is still no go, I will try to put windows directly on my netbook to see if this could be a Virtual problem anyways, but I don't think so. USB stuff is working fine on the Virtual OSX.
Will report back later
EDIT:
Nothing is working. All I have installed, is the naked driver. When I plug-in my HTC Desire or HTC Wildfire S, the driver is working fine. But when I plug-in the Galaxy S3 or the Galaxy Y, I get the "The device cannot start (Code: 10)".
So HTC devices are working, but Samsung is not. The same problem I had with separate HTC and Samsung drivers.
try the one from my link,its latest usb driver exe from kies,worx on win8 64bit too.
http://forum.xda-developers.com/showthread.php?t=1927769
-CALIBAN666- said:
try the one from my link,its latest usb driver exe from kies,worx on win8 64bit too.
http://forum.xda-developers.com/showthread.php?t=1927769
Click to expand...
Click to collapse
Thanks, but I have tried that version, and the one newer (1.5.23). I did manage, efter some reinstalls, to get 1.5.18 (I think is was) to work on the real installation. So maybe my issue is with virtualbox, I just can't see what. I have disabled everything in linux that could block something, I have disabled firewall and such on the virtual windows, I have tried checking and changing perms on the linux device nodes, and tried running VB as root.
At least I got the Galaxy Y running again, but I don't like having unresolved issues so VB is going down
so I got the latest Universal Naked Drivers 0.73 zip file, extraced it to its own folder on my desktop, and then I opened device manager, went to Other Devices>Nexus 4, right clicked, uninstalled, restarted my laptop and nexus 4, and then opened device manager again, and this time clicked on Update Drivers for nexus 4, and when I select browse files on my computer, then I click that folder, which has two sub folders in it, one for AMD64 and then i386, and there is also some other files in the main folder, outside the subfolders, called androidwinusba64 and androidwinusb86, as well as two more called android_apxusb and android_winusb.
But When i click on the main folder so it searched through that and the two subfolders, it keeps saying it's not finding any drivers for my device, and i've tried clicking on each of the sub folders, and neither of those make it work either. I've done what every guide has shown me, which I've installed drives hundreds of times in my 27years of life, and I have never had a problem before. Especially not with Android devices. I can't get my brand new 16gb nexus 4 that i just got yesterday (got it while I wait for Tmobile to get the Nex5 in stock, and then I am switching them out) to show up under my computer as a media device so I can actually drop files onto it. I dont get what the issue is here. I know that the 4.3 update (which I updated to last night when i first powered on my phone and activated it) cause some driver issues from what i've read, but supposedly they have been fixed or whatever, and this Naked Driver is supposed to help as well. But getting them installed first would work better lol. everytime I plug the phone in, it tries to install the drivers itself, but it keeps failing for some reason. Any thoughts on how to proceed ?
It's ADB driver, you need to enable USB Debugging. If you are using Windows 8, reboot it into advance mode and disable driver signature checking.
eksasol said:
It's ADB driver, you need to enable USB Debugging. If you are using Windows 8, reboot it into advance mode and disable driver signature checking.
Click to expand...
Click to collapse
i already know all that lol I've been modding for quite a few years, so I know all about USB debugging, thanks tho. That's definitely not the problem. I can get the phone to work with ADB no problem, but I can't get it to show up as a media device like its supposed to when i have that selected in the USB mode options.
Oh, and I am sorry, I shoulda clarified, I am on Win 7. I already read about the Windows 8 thing tho. Which I got a copy of Win8, so I do plan on upgrading soon, check it out see what its like. But I just gto a new copy of Ubuntu, so I've been playing around with that a lot lately.
Anyone ? I have tried so many different things and Just can't get it to work, bout to chuck my laptop out the window lol
I can't speak for the naked drivers as I have never used them, but the ones that come with the SDK work fine with Win 7 on Android 4.3 (Copy and pasting files with Windows Explorer, adb, fastboot, etc.).
Did you resolve your issue? If not you should try to run "Usb Tree View" and make sure your phone internal USB switch is set to PDA and not MODEM or BOTH etc. I don't know how that works for the Nex4 but its a thing to look at.