Related
After racking my brain for a few days, a couple hours each day, I've fixed my issue with my device being unknown.
Let me start by saying I'm flash happy, and everyone that knows me personally, tells me to just quit jacking with my phone. NOT A CHANCE! I'm on my 3rd Cappy and shouldn't have ever exchange it again. I only had to in the beginning, because I was a newbie and had not know enough, but to get me in trouble.
I presume that this should work on all Windows OS's. I personally am running Vista Enterprise x86.
My symptoms:
Plug in phone to the usb and it there was about a 15% chance off being able to mount to usb, and Windows recognizing as a mass storage device. I tried un-installing drivers and re-installing and it would work some of the time, until the point came when parts of the driver install would fail. Then to the point when it was just completely unrecognizable. I thought I had it fixed because it seemed intermittent. In the middle of flashing to stock, something interrupted communication between the pc and my phone. Restarted the phone and attempted the flash again. Got a little farther and froze again. I had to use another pc that I had never connected my phone to before and I was able to use my jig to trigger download mode, because no buttons combinations would allow it into download mode.
This got me thinking that it was specific to my pc and not my cable or my phone.
My resolution:
I went straight to the registry and went to find. I deleted every entry that came up for "i897" and "i9000" excluding what was listed in the system volume information, as I didn't have permissions to remove any keys. I didn't keep count, but I probably deleted 300-400 registry keys that pointed to my phone. It seems as if with each developers rom that I had flashed, there was an entry for a different device. Don't quote me on that, because it is just my personal consensus. I also un-installed the samsung drivers, the unknown device driver, kies software, and anything associated with samsung. I noticed that next to all of the i9000 instances, the hex key for me started with 1000ee. So I also searched for the first part of that key trying to ensure that all instances of the device. Lastly, I deleted the samsung folder from program files.
I installed the samsung drivers package commonly listed in all of the other threads for x86 operating systems. I plugged in my phone and watched as each and every driver installed successfully. Keep in mind different drivers are installed depending on if you have usb debugging on/off, and the options for if the preferences on you phone are set to media, storage, or kies. I have multiple usb ports, however testing has shown me that, for me and my setup, I can plug into the port that I used when installing the drivers the final time, I am able to connect consistently. Earlier today, I tried to plug into a different usb port and it was an unknown device. I am led to believe, this is because I didn't un-install the unknown device on this particular port.
If you intend to work in the registry, please remember to always back it up first. You can always restore.
Hopefully my findings can help you as they did me. Happy flashing and I would like to thank the community for the dedication to assisting each other and the developers, for making flashing, better than crack cocaine. Flashing rom's doesn't make you twitch near as much as a crackhead.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Has anyone had any luck with this?
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
So I got my Samsung Galaxy Tab (sprint CDMA version) today and when I first plugged it into my computer the drivers installed fine. I was able to mount the sd card and transfer files with ease. I then proceeded to root the device hoping to put a new rom on it, I've got a captivate and am not a rookie at all when it comes to flashing roms via odin, cwm, etc...I first put the device into debugging mode which is where things got weird. As soon as I put the device into debugging mode and plugged it in via usb it immediately became "unrecognizable". I have the correct updated drivers for the device both from the Samsung website and via the Android SDK tools. There should be no reason why this happened. So I then took it out of usb debugging and plugged it back in and bam, again, "USB Device not recognized". I've been installing and uninstalling drivers, the device itself from the device manager, and have been trying other numerous ideas. I've been Googling and searching for hours upon hours at this point and don't know what to do next. Odin does NOT recognize the device when in download mode and the device does charge when connected to the computer. I have tried a different cord with the device and different computers and it's all the same story, works until debugging is enabled then it will no longer work no matter what. I am fairly sure at this point the device itself is malfunctioning or defected but I wanted the opinion of others before sending it back. I am pretty sure have tried everything and am doing everything right. Please help if you can, if not I still appreciate your time! Specs are listed below:
Hardware Version
P100.08
Model Number
SPH-P100
Firmware Version
2.2.1
Kernel Version
2.6.32.9
Ebicoustic said:
As soon as I put the device into debugging mode and plugged it in via usb it immediately became "unrecognizable".
....the device does charge when connected to the computer.
Click to expand...
Click to collapse
1. Just wondering, have you installed Kies before connecting the tab to your PC?
2. The SGT will not charge "normally" with a USB connection. It will trickle charge, which is very slow way of charging, and the device will not indicate that it is charging. Does your device indicate it's charging? (As stated above)
Hit thanks if I deserve it..
FWIW, My SPH-P100 Sprint Galaxy Tab has been an adventure as well. Enough so that I wish I'd known more and held out for a GSM model.
I am not even sure if Kies and/or Odin will in fact work with the Sprint GT. I've had almost no luck with a variety of attempts. Even the widely used ClockWorkMod Recovery does not include the Sprint GT among its list of supported devices. It does include the CDMA Verizon GT - and some folks have posted that they eventually got that to work.
I did get the SuperOneClick to work and setup root privileges on my tab. That part works fine. But so far I've been reluctant to experiment too much with the various tools that "almost appear that they should work" as I have too little experience with this Android tablet environment to feel comfortable that I can recover from the eventual disaster.
Am hopeful that Samsung will in fact follow through on their commitment to provide upgrade of all GTs to Gingerbread 2.3.3. If so that may be enough for my needs. I WOULD like to get the Netflix viewer app working. Is frustrating to already have a Netflix account and not be able to access it via my GT. A guy down the hall can get Netflix on his Droid X - which really bugs me! lol
IMHO, Google/Samsung/Motorola/HTC/etc. have done a horrible job rolling out Android - both on phones and tablets. Netflix really highlighted this when they decided to do device-by-device testing and certification before allowing Android devices access to their movies. Apparently the 'capabilities' inherent to various Android devices varies so much (and not just OS version) makes it difficult to roll out something as simple as Netflix access. It is frustrating. And the only "solution" so far is to wildly 'hack' your device in the hope that you'll shake something loose enough to make it work as you wished it had when you bought it.
Enough whining for now. But it has been a very frustrating and disappointing experience.
I installed Kies AFTER installing drivers and connecting the tablet and it has no effect. I also learned after googling that kies does not support the sprint cdma version though I could be wrong but many people have stated this. And the device does charge and does so very fast actually, 20% to 100% in 4 hours. I don't think it's trickling down as you say because it is very clearly charging at a fast pace. Thanks for the quick response though! And I have also tried superoneclick root and other methods i.e odin but neither can find the device. I know some people have had luck with this sort of thing after upgrading the rom and/or flashing firmware onto the device which I would love to try but unfortunately without windows being able to see the device, none of this is even remotely possible.
I think the reference to slow charging on USB is really refering to using a data USB port on a notebook or desktop computer. This is because the data USB ports are limited in how much current they will pass. My SPH-P100 will in fact charge on a data USB port - but very, very slowly. In fact if the device is ON it may just barely be breaking even.
The USB charger is certainly capable of charging at a very reasonable rate.
I'm still waiting on the 2.3.3 update that Samsung has promised. It only took them 5 months to get the 2.2.1 update out for my Fascinate! So maybe we'll see the 2.3.3 update by Thanksgiving...or Christmas...or...
Hi all,
I have problem with connecting my O2X to laptop.
When I connect phone to laptop phone start to charge, but USB connection is not recognized and no notification on phone (top left corner) is shown.
It was working once, but since then my phone was updated via OTA to V10e and then to V10f yesterday.
My phone is on stock.
I've seen on other forum that people had similar problem but I didn't found any solution.
I've tried different USB cables, different laptop (home and business - on both was working once before), unnistaling drivers and similar.
Please help!!!
Thank You.
I have the same problem and I still don't understand if it is hardware or software related.
In my case the usb sometimes stop working for a certain time, sometime a couple of hour, some time for a full day. After that magically start to work again.
I've tried every in my knowledge but without success.
You are not alone
Air_Mike said:
Hi all,
I have problem with connecting my O2X to laptop.
When I connect phone to laptop phone start to charge, but USB connection is not recognized and no notification on phone (top left corner) is shown.
It was working once, but since then my phone was updated via OTA to V10e and then to V10f yesterday.
My phone is on stock.
I've seen on other forum that people had similar problem but I didn't found any solution.
I've tried different USB cables, different laptop (home and business - on both was working once before), unnistaling drivers and similar.
Please help!!!
Thank You.
Click to expand...
Click to collapse
Using Topogigi 1.6 this exact thing hit me yesterday, I suddenly lost ADB-access (I was programming at the time, and suddenly couldn't upload the app to the phone anymore.) The "bug" top left had vanished, and no toggling of USB-debugging would turn it on again. I tried restoring froyo backups, tried wipe-install, didn't work. What finally solved it was to smartflash back to 10D. Very strange, I cannot find any logical reason for this behaviour, so it can only speculate it must be something illogical, like maybe overheating (wasn't overclocked.)
EDIT: Let me elaborate. When this happened I of course tried another cable, and what was extra weird was that it wouldn't even recognize a USB-connection, but it would charge. Plugging it back in the dock I normally use when programming would show a USB-connection, but no ADB. At first I was worried that perhaps the dock had pushed the pins in the socket too far in for the regular cable to get a connection. After smartflashing back to 10D though, both the dock and cable work as usual. So maybe, just maybe, a hot phone will expand certain areas around the usb-connection points either in the socket or on the motherboard. Again, just speculation. The usb-connection has worked fine since, using any cable.
Happened to me as well. In one day i can't connect my phone to the pc but after two weeks when i connected the o2x to a pc with vista the problem was vanished. I connected to my usual pc and the same it worked. let's hope that i will not have anymore this problem. It is possibility that your phone will revive i one day. good luck.
I think I may have solved this particular mystery, I'm now able to reproduce it at will, and get usb/adb functionality back.
It happens through a combination of ADB crashes/bugs on a computer and a usb-stack crash/error on the phone.
I can reproduce it by plugging in another phone/tablet on the computer (while still having the phone connected), installing/running something from eclipse on the other device, unplug and replug the o2x and then try to run/install something on it via ADB. This invariably leads to the ADB-icon (the status-bar bug-icon) disappearing, *and* it will lead to the phones USB not working on another computer, or even another port on the same computer.
Funny thing is, if I reboot the phone, and plug it back on the same computer, this instantly leads to the same behaviour. USB will only get recognized on the same port it was plugged in the last time, and ADB will still not get activated. Trying to connect to another computer *after* this will not work.
The solution is simply to reboot *both* the phone *and* the computer (or just kill adb I guess) before plugging in anything.
Plugging in the phone while *either* the PC *or* the phone is in this confused state will lead to both devices malfunctioning in the same way as before, which is why you cannot simply connect the phone to another PC. (Although unplugging the phone, rebooting it *before* plugging in to another computer should work.)
Thank You for info.
I just tried it but unfortunately it didn't work for me. I've tried restarting phone couple of times, plugin into different computers but phone still doesn't recognize usb connection (just charging).
I this the problem is in the phone and it maybe due to update to v10e and v10f.
Air_Mike said:
Thank You for info.
I just tried it but unfortunately it didn't work for me. I've tried restarting phone couple of times, plugin into different computers but phone still doesn't recognize usb connection (just charging).
I this the problem is in the phone and it maybe due to update to v10e and v10f.
Click to expand...
Click to collapse
Hm, okay, your problem may be of a different kind. I'm not entirely convinced yet, as you don't mention having rebooted any computer. So just to satisify my curiosity, do exactly these steps in the following order:
1) Unplug the phone from the computer.
2) Power down the computer
3) Power off the phone
4) Turn on your computer
5) Re-install the LG USB drivers
6) Turn on your phone
7) Connect the phone
If this doesn't work then you indeed have a completely different problem, and we're back to speculating.
TrymHansen said:
Using Topogigi 1.6 this exact thing hit me yesterday, I suddenly lost ADB-access (I was programming at the time, and suddenly couldn't upload the app to the phone anymore.) The "bug" top left had vanished, and no toggling of USB-debugging would turn it on again. I tried restoring froyo backups, tried wipe-install, didn't work. What finally solved it was to smartflash back to 10D. Very strange, I cannot find any logical reason for this behaviour, so it can only speculate it must be something illogical, like maybe overheating (wasn't overclocked.)
EDIT: Let me elaborate. When this happened I of course tried another cable, and what was extra weird was that it wouldn't even recognize a USB-connection, but it would charge. Plugging it back in the dock I normally use when programming would show a USB-connection, but no ADB. At first I was worried that perhaps the dock had pushed the pins in the socket too far in for the regular cable to get a connection. After smartflashing back to 10D though, both the dock and cable work as usual. So maybe, just maybe, a hot phone will expand certain areas around the usb-connection points either in the socket or on the motherboard. Again, just speculation. The usb-connection has worked fine since, using any cable.
Click to expand...
Click to collapse
Trym,
Does that mean you were able to smartflash despite having USB connectivity problems? I had these problems with my first O2X and after I flashed MCR I couldn't connect to USB at all. Luckily this was within the exchange period and I was given a replacement handset which hasn't had these issues but then I am still using stock 2.2
I did try all combinations of reboots on the phone and also driver installs etc on the problematic handset but nothing worked then.
mparack said:
Trym,
Does that mean you were able to smartflash despite having USB connectivity problems?
Click to expand...
Click to collapse
That's exactly what it means, yes. It's never been a hardware problem (luckily)
I had these problems with my first O2X and after I flashed MCR I couldn't connect to USB at all. Luckily this was within the exchange period and I was given a replacement handset which hasn't had these issues but then I am still using stock 2.2
I did try all combinations of reboots on the phone and also driver installs etc on the problematic handset but nothing worked then.
Click to expand...
Click to collapse
You may of course have had a genuine hardware fault, after all usb-sockets are among the first things to break on any phone. I thought my phone was a goner as well, until I discovered the things mentioned in my post. It's a really sneaky affair, it would be impossible not to assume the phone is broken the first time you experience it.
EDIT: Removed invalid assumption.
Just to report that I've tried everything, including connecting phone to computer on which my friend runs Nexus S with no problem and then connecting to computer on which my phone was never connected.
Is there easy way to revert to v10d (last version I know my usb connection worked)?
I don't want to experiment too much because this is my business phone.
Maybe I'll just wait for GB and V20e (I hope it will finally be released soon) and hope that this will resolve my problem, but until them I'm missing one of main functionality
What a waist, since I get the phone with all that fuzz about it, is nothing but problem after another: rebooting, battery drain, wifi problem, usb connection... whats next?
Air_Mike said:
Is there easy way to revert to v10d (last version I know my usb connection worked)?
Click to expand...
Click to collapse
Assuming your usb isn't actually broken, yes, it's pretty easy. Download 10D from here: http://forum.xda-developers.com/showthread.php?t=1035041
Instructions here: http://forum.xda-developers.com/showthread.php?t=1008070
NOTE: The instructions are for flashing baseband only. In addition to that, you also need to select the .bin file in "Ap bin"
Thanks, but links are broken.
Air_Mike said:
Thanks, but links are broken.
Click to expand...
Click to collapse
Indeed they are, were copied from another post I made, and XDA had truncated them.
1st one: http://forum.xda-developers.com/showthread.php?t=1035041
2nd one: http://forum.xda-developers.com/showthread.php?t=1008070 (this link is also at the bottom of the first post of the first link.)
Just to report that my USB connection suddenly stared to work again on both of my laptops (home and work).
I didn't do anything after I gave up weeks ago. Before that I've tried everything but with no success.
Air_Mike said:
Just to report that my USB connection suddenly stared to work again on both of my laptops (home and work).
I didn't do anything after I gave up weeks ago. Before that I've tried everything but with no success.
Click to expand...
Click to collapse
Weird. Glad you got it working.
Looking around on different LG Forums, as useless as they are, the support-people always gives the advice that you should take out the battery, and leave it out for five minues to "clear residual memory." (This, apparently, is the solution for any kind of problem with the phone ;-)) That's always sounded completely nuts to me, but that's the advice I'm going to give the next guy with usb problems ;-)
And another one bytes the dust.
That's ultra weird. one minute everything is just fine and on the other, USB is dead.
So, apart from the procedure TrymHansen gave us a few post back, there is no known solution/diagnose/whatever for this problem, right?
SmartFlash will not detect phone...
My post from other thread which was closed:
My optimus 2x is not detected when I plug it to my laptop via USB.
Turn on mass storage" in the phone does not appear, it's like I'm just plugging in into a wall charger.
It could connect just a few days before, same laptop, same drivers (LG mobile united drivers)
Have tried it with 3 different laptops, still can't connect (drivers are installed)
A google search reveals other people having the problem as well and unable to solve it.
Can't return it yet for warranty because superuser app is still there.
Originally, I rooted it using superoneclick. Can't unroot it in superoneclick since not detected in USB.
So i unrooted it using z4root (without a pc). It's now unrooted, however superuser app is still in the app drawer.
i believe mine can be detected from smartflash so maybe i can flash stock rom. will doing this remove superuser.apk?
fmartinezjr said:
i believe mine can be detected from smartflash so maybe i can flash stock rom. will doing this remove superuser.apk?
Click to expand...
Click to collapse
Yes it will.
So did you try to flash a stock rom and did solved your usb problem ?
I will try with a modaco rom next we.
lol, is this fixed or not?
ive had the same problem.. when my rom is totally chrashed, and usb is like stuck?
strange is, all the other usb devices (wifi dongle, not keybord mouse) stops working when i plug in my phone? also the phone does not see that there is an data cable in him so i cant mount my storage?
is this an warranty issue?
I don't believe there was a thread covering this exact issue, if there is I sincerely apologize. AT&T Samsung Galaxy S III Mini SM-G730A
My problem is that my phone will not connect to any computer via USB mass storage, the battery will begin to charge but that is all. I have searched the internet for possible reasons/solutions and I have also contacted Samsung customer service which only lead to the discovery of completely different issue. Of course upon this discovery as coincidence would have it the call with customer service was disconnected. The lady had told me to boot the phone, take the battery out, and boot into recovery mode. Once there she instructed that I choose the option to wipe the cache partition, when I selected this option it said it was clearing the partition then gave me an "ERROR" message, shut down, and rebooted the phone. Basically, to get to the point, I wanted to root the phone and this problem is somewhat a hindrance. Any help or suggestions would be greatly appreciated. Thanks in advance
Also I don't know if this needed or would help but I have tried connecting it to computers running Win XP Home Service Pack 2, Win Vista, Win 7 Home Edition, and on my laptop which is the one I would be using if fixed it's running Ubuntu Saucy 13.10. I also used the original cable that came with the phone I bought it brand new. Thanks again.
Possible reason of your problem
pwnerize_me_cap'n said:
I don't believe there was a thread covering this exact issue, if there is I sincerely apologize. AT&T Samsung Galaxy S III Mini SM-G730A
My problem is that my phone will not connect to any computer via USB mass storage, the battery will begin to charge but that is all. I have searched the internet for possible reasons/solutions and I have also contacted Samsung customer service which only lead to the discovery of completely different issue. Of course upon this discovery as coincidence would have it the call with customer service was disconnected. The lady had told me to boot the phone, take the battery out, and boot into recovery mode. Once there she instructed that I choose the option to wipe the cache partition, when I selected this option it said it was clearing the partition then gave me an "ERROR" message, shut down, and rebooted the phone. Basically, to get to the point, I wanted to root the phone and this problem is somewhat a hindrance. Any help or suggestions would be greatly appreciated. Thanks in advance
Also I don't know if this needed or would help but I have tried connecting it to computers running Win XP Home Service Pack 2, Win Vista, Win 7 Home Edition, and on my laptop which is the one I would be using if fixed it's running Ubuntu Saucy 13.10. I also used the original cable that came with the phone I bought it brand new. Thanks again.
Click to expand...
Click to collapse
Your problem if you still hve it is that the usb port is damaged, normally when they get damaged they can still charge the phone but will not be recogniced by the pc, so you would not be able to rooted, or transfer any file to it, .
Solution is to change the usb port. Hopefully you can fix your issue, Greetings.
Try enabling / disabling usb debugging, maybe that will help. You'll need to go to 'about phone' in settings then tap on the version number 10 times to enable developer options, then you can enable usb debugging.
Around February, my phone was working fine and connecting to my PC and being recognised (in both the phone AND PC/Device Manager). Because I was rooted, I used Wug's toolkit to flash the latest factory image at the time (which included the February security update) and kept data as I've done in the past. It was fine for ~2 weeks after that factory image flash and then my phone just stopped recognising the PC, and my PC stopped recognising the phone as a device. It was completely out of the blue, and seems unfixable.
When I plug my phone into my Desktop - it just charges. It doesn't appear in the device manager at all (image below - Device manager WITH phone plugged in and not appearing):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've had to do the old 'update drivers' thing in the past with other phones, but they would normally appear under "Phone" or "Other devices" - but both are missing from the list ("Show hidden devices" used in that image). There's also no yellow triangle to say an unknown device has been connected. It just flat out doesn't know it's there. I've also updated/re-downloaded the SDK (and Google drivers) but the phone still isn't recognised.
It got so bad, I had to use USBDeview to uninstall the drivers in the first place because they never appeared. It still didn't help.
On the phone side of things - I'm not given an option to mount the phone as any form of storage. It just behaves like I've plugged it into a charger.
In the USB and Storage settings (image below) - I'm not given an option for ANY form of USB connection.
And in the notification shade (again, while plugged into my PC) no option is given. It just charges:
I've also tried factory resetting the phone, since it charges fine so I don't think it's the charging port but now I've lost root AND the problem is still there. I still can't install OTA updates because in order to get Root, I had to use a kernel which disabled those "this device has been modified" alerts when you boot it, which means the OTA just fails (Error 7 (or 6) - and something about recovery).
In Fastboot, it just says it's 'charging' and makes no attempt to connect via USB. Recovery is the same so it doesn't sound like an Android problem per-se since it affects Fastboot but hardware wise - would could it be?
As a last resort, I've also tried multiple cables (working one for the Nexus 7, DS4 one and a Motorola one) and none of them seem to have helped.
I've also tried different USB ports and on different machines - both running windows 10 and both with the drivers installed but still no luck.
Any help would be greatly appreciated because I'm just sick of this problem at this point.
Zenamez said:
I'm just sick of this problem at this point.
Click to expand...
Click to collapse
You've tried a lot.
My idea is to try to connect to another PC, when possible not Windows 10.
This to check that the problem isn't caused by the phone.
NLBeev said:
You've tried a lot.
My idea is to try to connect to another PC, when possible not Windows 10.
This to check that the problem isn't caused by the phone.
Click to expand...
Click to collapse
That's a very good point. Pretty glad one of my PCs didn't like the 10 upgrade and is still on 7.
I'll try it when I get home. Thanks for the reply!
Zenamez said:
That's a very good point. Pretty glad one of my PCs didn't like the 10 upgrade and is still on 7.
I'll try it when I get home. Thanks for the reply!
Click to expand...
Click to collapse
Wish you luck.
W10-updates are causing issues on my PC
If changing PCs doesn't help, try a different cable. If that still doesn't work, you likely have a problem with the micro USB port.
Strephon Alkhalikoi said:
If changing PCs doesn't help, try a different cable. If that still doesn't work, you likely have a problem with the micro USB port.
Click to expand...
Click to collapse
Tried 3 different USB cables and no luck.
I've got a spare microUSB I bought from eBay which I'll need to solder but the only thing I could find on faulty ports were that it doesn't charge right but mine does.
Going to try connecting it to a windows 7 laptop and see where that goes. If it still doesn't work - the only thing left would be the port itself which will be a pain to replace (and still doesn't guarantee it'll be fixed).
Honestly it sounds like a hardware issue with the MicroUSB port. I can confirm it works fine under my Windows 10 PC at home, both normal access for files and I've also had no issues with using fastboot or ADB. If it's under warranty try to RMA it. If it's out of warranty see how much it would cost to change the MicroUSB port from a local shop or try it yourself
I've had the same thing happen to me twice. I think that some times Windows updates and kills the drivers. Whenever it's happened to me I've installed a universal adb driver that's floating around XDA. Once that alone fixed the issue. Once it didn't. The time it didn't I had to open every device heading in the device manager until I found one that had Google hidden inside it. I uninstalled the Google driver from there in the device manager and then plugged my phone in. Windows did the normal device install from the phone and all was fixed. Hope that helps. Good luck. Windows 10 truly sucks.
Maybe to rule out pc, find a buddy with android phone and see whether you can detect it with adb or fastboot on your pc. I think those drivers are supposed to be universal (all phones)....aren't they?
electricpete1 said:
Maybe to rule out pc, find a buddy with android phone and see whether you can detect it with adb or fastboot on your pc. I think those drivers are supposed to be universal (all phones)....aren't they?
Click to expand...
Click to collapse
Tried it on my Windows 10 laptop as well and it's the same problem. Just tried it on my older Windows 7 laptop as well, and same story.
My older Nexus 7 2012 connects fine to all 3 so I don't think it's the drivers.
Dvoraak said:
I've had the same thing happen to me twice. I think that some times Windows updates and kills the drivers. Whenever it's happened to me I've installed a universal adb driver that's floating around XDA. Once that alone fixed the issue. Once it didn't. The time it didn't I had to open every device heading in the device manager until I found one that had Google hidden inside it. I uninstalled the Google driver from there in the device manager and then plugged my phone in. Windows did the normal device install from the phone and all was fixed. Hope that helps. Good luck. Windows 10 truly sucks.
Click to expand...
Click to collapse
Sadly already tried this but what's worse is - I've looked through all the possible 'dropdown' options and the drivers/device doesn't appear but it appears in USB Deview (where I uninstalled them).
Tried both the universal ADB driver and Google's own one from the SDK - sadly didn't work in the end.
Dopamin3 said:
Honestly it sounds like a hardware issue with the MicroUSB port. I can confirm it works fine under my Windows 10 PC at home, both normal access for files and I've also had no issues with using fastboot or ADB. If it's under warranty try to RMA it. If it's out of warranty see how much it would cost to change the MicroUSB port from a local shop or try it yourself
Click to expand...
Click to collapse
I'm beginning to think the same to be honest. It doesn't connect in Fastboot, which leads me to believe it's more hardware than software because if it were Android itself screwing up - it would at least work in Fastboot as that doesn't touch Android.
It doesn't mount as anything, so I can't access my files on any of the systems I've tried. I've even tried my younger brother's laptop and it doesn't 'see' it (but his Nexus 4 connects and works just fine).
I bought my Nexus 6 ~6 months after release so it's out of warranty (what a time for it to run out of warranty). I bought a new USB port from eBay ages back so I might have to fit it myself since all the repair shops I've contacted would take ~3 days to do it and I need to have a phone.
I really hope replacing the port will fix it. It charges fine, which makes me slightly worried it won't work (as it's not an obvious port issue) but I can't think of anything else which could be the problem.
Thanks to everyone who's replied though! I'll see how the USB replacement works out.
Hello all, long time lurker 1st time poster....
I've never really felt the need to post because i normally just do a search and work things out for myself, but i'm now having the same problem and noticed this around 2-3 weeks ago after trying to copy some pictures i'd taken onto my Laptop from my Nexus 6 and it not being recognised, only charging.
I've tried EVERYTHING (apart from reverting back to Windows 7) mentioned in this thread and in a couple of the other threads i've found where a few Nexus 6 users have had the same problem. I'm now stumped for ideas.
My Nexus 6 runs as flawlessly as usual, no battery drainage, stutters etc.
I'm currently running Temasek's 18.2 (5.1.1) rom, and have been using it now for a long time (probably for 8 months or so with absolutely no problems whatsoever). I've updated to MM a few times and tried a few different Roms, but to be honest i just found that LP worked better for me so have always just reverted back to the last official LP 5.1.1 LVY48I Rom using Wugfresh's Tool Kit (i know i know , but having rooted/played about with other Samsung/HTC Phones in the past, i just preferred to use it) and then restoring my backed up reliable Temasek's 18.2 Rom.
So, what else can i say....well, i called Motorola around a week ago for some advice, just incase there is a potential warranty claim (because my Nexus 6 is only around 9 months old), but as i have a Custom Rom on it, they said that there is nothing that they can do.
I do have an official clean 5.1.1 Rom LMY48M that i fortunately backed up to my TWRP Folder on my laptop just after installing TWRP+rooting. I did 1st of all also try connecting my Sandisk Ultra Dual USB DRIVE 3.0 to my Nexus with the Rom on there, but the Nexus just doesn't even know that the USB Drive is connected, so I have had to send it via bluetooth to my Nexus from my laptop, as that was the only way to get it on there. I found that Zipping the file 1st, sending it to my Nexus via Bluetooth and then extracting it once i'd received it saved hours in time because the file was too large in its original form (something like 4+gb down to 1.9gb). I've also tried a few other LP Rom's in the last couple of weeks, hoping that maybe i'd accidentally switched a setting off or something and that the phone would correct itself and my connection problem would correct itself but i've had no joy.
NOW...........................probably a silly question but it's the only other way i can think of returning to Stock for a potential warranty claim. I know that i can install the official 5.1.1 Rom i backed up via TWRP because i've tried, but is there a way to remove Root+TWRP and return to Stock Recovery+remove root without using a PC ? I'm pretty sure that there isn't but feel the time is right for me to ask the Question as i'm really not 100% sure.
Many Thanks in advance for helpful advice given, like i've said at the start of this post, i've held off asking Questions before because i had no real need and just searched :angel: , but this has really stumped me .
CHEERS
Some quick thoughts.
1. The Motorola rep you spoke to I think read from a script and didn't realize you were talking about the Nexus 6. As this is a developer device, having custom software on it should make no difference for warranty purposes. If I am mistaken however, read on.
2. If you're going to install a stock ROM on the Nexus 6, a PC will be required, especially if needing to replace TWRP with the stock recovery. So why not download the latest Android 6.0.1 image from Google's Nexus firmware page and flash that? There's no point in reverting to an Android 5.x image simply for a warranty claim.
Many thanks Strephon Alkhalikoi for your quick reply and sorry for my slow 1 (work was getting in the way....)
1 - at some point today, i hope to chase my potential problem up with Motorola or possibly Expansys because i purchased the Nexus 6 from them via Play.com/Rakuten.co.uk
2 - The 5.1.1 Stock image that was going to be put on the Nexus was only a normal TWRP back up i'd saved by chance straight after flashing+rooting that i had saved to my Laptop. There is no way for me to flash any new Stock software because my Nexus is just not recognised by my Laptop. I've tried installing+uninstalling drivers/Minimal ADB Fastboot file/Wugfresh's Toolkit, plus Developer options usb debugging on/off etc and Settings/Storage/USB Connection (3 little dots top right) which gives me 2 options Media Device (MTP) + Camera (PTP) but after changing either, still no sign of connection, just charging.
As it stands it works fine on 5.1.1, but with me not being able to Flash any Stock Roms because of my Laptop connection issue, it will be forever more on LP. I could put up with that but obviously i need to try and sort this out also because i can't transfer normally any media files backwards/forwards (only via the much slower Bluetooth) and it will affect any future sell on value when it's time to move on.
Many Thanks once again
**Latest Update** for those not asleep yet....
i spent nearly 20 minutes on the phone around an hour or so ago explaining my problem to Motorola. It's not something they've heard of before so couldn't really help and that by being Rooted, their repair center will not touch it. I can only think that if i'd purchased the Nexus 6 straight from Google, it would not have been such a problem to handle a Rooted device so it would have been taken in for repair i'm guessing.
It was explained to me that i would be contacted via email once a technician had been consulted and here is the reply i received a little while ago.
"Thank you for contacting Motorola.
As promised, I have spoken to a technician who has a couple of suggestions.
A. As we discussed, he also suggested connecting your phone to another computer.
B. Be sure that you have Windows Media Player and the PS Drivers installed on your laptop.
[link removed due to my lack of XDA posts]
C.
At this point, I would like to suggest that you restart your phone on Safe Mode.
Safe Mode puts a phone in a diagnostic state and it can help us determine if a third-party app is causing the device to malfunction (freeze/reboot/run slow/error message). Safe Mode temporarily disables all applications that have been installed via the Google Play store. Performing this troubleshooting step is necessary to determine whether a third-party app is the cause of the issue you are experiencing.
Please long press the power button > long tap on power off > reboot to safe mode >ok.
If you find that the issue is resolved in Safe Mode, please delete all apps from the phone, and gradually add them back one or two at a time, until you are able to identify which is causing the sound issue.
To move phone from Safe Mode back to normal mode, you can simply restart it.
D.
To be sure if the problem is software or the port itself:
1. Reboot phone in Fastboot Mode
2. Plus phone into computer
3. If phone is recognised as 'Fastboot Shamu NS,' the issue is software, rather than a physical issue.
In this case, you would need to reset the phone, which I know you are hesitant to do, but you should then be able to reflash the factory images, available on the Google website.
Unfortunately, there little else that we are able to do to help you since, as discussed over the phone, SBE UK, our repair, centre will not accept a rooted device.
For any further assistance or information please do not hesitate to contact us, quoting your Customer Reference number. We are reachable on 03339 997 550 to discuss the matter further with one of our experienced customer service agents. Please contact us any time between the hours of 8am and 8pm from Monday to Friday.
Kind regards,
Anna
Motorola Mobility UK Ltd.
[another link removed] "
I've tried all of the above (apart from connecting to another PC) and still no joy so it looks like i'm stuck on LP. Like i've said before, it still works as normal so no real hardship apart from the lack of Software updates and the normal easier transferring of media files. I'll keep an eye out on this and the other threads to see if a solution becomes available.
*I've posted the above it as it might help someone else out in the future*
qprjim said:
**Latest Update** for those not asleep yet....
i spent nearly 20 minutes on the phone around an hour or so ago explaining my problem to Motorola. It's not something they've heard of before so couldn't really help and that by being Rooted, their repair center will not touch it. I can only think that if i'd purchased the Nexus 6 straight from Google, it would not have been such a problem to handle a Rooted device so it would have been taken in for repair i'm guessing.
It was explained to me that i would be contacted via email once a technician had been consulted and here is the reply i received a little while ago.
"Thank you for contacting Motorola.
As promised, I have spoken to a technician who has a couple of suggestions.
A. As we discussed, he also suggested connecting your phone to another computer.
B. Be sure that you have Windows Media Player and the PS Drivers installed on your laptop.
[link removed due to my lack of XDA posts]
C.
At this point, I would like to suggest that you restart your phone on Safe Mode.
Safe Mode puts a phone in a diagnostic state and it can help us determine if a third-party app is causing the device to malfunction (freeze/reboot/run slow/error message). Safe Mode temporarily disables all applications that have been installed via the Google Play store. Performing this troubleshooting step is necessary to determine whether a third-party app is the cause of the issue you are experiencing.
Please long press the power button > long tap on power off > reboot to safe mode >ok.
If you find that the issue is resolved in Safe Mode, please delete all apps from the phone, and gradually add them back one or two at a time, until you are able to identify which is causing the sound issue.
To move phone from Safe Mode back to normal mode, you can simply restart it.
D.
To be sure if the problem is software or the port itself:
1. Reboot phone in Fastboot Mode
2. Plus phone into computer
3. If phone is recognised as 'Fastboot Shamu NS,' the issue is software, rather than a physical issue.
In this case, you would need to reset the phone, which I know you are hesitant to do, but you should then be able to reflash the factory images, available on the Google website.
Unfortunately, there little else that we are able to do to help you since, as discussed over the phone, SBE UK, our repair, centre will not accept a rooted device.
For any further assistance or information please do not hesitate to contact us, quoting your Customer Reference number. We are reachable on 03339 997 550 to discuss the matter further with one of our experienced customer service agents. Please contact us any time between the hours of 8am and 8pm from Monday to Friday.
Kind regards,
Anna
Motorola Mobility UK Ltd.
[another link removed] "
I've tried all of the above (apart from connecting to another PC) and still no joy so it looks like i'm stuck on LP. Like i've said before, it still works as normal so no real hardship apart from the lack of Software updates and the normal easier transferring of media files. I'll keep an eye out on this and the other threads to see if a solution becomes available.
*I've posted the above it as it might help someone else out in the future*
Click to expand...
Click to collapse
SBE repaired my nexus 5, when it was rooted/unlocked.
Is there any damage to the usb port? Never tell the customer service rep that your device.
Cheers for the reply JonesL
As far as I'm aware, there isn't any damage to the USB Port. I did say I thought that that might be the problem but she said if it was the reason, then the phone wouldn't charge at all.
I could still send it in and hope that on the off chance they don't check for Root, but i will be liable for the postal returns plus the hassle of being without a mobile whilst it is away. Also, I've now given my IMEI number and a couple of other details so I'm sure I'll now flag up on their system when its checked.
Oh well....