Reading 4 min.

Hello everyone, dear readers and smartphone users. Today I will tell you what to do if the error “USB device MTP refusal” occurs when you connect your smartphone to a personal computer. Below you can see a screenshot of this error. If you have the same problem, then read on.

The error “USB device MTP failure” can occur for several reasons, here are some of them:

1. MTP driver problem. This happens sometimes, but not on all computers. This problem can be fixed very easily and quickly, below I will describe it in more detail;
2. Incorrect settings in the device itself. As practice shows, such a reason occurs in 1% of cases, but nevertheless, it is possible for you that it is the cause of the error;
3. Outdated drivers. This problem also takes place, but, like the previous ones, this cause of the error can be eliminated by simply updating the driver for your operating system.

So, we have sorted out the reasons, now let's get down to fixing this problem. Let's start in order, with the most working and common method to eliminate an unpleasant error.

Method 1

Now reconnect your mobile device to your personal computer and check if the error that occurred earlier has disappeared.

Method 2

If the previous method did not help, then let's try to delve into the settings of the mobile device itself. Follow these steps:

Important: if the development item is not visible, then do the following: go to the "About the device" section and click on the build number about 10 times. Thus, you activate the item "Development".

Method 3

As I said above, this method is also simple and straightforward as the previous ones. It consists in a banal driver update... In order for everything to go as smoothly as possible, follow these steps:

Now try again to connect your Android mobile gadget to your personal computer and check if the USB error has disappeared.

If the article was useful to you, then you can thank the author of the article by publishing a link to this material in your social network accounts, to do this, click one of the share buttons below. Do not forget to add this resource to your bookmarks, I think it will be useful to you more than once during the operation of your Android device. See you in the following, undoubtedly, useful materials.

Previous articles covering this topic were largely devoted to only one protocol - Mass Storage. This is not surprising, it is he who, either in its pure form or bundled with a software shell, rules the market today. Although it was not developed for these players at all, nevertheless, it received the widest distribution here due to its standardization, simplicity, and transparency in use. Moreover, MSC / UMS is being actively implemented in other portable devices: digital cameras, cell phones and smartphones, PDAs.

However, there is a company on the market that believes that the final word in this area has not yet been said. This is Microsoft, which has been aggressively trying to instill in the industry a completely different approach to transferring content to portable devices for three years.

Speaking earlier about the circumstances of the appearance of Mass Storage on MP3 players, we mentioned the injustice that the industry has done towards them. Portable players have been “bypassed” in the distribution of USB device classes, mainly due to the lack of foresight, suspicion shown by the leading companies in the industry, and their inability to create a really working mechanism for protecting copyright.

Now Microsoft is declaring its desire to eliminate this annoying example of segregation. Although, of course, everyone understands that the company does not at all forget about the opportunity to seriously improve its position in the digital entertainment market.

Microsoft's approach to this issue is significantly different from anything that could be found in the industry before. So, it has nothing to do with Mass Storage, it is a completely different architecture, originally intended for portable multimedia devices.

On the other hand, it cannot be equated with proprietary protocols. It is a relatively open technology and is actively licensed by many vendors. In addition, in recent years, Microsoft has been actively integrating its support into its operating systems installed, as you know, on most PCs in the world.

Mass Storage was developed back in the last century. The first information about Microsoft's developments in this direction appeared only in 2003-2004. The new protocol was officially introduced on October 12, 2004 as part of the Microsoft PlaysForSure (P4S) partner program. It was named Media Transfer Protocol (MTP).

PlaysForSure, of which MTP is a part, was first presented to the public at the end of 2004

Zen PMC - one of the first P4S players - did not gain much popularity

At the same time, the first list of compatible devices was announced, in particular, players from Creative, iriver, Samsung.

Within the PlaysForSure Affiliate Program, MTP was far from the top star. Much more attention was paid to its other components:

• media file formats WMA (audio) and WMV (video)
• Windows Media Player 10th version
• new DRM system Janus
• operating system for Portable Media Center players (optional).

Microsoft looked at the prospects of Portable Media Center realistically. Therefore, she was preoccupied with the introduction of PlaysForSure support into the existing varieties of proprietary operating systems for portable players. She quickly found a common language with most platform manufacturers. The new concept, although not without a squeak and not without skeptical and judgmental comments from outside experts, began to develop.

