I've had a look and not seen anyone else with this issue. I installed CM7 and everything worked fine after reboot except when I connect it to PC to debug it doesn't read the phone. It will however read phone when in external storage mode and in device manager it shows the phone and it's current USB driver. Reinstalling drivers didn't work.
So then I wiped system memory and cache and reflashed CM twice as heard that helps. Still not read by adb and this was before I backed up apps from titanium. Then spent another few hours reinstalling drivers, including the one from the Heimdall suite, continuely restarting ADB and computer. ADB still not reading it. Any ideas?
Didyou check Development to see if USB Debug is checked? By default it's checked but you may just have to uncheck it and recheck it again?
Yeah in addition to the restarting ADB and phone etc.. I also tried that a few times.
I believe you need the Nexus S drivers. But i'm not sure because I never tried it.
Thanks so much, works perfectly now!
Related
So I just got an Atrix and im trying to root it, however when I plug it in, after setting USB Mode to None and turning on the USB Debug, ADB drivers fail to install. It shows up in my device manager with a ! ontop of the icon, and windows tells me it cant find a driver. I manually downloaded the drivers but that still didnt help, my phone isnt making a connection of the bridge. Ive wiped everything everything motorola related, reinstalled the drivers manually, reinstalled the ADB driver manually, rebooted about 10 times and now im absolutely stuck.
Has anyone run into this before? Im going to try plugging the phone into my work computer today, but id like to be able to get this working on my home computer. I followed the guide thats available out there that tells you to run the driver installer and delete all the files it shows, and that didnt help either. Im on Windows 7 but i also have a laptop with Ubuntu available, however i couldnt find a rooting guide for linux so im not sure if that will help.
albinojoe said:
So I just got an Atrix and im trying to root it, however when I plug it in, after setting USB Mode to None and turning on the USB Debug, ADB drivers fail to install. It shows up in my device manager with a ! ontop of the icon, and windows tells me it cant find a driver. I manually downloaded the drivers but that still didnt help, my phone isnt making a connection of the bridge. Ive wiped everything everything motorola related, reinstalled the drivers manually, reinstalled the ADB driver manually, rebooted about 10 times and now im absolutely stuck.
Has anyone run into this before? Im going to try plugging the phone into my work computer today, but id like to be able to get this working on my home computer. I followed the guide thats available out there that tells you to run the driver installer and delete all the files it shows, and that didnt help either. Im on Windows 7 but i also have a laptop with Ubuntu available, however i couldnt find a rooting guide for linux so im not sure if that will help.
Click to expand...
Click to collapse
which windows 7 32 or 64?
32 bit.
Tried on 2 different PC's, my home computer and my work computer. ADB driver fails to install on both. Both running windows 7 32bit.
albinojoe said:
32 bit.
Tried on 2 different PC's, my home computer and my work computer. ADB driver fails to install on both. Both running windows 7 32bit.[/Q
try to use the drivers from this thread and see if that works
Click to expand...
Click to collapse
or this site use the motohelper
http://www.motorola.com/consumers/v/index.jsp?vgnextoid=bda09ec8009a0210VgnVCM1000008806b00aRCRD
I got it sorted. Installed the ADB driver manually (choosing the regular adb driver NOT the composite driver) and then ran super one click to start the ADB service. Then once the phone was connected, ran aroot and it worked.
albinojoe said:
I got it sorted. Installed the ADB driver manually (choosing the regular adb driver NOT the composite driver) and then ran super one click to start the ADB service. Then once the phone was connected, ran aroot and it worked.
Click to expand...
Click to collapse
glad you got it
I just plugged my S3 into my PC to copy some files over, and all of a sudden i got this error from windows saying USB Device not recognized and this USB device has malfunctioned. I heard its a known problem on android phones, but never really found a solution for it. Can someone help?
cr0wnest said:
I just plugged my S3 into my PC to copy some files over, and all of a sudden i got this error from windows saying USB Device not recognized and this USB device has malfunctioned. I heard its a known problem on android phones, but never really found a solution for it. Can someone help?
Click to expand...
Click to collapse
I had the same problem.Make a back up of your phone
and do a factory reset.
tried installing usb drivers sgain ??
Sent from my GT-I9300 using xda premium
try installing Kies?
Its ok i got it to work. Went into download mode and plugged into my PC and windows installed some drivers, Odin detected the phone just fine. Then i booted up into android like normal but switched to PTP mode, windows then installed the MTP drivers (though it was already installed) then after that all worked well again
Please help...
Im having the same problem. But nothing seems to work for me. Tried everything possible. Re-installed drivers, connected in download mode, installed Kies, reset to factory setting..ALL TO NO AVAIL. I keep getting 'USB device attached to this computer has malfunctioned...' message...
The solution isnt always the same for all users.. Fortunately mine was fixed by a simple driver install. I remember browsing the internet and found out that there is a way to fix it but it requires simple adb commands and the Android SDK.
I have been fighting this for awhile now. My phone boots up just fine, and I am able to charge it through USB, but I cannot get Windows to recognize it. I have tried multiple ports, checking and unchecking MTP and PTP in settings, enabling and disabling ADB, and even putting the phone in download mode. LGNPST won't even recognize it in download mode. I'm really not sure what to do at this point. Does anybody have a suggestion? I'm currently running CWM 6.0.4.7 and CM 11. Thanks in advance for any help.
jimsal82 said:
I have been fighting this for awhile now. My phone boots up just fine, and I am able to charge it through USB, but I cannot get Windows to recognize it. I have tried multiple ports, checking and unchecking MTP and PTP in settings, enabling and disabling ADB, and even putting the phone in download mode. LGNPST won't even recognize it in download mode. I'm really not sure what to do at this point. Does anybody have a suggestion? I'm currently running CWM 6.0.4.7 and CM 11. Thanks in advance for any help.
Click to expand...
Click to collapse
Had same problem with my laptop. I installed the correct drivers but still, nothing. Might want to try a different pc to see if the problem is the phone or the pc.
I have a similar problem here at work. We all use Win7 PCs. Mine has the LGOG driver package installed and despite all efforts to install, etc my LGOG only charges. The notice window appears announcing that drivers are being installed, but then it fails.
When I go to my neighbor's pc, that doesn't have the driver package installed the notice window appears, says searching and installing drivers and I can see my phone in explorer. I can't explain but a different pc is a solution.
Hi!
I have searched XDA forum and other forum concerning LineageOS. But I have not found a solution.
My latest experiments were with installation of the adb interface on windows. At first, this worked well and I got full massstorage access. The Galaxy and its both memories did show up in Windows Explorer (like in old ages).
At the next restart of Windows (Win 7 64-bit Pro) when I connected my phone, Windows immediately did install the samsung drivers again. And since that things got even worse: No even the MTP and PTP Mode did not work, so that the Smartphone does not show up at all in the Windows Explorer!
At F-Droid, I have found an app, called USB Mountr. I tried this, but without any effort.
In the device manager of Windows I can see an „Android Composite ADB Interface”. It tells, that the device would work OK.
Now I am stuck with this and I hope, someone will help me, to activate usb massstorage access.
BTW: I have flashed my Galaxy S2 with Heimdall, running on Ubuntu. Heimdall on Windows 7 did not work, because of libusb error -12.
Latest status:
I have uninstalled the app USB mountr and did reboot the phone. Now the USBconnector is only active for charging the battery. I even get no connection in PTP or MTP mode.
Then I have deactivated USB debug mode and ADB. did a reboot, reactivated ADB and USB debug etc. and did further reboot the phone but with no success.
USB connection is nearly dead and cannot have connect with LUBUNTU Laptop. On Win 7, I get the signal tone, which is typical for connecting an USB device. The GT.i9100 shows up in Explorer but cannot be connected. Device manager tells me, that it is an Android device and all would be OK.
As a work around I am using MyPhoneExplorer on Win-7 and KDEconnect for Ubuntu.
Please can anybody tell me, what I should do, to get back at least USB connection in MTP or PTP mode???
I have the exact same problem.
I did notice, that after first boot, there was a message (several times) the MTP daemon/service stopped working (Crashed ?)
Does anyone else encounter this ?
Did anyone else resolve this ?
(Currently I was only able to get/send files to the device via BT, which is slow, annoying,
and a lot of work moving files to their required places after transmitting over BT)
Quick Fix for stuck on boot
This probably isn't the right place but you said there weren't many solutions. If your phone randomly gets stuck on boot you need to Delete Everything including system, factory data reset, flash ROM again with ADB, go through setup. The reason it probably hanged is because you installed an old version of SuperSU Binary or because you flash OpenGapps before setting up phone.
Hope this works
P.S Sorry for the late reply
Hi Guys,
I might have ****ed up something,
I was on B131-SP1, rooted with magisk, I wanted to install B137, so I ran the magisk uninstall, repacked the B137 update, and ran the OTA.bat, everything went ok.
I wanted a fresh install, so I went in the recovery and wiped data.
To get root back I booted the phone in fastboot, and ran the magisk installer, and it asked to disconnect the phone and boot in to recovery,
everything ok, booted the phone in to recovery, and when I connected the phone I got a error on Windows that the device malfunctioned.
And since then also when I'm in fastboot the system won't recognize the phone anymore.
When the phone is on, I can run adb commands without problems.
I've tired everything, uninstalling and reinstalling drivers, Hisuite, other USB ports....
When I wiped the system, before flashing magisk again, I forgot to enable USB debugging and OEM unlock in developer settings, (tho BL was unlocked from before).
When I connect the phone in recovery, it shows in Windows as a failed mass storage device.
In fastboot I got to the point to have the right driver (Android bootloader interface) shown up, but it fails to start.
Anyone has a clue of what is happening?
I freaked out for a while thinking I might have done something wrong.
Turned out that Windows is the problem, since adb and fastboot are both working well on Ubuntu.
Luinwethion said:
I freaked out for a while thinking I might have done something wrong.
Turned out that Windows is the problem, since adb and fastboot are both working well on Ubuntu.
Click to expand...
Click to collapse
There is a regfile fix in mankindtws hwota thread, see if that one helps.
Or you could Google how to completely uninstall drivers, then reinstall minimal adb & fastboot.
ante0 said:
There is a regfile fix in mankindtws hwota thread, see if that one helps.
Or you could Google how to completely uninstall drivers, then reinstall minimal adb & fastboot.
Click to expand...
Click to collapse
Thanks, I found this register hack, and also made sure to reinstall all drivers from 0 but somehow Windows still refuses to recognize my phone.
I guess a reinstall is the best way of solving it. Or using Ubuntu from now on....
Luinwethion said:
Thanks, I found this register hack, and also made sure to reinstall all drivers from 0 but somehow Windows still refuses to recognize my phone.
I guess a reinstall is the best way of solving it. Or using Ubuntu from now on....
Click to expand...
Click to collapse
I ran into this also and I un-installed HiSuite, then re-installed it and after that in device manager set up drivers as seen in screen copy in attachement.
I also refer to this page for more info: https://www.dc-unlocker.com/huawei-mate-10-fastboot-usb-device-not-recognised-fix
Luinwethion said:
Hi Guys,
I might have ****ed up something,
I was on B131-SP1, rooted with magisk, I wanted to install B137, so I ran the magisk uninstall, repacked the B137 update, and ran the OTA.bat, everything went ok.
I wanted a fresh install, so I went in the recovery and wiped data.
To get root back I booted the phone in fastboot, and ran the magisk installer, and it asked to disconnect the phone and boot in to recovery,
everything ok, booted the phone in to recovery, and when I connected the phone I got a error on Windows that the device malfunctioned.
And since then also when I'm in fastboot the system won't recognize the phone anymore.
When the phone is on, I can run adb commands without problems.
I've tired everything, uninstalling and reinstalling drivers, Hisuite, other USB ports....
When I wiped the system, before flashing magisk again, I forgot to enable USB debugging and OEM unlock in developer settings, (tho BL was unlocked from before).
When I connect the phone in recovery, it shows in Windows as a failed mass storage device.
In fastboot I got to the point to have the right driver (Android bootloader interface) shown up, but it fails to start.
Anyone has a clue of what is happening?
Click to expand...
Click to collapse
Hi, I have the same problem after upgrading to 137 version. If the phone is on works with debug usb, also in fastboot mode works. Only in recovery mode windows doesn't find driver. Have you solved?
AntoRei said:
Hi, I have the same problem after upgrading to 137 version. If the phone is on works with debug usb, also in fastboot mode works. Only in recovery mode windows doesn't find driver. Have you solved?
Click to expand...
Click to collapse
So I reinstalled my PC from scratch, and I could get adb working, but no fastboot, so I ended up using Linux live flash drive.
Luinwethion said:
So I reinstalled my PC from scratch, and I could get adb working, but no fastboot, so I ended up using Linux live flash drive.
Click to expand...
Click to collapse
You can use this guide with linux?
https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814