Related
I recieved my N4 yesterday.
When I try to connect it to my notebook (running Windows 7 Professional), the installation of the MTP driver fails. The error message says something like "driver could not be found". ADB however works without problems. (I allready debugged some apps on the phone.)
I tried installing the drivers from the toolkit, but it didn't work.
On my brothers netbook the MTP drivers were installed successfully. But I can't get it working on my notebook.
Can anyone help me?
mseebass said:
I recieved my N4 yesterday.
When I try to connect it to my notebook (running Windows 7 Professional), the installation of the MTP driver fails. The error message says something like "driver could not be found". ADB however works without problems. (I allready debugged some apps on the phone.)
I tried installing the drivers from the toolkit, but it didn't work.
On my brothers netbook the MTP drivers were installed successfully. But I can't get it working on my notebook.
Can anyone help me?
Click to expand...
Click to collapse
I was just having this problem but I fixed mine by changing the USB port. Not sure if itll help but worth a try.
bigcrav said:
I was just having this problem but I fixed mine by changing the USB port. Not sure if itll help but worth a try.
Click to expand...
Click to collapse
Thanks for your help. I allready tried an other usb port. It did'nt work.
I wanted to avoid it but I reinstalled windows. Now it works. Thanks again.
Hmm, messed with this problem for ages yesterday, mtp installed fine in normal mode but refused when in 'usb debugging' mode
simple fix, find your wpdmtp.inf file in windows/inf
edit it like shown, look for the [Generic.NTx86] and [Generic.NTamd64] entries near the top of the file........
[Generic.NTx86]
%GenericMTP.DeviceDesc%=MTP, USB\MS_COMP_MTP
%GenericMTP.DeviceDesc%=MTP, USB\VID_18D1&PID_4EE2&MI_00
[Generic.NTamd64]
%GenericMTP.DeviceDesc%=MTP, USB\MS_COMP_MTP
%GenericMTP.DeviceDesc%=MTP, USB\VID_18D1&PID_4EE2&MI_00
...then update the driver in device manager, use automatic search
just make sure the 'VID_18D1&PID_4EE2&MI_00' matches your device id, check in device manager.. but i'm guessing all nexus 4 are the same.. usb debugging mode
I did a clean install of windows and that solved the issue for me. Thanksfor your help anyway.
I usually see what drivers do install, like adb or whatever, and then remove/uninstall them AND delete them
Then installed this pack
http://forum.xda-developers.com/showthread.php?t=1998650
then connect to a different USB port and try again with the new drivers
Also, some USB hubs can be under-powered and cause problems.
meangreenie said:
just make sure the 'VID_18D1&PID_4EE2&MI_00' matches your device id, check in device manager.. but i'm guessing all nexus 4 are the same.. usb debugging mode
Click to expand...
Click to collapse
Just FYI, just got a Nexus 4 from T-Mobile yesterday and the device ID is slightly different:
VID_18D1&PID_4EE2&MI_01
01 at the end instead of 00
---------- Post added at 09:11 AM ---------- Previous post was at 08:53 AM ----------
Fitchman said:
I usually see what drivers do install, like adb or whatever, and then remove/uninstall them AND delete them
Then installed this pack
http://forum.xda-developers.com/showthread.php?t=1998650
then connect to a different USB port and try again with the new drivers
Also, some USB hubs can be under-powered and cause problems.
Click to expand...
Click to collapse
How/where do you install those files/drivers? There are no instructions.
lannister80 said:
How/where do you install those files/drivers? There are no instructions.
Click to expand...
Click to collapse
When Windows asks where the drivers are you point to the folder with the ones you want to use...
EddyOS said:
When Windows asks where the drivers are you point to the folder with the ones you want to use...
Click to expand...
Click to collapse
It doesn't ask. I plug in the phone, and Windows says it can't install the MTP driver.
If I go into Device Manager and find the phone (with the yellow triangle and !) and select Update Driver Software, then navigate to the i386 folder from the Universal Naked Driver (on an i5 system), it tells me that "The best driver for your device is already installed" or something similar.
Of course, if I uninstall the device from device manager (and presumably the bad MTP driver as well), it disappears, so I have nothing to point to to install the drivers.
Earlier today I reinstalled the drivers for my N4 on my work PC (Vista Business) and I had to reboot before it recognised the N4 as an MTP Device - prior to that it only saw it as an 'MTP Device'. Now it sees at 'Nexus 4'
I have a similar problem I have a kindle fire
I have install the ADB driver but am having extreme difficulties getting the MTP drivers to work
I have tried everything (every solution on Google)
and nothing works
I've tried the "Media Transfer Protocol Porting Kit"
I tried to get Microsoft help they gave me the run around and confused me even more
here is the conversation
Microsoft: "Thank you for that information
Nathaniel I was checking your product key and it is blocked that is why you can not connect these devices to your computer, you may be a victim of counterfeit software so in this case since it is an OEM computer which means that the manufacture of the computer installed Windows 7 on your computer I recommend you to contact the manufacture of your computer to see if they have an option in order to resolve this issue you are having."
me: when i contact them what do I ask for?
Microsoft: You need to ask for a new product key
me: I am confused what does this mean? that the manufacturer put windows 7 OS on here illegally? but all PC's come with windows OS so every PC in the world is suspect to counterfeiting
them: No, this could be because someone still some information of your computer and use the product key to try to activate Windows until the product key got blocked
No, the name is not involved in this case it is jut the product key
what do I do?
is there an alternative to MTP drivers?
Solved
Hi, i had the same problem described in previous posts and I managed to solve thanks to what is written by meangreenie.
In practice, in the windows\inf of my Windows 7 the file wpdmtp.inf was no longer present but there is only the "compiled" version (wpdmtp.pnf).
I retrieved the file from an earlier version founded in he folder Winsys and so the LG driver are installed without further problems.
Jon McDougal said...
You might be using the wrong driver (Android ADB) instead of the MTP driver. This happened to me the other day!
If you're in Debug Mode, you've already done the first step I was going to suggest.
Here's the second step that worked for me: Open Device Manager -> Click Android Device (top of my list) which exposes "Android Composite ADB Interface" -> Right click that device -> Update Driver Software -> Browse My computer for driver software -> Let me pick from a list of device drivers on my computer -> then choose "MTP USB Device" -> Next
Mine installed the MTP driver and then the N4 opened normally.
Click to expand...
Click to collapse
That works for me with USB Debug ticked and in MTP Mode but not in PTP Mode (on CM10.2-nightly-20130817). I absolutely can't see my pics in no way... (I suppose this is a bug from Google to be fixed in further updates). ADB and FB are correctly working as tested with NexusRootToolkit 1.7.1 Drivers Test.
May it help to delete original DCIM folder and start from a new one??
edit: Shame on me... I forgot that I've formatted my SDcard, so I've no picture in DCIM folder.... Sorry! So I can say that McDougal trick totally worked for me!
try to check the device manager to check the missing drivers with ! mark
Maybe I'm not completely getting the problem, but just doing this worked fine for me:
danielms22 said:
Enable USB debbuging in your phone. Go to Settings -> about phone -> tap about 10 times on build number item until USB debbuging is unlocked.
Also, on your computer go to the device manager, look for your phone, if you find it, right click on it, then update Driver Software, browse computer, Let me pick from a list of device drivers on my computer, USB composite device
That should do it.
Click to expand...
Click to collapse
No need for additional driver download or anything...
Finally a working solution
Finally I found a solution.
Visit answers.microsoft.com/en-us/windows/forum/windows_xp-hardware/mtp-usb-device-drivers-will-not-install-correctly/0ee71b7c-4ae7-403f-abbb-63c7ed9a79f9?rtAction=1387606800207 and search for the "Bret B"'s answer which has also been marked as the most helpful answer. It works perfectly. He simply says..
Go to the Registry Editor (Start –> Run –>type in, “regedit” (without the quotes) then click OK.
Search the following key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Class\
Go upto Edit>Find, type in or copy/paste Portable Devices
In the right hand pane you will see the (Default) value “Portable Devices” on the string
Once found, you see a string value called UpperFilters –> delete it!
Reconnect the device. Finished!
Hi,
Just got a Nexus 4, had a Galaxy S2 before. The problem is that I can't get it to be recognized in Windows 7 x64. Nothing really happens, I plug it, it starts to charge but nothing more, no icon appearing at device manager etc. Tried to install the drivers via nexus 4 toolkit and nothing changed, tried on another windows 7, a notebook and its the same. Changed the USB cable, no difference. Charging and nothing more.
I searched on internet and found similar issues but didn't find a solutions.
PS: Its a new phone, never unlocked or rooted.
Works here dude download latest android SDK and go to device manger on computer update drivers
alkasber said:
Hi,
Just got a Nexus 4, had a Galaxy S2 before. The problem is that I can't get it to be recognized in Windows 7 x64. Nothing really happens, I plug it, it starts to charge but nothing more, no icon appearing at device manager etc. Tried to install the drivers via nexus 4 toolkit and nothing changed, tried on another windows 7, a notebook and its the same. Changed the USB cable, no difference. Charging and nothing more.
I searched on internet and found similar issues but didn't find a solutions.
PS: Its a new phone, never unlocked or rooted.
Click to expand...
Click to collapse
Get Wug's toolkit. http://forum.xda-developers.com/showthread.php?t=2015469
Follow the directions for installing the drivers. Really follow them exactly.
a g bell said:
Works here dude download latest android SDK and go to device manger on computer update drivers
Click to expand...
Click to collapse
Did it and again nothing happens.
Dungeon47 said:
Get Wug's toolkit. http://forum.xda-developers.com/showthread.php?t=2015469
Follow the directions for installing the drivers. Really follow them exactly.
Click to expand...
Click to collapse
Installed the toolkit, folowed the instructions but the problem still there. The problem is that when I connect the phone I don't get the "connect to usb" familiar sound but the charging starts. So is not that the drivers are wrong or bad, the problem is that is that the phone doesn't even shows as something in device manager.
Go to your phone settings.... then click on about phone....
then scroll down and hit the "build number 10 times" that will unlock the developer menu
then go back to "about phone" scroll down to the developer menu.
then check box for "usb debugging" and the computer will see the phone.
Had this problem too the first time i got my Nexus 4.
It frustrated me for the first couple of hours when i could'nt connect it to my pc, and no solution seems to work.
However, i found the solution. This was: Install the latest version of Windows Media Player.
This phone uses MTP, instead of mass storage, and thus needs WMP.
Link to Windows Media Player download:
http://windows.microsoft.com/nl-nl/windows/download-windows-media-player
kthejoker20 said:
Go to your phone settings.... then click on about phone....
then scroll down and hit the "build number 10 times" that will unlock the developer menu
then go back to "about phone" scroll down to the developer menu.
then check box for "usb debugging" and the computer will see the phone.
Click to expand...
Click to collapse
Its not that, this was the first thing I tried.
mumaster20 said:
Had this problem too the first time i got my Nexus 4.
It frustrated me for the first couple of hours when i could'nt connect it to my pc, and no solution seems to work.
However, i found the solution. This was: Install the latest version of Windows Media Player.
This phone uses MTP, instead of mass storage, and thus needs WMP.
Link to Windows Media Player download:
http://windows.microsoft.com/nl-nl/windows/download-windows-media-player
Click to expand...
Click to collapse
I have the latestes WMP version and anyway, I have a digital camera that works in MTP in this same PC.
This is becoming short of solutions and I beginning to think maybe its a nexus 4 hardware fault.
turn them both off and on again
I have this same problem and haven't found a solution yet!
I have this problem only when USB Debugging isn't turned on. I'm not sure what's wrong with it but by computer (running W8 Pro) won't see my phone until I turn on debugging. All drivers are installed but the only way I can copy files to/from my N4 is with debugging enabled.
Would love to see a solution come through and I'll continue looking for one myself to help us all out.
-Sent from that.... you know.... thing that sends these things-
Same issue.
I have tried over 5 computers running windows 7 and about 5 different usb cables.
I have tried having usb debugging checked, unchecked, MTP on/off and PTP on/off.
Still nothing.
Im having this problem too. I tried in 4 different pc's and a mac. My nexus 4 cant be detected. Its just charging. Weird thing is that no "Charging (USB)" on my lock screen just "Charging"
i had the same problem and read everysingle forum and finally found the working solution
Device Manager - right click device (Android ADB OR Nexus 4 ADB interface)
- Update Driver Software
- Browse my computer for driver software
- Let me pick from a list of device drivers on my computer
- then choose "MTP USB Device" OR "USB composite driver"
- Next
here you go instant discovery
make sure you are on MTP and USB debugging is on
yacbos said:
i had the same problem and read everysingle forum and finally found the working solution
Device Manager - right click device (Android ADB OR Nexus 4 ADB interface)
- Update Driver Software
- Browse my computer for driver software
- Let me pick from a list of device drivers on my computer
- then choose "MTP USB Device" OR "USB composite driver"
- Next
here you go instant discovery
make sure you are on MTP and USB debugging is on
Click to expand...
Click to collapse
thanks, saved my sanity
You, sir, are amazing.
You Save Me...........
help needed
Same problem here... usb debugging on, but dont know where to find MTP on my phone... probably a dumb question
yacbos said:
i had the same problem and read everysingle forum and finally found the working solution
Device Manager - right click device (Android ADB OR Nexus 4 ADB interface)
- Update Driver Software
- Browse my computer for driver software
- Let me pick from a list of device drivers on my computer
- then choose "MTP USB Device" OR "USB composite driver"
- Next
here you go instant discovery
make sure you are on MTP and USB debugging is on
Click to expand...
Click to collapse
What if Device Manager does not show Android ADB or Nexus 4 ADB Interface? I am having this problem and can not figure it out.
what version of windows r u using
yacbos said:
what version of windows r u using
Click to expand...
Click to collapse
Windows 7. It worked fine for me before the 4.3 update.
Hello guys!
I have already read some topics on this forum but it is my first message.
As indicated in the title, I cannot connect my Nexus 4 on my computer using MTP. This computer is running Windows 8.1 Update 1. So far I have tried every method I have seen on the web so I am a little bit desperate.
I have tried to plug my device on other computers and it was automatically detected on Windows 7, Windows 8.1 Update 1 and Ubuntu 14.04.
On my computer, as it does not auto-configure MTP I have tried to install ADB drivers, hoping it would help me. Universal ADB drivers, Naked Drivers and drivers from the SDK didn't changed anything. I also tried changing USB port.
It always recognised my phone as a "Nexus 4" in the "Other devices" section of the Device Manager (I do not have "Android Device" section), except in when MTP + debugging are activated. Then I have both "Nexus 4" and "MTP", in "Other devices" section.
It does not work in PTP mode either and I also tried uninstalling/reinstalling the Nexus Root Toolkit, even if I do not see how it can help...
One last point: I have the "connected as multimedia device" notification on my Nexus 4 when MTP is activated, even if it's not recognised by Windows.
Do you have any idea of what I can do?
Have you tried Nexus 4-specific drivers? Try following this guide.
Marvlesz said:
Have you tried Nexus 4-specific drivers? Try following this guide.
Click to expand...
Click to collapse
I have already tried to follow this guide, it just helped me to install ADB drivers but I still don't have access to the content of my Nexus from my computer. I just tried it again, just in case. No changes
Bartimoot said:
I have already tried to follow this guide, it just helped me to install ADB drivers but I still don't have access to the content of my Nexus from my computer. I just tried it again, just in case. No changes
Click to expand...
Click to collapse
Last time I had such an issue: I uninstalled the drivers using Device Manager, then installed the drivers from that guide, plugged in my phone and it worked..
Here is another post from another forum that has something you could try:
still1 said:
ttwiitch said:
still1 said:
1. make sure Settings ->Storage -> Menu[3 dots on top right] -> USB Computer Connection is MTP
2. USB debugging is disabled (if you ever enabled it)
3. make sure the drivers installed is MTP drivers rather than adb device(you do this when you unlock/root nexus)
point 3 is important. thats the reason why its not getting detected
Click to expand...
Click to collapse
2. Where in setting do I check for USB debugging?
3. How do I check this? (I'm not rooted)
Click to expand...
Click to collapse
2. developer option.. if you have not enabled developer option then you wouldnt have enabled USB debugging. so skip this
3. Connect your nexus to PC-->Go to Control panel-->device manager
you will see something like Android adb in device manager
Right Click and click "Update device Software"
Click "Browse your Computer for driver Software"
Click "Let me Pick from a list of device drivers on my Computer"
Click Next, for the device list shown.
Click to expand...
Click to collapse
Tell us how it goes..
Thank you for spending some of your time to help me Marvlesz, I really appreciate.
Marvlesz said:
Last time I had such an issue: I uninstalled the drivers using Device Manager, then installed the drivers from that guide, plugged in my phone and it worked..
Click to expand...
Click to collapse
Yes, I saw it worked for a lot of people, for what I have read, but it seems that I am not that lucky
When picking from the list, I tried from the Android Device section and it displays "Unable to find any drivers for this device". Same Results in “Mobile devices”.
When I try “Show all devices”, I have a lot of possibilities. I just tried “MTP Device” from both “Standard MTP-Compliant Device” and “Standard MTP-Compliant devices” sections, and it displayed “The install class is not present or is invalid”
Am I cursed?
I was wondering, is it possible that the problem is coming from my hardware? Or its drivers? (Those for the motherboard maybe?)
EDIT: I just found this thread : http://forum.xda-developers.com/showthread.php?t=2493734
I will try it and I will keep you updated when it is done.
EDIT 2:
So I tried the solution... and it worked! :good:
I had the N version of Windows 8.1, mainly to avoid useless software like Windows Media Player, and it was the exact problem.
Sorry for taking a little of your time, and thank you again!
No problems, I'm glad you had it fixed.
Hi,
I've received a couple of days ago two Onplus 5.
They both work great but when I try to connect them to my desktop, they get detected as "qualcomm hs-usb diagnostics 900e" by windows 10 that states the USB device is not recognised.
The issue is reproduced on a laptop, although it did get picked up once by the laptop, only to fail on a second attempt with the same device name "qualcomm hs-usb diagnostics 900e" after I installed the driver provided by Oneplus.
I read on the forum that "qualcomm hs-usb diagnostics 900e" is normally related to Bricked phone issues, which is not my case and I don't know what to do to resolve this.
I also tried to activate the USB debug mode on the phone, but this didn't change the problem.
My windows are all up to date and my phones as well (running Android 7.1.1, OxygenOS 4.5.2)
Has anyone experienced this issue with that phone or any other?
I would greatly appreciate some help and I thank you in advance for reading this and offering advice.
Unplug phone, restart windows.
Go to settings / about phone / press build number 5-6 time (don't remember exactly how many times) to enable developer options
turn on USB debugging
select USB configuration MTP (media transfer protocol)
plug it in
Install drivers
And now on you should have it working every time you plug it to your laptop.
dcrnic said:
Unplug phone, restart windows.
Go to settings / about phone / press build number 5-6 time (don't remember exactly how many times) to enable developer options
turn on USB debugging
select USB configuration MTP (media transfer protocol)
plug it in
Install drivers
And now on you should have it working every time you plug it to your laptop.
Click to expand...
Click to collapse
Thanks dcrnic, I must have skipped a step with the debugging mode because your procedure did the trick.
Is this a normal process to have to go to Dev mode and Debug mode to be able to connect to a PC?
Thanks again for your help!:good:
Win 10 do not recognize device as it is so new. Probably in the future this will be solved on Windows end.
I found online link for drivers
https://drive.google.com/file/d/0B-LgkimFUEksbjRCY1BkWnduVW8/view?usp=sharing
Moderators
Please delete ... Today forum is so slow, and it do double posting for some reason even I press reply just once.
Thank you.
FIXED: Use stock op5 cable. The other cable that gave me issues works just fine for op2.
The phone used to be seen by win10, but since oem unlock and superSU, the computer at work doesn't recognize it. Ran the 4.5.2 update with same results. I noticed that in Developer Options -> Select USB configurations charging is selected and greyed out. Going in selecting anything else returns is to Charing.
Device Manager > Find the phone > Right click > Update drivers (or something like that) > Select driver from Computer > Select "MTP USB Device" Enjoy
I'm having the same issue. If I manage to get it to connect to the PC, then after I unplug and plug it again it gives the same not recognised balloon. It only seems to work with USB Debugging On
I ended up using the original op5 cable and it recognizes the phone right away.The cable that didn't work for op5 is not stock, but worked perfectly fine for op2.
Same issue
Even I'm facing the exact same issue on my op5
dcrnic said:
Win 10 do not recognize device as it is so new. Probably in the future this will be solved on Windows end.
I found online link for drivers
https://drive.google.com/file/d/0B-LgkimFUEksbjRCY1BkWnduVW8/view?usp=sharing
Click to expand...
Click to collapse
The drivers are on the phone, they're mounted as a drive when you plug the phone in? They even add ADB tools when you install them, they're in C:\Program Files (x86)\OnePlus USB Drivers and the ADB tools are in the Android folder within there.
djsubterrain said:
The drivers are on the phone, they're mounted as a drive when you plug the phone in? They even add ADB tools when you install them, they're in C:\Program Files (x86)\OnePlus USB Drivers and the ADB tools are in the Android folder within there.
Click to expand...
Click to collapse
Yes, they are on the phone, but computer need to recognize device to see it. It does not, so the drivers on the phone are useless in this case.
I compared this to my ZTE Axon 7. If you choose "Charge only" the Axon 7 is recognized as a USB input device. This should also happen for our OP5 but the driver (which btw. is a windows standard driver) does not contain PID 900E and also does not like to have it forced to a USB input device.
The Axon 7's PID is F006.
However, the real issue is when Windows decides to use Qualcomm's HS USB Diagnostic Interface driver which seems to give even more trouble (at least for me). When I tried to switch to MTP this would not work and my Windows 10 hung itself up when rebooting or shuting down. For now I just disabled the "Unknown device" to prevent such things from happening. Charging still works this way and the phone is correctly recognized when changing to MTP.
If you are facing the same issue, disconnect the Oneplus 5 from your PC, reboot the PC and after that launch the device manager. You need to enable hidden devices in the view menu of the device manager to see disconnected devices. Now remove the device "Qualcomm HS USB Device Interface" and also choose to uninstall the driver itself. After that you can connect your device again and it should pop up as "Unknown device". Then simply disable the device.
Regarding the drivers from Oneplus: this package is lacking a driver for the device we are seeing (VID_05C6&PID_900E).
Does anyone know if the latest update (OxygenOS 4.5.5 update) addresses this issue? It says the following as one of the bug fixes:
"To restore connectivity to a Windows 10 PC, please turn off USB debugging prior to the upgrade"
aa_chow said:
Does anyone know if the latest update (OxygenOS 4.5.5 update) addresses this issue? It says the following as one of the bug fixes:
"To restore connectivity to a Windows 10 PC, please turn off USB debugging prior to the upgrade"
Click to expand...
Click to collapse
Worked for me, only remember to Uncheck usb debugging BEFORE the update....
Hmm, didn't work for me, same behavior as before the update...Qualcomm HS-USB as soon as phone is plugged in...USB debug was off.
Sent from my ONEPLUS A5000 using Tapatalk
try changing port (and remember to restart the pc)
Just got my phone today. It updated to 4.5.5 immediately. All I did was connect it to the computer (windows 10) and everything works.
bricky23 said:
Just got my phone today. It updated to 4.5.5 immediately. All I did was connect it to the computer (windows 10) and everything works.
Click to expand...
Click to collapse
It worked the first time too, but not the second time...at that point connected detected as Qualcomm HS-USB Diagnostic, and computer won't shut down.
And yes I installed it a few time, and it works the first time connecting, but not the second time around.
Sent from my ONEPLUS A5000 using Tapatalk
I don't have my OP5 yet, but I had a very similar and difficult experience with my OP3 when I first received it on Windows 10 Pro. On top of installing the proper drivers, I also had to go into Device Manager and run some steps (I'm going off on memory so they may not be entirely accurate). The root cause is driver signature check enforced in Windows 8+. So by going into Device Manager and seeing "kedacom USB driver", right click and find the oneplus USB driver you installed above and also need to disable the driver signature enforcement (in windows 10 go to advanced startup settings, reboot and choose (I think) #7 then reboot). Then plug in the phone usb go to device mgr right click on kedacom USB driver and choose the oneplus driver.
I don't have all the steps in the right order but it should fix your issue.
Basically it just charges the device even when selected media transfer, nothing shows up.
Tried different USB cables, updating drivers, restarting nothing is working.
Device manager has a error symbol next to the driver SDM636, updating the driver however fails.
Any help is greatly appreciated.
Mordecai07 said:
Basically it just charges the device even when selected media transfer, nothing shows up.
Tried different USB cables, updating drivers, restarting nothing is working.
Device manager has a error symbol next to the driver SDM636, updating the driver however fails.
Any help is greatly appreciated.
Click to expand...
Click to collapse
Is your device rooted/has twrp installed?
Mr.Ak said:
Is your device rooted/has twrp installed?
Click to expand...
Click to collapse
No not rooted, out of the box problem
ok. install this file.
https://1drv.ms/u/s!AhCMXaKFXMiuh6t_TSqRqQZLLKOGJg
if you are running windows 7 and up right click and click run as admin.
say yes to all the prompts.
if you are running 64bit windows you will get security error when installing device drivers just check always install and click install.
once it installs connect phone to pc and select mtp mode and see if it works.
Mordecai07 said:
Basically it just charges the device even when selected media transfer, nothing shows up.
Tried different USB cables, updating drivers, restarting nothing is working.
Device manager has a error symbol next to the driver SDM636, updating the driver however fails.
Any help is greatly appreciated.
Click to expand...
Click to collapse
Try connecting your phone to another system.. sometimes the drivers get corrupted on the system. If the phone is detected on another system, then just search on the net to show hidden devices in devices manager, and delete the ghosted devices in the device manager on the system.
No none of the methods are working.
Removed all ghosted devices too. Shows unknown device below sdm636, both have error sign next to them.
The main issue is all phones in device manager show up under "portable devices" but mine is showing under "other devices".
It's not updating even when manually done.
Mordecai07 said:
No none of the methods are working.
Removed all ghosted devices too. Shows unknown device below sdm636, both have error sign next to them.
The main issue is all phones in device manager show up under "portable devices" but mine is showing under "other devices".
It's not updating even when manually done.
Click to expand...
Click to collapse
My last thought would be to enable USB debugging through developer options and check again.. sometimes it works as it does change the connected path in the phone. If this doesn't work, maybe you should try warranty to replace it.
Just for your info, there are android apps like Airdroid which can transfer any content from a system to a phone in a matter of seconds through WiFi.
spunxhoe said:
My last thought would be to enable USB debugging through developer options and check again.. sometimes it works as it does change the connected path in the phone. If this doesn't work, maybe you should try warranty to replace it.
Just for your info, there are android apps like Airdroid which can transfer any content from a system to a phone in a matter of seconds through WiFi.
Click to expand...
Click to collapse
USB debugging didn't work as well.
AirDroid and share it for PC are annoying.
Mordecai07 said:
Basically it just charges the device even when selected media transfer, nothing shows up.
Tried different USB cables, updating drivers, restarting nothing is working.
Device manager has a error symbol next to the driver SDM636, updating the driver however fails.
Any help is greatly appreciated.
Click to expand...
Click to collapse
1) Download drivers at ASUS Website
2) Right click (your device) and update drivers in Device Manager
3) That's it
Saktis_STi said:
1) Download drivers at ASUS Website
2) Right click (your device) and update drivers in Device Manager
3) That's it
Click to expand...
Click to collapse
Ya that was my go to method.
Isn't working.
Mordecai07 said:
Ya that was my go to method.
Isn't working.
Click to expand...
Click to collapse
If Windows 10, you will find an error like " device descriptor request failed" device under USB in Device Manager. Just uninstall it and reconnect your phone. It should detect under "This PC".
Worked for me this way.
pprakash said:
If Windows 10, you will find an error like " device descriptor request failed" device under USB in Device Manager. Just uninstall it and reconnect your phone. It should detect under "This PC".
Worked for me this way.
Click to expand...
Click to collapse
No that's not it.
Mine is a completely different problem, it says " one of the installers cannot complete the installation at this time ".
No difference if I uninstall update or disable it's getting nowhere.
Had same problem! Was trying all the steps, but for me helped to switch to MIDI and then to MTP (in developer settings) - now it works. Try yourself.
Mordecai07 said:
Basically it just charges the device even when selected media transfer, nothing shows up.
Tried different USB cables, updating drivers, restarting nothing is working.
Device manager has a error symbol next to the driver SDM636, updating the driver however fails.
Any help is greatly appreciated.
Click to expand...
Click to collapse
Somewhat a similar case to mine.
Today I decided to unlock bl , flash twrp and root my M1.
Tried 3-4 methods , 3 PCs , manually installed drivers and wasted 4hrs but all got zero results. Everytime after clicking on "unlock.cmd" nothing happens. Just command window shows erase all devices ... something like that.
I am currently on latest build i.e. 311.
Any help is welcomed.
Mordecai07 said:
Basically it just charges the device even when selected media transfer, nothing shows up.
Tried different USB cables, updating drivers, restarting nothing is working.
Device manager has a error symbol next to the driver SDM636, updating the driver however fails.
Any help is greatly appreciated.
Click to expand...
Click to collapse
Download and Install Google USB Driver - https://developer.android.com/studio/run/win-usb
Disable, if already enabled, USB Debugging then re-enable it and try connecting it to your computer. Try switching modes (charging>photos>mtp) if your device doesn't get detected straight away.
Solved : This works for me !!!
This is on my Windows 7
Go to Device manager and "Show enable hidden device" under view menu.
I found a new device at the very top with strange name (forgot to note the name)
Uninstall it and then right click on any device and click on "scan for hardware changes" again (Make sure the phones is connected when scaning)
It reinstalled the device and got my phone working
Hope this helps someone..
I somehow solved this by installing both usb google driver and the asus driver one for windows. Didn't restart my computer or anything and when I reconnect my phone with usb debugging and ptp transfer, suddenly there's the permission with certificate something on my phone and I pressed yes and allow this computer, and voila! It shows up after I typed adb devices on the command prompt.
I am having the very same problem but I can transfer file connected of a portable media player, etc.
The problem comes when I try to connect my phone via USB debugging, it shows "No drivers found". Also when installing/reinstalling drivers using 15 seconds installer in the second next windows it's Shows Google Inc. drivers are installed.
OS on PC: Windows 7 32-bit
Phone: Stock (Out of the box and updated over OTA updates to latest).
.hack//G.U. said:
I somehow solved this by installing both usb google driver and the asus driver one for windows. Didn't restart my computer or anything and when I reconnect my phone with usb debugging and ptp transfer, suddenly there's the permission with certificate something on my phone and I pressed yes and allow this computer, and voila! It shows up after I typed adb devices on the command prompt.
Click to expand...
Click to collapse
@.hack//G.U. Could you please upload the Asus driver somewhere and share it? Since then Asus has removed whatever driver was there. Nothing like that now in the Downloads.
You need to install your phone's drivers in PC
You need to install your phone's drivers in PC in order to get recognised by your PC.
Try ADB driver which is time saver always.
---------- Post added at 10:30 PM ---------- Previous post was at 10:03 PM ----------
You can try these USB drivers for your Asus: Asus Zenfone Max Pro (M1)