Critics, not without reason, called PlaysForSure a response to, if not a clone of Apple's iPod + iTunes combination. Where:

• WMA = AAC
• Windows Media = iTunes
• Janus DRM = FairPlay
• The stillborn Portable Media Center hoped to become = iPod OS.

The MTP, however, was the original element here. Perhaps only a de facto monopolist in the operating system market could afford such a thing.

The P4S architecture was clearly not created without looking back at Apple's experience.

The protocol, quite in the tradition of Microsoft, was not created from scratch, but was a modification of an existing solution. In this case, it was the proven Picture Transfer Protocol (PTP). Back in 2000, it was approved as a standard protocol for digital cameras and entered the number of USB classes under the number 0x06.

MTP is a direct descendant of the Picture Transfer Protocol, familiar to many from digital cameras.

MTP borrowed a lot from him, starting with two letters in the title. By and large, MTP can be called an add-on over PTP: the entire software part, which is directly responsible for transporting data, has remained unchanged. The set of commands was only slightly expanded to cover new types of content and their interaction with each other.

The fundamental difference between PTP / MTP and Mass Storage is the concept of “objects”. Objects in the TP system can have types and characteristics that can be queried by means of the protocol. Objects are made up of component parts that include links to other objects, metadata, and content itself.

MTP object structure

Thus, TP protocols can be called "smart" protocols that can constructively interact with the firmware of a portable device or a software shell installed on a PC.

Algorithm of MTP work

In fact, the set of TP objects already contains a database of information about the content, which in the Mass Storage system has to be created independently either by the player or using a PC, wasting time and device resources. As a result, the user-friendly functionality of portable players such as displaying metadata and Album Art, a powerful and flexible navigation system, can be implemented with much less "gore", it becomes available to resource-constrained developers as well.

MTP features on the example of Sandisk Sansa e200 - Album Art, metadata navigation, rating system

Has protocol and other capabilities such as creating virtual folders.

Media and Data virtual folders in MTP connection mode, Zen Micro Photo player

“Naked” Mass Storage cannot compete in terms of capabilities. In its pure form, the protocol requires a fair amount of portable device power and a lot of work on firmware, few developers go for it. Thus, the main opponent of MTP is Mass Storage with a shell, which offers similar capabilities.

Here, the advantage of MTP should in the future be its great versatility. If Windows XP acquires MTP support only with the installation of Windows Media Player version 10, then in Windows Vista the protocol is already built in from the very beginning. This will allow users to fully use it without any additional installations.

Plus, unlike iTunes and SonicStage, which work exclusively with Apple and Sony devices, respectively, PlaysForSure is open source. MTP devices can be produced by any company using platforms with protocol support. Nowadays, the vast majority of platforms are compatible with MTP.

Major platform manufacturers support MTP

MTP can be used with any file system. This allows developers to create dual-protocol players with support for both Mass Storage and MTP. Usually, the user can choose which mode the device should work in through its (device) settings. Microsoft, however, looks at this practice very askance. In the latest specifications of PlaysForSure, such feints are completely prohibited. Now MTP has priority, and the Mass Storage protocol is activated only if no drivers supporting Media Transfer Protocol were found on the PC. Below it will be described to what troubles this can lead.

Fortunately, no one is tying developers to the PlaysForSure specs. This is something that protocol critics often forget: the player manufacturer can send both PlaysForSure and Janus DRM without any problems, while retaining MTP support. This allows them to ignore Microsoft's recommendations and allow the user to choose the protocol they like.

Choosing between MSC and MTP (from the Sandisk Sansa e200 user manual)

Curiously, the priority of the MTP protocol over the PlaysForSure concept as a whole was unwittingly demonstrated by Microsoft itself with the release of its own Zune player. The latter is not a P4S device, does not support Janus DRM, but uses MTP nonetheless.

Having listed a number of obvious advantages of the protocol, we, however, cannot close our eyes to a number of serious disadvantages that reduce its attractiveness to the consumer.

Perhaps the main root of all the troubles is that MTP came too late. In 2004, the MP3 player market hit six years. Naturally, by this time the majority of market players had somehow solved the problem of choosing a protocol for their devices, preferring Mass Storage in one form or another.

