So all of the sudden my computer, or other computers wont recognize my phone.
I might be answering myself, but maybe my socket is kind of/might of broken?
When I connect it, I still get the CHARGE ONLY or DISK DRIVE option, but my computer(s) doesnt recognize it. I have to try several times inserting it for my computer to recognize it. I used my other HTC INSPIRE chargers..same problem..
I read on other forums that, their device is having the same problem as mine, at all of the sudden.
even my USB DEBUGGING mode wont recognize on the computer..
help....
EDIT: some people are saying something about MOUNTING/UNMOUNTING SD CARD.
If you're using windows, check the device manager and make sure it's not an "unknown" device. If it is, try manually installing the device (using HTC sync drivers or Android SDK drivers). If that doesn't work, open the properties of the unknown device, and find the device ID and check it against the listed ID's in the .INF files for the driver. (Had to hack them recently to get ADB working, presented the "wrong" device....)
Related
I originally posted this inside the Glorious Overdose V2 thread, but decided to post here as well.
For some reason my computer won't recognize my Sidekick when I plug it in via usb. I do have the samsung drivers installed and it will read my friends Samsung Droid Charge just fine, but when I plug my Sidekick in it comes up saying "USB Device Not Recognized". So far I've tried uninstalling and reinstalling the drivers from the device manager to no avail. Wondering if anyone has an idea as to what it could be. I've also tried googling the solution and everyone says to just uninstall and reinstall the drivers and it should work. Now the phone is not plugged into a USB Hub, extender, or case, it is plugged directly into a usb port on the mother board.
PC Specs just in case:
Motherboard - Gigabyte GA-970A-D3
OS - Windows 7 Ultimate x64
CPU - AMD FX-4100
Memory - 8GB DDR3 1066
Phone:
T-Mobile Sidekick 4G running Glorious Overdose V2
Nothing added just the rom and some apps/games.
I have tried with USB Debugging on and off, either way does not work.
Update: I have since tried Kies mini, as well as the drivers found on Softpedia. Neither of those worked, so I just got done reformatting and reinstalling Windows hoping that would work. At first it did not, right now I am running windows update to see if that was the issue, I'll update of what the outcome is.
Update: After installing all available Windows updates it's still not recognizing the phone. Now no matter what it's saying it's an Unknown Device. Even after I try and do a manual driver update and tell it to look in the folder with the driver files from Softpedia. I'm at a complete loss now.
If anyone has any idea's please let me know.
What mode do you have the phone in? Settings->Applications->USB Settings. It should be in Mass Storage if you want to access its SD Card.
Maybe put another rom on the sd card and flash something else, I don't think it would be a rom issue but it would be worth a try?
Sent from my SGH-T839 using XDA
Jax184 said:
What mode do you have the phone in? Settings->Applications->USB Settings. It should be in Mass Storage if you want to access its SD Card.
Click to expand...
Click to collapse
It's set to USB Debugging. But even then, it should read as something else other then Unknown Device when I plug it in. I have tried plugging it in and selecting Mass Storage, still comes up as Unknown Device.
HewettBR said:
Maybe put another rom on the sd card and flash something else, I don't think it would be a rom issue but it would be worth a try?
Sent from my SGH-T839 using XDA
Click to expand...
Click to collapse
I've thought about that, and from everything I can see it's either the ROM or the drivers. So we'll see...I'll probably try a different ROM and see what happens.
I suggest turning USB debugging off and mass storage on, for how you'll be using it. And recall that you have to change this stuff with the USB cable unplugged.
I've tried that, and after talking with the T2 Technical Support from Samsung for 45min today, the only option left is to send the phone in to get worked on. Though, I'm going into the T-Mobile store and see if they can't replace the phone or give me a loner while this one is out getting repaired.
More info request.
Can you provide us with the names and links to the drivers you have tried?
DuctTapedGoat said:
Can you provide us with the names and links to the drivers you have tried?
Click to expand...
Click to collapse
Kies Mini - http://www.samsung.com/us/support/owners/product/SGH-T839HABTMB
Softpedia - http://drivers.softpedia.com/get/MOBILES/Samsung/SAMSUNG-USB-Driver-1480.shtml
As well as the Samsung Vibrant drivers from both of those sites.
Samsung SideKick 4G Drivers
www DOT filedropper DOT com FWSLASH sk4gx64drivers
This is the exact drivers I pulled off of my own machine, I ran into massive issues with those same driver packages, especially in getting the initial root to take with a few different utilities designed to grant sudo/su/root access, and these are the drivers I have running currently, just pulled off my own machine. I run Windows 7 x64, but as well, there should be no reason why these drivers wouldn't work on a x86 machine and/or OS.
NOTE : I apologize it's not a proper link, but I'm unable to post a raw link until I hit my 8th post. I will come back and fix this after I hit that 8th post, but until then it will be ghetto-bypass HTML.
DuctTapedGoat said:
www DOT filedropper DOT com FWSLASH sk4gx64drivers
This is the exact drivers I pulled off of my own machine, I ran into massive issues with those same driver packages, especially in getting the initial root to take with a few different utilities designed to grant sudo/su/root access, and these are the drivers I have running currently, just pulled off my own machine. I run Windows 7 x64, but as well, there should be no reason why these drivers wouldn't work on a x86 machine and/or OS.
NOTE : I apologize it's not a proper link, but I'm unable to post a raw link until I hit my 8th post. I will come back and fix this after I hit that 8th post, but until then it will be ghetto-bypass HTML.
Click to expand...
Click to collapse
Thank you, I tried unpacking them to a folder on C:\ went into Device Manager, right clicked on the Unknown Device, Update Driver Software..., Browse My Computer for Driver Software, Set the search to C:\, and still saying Unknown Device is the best driver software for it. No idea why it's doing this.
Proper Driver Update
What is going on is that Windows is seeing a more recent signature file attached to the SK4G drivers on your computer (I don't believe anything at all is wrong with your device) than the working ones there.
First, in Add/Remove Programs, uninstall the Samsung Kies and Samsung Driver pack you installed earlier. Now...
Go into on your PC:
://windows/system32
And locate the same file names, cut them all, and paste them in a temporary folder you create, preferably on the desktop or something similar. You may not find every file, and that's okay, just the ones you can find. Next, you will be wanting to paste the driver files from the package I uploaded. Now, turn off Automatic Updates, so it doesn't automatically install drivers upon connection. Reboot the computer, double check and make sure Automatic Upates are off when you log back on. Now, connect the device and see if it gives you the same results. By removing the old drivers which don't work, you'll be able to force it to the ones we know work, and you /should/ have success. As well - USB data debugging active and activating connection for data transfer via the notification pulldown menu would be the best way to do this initially.
Would I be looking in c:\windows\system32\drivers for the same file names as the ones you packed up?
Ok, so the only one I could find in the drivers folder was modem.sys. But it will not let me move/replace the one that's already in there. It's telling me access is denied, same thing when I try and set the permissions it will not let me. I am logged in as an Administrator, as well it says it when I log in as THE Administrator account. So yeah...
Cool - modem.sys is a stock one that is shared with the device, so that's fine.
With the other two programs uninstalled, the old drivers uninstalled, and forcing it into those by pasting them into //win/sys32/drivers you should be in business. Hmm. You can try UnlockRoot.com's device rooter - I know they have an auto driver detector in their program. As well, you can try SuperOneClick, but I don't remember if they do or no. What about going in from the Recovery menu and toggling USB? Anything wierd going on in the /mounts? What about ADB shell access from the Android SDK on Windows?
DuctTapedGoat said:
Cool - modem.sys is a stock one that is shared with the device, so that's fine.
With the other two programs uninstalled, the old drivers uninstalled, and forcing it into those by pasting them into //win/sys32/drivers you should be in business. Hmm. You can try UnlockRoot.com's device rooter - I know they have an auto driver detector in their program. As well, you can try SuperOneClick, but I don't remember if they do or no. What about going in from the Recovery menu and toggling USB? Anything wierd going on in the /mounts? What about ADB shell access from the Android SDK on Windows?
Click to expand...
Click to collapse
I tried plugging the phone in, still showing up as Unknown Device. Tried UnlockRoot.com's program, no change. Installing the Android SDK right now, as well as I tried deleting the INFCACHE.1 file, and no change with that either. Once I'm done installing the Android SDK I'll redelete the INFCACHE.1 file and restart and try the phone again.
I did go in and check the mounts in recovery and they were set to:
UNMOUNT CACHE
MOUNT DATA
UNMOUNT SDCARD
UNMOUNT SYSTEM
Thank you for your help so far.
UPDATE: So after installing the Android SDK, deleting the INFCACHE.1 file, restarting, and then plugging the phone in, comes up and says the USB Device is Not Recognized. Then goes to search the preconfigured driver folders, and fails to install the driver for Unknown Device. And ADB Devices shows no devices as well(didn't think it would, but yeah).
UPDATE: So after using my friends phone as a conduit to throw the Stock Odexed KJ2 w/ Root(http://forum.xda-developers.com/showthread.php?t=1328698) onto my SDCard and flashing that the phone seemed to go into a soft brick at pre-boot screen(where it says SAMSUNG T-Mobile blah blah blah). Mind you this would freeze before it was even able to get into recovery. So I took it into T-Mobile and they are doing a manufacturer warranty replacement. So hopefully this next phone will be able to connect to the computer and be read correctly.
So I have an unrooted standard MT4GS phone and trying to start the rooting procedures, but my computer is not recognizing the phone in anyway other than in disk drive mode. When installed all of the fast boot drivers, standard drivers, HTC sync, rebooted both computer and device, it still is not recognized at all. I have usb debuggin on and i have tried all modes when connected to pc (tethering, disk drive (recognizes it as a removable disk), and charge only). Any ideas what I am doing fundamentally wrong? PS I have searched the forum multiple times for answers but to no avail. Thanks in advance.
I think I have a solution, but I'm not sure. I think you are missing the drivers for it. Google HTC Drivers and it should be the one that's named HTC Drivers 3.0.0.7 or something similiar.
Make sure USB debugging is turned on...
slivingston said:
So I have an unrooted standard MT4GS phone and trying to start the rooting procedures, but my computer is not recognizing the phone in anyway other than in disk drive mode. When installed all of the fast boot drivers, standard drivers, HTC sync, rebooted both computer and device, it still is not recognized at all. I have usb debuggin on and i have tried all modes when connected to pc (tethering, disk drive (recognizes it as a removable disk), and charge only). Any ideas what I am doing fundamentally wrong? PS I have searched the forum multiple times for answers but to no avail. Thanks in advance.
Click to expand...
Click to collapse
Try going into Control Panel ===>System===>Device Manager ===>USB Controlers & you should see a listing for a Mass Storage Device. If you'll right click on that & reinstall drivers it might get you going. I had to do that myself. It may not want to overwrite the installed ones so you might have to uninstall & REinstall.
You need to install HTC Sync, it will provide the drivers for Windows 7.. after it's installed you can just plug in the device and windows will find and install it. Then you have to close HTC Sync and continue.
I have a Nexus 5 that I have had about a month now and I had the USB on it working before about a week ago. I plugged it in today and neither my desktop or laptop could recognize it anymore. Both computers are running Windows 8.1.1 and the issues seems to be new as I can neither get USB storage or ADB to find it. The closest I can get it to working is to switch the USB mode to PTP and it reads that but I don't want to pull photos off. When I have it in MTP, it makes the sound of it plugging in and my phone shows it is plugged into a computer but Explorer shows nothing and it says it is working normally in device manager. I've tried everything from enabling and disabling debugging, restarted both my phone and computer tried reinstalling the drivers (both by the computer automatically finding them and manually installing them) but nothing seems to work. Is it possible that Windows Update could of broke the drivers since my computer installed updates yesterday? I also have Linux on my laptop and it appears to read fine with Linux.
That's the exact issue. If you check in Device Manager you'll see it listed as 'ACER ADB Device' (or something like that). You have right-click on it, select update driver, manually check and go through the list option and choose the MTP driver and it'll work again (and with USB Debugging enabled if you don't usually have it on like me)
I theorise that it's happened cause the Acer driver is digitally signed and the Google ones aren't but I could be wrong. Either way, it's a PITA
EddyOS said:
That's the exact issue. If you check in Device Manager you'll see it listed as 'ACER ADB Device' (or something like that). You have right-click on it, select update driver, manually check and go through the list option and choose the MTP driver and it'll work again (and with USB Debugging enabled if you don't usually have it on like me)
I theorise that it's happened cause the Acer driver is digitally signed and the Google ones aren't but I could be wrong. Either way, it's a PITA
Click to expand...
Click to collapse
OK thanks. I'll give it a try because it was showing up as ACER ADB Device under device manager
EDIT: I updated the drivers and used the USB composit drivers instead and it got MTP working again. When I set it to USB composit, it installed Google's ADB drivers and the Nexus 5's USB drivers so everything is working again. Thanks for your help
EddyOS said:
That's the exact issue. If you check in Device Manager you'll see it listed as 'ACER ADB Device' (or something like that). You have right-click on it, select update driver, manually check and go through the list option and choose the MTP driver and it'll work again (and with USB Debugging enabled if you don't usually have it on like me)
I theorise that it's happened cause the Acer driver is digitally signed and the Google ones aren't but I could be wrong. Either way, it's a PITA
Click to expand...
Click to collapse
I can´t manually update driver because of this:
when i update the acer adb it says the driver is up to date and everything is all same. what to do?
Thanks! Thought I was going to go crazy. Worked for me...
i set the driver to MTP as mentioned above and the phone started to show up on the explorer but now i couldnt copy any files from my laptop to the
phone. It displays like that and if clicked yes then the copy wouldnt happen.what is the problem.
Uninstall driver, plug in device, tell windows to not auto install driver (or disconnect from internet), click to update or install driver, point to folder with drivers, install, all is done.
wangdaning said:
Uninstall driver, plug in device, tell windows to not auto install driver (or disconnect from internet), click to update or install driver, point to folder with drivers, install, all is done.
Click to expand...
Click to collapse
actually i did all the process above(when the phone was not appearing) and then i got to display the thing on the explorer. and shall i do it still what you say.
Big tree said:
actually i did all the process above(when the phone was not appearing) and then i got to display the thing on the explorer. and shall i do it still what you say.
Click to expand...
Click to collapse
That msg comes when you're in PTP mode I think...Only certain formats are supported.
Check under storage, expansion menu and make sure you are set to the first option...not PTP.
Above guy mentioned to have phone in USB debugging mode when setting up drivers.
If the device is showing then you need to point to the drivers for it (download them from google). I reinstalled windows a few days ago and had the acer issue (device first shows up in device manager as nexus 5 then switches to acer), windows wants it to be an acer device. Stop windows and then install the correct drivers,
For me I had to click the auto install in windows tray and tell it to stop. After a few times it worked.
No I'm connecting in MTP mode. Ahh its gettn irritating.
I was moving some pictures from my phone to my computer today, and windows explorer stopped working when it was almost done.
I started windows explorer again and selected the memory of my phone and it was loading really long (longer then the first time).
So I plugged the phone out of the computer (without ejecting it) and now my computer doesn't recognize my phone anymore .
(the computer does recognize the phone, and it will charge so the cable works, but it fails to install a driver for my device)
I already tried this:
Rebooting my phone and computer.
Using another USB port.
Checking if my settings on the phone where correct.
Plugging the phone into my brothers computer and that worked (so the problem is with my computer, not my phone).
Uninstalling the drivers of my phone by going to my Device Manager. (I uninstalled MTP USB-device, under Portable Devices)
I tried to update my drivers (MTP USB-device) and I clicked browse my computer, let me pick, ok.
Could someone please help me?
Hi,
I have a very serious problem with my OnePlusOne (64GB) after updating to version YOG4PAS3JL. Since the update, ADB no longer recognizes my phone.
It doesn't depend on the computer I'm using, I have tried to use my phone on 3 different computers (Windows) that I use on a regular basis and none shows my phone with the command adb devices.
Connecting via MTP is no problem, but when I enable Android debugging with USB, my phone will not show up in Windows Explorer.
I have also attached a Samsung Galaxy Note 4 and a HTC phone, both are recognized by ADB.
If I change the mode to MTP, it will show up as portable device called A0001 in the windows device manager. If I switch to Android Debugging, it will simply disappear and not show up
as "other device" or usb device without driver. So I can't even reinstall Android ADB Interface, it also doesn't show up in the Device Manager any longer. If I try to install a driver for my OnePlus One when it is in MTP mode, it will also only allow me to install MTP drivers (no possibility to install the previously so fine working Samsung USB drivers).
I have literally tried every solution out there I have found, from unplugging and restarting my phone, using different USB ports, using different USB cables, reinstalling Samsung USB drivers (didn't help as phone did not show up as unrecognizes device any longer), uninstalling Google USB driver, adding OnePlusOne to the .inf usb driver file myself (which mostly resulted in an "no compatible driver was found in this folder"-error), installing fastboot (didn't change anything), universal adb driver setup, pdanet, using USDBDeview, removing drivers with the bacon root toolkit to removing mtp files from the inf folder of windows to prevent MTP driver installation, but nothing worked
I would prefer to go back to the version before YOG4PAS3JL, where ADB worked fine or install a different ROM, but I have seen that every guide states that you need to have ADB to install a new ROM. As my phone is not rooted and I can no longer use ADB with my phone, I'm basically pretty stuck and don't know what to do I'm pretty desperate after two days of trying to solve this problem without success and would be so thankful for any suggestion what I could do.
Same situation...let me know if you find any solution.
Same situation here. Anf I guess this might have a link with my lack of internet connection while tethering.
Did any of you tried the USB or wifi tether? Does it work?
Sent from my A0001 using XDA Free mobile app