Related
I just got my SNS yesterday and it's my first android phone (was previously using an LG cookie) First thing I did was try to root it, and I seemingly succeeded, or so I thought. It looks like it's rooted and the superuser apps there but I can't install apps using any of the guides I find or even update to 2.3.2 (keep getting and error 7 msg). When I try to install using APKInstaller it tells me it can't find the device, which I think is the problem.
I think the problem is that someway or another windows 7 64 bit stopped recognizing my phone as a Nexus S and now recognizes it as a portable device in device manager (There's also an Android Phone, with an Android Composite ADB interface) I used the SDK to install all the updates available including the google usb driver rev. 4. I tried updating the Portable device driver using the google usb driver but windows keeps it as a WPD Filesystem Volume Driver. Also I noticed when I checked to see if adb gave me a serial number for the phone using the cmd prompt commands in the rooting guides it comes up blank.
I used usbdeview to delete everything seemingly related to Android, but everytime I reconnect the phone it, installs the drivers for the portable device.
I need help to make windows recognize the phone as a nexus s again so I can update and install apps and games etc. If anybody out there can help i'll really appreciate it. Explain the steps to me as if you were talking to a child, leaving nothing out plz. Thanks for any assistance.
I live outside the US (no android market) and would hate to think I messed up and expense phone purchase in just one day
Not quite sure where to start. But my intuition tells me its the Windows 7 64-bit and drivers that's not playing along. You might want to google if other users are having trouble with W7 64-bit with Android drivers. Otherwise, find another computer and repeat the steps. If not, flash a custom ROM to see if that eliminates the problem. You haven't damaged your phone. Don't worry.
just install directly from android market website
Sent from my Nexus S using XDA App
I assume you mean instal the update from the market (which I can't do because I don't have wifi)?
I managed to get the adb to list a device number after I installed java x32 & x64 bit. I still can't install apps or get the update to work, but I'll try unrooting and then rerooting my phone as see how that goes.
Oh, I haven't done the initial sign into gmail thing yet in case that makes any difference
Edit: god I feel stupid. I didn't realize that I had to upgrade from 2.3 to 2.3.1 and then to 2.3.2. I did that an everything upgrade without any problems. Now just got to figure out how to install apk's and I'm golden
Edit 2: Ok, I figured everything out and now i'm up to date with updates and I can install apps and games. Oh Happy Day Thx for all the help
For the life of me I cannot get my Desktop - Gigabyte Mobo (Windows 7 pro 64 bit SP1 with all windows updates) to install the mtp driver for my Galaxy S III (VZW). So far I have tried installing and uninstalling, rebooting, installing drivers both from Samsung website as well as through Kies. The error code I get for the Samsung Mobile MTP Device is
"This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)"
(looking at device manager)
As a sidenote, I tried installing Universal_Naked_Driver_0.7 from this forum and while it does install without error the phone still doesn't show up in any way on the computer (I.E. My computer/as a storage device).
What is strange is that using the Samsung driver that I tried first (on the desktop) I was able to get the phone to install and work perfectly on my Windows 7 64 bit sp1 home premium (Dell laptop).
Any thoughts or suggestions as not even Samsung chat was able to remedy the issue.
*I am new to the forum but I did my best to (beforehand) search for solutions (which I have yet to find).
I couldn't get the MTP drivers to load on XP, due to the well known problems there. I got the built-in Windows drivers to work, and it seems to be working relatively well. I will be testing a longer upload to my wife's phone later today, but for the few songs I tried on my SGS3, it's working well.
I posted my hack here: http://forum.xda-developers.com/showthread.php?t=1851547
I just got a S3 yesterday but was greeted with the dreaded MTP driver installation failed message on win 7 (32 bit)
I installed the regular verizon s3 drivers from samsung's site, did the same thing, uninstalled and tried Kies and let it install the drivers, same problem
tried a different usb port, same thing
restarted the comp and computer, still no go
im getting frustrated now
it seems samsung has known about this issue for over a month now but still hasnt been able to fix it
my a500 and galaxy nexus work fine with MTP so not sure why this would mess up
ive looked at other threads but there was no clear solution on how to fix it
I don't have any issues with mine
Sent from my SCH-I535 using Xparent Blue Tapatalk 2
thats nice but it doesnt exactly do anything for my problem
Joey22688 said:
thats nice but it doesnt exactly do anything for my problem
Click to expand...
Click to collapse
Did you try a factory reset?
Sent from my SCH-I535 using xda app-developers app
This happened to me too but I was running a CM10 ROM. What are you running and have you tried a different ROM?
Unfortunately, I cannot remember exactly what I did but I recall allowing Windows (I'm on W7) to find the drivers and install for me.
I'm not having any issues either, I'm using both 32/64 versions of Win 7...
These are the drivers I'm using:
http://downloadcenter.samsung.com/content/SW/201206/20120620051748445/Verizon_Wireless_I535_GSIII_Samsung_USB_Driver_v1_4_6_0.exe
Hope this helps..
I think I found the problem (its not the phone)
its the drivers that samsung issued
I plugged the phone on my win 7 64 bit desktop (not installing any drivers beforehand) and I got a few failed messages for drivers but I was able to access the file system fine
I then installed the driver pack posted and above then got the mtp driver installation failed message and was unable to access the file system
uninstalled the driver pack and connected the phone back up and I can access the file system (with some other drivers failing to install, I think relating to usb modem stuff ect...)
so until samsung fixes the driver problem I will have to deal with a few driver installation failed message every time I hook up the phone, but at least I can access the file system
im running the phone on the stock ics btw, didnt install cm10 or anything like that, the phone is rooted though but I rooted it after I found out about the mtp driver problem so it shouldnt mean anything
I have the same problem on Windows 7 32 bit. I rooted my phone and installed samba as a temporary fix.
Plus I just bought an external 32 GB SD card and I plan on using that as my workaround and just transfering files between the two.
Sent from my SCH-I535 using Tapatalk 2
Problem for me was the root.
Could you humor me and try this:
- go into the superuser app
- Select the 'temp unroot' checkbox from the first screen.
- unplug then replug the USB cable on your phone. The drivers should install on the first try this time (they did for me) and Kies should work too.
The problem seems to be that SuperUser exploits the USB Debug internally so, even though USB Debug is unchecked, it is still detected as checked by the connection and fails the install of the driver.
Solution #2 is the amazing script that transforms your MTP connection into a UMS one (look in this thread http://forum.xda-developers.com/showthread.php?t=1785243 and thank open1your1eyes0 ). Once in UMS, you don't need the MTP driver to see your device so that's another approach.
Good luck
I bought Samsung Galaxy S3 2 weeks ago. Windows installed the drivers for it when first connected to my Windows 7 64 bit PC. It came up in the list of Devices on the Explorer. I installed "Kies_2.5.0.12094_28_8" which installed USB driver on top of the Windows driver. At the end of the installation, it gave "failure to install Samsung MTP driver".
Saw a thread on other forum where it was suggested to remove the driver from System Driver window under Control Tab/System and reboot. To be cautious, uninstalled Kies. Rebooted PC. Windows installed the driver. As soon as Kies was installed the whole issue unfolded again.
Looks like ALL Kies versions (including previous version of Kies_v2.3.3.12085_7_5) have incompatible and wrong driver which is resulting in this unresolvable situation.
I removed the MTP driver (control panel/system/device manager - MTP driver has ? mark - this is the one). Then removed the phone and rebooted PC. After reboot, connected the phone back. Windows detected the device and automatically installed the driver. The device is listed in Explorer and is fully accessible. Started Kies. It showed the device as GT-I9300. It took a while and connected to the phone. All functions became useable. Sync'ed the contacts etc.
Day2. Booted the PC. Device is still shown in Explorer. Kies shows GT-I9300 and then displays "Connecting Device" - IT FAILS TO CONNECT and on pressing "Trouble shooting" button, it re-installs its own drivers and fails to install MTP driver AGAIN" - the Kies software SUCKS
Solved! For real!
For some reason, any of those options helped me to make it work:
- Reinstall Windows Media Player
- Remove registry key
- Clean up old usb drivers
- re-install 100 times drivers from Verizon, Samsung. Even old versions.
- Install from Windows Update. I tried to do that 1000 times. Gosh!
- enable UMT access (mass storage) on the phone.
The only thing that worked was, for some reason , getting the drivers from a random computer that was the only computer that worked.
Windows 7 x64
Attached the files. Go to the devices manager and update the drivers.
Israel Leite
How I solved it
Joey22688 said:
I just got a S3 yesterday but was greeted with the dreaded MTP driver installation failed message on win 7 (32 bit)
I installed the regular verizon s3 drivers from samsung's site, did the same thing, uninstalled and tried Kies and let it install the drivers, same problem
tried a different usb port, same thing
restarted the comp and computer, still no go
im getting frustrated now
it seems samsung has known about this issue for over a month now but still hasnt been able to fix it
my a500 and galaxy nexus work fine with MTP so not sure why this would mess up
ive looked at other threads but there was no clear solution on how to fix it
Click to expand...
Click to collapse
1. Un-install Samsung Kies and USB drivers
2. Then install the Install Samsung Usb driver for mobile phones version 1.4.6.0
3. with phone un-pluged from the usbcable Go into settings/Developer Options un-check Stay Awake un-check USB debugging un-check Allow mock locations Now hit the HOME button then plug in the USB cable and your are set..
This worked perfectly painless for me :laugh:
Solution x Win XP
This solution worked for me.
Install microsoft patch for usb and reinstall MTP driver
see:
http://forum.xda-developers.com/showthread.php?t=1150211
Hope this helps
I have scoured the internet and xda and have not found a solution. I am trying to unlock my bootloader, so I can install ROMs and whatnot, on my HTC One S. However, the device is not recognized by adb, even though the normal drivers are installed through HTC sync. I cannot install any additional driver through any other way.
Basically, I just need to know if anyone has a solution to getting the HTC One S to recognize with adb on Windows 8, or any alternate way to get a token.
I have done this many times before on windows 7, and even used adb for other devices on Windows 8, but cannot get the One S to read.
..and unfortunately my Windows 7 machine is in need of repair.
Any suggestions would be appreciated.
Adb still worked after I went from 7 to 8. Uninstall drivers and install android sdk which has required drivers. I've never used HTC sync due to its suckness. You can also google the download for just the drivers without any extra software. There are multiple devices that have adb drivers for download here on xda aswell.
Good hunting
But as far as driver compatibility nothing has changed since the update
Sent from my HTC VLE_U using xda app-developers app
the drivers wont work until htc/Microsoft updates them. doesn't work on my windows 8 pro, I had to installed a virtual machine to get it to work with windows 7.
Definitely nofun that the htc drivers seem to be the big issues. Whendid not have trouble with the kindle orsamsung. Did update as much through the sdk, and tried manually installing the win 7 drivers, and more andno luck. So guess Ill be waiting.
Works for me on windows 8 pro....don't know what you are talking about
Sent from my HTC VLE_U using xda app-developers app
Spastic909 said:
Works for me on windows 8 pro....don't know what you are talking about
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
Thats good to hear that there is a way to get it working. What drivers did you install?
Are you looking for a driver that will work for when you are in bootloader? I used a Samsung driver and it worked fine.
mbh87 said:
Are you looking for a driver that will work for when you are in bootloader? I used a Samsung driver and it worked fine.
Click to expand...
Click to collapse
I just installed the latest htc sync and all the drivers were good
Sent from my HTC VLE_U using xda premium
mikeyinid said:
I just installed the latest htc sync and all the drivers were good
Sent from my HTC VLE_U using xda premium
Click to expand...
Click to collapse
Did this allow detect in adb? not just for windows recognizing the device?
Ive come to find that adb will recognize the device, but not in fastboot mode. Which is the killer, cause thats the only mode I really need it to be recognized in.
I use both ADB and Fastboot on my W8, and never had a problem. Worst case scenario, if you install the drivers but you still have an exclamation mark next to the device in device manager, try and install the Android USB drivers on a W7 machine and copy the files on your W8. Then go to device manager and update the driver, and point to the folder you just copied. This should do.
Ruwin said:
I use both ADB and Fastboot on my W8, and never had a problem. Worst case scenario, if you install the drivers but you still have an exclamation mark next to the device in device manager, try and install the Android USB drivers on a W7 machine and copy the files on your W8. Then go to device manager and update the driver, and point to the folder you just copied. This should do.
Click to expand...
Click to collapse
Already tried Used both windows 7 and windows vista drivers.
Oh well.
I installed the SDK and some hacked HBOOT drivers. Doesn't work. I'll have to try new methods
phoenixbennu said:
Ive come to find that adb will recognize the device, but not in fastboot mode. Which is the killer, cause thats the only mode I really need it to be recognized in.
Click to expand...
Click to collapse
I've found in some pages that HTC has already uploaded their HTC Sync and that is now compatible with Windows 8. However, still not working for me in 8 Pro.
---------- Post added at 02:02 AM ---------- Previous post was at 01:55 AM ----------
Ruwin said:
I use both ADB and Fastboot on my W8, and never had a problem. Worst case scenario, if you install the drivers but you still have an exclamation mark next to the device in device manager, try and install the Android USB drivers on a W7 machine and copy the files on your W8. Then go to device manager and update the driver, and point to the folder you just copied. This should do.
Click to expand...
Click to collapse
I've uploaded from W7 to W8 pro and my now I'm not able to find a driver that fits my computer. It's a very strange situation.
I have tried pretty much everything lol, its not worth it if you are installing a RUU then windows 8 suddenly stopped detecting your phone then you have a brick. I would just wait till htc releases drivers for windows 8. or installed windows 7 through VMware, like I did.
Just have the device for 1 day and had some issues. Is there any working solution for this? I've spend some time searching and reading, I tried alot of drivers (HTC, from android-sdk and so on)...with all the same issue. Windows 8 recognizes the device as My HTC BUT...adb doesn't. When issuing "adb devices" command, returned list is blank.
Finally I've installed recovery and unlocked on a Windows 7 machine but I don't want to do that each time I flash a ROM (and I flash alot).
Also short question... I didn't saw anywhere clearly stated but from what I've read, I understood there's no S-Off for One S right? I'm comming from Desire S and everything there was flawless.
It is working on my Windows 8 Pro without an issue. I installed the driver which comes together with the android sdk.
1. Open device manager
2. Select the android device with yellow sign
3. right click and select "Update Driver Software ..."
4. select browse my computer for driver software
5. select "Let me pick from a list of device drivers on my computer"
6. select have disc and browse for the "android_winusb.inf" in the android sdk folder
7. select Android ADB Interface and press next
8. select yes, ...
-> adb driver is installed and device should now work with adb.
Best regards,
dexi
dexi00 said:
It is working on my Windows 8 Pro without an issue. I installed the driver which comes together with the android sdk.
1. Open device manager
2. Select the android device with yellow sign
3. right click and select "Update Driver Software ..."
4. select browse my computer for driver software
5. select "Let me pick from a list of device drivers on my computer"
6. select have disc and browse for the "android_winusb.inf" in the android sdk folder
7. select Android ADB Interface and press next
8. select yes, ...
-> adb driver is installed and device should now work with adb.
Best regards,
dexi
Click to expand...
Click to collapse
wbut i can't find android-winusb.inf in my sdk,
can you mention the folder's path?
I'm having same issue but on Win7 also tried many installs and uninstall of HTC drivers, still not recognized plus have my own thread which 2 members tried all they know also tried on my Dad's Vista with a no go? I found my computer recognized my device if u do this, power down ur device than restart ur computer while booting up plug in ur device and sometimes it recognizes it but not always staying connected
Sent from my HTC One S using xda premium
I have Windows 8 Pro Media Center, install drive from htc sync manager from htc site, flashing fastboot, oem lock, etc seem to work in cmd. But odd was if i do adb devices, it just say something like "list device" i don't see my device number.. or i should use fastboot devices instead
Try this:
[Solution]Windows 8 - ADB/fastboot driver problem solved!!
I have the Windows 10 Pro N edition that I recently upgraded to from Windows 8.1. Ever since then my computer will not properly get the drivers it needs for my android. In device manager it only shows it as MTP and when i try to point it to the correct Z5 driver I downloaded from Sony's website it immediately tells me it failed. I assumed the fix would be to download the Media Feature Pack for Windows 10 N versions but I have done that at least 4 times now and still refuses to be recognized properly. The most annoying part is my Windows 7 laptop recognizes it perfectly... Any suggestions are greatly appreciated.
Kirshy said:
I have the Windows 10 Pro N edition that I recently upgraded to from Windows 8.1. Ever since then my computer will not properly get the drivers it needs for my android. In device manager it only shows it as MTP and when i try to point it to the correct Z5 driver I downloaded from Sony's website it immediately tells me it failed. I assumed the fix would be to download the Media Feature Pack for Windows 10 N versions but I have done that at least 4 times now and still refuses to be recognized properly. The most annoying part is my Windows 7 laptop recognizes it perfectly... Any suggestions are greatly appreciated.
Click to expand...
Click to collapse
http://www.howtogeek.com/167723/how...8.1-so-that-you-can-install-unsigned-drivers/
Install Sony PC Companion, it comes with the drivers
Sent from my E6853 using XDA-Developers mobile app