Moreover, the first version of MTP was seriously inferior to MSC / UMS in terms of user friendliness. She forced him to install Windows Media Player 10, did not have support in Explorer Shell Extensions and, as a result, did not allow him to see the device from Windows Explorer, copy files using Drag & Drop, and use a portable player to transfer data. Finally, in other operating systems, be it macOS or Linux, protocol support was very bad. Compare that to Mass Storage, for which drivers can be found even for DOS.

For some users, an additional negative factor was the simultaneous announcement of Janus, a new DRM from Microsoft, with MTP. Of all the PlaysForSure bunch, it was Janus that received the widest promotion. The American company repeated the mistake of the SDMI contributors, widely touting the new DRM as some kind of remarkable advantage of the PlaysForSure architecture. The result is an unambiguous association of PlaysForSure = DRM => and MTP = DRM. And Mass Storage, on the contrary, = Freedom.

Along with FairPlay from Apple, PlaysForSure received its portion of slop from the Internet community

DRM-friendliness is indeed one of the differences between MTP and PTP. Thus, information related to DRM is included among the types of protocol objects. However, the MTP architecture does not include DRM as a required component at all, it simply makes it easier for developers who need it to implement it. In other words, MTP supports DRM, but MTP does not = DRM. Despite this, it is widely believed that MTP is essentially just a copy protection measure, that it "embeds" DRM into copied files, and the like. Microsoft's controversial reputation has fueled these myths - many expect a trick from Microsoft's products.

Microsoft has traditionally been one of the most heavily criticized corporations for their adherence to DRM. Campaign banner against Windows Vista from anti-DRM activists from defectivebydesign.org

As a result, by announcing MTP as part of PlaysForSure, Microsoft rendered the protocol a disservice by "hanging" all the negative from other program components on it: DRM, Windows Media Player. This is despite the fact that of the entire P4S set, MTP was perhaps the most successful and viable component.

On the other hand, some of the music is purchased by Western users in online stores using P4S architecture and Janus DRM. Such tracks will only be played on MTP players. Although the future of DRM in music is rather vague right now, it is difficult to say whether its support will remain an advantage.

Shortly before her death, Rio Audio campaigned for MTP, illustrating this with diagrams showing the horror of the impossibility of recording PlaysForSure tracks on an MSC player.

Another cons is the intrinsic complexity of the MTP architecture. If Mass Storage is actually managed with one driver, then Microsoft has built a whole structure for its protocol. It is an API called the "Windows User-Mode Driver Framework (UMDF)", which can be roughly called "DirectX for Peripherals." Today this architecture is more widely used, but it was developed specifically for MTP and in 2004 was included in the installation of Windows Media Player 10. Support for the data transfer protocol is implemented here with a whole set of drivers and libraries. This makes the system more vulnerable and unstable.

In particular, such a situation occurs. Most of the MTP drivers included in the UMDF are installed on the PC. But Windows Media Player version 10 or higher is not available, the libraries responsible for integrating MTP into the standard Windows shell (Shell Extensions) are also missing. The result is that the player is recognized by the system as an MTP device, but there is no way to work with it, the device becomes a “thing in itself”. If the player can be switched to Mass Storage mode via the menu, then it's not so bad. But if it is designed according to the PlaysForSure specification, then, upon detecting MTP support by the system, it will work exclusively using this protocol, depriving the user of the opportunity to fully use the device. Of course, such phenomena are a consequence of the youth of the protocol, its insufficient prevalence, in the same "Vista" this will not happen. However, critics rightly point out the complexity and severity of the MTP infrastructure as a disadvantage.

Work on improving MTP is underway, its latest versions already look much more interesting. The protocol has now been integrated into Explorer, thanks to which working with an MTP device is not much different from using a Mass Storage player (although there is no correct support in alternative file managers yet).

The only significant difference between the MTP integration into the Windows shell from the usual Mass Storage is that MTP players are displayed as devices, not as disks (screenshot from "dapreview.net")

The PlaysFromDevice standard is developing - MTP support by third-party equipment, such as stationary audio systems, car radios, etc. Its absence was another serious disadvantage for MTP players, since There are already quite a lot of techniques that “understand” Mass Storage.

If we abstract from the fact that MTP is, first of all, Microsoft's tool for conquering and retaining the market, most of the ideas embodied in the protocol can be assessed positively. In its latest variation, it surpasses the most common system in terms of convenience and capabilities - Mass Storage with a shell.

