Support Fixed MTP device error with Samsung Galaxy

Thank you very much for that detailed information.

 

I am using windows 7. Is there another way to do this on this OS????

 

I have a win 7 pc also, what I did for this phone is change it to media player mode in the usb settings, it installed the drivers correctly right away and I haven't noticed any problem with it on the phone.(although I did only put songs on the external sd card and not the internal)

If you want to do this you just go to settings in the phone and to "about phone" at the bottom, then just change the "usb setting" to media player. Didn't try any others as this worked for me.

Hope this helps and if this may cause an issue on my phone please let me know...

 

Tried all but didnt work. Then i took help of Odin. Now i am on 2.3.4 gingerbread. Updating through odin took me only 15 mins or so once all drivers, Odin itself and the set up files are downloaded. I am recommending upgrade through Odin to all who are still stacked because of dumb Kies. there is a forum post by Mr. Kapil at androidsoul which has got a very clear and easy set of instruction.

 

I live in Asia and yesterday a friend brought me a Dutch Galaxy GT-i9000. Firmware was old and I went to the Dutch website from Samsung and downloaded Kies and instillation was a matter of 15 minutes and now I have Gingerbread smoothly running on the Galaxy.
Seems that ( perhaps with some luck ) things also can work smooth.

Wish that others also nod have problems and a positive posting sometimes also can be nice.

 

Hi Sizzlingice,

I do not have winusb.sys at all in my system..what can I do..It has been a big problem for me as I have not been able to do much with my galaxy s2.

My laptop recognizes all other usb devices.Not sure what is so unique about galaxy s2 though that the system is not recognizing it.

 

Hi SizzlingIce...Thank you very much... You saved my day.. Working for my mobile galaxy. Im able to connect kies now.

 

I must have wasted a day or two on and off idly trawling the Internet looking for solutions:

Windows XP SP3, Samsung Galaxy Tab 8.9 with 3.2, latest Kies, and latest everything else.

This thread led me to a solution but all I did was reinstall Windows Media, connect the Tab again and, boomph, it worked first time. No deleting drivers, nothing, and what's more the Windows Media version I had was the current version which I reinstalled over anyway.

Hope this shows up prominently in Google searches so others don't waste as much time as I did.

 

I found a solution that worked. Below was the method I used, followed by further explanation. You may not need to follow these steps exactly, but they're the steps I used.

1) Plug Samsung Galaxy S3 phone into computer's USB port. You will get the MTP driver failed to installed message.

2) Backup SMS / MMS using a backup app (like MyBackup Pro).

3) Factory reset phone (while still plugged into computer).

4) Do NOT sign in to your Google Account when phone resets - This is CRITICAL. You can do it later.

5) Basically, just get the phone started up again without signing into any accounts (like Dropbox, Samsung account, etc.)

6) MTP driver should have automatically installed on computer - if not, then unplug phone from computer and reconnect.

7) Sign into your Google Account, and feel free to re-customize your phone at this point.


Explanation and Notes:

1) I factory reset my phone 2x in a row. The first time, without doing ANYTHING on the phone after factory resetting it except for signing into my Google Account, the MTP driver failed to install. I believe this happens because signing into my Google Account uses the "backup and restore" functionality of the Google Android account and Google starts automatically downloading saved settings like home screen, Wallpaper, Play Store apps, and other settings. This interferes with the initial MTP driver installation. The 2nd time I factory reset (within minutes of the first factory reset), I did NOT sign into Google Account, and voila, the MTP drivers installed. Only AFTER I was able to connect to the computer did I sign in to Google Account.

2) Previous to this solution, I had tried every solution I had found online including:

a) checking / unchecking USB debugging mode
b) toggling between MTP mode and Camera mode
c) changing some hidden Android settings
d) using different USB cables (the one that came with the phone along with others I had)
e) uninstalling and reinstalling the Samsung drivers
f) uninstalling and reinstalling Samsung Kies
g) Device Manager in Microsoft Windows - deleting everything under Universal Serial Bus Controllers so it would reinstall upon Windows restart
h) cleaning registry
i) trying to connect to different computers (it didn't work)


I had initially thought it was a computer problem, but then realized I was using MTP to connect other devices (like a Sony videocamera). The problem was with the Google Account automatically downloading various settings to the phone (because of the Backup and Restore functionality) PRIOR to connecting to the computer.


For those of you who have tried everything suggested online to connect to the computer, I hope this solution helps!

 

Brilliant!

I have been working for a couple of days myself, trying all of the suggestions, installing and uninstalling drivers/kies etc., visiting support sites and forums. With fingers crossed I installed Windows Media Player 11 and rebooted. I plugged my phone in and voila! MTP Access!! This is the only place I've ever seen mention of this. It would be great if the word gets out so that others may not go through the headaches that we have.

Thanks again StuffDabbler!

 

Hi,

i was also having the same issue when i purchased my gnote. i format it several time and updated it to final version 4.0.4. but MTP error was still scratching my head. Finally i got the solution. Keep it in mind that there is no problem with your PC neither with gnote. the main culprit is the APPS which you would have downloaded that prevent gnote to get connected to the PC due to some crappy security reasons. Do this to solve the issue:

1. go to settings>security>device administrators.
2. delete what ever is the device administrator since it is creating problem in your note due to some security reasons.
3. BOOM problem solved.

Now connect your gnote to PC. KIES will detect it and you are done.

Regards,

VRS

 

Tried regressing to older version, and that doesn't work anymore either.

Doing this for XP and Window 7 Professional is bust too, which didn't give me any problems in the first place!

No problem with the MTP driver now under both operating systems, my Tab appears in the file system of both computers, its just this KIES and the only problem is how do I get ICS when/if it arrives?

Life's too short and I have a proper job to do rather than frigging around with this dumbass piece of software that is KIES.

 

Thank you for your solutions, this worked for me:

Samsung Galaxy nexus phone, Windows XP SP3, latest everything

After trying thousand things: I had simply to re-install Windows Media 11 - and everything is fine.

Puh, this took me two days searching around. Hope it helps others.

 

sizzlingice's method
easy and quick,

this works for me, thanx!!!! gt-p6200.

 

I also had this same error, but I found a different solution. After trying all the software/registry fixes, I thought there might be a hardware problem somewhere. I tried swapping the USB cord, but my phone was finally recognized properly when I plugged it into a different USB port on my computer.

 

It didnt work for me ....!!!!
then, I just gave up and used Odin only to update my SGS2 (GT-I9100) with new firmware (4.0.4) ...
For some reason, my phone was reset to factory defaults...!!!
Then Guess what happened ??!!
Kies worked normally and been able to connect normally and backup my phone ..
Then, happy with this, I continued installing my applications on phone ....
Until ...
I configured the "Microsoft Exchange Activesync" .....
I connected my phone again to PC, Kies stopped working again ...with same error message ... (searching for preconfigured folders).
Then, I could analyse it and find the reason ...
ITS DUE TO ADDITIONAL SECURITY RESTRICTIONS THAT ARE INFORCED BY ActiveSync ADMIN.
When I installed ActiveSync, it tells that I must put screen password and let remote administrator manage my security.
it seems that there is a "bug" in Kies with this and hope I can report the issue to Samsung.
I tested my assumption by removing ActiveSync account totaly and in fact i connected to Kies normally ...!!!
Please make sure that non of your applications is puuting additional security on your phone.

 

seems to be an old thread but i will post maybe it still usefull for somebody also the problem persist with many of the moden phones, i tried many solution inluding many posted here and no one works for me , many thing can make this happen, in my case it was the norton antivirus my galaxy s4 worked fine until one automatic update of the security polics fron android then the error 10 apears , it drive me nuts 2 months until i figure out to uninstall the norton anivirus from the phone , it was all the problem so i changed to avast antivirus it seems that that one doesnt causes that problem. in conclusion , before moving the regedit from you computer try uninstalling the programs in your phone that uses special permisions or security protection or even multimedia sync. majybe one of them are making a hardware conflict. Hope this help somebody

 

i can tell you, that if you have rooted your phone and played with starp-up programs, then you could turn off some services ( i turned off ****ing MTP-service! Ha ha how stupid I was!!! It was just so ****ing simple! Good luck fellas!

 

HELLO!! thanks and GOOD NEWS everyone!! I did it!

 

I'm sorry I düthink it didnt work...

 

yes my first post is true just try

 

HERE is a SIMPLER FIX.

I signed up just to comment on this issue. It's a plague, but there is a much easier approach. People are drowning in a spoonful of water, and the issue is like a storm in a teacup.

But first, understand what is the cause or skip and go to the solution below: This problem is caused by trying to root your phone (unsuccessfully or successfully) and/or installing the debugging USB drivers instead of the "Android MTP" driver, or simply because we're all idiots and mess around with our drivers at one point or another, then we forget what we did wrong and just live with the problem for a while until we can't take it anymore. In any case, you simply you have the driver, but you don't have the driver in operation. The fix is much simpler than you imagine, and simpler and quicker than what the person is writing in the initial thread, without messing with your computer system files.

First things first, make sure in your android device options you select MTP instead of PPT. Don't worry if it is not recognized by windows explorer -- window's knows you've plugged something in, but we need to tell windows what it is by using the correct driver.

With your device plugged in in MTP mode, even if it isn't being recognized, do the following in your windows PC (the windows version matters little, and the steps are the same):

1. Go to device manager
2. find ANY device that has a description such as "Android Debug Bridge (ADB)" (or look specifically for the acronym "ADB"). This bridge is what is causing the problem. Search carefully, you'll find it.
3. right click on it and select "update driver software"
4. select "Browse my computer for driver software"
5. select "let me pick from a list of device drivers"
6. select "MTP (Android) USB Device"
7. click ok/next.

Done.

Your device should immediately appear as MTP (Media transfer protocol) and your videos will also appear in windows explorer -- some people complain that they can't see videos when they connect android devices to windows, well it's because the connect as PPT, (the picture-only transfer protocol).

If this does not work, you have messed up/disabled windows services dependencies to the service and driver.

 

Hey guys,

I wanted to note that I have an s6 edge and was experiencing the same issues. My resolution was to use the original cable that the phone came with to do my sync to PC. If are having issues please try this as it might resolve your problem.

 

OMG this solution that you gave (ORIGINAL POST FROM LIKE 2011) is CRAZY. You know you have to go into PERMISSIONS and CHANGE THE OWNER in order to get this to even let you change the name of those 2 drivers? What are you trying to do to me? This was not my solution at all, but I did solve it and I'll tell you how. (note, it's 5 years later, and the drivers must be downloaded to solve this problem, but it's a piece of cake)

EDIT: Ok adding to the frustration, this solution offered, which helped the device initially to be recognized, also did not work. Since we're discussing samsung galaxy here, and I have another page open with links, that I just used, I will give that to you which should further solve your problem. (As my problems have finaly also been solved). See my biggest problem was that I had AN OLD VERSION OF SAMSUNG PHONE DRIVERS DOWNLOADED. This is a big problem as my MTP Driver was continually popping up with the RED X. So I finally decided to get the right drivers, same as I used to have. I uninstalled drivers from Control Panel on the PC, and I installed the correct driver from a driver search for my phone and downloads. This should work for you, (I can't seem to add a link cause it says it's spam in edit window)

Make sure you download this driver and keep it in your C drive in a special folder just for your phone that you are working with. This organization of files for your phone, should help you in the future if you need to go back and problemsolve or troubleshoot after a long period of inactivity with your device. My phone the Galaxy Core Plus worked with the driver in the "Galaxy Core" subheader on that page of drivers. Quick 9.03 MB download, which is a .exe file I can always run to recreate my drivers in the future. Very handy to keep on hand. The old driver file which was giving me the trouble today, after my initial disconnect with problems of my phone (If someone could splain to me why this happens so much, I would be impressed) was 15 MB. It was the WRONG driver. Now I'm up and I have transfered the file that I meant to transfer, and everything is alright. Good luck to you