Brand new nexus 6, build #LMY47E, running Android 5.1
OS Windows 7 Home Premium 64-bit SP1
My issue is when I plug the device into the computer, regardless of USB port, using the brand new cable provided by Motorola. If I leave USB Debugging off, the phone gets recognized and it says it is working properly. As soon as I turn on USB debugging, the computer attempts to download the drivers, but it always fails on adb interface. MTP gets installed, and Nexus 6 gets installed, but never adb.
What do I do?
a.demarco said:
Brand new nexus 6, build #LMY47E
OS Windows 7 Home Premium 64-bit SP1
My issue is when I plug the device into the computer, regardless of USB port, using the brand new cable provided by Motorola. If I leave USB Debugging off, the phone gets recognized and it says it is working properly. As soon as I turn on USB debugging, the computer attempts to download the drivers, but it always fails on adb interface. MTP gets installed, and Nexus 6 gets installed, but never adb.
What do I do?
Click to expand...
Click to collapse
Have you downloaded the Android SDK? If not, here it is:
https://developer.android.com/sdk/index.html
Once downloaded, you don't need all of the components. Just install platform-tools, and Google drivers. You may have to uninstall any drivers that aren't for your nexus 6. You may also have to point your PC to the Google drivers via device manager. :victory:
Evolution_Freak said:
Have you downloaded the Android SDK? If not, here it is:
https://developer.android.com/sdk/index.html
Once downloaded, you don't need all of the components. Just install platform-tools, and Google drivers. You may have to uninstall any drivers that aren't for your nexus 6. You may also have to point your PC to the Google drivers via device manager. :victory:
Click to expand...
Click to collapse
Yes, I downloaded Android SDK, and installed the 4 packages it said to. I will see if I can get it to work through device manager, thanks!
a.demarco said:
Yes, I downloaded Android SDK, and installed the 4 packages it said to. I will see if I can get it to work through device manager, thanks!
Click to expand...
Click to collapse
Yeah, I knew there were a couple other SDK components needed but I couldn't think of them off the top of my head and also get my kids ready for bed at the same time. Lol!! Glad you're on the right track! :good:
a.demarco said:
Yes, I downloaded Android SDK, and installed the 4 packages it said to. I will see if I can get it to work through device manager, thanks!
Click to expand...
Click to collapse
Try turning the device off and then boot into fastboot (Pwr + Vol down) then plug the phone into the computer. You can also install Wug's Toolkit at the link below:
http://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452
slimc84 said:
Try turning the device off and then boot into fastboot (Pwr + Vol down) then plug the phone into the computer. You can also install Wug's Toolkit at the link below:
http://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452
Click to expand...
Click to collapse
I will try turning it off and booting into fastboot, thanks for that! I am trying to avoid using toolkits, I enjoy the learning process.
a.demarco said:
I will try turning it off and booting into fastboot, thanks for that! I am trying to avoid using toolkits, I enjoy the learning process.
Click to expand...
Click to collapse
I was recommending the toolkit just to install the drivers. I too enjoy the learning process and familiarizing myself with adb. Just in case I need it one day.
slimc84 said:
I was recommending the toolkit just to install the drivers. I too enjoy the learning process and familiarizing myself with adb. Just in case I need it one day.
Click to expand...
Click to collapse
Ah, gotcha... Had no idea the drivers were in the toolkits!
a.demarco said:
Ah, gotcha... Had no idea the drivers were in the toolkits!
Click to expand...
Click to collapse
Are you still having driver issues or did you get it sorted out? Just curious.
Evolution_Freak said:
Are you still having driver issues or did you get it sorted out? Just curious.
Click to expand...
Click to collapse
Haven't tried it again since last night... Doing some high pressure ductile iron underground water piping all day today, will try later tonight.
a.demarco said:
Haven't tried it again since last night... Doing some high pressure ductile iron underground water piping all day today, will try later tonight.
Click to expand...
Click to collapse
Yes, priorities. If you have any questions later, don't hesitate to ask.
Download the nexus toolkit and follow the instructions given in it to install the drivers, you don't even need the android sdk,
a.demarco said:
OS Windows 7 Home Premium 64-bit SP1
...
What do I do?
Click to expand...
Click to collapse
Delete that crap and install a real operating system.
doitright said:
Delete that crap and install a real operating system.
Click to expand...
Click to collapse
And what in your opinion is a real operating system?
Related
Am attempting to root my new n7 using:
Nexus-7-root-toolkit-v.1.1
iiuc as I have not put anything on there I don't need to unlock the bootloader. So I proceeded directly to installing the drivers.
I got a message saying that I had an existing Android driver installed (I assume for my sgs2) and a 'hit yes to reinstall, no to keep' message, which is a bit ambiguous. YES seems to lead to further activity. Enabled usb debugging, replugged the n7 and never saw any more activity, wizard or reboot. Hitting OK goes to phone not detected rc=103. Driver appears to uninstall from here.
Not a clue what I'm meant to do from this point, and suggestions welcome.
Ian
I chose yes (to reinstall driver).
ikeny said:
I chose yes (to reinstall driver).
Click to expand...
Click to collapse
I tried that too, but it lead to the 103.
Don't know how to proceed from here.
i
I'm confused. The Nexus Root Toolkit is v1.5 (not 1.1).
http://forum.xda-developers.com/showthread.php?t=1766475
Are you actually using the one click root tool (v1.1)?
http://forum.xda-developers.com/showthread.php?t=1742919
Either way, watch the youtube videos linked on the first post in each thread. It'll help to clarify things.
You have to unlock the boot loader in order to root.
Manually install them, follow the cyanogenmod guide on installing adb drivers.
Sent from my LG-P999 using xda app-developers app
IanWorthington said:
Am attempting to root my new n7 using:
Nexus-7-root-toolkit-v.1.1
iiuc as I have not put anything on there I don't need to unlock the bootloader. So I proceeded directly to installing the drivers.
I got a message saying that I had an existing Android driver installed (I assume for my sgs2) and a 'hit yes to reinstall, no to keep' message, which is a bit ambiguous. YES seems to lead to further activity. Enabled usb debugging, replugged the n7 and never saw any more activity, wizard or reboot. Hitting OK goes to phone not detected rc=103. Driver appears to uninstall from here.
Not a clue what I'm meant to do from this point, and suggestions welcome.
Ian
Click to expand...
Click to collapse
first off download the newest root toolkit from wugfresh 1.52
then if u have problem with the drivers with the toolkit, then stop the toolkit and install pda net on ur pc and it will install the drivers for u! then try unlocking and rooting and it should be alot easier. The only problem i had was with the drivers.
ikeny said:
I'm confused. The Nexus Root Toolkit is v1.5 (not 1.1).
http://forum.xda-developers.com/showthread.php?t=1766475
Are you actually using the one click root tool (v1.1)?
http://forum.xda-developers.com/showthread.php?t=1742919
Either way, watch the youtube videos linked on the first post in each thread. It'll help to clarify things.
You have to unlock the boot loader in order to root.
Click to expand...
Click to collapse
It *is* the one click tool, yes. I'l check out the videos, thanks. The text says the boot loader unlocking was optional, but I'll install the SDK and try that, thanks.
i
IanWorthington said:
It *is* the one click tool, yes. I'l check out the videos, thanks. The text says the boot loader unlocking was optional, but I'll install the SDK and try that, thanks.
i
Click to expand...
Click to collapse
It's only optional for those that already unlocked their boot loader previously.
In you case, you have to do it since yours is locked at the moment.
Needed to change the USB mode then the driver install and rooting worked fine. Wasn't obvious to me at least!
Many thanks.
Ian
ikeny said:
It's only optional for those that already unlocked their boot loader previously.
In you case, you have to do it since yours is locked at the moment.
Click to expand...
Click to collapse
Didn't have to unlock prior to rooting, the one click process did that for me.
i
After upgrading to 4.2.2, some N7 will not be seen by any computer via USB and the only way to remedy it is to shut off USB debugging. On other devices, the computer will see the N7 even if USB debugging is enabled, but running "adb devices" will show the device as offline. This is a problem with the Nexus 10 as well.
UPDATE: This turns out to be security. See below.
Sent from my Nexus 7 using Tapatalk HD
oldblue910 said:
After upgrading to 4.2.2, some N7 will not be seen by any computer via USB and the only way to remedy it is to shut off USB debugging. On other devices, the computer will see the N7 even if USB debugging is enabled, but running "adb devices" will show the device as offline. This is a problem with the Nexus 10 as well.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Just waiting for more ppl to confirm this problem. I still stay at 4.2.1
Re: Warning: 4.2.2 Breaks ADB and USB Debugging
No problems here. USB debugging turned on, transferring my data back to my storage now. Tho I did update my SDK tools to the latest the other day. You will see a new pop up message to allow debugging pop up.
Sent from my Nexus 4 using xda premium
rayford85 said:
No problems here. USB debugging turned on, transferring my data back to my storage now. Tho I did update my SDK tools to the latest the other day. You will see a new pop up message to allow debugging pop up.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Ah this may be my issue...I may need to update my SDK tools. I haven't done that in months.
Confirmed breakage usb debugging and adb on my nexus 7
I just installed the 4.2.2 update on rooted stock and after installation root no longer worked. When I went to re-root I could not connect. It showed my tablet but it said it was showing as turned off or unavailable even though it was connected so then I restored back to 4.2.1 unrooted and tryed to connect and same problem. You can connect and send media files but anything else is not working at least for me.
So for my device I can confirm adb and usb debugging seems broken for now. I have the first production run 16 wifi model. I can also say wifi performance seems improved. The signal seems slightly boosted and also seems to stream content smoother farther away from the router. I do not have any bluetooth devices to confirm those fixes. Seems fast and stable for me so far.
I will probably revert back to a custom rom since I like the rooted apps but this release initially seems pretty solid.
Re: Warning: 4.2.2 Breaks ADB and USB Debugging
robbbzilla said:
I just installed the 4.2.2 update on rooted stock and after installation root no longer worked. When I went to re-root I could not connect. It showed my tablet but it said it was showing as turned off or unavailable even though it was connected so then I restored back to 4.2.1 unrooted and tryed to connect and same problem. You can connect and send media files but anything else is not working at least for me.
So for my device I can confirm adb and usb debugging seems broken for now. I have the first production run 16 wifi model. I can also say wifi performance seems improved. The signal seems slightly boosted and also seems to stream content smoother farther away from the router. I do not have any bluetooth devices to confirm those fixes. Seems fast and stable for me so far.
I will probably revert back to a custom rom since I like the rooted apps but this release initially seems pretty solid.
Click to expand...
Click to collapse
There's a new security feature in 4.2.2 to keep "adb thiefs" off your device. http://www.androidpolice.com/2013/0...s-from-stealing-your-data-in-some-situations/
After you enable USB debugging and plug the device in, you should get a prompt to allow the computer access to your device.
Sent from my Nexus 4 using xda premium
Wouldn't exactly say "it's broken" considering:
http://www.androidpolice.com/2013/0...s-from-stealing-your-data-in-some-situations/
It's a new addition to the ADB security and I'm sure as time passes we'll learn more about the inner workings.
Disclaimer: I installed 4.2.2 this morning just after it was released and I had no issues with ADB or USB debugging in the 2-3 hours I was testing it - I was pure stock across the board from 4.2.1 to 4.2.2 and had no problems.
Bleh, post above me covered it just as I did, only a few seconds faster.
Definitely not a bug
... it's a security feature, as mentioned above. I was pulling my hair out over it at first, until I rebooted my computer and restarted adb, and got the familiar dialog. You have to activate it for each machine you plug it into, it seems.
rayford85 said:
There's a new security feature in 4.2.2 to keep "adb thiefs" off your device. http://www.androidpolice.com/2013/0...s-from-stealing-your-data-in-some-situations/
After you enable USB debugging and plug the device in, you should get a prompt to allow the computer access to your device.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I know about the security feature. It did not prompt me. I even turned usb debugging on and off, turned pc and device on and off. I cleared cache and no difference. I did not get any prompt.
Maybe it is just me.
I will reflash and reboot and update it again and see if it works but for me it doesn't work. Not sure about broken just not working for installing root. I can transfer media files fine.
Just run the Android SDK Manager and update everything. Fixed.
Always remember, new version? Use ADB? Update SDK.
Also Wugs Toolkit will work again if you replace the adb files that comes with his kit.
r00t4rd3d said:
Just run the Android SDK Manager and update everything. Fixed.
Always remember, new version? Use ADB? Update SDK.
Also Wugs Toolkit will work again if you replace the adb files that comes with his kit.
Click to expand...
Click to collapse
I will give it a shot. Sometimes I forget to do basic things thinking I know about something I don't. So many more knowledgeable people here. Thanks for the help.
R
oldblue910 said:
After upgrading to 4.2.2, some N7 will not be seen by any computer via USB and the only way to remedy it is to shut off USB debugging. On other devices, the computer will see the N7 even if USB debugging is enabled, but running "adb devices" will show the device as offline. This is a problem with the Nexus 10 as well.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
It was working for me,I used adb to pull the system of the nexus 7.
Re: Warning: 4.2.2 Breaks ADB and USB Debugging
Updating adb fixed my N10 but not the N7. On the N7, with USB debugging enabled, adb devices shows no devices and will not show up as a media device. If I disable USB debugging, it will show up as a media device, though. Also, adb sideload works fine in stock recovery. Any thoughts?
Sent from my Galaxy Nexus using Tapatalk 2
Re: Warning: 4.2.2 Breaks ADB and USB Debugging
Yes, be sure to update your SDK to API17. There is a glitch on the SDK manager though that I had where I had to refresh the list twice to even have API17 appear. Otherwise it ended at API16/4.1
Sent from my Nexus 7 using Tapatalk HD
Re: Warning: 4.2.2 Breaks ADB and USB Debugging
r00t4rd3d said:
Just run the Android SDK Manager and update everything. Fixed.
Always remember, new version? Use ADB? Update SDK.
Also Wugs Toolkit will work again if you replace the adb files that comes with his
Where can I find the adb file I need to 'replace in wugs kit?
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
tdizzle404 said:
Where can I find the adb file I need to 'replace in wugs kit?
Click to expand...
Click to collapse
The data folder of where ever you installed Wugs tool kit too. I replaced 4 files, adb.exe, fastboot.exe, AdbWinApi.dll, AdbWinUsbApi.dll. You get these 4 files from the Android SDK platform-tools folder after you update the SDK.
-
Perhaps the title of this thread should be changed from
"Warning: 4.2.2 Breaks ADB and USB Debugging"
to
"New Enhanced Security Feature with 4.2.2"
Just a thought..
r00t4rd3d said:
The data folder of where ever you installed Wugs tool kit too. I replaced 4 files, adb.exe, fastboot.exe, AdbWinApi.dll, AdbWinUsbApi.dll. You get these 4 files from the Android SDK platform-tools folder after you update the SDK.
-
Click to expand...
Click to collapse
Cheers, that was just the info I needed to reapply root after upgrading to 4.2.2. I couldn't work out why ADB could connect but not Wugs toolkit.
ingenious247 said:
Perhaps the title of this thread should be changed from
"Warning: 4.2.2 Breaks ADB and USB Debugging"
to
"New Enhanced Security Feature with 4.2.2"
Just a thought..
Click to expand...
Click to collapse
Exactly ADB Debug has always been a huge glaring security hole for Android devices, some third party apps have been developed or added functionality to disable ADB Debug when the screen is off, etc, to close this hole.
Thanks
r00t4rd3d said:
The data folder of where ever you installed Wugs tool kit too. I replaced 4 files, adb.exe, fastboot.exe, AdbWinApi.dll, AdbWinUsbApi.dll. You get these 4 files from the Android SDK platform-tools folder after you update the SDK.
-
Click to expand...
Click to collapse
you made it possible for me to be rooted again ... wish i could thank you more than once ... that was getting frustrating ... now after that whole ordeal im considering going back to aokp jb mr1 B3 over staying stock ... but maybe ill just wait ... depends on how long i can stand using the GNEX with a cracked f'n screen lol ... man can the SG4 hurry up??? idk what to do right now .. i need something to flashhhhhhh!!!
Hi,
I'm having problems connecting my phone to my computer (MacBookPro). I tried downloading Motorola Device Manager, but it won't work (since I'm using OS X Yosemite). I rebooted in to Win 7, and tried downloading MDM there, but it doesn't install drivers for the phone.
The reason I want to connect the phone to the computer is I'm looking to update the phone to Lollipop (can't stand waiting for the OTA).
//nejo01
nejo01 said:
Hi,
I'm having problems connecting my phone to my computer (MacBookPro). I tried downloading Motorola Device Manager, but it won't work (since I'm using OS X Yosemite). I rebooted in to Win 7, and tried downloading MDM there, but it doesn't install drivers for the phone.
The reason I want to connect the phone to the computer is I'm looking to update the phone to Lollipop (can't stand waiting for the OTA).
//nejo01
Click to expand...
Click to collapse
Have you tried Android File Transfer? https://www.android.com/filetransfer/
_MetalHead_ said:
Have you tried Android File Transfer? CANT QOUTE THIS
Click to expand...
Click to collapse
No, I thought that was just for file transfers (I was looking to try to update my phone, which doesn't seem possible)?
same problem here.
In yosemite (mac osx) doesnt work and dont detect the device.
I think the problem is the compatibility between MDM and Yosemite...
nejo01 said:
No, I thought that was just for file transfers (I was looking to try to update my phone, which doesn't seem possible)?
Click to expand...
Click to collapse
How are you trying to update? ADB/fastboot? You need the Android SDK for that.
_MetalHead_ said:
How are you trying to update? ADB/fastboot? You need the Android SDK for that.
Click to expand...
Click to collapse
No, I was simply trying to check for updates via the computer (as I read somewhere that Lollipop was released - but it didn't show up in my phone)
I've been skimming some threads on updating the phone, but from what I could tell the phone needs to an XT1095 and not the 92 that I have?
nejo01 said:
No, I was simply trying to check for updates via the computer (as I read somewhere that Lollipop was released - but it didn't show up in my phone)
I've been skimming some threads on updating the phone, but from what I could tell the phone needs to an XT1095 and not the 92 that I have?
Click to expand...
Click to collapse
I think you know something I don't here... exactly how do you plan on updating through your computer? I'm lost.
_MetalHead_ said:
I think you know something I don't here... exactly how do you plan on updating through your computer? I'm lost.
Click to expand...
Click to collapse
I thought that maybe the OTA update-function on the phone wasn't a hundred percent, so figured I'd check out updating via Motorola computer software.
nejo01 said:
I thought that maybe the OTA update-function on the phone wasn't a hundred percent, so figured I'd check out updating via Motorola computer software.
Click to expand...
Click to collapse
Ahhh, through Motorola Device Manager? I didn't even know it existed prior to this thread.
And it's not that it's not 100%, it's that the OTA rolls out in stages. Not every phone gets it at the same time. Not quite sure how it'll work through that software though.
Hello,
Maybe this has already been answered, but does anyone know if it's possible to flash an updated radio.img, system.img, bootoader.img and boot.img? I'm a bit of a noob, and I want to upgrade my Nexus 6 to 5.1 once the factory images are released (and the modified boot.img to remove encryption). However, I'd like to do this without the use of a computer. I would use the Nexus Root Toolkit, but for some reason my PC no longer recognizes my device (even though I've tried EVERYTHING to fix, including different cables, ports, drivers, restarts etc.). Maybe the 5.1 update will fix, but I think I have a faulty micro usb port on the device.
I don't want to wipe my data or lose root, which is why I would only update the above images. I thought it could be done through Flashify, but the dev said I'd have to flash an entire .zip through TRWP, but I need the files along with the correct commands. I would lose root, but would use the Towelroot apk to get it back.
Please let me know if this is correct or if I'm missing something. Or if there is an easier way (like maybe Nexus Update Checker).
Thanks
ryan4a said:
Hello,
Maybe this has already been answered, but does anyone know if it's possible to flash an updated radio.img, system.img, bootoader.img and boot.img? I'm a bit of a noob, and I want to upgrade my Nexus 6 to 5.1 once the factory images are released (and the modified boot.img to remove encryption). However, I'd like to do this without the use of a computer. I would use the Nexus Root Toolkit, but for some reason my PC no longer recognizes my device (even though I've tried EVERYTHING to fix, including different cables, ports, drivers, restarts etc.). Maybe the 5.1 update will fix, but I think I have a faulty micro usb port on the device.
I don't want to wipe my data or lose root, which is why I would only update the above images. I thought it could be done through Flashify, but the dev said I'd have to flash an entire .zip through TRWP, but I need the files along with the correct commands. I would lose root, but would use the Towelroot apk to get it back.
Please let me know if this is correct or if I'm missing something. Or if there is an easier way (like maybe Nexus Update Checker).
Thanks
Click to expand...
Click to collapse
first off, towelroot doesnt work in android 5.0+. 2ndly, if you are planning on flashing the official 5.1, you need a computer. if you are planning on updating a custom rom, and you have twrp recovery, download the rom and flash it via twrp.
simms22 said:
first off, towelroot doesnt work in android 5.0+. 2ndly, if you are planning on flashing the official 5.1, you need a computer. if you are planning on updating a custom rom, and you have twrp recovery, download the rom and flash it via twrp.
Click to expand...
Click to collapse
Thanks. I don't have a custom ROM. So I guess I'll wait for one to get updated, then install it. Like I said, using a computer is not an option
ryan4a said:
Thanks. I don't have a custom ROM. So I guess I'll wait for one to get updated, then install it. Like I said, using a computer is not an option
Click to expand...
Click to collapse
thats the easiest way. i dont own a computer nor laptop, so i try to do everything from the phone. but its easier to update via recovery anyways. one thing though, since you are on the stock rom, you will have to wipe your data before flashing a custom rom, since the majority are aosp based, and wont flash over stock.
Before you give up, try a different computer (preferably running Linux), or booting the one you have on a livecd/usb.
If the USB plug on the phone is, in fact, broken, try calling motorola. The phone is still under warranty....
doitright said:
Before you give up, try a different computer (preferably running Linux), or booting the one you have on a livecd/usb.
If the USB plug on the phone is, in fact, broken, try calling motorola. The phone is still under warranty....
Click to expand...
Click to collapse
Thanks. I've tried on multiple computers (PC & Mac, but not Linux). Nothing works. I originally thought it was one of the modifications I made to the device, like root, unlock, custom boot.img, custom recovery, modified build.prop, etc. The more I search, the more I think it's hardware. I'd like to not have to warranty it because I'd have to wipe everything, restore to factory settings, unroot, etc. It's just a big hassle. Plus I'd be without a phone until the replacement arrives. I may end up just living with staying on lollipop 5.0.1 forever. It's just super frustrating.
ryan4a said:
Thanks. I've tried on multiple computers (PC & Mac, but not Linux). Nothing works. I originally thought it was one of the modifications I made to the device, like root, unlock, custom boot.img, custom recovery, modified build.prop, etc. The more I search, the more I think it's hardware. I'd like to not have to warranty it because I'd have to wipe everything, restore to factory settings, unroot, etc. It's just a big hassle. Plus I'd be without a phone until the replacement arrives. I may end up just living with staying on lollipop 5.0.1 forever. It's just super frustrating.
Click to expand...
Click to collapse
update your nexus 6 driver, or install the adb driver. your computer cant see your phone until it has one of the drivers installed. if you had it installed, uninstall it and reinstall.
simms22 said:
update your nexus 6 driver, or install the adb driver. your computer cant see your phone until it has one of the drivers installed. if you had it installed, uninstall it and reinstall.
Click to expand...
Click to collapse
For a driver, it isn't a question of seeing it. Its a question of knowing how to talk to it. Further, one of the reasons I suggest he use something that runs linux, is because it avoids this whole driver problem altogether. The other reason is that it is actually consistent, and trivial to determine whether the devices itself actually made a connection, i.e. "dmesg -w", plug it, and see if it says anything.
simms22 said:
update your nexus 6 driver, or install the adb driver. your computer cant see your phone until it has one of the drivers installed. if you had it installed, uninstall it and reinstall.
Click to expand...
Click to collapse
I've deleted and reinstalled the google driver, and installed the ADB driver. No dice. I'm telling you...I've tried everything. That's why I think it's hardware, however unlikely.
ryan4a said:
I've deleted and reinstalled the google driver, and installed the ADB driver. No dice. I'm telling you...I've tried everything. That's why I think it's hardware, however unlikely.
Click to expand...
Click to collapse
when getting adb to work, thats the #1 issue, installing and getting the driver to work. so, i can tell you, many people dont get the driver working without help in manually installing it. it seems those with older windows have less issues then those with newer windows. i really doubt that its a hardware issue.
simms22 said:
when getting adb to work, thats the #1 issue, installing and getting the driver to work. so, i can tell you, many people dont get the driver working without help in manually installing it. it seems those with older windows have less issues then those with newer windows. i really doubt that its a hardware issue.
Click to expand...
Click to collapse
Man I hope you're right. But my PC doesn't even recognize my device. Like it's not even showing up in the device manager. At best, I can sometimes get the PC to recognize it as an "unknown device". When I try to automatically update the driver, it says complete. But nothing changes. What do I do at that point? I haven't been successful in manually updating the driver.
As a matter of fact, I thought my new Turbo charger was broken because it stopped charging my phone. But when I unchecked USB debugging AND unchecked the MTP connection, the charger started working again. Very strange!
ryan4a said:
Man I hope you're right. But my PC doesn't even recognize my device. Like it's not even showing up in the device manager. At best, I can sometimes get the PC to recognize it as an "unknown device". When I try to automatically update the driver, it says complete. But nothing changes. What do I do at that point? I haven't been successful in manually updating the driver.
Click to expand...
Click to collapse
i wouldnt be able to help you there, as i dont own a computer. but there are many that can help out. maybe someone else will see this thread..
ryan4a said:
As a matter of fact, I thought my new Turbo charger was broken because it stopped charging my phone. But when I unchecked USB debugging AND unchecked the MTP connection, the charger started working again. Very strange!
Click to expand...
Click to collapse
Like I said, TRY LINUX.
No drivers required. Everything is built into the kernel.
Fedora even has an "android-tools" package that includes adb. You just install it with "yum install android-tools" -- even on the livecd (it will install to ramdisk).
Quit screwing around with wondoze and TRY IT.
Linux is a mega pita. Nothing is intuitive or easy. All these commands that have to be typed in, yuk. Give me good ol' Windows any day. Lol.
To the OP. Are you on windows 8.1? Have you disabled 'driver signature verification'?
killall said:
Linux is a mega pita. Nothing is intuitive or easy. All these commands that have to be typed in, yuk. Give me good ol' Windows any day. Lol.
To the OP. Are you on windows 8.1? Have you disabled 'driver signature verification'?
Click to expand...
Click to collapse
I'm using Windows 7. Don't think I'll be using Linux either. I'm running out of options for upgrading android versions without a PC. I'm highly considering installing CM12. I'd rather not because it's seems unnecessary on a Nexus device, but don't know what else to do.
There is also about a 5 second delay from the time I plug my device into any charger, to when it actually begins charging. I'm thinking these two issues are related, which leads to believe it's hardware.
Definitely sounding more and more like hardware
ryan4a said:
There is also about a 5 second delay from the time I plug my device into any charger, to when it actually begins charging. I'm thinking these two issues are related, which leads to believe it's hardware.
Click to expand...
Click to collapse
I have the same delay when plugging in a charger. But my PC recognizes my N6 without any problems.
On my Droid Maxx I had driver issues. I asked on XDA and got it figured out. I can't check now but have a look at my posts and you may find your answer.
Back to V-Day.
Hello all, after spending many hours Googling, rebooting, retrying, and staying up way too late, I am stuck. Hopefully someone can provide some guidance as I'm lost.
Yesterday I received my 64GB Nexus 6 from Motorola. I'm on Verizon. Popped in my SIM and was in business. Got it set up in short order, and it applied 5.0.1 OTA almost immediately. I downloaded the .zip for 5.1 and wanted to sideload it as I didn't want to wait for the OTA to hit my phone who-knows-when. Downloaded all the proper utilities and got the phone to show up when executing adb devices. I followed the sideloading guide and was golden up to the point of adb sideload xxxxxxx.zip. Error is "device not found". I uninstalled and reinstalled more drivers than I can shake a stick at, and the phone just won't show up in Device Manager once it's in Recovery. I did my fair share of Googling before posting here and there are many suggestions - most of which point to the driver - but none of them seem to work. I even tried the NRT by Wug and while it gives me two thumbs up as far as drivers are concerned, no dice once the phone is in Recovery.
I am on a Windows 7 Pro 64-bit machine.
So my questions are:
What the heck am I doing wrong?
Is there a way to sideload with the file on the phone already and not have to use adb?
Any help, suggestions, "hey dummy you forgot this", etc., is most welcome . Thank you in advance!
@Lucky Armpit
When you are in recovery, at the adb sideload screen, unplug your N6 and plug it in again.
Lucky Armpit said:
Hello all, after spending many hours Googling, rebooting, retrying, and staying up way too late, I am stuck. Hopefully someone can provide some guidance as I'm lost.
Yesterday I received my 64GB Nexus 6 from Motorola. I'm on Verizon. Popped in my SIM and was in business. Got it set up in short order, and it applied 5.0.1 OTA almost immediately. I downloaded the .zip for 5.1 and wanted to sideload it as I didn't want to wait for the OTA to hit my phone who-knows-when. Downloaded all the proper utilities and got the phone to show up when executing adb devices. I followed the sideloading guide and was golden up to the point of adb sideload xxxxxxx.zip. Error is "device not found". I uninstalled and reinstalled more drivers than I can shake a stick at, and the phone just won't show up in Device Manager once it's in Recovery. I did my fair share of Googling before posting here and there are many suggestions - most of which point to the driver - but none of them seem to work. I even tried the NRT by Wug and while it gives me two thumbs up as far as drivers are concerned, no dice once the phone is in Recovery.
I am on a Windows 7 Pro 64-bit machine.
So my questions are:
What the heck am I doing wrong?
Is there a way to sideload with the file on the phone already and not have to use adb?
Any help, suggestions, "hey dummy you forgot this", etc., is most welcome . Thank you in advance!
Click to expand...
Click to collapse
Use Wugs toolkit to install drivers. It has a great step by step set-up to make sure it works and it tests everything so you know it works..
cam30era said:
@Lucky Armpit
When you are in recovery, at the adb sideload screen, unplug your N6 and plug it in again.
Click to expand...
Click to collapse
Hi cam30era, I tried that but it didn't help. I didn't try it after using Wug's toolkit so it's worth another shot.
Xplicit84 said:
Use Wugs toolkit to install drivers. It has a great step by step set-up to make sure it works and it tests everything so you know it works..
Click to expand...
Click to collapse
Hi Xplicit84, I used the Wugs toolkit provided in the NRT to install the proper drivers (it worked fantastic, by the way... mad props to Wug). That didn't help unfortunately.
try a different usb port
goto the device manager in windows and see if everything is good (no ! by a device)
apristel said:
try a different usb port
goto the device manager in windows and see if everything is good (no ! by a device)
Click to expand...
Click to collapse
Hi apristel, yup, tried that too, as I had read that perhaps there may be an issue with USB 3.0 ports. I don't think I have USB 3.0 ports (my laptop is a 2012-era Alienware M17x R3) but I tried a different port for the sake of doing it and it didn't make a difference.
Where did you get the 5.1 .zip file? Give us the exact name of the file because the 5.1 VZW .zip file that has been posted here that ends with .xml.zip is not designed for an adb sideload command. I.e., not designed to be flashed in recovery at all.
teddyearp said:
Where did you get the 5.1 .zip file? Give us the exact name of the file because the 5.1 VZW .zip file that has been posted here that ends with .xml.zip is not designed for an adb sideload command. I.e., not designed to be flashed in recovery at all.
Click to expand...
Click to collapse
Hi teddyearp, I downloaded it from a link on Droid-Life. I don't remember the exact name of the file because I renamed it to something much shorter, but here's where I got it from -
http://www.droid-life.com/2015/03/1...s-for-nexus-devices-4-5-6-7-9-10/#more-163271
Edit - Here's the direct link (the one I used) - http://android.clients.google.com/p...ed-shamu-ota-LMY47D-from-LRX22C-fullradio.zip
Lucky Armpit said:
Hello all, after spending many hours Googling, rebooting, retrying, and staying up way too late, I am stuck. Hopefully someone can provide some guidance as I'm lost.
Yesterday I received my 64GB Nexus 6 from Motorola. I'm on Verizon. Popped in my SIM and was in business. Got it set up in short order, and it applied 5.0.1 OTA almost immediately. I downloaded the .zip for 5.1 and wanted to sideload it as I didn't want to wait for the OTA to hit my phone who-knows-when. Downloaded all the proper utilities and got the phone to show up when executing adb devices. I followed the sideloading guide and was golden up to the point of adb sideload xxxxxxx.zip. Error is "device not found". I uninstalled and reinstalled more drivers than I can shake a stick at, and the phone just won't show up in Device Manager once it's in Recovery. I did my fair share of Googling before posting here and there are many suggestions - most of which point to the driver - but none of them seem to work. I even tried the NRT by Wug and while it gives me two thumbs up as far as drivers are concerned, no dice once the phone is in Recovery.
I am on a Windows 7 Pro 64-bit machine.
So my questions are:
What the heck am I doing wrong?
Is there a way to sideload with the file on the phone already and not have to use adb?
Any help, suggestions, "hey dummy you forgot this", etc., is most welcome . Thank you in advance!
Click to expand...
Click to collapse
Any luck, having the same problem and it's driving me nuts.
Mongo23ny said:
Any luck, having the same problem and it's driving me nuts.
Click to expand...
Click to collapse
Are you selecting "apply update from ADB" in recovery and then hitting power?
Then: adb sideload <filename of update.zip>
?
apristel said:
Are you selecting "apply update from ADB" in recovery and then hitting power?
Then: adb sideload <filename of update.zip>
?
Click to expand...
Click to collapse
Yes, as soon as boots into recovery it completely disappears from device manager. If I run the command after apply update from adb it says device not found.
Mongo23ny said:
Yes, as soon as boots into recovery it completely disappears from device manager. If I run the command after apply update from adb it says device not found.
Click to expand...
Click to collapse
Most likely a driver issue. I can remote in and check it out if you want using teamviewer
Go through the driver setup in wug again, pay close attention when you are deleting any old drivers..... delete anything that says google nexus or android... I had to do it twice.... put the phone into adb side load mode... check device manager again.. make sure you dont have a ? by android device... I did... update the driver from wug ( also I hid the sdk driver folder by renaming it so windows didn't try to pick up the driver from there again... once installed bingo!
apristel said:
Most likely a driver issue. I can remote in and check it out if you want using teamviewer
Click to expand...
Click to collapse
When I run the command reboot bootloader, no problem. But when it is in recovery I watched it disappear from device manager.
---------- Post added at 10:19 PM ---------- Previous post was at 10:18 PM ----------
Gage_Hero said:
Go through the driver setup in wug again, pay close attention when you are deleting any old drivers..... delete anything that says google nexus or android... I had to do it twice.... put the phone into adb side load mode... check device manager again.. make sure you dont have a ? by android device... I did... update the driver from wug ( also I hid the sdk driver folder by renaming it so windows didn't try to pick up the driver from there again... once installed bingo!
Click to expand...
Click to collapse
I used CF auto root to unlock the bootloader and root. I do have the NRT on my computer though.
Mongo23ny said:
When I run the command reboot bootloader, no problem. But when it is in recovery I watched it disappear from device manager.
---------- Post added at 10:19 PM ---------- Previous post was at 10:18 PM ----------
I used CF auto root to unlock the bootloader and root. I do have the NRT on my computer though.
Click to expand...
Click to collapse
I still think its a driver issue for you though. I am using the ones you can download here and it works fine.
http://developer.android.com/sdk/win-usb.html#download (Where it says... Click here to download the latest Google USB Driver ZIP file.)
apristel said:
I still think its a driver issue for you though. I am using the ones you can download here and it works fine.
http://developer.android.com/sdk/win-usb.html#download (Where it says... Click here to download the latest Google USB Driver ZIP file.)
Click to expand...
Click to collapse
How do I install it properly? I got rid of some old drivers as well
Mongo23ny said:
How do I install it properly? I got rid of some old drivers as well
Click to expand...
Click to collapse
Well you can just change them in the device manager.
I'm willing to use team viewer and show you how. (you'd see everything i do) It's hard to write it out for me right now..just had hand surgery this morning and my hand is still completely numb. If you want to download this and run it http://download.teamviewer.com/download/TeamViewerQS_en.exe
PM me the id and password and i'll connect up and show ya. Just so you know, it'd be a one time thing connecting, your password changes everytime and you'd have to have that running to connect. I own a computer repair store and use it frequently.
apristel said:
I still think its a driver issue for you though. I am using the ones you can download here and it works fine.
http://developer.android.com/sdk/win-usb.html#download (Where it says... Click here to download the latest Google USB Driver ZIP file.)
Click to expand...
Click to collapse
I'm thinking that's the problem for me too, but I don't understand what I'm missing. When I ran Wug, I removed anything and everything that had the word "Google" next to it. Wug installed the drivers (had to do option #2 before I got no errors at all) and it reports that everything is hunky-dory. But as Mongo23ny said, that's exactly what happens... when it's at the boot menu it's in Device Manager but the moment I select Recovery it disappears.
Lucky Armpit said:
I'm thinking that's the problem for me too, but I don't understand what I'm missing. When I ran Wug, I removed anything and everything that had the word "Google" next to it. Wug installed the drivers (had to do option #2 before I got no errors at all) and it reports that everything is hunky-dory. But as Mongo23ny said, that's exactly what happens... when it's at the boot menu it's in Device Manager but the moment I select Recovery it disappears.
Click to expand...
Click to collapse
I can try to fix your drivers too, just follow the link i posted for him and send me the info. I don't have stock recovery on my phone to replicate your issue.
apristel said:
I can try to fix your drivers too, just follow the link i posted for him and send me the info. I don't have stock recovery on my phone to replicate your issue.
Click to expand...
Click to collapse
PM sent. Thanks