Thus, the user is given a full choice between using the Windows Media Player software shell and Drag & Drop through Explorer. MTP players can be used to transfer any data without any problems - the lack of this feature was one of the main complaints of users. Protocol support for third-party operating systems is gradually emerging.

An alternative to working through Explorer is synchronization through Windows Media Player 11

If we imagine a world where all PCs, all home audio equipment and other related devices “understand” MTP, then for multimedia players it looks more attractive than Mass Storage.

Error messages that a user of MTP devices may encounter (more details)

Microsoft has already managed to seduce three big five players with this prospect: Creative, Sandisk and Samsung. From the "second echelon" in the camp of the company from Redmond iriver, Archos, Philips, Trekstor, Cowon, Mpio, many other small companies.

Most of the supporting producers support MTP

Slowly but surely, MTP is spreading among Chinese companies - some small Asian manufacturers are already claiming support for the protocol as an advantage of their products. Their complete for this protocol looks quite real, tk. most of them work exclusively for Europe and the USA, where people are gradually getting used to MTP.

Chinese company Meizu is already equipping its players with MTP support

And against the background of the theoretically possible general rejection of DRM, even the use of MTP by Apple does not seem completely impossible - nothing prevents the integration of protocol support into the iTunes shell.

And yet, for now, there is a feeling that MTP has not yet crossed the line separating just widely advertised technology from technology that has received real public recognition.

Today, the owner of an MTP player is still sometimes forced to face problems that still tormented users of players with proprietary protocols: opaque operation, incompatibility with hardware, the need to install additional software.

The protocol is still quite shaky, and without Microsoft's decisive action, it could easily sink into oblivion. In some ways, the situation resembles the situation with the MP3 format and its alternatives. Just like MP3, Mass Storage offers a sufficient level of capabilities and is widespread, so there is really no serious incentive to switch to the new protocol. Similar to alternative audio formats such as WMA and AAC, MTP is implemented "from above", in an "order" manner.

Microsoft hopes to improve the situation if it succeeds in registering MTP as a new class of USB devices. This will make the protocol the industry standard. The ambitions of the American company go further - it hopes to "drive" all portable media devices under this protocol - cameras, cell phones, smartphones - leaving Mass Storage only storage devices for which it was, in fact, intended.

What will the future hold for data transfer protocols in portable players? Will MTP Become the New Industry Standard? Or will Mass Storage keep its positions? Perhaps there will be new solutions? It is difficult to say for sure: everything in this industry depends too much on subjective factors, in particular, the actions of the largest players. So far, the Mass Storage protocol remains king, first of all, in the edition from Apple, with a software add-on in the form of iTunes. "Pure" Mass Storage remains the domain of budget players and devices for enthusiasts, occupying the second step of the pedestal. MTP, which is spreading in the middle class of the market, is still the third.

Schematic distribution of shares between protocols in 2006 sales.

Time will tell what changes will be made by the fall of DRM (if it does happen), as well as the spread of wireless technologies.

FSP has announced the 80 Plus Bronze Certified Hydro Series Power Supplies. So far, the line includes three models of 500W, 600W and 700W. All of them are capable of powering PC systems with power-hungry graphics cards, thanks to the stable and powerful + 12V rail. The presence of the 80 Plus Bronze certification means that the efficiency of new products can reach 88%.

FSP Hydro Series 80 Plus Bronze PSUs are equipped with a 120mm fan controlled by a controller. The rotation speed of the propeller blades is determined depending on the load. Thanks to the clever design, the level ...

Cryorig has unveiled prototypes of the first LED coolers in its range. The new Lumi Edition and Lumi RGB + Edition H7, unlike most solutions that use LED fan illumination, offer a completely different approach to illumination: illumination of the entire radiator area. To implement such a unique project, the manufacturer had to develop special components using numerical control such as CNC.

The cooler Cryorig H7 has entered the Cryorig H series, whose representatives are characterized by high performance and ...

Mid-range motherboards are always at their peak due to the symbiosis of good equipment and reasonable prices. In addition, these solutions are able to satisfy the needs of a fairly wide audience. These criteria are fundamental for Asus products, which are famous for their excellent component base and a large number of interfaces. The Asus Z87-C is a bright representative of the mid-price segment, capable of offering the maximum at a rather pleasant price - only $ 140. Let's see what else ...

