Develop Bugs

[Q] Cannot initiate USB data connection on GS3 (rooted, CM10; Win 7)

A few weeks after rooting and installing CM10 on my GS3, it stopped recognizing any form of USB data connection. It still charges from both computer and wall adapter, but I cannot initiate a data transfer or recognize my device using ADB.
I have tried:
three different OEM Samsung cables (from SG3/SG4 phones)
all the ports on two different Win 7 laptops
all the ports on an Ubuntu desktop
enabling or disabling USB debugging
with different combinations each time. No "USB connection" dialog has shown up on the phone, and no "new device" dialog has shown up on any of the computers. I know that I can get ADB working with a different Android phone (HTC Inspire 4G) so I know that my main laptop has USB ports that work and the cables I've tried work as well, so I'm left to assume that the issue is with the GS3. External visual inspection does not suggest the USB port on the phone is damaged, and the phone is only a year old, so I don't believe that is the cause.
Is there a system setting that I may have modified on the GS3 that would disable all forms of USB communication?
(The end goal is to get at least ADB working so I can try and recover some deleted files from the internal memory; I haven't found a reliable method that does not require ADB so I'm trying to get that to work. I know that transferring files on or off can be accomplished with the external SD card or over Wifi but that is not what I'm looking for)

Any suggestions from anyone?

I am not sure. Could be a software issue. I would try backing up your current cm ROM and try installing a fresh touchwiz ROM to see of that works, to rule out software issues. This could also be a android 4.3 issue. Could try stickmount or a similar otg app from the market.
Sent from my Nexus 7

stelv said:
I am not sure. Could be a software issue. I would try backing up your current cm ROM and try installing a fresh touchwiz ROM to see of that works, to rule out software issues. This could also be a android 4.3 issue. Could try stickmount or a similar otg app from the market.
Sent from my Nexus 7
Click to expand...
Click to collapse
I don't think any OTG app like stickmount will help; I'm not trying to connect devices to my phone. I'm trying to get my computer to recognize my phone (and vice versa) in order to get ADB working.
If I can avoid flashing a RAM I'd like to, because I'm still interested in recovering those deleted files. If that is the only thing that would help, though, then I'll do it. Any other suggestions?

Install Kies and that should get the drivers for the pc in place. Odin should recognize the device when it is in the download mode. If that works, then the pc to phone connection is OK and I'd look to software instead of hardware.
Or, if you boot into your custom recovery, either CWM or TWRP, you should be able to get ADB to recognize the device and issue commands including pulling the files on Internal storage. TWRP also has a file browser built in that might be useful.

I have tried uninstalling any Samsung drivers then using the SGS3 toolkit to install the official drivers, but that didn't change anything on the PC end.
Additionally, I tried finding my device while it was in recovery using ADB and there was no connection indication either.
I currently have CWM installed, but I didn't see a mounting option like I've seen for TWRP. Can I flash TWRP without a computer?

Or try this out: Download mode>Connect via USB>Let Windows download and update all drivers until the notification in the bottom right says it's ready to use>Unplug>Battery Pull>Boot normally>connect again. Voila! It works every time when it's being wonky and its a simple way that doesn't require a bunch of downloads!

installing insecure adb might help

Rebooting into download mode does nothing.
I believe rooting and installing CM10 means I already have insecure adb?

thanks
thanks

what next?
aEx155 said:
Rebooting into download mode does nothing.
I believe rooting and installing CM10 means I already have insecure adb?
Click to expand...
Click to collapse
I have this same issue, in download mode, the device is still not connecting.
what is the next step? I have followed this thread and have the still have the same issues.

[Q] Craziest thing: can't get USB drivers to install in recovery or booted OS mode

I've been eager to try Scott Crosler's new CM11 but didn't have time until tonight. To ensure cleanliness, at the bootloader I erased cache, system and userdata. I've flashed ROMs dozens of times, and as usual, there were no problems with fastboot recognizing the device.
I then entered CWM, and it was the darndest thing: three fast USB connection beeps and this error:
"Windows could not install driver software for your device."
But I've had the generic USB drivers installed for two years! At first I thought it was interference from the Samsung drivers when reflashing my wife's tablet, but I tried our two laptops, same result. No matter that I right-clicked "Nexus 7" in Device Manager and pointed it to freshly downloaded drivers, even that I tried installing drivers using the SDK Manager,
"Windows could not install driver software for your device."
I've read that turning off USB debugging helps, but um, with an erased /system, I had nothing to boot into!
Normally I prefer flashing via ADB sideload. To get up and running again, I flashed TWRP and used its feature of mounting USB-OTG and flashing from an external drive. Once I got into CM11, I turned on and off USB debugging, but I still can't install the USB drivers, and ADB can't recognize any devices. At least there's flashing via external flash drives.
Has anyone had the like?

didn't see win 8.1 mentioned but thought this may help? http://forum.xda-developers.com/nexus-7-2013/general/windows-8-1-users-careful-t2856908. I have had problems with drivers in past. adb composite are the ones that work for me. I simply removed drivers under android devices in device manager then plugged in device. GL.

Windows 7 here, but thanks for the suggestion anyway.
This morning I can connect it as a media device, and it's in Device Manager just fine as "Nexus 7." But turning that off, it becomes "flo" in Device Manager and can't find the updated drivers. And either way, I still can't get it recognized while in recovery mode. Ah well, as I said, at least TWRP has the option to mount USB OTB and flash files from an external drive.

Let me add that I already tried another cable (for our Samsung tablet), and tonight I see that I can connect it in MTP mode. In MTP mode, it shows up just fine in Device Manager (under Portable Devices), but turning off MTP throws it under Other Devices with the dreaded ! (and I just can't get it to install the driver no matter where I point it to). And no matter what combination I try, I still can't get ADB to recognize it at all.

Although this is for Windows 8.1 it may apply to your situation: http://forum.xda-developers.com/nexus-7-2013/general/windows-8-1-users-careful-t2856908

As I e-mailed you, sfetaz's suggestion of USBDeview is part of the solution! I still can't get it recognized in booted Android as anything but a media device, but now it's fine during recovery. Darndest thing I ever saw in 19 years of dealing with Windows drivers.
http://www.nirsoft.net/utils/usb_devices_view.html
Then in an old bookmark, I tried Koush's universal ADB drivers.
http://download.clockworkmod.com/test/UniversalAdbDriverSetup.msi
Even if USBDeview hadn't helped, it was still good to clear out all the old devices I no longer use. Definitely a handy utility to keep around and recommend.

[help] widows, ubuntu, cannot recognise OP 3 fastboot.

Problem
When I plug my phone into usb 2.0 ,usb 3.0 doesn't have any popup and I can't see it in inside device manger, windows shows "The last USB device you connected to this computer malfunctioned and Windows does not recognise it. " error message and I can't see my phone through fastboot.
Side Problems
I updated to cm14 which made my recovery, (twrp) just black screen and when i went back to cm13 it made my normal boot black screen too.
Note
Have tried multiple Cables. standard OP 3 cable and off brand white one.
Have tried many usb ports.
Have tried three computers. two Win 10, one ubuntu 16.04
Have got the Media Feature Pack for windows 10
Have got latest ADB (on all computers)
Have got latest Fastboot (on all computers)
Have got latest OnePlus 3 drivers
Thank you for reading, any suggestions or links to other threads would be very much appreciated.

laal75 said:
Problem
When I plug my phone into usb 2.0 ,usb 3.0 doesn't have any popup and I can't see it in inside device manger, windows shows "The last USB device you connected to this computer malfunctioned and Windows does not recognise it. " error message and I can't see my phone through fastboot.
Side Problems
I updated to cm14 which made my recovery, (twrp) just black screen and when i went back to cm13 it made my normal boot black screen too.
Note
Have tried multiple Cables. standard OP 3 cable and off brand white one.
Have tried many usb ports.
Have tried three computers. two Win 10, one ubuntu 16.04
Have got the Media Feature Pack for windows 10
Have got latest ADB (on all computers)
Have got latest Fastboot (on all computers)
Have got latest OnePlus 3 drivers
Thank you for reading, any suggestions or links to other threads would be very much appreciated.
Click to expand...
Click to collapse
Normally when your phone is not recognised, it indicates a driver problem. On Win10, it happens invariably. So search and find ways of properly installing OP3 drivers on Win10. There are umpteen threads in OP3 sub forum.
On black screen, are you using TWRP 3.0.2-23? If not search for it and install it. If nothing works, go to the Mega Unbrick Guide.

Hm thats odd, but its recognized in MTP mode?
I would suggest to only use ubuntu for that cause you don't have that struggle with drivers.. I will flash TWRP on my OP3t now and report back if its working

Black screen on recovery is because of the firmware compatibility with the recovery. Use eng.stk's modded twrp.
If "fastboot devices" doesn't return you anything, try typing the device id after fastboot. Like if you want to flash a recovery, type fastboot -i 0x2a70 flash recovery ---.img
If that doesn't work out, I don't know of any other workaround. If you find a fix, do let us know.

*Mod, please delete this.*
Unwanted post.

How did you go about installing fastboot drivers for Ubuntu? If your device isn't recognised in fastboot I'm sure it's a driver issue.

Needed to reinstall drivers, by disabling device and installing drivers then plugging my phone in.
Phones fine now.
Thanks for the help.

[KF HD7 2nd] after trying return2stock system recognition unstable, TWRP ok, USB ok

Hi,
I had a running N2AOS with CM12 install, then did a return2stock but something went wrong
I have orange/blue boot sequence and can get into TWRP without a problem, can boot into fastboot etc. from TWRP. Battery is 100% - ok, too
But system seems empty now. Maybe wiped wrong. I see a lot of empty folders incl. sdcard etc. I've basic ux knowledge - can use TWRP terminal or file manager.
Is there a chance pulling a rom in the twrp using the usb? On win 8.1 I can delete the adb/amazon drivers. then it gets recognized as "Kindle" or "Tate", but can't connect.
My primary system is macOS Sierra, but have a running windows 8.1/ubuntu laptop with usb 2/3.
I think I'm equipped perfectly and the KF7HD2 is not hard bricked, but leaking adb/kindle knowledge. and the most trys end up with "< waiting for device >"
update: when I try TWRP > mount (anything) it gets recognized by win 81 or ubuntu for a short time, but I can't read or write a thing
maybe someone could help?! I read and tried as much as possible, but don't want to kill my old kindle because my girlfriend wants to read with it
thank you very much!
best
tom

addition: can I connect via twrp console and usb or wifi to a local ip or sth to use ftpget

really nobody an idea?

pixel 2 xl refuses data connection with all computers except one.

Hi so i installed twrp and rooted my pixel with magisk. everything went fine.
saw the sultan kernel decided to flash but my phone does not recognize any computer with any cable as a computer but as a powersource. Adb and fastboot not working on any laptop or desktop (except the desktop on which i unlocked my bootloader and rooted my device) tried to connect over usb (adb fastboot filetransfer) on Linux Windows and MacOs. all unsuccesfull.
dev options is on:
oem unlock toggled
usb debug toggled
phone is running stock rom stock kernel. (Edit: kernel is the sultan kernel on stock rom)
once i connect the phone sees it as a pc pops op usb options then blacks it out because it sees it as a powersource.
whats wrong with it i cant figure it out...

Nightfall41 said:
Hi so i installed twrp and rooted my pixel with magisk. everything went fine.
saw the sultan kernel decided to flash but my phone does not recognize any computer with any cable as a computer but as a powersource. Adb and fastboot not working on any laptop or desktop (except the desktop on which i unlocked my bootloader and rooted my device) tried to connect over usb (adb fastboot filetransfer) on Linux Windows and MacOs. all unsuccesfull.
dev options is on:
oem unlock toggled
usb debug toggled
phone is running stock rom stock kernel.
once i connect the phone sees it as a pc pops op usb options then blacks it out because it sees it as a powersource.
whats wrong with it i cant figure it out...
Click to expand...
Click to collapse
I'm in very much the same situation. I've seen several USB connectivity threads roll through here recently so I'm not sure if anything larger is going on or not. Basically, I always do updates with full factory images w/o wiping. I was able to install the April update (in early April) just fine. I went back in late April to try to use fastboot and couldn't connect via USB for file transfer, ADB, or fastboot. I updated all my platform tools and the Google USB driver which made no difference. I tried on 3-4 Windows 10 desktops/laptops and 1 MacOS laptop. Nothing. I opened a support ticket with Google (and went through extensive troubleshooting steps) which was then escalated. It has been over a week and they have not responded. I even checked back yesterday to make sure it wasn't lost in the shuffle, and I was assured that it was still active and assigned to the proper team.
Just for giggles, I tried connecting to a Win7 desktop w/ only USB 2.0 and the phone immediately connected MTP (we had made this the default USB mode during the troubleshooting process). Since I was still running a modified (root) kernel, I went ahead and tried flashing the stock boot image with fastboot (both slots) and it worked! I figured since I had already wiped the phone for troubleshooting, I would try pushing the entire April image (w/ wipe). It flashed bootloader, radio, and maybe boot image (can't remember), but then lost connectivity when trying to push the system image. Fortunately, the phone booted right back up. Since then, connectivity is possible, but sporadic, on that machine. Being 100% stock, with no other options, I knew the only way to get an entire factory OTA pushed to the phone would be to opt into the beta, install the beta, then opt out, which pushes the latest non-beta and wipes the phone. I did this, but, again, it resolved nothing.
BTW, for me, this issue affects all devices that pass data through the port including USB OTG flash drives and game controllers. It's also not cable specific as I have tried a factory Google USB-A to C cable, factory Google USB-C to C, and several other USB-A to C cables (the ones I always use for ADB and fastboot commands). There does not appear to be any physical damage to the port and I cleaned it extensively with compressed air and a plastic dental pick.
Sorry I don't have a solution at this point, but I wanted to pass on the steps that I have taken.