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?
Related
Hi everyone, first, this is my first post, new to the forums, at least as a registered user. I have a problem with my phone. I know most of you are wondering why I have not just read the other posts on the forums, but I have. I have attempted every solution to the problem posted previously.
Background: Phone: Samsung charge.
I was being impatient and did not want to wait for the gingerbread update form Verizon. I flashed the leaked gingerbread 2.3.4 onto my phone using odin. Everything went great. I was able to use my phone with no problems except shortened battery life, but nothing major. About a month ago the battery life was impossible to maintain and there were some software bugs, like clicks during calls, startup taking forever, around 2 minutes on average!, and random restarts that never happened before. I decided to look up some fixes and found that verizon and samsung had released GB 2.3.6 for the charge. I got excited and decided I wanted to get that, but I could not via OTA. I read some forum posts and they mentioned attempting a factory reset on the phone then trying OTA update. I went ahead with factory reset and everything went fine. My startup time is around 25 seconds now and no random clicks or gliches, but still not on 2.3.6, which was the whole point. I then decided to just flash the stock 2.3.6 rom to the phone.
Problem: When I plug my phone in to multiple computers it will charge but not connect to the computer. This means on my Mac it does not show as an external drive, which it has in the past. On my windows 7 machine it says that drivers were installed but could not be used (I can get the exact quote if needed.) I attempted to go into device manager and solve problem that way but it shows my phone as "unknown device". I have tried to enter download mode when hooked up to windows computers and no connection is found.
Possible solutions attempted and their outcomes:
1. As stated, I attempted the method shown in a thread on droid forums for installing the samsung drivers. I have attempted multiple times to install the drivers on my windows machine and the device remains "unknown".
2. I have attempted multiple cables on multiple computers, both mac and windows 7. No change.
3. I have installed adb and attempted to locate devices using adb devices command on mac. No devices found.
4. I have attempted all methods with both usb debugging checked and unchecked.
5. I have tried every possible usb port I have.
Ideas/questions I have had that I have no idea are possible or how to fix!
Would a factory reset take away the ability to connect to a computer from my phone. So, is there a piece of software in the build I have that controls the connection between the computer and the phone, an identifier of sorts, which is now missing, now that I have reset the leaked ROM.
Is there a way to flash a new ROM without connecting to a computer, via the sd card, and what is that? I have read some things in other posts but am too much of a n00b to understand most of them when using sdcards.
ANY help will be greatly appreciated. PLEASE PLEASE PLEASE!!! I have been at this for at least 6 hours, sifting through forums, searching google, attempting fixes that others have stated worked for them, only to fail every time. Thank you all.
i've had a few issues with this on my Droid Pro. with windows connection a connection assistant came up with some options that I was able to get it to work as a drive.
Getting it to work with adb is another issue alone. The phone needs to be in "debug" mode. I would search for a tutorial on this because you need to edit files on the computer.
for example on my windows I needed to edit one set of files, while on my linux I had to edit another set of things.
I leave my phone in debug mode because i use it for my android app dev on both computers. try that and see if it shows up on your mac.
I have a strange issue with my G2x. A couple of months ago I was trying to sync my music with my phone and the computer wouldn't recognize the phone as a disk drive. At first I chalked it up to the computer I was using at is was old and hadn't been rebuilt in quite a while. I had installed the LG USB drivers already, but just for kicks and grins I installed them again. Still nothing. I decided to rebuild my computer and reinstall the LG USB drivers. Still nothing. The phone charges, but Win 7 doesn't see it.
Fast forward to yesterday. I want to restore my phone to stock so I can get the new BB & stock 2.3.4. I installed the APX driver and when I plug the phone in, I get an error code 10 in Device Manager - the device cannot start. I researched that and found nothing helpful. I tried using another computer that I know used to work with that phone, still nothing. I tried the LG Phone updater - it can't find the phone either. I also tried the KDZ updater - it can't find the phone either (even with the phone in Software Update mode). I also tried several different USB cables.
The phone is rooted and I can change between ROMs with no issues, provided I pull the SD card and copy the ROM to that, or download it directly to the phone.
I think the USB port on the phone is hosed. Any suggestions on how to get the updated BB & 2.3.4 on my phone so I can get a warranty replacement?
[edit] - I am on Windows 7 64 bit.
mjoseph472 said:
I have a strange issue with my G2x. A couple of months ago I was trying to sync my music with my phone and the computer wouldn't recognize the phone as a disk drive. At first I chalked it up to the computer I was using at is was old and hadn't been rebuilt in quite a while. I had installed the LG USB drivers already, but just for kicks and grins I installed them again. Still nothing. I decided to rebuild my computer and reinstall the LG USB drivers. Still nothing. The phone charges, but Win 7 doesn't see it.
Fast forward to yesterday. I want to restore my phone to stock so I can get the new BB & stock 2.3.4. I installed the APX driver and when I plug the phone in, I get an error code 10 in Device Manager - the device cannot start. I researched that and found nothing helpful. I tried using another computer that I know used to work with that phone, still nothing. I tried the LG Phone updater - it can't find the phone either. I also tried the KDZ updater - it can't find the phone either (even with the phone in Software Update mode). I also tried several different USB cables.
The phone is rooted and I can change between ROMs with no issues, provided I pull the SD card and copy the ROM to that, or download it directly to the phone.
I think the USB port on the phone is hosed. Any suggestions on how to get the updated BB & 2.3.4 on my phone so I can get a warranty replacement?
[edit] - I am on Windows 7 64 bit.
Click to expand...
Click to collapse
Do you have USB debugging turned on in Settings, Applications, Development? That may help get connected to the Win7 PC.
Yeah - USB debuggin is on.
I had the same problem a little while ago. The solution for me was to install the drivers throught the updater application available on T-Mobile's website. I'm not sure why directly installing the drivers doesn't work, but that's just how it is for some people, apparently.
---------- Post added at 02:57 PM ---------- Previous post was at 02:56 PM ----------
Oh, and turn debugging OFF
Yeah, i would turn off usb debugging, as then you can't get to USB Mass Storage. I would also try uninstalling and reinstalling the LG USB Drivers, and then try it again.
I have tried all manners of the solutions presented. Installing drivers from the LG Update tool, from the LG website, with and without USB debugging, with and without the SD card (saw that somewhere else). The more I work on it, the more I believe the USB port is bad. Thank goodness I can still charge it. The guy at the T-mobile store states I can get a new phone in 3 months. So I think I will just live with it for the time being.
What ROM are you on? I remember having problems with some of the ICS ones.
Kinda shocked no one said did you make sure you have USB set for mass storage? Thats usually the most common thing to miss. If your using ICS I'm gonna take the guess of HFS? Which i know for a fact he posted the update morfic kernel so you can use mass storage. If your not using HFS, then you should try it first and then worry about the USB.
This is ROM independent. I've used pretty much all ROMS for the G2x, most recently Owain's ICS, Weapon and right now HFP - all experience this issue. As stated in the original post, though, it doesn't work with the APX drivers when trying to flash CWM or go back to stock. No matter which ROM, when plugging in to Windows, there is not the distinctive sound that a device has been added.
mjoseph472 said:
This is ROM independent. I've used pretty much all ROMS for the G2x, most recently Owain's ICS, Weapon and right now HFP - all experience this issue. As stated in the original post, though, it doesn't work with the APX drivers when trying to flash CWM or go back to stock. No matter which ROM, when plugging in to Windows, there is not the distinctive sound that a device has been added.
Click to expand...
Click to collapse
Check your device manager in the properties (open computer, right click, selct properties, should be the first or second option on the right side, will open in a new window). Open the option all the way at the bottom and you should see something like USB ADB storage device. If its there then you should be able to access it. USB debug and USB mass storage should both be on, try adding "allow mock locations," and if none of the above work, try doing it the old fashioned way. Get the Micro SD adaptor and plug it into the computer that way.
My Samsung Galaxy R stopped working all of a sudden. It is not powering up at all.
When I tried to connect it to the computer, it shows "Installing APX driver" which does not install and in the device's window the phone is listed under "Unspecified" tab as "APX" with need to troubleshoot.
I want to know if this is a software issue and if I can retrieve any of my data aboard the phone memory. I have very important contact information and images that I need to retrieve.
gothic_dude said:
My Samsung Galaxy R stopped working all of a sudden. It is not powering up at all.
When I tried to connect it to the computer, it shows "Installing APX driver" which does not install and in the device's window the phone is listed under "Unspecified" tab as "APX" with need to troubleshoot.
I want to know if this is a software issue and if I can retrieve any of my data aboard the phone memory. I have very important contact information and images that I need to retrieve.
Click to expand...
Click to collapse
Install latest kies & Driver of your mobile. Then reboot & connect the Phone via USB. It will detect "adb driver". Btw what last you have done.? Can you brief yourself.?
Thanks
Disturbed
The last thing I did was turn off the internet and then switch off the screen.
I updated Kies to the latest version and there has been no change at all.
The issue is still the same.
I had a similar problem and issue was that the mobo needed to be replaced, luckily i was in warranty period then so got it replaced for free. Though I still don't know what had caused the problem.
Sent from my GT-I9103 using Tapatalk 4 Beta
I've encountered a problem that I'm thoroughly convinced no one can help me fix (mostly due to the amount of time I've already put into seeking a fix). I recently rooted my phone, and it worked, but now I am starting to experience problems. I used VRoot to root the phone. All of the problems I'm experiencing happened after an attempt to boot my phone into recovery mode using the ROM Manager application.
PHONE INFORMATION
Model # - VS870 4G
Firmware - 4.1.2 (Jelly Bean)
Kernel version - 3.4.0-g2696711 [email protected]
Build # - JZO54K
Software version - VS87012A
Issue 1:
My phone no longer connects to wi-fi. Upon selecting the connection and inputting the pass-code the phone only saves the connection but makes no attempts to connect. It can't possibly be the router that is causing the issue because the phone was able to connect flawlessly before I tried booting into recovery mode.
Issue 2:
My phone's status is currently "Rooted" but it doesn't behave like a rooted phone. When attempting to install applications that require root, the applications insist on informing me that my phone is indeed not rooted. When attempting to re-install lost applications after the numerous amount of hard resets I've done, the applications are shown to be already installed yet they are nowhere to be found on the phone.
Issue 3:
Even after installing the updated USB drivers (and multiple re-installs) any computer I plug the phone into refuses to recognize the phone if it is in Emergency mode, yet it is still recognizable in the default mode.
Issue 4:
In order to install apps, I have to download the .apk file because my phone will not connect to Google Play even when I'm directly connected to the internet via usb or using 4G. Various other applications that require an internet connection refuse to work as well which is making the troubleshooting process extremely frustrating.
Fixes I tried -
Reboot, hard reset, battery/SIM/SD removal, selecting the "Avoid poor connections" option, reset router, re-setup wireless connection (tried without a pass as well), switching the IP setting to "Static" (doesn't allow me to select connect if it is on static), toggled the 802.11g only mode, toggled the routers DHCP server option, unrooting phone (SuperUser deems it impossible due to the lack of a su binary, which I don't understand seeing that when the phone is in emergency mode the status of the phone is "Rooted"), installing a stock firmware install via KDZ, as well as failed attempts to manually install CWM (my purpose of trying to manually install CWM is due to a lot of the fixes I found having "being able to boot in recovery mode" as a requirement, which my phone lacks)
So here is/are my question(s):
If I'm not able to unroot the phone, is taking the phone to a manufacturer no longer an option?
Is there a way to "reset" the wireless hardware/software on the device directly that works around my current issues?
Are there any alternatives to installing the KDZ stock firmware file where the device isn't required to be in Emergency mode?
I'm still not exactly sure what a su binary is but is there a way to install it independently?
Thanks in advanced~
And the intricate thesis pattern.
k.imora said:
I've encountered a problem that I'm thoroughly convinced no one can help me fix (mostly due to the amount of time I've already put into seeking a fix). I recently rooted my phone, and it worked, but now I am starting to experience problems. I used VRoot to root the phone. All of the problems I'm experiencing happened after an attempt to boot my phone into recovery mode using the ROM Manager application.
PHONE INFORMATION
Model # - VS870 4G
Firmware - 4.1.2 (Jelly Bean)
Kernel version - 3.4.0-g2696711 [email protected]
Build # - JZO54K
Software version - VS87012A
Issue 1:
My phone no longer connects to wi-fi. Upon selecting the connection and inputting the pass-code the phone only saves the connection but makes no attempts to connect. It can't possibly be the router that is causing the issue because the phone was able to connect flawlessly before I tried booting into recovery mode.
Issue 2:
My phone's status is currently "Rooted" but it doesn't behave like a rooted phone. When attempting to install applications that require root, the applications insist on informing me that my phone is indeed not rooted. When attempting to re-install lost applications after the numerous amount of hard resets I've done, the applications are shown to be already installed yet they are nowhere to be found on the phone.
Issue 3:
Even after installing the updated USB drivers (and multiple re-installs) any computer I plug the phone into refuses to recognize the phone if it is in Emergency mode, yet it is still recognizable in the default mode.
Issue 4:
In order to install apps, I have to download the .apk file because my phone will not connect to Google Play even when I'm directly connected to the internet via usb or using 4G. Various other applications that require an internet connection refuse to work as well which is making the troubleshooting process extremely frustrating.
Fixes I tried -
Reboot, hard reset, battery/SIM/SD removal, selecting the "Avoid poor connections" option, reset router, re-setup wireless connection (tried without a pass as well), switching the IP setting to "Static" (doesn't allow me to select connect if it is on static), toggled the 802.11g only mode, toggled the routers DHCP server option, unrooting phone (SuperUser deems it impossible due to the lack of a su binary, which I don't understand seeing that when the phone is in emergency mode the status of the phone is "Rooted"), installing a stock firmware install via KDZ, as well as failed attempts to manually install CWM (my purpose of trying to manually install CWM is due to a lot of the fixes I found having "being able to boot in recovery mode" as a requirement, which my phone lacks)
So here is/are my question(s):
If I'm not able to unroot the phone, is taking the phone to a manufacturer no longer an option?
Is there a way to "reset" the wireless hardware/software on the device directly that works around my current issues?
Are there any alternatives to installing the KDZ stock firmware file where the device isn't required to be in Emergency mode?
I'm still not exactly sure what a su binary is but is there a way to install it independently?
Thanks in advanced~
Click to expand...
Click to collapse
Any luck? I am having basically the exact problems you are talking about and was wondering if you found a fix or what you ended up doing. Thanks.
do a rollback is needed
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