Good Morning XDA-Mindhive!
I've been encountering this issue at work with connecting my phone to my desktop, hopefully I can get a little help.
I'm currently using CleanROM 5.5.1
Kernel version 3.0.31-381038
When I connect my S3 to the computer, I'm getting the following error
There was a problem installing this Hardware:
SAMSUNG Mobile MTP device
Required selection not found in INF.
I have switched usb debugging on and off, still get the same issues, and have went directly to samsung to install the drivers, I did notice that during the install it had issues there too.
My only concern is I remember in a previous build having KTweaker, which after some research it would appear I do not have. I had intially set it up for fast charge so I would not be prompted everytime I connected my phone. I no longer have KTweaker so I'm wondering if it's possible after flashing the new clean rom if it somehow maintained that setting and is not not allowing me to connect it to my desktop.
Any ideas or more information that could help?
Hi folks,
wasn't really sure where to post this thread as my phone doesn't have a separate section and since this is more of a general issue rather than one related to a specific phone model, thought I'd try my luck here.
Anyways onto the problem - was gifted a Micromax A092 a few days back. Worked fine until last night when Windows stopped detecting it. When this issue first cropped up, a few times of disconnecting & reconnecting the USB cable got the phone working again but after I plugged in another phone to transfer data and reconnected mine, the issue became permanent and continues to persist.The phone charges when connected to the wall but doesn't charge nor does it get detected when plugged into the PC.
Now when I pull the USB cable and stick it into a different port on the PC, for a second or two, the "connected in charging mode" message appears in the pull down menu and Windows detects phone memory/storage briefly before both disappear. I haven't had the opportunity to plug it into a different machine to check whether its being detected but I can assure you that the USB cable isn't the issue as every other phone in the house works with all the cables I have been using ( 3 to be precise - 2 Micromax and a Sony cable).
Another strange thing I think I should mention in the hope that it could lead to a resolution is that ever since this issue started, none of the phones are being detected by fastboot/adb and don't appear in Device Manager under Android Device as Android ADB Interface. Just two days back, I flashed an Xperia M with fastboot but now the phone doesn't show up under Android Devices, just as Sony 0104 or something. Same with a Galaxy Star Pro. I have reinstalled Android SDK, usb drivers, fastboot/adb but no dice. Opening up the command prompt in the adb/fastboot folder and typing fastboot devices doesn't list any of these phones either.
So can someone please help me in determining whether this is a software or a hardware issue? Any suggestions are welcome and truly appreciated. Thanks.
If you updated your Windows to Windows 8.1 than have following problem:
Since Windows 8.1 MS expects a USB BOS descriptor - USB 2.0/3.0
see htthttp://blogs.msdn.com/b/usbcoreblog/archive/2013/11/26/why-does-my-usb-device-work-on-windows-8-0-but-fail-on-windows-8-1-with-code-43.aspx
There is a dirty solution which works on updated Windows 8.1 update 1:
http://forum.xda-developers.com/showthread.php?t=2598155
Maybe you need a reboot.
fanmile said:
If you updated your Windows to Windows 8.1 than have following problem:
Since Windows 8.1 MS expects a USB BOS descriptor - USB 2.0/3.0
see htthttp://blogs.msdn.com/b/usbcoreblog/archive/2013/11/26/why-does-my-usb-device-work-on-windows-8-0-but-fail-on-windows-8-1-with-code-43.aspx
There is a dirty solution which works on updated Windows 8.1 update 1:
http://forum.xda-developers.com/showthread.php?t=2598155
Maybe you need a reboot.
Click to expand...
Click to collapse
Thanks for the reply
No I haven't updated Windows. Mine's a standalone Win 8.1 installation that's been running for a good few months now.
Like I said, w/o any rhyme or reason, it stopped working in the middle of the night and so did fastboot/adb. I remember typing fastboot devices and having the phone detected just prior to Windows acting up and in following time period, I don't remember installing any software or applying any Windows updates. This issue basically just came out of nowhere.
I'll take a look at the links but will it work for someone who was already using 8.1?
XenolithicYardZone said:
I'll take a look at the links but will it work for someone who was already using 8.1?
Click to expand...
Click to collapse
These work arounds are only for Windows 8.1. The MS Patch should work, if you have not the latest patches. I have the latest patches installed and I cannot install the patch. I need the dirty solution for my old samsungs galaxy models and HTC One X with cyanogenmod 11 - M8.
At the moment I have no further ideas to help you.
fanmile said:
These work arounds are only for Windows 8.1. The MS Patch should work, if you have not the latest patches. I have the latest patches installed and I cannot install the patch. I need the dirty solution for my old samsungs galaxy models and HTC One X with cyanogenmod 11 - M8.
At the moment I have no further ideas to help you.
Click to expand...
Click to collapse
No worries man....guess what? On a whim, I plugged it back in and voila...there was detection. I have no idea how it started working but I have been at it all day and something probably did the trick though I have no clue what it was which is annoying me because if this were to happen again, I would be back to square one.
Ah I see...I did download the patch you had linked to but before I could get around to installing it, this thing started working again. Anyways good to know it won't work with the latest updates as I installed the latest Windows update just this morning myself.
Although now my phone's being detected, the fastboot problem still persists. Neither my phone or any other phones I have access to are detected via fastboot. They all show up under Device Manager as Android ADB Interface but are not recognized by fastboot. Its really irritating me because only 2 days back I flashed the Xperia M on the same damn OS but no dice now. I applied the Windows update hoping it would fix this issue but no luck so far. No software installations, no Window's tweaking...nothing. Hell I haven't even rebooted the PC in the last few days until this started happening. Strange. More research....yay
If you happen to recollect or come across any other workarounds, please do let me know.
use this driver worked for me
download these driver this is only driver fault
d-h.st/ZUh
copy link and download lenovo.zip and in device manager select android and use update driver option to install driver and its done try it works for me
get drivers from
micromax official website
The USB on my phone is not working. It charges only when the phone is off and continues to charge if I turn it on while charging from off state. I made some repairs on the phone and now the camera and flash light is not working. I checked everything 3 times (disassembling it) yet its not working. I want to flash my ROM and android to factory versions i.e. 5.0 in hopes of getting the USB and the camera to work. I want to give it a try at-least. Can anyone help me or direct me to downgrade my android without PC. Its not rooted. I tried the latest RUU on HTC site. It did not solve my problem.
I recently installed the MIUI 10 Global Beta. Since then, none of my computers or operating systems detect the device in fastboot mode.
In Linux, no device file is created under /dev.
Trying to flash anything results in errors. I'm not even able to flash TWRP through fastboot. My bootloader has been unlocked.
Has anyone else come across this issue? Does anyone know any fixes?
EDIT
Turns out, this issue is also present in some other recent Xiaomi devices. Works fine with USB 2.0, the problem occurs when using USB 3.0.
This is the first time I've heard this problem.
But I assume that you installed the new system via TWRP, so why didn't you reinstall TWRP immediately before the first start?
Did you tickled usb debugging modus in developer options?
Hi, I have a Sandisk Dual Drive USB Type-C pendrive which used to work normally with my OnePlus 6, but when I tried using it yesterday its no longer showing up. I have turned on OTG storage, restarted phone and cleared phone cache but none of this makes any difference.
I have tried using the same Pendrive in OnePlus 6T and its working without any problems. It seems like the issues with latest software update. Currently I am on OS version 10.3.4 abd Build A6000_22_200505.
Is there something can be done about this?
I'd also like to know. I've so far had zero luck with OTG storage. I've tested several pen drives on my OnePlus 6 from OOS 9 till latest 10.3.4. All of the drives I've tested on my phone without success work flawlessly on my wife's Hauwei P9.
Sorry for the late reply. My oneplus 6 has recently got 10.3.5 update and the issue still persists, not sure how this can be fixed.
Many people have been facing this issue.
Same problem here on 10.3.6 - OTG does not work BUT when I boot TWRP then it works in TWRP so this is clearly a software issue in these versions.