Related
Hello.
And bacon and spam:
I've recently upgraded my SGS to ICS (ICSSGS ROM) and started to develop a simple application.
So, now i've got to the point that the emulator starts to show its limitations, so i need to debug directly on the real device.
Well, i've been trying to make ADB recognize my phone, tried several usb drivers from several sites, none of them worked.
After several hours spanking windows, it's finally working (yes! almost 6 AM in the morning!).
What matters:
So, to anybody who have the same problem as i had, do the following:
0. Uninstall any drivers that you've tried before.
1. Extract the zip file that i've uploaded to anywhere you like.
2. Enable debugging on your phone and connect it to PC throught the USB cable
(Just connect it, don't mount)
3. On your computer, click Start -> Right click on "Computer" -> Manage
This will open the "Computer Management" window (it might take some seconds to load).
4. Click "Device Manager". Now you should find your device in the list. It must be really easy to find. It's called something like "GT-I9000" or "GalaxyS" and it has a yellow warning sign next to it.
5. Right click on it and choose "Update Driver Software". In the window that appears, choose "Browse my computer for driver software". It then asks you where is the driver.
6. Click the "Browse" button and choose the folder you extracted from my zip file.
(If you didn't change it, it must be called "Android Composite ADB Interface")
7. Click "Next" and cross your fingers. If you're lucky, it may work for you.
Final notes:
1. I'm not responsible for ANYTHING. Whatever you do, it's your own choise to do it. I guarantee absolutely nothing.
2. This is was tested on Windows 7 - 64 bits with Team ICSSGS RC4.2 ROM and Semaphore ICS 0.9.1 Kernel.
3. Have fun.
4. If you try this, please answer the topic and tell everybody if it's working for you (mentioning your Windows version and what ROM you use).
Driver file:
-> http://www.mediafire.com/?t8ekrd9ly3mwwbk
Missing file when installing driver on windows 7 x64
Hi,
I have recently installed the most recent Dark Knight ICS 4.0.4 build to my Samsung Galaxy S. The ROM seems very good but I'm an android app developer and need to be able to debug my applications on the device via USB.
I have tried the driver provided in the thread which won't install due to a missing file according to the Windows 7 x64 driver install wizard. The exact message is displayed after step 7 and says:
"Windows found driver software for your device but encountered an error while attempting to install it."
"Android Composite ADB interface"
"The system cannot find the file specified".
Is there a file missing in the package? Has anybody managed to get this driver working?
Cheers,
Ben
Does it say that it doesn't find a controller or that is there a missing file?
Anyway, please try this installer and let me know if it works for you:
http://www.mediafire.com/?v70501cxbzzdvc2
What's wrong with the Nexus S drivers available with Android SDK?
Google USB driver, R4 developer.android.com/sdk/win-usb.html
The SGS will present it self like that when it is running ICS/CM7/CM9.
Sent from my GT-I9000
METEMEDO said:
Does it say that it doesn't find a controller or that is there a missing file?
Anyway, please try this installer and let me know if it works for you:
http://www.mediafire.com/?v70501cxbzzdvc2
Click to expand...
Click to collapse
Dont work for me.
System: Windows 7 x64
Android 4.04 Dark Knight
Nevertheless thanks for your approach. I'll test if it works with the SDK Updater.
I'm going to test in my desktop this weekend to check if it works with it.
I have the same problem, but with WIndows 7 32 bit. Drivers from discusion doesn't work. Don't you have some for 32 bit?
I found SDK Components on developer.android.com, where is Android driver which suppose to work, but unfortunately ODIN still do not see phone.
I also have the same problem but mine is worse because my phone is completely down after I tried to restore from a GB ndriod backup failure , phone won't boot , cannot boot into recovery only in download mode but no way my 4 x computers would detect the phone now ....tried using heimdall in linux as well as sdb, no go....so sad...help...
Sent from my Dell Streak using XDA
Using Google USB drivers finally worked for me. They can be optionally installed with Android SDK using SDK manager (extras). After installation drivers can be found in <sdk>\extras\google\usb_driver.
Just follow the instructions in the first post to find your device from device manager with exclamation mark. Need at least one reboot to work and I also redirected the driver installation process to Google usb driver directory but now ADB finally recognizes my SGS (MyICS, Android 4.0.3).
Edit: Operating system Vista 64-bit
[Currently stuck in "error: device not found" while trying adb push -command. I will update if I find a workaround. Probably something to do with inf-file.]
For alternate .inf -file (optional):
Google "usb-drivers-not-working-after-flash-latest-rom-ota" and see post #12 to see alternative inf-file. Some have managed to make adb recognize the device with that file, but I have at least this far been unsuccessful.
Edit: Problem above was caused by me being stupid and trying to use push in shell, which caused phone unable to locate host system folders. I don't know if that inf file has anything to do with drivers working now, but go ahead and try it if doesn't work with the original .inf
I got my i9000 recognized using the latest drives from the Google sdk
That‘s great
http://ics.samsung-updates.com/addons/usb_driver.zip
oxidising said:
I got my i9000 recognized using the latest drives from the Google sdk
Click to expand...
Click to collapse
I tried last night didn't work for me.... (r18)
Sent from my Dell Streak using XDA
oxidising said:
I got my i9000 recognized using the latest drives from the Google sdk
Click to expand...
Click to collapse
Daha açık anlatabilir misiniz?
IWillExplain said:
http://ics.samsung-updates.com/addons/usb_driver.zip
Click to expand...
Click to collapse
... this driver actually worked for me...!
(Tiramisu ICS)
USB option has been lost in my galaxy s
RazorNova said:
Using Google USB drivers finally worked for me. They can be optionally installed with Android SDK using SDK manager (extras). After installation drivers can be found in <sdk>\extras\google\usb_driver.
Just follow the instructions in the first post to find your device from device manager with exclamation mark. Need at least one reboot to work and I also redirected the driver installation process to Google usb driver directory but now ADB finally recognizes my SGS (MyICS, Android 4.0.3).
Edit: Operating system Vista 64-bit
[Currently stuck in "error: device not found" while trying adb push -command. I will update if I find a workaround. Probably something to do with inf-file.]
For alternate .inf -file (optional):
Google "usb-drivers-not-working-after-flash-latest-rom-ota" and see post #12 to see alternative inf-file. Some have managed to make adb recognize the device with that file, but I have at least this far been unsuccessful.
Edit: Problem above was caused by me being stupid and trying to use push in shell, which caused phone unable to locate host system folders. I don't know if that inf file has anything to do with drivers working now, but go ahead and try it if doesn't work with the original .inf
Click to expand...
Click to collapse
What should i do after instaling SDK
IWillExplain said:
http://ics.samsung-updates.com/addons/usb_driver.zip
Click to expand...
Click to collapse
This worked for me
The very important thing is that newest Google USB driver is in
Code:
[B]<android-sdk>/extras/google/usb_driver/[/B]
location, not in
Code:
<android-sdk>/usb_driver
It really makes the difference !
these drivers only worked once...
all the other times killing and starting over adb i was getting error messages like "device not found" and "protocol fault" even though adb devices was listing the device online.
apparently i connected the phone to another USB3 port on my pc (front panel) and that was it!! it now works every time i type adb shell or adb devices.i no longer get any error messages.rather weird
anyway..i also wanted to be up to date with everything so i uninstalled all related software like the older java 6 jdk, Android SDK and the drivers mentioned above.
i followed the procedure below and installed all the latest packages:
latest java 7u5 JDK, the latest Android SDK (nstaller_r20.0.1-windows.exe) then ran sdk-manager and loaded http://developer.android.com/tools/extras/oem-usb.html#InstallingDriver google USB drivers rev 6. then installed these drives so i got the ADB composite interface on my device manager and it all works fine now.
I recenelty installed latest ICS , and SDK recognizes my phone as ACER ADB , when I'm pretty sure its a Samsung I9000 . I tried uninstalling the ACER ADB and install the one that the guy posted in the first post , and it didn't work , it said this driver is not compatible , oddly it reinstalled ACER ADB though. I can't even uninstall it at all , I removed all my Samsung drivers , and everything else I installed for Samsung , and its still there , I even tried removing the GOOGLE USB drivers , still there.
Neendless to say that the phone doesnt connect to the PC at all even though it says everything is alright. For example i got ths gPAD app , which uses the USB with Debugging to turn the phone into a mouse , but it says its not connected even though it is.
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!
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.
New laptop (to me) Dell e7470.
Win7 x64
Phone: XT1575
Installed:
MotorolaDeviceManager_2.5.4
MotoHelper_2.1.32_Driver_5.4.0
Motorola_End_User_Driver_Installation_6.4.0_64bit
(also tried Kushik Dutta universal adb driver from 2013)
No adb driver detected or found when all the other drivers install fine when plugging in the phone
I've tried multiple usb cables, but this all works fine on my other computers.
If reboot to fastboot Motorola ADB driver is found and installed
But no adb driver when in rom
I've done this successfully for years, first android device many moons 2008ish
I dont know why this laptop is giving me troubles, or maybe i'm just gettin old and forgot a basic sequence or step to success.
Thanks for any ideas, its got to be something dumb.
You need to turn on usb debugging - developer options.
Minimal adb & fastboot installed too.
Dev.opt. - settings - infi about phone - tap few times compilation number. @eigerzoom
What for do you need adb if fastboot works?
MDM is all you need for drivers.
I have adb debugging enabled
I apparently need it for tethering, since that isn't working.
Works just fine on my other win7 asus laptop.
Any other ideas?
it feels like windows is missing something, but its hard to feel a computer
Run cmd and type:
adb devices
I've done that, thats how i test it.
its blank
actually i test it with 'adb usb' which gives error: no devices
File transfer works?
how would it transfer files if no device is found?
adb device shows up in device manager with an error
File transfer - mtp - not needed adb drivers. From notification bar you can change/enable when connected.
---------- Post added at 07:31 PM ---------- Previous post was at 07:28 PM ----------
Error in win dev manager - rpm - update driver - choose from installed.
Find & choose "adb device".
I'll test it soon, sorry
Also in developer settings you can choose usb configuration mode
if I cycle through them all
All drivers get recognized except in 'audio source' mode xt1575 no drivers install, and in 'rndis usb ethernet' no adb drivers install
I haven't Windows english version - I don't know names.
So I suggest:
Uninstall all Android programms(apps) & drivers from pc, restart pc.
Install and run MDM, when it finished connect Moto with debugging on, allow the connection on Moto(it should ask itself) .
Anyone else???
eigerzoom said:
Anyone else???
Click to expand...
Click to collapse
No try what @dzidexx suggested, before asking for someone else! Especially since his solution isn't hard to try out and see if it works!
I've done all that....obviously....
ANYONE ELSE ???
something tells me i have to install a stock rom to get the adb driver to install
and then it will work fine installing other roms after that
running LOS13 currently
i've run into this in the distant past on pre 2010 devices
anyone else with ideas?
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)