If anyone can give advice it would be appreciated.
So I bought an Ouya from a friend that had CM11 on it and still some of their apps ect
I plugged it in, I noticed the screen over cast but the device was working, I went into CM11 and did a factory wipe (for a fresh start)
CM11 booted back up, but the controller wasnt working anymore. Took me a while to access the menus with the keyboard but I got the controller working.
I got fed up with the screen issue and the hassle and thought it was CM11s problem so I wanted to see what stock ouya was like
I alt + print scrn + i and flashed stock Ouya
now all I see when turning on the Ouya is the Orange Ouya logo, and alt + print scrn + i does NOT longer take me into recovery.
What can I do here? Thanks in advance.
Can you turn on the ouya, then plug in a usb cable and test whether your pc sees the ouya? If so, you should be able to use a tool like ouya toolbox to flash cwm, then boot into recovery. I would highly recommend installing the latest boot menu, so you don't have to time the alt-ps-i in the future.
jerry, thanks for your reply
My pc recognizes the ouya but I haven't been able to get the drivers properly installed
I've tried win xp, win 7 and 8
it loads as a mtp device. I've got android sdk installed but that's as far as I've got
well it's been a few days and I can't figure it out
when I plug the ouya into my pc it tries to install drivers for "MTP device"
it fails. tried diff ports. sdk installed. windows 7 and windows xp. no luck
anyone know what I can do? I can't get the Google usb drivers to install at all
Can you check the USB ID of the ouya when it's connected to your PC? Under linux you can do a simple lsusb, but under Windows, I think you'll need to install a little utility to list all of the devices on the USB bus.
Edit: You can get the ID in Windows using the Device Manager. Under the Details tab Hardware Ids
The Ouya vendor id is 2836. The device ID will be different depending on what state the Ouya is in. That might give us a clue as to what's happening.
Edit2: There are a number of threads out there about adding the Ouya hardware ID to android-sdk\extras\google\usb_driver\android_winusb.inf in order to get the Ouya to be recognized by the Google drivers
jerryfath said:
Can you check the USB ID of the ouya when it's connected to your PC? Under linux you can do a simple lsusb, but under Windows, I think you'll need to install a little utility to list all of the devices on the USB bus.
Edit: You can get the ID in Windows using the Device Manager. Under the Details tab Hardware Ids
The Ouya vendor id is 2836. The device ID will be different depending on what state the Ouya is in. That might give us a clue as to what's happening.
Edit2: There are a number of threads out there about adding the Ouya hardware ID to android-sdk\extras\google\usb_driver\android_winusb.inf in order to get the Ouya to be recognized by the Google drivers
Click to expand...
Click to collapse
Hi jerry, Ive tried editing the google usb driver inf file but no luck. theres a 2nd inf file in most steps but I dont have the other android folder.
here is the device instance ID in windows xp
USB\VID_2836&PID_0012\015D8CA2FD2BF006
the steps ive done are.
download android sdk
install google usb driver
download google usb driver stand alone
edit inf file
try to detect drivers - fail
When you say "try to detect drivers - fail" what are you actually doing?
If you haven't already, you should go into Device Manager, right click on the ouya, select the driver tab, choose update driver, choose have disk, then navigate to the folder with the usb driver .inf that you've edited.
When you do that, it should either install the driver or tell you no driver was found for the device.
I'm sure you tried lots of times and I apologize if this is no help, but I just kept banging on alt + prn scrn on mine until it finally went into recovery and a factory reset fixed it. I would imagine that's all that yours needs...just need to find a way to kick it into recovery.
Edit - I did have to install the newest Google driver from the Android SDK Manager as well, and did not need to modify like you used to need to do IIRC.
Related
I just got my data cable in an accessory bundle from hong kong(ebay). Installed htc sync and when I plug in my phone to the PC I get a usb not recognized error. I tried on a different laptop and same problem. Could it be the generic usb cable?...or did I miss something somewhere?
which os are you using. I believe if you are using win 7 64 there is an additional driver you have to install. I know i did.
windows 7 64 bit. Is the additional driver a separate download or is it in the sense folder??
when you plug it in...does it start charging? do you get the USB connection sound?
if the PC has no response to the phone being plugged in, then try swapping the cable.
if the PC does respond (in any way..lights, sounds, etc) then it's prolly a software issue.
did you actually try doing a google search on this?
something like: evo windows 7 64 "usb not recognized error"
http://forum.androidcentral.com/htc-evo-4g/22285-usb-device-not-recognized.html
http://www.htc.com/us/support/evo-sprint/downloads/
... updated version of HTC Sync
http://community.htc.com/na/htc-forums/android/f/94/tags/Windows+7/default.aspx
http://community.htc.com/na/htc-forums/android/f/94/p/5082/23208.aspx
... a problem with the USB hub.
it was a seperate download i cant find it on my pc but i got it off the guide for adb in development forum. hopefully that works for you.
Thanks for the links magic, but I found those when I actually did search before making this post. None of them worked. I did find a more detailed tut on how to root, so maybe something I missed is in it.
Still havent been able to figure it out. When I connect the device and open device manager I get an !unknown device. I click it and "view drivers" and says none are loaded. SHould I boot into safe mood and try all of this?...or disable driver signature or something??
i've had this issue in the past...in my situation is was a bad port...
you may want to reload everything on the phone though... i've ran into situations in the past were i flash a rom and the usb stops working i am able get the usb to work again by reloading the rom
skuzzie said:
Still havent been able to figure it out. When I connect the device and open device manager I get an !unknown device. I click it and "view drivers" and says none are loaded. SHould I boot into safe mood and try all of this?...or disable driver signature or something??
Click to expand...
Click to collapse
sounds like you just don't have the drivers. they're around here, or, you could update the sdk and the drivers are included in the package. you'd have to do the devmgmt.msc command w7, right click on the device, search for drivers, they're in the sdk usb driver folder.
or, someone around here posted them up somewhere. search.
Thanks for the help guys, I did all of the updates and what not, removed all the associated devices to all usb ports and none of that worked.
I decided to just go the easy route and rule of my generic cable, went to best buy and picked up a new one (data pilot) and it recognized it asap.
Thanks for the help though.
thanks for the update. TBH...the cable was lowest on my list of possible issues.
Hi Guys,
Any help would be great! i do have google talk if anyone is willing to help me out!
My R800i Is rooted and has a version of recovery but not sure which version, i am wanting to update my phone with a better kernel and rom since the current one i have installed is giving me issues ( not being able to receive incoming calls for example )
Another problem is i reformatted the phone since i was having issues with receiving calls but now when i connect my phone to ANY computer via the USB cable the computer trys to install MTP or MSC driver ( depends on which connection type i select ) the Installer fails and i cant even take any files off my phone.
Provided details below. i want to somehow get into the current bootloader and install the ROM thats on my SD card! i do have flashtool installed and Android tool SDK installed but still no success in phone wanting to talk to my laptop.
I am running windows 7 64 bit. i am starting to think the phone is belond repair since i cant get any software to work between the phone and computer.
does anyone know what buttons i need to push on the Xperia Play to enter into the boot loader, i have tried pressing the back button and search button on phone boot but nothing happens apart from the phone starts up normally.
would a factory reset delete the boot loader and other config-ed software off the phone is this why i cant enter the boot loader or am i not pressing the right buttons on boot.
Any help would be really appreciated!
IMEI:
357302043579712
IMEI Software Verson
49
Available Speech Codecs
HR, FR, EFR, AMR_HR, AMR_FR
Working Bands
GSM850, GSM900, GSM1800, GSM1900, UMTS_BC1, UMTS_BC8
Rooting Status Bootloader Unlocked Allowed: Yes
Phone Software Version
1245-8821_4.0.1.A.0.283
S1 Boot Version
1241-3656 R9A021
EST Software Version
1242.5099_10
Android Version
2.3.4
Baseband Version
8x55A-AAABQMAZM-203028A-49
Kernel Version
2.6.32.9-perf
Build Number
4.0.1.A.0.283
If you want to change the kernel you must unlock your bootloader. If your Xperia Play is a SIM free one, you can do it for free in this link: http://unlockbootloader.sonymobile.com
For SIM locked devices I think you must find another ways to do it. There are some online sites that unlock bootloader to SIM locked devices for a fee.
Once you have unlocked your bootloader, turn off the phone, hold on the search button, plug the USB cable in the computer, release the search button (power button LED will be blue) and install this driver: http://drivers.softpedia.com/progDownload/Google-USB-Driver-Revision4-Download-139077.html
Now you are ready to flash any kernel you want with Flashtool or any other app.
Thanks for the information, i have already done this, i payed £25 for a guy on this forum to unlock my phone to any network. i'll give this a try and get back to you, problem is the phone doesn't like to talk to my laptop via USB cable keeps on failing to install the drivers..
Thanks for quick response.
PsychoShaft said:
Thanks for the information, i have already done this, i payed £25 for a guy on this forum to unlock my phone to any network. i'll give this a try and get back to you, problem is the phone doesn't like to talk to my laptop via USB cable keeps on failing to install the drivers..
Thanks for quick response.
Click to expand...
Click to collapse
I have tried what you said but having problems with connecting my phone to my Windows 7 Laptop!
Check your device manager. The fastest way to open it is running this command: devmgmt.msc
There must be some kind of Android device while your phone is connected in fastboot mode. If you see it, update its driver with the Google USB driver v4 pointing at the folder path with the uncompressed files.
jcarbox said:
Check your device manager. The fastest way to open it is running this command: devmgmt.msc
There must be some kind of Android device while your phone is connected in fastboot mode. If you see it, update its driver with the Google USB driver v4 pointing at the folder path with the uncompressed files.
Click to expand...
Click to collapse
Hi I tried what you said, i Turned off my phone and holded the search button and turned it back on, the light went blue and the computer popped up trying to install fast boot i point to the SDK folder to update the driver but it fails.
do you have google talk might be easier on there to talk! cheers!
I'm not using gtalk atm. Sorry.
Be sure the driver you downloaded is named usb_driver_rev4.zip: http://drivers.softpedia.com/dyn-postdownload.php?p=139077&t=4&i=1
If Windows doesn't detects any driver in that uncompressed folder, you can choose to select the device from a list, point to that folder and force to install the driver. It's named something like Android ADB Interface.
jcarbox said:
I'm not using gtalk atm. Sorry.
Be sure the driver you downloaded is named usb_driver_rev4.zip: http://drivers.softpedia.com/dyn-postdownload.php?p=139077&t=4&i=1
If Windows doesn't detects any driver in that uncompressed folder, you can choose to select the device from a list, point to that folder and force to install the driver. It's named something like Android ADB Interface.
Click to expand...
Click to collapse
Thanks for the download link, i going to try this in a bit and get back to you! thanks for the support guys! :good:
Just tried, i put my phone into Media Transfer Mode.. my computer tried to install the MTP usb device and i directed the installation to the driver you linked..
Update Driver Software says: the best driver software for your device is already installed MTP USB DEVICE, there is a small yellow triangle on the icon and in MTP USB Device Properties it says: This device cannot start. (Code 10)
i need someone to Teamviewer with me, for the record i don't have the Sony Ericsson software installed on my Computer because that still wont install the drivers for my phone, i also know its not needed for installing new kernel and roms.
i tried connecting this phone to a bunch of pcs including my friends and it still fails to install any drivers!!! i think i am just going to bin this phone! i have had enough (
You must install that driver when you plug the phone in fastboot mode. It shouldn't work in any other case. In other words, when you plug your Xperia Play being powered on and Android is running it needs one driver, and when you boot it in fastboot mode you need other driver.
Please, install the driver following the steps previously posted with your phone in fastboot mode (blue LED).
Hello, i put my phone into fastboot mode, my device manager shows 1 device not installed S1Boot Fastboot, i right click go to properties and click update driver...
then i browse my computer for driver software i point the location to usb_driver_rev4\usb_driver and it says: Windows was unable to install your s1Boot fastboot!
Ok, let's see...
Try to update the driver using the "choose from a list" option to force the installation, point to the driver folder and select "Android ADB Interface" from the list. If Windows shows a warning message don't worry about it and go ahead.
i tryed this and its not wanting to work (
Sorry to hear that because I don't have any more ideas for your problem.
Maybe you may spend some minutes searching in the forum to find some detail that can help you.
i need someone with teamviewer to help me go though the setup process again, if anyone is willing to get my phone working i will happy pay them some money!
Thanks Jcarbox for all your support!
Regards
Paul
I just check the Windows device manager with my phone plugged in bootloader mode and it appears as Android Bootloader Interface, so this is the device you must choose from the list when you install the driver.
Hope this helps you.
thanks for the help, to bad my phone isnt having any of it.. just going to buy another phone (
This may work
PsychoShaft said:
thanks for the help, to bad my phone isnt having any of it.. just going to buy another phone (
Click to expand...
Click to collapse
hi PsychoShaft,
I had similar problems. I don't know how to fix it permanently. but i do this to make it work for some time.First, download flashtool and install it.Open your device manager and select view->show hidden drivers.Then, delete all your drivers related to xperia play. like the adb interface, semc flash ,etc. All of them in all categories. then reboot your computer into safe mode with administrator and connect your device with flashtool running in your windows in safe mode. then the flashtool will indicate that you don't have the drivers. then,open the drivers folder in flashtool and use the setup to install arc-play-...,flashmode drivers and fastboot mode drivers.then after the installation is over windows will ask you to reboot.now reboot with your mobile connected. after boot windows will automatically install the drivers. then unplug your phone and turn off it and connect in flash/fastboot mode.it will automatically install drivers.wait for windows to say drivers installed successfully or installation failed. don't unplug it in the middle of the process then you will have to start from first.sometimes it will not work in the first time ,then reboot into safe mode and try again installing the drivers and rebooting into safe mode itself and connecting your device.at one point of time flashtool will say your device is connected in flas/fastboot mode.then continue with flashing
Gladwin.
Thanks for the support guys i managed to solve the issue!
^^^^ Glad i could help
Sent from my GT-I9300
Windows 8.1; but had same problem with Windows 7 computer.
USB device not recognized
The last USB device you connected to this computer malfunctioned. And Windows does not recognize it.
Windows has stopped this device because it has reported
problems. (Code 43) A request for the USB device descriptor failed
Tried using WUGS Toolkit to install drivers, not happening.
The phone charges via usb port with no problems
On top of that, daughter wiped phone, there are no ROMS, or usable backups.
I can get into TWRP Recovery, but it can recover what isn't there. Tried factory
reset, still nothing. No matter what I do, I get No OS Installed! Are you
sure you wish to reboot? If I do reboot, just get GOOGLE screen with lock
symbol.
Without being able to get a computer to see the phone, I can't get a ROM to
load.
Maybe change USB port with cable? But I don't want to do that if the problem
is software related.
Any ideas what I can do???
I just went through something similar like this last week, what a pain in the A$$.
Not entirely sure if this will fix your issue, but hopefully it'll help some how.
I ended up having to manually install galaxy nexus driver so I could sideload a ROM since I formatted my internal storage to test out this new F2FS BS... Anyways.
LOL
First you'll need to download and unzip "universal naked driver 0.72" Google it.
Now, without your GN connected open device manager and THEN when you plug in your GN to your PC you should see it pop up in the portable devices section.
AND also under other devices there should be "galaxy nexus" right click on it and click "update driver software"
Click "browse my computer for driver software" select the unzipped universal naked driver folder, click next and click "install this driver software anyway"
Now it should show "Google galaxy nexus ADB interface" in device manager under Samsung Android Phone.
Reboot GN into bootloader
OR
recovery (if you have a ADB supported recovery eg. TWRP 2.7.0.0, and enter ADB mode)
Now there are 2 ways to do flash an Android OS, some may find 1 easier then the other:
download/install "Wug's Nexus Root Toolkit aka NRT v1.8.3.sfx"
Google it.
Run NRT and it'll instruct and guide you through the steps required and whatever is needed to continue, eg. Select device, download TWRP 2.7.0.0...ETC.
Or
Download/install ADB setup 1.3
Google it.
I found this method a little more simpler.
Open the folder you have your ROM/gapps zip files saved on your PC, hold down shift key and right click on the folder, click "Open command window here"
Now in the command window type in "adb sideload XXXXX.zip"
XXXXX = COPY/PASTE the ROM file name. Eg. 20140615PA443RC2.zip
Press enter and now it'll flash the ROM onto your GN.
Repeat the same steps for gapps/kernel zip files.
Reboot your GN and enjoy.
BTW
I'm still loving running ParanoidAndroid Jellybean 4.1.2.
Its like pain in the A** to install phone/adb drivers in win8/8.1
I had a similar issue with my gNex a while ago but i had the drivers installed in my pc so it wasn't that difficult.
Why don't you try to install this toolkit http://forum.xda-developers.com/gal.../gnex-toolkit-v11-1-0-drivers-backup-t1392310
When you run the toolkit, it may ask you to select your device, build number etc and also about installing device drivers.
Install the drivers through it and then connect the device in recovery (twrp) mode.
it should detect it and then you can push files/roms to sdcard (internalMemory) using adb push or the built in options in the toolkit.
then flash the rom and you're done
and i recommend using win7 or xp or vista for doing this because the driver installation in win8/8.1 is a bit difficult compared with other previous windows versions but there is still a way to install drivers in win8/8.1 its just a lengthy process
All the best :good:
stargazer127 said:
Windows 8.1; but had same problem with Windows 7 computer.
USB device not recognized
The last USB device you connected to this computer malfunctioned. And Windows does not recognize it.
Windows has stopped this device because it has reported
problems. (Code 43) A request for the USB device descriptor failed
Tried using WUGS Toolkit to install drivers, not happening.
The phone charges via usb port with no problems
On top of that, daughter wiped phone, there are no ROMS, or usable backups.
I can get into TWRP Recovery, but it can recover what isn't there. Tried factory
reset, still nothing. No matter what I do, I get No OS Installed! Are you
sure you wish to reboot? If I do reboot, just get GOOGLE screen with lock
symbol.
Without being able to get a computer to see the phone, I can't get a ROM to
load.
Maybe change USB port with cable? But I don't want to do that if the problem
is software related.
Any ideas what I can do???
Click to expand...
Click to collapse
isajoo said:
I just went through something similar like this last week, what a pain in the A$$.
Not entirely sure if this will fix your issue, but hopefully it'll help some how.
I ended up having to manually install galaxy nexus driver so I could sideload a ROM since I formatted my internal storage to test out this new F2FS BS... Anyways.
LOL
First you'll need to download and unzip "universal naked driver 0.72" Google it.
Now, without your GN connected open device manager and THEN when you plug in your GN to your PC you should see it pop up in the portable devices section.
AND also under other devices there should be "galaxy nexus" right click on it and click "update driver software"
Click "browse my computer for driver software" select the unzipped universal naked driver folder, click next and click "install this driver software anyway"
Now it should show "Google galaxy nexus ADB interface" in device manager under Samsung Android Phone.
Reboot GN into bootloader
OR
recovery (if you have a ADB supported recovery eg. TWRP 2.7.0.0, and enter ADB mode)
Now there are 2 ways to do flash an Android OS, some may find 1 easier then the other:
download/install "Wug's Nexus Root Toolkit aka NRT v1.8.3.sfx"
Google it.
Run NRT and it'll instruct and guide you through the steps required and whatever is needed to continue, eg. Select device, download TWRP 2.7.0.0...ETC.
Or
Download/install ADB setup 1.3
Google it.
I found this method a little more simpler.
Open the folder you have your ROM/gapps zip files saved on your PC, hold down shift key and right click on the folder, click "Open command window here"
Now in the command window type in "adb sideload XXXXX.zip"
XXXXX = COPY/PASTE the ROM file name. Eg. 20140615PA443RC2.zip
Press enter and now it'll flash the ROM onto your GN.
Repeat the same steps for gapps/kernel zip files.
Reboot your GN and enjoy.
BTW
I'm still loving running ParanoidAndroid Jellybean 4.1.2.
Click to expand...
Click to collapse
OK, downloaded universal naked driver 0.72, connected gnex, but it only shows up under Universal Serial Bus controllers as Unknown USB Device (Device Descriptor Request Failed), not under Portable Devices, and will not allow install of of universal naked drivers, & yes I have toggled to allow win 8.1 to installed unsigned drivers. Since I cannot get phone to turn on to full android, it is not recognized. Any other suggestions?
KingWickedd said:
Its like pain in the A** to install phone/adb drivers in win8/8.1
I had a similar issue with my gNex a while ago but i had the drivers installed in my pc so it wasn't that difficult.
Why don't you try to install this toolkit http://forum.xda-developers.com/gal.../gnex-toolkit-v11-1-0-drivers-backup-t1392310
When you run the toolkit, it may ask you to select your device, build number etc and also about installing device drivers.
Install the drivers through it and then connect the device in recovery (twrp) mode.
it should detect it and then you can push files/roms to sdcard (internalMemory) using adb push or the built in options in the toolkit.
then flash the rom and you're done
and i recommend using win7 or xp or vista for doing this because the driver installation in win8/8.1 is a bit difficult compared with other previous windows versions but there is still a way to install drivers in win8/8.1 its just a lengthy process
All the best :good:
Click to expand...
Click to collapse
OK, tried this too, but it only shows up under Universal Serial Bus controllers as Unknown USB Device (Device Descriptor Request Failed), not under Portable Devices, tried 1st way by installing drivers, then using PDA, cannot complete PDA driver installation because it can't see the phone. & yes I have toggled to allow win 8.1 to installed unsigned drivers. Since I cannot get phone to turn on to full android, it is not recognized. Any other suggestions?
stargazer127 said:
OK, tried this too, but it only shows up under Universal Serial Bus controllers as Unknown USB Device (Device Descriptor Request Failed), not under Portable Devices, tried 1st way by installing drivers, then using PDA, cannot complete PDA driver installation because it can't see the phone. & yes I have toggled to allow win 8.1 to installed unsigned drivers. Since I cannot get phone to turn on to full android, it is not recognized. Any other suggestions?
Click to expand...
Click to collapse
You have to go to the device manager, double click on the "unknown usb..."
a dialog box may appear and then click on the 'driver' tab.
There u may find update/install driver button.
click on it and another window may open.
then select browse my computer for driver software and go to the respective folder where the drivers are.
then click next and it may install the drivers.
if you have installed the toolkit then you may find a folder in the toolkit's installation folder which has drivers in it.go through it if you want :good:
I've been eager to try Scott Crosler's new CM11 but didn't have time until tonight. To ensure cleanliness, at the bootloader I erased cache, system and userdata. I've flashed ROMs dozens of times, and as usual, there were no problems with fastboot recognizing the device.
I then entered CWM, and it was the darndest thing: three fast USB connection beeps and this error:
"Windows could not install driver software for your device."
But I've had the generic USB drivers installed for two years! At first I thought it was interference from the Samsung drivers when reflashing my wife's tablet, but I tried our two laptops, same result. No matter that I right-clicked "Nexus 7" in Device Manager and pointed it to freshly downloaded drivers, even that I tried installing drivers using the SDK Manager,
"Windows could not install driver software for your device."
I've read that turning off USB debugging helps, but um, with an erased /system, I had nothing to boot into!
Normally I prefer flashing via ADB sideload. To get up and running again, I flashed TWRP and used its feature of mounting USB-OTG and flashing from an external drive. Once I got into CM11, I turned on and off USB debugging, but I still can't install the USB drivers, and ADB can't recognize any devices. At least there's flashing via external flash drives.
Has anyone had the like?
didn't see win 8.1 mentioned but thought this may help? http://forum.xda-developers.com/nexus-7-2013/general/windows-8-1-users-careful-t2856908. I have had problems with drivers in past. adb composite are the ones that work for me. I simply removed drivers under android devices in device manager then plugged in device. GL.
Windows 7 here, but thanks for the suggestion anyway.
This morning I can connect it as a media device, and it's in Device Manager just fine as "Nexus 7." But turning that off, it becomes "flo" in Device Manager and can't find the updated drivers. And either way, I still can't get it recognized while in recovery mode. Ah well, as I said, at least TWRP has the option to mount USB OTB and flash files from an external drive.
Let me add that I already tried another cable (for our Samsung tablet), and tonight I see that I can connect it in MTP mode. In MTP mode, it shows up just fine in Device Manager (under Portable Devices), but turning off MTP throws it under Other Devices with the dreaded ! (and I just can't get it to install the driver no matter where I point it to). And no matter what combination I try, I still can't get ADB to recognize it at all.
Although this is for Windows 8.1 it may apply to your situation: http://forum.xda-developers.com/nexus-7-2013/general/windows-8-1-users-careful-t2856908
As I e-mailed you, sfetaz's suggestion of USBDeview is part of the solution! I still can't get it recognized in booted Android as anything but a media device, but now it's fine during recovery. Darndest thing I ever saw in 19 years of dealing with Windows drivers.
http://www.nirsoft.net/utils/usb_devices_view.html
Then in an old bookmark, I tried Koush's universal ADB drivers.
http://download.clockworkmod.com/test/UniversalAdbDriverSetup.msi
Even if USBDeview hadn't helped, it was still good to clear out all the old devices I no longer use. Definitely a handy utility to keep around and recommend.
I have recently root my samsung tab pro 8.4 wifi version. Everything seems to work well, except USB connection to my windows7 desktop. I installed the latest version of Samsung usb driver (download from Samsung's web site for my device). Whenever I connect it, media device mode, the "installing device driver software" icon spins for couple of minutes, then I got the error of "Device driver software was not successfully installed" . In the detail dialog window, it says "MTP USB Device" failed with a red cross. what did I do wrong? thanks.
I have tried several different USB 2 ports on my computers. Also I have Developer mode turned on, with or w/o USB debugging checked. Nothing seems to work. Also the camera mode doesn't work either.
Did you install kies 3 from samsung?, this should install all the drivers you need.
http://www.samsung.com/us/kies/
I tried with this version of kies from samsung's website, not working. Got the same failed to install device driver message.
In windows device mananger, it shows a MTP USB device with yellow "!" mark on it. If I try to update driver from here with the driver installed on my computer, it says I have the latest driver installed already.
dealcrack said:
I tried with this version of kies from samsung's website, not working. Got the same failed to install device driver message.
In windows device mananger, it shows a MTP USB device with yellow "!" mark on it. If I try to update driver from here with the driver installed on my computer, it says I have the latest driver installed already.
Click to expand...
Click to collapse
Try going to Device Manager in Windows, find the device, pick the option to select from the drivers on the computer, then pick the "USB MTP drivers" (generic, not Samsung) and see if that helps.
redpoint73 said:
Try going to Device Manager in Windows, find the device, pick the option to select from the drivers on the computer, then pick the "USB MTP drivers" (generic, not Samsung) and see if that helps.
Click to expand...
Click to collapse
thanks for your help. I tried your suggestion, and
I went to the Device Manager, and select the "MTP USB Device" with yellow "!" mark, choose this menu,
Update driver software->Browse my computer for driver software->let me pick from a list of device drivers on my computer
I see two drivers, however either works for my 8.4 pad. It says "This device cannot start (code 10)"
Also when I open the properties for this device in device manager, it shows its driver running is from Microsoft, driver version 6.1.7600.16385. Should be a driver from Samsung?
dealcrack said:
thanks for your help. I tried your suggestion, and
I went to the Device Manager, and select the "MTP USB Device" with yellow "!" mark, choose this menu,
Update driver software->Browse my computer for driver software->let me pick from a list of device drivers on my computer
I see two drivers, however either works for my 8.4 pad. It says "This device cannot start (code 10)"
Also when I open the properties for this device in device manager, it shows its driver running is from Microsoft, driver version 6.1.7600.16385. Should be a driver from Samsung?
Click to expand...
Click to collapse
Are you running stock TouchWiz ROM? Just to be sure.
Otherwise you could remove all your USB drivers related to Android and start from scratch with just the Sammy driver. I had to do that for my previous OnePlus One, it just wouldn't connect. It chose a wrong driver each time I hooked it up so I had to just remove those from the driver store and then make it choose another one. That was for ADB thought, but I guess it couldn't hurt to try anyways.
The reason I'm mentioning if you're on stock ROM is because this morning, on CM nightly 01-24 I had some troubles with my tablet being read by Windows, it was fixed in 26 so.. Just wanted to mention it.
CuraeL said:
Are you running stock TouchWiz ROM? Just to be sure.
Otherwise you could remove all your USB drivers related to Android and start from scratch with just the Sammy driver. I had to do that for my previous OnePlus One, it just wouldn't connect. It chose a wrong driver each time I hooked it up so I had to just remove those from the driver store and then make it choose another one. That was for ADB thought, but I guess it couldn't hurt to try anyways.
The reason I'm mentioning if you're on stock ROM is because this morning, on CM nightly 01-24 I had some troubles with my tablet being read by Windows, it was fixed in 26 so.. Just wanted to mention it.
Click to expand...
Click to collapse
Yes, I am on the stock TouchWiz ROM, but I rooted it following steps from one thread in this forum. Before rooting, I was able to connect. I do have a LG G3 phone connecting to the same computer successfully. Will this cause any problem? Will going to CM ROM solve my problem?
Also, can you tell me steps to remove all my USB drivers related to Android in Windows 7?
dealcrack said:
Yes, I am on the stock TouchWiz ROM, but I rooted it following steps from one thread in this forum. Before rooting, I was able to connect. I do have a LG G3 phone connecting to the same computer successfully. Will this cause any problem? Will going to CM ROM solve my problem?
Also, can you tell me steps to remove all my USB drivers related to Android in Windows 7?
Click to expand...
Click to collapse
It may work to install CM11 or CM12, BUT try this toolfirst (uploaded to my personal box account) Find all your mobile device drivers in this list and mark them and go to "File" and click "Uninstall marked drivers", restart your PC and plug in your tablet. Then try plugging in LG after so it gets drivers later. I'm not sure if it will work. But it should apply new drivers. If it doesn't work, uninstall the drivers one more time and download the Samsung drivers from 3rd party and install them and apply then manually to your tablet through Device Manager in Windows.
https://app.box.com/s/7njztz17hekfkpxbjk7h79xsctnmuptn
Anyways, try this first.
dealcrack said:
I do have a LG G3 phone connecting to the same computer successfully. Will this cause any problem?
Click to expand...
Click to collapse
Its always a possibility. I'd try to uninstall the LG drivers. You can always re-install later (if needed).
In a perfect world, the Sammy drivers would be what you want. But this is of course not a perfect world. I've had better luck using the "generic" Microsoft MTP USB drivers over the HTC drivers on my HTC devices.
CuraeL said:
It may work to install CM11 or CM12, BUT try this toolfirst (uploaded to my personal box account) Find all your mobile device drivers in this list and mark them and go to "File" and click "Uninstall marked drivers", restart your PC and plug in your tablet. Then try plugging in LG after so it gets drivers later. I'm not sure if it will work. But it should apply new drivers. If it doesn't work, uninstall the drivers one more time and download the Samsung drivers from 3rd party and install them and apply then manually to your tablet through Device Manager in Windows.
https://app.box.com/s/7njztz17hekfkpxbjk7h79xsctnmuptn
Anyways, try this first.
Click to expand...
Click to collapse
I download this tool, and remove all Samsung or Android related USB driver. Restart my computer and connect the pad it's not working. Then I uninstall the Samsung driver software, and all USB driver. Then restart and install a samsung driver from the thread about how to root my pad in this forum. Connect my pad, no luck. Still the same problem. I am about to give up.
redpoint73 said:
Its always a possibility. I'd try to uninstall the LG drivers. You can always re-install later (if needed).
In a perfect world, the Sammy drivers would be what you want. But this is of course not a perfect world. I've had better luck using the "generic" Microsoft MTP USB drivers over the HTC drivers on my HTC devices.
Click to expand...
Click to collapse
I uninstall my LG driver too, along with all Samsung/Android usb driver with the tool from previous reply. No luck, It still shows a MTP device with yellow "!" mark.
Just before I about to give it up, it connects to my another computer now, which is my main computer and it had trouble connecting to. All I did was restart my pad several time and odin twrp recovery to it. It connects after rebooting. No idea what cause this problem, but it works now. thank you for all your help.
dealcrack said:
Just before I about to give it up, it connects to my another computer now, which is my main computer and it had trouble connecting to. All I did was restart my pad several time and odin twrp recovery to it. It connects after rebooting. No idea what cause this problem, but it works now. thank you for all your help.
Click to expand...
Click to collapse
Glad you sorted it out, to some degree or other.
USB connectivity on Android devices is very tricky, at least on Windows (can't speak on other OSes). My HTC phone connects fine to my work laptop with the HTC drivers. On my home computer (also Win7) it frequently drops adb connection and I have to manually select the "generic" Microsoft drivers to make it work (and the HTC drivers never seemed to work completely right either). My Sammy Pro 8.4 seems to connect just fine to my home PC, however. So it seems its just a crap shoot what kind of connectivity you will get, really.