Today, a huge number of people use mobile devices on an ongoing basis, but not everyone is able to “make friends” with a computer. We will devote this article to an analysis of how to troubleshoot the problem, expressed in the impossibility of installing a driver for a smartphone connected to a PC.

The error discussed today occurs when the phone is connected to a computer. This happens for various reasons. This may be the absence of necessary components in the system, or, conversely, the presence of superfluous ones. All these factors prevent the correct installation of the media driver for mobile devices, which allows Windows to communicate with the smartphone. Next, we will consider all possible options for eliminating this failure.

Method 1: Editing the system registry

The registry is a set of system parameters (keys) that determine the behavior of the system. Some keys may interfere with normal operation for various reasons. In our case, this is the only position to get rid of.

If the keys are not found or the method did not work, then the system lacks the required component, which we will talk about in the next paragraph.

Method 2: Installing MTPPK

MTPPK (Media Transfer Protocol Porting Kit) is a driver developed by Microsoft for interacting a PC with the memory of mobile devices. If you have a "dozen" installed, then this method may not bring results, since this OS is able to independently download such software from the Internet and it is most likely already installed.

Installation is very simple: run the downloaded file with a double click and follow the prompts "Masters".

Special cases

Conclusion

As you can see, it is not so difficult to solve the problem with the detection of mobile devices by the system, and we hope that the given instructions will help you with this. If all else fails, it is possible that a critical change has occurred in Windows, and you will have to reinstall it.

This document will guide you through the installation of the Intel® USB Driver for Android * Devices, which will enable you to connect your Windows * device to your Intel® Atom ™ processor-based Android device.

System requirements

Hardware Requirements:
Android mobile device based on Intel Atom processor, excluding SoFIA
Micro-USB to USB cable (cable used to charge the device)

Supported computer operating systems:

Windows® 10 (32/64-bit)

Windows 8.1 (32/64-bit)
Windows 8 (32/64-bit)
Windows 7 (32/64-bit)
Windows Vista (32/64-bit)
Windows XP (32-bit only)

Supported Android device operating systems:
Android 2.3.7 - Gingerbread (GB)
Android 4.0.x - Ice Cream Sandwich (ICS)
Android 4.4 - Kit Kat
Android 5.x - Lollipop

Installation steps

Note: During the installation process, do not connect your Android device to your computer.

Supported USB profiles

After installing the USB driver package, connect your Android device to your computer using a micro-USB to USB cable. The following are the USB profiles used by the Intel USB Driver Package for Android:

• ADB (Android Debug Bridge). This is the Android debug interface. It is mainly used for flash upgrades and debugging.
• MTP (Media Transfer Protocol): It is the Windows protocol for transferring media files.
• PTP (Picture Transfer Protocol): It is a protocol for transferring images from digital cameras to computers.
• RNDIS: This feature creates a virtual Ethernet link using the telephone network.
• CDC Serial (Modem AT Proxy): This function creates a communication channel with the modem for using AT commands through the virtual communication port:

Troubleshooting

1 / The device is not detected at all

• These drivers are for Intel® devices only. If you are using a device manufactured by one of the OEMs, please obtain the drivers directly from the manufacturer's website or use the links provided by Google.

2 / I'm getting errors in Windows Device Manager

• Open Windows Device Manager:
  • You can find the element USB Mass Storage instead of ADB Device. In this case, right-click the Mass Storage device icon and select 'Delete'.
    
  • You can see Android device icon with yellow exclamation mark... In this case, right-click the Android device icon and select 'Uninstall'.
    Then disconnect the device from the computer and run the driver installer again.

3 / Portable device is displayed but there is no Android Debug Bridge (ADB) profile

You may not have enabled the USB Debugging option.
By default, the developer options are hidden on your phone. Open the settings menu on your phone and find the section About the phone... Scroll down and find Assembly. Press it five times and you should see a small dialog informing you that you have activated the developer features.
Return to the main settings menu and open Developer options and then turn on BeDebugging.

4 / I am still using Windows XP. After activating MTP, a pop-up dialog does not appear, which should open access to the phone's file system or transfer media files.

By default, MTP is not supported on Windows XP. You must install Windows Media Player 10 or later.

Additional questions and support
For other troubleshooting support, post your questions on the Intel Android Developer Support Forum at: ()