Related
Some of you may have felt the frustration of trying to root using a computer running Windows 8.1. (I have Windows 8.1 RTM) I actually tried to root last night. Windows 8.1 would not recognize my HTC One while in fastboot, no matter what I tried. I Googled and tried EVERYTHING out there! I tried various drivers. I tried uninstalling and reinstalling the device. I tried uninstalling and reinstalling the usb root hub through Device Manager. I even tried a virtual machine, which also didn't work. I also have a crappy netbook that dual boots Windows 7 and Ubuntu 12.04, but I was stubborn and was determined to try to figure it out.
Then the update came today. Since the update included a new HBoot, I was curious if that would make a difference. So I went into fastboot and hoped for the best. Lo and behold, the computer began installing the correct drivers! That was enough. And now I am happily rooted. Not S-Off yet, but that will come!
I am a happy Panda!
pandacookie said:
Some of you may have felt the frustration of trying to root using a computer running Windows 8.1. (I have Windows 8.1 RTM) I actually tried to root last night. Windows 8.1 would not recognize my HTC One while in fastboot, no matter what I tried. I Googled and tried EVERYTHING out there! I tried various drivers. I tried uninstalling and reinstalling the device. I tried uninstalling and reinstalling the usb root hub through Device Manager. I even tried a virtual machine, which also didn't work. I also have a crappy netbook that dual boots Windows 7 and Ubuntu 12.04, but I was stubborn and was determined to try to figure it out.
Then the update came today. Since the update included a new HBoot, I was curious if that would make a difference. So I went into fastboot and hoped for the best. Lo and behold, the computer began installing the correct drivers! That was enough. And now I am happily rooted. Not S-Off yet, but that will come!
I am a happy Panda!
Click to expand...
Click to collapse
nice.
That is real good news
Well I've been rooting and un rooting and going into the bootloader on Windows 8.0 since the beginning. But happy it's working for you now.
Sent from my HTCONE using XDA Premium 4 mobile app
BrianBaker said:
Well I've been rooting and un rooting and going into the bootloader on Windows 8.0 since the beginning. But happy it's working for you now.
Sent from my HTCONE using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Oh, I know it worked in 8.0. But it didn't work in 8.1 for a lot of people, myself included. This wasn't just an HTC One issue, either. This was an issue for quite a few phones. But yeah, it works now. Either it's one crazy coincidence that this triggered 8.1 to recognize my HTC One in fastboot, or this update really makes a difference.
Just re-read what you wrote and realized what you were saying.. My bad... Waiting for official 8.1 to roll out myself so I'm happy to know I won't have an issue.
Sent from my HTCONE using XDA Premium 4 mobile app
Oh it's all good! I hope what I discovered here helps a few people.
Yea, I had to reinstall 8.1 to 8.0 at work because no matter what I did it would not work..
pandacookie said:
Some of you may have felt the frustration of trying to root using a computer running Windows 8.1. (I have Windows 8.1 RTM) I actually tried to root last night. Windows 8.1 would not recognize my HTC One while in fastboot, no matter what I tried. I Googled and tried EVERYTHING out there! I tried various drivers. I tried uninstalling and reinstalling the device. I tried uninstalling and reinstalling the usb root hub through Device Manager. I even tried a virtual machine, which also didn't work. I also have a crappy netbook that dual boots Windows 7 and Ubuntu 12.04, but I was stubborn and was determined to try to figure it out.
Then the update came today. Since the update included a new HBoot, I was curious if that would make a difference. So I went into fastboot and hoped for the best. Lo and behold, the computer began installing the correct drivers! That was enough. And now I am happily rooted. Not S-Off yet, but that will come!
I am a happy Panda!
Click to expand...
Click to collapse
Yep can confirm! Fastboot finally works on 8.1!
It always worked with 8 and 8.1 if you used the clockworkmod universal adb drivers
orthonovum said:
It always worked with 8 and 8.1 if you used the clockworkmod universal adb drivers
Click to expand...
Click to collapse
They didn't work for me, though.
pandacookie said:
They didn't work for me, though.
Click to expand...
Click to collapse
strange, works for me and friends on windows 7, 8, 8.1 no problems.. anyway sounds like things are no longer an issue with 4.3 tho so good to hear
Perhaps it works for only people that updated to the newer hboot. I flashed the firmware without the new hboot and mine is still borked.
I think it does have something to do with the new hboot, I have the new firmware minus the hboot and it still isn't working for me.
Sent from my HTCONE using Tapatalk 4
pandacookie said:
Some of you may have felt the frustration of trying to root using a computer running Windows 8.1. (I have Windows 8.1 RTM) I actually tried to root last night. Windows 8.1 would not recognize my HTC One while in fastboot, no matter what I tried. I Googled and tried EVERYTHING out there! I tried various drivers. I tried uninstalling and reinstalling the device. I tried uninstalling and reinstalling the usb root hub through Device Manager. I even tried a virtual machine, which also didn't work. I also have a crappy netbook that dual boots Windows 7 and Ubuntu 12.04, but I was stubborn and was determined to try to figure it out.
Then the update came today. Since the update included a new HBoot, I was curious if that would make a difference. So I went into fastboot and hoped for the best. Lo and behold, the computer began installing the correct drivers! That was enough. And now I am happily rooted. Not S-Off yet, but that will come!
I am a happy Panda!
Click to expand...
Click to collapse
Oh man you are the best! Sorry to quote you again, but you safed my from doing my head in on the next wall as I couldn't get fastboot to be recognised either.
I have the HTC One Int'l though, but upgrading my Hboot 1.54 to Hboot 1.55 finally got my computer running W8.1 to download the correct drivers and fastboot is working now! What an easy fix LOL
However, latest HTC Sync drivers are necessary and best to upgrade them before upgrading to W8.1 which definetely needs the latest Hboot
I am also a very happpy Panda now!
An issue arises for me when you begin to run an RUU and then it boots you into FastbootRUU mode after root and recovery installed, then it will not work properly.
as I expected, upgrading to the newer hboot from 1.44 to 1.55 does allow windows 8.1 to install fastboot driver.
does updating the hboot to 1.55 effect being s-off at all? i would like my windows 8 to work with my htc one but not if itll take away my s-off.
Still don't work for me
liljthatbol said:
Still don't work for me
Click to expand...
Click to collapse
Update to latest HBOOT and install HTC sync.
Details:
ViperOne 3.5, S-ON, did not update firmware from yesterdays release (not radio either).
Did this:
PRL update
Update Profile
Baseband: 1.00.20.0913_3
Build Number: 3.62.401.1 CL264544-release-keys
Kernel (stock).
Did I miss? It's just a frickin' PRL and profile update, and that kills calls? Data works, though. So crap! Any help would be greatly appreciated.
tdhite said:
Details:
ViperOne 3.5, S-ON, did not update firmware from yesterdays release (not radio either).
Did this:
PRL update
Update Profile
Baseband: 1.00.20.0913_3
Build Number: 3.62.401.1 CL264544-release-keys
Kernel (stock).
Did I miss? It's just a frickin' PRL and profile update, and that kills calls? Data works, though. So crap! Any help would be greatly appreciated.
Click to expand...
Click to collapse
I had this issue as well where I had data but couldnt make calls or send or recieve texts. Went three days without it. Did everything ruu'd back to stock, reflashed recovery, roms, re rooted, nothing worked. Then I flashed the newest radio I found on xda, rebooted and after a period time it started working. I'm not sure if it was the radio or something a miss with the tower in my area but yeah that's what I did.
tdhite said:
Details:
ViperOne 3.5, S-ON, did not update firmware from yesterdays release (not radio either).
Did this:
PRL update
Update Profile
Baseband: 1.00.20.0913_3
Build Number: 3.62.401.1 CL264544-release-keys
Kernel (stock).
Did I miss? It's just a frickin' PRL and profile update, and that kills calls? Data works, though. So crap! Any help would be greatly appreciated.
Click to expand...
Click to collapse
TRY toggling airplane mode on then off, sometimes it works.
Aldo101t said:
TRY toggling airplane mode on then off, sometimes it works.
Click to expand...
Click to collapse
wow -- would not have thought of that. seems to have worked. that's friggin' strange. thanks a million.
I am running Stock 4.3 S-OFF with root. I have not taken the new OTA. I figured I might as well at least grab the new 55017 PRL as I was on 55016. Everything said it was successful and I didn't think much about it. A couple hours later I realize I can't send texts or make phone calls. Tried all the tricks (airplane mode, ##72786#, etc), same result. Had to call Sprint and they could see that earlier I updated profile and PRL, but something wasn't looking right on their end. Turns out that the PRL and profile update I did changed the MSID of the device. They had me program in the correct MSID tied to this device and voila....everything works again! All these years of doing this stuff I have never seen a profile/PRL update change the MSID....CRAZY!!
Hey, mind me asking which ROM you used and which S-OFF till you used. I'm on that this weekend, liking for the right setup to go without a hitch.
tdhite said:
Hey, mind me asking which ROM you used and which S-OFF till you used. I'm on that this weekend, liking for the right setup to go without a hitch.
Click to expand...
Click to collapse
I would suggest OMJ/benny's stock rooted 3.04 rom it has worked flawlessly every time I have helped smeone S-OFF using rumrunner
Thanks, 'been looking for just that info for a while, and better yet, your word is always good around here.
I had the same issue. updated prl and profile and no more phone or text. Sprint had to reset my network on my phone and now it works.
01bird said:
I had the same issue. updated prl and profile and no more phone or text. Sprint had to reset my network on my phone and now it works.
Click to expand...
Click to collapse
@bigdaddy619 -- got Ubuntu up, Android SDK works flawlessly (adb, fastboot, all things work fine -- tested 'em before starting). The SDK works whether root or standard user, though I ran RumRunner as root.
Using the ROM you suggested above, ends up with "ERROR: looks like device is not rooted AND lacks an unsecure kernel. su or FU!!!" so no go. Interestingly, during the first reboot I saw superuser grant rights to adb, and I tested root (adb shell; su) so I know it's rooted.
Whole log is attached -- would love some help getting this going.
tdhite said:
@bigdaddy619 -- got Ubuntu up, Android SDK works flawlessly (adb, fastboot, all things work fine -- tested 'em before starting). The SDK works whether root or standard user, though I ran RumRunner as root.
Using the ROM you suggested above, ends up with "ERROR: looks like device is not rooted AND lacks an unsecure kernel. su or FU!!!" so no go. Interestingly, during the first reboot I saw superuser grant rights to adb, and I tested root (adb shell; su) so I know it's rooted.
Whole log is attached -- would love some help getting this going.
Click to expand...
Click to collapse
BTW, just PM me if it's easier for debugging / working through.
tdhite said:
@bigdaddy619 -- got Ubuntu up, Android SDK works flawlessly (adb, fastboot, all things work fine -- tested 'em before starting). The SDK works whether root or standard user, though I ran RumRunner as root.
Using the ROM you suggested above, ends up with "ERROR: looks like device is not rooted AND lacks an unsecure kernel. su or FU!!!" so no go. Interestingly, during the first reboot I saw superuser grant rights to adb, and I tested root (adb shell; su) so I know it's rooted.
Whole log is attached -- would love some help getting this going.
Click to expand...
Click to collapse
Did you update the binaries in SuperSU? Because both of those roms have su and an insecure kernel as far as I know
bigdaddy619 said:
Did you update the binaries in SuperSU? Because both of those roms have su and an insecure kernel as far as I know
Click to expand...
Click to collapse
Hmmm... I just ran SuperSU and it did want to restart in CWM (PhilZ for me) and update. That's the issue? Think? I just run 'er again after the update? I want my cleansing shower of rum
tdhite said:
Hmmm... I just ran SuperSU and it did want to restart in CWM (PhilZ for me) and update. That's the issue? Think? I just run 'er again after the update? I want my cleansing shower of rum
Click to expand...
Click to collapse
Could be the issue if the binaries have not been updated
bigdaddy619 said:
Could be the issue if the binaries have not been updated
Click to expand...
Click to collapse
Yea -- I let it restart into recovery and update the binary, but hey -- I also notice MTP is enabled. Ubuntu (of course) mounts it up (Windows would too if MTP is enabled). Seems in Windows, they want HTC Sync uninstalled -- no doubt, but even that wouldn't disable MTP in Windows.
Has MTP been enabled when you did this (or others you've seen)? I'm actually not quite sure how to turn it off on the phone!
tdhite said:
Yea -- I let it restart into recovery and update the binary, but hey -- I also notice MTP is enabled. Ubuntu (of course) mounts it up (Windows would too if MTP is enabled). Seems in Windows, they want HTC Sync uninstalled -- no doubt, but even that wouldn't disable MTP in Windows.
Has MTP been enabled when you did this (or others you've seen)? I'm actually not quite sure how to turn it off on the phone!
Click to expand...
Click to collapse
Not to my knowledge. Everyone I have helped was using Windows, I don't have much knowledge about Ubuntu
tdhite said:
Yea -- I let it restart into recovery and update the binary, but hey -- I also notice MTP is enabled. Ubuntu (of course) mounts it up (Windows would too if MTP is enabled). Seems in Windows, they want HTC Sync uninstalled -- no doubt, but even that wouldn't disable MTP in Windows.
Has MTP been enabled when you did this (or others you've seen)? I'm actually not quite sure how to turn it off on the phone!
Click to expand...
Click to collapse
Thanks BD -- got it to run through. I feeeeeeeeeeel cleansed! Rum cleansed. S-OFF finally. You're a big help as always -- thanks so much.
Log attached in case any other 'over-careful' person wants to see the entire run.
Be sure to note it -- the ROMs mentioned just need to get the SU update and it'll go well.
This all sure veered off course of the OP -- LOL.
tdhite said:
Thanks BD -- got it to run through. I feeeeeeeeeeel cleansed! Rum cleansed. S-OFF finally. You're a big help as always -- thanks so much.
Log attached in case any other 'over-careful' person wants to see the entire run.
Be sure to note it -- the ROMs mentioned just need to get the SU update and it'll go well.
This all sure veered off course of the OP -- LOL.
Click to expand...
Click to collapse
Nice congrats
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 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
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?