Hi everyone. I've tried searching everywhere, but I can't find anyone with this same particular issue. I recorded what's going on so you can better understand what I'm trying to explain. youtube(dot)com/v/0Rp9XWEfVwE (sorry, I don't have the required number of posts for a link)
My Nexus 5 connects to then immediately disconnects. This happens with any computer I try it with. It will then not recognize or be recognized by any other computer, or charger until you restart the phone.
I can't connect the phone to the computer to unroot it for me to apply the OTA update.
My laptop is able to recognize my Nexus 7. It is also still able to recognizes as a Nexus 5 for the second that it connects.
Any ideas as to what's going on, and how I can solve this? I have no idea where else to pose the question.
I've done several factory resets, both in the menu and in fastboot. I've also erased the cache from fastboot.
I was able to connect to any computer just fine before I updated to 5.0. That's when this issue started.
I've tried several different computers and OS's, they all have the same result. It's not the drivers. Regardless of if there are any drivers on the PC, it will still show up for a second, then immediately disconnect and the phone doesn't respond to any further connections/charging until restart.
Related
I tried looking around all over for a solution. Initially, I updated webOS to the latest version, and installed Android CM7 3.5 to check it out, and everything worked out fine. Installed the .zip to get the Marketplace fix, and next reboot I noticed when plugged in the Touchpad wasn't recognized that it is connected to my computer. Couldn't get the USB connection on in notification tray, unless there's something else I have to do to bring it back.
I went back into webOS, same thing. Rebooted many times, power on + volume button, big USB logo, nothing happening. I may of made a bad mistake here, I performed a full reset in webOS but Android still works fine and asks me what system I want to boot into when I turn on the device.
Anyone have any ideas what I can do to fully restore my device? I am kind of lost because all the solutions I've seen on the web involve the touchpad being connected to the PC and transferring things to it. When I hold the power button and volume up and get the big USB icon, Windows says the device can not be recognized, one of the usb devices has malfunctioned.
Thanks so much in advance.
Got a similar problem. Windows shows me the Device as removable storage, but when I click on it it says "please insert a disk"... Same in webOS and Android.
Edit: Nevermind, the good old "have you tried turning it on and off again" worked. (Desktop).
Check your pc and ensure you have the novacom drivers installed. Novacom is used to access the touchpad when connecting to the pc. Without it, the pc cannot see the touchpad.
Sent from my Touchpad using Tapatalk
Novacom drivers are definitely installed, I used them to install CM7.
So the ota screwed up my phone. I was able to connect and intstall the stock eoh3 for xda the phone now starts up but I am unable to connect USB to root or flash any new rooms with Odin I can only connect Odin if the phone is booted up and debug and mock locations are on. If I pull the battery and put it in download mode it will not connect to the pc it just shows as an unknown device. I have reloaded drivers ect but not getting anywhere. Any ideas?
Try another cable if you have one, and try putting the drivers on another PC. For reasons I still haven't figured out, my home desktop PC quit connecting a couple of ROM's ago, and it won't even let me reinstall the drivers. I have a laptop that works fine (so I haven't gone into major troubleshooting) and my work PC also connects fine.
If the same issue repeats on other PC's and cables, there may be something wrong with your mini USB port. I had to have mine replaced a few months back.
I thought I would share this. I am kind of answering my own question but I am not really sure how I got into the state that I did.
Today I realized that I could no longer connect via USB to my PC. My phone has DietICS ROM. I tried the following:
New Cable
New USB port
Cache wipe
Dalvik wipe
Factory Reset
Rolling back to a previous nandroid that I knew worked
Reinstalling USB drivers
I still couldn't connect the phone as a media device and nothing was reported in Device Manager.
I ended up trying to put the phone in download mode and firing up Odin (to see if it would show as connected) and whalla. It saw the phone. I shut the phone down and rebooted it again and everything was working as it should.
If anyone has any insight on this, it would be appreciated. I am still not sure if it was the PC or the phone that had the hiccup.
Did you try rebooting the PC? I don't see that on your list.
Occasionally I have issues with Windows 7 (and 8) where it doesn't see that a USB device was unplugged, and if I try to use that same USB port for something else it just never detects anything.
It's rare in my case, but maybe something similar happened on your end and just having a different device ID show up (download mode shows up as a different device) kicked Windows in the pants and got your USB drivers working properly again?
dstruct2k said:
Did you try rebooting the PC? I don't see that on your list.
Occasionally I have issues with Windows 7 (and 8) where it doesn't see that a USB device was unplugged, and if I try to use that same USB port for something else it just never detects anything.
It's rare in my case, but maybe something similar happened on your end and just having a different device ID show up (download mode shows up as a different device) kicked Windows in the pants and got your USB drivers working properly again?
Click to expand...
Click to collapse
bah, yes. Rebooting the PC was one of the first things. I missed that on my list.
Weird... happened again.
1.) connected device to USB. Got the double beep and charging but no "MTP" connection message on phone and nothing detected in windows.
2.) Booted phone into download mode. Connected phone and windows saw it.
3.) Rebooted phone again and everything works fine
Happened again (updating this thread for no apparent reason).
Fully powering down the phone and then booting it back up (cold boot) seems to be fixing it.
camoto said:
Happened again (updating this thread for no apparent reason).
Fully powering down the phone and then booting it back up (cold boot) seems to be fixing it.
Click to expand...
Click to collapse
I have the gnex and although different phone i just have plain out usb issues. Does your phone and/or battery have nfc chip?
*Android is upgrading...*
JediNinjafication said:
I have the gnex and although different phone i just have plain out usb issues. Does your phone and/or battery have nfc chip?
*Android is upgrading...*
Click to expand...
Click to collapse
Yes it does
camoto said:
Yes it does
Click to expand...
Click to collapse
Ok, I download all roms and mods directly from phone browser so don't usually have it plugged into computer but have been having issue when trying to charge it with the factory plug. If phone is hot i have to reboot or it says "not charging" in stats. Might not even be related but i found out the battery also has an nfc inside it. Maybe it's something in the connection or the chip in battery between the port and battery..? Because when hooked to computer it also tries to charge right?
*Android is upgrading...*
I've searched around a few threads but not having much luck on this. I've started on a different computer totally from scratch several times and it just doesn't recognise that the phone has been plugged in. It's really quite irritating as the ODIN CF root method is literally 5 clicks and should take about 10 seconds to do.
I plug the phone into my PC while it's on and it detects it as the USB device and I can go into the folders and copy music on etc etc.
I switch it to download mode, plug it in and it does sod all. No windows beep to say it's plugged in a USB device. If I open ODIN then plug it in it's not doing the COM added.
I've tried installing then uninstalling kies then rebooting, installing just the USB driver, uninstalling, rebooting, reinstalling, rebooting. Just NOTHING seems to make my PCs detect that I've plugged the damn phone in when it's in download mode. It should be such an easy process but I'm left banging my head against the wall mid way through because it just refuses to acknowledge the device. I unplug, switch it on, plug back in and there it is, device connected. I've tried different computers, different USB ports. It doesn't show up in device manager even.
So my question: any idea as to why it will detect when the phone is on normally, but will not even think it's plugged in when switch on in download mode? And of course, how to fix it would be useful!
OK I fixed it.
I uninstalled the USB driver and restarted.
Downloaded/installed a new USB driver (specifically SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.23.0-retail).
Went to download mode and it picked it up straight away! ODIN worked in 10s as expected.
Found the instructions here, for reference. http://www.modaco.com/topic/361286-...-phones-15230-for-win-87vistaxp-adb-fastboot/
A while back I tried flashing a rom using TWRP and after it restarted it had a bootloop. I have tried everything I can think of to get this back into recovery mode to flash a good rom. I have tried two computers, both running Windows 10 x64, and neither recognize the Kindle. When I do either an adb or fastboot command it just says "waiting for device". The kindle does not even show up under 'device manager'. It hasn't been recognized for a long time even before I screwed up the Kindle. I have tried several utilities, but none will work due to my device not being recognized. Any help to get this thing back online would be greatly appreciated!!
EDIT: Also, I am able to get into fastboot mode with a fastboot cable I just received in the mail. Doesn't help the pc recognize it thought.
Anyone?
Bump
Connect your kindle to the pc, and let it start bootlooping.
Then, hold the power button for at least 40 seconds. the kindle will turn off early on; disregard this.
now, leaving it attached to PC, turn on the kindle again.
It should now be recognised by PC
After this you can use normal methods to restore it back such as SRT
Sorry for replying 5 years too late, but better later than never I guess :/