I've been trying to get a ROM on my nexus 6, but as I go to unlock the bootloader, I enable usb debugging but get no prompt to authorize my computer's RSA Fingerprint. Any Ideas would be helpful. I've Tried all different combinations of connections (MTP+USB Debugging, etc.), and it still will not prompt me to authorize it. Thanks.
Have you tried Nexus Root Toolkit? I used that back in January to unlock and root my Nexus 6.
Sent from my Nexus 6 using Tapatalk
xt99ikd said:
I've been trying to get a ROM on my nexus 6, but as I go to unlock the bootloader, I enable usb debugging but get no prompt to authorize my computer's RSA Fingerprint. Any Ideas would be helpful. I've Tried all different combinations of connections (MTP+USB Debugging, etc.), and it still will not prompt me to authorize it. Thanks.
Click to expand...
Click to collapse
Reboot the device. Set switches for USB debug and bootloader unlock. Plug in phone. If don't work there a driver problem. If see your drive on PC don't worry about it. If it sees adb and/or fastboot don't worry about it. Don't use toolkit unless already know how to fastboot. If it screws up you are screwed cause don't know what happened.
xt99ikd said:
I've been trying to get a ROM on my nexus 6, but as I go to unlock the bootloader, I enable usb debugging but get no prompt to authorize my computer's RSA Fingerprint. Any Ideas would be helpful. I've Tried all different combinations of connections (MTP+USB Debugging, etc.), and it still will not prompt me to authorize it. Thanks.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2948481
For those who happen across this thread but cannot be bothered to read the link above, here is a little note. You do NOT need USB Debugging to unlock the bootloader. USB Debugging is an ANDROID setting, for use in Android. It has no effect on what happens to USB connections made in the bootloader or recovery.
EDIT> Actually that thread says you do need it. You do not.
danarama said:
For those who happen across this thread but cannot be bothered to read the link above, here is a little note. You do NOT need USB Debugging to unlock the bootloader. USB Debugging is an ANDROID setting, for use in Android. It has no effect on what happens to USB connections made in the bootloader or recovery.
EDIT> Actually that thread says you do need it. You do not.
Click to expand...
Click to collapse
For that thread no you do not need it if boot into the bootloader manually. For others that use the adb reboot bootloader command you will need it.
prdog1 said:
For that thread no you do not need it if boot into the bootloader manually. For others that use the adb reboot bootloader command you will need it.
Click to expand...
Click to collapse
That's not my point.
I have been struggling with drivers have uninstalled and reinstalled multiple times to no luck. For some reason keeps thinking its a Samsung
Any suggestions?
Sorry for Thread Hijack
ostap999 said:
I have been struggling with drivers have uninstalled and reinstalled multiple times to no luck. For some reason keeps thinking its a Samsung
Any suggestions?
Sorry for Thread Hijack
Click to expand...
Click to collapse
Try this:
http://forum.xda-developers.com/showthread.php?t=2588979
The NRT kit should be working! :good:
no luck...
cant figure out what i am not uninstalling...
ostap999 said:
no luck...
cant figure out what i am not uninstalling...
Click to expand...
Click to collapse
I know you said you already did, but uninstall every android driver you find on your PC. Then connect your nexus, while booted to android and let drivers install. Then disconnect, boot your nexus into bootloader, and reconnect again to install fastboot drivers.
Related
HI all,
i cant seems to root my device, i followed doomlords guide strictly, but the command prompt never goes beyond "WAITING FOR DEVICE"
i don't know what the problems is, i believe i have installed all the drivers.
can any one help?
Li-polymers said:
HI all,
i cant seems to root my device, i followed doomlords guide strictly, but the command prompt never goes beyond "WAITING FOR DEVICE"
i don't know what the problems is, i believe i have installed all the drivers.
can any one help?
Click to expand...
Click to collapse
Have you turned on USB Debugging under Settings>Developer Options>Debugging ??
If you haven't, then turn it on and then try rooting :silly:
Li-polymers said:
HI all,
i cant seems to root my device, i followed doomlords guide strictly, but the command prompt never goes beyond "WAITING FOR DEVICE"
i don't know what the problems is, i believe i have installed all the drivers.
can any one help?
Click to expand...
Click to collapse
"WAITING FOR DEVICE" is sign u have to active this option SETTINGS -> DEVELOPER OPTIONS -> USB Debugging :highfive:
I did that, I'm not that ignorant.
Sent from my C5303 using xda app-developers app
Tried Connecting the USB cable to some other free USB port in your computer??
Or you could try uninstalling the drivers under Device manager...and then reconnecting the USB cable..:fingers-crossed:
By the way, i followed DoomLord tutorial to root the phone. Is it possible to "unroot" the phone then ? Without losing the change ?
In fact i needed to be root to change a system file to fix wifi
ramcool789 said:
Tried Connecting the USB cable to some other free USB port in your computer??
Or you could try uninstalling the drivers under Device manager...and then reconnecting the USB cable..:fingers-crossed:
Click to expand...
Click to collapse
thanks for the tip, re-installing drivers solved the issue. thanks again.
So I have a rooted and unlocked phone and have been trying to get back to stock, unrooted and relocked. However, I can't seem to get my computer to identify my phone. I have followed the guides on here, I have ADB with all the stuff downloaded and I can get the phone into fastboot. But, when I go into CMD (launched from the correct folder) and type:
fastboot devices
I get a blank response. It isn't recognizing my phone. I have tried going into device manager and deleting the drivers and re-installing but my computer says it can't find the drivers online.
Angel1317 said:
So I have a rooted and unlocked phone and have been trying to get back to stock, unrooted and relocked. However, I can't seem to get my computer to identify my phone. I have followed the guides on here, I have ADB with all the stuff downloaded and I can get the phone into fastboot. But, when I go into CMD (launched from the correct folder) and type:
fastboot devices
I get a blank response. It isn't recognizing my phone. I have tried going into device manager and deleting the drivers and re-installing but my computer says it can't find the drivers online.
Click to expand...
Click to collapse
*http://forum.xda-developers.com/showthread.php?t=879701
ADB Workshop and Guide for everyone
Thanks to "Captainkrtek" for posting
*http://forum.xda-developers.com/showthread.php?t=1474956
[HOW-TO] Install & Use ADB tool | Android Debug Bridge | Drivers - Videos - Tutorial
Thanks to "lavero.burgos" for posting
*http://forum.xda-developers.com/showthread.php?t=2277892
Frequently Asked Questions - HTC One-Sprint(m7wls)
Thanks to "bigdaddy619" for posting
Check these out. & if ur still having probs, let me know.
Sent from my HTCONE using Tapatalk
What OS on computer?
Angel1317 said:
So I have a rooted and unlocked phone and have been trying to get back to stock, unrooted and relocked. However, I can't seem to get my computer to identify my phone. I have followed the guides on here, I have ADB with all the stuff downloaded and I can get the phone into fastboot. But, when I go into CMD (launched from the correct folder) and type:
fastboot devices
I get a blank response. It isn't recognizing my phone. I have tried going into device manager and deleting the drivers and re-installing but my computer says it can't find the drivers online.
Click to expand...
Click to collapse
type: adb devices>enter
Aldo101t said:
type: adb devices>enter
Click to expand...
Click to collapse
Have you checked to make sure usb debugging is ticked on? Sometimes, if it is, you need to un-tick it and then re-tick. Resetting helps and we always forget to check!
Sent from my BNTV600 using Tapatalk 4
Hi guys
Really need urgent help on this one
I wanted to update my nexus 6 to latest5.0.1.
Usually i flash factory images but this time i tried to sideload. This is what i did.
I wanted to factory reset my phone and wipe everything and then side load. so i used TWRP and wiped by mistake the android OS. Now im left with nothing but twrp which also deleted my recovery file.
Now i can access my bootloader and twrp.
My main problem is that when i plug my phone to my pc it does not recognize it and i tried every possible way suggested by NRT tool to update my driver and no luck?
When i plug it to the pc it charges and i get baloon message that pc did not recognized the device.
Im using original cable.
Any help is really appreciated
Thanks
if your pc can recognize your device in fastboot mode then you can go this thread
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
fethi2 said:
if your pc can recognize your device in fastboot mode then you can go this thread
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Click to expand...
Click to collapse
As i said earlier my pc wont recognize my device.
Some said that my motherboard could be damaged is it true?
try the universal adb driver http://adbdriver.com/
you can try this one too.
Najeeb Al Busaidi said:
As i said earlier my pc wont recognize my device.
Some said that my motherboard could be damaged is it true?
Click to expand...
Click to collapse
simms22 said:
try the universal adb driver http://adbdriver.com/
Click to expand...
Click to collapse
Najeeb Al Busaidi said:
As i said earlier my pc wont recognize my device.
Some said that my motherboard could be damaged is it true?
Click to expand...
Click to collapse
If mother board was damaged, you were not able to enter in bootloader Try installing universal driver as other suggested above or install motorola's driver
Najeeb Al Busaidi said:
As i said earlier my pc wont recognize my device.
Some said that my motherboard could be damaged is it true?
Click to expand...
Click to collapse
Enable usb debugging in developer options on the phone, then choose either the drivers posted above or the Google usb drivers from the sdk. Choose to install the drivers manualy in device manager when connected to the pc.
gee2012 said:
Enable usb debugging in developer options on the phone, then choose either the drivers posted above or the Google usb drivers from the sdk. Choose to install the drivers manualy in device manager when connected to the pc.
Click to expand...
Click to collapse
Debugging is both impossible and useless.
Can't set USB debugging if android is not installed. USB debugging only works in android anyway. It has no affect on bootloader or recovery
rootSU said:
Debugging is both impossible and useless.
Can't set USB debugging if android is not installed. USB debugging only works in android anyway. It has no affect on bootloader or recovery
Click to expand...
Click to collapse
Oke thanks, never to old to learn
gee2012 said:
Oke thanks, never to old to learn
Click to expand...
Click to collapse
99.99999999 .... % of the issue is USB Drivers on the PC in question.
I'd uninstall, then reinstall, or try the universal ones.
Try on another PC if available, once seen you can get it back.
fethi2 said:
if your pc can recognize your device in fastboot mode then you can go this thread
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Click to expand...
Click to collapse
My pc cant recognize the phone while in fastboot
Hi guys
Check the attachment
And let me know if u found the problem.
So I am currently rooted on a Motorla Nexus 6 in Android 5.1.1, I started up the Nexus Root Toolkit and when it finishes downloading stock Android 60.1 to restore my device ready for Android N it sends the adb reboot bootloader command but my device then says in the bootloader menu "Connect USB Data Cable"
Since I cannot post the image link of what the toolkit says then I will just write it below...
"FASTBOOT device was not found
STEP #1: Connect your device via USB:
- Utilize the OEM USB cable if available
- Try an alternative USB port.
STEP #2: Manually Boot your device into bootloader mode:
- Power your device down completely:
- Press and hold the volume down button, them press and hold the power button t the same time until the phone turns on. You'll see the word 'start' with an arrow around it/
STEP #3: Install drivers:
- Utilize the 'initial setup' if you not done so already.
- USB debugging is NOT required for connectivity in bootloader mode.
- Just follow the the instructions in the guide for configuring your device in bootloader mode.
- For example: if you are using driver solution #3, start on step 7.
Alternatively you may just need to recheck connection.
Press 'OK' to recheck device connectivity.
Press 'Cancel' to exit this script"
If anyone has any info on how to get around or resolve this issue as I cannot proceed with the stock flash unless the Fastboot connectivity is working, then that would be great
(if it helps I already have Android Studio installed with all its components)
Lucas_Stone said:
So I am currently rooted on a Motorla Nexus 6 in Android 5.1.1, I started up the Nexus Root Toolkit and when it finishes downloading stock Android 60.1 to restore my device ready for Android N it sends the adb reboot bootloader command but my device then says in the bootloader menu "Connect USB Data Cable"
Since I cannot post the image link of what the toolkit says then I will just write it below...
"FASTBOOT device was not found
STEP #1: Connect your device via USB:
- Utilize the OEM USB cable if available
- Try an alternative USB port.
STEP #2: Manually Boot your device into bootloader mode:
- Power your device down completely:
- Press and hold the volume down button, them press and hold the power button t the same time until the phone turns on. You'll see the word 'start' with an arrow around it/
STEP #3: Install drivers:
- Utilize the 'initial setup' if you not done so already.
- USB debugging is NOT required for connectivity in bootloader mode.
- Just follow the the instructions in the guide for configuring your device in bootloader mode.
- For example: if you are using driver solution #3, start on step 7.
Alternatively you may just need to recheck connection.
Press 'OK' to recheck device connectivity.
Press 'Cancel' to exit this script"
If anyone has any info on how to get around or resolve this issue as I cannot proceed with the stock flash unless the Fastboot connectivity is working, then that would be great
(if it helps I already have Android Studio installed with all its components)
Click to expand...
Click to collapse
Make sure you have develops options unlocked and usb debugging enabled.. Then unplug cord and plug it back in.
kwdan said:
Make sure you have develops options unlocked and usb debugging enabled.. Then unplug cord and plug it back in.
Click to expand...
Click to collapse
Got the same error again (I always have USB Debugging on)
Lucas_Stone said:
Got the same error again (I always have USB Debugging on)
Click to expand...
Click to collapse
Try a different port on the computer
kwdan said:
Try a different port on the computer
Click to expand...
Click to collapse
Still the same man, my Laptop has the Google Nexus ADB drivers installed but for some reason the Root Toolkit does not detect Fastboot in my phone
Lucas_Stone said:
Still the same man, my Laptop has the Google Nexus ADB drivers installed but for some reason the Root Toolkit does not detect Fastboot in my phone
Click to expand...
Click to collapse
did you install adb and fastboot onto your computer? it doesnt matter if you have the driver installed if you dont have the actual program installed onto your computer. and anyways, learn to do it right instead of using a toolkit, its very easy.
simms22 said:
did you install adb and fastboot onto your computer? it doesnt matter if you have the driver installed if you dont have the actual program installed onto your computer. and anyways, learn to do it right instead of using a toolkit, its very easy.
Click to expand...
Click to collapse
All sorted now I think lol, I will close this thread when I finish. if it fails horribly then I will let you know (p.s I use the cmd most the time it's just I use the Toolkit to download and install stock)
Lucas_Stone said:
All sorted now I think lol, I will close this thread when I finish. if it fails horribly then I will let you know (p.s I use the cmd most the time it's just I use the Toolkit to download and install stock)
Click to expand...
Click to collapse
please dont close the thread, people always have issues, maybe someone will read this thread and it will help them.
and about toolkits, i dont recommend using them, but feel free to. its just many dont take the time to learn to do it the "right" way. but if you do know it, a toolkit is alright usually.
simms22 said:
please dont close the thread, people always have issues, maybe someone will read this thread and it will help them.
and about toolkits, i dont recommend using them, but feel free to. its just many dont take the time to learn to do it the "right" way. but if you do know it, a toolkit is alright usually.
Click to expand...
Click to collapse
Okay, I will keep it open and also everything is fine now, I am now on Android N preview (had it for 5 mins and I love it)
I found out this morning that my phone had cut off during the night. When I tried to turn the phone back up it just stayed at the loading screen and does not go any further than that. I can get into Fastboot/recovery but not sure what is going on. Phone is locked as well.
I am running on Developer preview 5 and I assuming it has something to do with this. I have read up on others having issues and talk about sideloading the OTA that has resolved the issue but my computer does not even detect the device, so adb does not see the device. Feel like if I can just get my computer to detect my phone I'll be in business.
Really need some help on this one as it is starting to look like I am going to have a nice paper weight the rate its going. Thank you in advance.
cjsill9473 said:
I found out this morning that my phone had cut off during the night. When I tried to turn the phone back up it just stayed at the loading screen and does not go any further than that. I can get into Fastboot/recovery but not sure what is going on. Phone is locked as well.
I am running on Developer preview 5 and I assuming it has something to do with this. I have read up on others having issues and talk about sideloading the OTA that has resolved the issue but my computer does not even detect the device, so adb does not see the device. Feel like if I can just get my computer to detect my phone I'll be in business.
Really need some help on this one as it is starting to look like I am going to have a nice paper weight the rate its going. Thank you in advance.
Click to expand...
Click to collapse
If I understand correctly, you can get to fastboot mode. If you then plug in the usb cable, and type fastboot devices, does the computer recognize it?
Have you ever connected to the phone using your computer and either adb or fastboot? In other words, is there a high level of confidence that the drivers are setup on your computer?
That is correct, I am able to get into fastboot mode, the phone will detect a USB cable "will say transfer mode: USB connected" but when I am in command prompt on my computer and type in "adb devices" it finds nothing.
I've had experience with using adb/fastboot on my moto x 2014 but this is the first time doing this on my nexus and I am pretty sure I had never hooked up my nexus to this computer before this issue happened. So I wouldn't be surprised if it is a driver issue but I have downloaded Android sdk and gone into sdk manager to have it install google drivers. I just now now played around with Nexus Root toolkit to assist in installing drivers with the same results. I had used the tool to uninstall any drivers that could have impacted this and reinstalled with no luck.
ktmom said:
If I understand correctly, you can get to fastboot mode. If you then plug in the usb cable, and type fastboot devices, does the computer recognize it?
Have you ever connected to the phone using your computer and either adb or fastboot? In other words, is there a high level of confidence that the drivers are setup on your computer?
Click to expand...
Click to collapse
cjsill9473 said:
That is correct, I am able to get into fastboot mode, the phone will detect a USB cable "will say transfer mode: USB connected" but when I am in command prompt on my computer and type in "adb devices" it finds nothing.
I've had experience with using adb/fastboot on my moto x 2014 but this is the first time doing this on my nexus and I am pretty sure I had never hooked up my nexus to this computer before this issue happened. So I wouldn't be surprised if it is a driver issue but I have downloaded Android sdk and gone into sdk manager to have it install google drivers. I just now now played around with Nexus Root toolkit to assist in installing drivers with the same results. I had used the tool to uninstall any drivers that could have impacted this and reinstalled with no luck.
Click to expand...
Click to collapse
Do you have an otg cable? Does that work?
I do but I don't have one on me currently. I am currently at work but will be home in about 2 hours.
ktmom said:
Do you have an otg cable? Does that work?
Click to expand...
Click to collapse
cjsill9473 said:
That is correct, I am able to get into fastboot mode, the phone will detect a USB cable "will say transfer mode: USB connected" but when I am in command prompt on my computer and type in "adb devices" it finds nothing.
Click to expand...
Click to collapse
When you are in fastboot mode, and connect to your computer, you should run "fastboot devices", instead of "adb devices".
You are correct, device does show up when type in fastboot devices. Guess that is what I get when trying to do this while I am at work and haven't messed with this type of stuff in months. I really appreciate the fast response on this and my derp moment. Now to try and side load the OTA to see if I can bring my phone back to life. Looks like I just need to go into custom recovery and select "Apply Update from ADB" and hopefully I'll be in business.
jj14 said:
When you are in fastboot mode, and connect to your computer, you should run "fastboot devices", instead of "adb devices".
Click to expand...
Click to collapse
Well at this point I was able to side load the OTA DP5 build and its doing the same thing. Trying a factory reset now to see if that will make a difference but if not looks like I am going to have to go out and get me a new phone till I can get this one fixed or RMA'ed. Just stuck at the loading animation.
Edit: Factory restore finally brought it back to life. Thank you again for the quick help and assistance on this!