I have 2 Galaxy Nexus phones. One is rooted and recognized by my W7 64bit PC. The other one I got today and it's brand new, locked bootloader and I can't get the computer to recognize it. I tried installing Samsung USB drivers, PDANet for Android, Universal Naked Driver and whatnot but they don't seem to install correctly. I read somewhere that old HTC drivers might stand on the way of the Samsung drivers but I don't seem to find any installed. Also why is a rooted device recognized and not rooted isn't?
I'm running 4.0.4 build IMM76K.I9250XWLD2
Any info or suggestions would be appreciated.
Thanks,
Dex
Hey guys!
I am wondering, can I somehow root my phone over Samsung Kies?
Or if not, can you help me to resolve this problem: When I connect my note 2 via USB on my laptop (running win 8) it doesn't recognise my note 2. I have all drivers installed, but my phone is only on charging mode.
tnx
First i had a problem Getting HTC Drivers for my DInk phone to be detected in windows and via HTC sync while it was On in Normal Operation.. luckily i found some HTC Drivers for W7 64bit and just manually installed them and it worked so that issue was FIXED!!!!!
BUUUUUT now it looks like i have a problem Only when the Phone goes into Bootloader, Hboot and Fastboot...
It looks like a windows 8.1 issue.......
ive been trying to fix my damn Droid Incredible for at least 1 year now, i finally have it half way figured out. I got to the part where i am trying to push a cwm recovery to my phone via miniadb (which requests that i restart the DInc into Bootloader mode . and blammmm as soon as my phone goes into Hboot a balloon pop up in Windows 8.1 Pro X64 says the device malfunctioned and the link between my phone and my computer is gone renedring the push completely stopped
.... This guy on Windows Eight forums is having the same problem:
http://www.eightforums.com/drivers-...n-8-1-doesn-t-allow-adb-fastboot-drivers.html
Is there a way to get a work around for this??? Im sure The Droid Incredible is not the only one having the problem....
Hi everyone,
I am trying to update my (unrooted and unlocked) Nexus 7 2013 wi-fi to Marshmallow via OTA. I have installed adb on my system and download the update package file.
When I connect my Nexus to Windows 10, the system recognizes the device as Android ADB Composite and everything seems to be working as it should. I open a command prompt and type:
Code:
adb devices
and the device along with its id is correctly shown. At this point I reboot to bootloader, so I type
Code:
adb reboot bootloader
the Nexus reboots, enters in the bootloader and the following happens:
adb can't find the device anymore
the device manager puts the Nexus among the Other devices and so it appears no driver has been installed for it.
As suggested on numerous tutorials, I right-click on the device and choose to manually install an appropriate driver. And I expect to find Android ADB Composite in the list and instead the only possible choice is Samsung Android ADB Interface — which does not work, because, naturally, Nexus 7 is not a Samsung device.
I have tried to solve this issue by installing the google usb drivers using the 15 seconds install and it didn't help at all.
What can I do to overcome this issue?
Once you're in the bootloader, adb will no longer be able to see the device. You need to use fastboot to carry out any commands while in the bootloader.
Sent from my Moto X using Tapatalk
UncleMike said:
Once you're in the bootloader, adb will no longer be able to see the device. You need to use fastboot to carry out any commands while in the bootloader.
Sent from my Moto X using Tapatalk
Click to expand...
Click to collapse
Hi UncleMike,
thank you for your reply. I am a bit confused: (once the Nexus is in recovery mode) how do I initiate sideloading if adb can't find the device?
haunted85 said:
Hi UncleMike,
thank you for your reply. I am a bit confused: (once the Nexus is in recovery mode) how do I initiate sideloading if adb can't find the device?
Click to expand...
Click to collapse
I'm only familiar with flashing images while at the bootloader. I've never had to side load anything, so I don't really have an answer for you.
Sent from my Moto X using Tapatalk
I had a similar issue myself when I started using ADB.
What I found happened, is that once you send the tablet into bootloader, you have to go into Device Manager on your windows machine and tell your computer to install the driver for your Nexus. Why it does this, I don't know. I had to do it yet again once I moved the Nexus into recovery mode to flash the OTA update as well. Good luck. Let me know if you need help with what I (poorly) tried to explain above!
Sent from my Nexus 7 using XDA Free mobile app
haunted85 said:
What can I do to overcome this issue?
Click to expand...
Click to collapse
Adb only works when in recovery or Android. Fastboot only works when in bootloader.
jslanger said:
I had a similar issue myself when I started using ADB.
What I found happened, is that once you send the tablet into bootloader, you have to go into Device Manager on your windows machine and tell your computer to install the driver for your Nexus. Why it does this, I don't know. I had to do it yet again once I moved the Nexus into recovery mode to flash the OTA update as well. Good luck. Let me know if you need help with what I (poorly) tried to explain above!
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
If you have to go through all that, something is broken with the Android driver setup on your computer. I plug any of my Android devices (N6, N7, Moto X, LG G3, Xperia Z3v, or Moto Xoom) into my laptop and they're automatically recognized.
nhizzat said:
Adb only works when in recovery or Android. Fastboot only works when in bootloader.
If you have to go through all that, something is broken with the Android driver setup on your computer. I plug any of my Android devices (N6, N7, Moto X, LG G3, Xperia Z3v, or Moto Xoom) into my laptop and they're automatically recognized.
Click to expand...
Click to collapse
If I am just accessing my Nexus 7 in Windows, yes, the tablet is normally recognized. However, once you send it into bootloader and recovery, the computer recognizes the tablet, but it knows it is not in its normal setup...I guess. It just needs some prodding to install the driver at each stage. The only reason I knew how to do this is because I followed directions on this online somewhere.
Hey guys I suggest using this tool called universal adb driver it will install all the drivers for the n7, I had problems sideloading marshmallow because of the recovery mode not being recognized by windows however this tool fixed it right up. It installs drivers for I believe the Galaxy nexus? But they work perfectly fine for the n7.
TL;DR: drivers fail in recovery mode this fixes it.
Here is the link: https://plus.google.com/103583939320326217147/posts/BQ5iYJEaaEH
Sent from my Nexus 7 2013 using Tapatalk
I recently updated my rom to cyanogenmod and suddenly my PC (windows 10, 64bit) couldn't find my phone. It worked with stock and it IS working if I put it to recovery mode, just not when I'm booted up with cyanogen, any thoughts?
I had this problem too and i installed a apk from xda if i rember right it was called mtp enabeler for cm13
Sent from my ASUS_Z00AD using Tapatalk
anjoliwanag said:
I recently updated my rom to cyanogenmod and suddenly my PC (windows 10, 64bit) couldn't find my phone. It worked with stock and it IS working if I put it to recovery mode, just not when I'm booted up with cyanogen, any thoughts?
Click to expand...
Click to collapse
by default when you connect usb cable - android sets connection to "Charging only", you can change it on notification area.