I'm attempting to flash android M on my nexus 6. I've installed the proper drivers from google, after checking in device manager it says the proper drivers are installed. When I enter "adb devices" into the terminal nothing shows up in the list. I've searched through forums and tried the universal adb installer which isn't compatible with Windows8x64, so I used the 15 second installer which worked but didn't change the result. Am I doing anything wrong?
Sent from my Nexus 6 using Tapatalk
semenick96 said:
I'm attempting to flash android M on my nexus 6. I've installed the proper drivers from google, after checking in device manager it says the proper drivers are installed. When I enter "adb devices" into the terminal nothing shows up in the list. I've searched through forums and tried the universal adb installer which isn't compatible with Windows8x64, so I used the 15 second installer which worked but didn't change the result. Am I doing anything wrong?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Are you using the usb cable that came with your phone? That's the only one that will allow my PC to recognize my N6.
Yes I am
Sent from my Nexus 6 using Tapatalk
I use wug's toolkit which includes easy setup for adb and has worked with both Windows 7 and Windows 10. You might try that.
Otherwise, you didn't say whether your device is recognized by the computer when you plug it in. Windows should recognize and try to install drivers for the device automatically when plugged in via USB. If it's not, there's probably something wrong with the cord you're using. If it is recognized, then it might be the drivers of you might not have debugging enabled on your phone.
Sent from my Nexus 6 using XDA Free mobile app
The computer recognizes the phone and USB debugging is enabled
Sent from my Nexus 6 using Tapatalk
Forget about adb since you don't use it for flashing anyway. Boot into the bootloader.and type "fastboot devices". That's all that matters. Check drivers and device manager in bootloader too.
Uninstall the device if you have to and set up as per my thread.. Nexus 6 general > sticky roll-up thread > adb and fastboot.
danarama said:
Forget about adb since you don't use it for flashing anyway. Boot into the bootloader.and type "fastboot devices". That's all that matters. Check drivers and device manager in bootloader too.
Uninstall the device if you have to and set up as per my thread.. Nexus 6 general > sticky roll-up thread > adb and fastboot.
Click to expand...
Click to collapse
I followed your guide and restarted my windows 8 computer accordingly. When I open the command window and type "fastboot devices" it says that is not recognized as an internal or external command, operable program or batch file
Sent from my Nexus 6 using Tapatalk
semenick96 said:
I followed your guide and restarted my windows 8 computer accordingly. When I open the command window and type "fastboot devices" it says that is not recognized as an internal or external command, operable program or batch file
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
That means you didn't do the environment variables correctly or it didn't take after the reboot.
Confirm the location you have fastboot in is the location in environment variables.
danarama said:
That means you didn't do the environment variables correctly or it didn't take after the reboot.
Confirm the location you have fastboot in is the location in environment variables.
Click to expand...
Click to collapse
How do I check the location of fastboot?
Sent from my Nexus 6 using Tapatalk
semenick96 said:
How do I check the location of fastboot?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
What part of my thread did you follow? How did you put fastboot on your.computer?
danarama said:
What part of my thread did you follow? How did you put fastboot on your.computer?
Click to expand...
Click to collapse
Is that the platform-tools? I'm sorry if these are stupid questions! I'm still learning aha
Sent from my Nexus 6 using Tapatalk
semenick96 said:
Is that the platform-tools? I'm sorry if these are stupid questions! I'm still learning aha
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Yes, if you followed my thread and installed the sdk, the fastboot.exe should be in there. The full path is mentioned in my thread. Go.and check that and if it is, go onto the next step about environment variables.. Remember, the variable must be the location of fastboot and MUST start with ;
To be honest, I cheat and simply drop adb and fastboot into c:\windows\system32 as that is already and environment variable.
danarama said:
Yes, if you followed my thread and installed the sdk, the fastboot.exe should be in there. The full path is mentioned in my thread. Go.and check that and if it is, go onto the next step about environment variables.. Remember, the variable must be the location of fastboot and MUST start with ;
To be honest, I cheat and simply drop adb and fastboot into c:\windows\system32 as that is already and environment variable.
Click to expand...
Click to collapse
I redid all of the steps, but my computer is taking a long time to do the restart. Is that normal?
Sent from my Nexus 6 using Tapatalk
semenick96 said:
I redid all of the steps, but my computer is taking a long time to do the restart. Is that normal?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
No.
danarama said:
No.
Click to expand...
Click to collapse
Alright, I'll look into it. Thanks for all the help!
Sent from my Nexus 6 using Tapatalk
Related
Not working got to made another one when i be back home.
I have a problem with the computer at work all my zip file are no more working.
I don't know why.
I will make another zip soon
Re: [delete this thread]Flashable zip of Bootloader 4.18 for grouper & tilapia
Yeah works well!
Edit: thought it worked. Stayed on 4.13
Sent from my Nexus 7 using xda premium
[email protected]_OC said:
Not working got to made another one when i be back home.
I have a problem with the computer at work all my zip file are no more working.
I don't know why.
I will make another zip soon
Click to expand...
Click to collapse
Thanks man!
Gave up on fastboot. Dunno why cant get it running!
I tried using fastboot but cant get it to work.
1) Create a folder called fastboot, copy the 4 files + bootloader img into it, and move the folder into C drive.
2) run cmd
3) enter cd C:\fastboot\
4) adb devices. check correct.
5) adb reboot-bootloader
6) fastboot devices. check correct.
7) fastboot flash bootloader bootloader-grouper-4.18.img
8) nth happened.
what went wrong?
o0boiboi0o said:
Thanks man!
Gave up on fastboot. Dunno why cant get it running!
I tried using fastboot but cant get it to work.
1) Create a folder called fastboot, copy the 4 files + bootloader img into it, and move the folder into C drive.
2) run cmd
3) enter cd C:\fastboot\
4) adb devices. check correct.
5) adb reboot-bootloader
6) fastboot devices. check correct.
7) fastboot flash bootloader bootloader-grouper-4.18.img
8) nth happened.
what went wrong?
Click to expand...
Click to collapse
I think you forgot unlock bootloader typing
fastboot oem unlock
Enviado de meu Nexus 7 usando o Tapatalk 2
eric-filth said:
I think you forgot unlock bootloader typing
fastboot oem unlock
Enviado de meu Nexus 7 usando o Tapatalk 2
Click to expand...
Click to collapse
oh! coz i saw there stated unlocked.
is it a must to type that?
o0boiboi0o said:
oh! coz i saw there stated unlocked.
is it a must to type that?
Click to expand...
Click to collapse
No, if are unlocked you dont need
Enviado de meu Nexus 7 usando o Tapatalk 2
o0boiboi0o said:
Thanks man!
Gave up on fastboot. Dunno why cant get it running!
I tried using fastboot but cant get it to work.
1) Create a folder called fastboot, copy the 4 files + bootloader img into it, and move the folder into C drive.
2) run cmd
3) enter cd C:\fastboot\
4) adb devices. check correct.
5) adb reboot-bootloader
6) fastboot devices. check correct.
7) fastboot flash bootloader bootloader-grouper-4.18.img
8) nth happened.
what went wrong?
Click to expand...
Click to collapse
This worked for me fine. How adb devices is working for you? I think when you are in fastboot adb doesnt work.......Maybe i am wrong.
nickporwal said:
This worked for me fine. How adb devices is working for you? I think when you are in fastboot adb doesnt work.......Maybe i am wrong.
Click to expand...
Click to collapse
I think you hit sth!
when tablet is on, adb devices give me return (serial number+device). But, when i adb reboot-bootloader, adb devices give me nth, instead fastboot devices give me return.
When you type in adb devices it returns your device but you'll notice that it says offline next to it.
Therefore you can't send any adb commands to it.
It's a new security measure apparently, the solutions can be found in the forums.
Sent from my Incredible S using xda app-developers app
where are the zips
o0boiboi0o said:
Thanks man!
Gave up on fastboot. Dunno why cant get it running!
I tried using fastboot but cant get it to work.
1) Create a folder called fastboot, copy the 4 files + bootloader img into it, and move the folder into C drive.
2) run cmd
3) enter cd C:\fastboot\
4) adb devices. check correct.
5) adb reboot-bootloader
6) fastboot devices. check correct.
7) fastboot flash bootloader bootloader-grouper-4.18.img
8) nth happened.
what went wrong?
Click to expand...
Click to collapse
You must make sure to put the files you are flashing in the same folder that fastboot is located, and also to cd to that folder in command prompt.
What error were you getting exactly?
[email protected]_OC said:
Not working got to made another one when i be back home.
I have a problem with the computer at work all my zip file are no more working.
I don't know why.
I will make another zip soon
Click to expand...
Click to collapse
I too tried to create a flashable zip from the OTA, but it doesn't stick. I had to use fastboot
Sent from my Nexus 7
o0boiboi0o said:
I think you hit sth!
when tablet is on, adb devices give me return (serial number+device). But, when i adb reboot-bootloader, adb devices give me nth, instead fastboot devices give me return.
Click to expand...
Click to collapse
I am experiencing the same problem. Guess I'll have to wait for the zip version...
I used this guide for the adb: http://forum.xda-developers.com/showthread.php?t=1830108
Adinaky said:
I am experiencing the same problem. Guess I'll have to wait for the zip version...
I used this guide for the adb: http://forum.xda-developers.com/showthread.php?t=1830108
Click to expand...
Click to collapse
I am in the same boat as well. I am having weird adb issues that won't allow me to fastboot either. I am gonna reinstall SDK and see if i can adb working.
Sent from my Nexus 7 using xda premium
Tone_Capone said:
You must make sure to put the files you are flashing in the same folder that fastboot is located, and also to cd to that folder in command prompt.
What error were you getting exactly?
Click to expand...
Click to collapse
Dont think there is any error. It kept stating waiting for device but nth happened on my device side. Seems like the command get thru but nth is done.
Oo more and more ppl are having the same prob as me! :victory: Lol
Lets wait for TS's flashable file!
http://forum.xda-developers.com/showpost.php?p=37989110&postcount=1650
waiting for a linux version, i hate windows
If you don't have a working adb, you should try this guide: http://www.teamandroid.com/2012/07/30/how-to-set-up-adb-fastboot-with-android-sdk/ , it's the only one that worked for me.
Sent from my Nexus 7 using xda premium
weird.
I tried fastboot again. Ok, running smoothly at first, but in the end, i got this error:
writing 'bootloader'...
FAILED <status read failed <too many links>>
So i closed the cmd (bcoz when i tried fastboot devices, it shows ????? devices. Then when i forced closed my device and reboot into bootloader, it showed 4.18 as the bootloader version but under SIGNING, it is not defined yet.
Is this correct?
o0boiboi0o said:
weird.
I tried fastboot again. Ok, running smoothly at first, but in the end, i got this error:
writing 'bootloader'...
FAILED <status read failed <too many links>>
So i closed the cmd (bcoz when i tried fastboot devices, it shows ????? devices. Then when i forced closed my device and reboot into bootloader, it showed 4.18 as the bootloader version but under SIGNING, it is not defined yet.
Is this correct?
Click to expand...
Click to collapse
This happened to me when my adb was not working properly, it showed 4.18, but I fixed the adb and installed the bootloader again, just to be sure.
Sent from my Nexus 7 using xda premium
Anyone an idea, why flashing the bootloader does not work with the zip files?
I am somewhere in nowhere and can not fastboot, have only my Nexus 3G with me. Its on 4.2.2 but bootloader still 4.13. Used this ROM:
[ROM][Factory Image][4.2.2] Nakasig -::- Odex, Deodex, Rooted -::- teshxx (02/14/13)
to update. Worked apart of bootloader and radio.
I had mutiple issues getting adb to work in adb sideload. It worked while in the OS but not in recovery after selecting sideload. This is how I fixed it!
You must first have SDK installed and know the basics of adb and fastboot. If you do not know how to install SDK or how to use terminal emulator or command prompt (cmd) to get to the platform tools folder you must do all that first. You must also have developers tools and USB debugging on.
See here if you have no idea what I am talking about: http://forum.xda-developers.com/showthread.php?t=2141817
Go to stock recovery and click adb sidload
In Win7 go to:
1. Go to Start
2. Right Click Computer
3. Click Manage
4. Click Device manager
5. You will see the nexus 5 with a yellow !
6. Right Click on nexus 5 and click update driver
7. then choose to browse for driver
Windows 8? See here:
gaga111 said:
http://www.theandroidsoul.com/nexus-5-driver-adb-fastboot-installation-guide/
this helped me
i used the naked driver and disabled the driver signature enforcement (only for windows 8 and 8.1)
Click to expand...
Click to collapse
8. then choose the second option search for driver by device
zallaaa said:
I believe that's the same "wall" I've found.
Select "Android Phone" and next, then you'll find a list of all the compatible "Android ADB Interfaces". I used "Android ADB Interface ver. 8.0.0.0" and it worked, thank The Greek!
Click to expand...
Click to collapse
9. click on Android ADB Interface
10. Should install driver succesfully.... check adb devices it will show device id in sideload mode
Hope this helps the people who can't function without an ota
Hit thanks if this helped:thumbup:
Step 8.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Android The Greek said:
I had mutiple issues getting adb to work in adb sideload. It worked while in the OS but not in recovery after selecting sideload. This is how I fixed it!
Go to stock recovery and click adb sidload
In Win7 go to:
1. Go to Start
2. Right Click Computer
3. Click Manage
4. Click Device manager
5. You will see the nexus 5 with a yellow !
6. Right Click on nexus 5 and click update driver
7. then choose to browse for driver
8. then choose the second option search for driver by device
9. click on Android ADB Interface
10. Should install driver succesfully.... check adb devices it will show device id in sideload mode
If someone can add screen shots of their computer while following these steps it would be helpful. I can't seem to replicate the issue now that its working on my PC
Click to expand...
Click to collapse
When i click step 8, no option for Android ADB Interface is on the list?
Can you post a screen shot of what the options are?
In the os not recovery does you device show up in adb?
Sent from my Nexus 5 using XDA Premium 4 mobile app
jonyid said:
When i click step 8, no option for Android ADB Interface is on the list?
Click to expand...
Click to collapse
I believe that's the same "wall" I've found.
Select "Android Phone" and next, then you'll find a list of all the compatible "Android ADB Interfaces". I used "Android ADB Interface ver. 8.0.0.0" and it worked, thank The Greek!
Android The Greek said:
Can you post a screen shot of what the options are?
In the os not recovery does you device show up in adb?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
when not in recovery yes it appears in adb and android device appears. When i got through the process of updating the OTA i get up to:
5) Using the command prompt type: 'adb sideload update.zip' The file will load and the update will begin.
and then it appears device not found
jonyid said:
when not in recovery yes it appears in adb and android device appears. When i got through the process of updating the OTA i get up to:
5) Using the command prompt type: 'adb sideload update.zip' The file will load and the update will begin.
and then it appears device not found
Click to expand...
Click to collapse
When device is in adb sideload type in you command prompt adb devices. Do you see anything? Try Ctrl alt delete kill adb.exe in process the retry if adb sees the device I'd in adb side load mode then your good. If not you need to get the drivers to work by following step 8. If you do not see that option add a screen shot of your options.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Android The Greek said:
When device is in adb sideload type in you command prompt adb devices. Do you see anything? Try Ctrl alt delete kill adb.exe in process the retry if adb sees the device I'd in adb side load mode then your good. If not you need to get the drivers to work by following step 8. If you do not see that option add a screen shot of your options.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm now getting the error message (i uninstalled and re-installed the drivers) "adb cannot run as root in production builds" at stage 3:
3) Open the command prompt from the directory above on your PC and type the command: 'adb reboot recovery'
http://www.theandroidsoul.com/nexus-5-driver-adb-fastboot-installation-guide/
this helped me
i used the naked driver and disabled the driver signature enforcement (only for windows 8 and 8.1)
jonyid said:
I'm now getting the error message (i uninstalled and re-installed the drivers) "adb cannot run as root in production builds" at stage 3:
3) Open the command prompt from the directory above on your PC and type the command: 'adb reboot recovery'
Click to expand...
Click to collapse
Are you stock? Why are you using adb recovery? If adb works in the os but when you manually boot into recovery mode adb sideload and it says failed to install the drivers my method will work.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Android The Greek said:
Are you stock? Why are you using adb recovery? If adb works in the os but when you manually boot into recovery mode adb sideload and it says failed to install the drivers my method will work.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm 100% stock. This is the guide i was advised to use:
Section A: adb sideload
NOTE:Make sure you have the latest version of adb. It seems people are having issues with older versions. Its attached at the bottom
1) Download the OTA.zip on your PC, rename the file update.zip, then place file in the same directory as adb.
2) Make sure you have USB Debugging checking in the Developer Options, then connect your phone.
3) Open the command prompt from the directory above on your PC and type the command: 'adb reboot recovery'
4) When in recovery, you’ll see an android laying down. Press power then immediately press volume up and release. The menu will appear. Select “apply update from adb”
5) Using the command prompt type: 'adb sideload update.zip' The file will load and the update will begin.
6) When completed, select reboot.
I've installed the google drivers and when plugged in it recognises both the phone (no yellow ! there) and also an 'android device - android composite ADB interface" option. Both say that the drivers are up-to-date.
jonyid said:
I'm 100% stock. This is the guide i was advised to use:
Section A: adb sideload
NOTE:Make sure you have the latest version of adb. It seems people are having issues with older versions. Its attached at the bottom
1) Download the OTA.zip on your PC, rename the file update.zip, then place file in the same directory as adb.
2) Make sure you have USB Debugging checking in the Developer Options, then connect your phone.
3) Open the command prompt from the directory above on your PC and type the command: 'adb reboot recovery'
4) When in recovery, you’ll see an android laying down. Press power then immediately press volume up and release. The menu will appear. Select “apply update from adb”
5) Using the command prompt type: 'adb sideload update.zip' The file will load and the update will begin.
6) When completed, select reboot.
I've installed the google drivers and when plugged in it recognises both the phone (no yellow ! there) and also an 'android device - android composite ADB interface" option. Both say that the drivers are up-to-date.
Click to expand...
Click to collapse
In recovery adb sideload do a adb devices in command prompt. What does it say
Sent from my Nexus 5 using XDA Premium 4 mobile app
Android The Greek said:
In recovery adb sideload do a adb devices in command prompt. What does it say
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
you mean at stage 3? it says:
List of devices attached
03b911s908eb03ff device
jonyid said:
you mean at stage 3? it says:
List of devices attached
03b911s908eb03ff device
Click to expand...
Click to collapse
Why not manually put your device in adb sideload
Sent from my Nexus 5 using XDA Premium 4 mobile app
Android The Greek said:
Why not manually put your device in adb sideload
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
How do i do this? Will it then allow me to install pretty quickly?
jonyid said:
How do i do this? Will it then allow me to install pretty quickly?
Click to expand...
Click to collapse
Pm me your number
Sent from my Nexus 5 using XDA Premium 4 mobile app
Android The Greek said:
Pm me your number
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
i'm in the UK that's the problem
I had to follow the instructions that were listed here to get my laptop to see my N5 in recovery mode. Worked like a charm afterward.
http://stackoverflow.com/questions/15721778/adb-no-devices-found
Sephiroth_Darko said:
I had to follow the instructions that were listed here to get my laptop to see my N5 in recovery mode. Worked like a charm afterward.
http://stackoverflow.com/questions/15721778/adb-no-devices-found
Click to expand...
Click to collapse
I'm on my work PC and not 100% about doing this
jonyid said:
I'm on my work PC and not 100% about doing this
Click to expand...
Click to collapse
I did it on my home laptop it and it worked fine. But I understand how you could be a bit hesitate to do this on a work machine. Best of luck!
My Kindle Fire HD 7 is bricked... When I put the fastboot cable in it goes into fastboot mode. However it is not being detected on my PC and I have the ADB drives installed and I am using the KFHD SRT 1.3.5.. When I select option 1 it just says < waiting for device > FOREVER... I need help ASAP!
AidenOwns said:
My Kindle Fire HD 7 is bricked... When I put the fastboot cable in it goes into fastboot mode. However it is not being detected on my PC and I have the ADB drives installed and I am using the KFHD SRT 1.3.5.. When I select option 1 it just says < waiting for device > FOREVER... I need help ASAP!
Click to expand...
Click to collapse
Try using fastboot -i 0x1949 getvar product and then plug it in. Otherwise use Ubuntu
SafinWasi said:
Try using fastboot -i 0x1949 getvar product and then plug it in. Otherwise use Ubuntu
Click to expand...
Click to collapse
Do I use it on a regular command prompt?
SafinWasi said:
Try using fastboot -i 0x1949 getvar product and then plug it in. Otherwise use Ubuntu
Click to expand...
Click to collapse
Nvm I tried it on command prompt and it said unknown command (I did it at the adb file place) And when I did it KFHD SRT it just closes the command prompt... Even tho it closes it I still tried and I didnt work.. Can you tell me how to do it on ubuntu
AidenOwns said:
Nvm I tried it on command prompt and it said unknown command (I did it at the adb file place) And when I did it KFHD SRT it just closes the command prompt... Even tho it closes it I still tried and I didnt work.. Can you tell me how to do it on ubuntu
Click to expand...
Click to collapse
I meant boot into an Ubuntu live CD,try the command. And you should have the android SDK installed
Sent from my device running CyanogenMod 11
AidenOwns said:
My Kindle Fire HD 7 is bricked... When I put the fastboot cable in it goes into fastboot mode. However it is not being detected on my PC and I have the ADB drives installed and I am using the KFHD SRT 1.3.5.. When I select option 1 it just says < waiting for device > FOREVER... I need help ASAP!
Click to expand...
Click to collapse
Hi, please wait for at least 15 minutes. It is quite slow so just leave the kindle for a while.
SafinWasi said:
I meant boot into an Ubuntu live CD,try the command. And you should have the android SDK installed
Sent from my device running CyanogenMod 11
Click to expand...
Click to collapse
Could you give me like a full tutorial? I do not know how to boot into ubuntu..
AidenOwns said:
Could you give me like a full tutorial? I do not know how to boot into ubuntu..
Click to expand...
Click to collapse
It should not take 15 minutes for your device to be recognized. Are you running Ubuntu? Or are you running Windows 7? Or what's your OS? Your using a fastboot cord which uses fastboot commands and requires the .exe files in inside SRT to run unless you download sdk and set the tools folders in your path.
Make sure you're in fastboot.
Now open a command prompt (you must be using the admin profile of the computer) type
"fastboot -i 0x1949 getvar product"
In a few seconds you should see you device on the computer screen. If not then check your drivers.
If your drivers are not being recognized, see this post http://forum.xda-developers.com/showpost.php?p=44446906&postcount=9
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
LinearEquation said:
It should not take 15 minutes for your device to be recognized. Are you running Ubuntu? Or are you running Windows 7? Or what's your OS? Your using a fastboot cord which uses fastboot commands and requires the .exe files in inside SRT to run unless you download sdk and set the tools folders in your path.
Make sure you're in fastboot.
Now open a command prompt (you must be using the admin profile of the computer) type
"fastboot -i 0x1949 getvar product"
In a few seconds you should see you device on the computer screen. If not then check your drivers.
If your drivers are not being recognized, see this post http://forum.xda-developers.com/showpost.php?p=44446906&postcount=9
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
Click to expand...
Click to collapse
Windows 8.1 and I dont know anything about ubuntu and when I plug it in it says USB device not reginized. I already tried the command prompt and I didnt work also...
AidenOwns said:
Windows 8.1 and I dont know anything about ubuntu and when I plug it in it says USB device not reginized. I already tried the command prompt and I didnt work also...
Click to expand...
Click to collapse
Disable your Windows driver security enforcement first http://www.isunshare.com/windows-8/...gnature-enforcement-in-windows-8-and-8.1.html then proceed to use the drivers in stunts signature.
Edit: Here are the drivers http://forum.xda-developers.com/showpost.php?p=44446906&postcount=9
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
LinearEquation said:
Disable your Windows driver security enforcement first http://www.isunshare.com/windows-8/...gnature-enforcement-in-windows-8-and-8.1.html then proceed to use the drivers in stunts signature.
Edit: Here are the drivers http://forum.xda-developers.com/showpost.php?p=44446906&postcount=9
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
Click to expand...
Click to collapse
I disabled it and Downloaded the usb driver file... Im not that great with files so could you tell me how to install the drivers at there is no .exe file??
AidenOwns said:
I disabled it and Downloaded the usb driver file... Im not that great with files so could you tell me how to install the drivers at there is no .exe file??
Click to expand...
Click to collapse
The drivers are USB drivers that are in my post above. You don't want .exe for this install. So simply install the drivers in the device manager so your tablet will be recognized. Then move forward from there.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
LinearEquation said:
The drivers are USB drivers that are in my post above. You don't want .exe for this install. So simply install the drivers in the device manager so your tablet will be recognized. Then move forward from there.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
Click to expand...
Click to collapse
Sorry if I keep asking questions but how do I install it in the device manager??
LinearEquation said:
The drivers are USB drivers that are in my post above. You don't want .exe for this install. So simply install the drivers in the device manager so your tablet will be recognized. Then move forward from there.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
Click to expand...
Click to collapse
Im sorry I dont know more about this stuff.. But how do I install it in the device manager could you give me like a tutorial or something?
AidenOwns said:
Im sorry I dont know more about this stuff.. But how do I install it in the device manager could you give me like a tutorial or something?
Click to expand...
Click to collapse
http://pcsupport.about.com/od/windows-8/a/update-drivers-windows-8.htm
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
LinearEquation said:
http://pcsupport.about.com/od/windows-8/a/update-drivers-windows-8.htm
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
Click to expand...
Click to collapse
Which device thing do I update and which file do I select?
AidenOwns said:
Which device thing do I update and which file do I select?
Click to expand...
Click to collapse
With your tablet hooked to the PC you'll look in the device manager for a device with a yellow triangle by it. Right click on it and manually install the drivers. You will point to the folder containing all the items in the screens not, not just a single file in the folder.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
LinearEquation said:
With your tablet hooked to the PC you'll look in the device manager for a device with a yellow triangle by it. Right click on it and manually install the drivers. You will point to the folder containing all the items in the screens not, not just a single file in the folder.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
Click to expand...
Click to collapse
This happens
AidenOwns said:
This happens
Click to expand...
Click to collapse
You're getting close. Did you verify that Window driver security enforcement is disabled? Also you must install manually, don't click the option for Windows to find and install. Make sure you're actually logged into the admin profile of your computer.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
LinearEquation said:
You're getting close. Did you verify that Window driver security enforcement is disabled? Also you must install manually, don't click the option for Windows to find and install. Make sure you're actually logged into the admin profile of your computer.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
Click to expand...
Click to collapse
I disabled it again, went to the device thingy, went to the usb driver path tried the usb driver file and it did the same thing....
first, i have already unlocked my bootloader using windblowz on a boot camp partition of my mac. BUT, since android is a unix-like os, and osx is a unix-like os, FOR MY OWN EDUCATION, i want to be able to use the osx terminal to do this stuff to my n6.
so here's what i tried, and none of it works... as in, none of it even results in any like link between my phone and my osx computer.
1) i watched this youtube video from droidmodderX, and followed it to the letter:
https://www.youtube.com/watch?v=aUkcWlknFsE
from the time he plugs his n6 into his mac, NOTHING he says will happen, actually happened. it was as if i had plugged the phone into nothing. He says NOTHING about installing the android SDK for osx in his video. sooo....
2) next, i install the android SDK for osx, thinking droidmodderX was just careless in his video, and forgot to mention that you need to do this. NOTHING. i open the terminal and run the various fastboot commands from the root directory... NOTHING. using the terminal, i change over to the directory where i actually put the SDK, and then run the fastboot/adb commands from terminal again, and NOTHING. I tried this with the phone in fastboot, and with the phone not in fastboot, and NOTHING.
so how do you get osx to talk to this phone with fastboot/adb commands using the terminal?
fwiw, android file transfer works fine in the gui, so i know the physical connecction is good.
also, fwiw, i did use the search function and someone asked a similar question about his n5 about a year ago... and got no answer. not a single one.
-peter
If you run "./adb devices" without quotes does it see the phone at all? Make sure you have the most up to date SDK for OS X and also make sure you update the platform-tools in the SDK manager.
Check this thread out, might help a bit.
EDIT: Try running the commands as root/sudo.
I used this method on my MacBook Air to root my device without any issues. Make sure that you are in the correct folder when executing the commands. The first time it should ask you for your password. Also make sure that you have USB debugging enabled on your phone and that you are in the bootloader. You can also try to download Android File Transfer (google it) and see if it works with your phone. Hope that this helps.
You're aware that the bootloader on the Nexus 6 can be unlocked simply by toggling "Enable OEM Unlock" under Developer Settings, right?
With that said, I agree that it is smart to keep up with proper ADB/Fastboot commands as those are the most sure fire way to get you out of a pinch.
I have had absolutely no issues using Terminal to perform Fastboot commands on my Nexus 6 using my Mac with OSX Yosemite. As long as you get it setup correctly you should have no issues.
I just dug up the detailed instructions I used to get my Mac setup for this. Start from scratch, follow these instructions and you should be good to go:
http://forum.xda-developers.com/showthread.php?t=1917237
geebee1932 said:
I used this method on my MacBook Air to root my device without any issues.
Click to expand...
Click to collapse
what method? can you be more specific? did you mean to put in a link describing the "method"?
geebee1932 said:
Make sure that you are in the correct folder when executing the commands.
Click to expand...
Click to collapse
I ran all the fastboot commands, to the letter, from the youtube video, from the terminal, in the folder where i had the SDK. nothing....
geebee1932 said:
The first time it should ask you for your password.
Click to expand...
Click to collapse
It didn't.
geebee1932 said:
Also make sure that you have USB debugging enabled on your phone and that you are in the bootloader.
Click to expand...
Click to collapse
I did.
geebee1932 said:
You can also try to download Android File Transfer (google it) and see if it works with your phone. Hope that this helps.
Click to expand...
Click to collapse
As I said in my original post, I already have Android File Transfer, no need to google it. It works great. Had it for years.
I made some headway when I started using ./adb before each command. It sees my device now and when i ran ./adb help, it put out a list of commands and switches in the terminal, that I'm starting to play with. thanks for the ./adb clue. that was a biggie now using ./adb i can reboot and boot into bootloader. but for example "./adb fastboot oem lock", (without the quotes), does nothing. (i used "oem lock" as a test, because the bootloader is already unlocked)
-peter
geebee1932 said:
I just dug up the detailed instructions I used to get my Mac setup for this. Start from scratch, follow these instructions and you should be good to go:
http://forum.xda-developers.com/showthread.php?t=1917237
Click to expand...
Click to collapse
thanks mate. that's the second reference to that link. it must be good
and geebee, sorry i sounded so douchey. i know you're trying to help. i was frustrated.
-peter
pcrussell50 said:
thanks mate. that's the second reference to that link. it must be good
and geebee, sorry i sounded so douchey. i know you're trying to help. i was frustrated.
-peter
Click to expand...
Click to collapse
No worries at all - I was frustrated myself until I found the YouTube video. I think after ./ you need a space before you use the command line. What I did was put the CF auto-root folder (unzipped) on my desktop. I renamed the folder CF to make it easy. I opened the folder and doubled clicked on the Mac file. It should open and say just press enter - it will not work. Keep the folder open and open up the terminal. Here is what I had to do.
Put the phone is download mode with "Start" appearing - then plug into computer. (make sure debugging on)
cd /Users/mycomputername/desktop/CF - I needed a space after cd
paste and copy the 3 sudo commands (with the sudo) out of the CF folder one at a time - pressing enter after each.
The first enter - you should be asked for your password.
Mike
Going well now guys thanks. I like having two unix-like devices (osx computer and android handset), talking without needing drivers.
-peter
sn0warmy said:
You're aware that the bootloader on the Nexus 6 can be unlocked simply by toggling "Enable OEM Unlock" under Developer Settings, right?
With that said, I agree that it is smart to keep up with proper ADB/Fastboot commands as those are the most sure fire way to get you out of a pinch.
I have had absolutely no issues using Terminal to perform Fastboot commands on my Nexus 6 using my Mac with OSX Yosemite. As long as you get it setup correctly you should have no issues.
I just dug up the detailed instructions I used to get my Mac setup for this. Start from scratch, follow these instructions and you should be good to go:
http://forum.xda-developers.com/showthread.php?t=1917237
Click to expand...
Click to collapse
Hello everyone,
I'm in the same boat, except my device won't show up under devices in transmission after the "./adb devices" command.
Got a Nexus 6, 2009 Macbook running OSX Mavericks. I followed http://forum.xda-developers.com/showthread.php?t=1917237 to a T, but no luck. Android File Transfer works just fine. Usb debugging and oem unlock is checked on my phone, I restarted both phone and computer. Any advice/guidance/direction would be greatly appreciated, thanks!
Hello, im using O+ 3 and just installed the Oxygen 3.2.2 OS
I wanna root it but got problem because my ADB says unauthorized
Ive already tried to dig some similar case and possible answers thru the internet but none of them work for me
Ive tried to enable disable the debug permission
I also already make sure my ADB is the latest one.
Also already try to delete the 'adb_key' files from my PC (im using windows 7 64bit)
The problem is most user which has similar problem with me got the 'authorized debug prompt' popped up again on their phone, but its not working on my phone.
It appear only one time at the very first time i connect it to my phone, but i accidentaly click 'cancel' on that prompt
But after that it never re-appeared again.
Can someone kindly help me? Thanks a lot
Install the Android SDK or install the OnePlus 3 drivers
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
speedyjay said:
Install the Android SDK or install the OnePlus 3 drivers
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
Click to expand...
Click to collapse
What does the Android SDK do mate?
I never used it before, so would be great if u can give me some hints
Thanks
toughkid said:
Hello, im using O+ 3 and just installed the Oxygen 3.2.2 OS
I wanna root it but got problem because my ADB says unauthorized
Ive already tried to dig some similar case and possible answers thru the internet but none of them work for me
Ive tried to enable disable the debug permission
I also already make sure my ADB is the latest one.
Also already try to delete the 'adb_key' files from my PC (im using windows 7 64bit)
The problem is most user which has similar problem with me got the 'authorized debug prompt' popped up again on their phone, but its not working on my phone.
It appear only one time at the very first time i connect it to my phone, but i accidentaly click 'cancel' on that prompt
But after that it never re-appeared again.
Can someone kindly help me? Thanks a lot
Click to expand...
Click to collapse
Make sure debugging is clicked on under developer options in the main menu. Then disconnect the phone from the pc and reboot the pc. Reconnect the phone after it reboots and hope that you get the adb prompt on the phone again.
android sdk have the latest tools including latest ADB. There is ADB standalone install, that means that if you tell us that you have the latest ADB, that only mean that someone extracted the ADB and lastest fastboot and did a repack and in the end it's not an official repack.
but "disable the debug permission" reset all the recorded device for debug so you should have another prompt.
If in the end you don't have another prompt, verify you adb version by installing the lastest android SDK, uninstall and reinstall the oneplus drivers.
Then if no prompt there is 2 choices :
- wipe the phone, it will reset the prompt for sure, 100%
- use another computer (well you have to have another computer).
I have a computer at home where this happened and I have never been able to straighten it out...tried everything.
Sent from my ONEPLUS A3000 using XDA-Developers mobile app
tdamocles said:
Make sure debugging is clicked on under developer options in the main menu. Then disconnect the phone from the pc and reboot the pc. Reconnect the phone after it reboots and hope that you get the adb prompt on the phone again.
Click to expand...
Click to collapse
Le_Zouave said:
android sdk have the latest tools including latest ADB. There is ADB standalone install, that means that if you tell us that you have the latest ADB, that only mean that someone extracted the ADB and lastest fastboot and did a repack and in the end it's not an official repack.
but "disable the debug permission" reset all the recorded device for debug so you should have another prompt.
If in the end you don't have another prompt, verify you adb version by installing the lastest android SDK, uninstall and reinstall the oneplus drivers.
Then if no prompt there is 2 choices :
- wipe the phone, it will reset the prompt for sure, 100%
- use another computer (well you have to have another computer).
Click to expand...
Click to collapse
Hello sir, i've been trying all of this method, include the wipe the phone (except using another computer) but still no prompt re-appear. Another advice would be greatly appreciated.
Thanks
joho5 said:
I have a computer at home where this happened and I have never been able to straighten it out...tried everything.
Sent from my ONEPLUS A3000 using XDA-Developers mobile app
Click to expand...
Click to collapse
Then how's in the end it goes mate? Do you root your phone? I just wanna root it, if u got any other way except the adb that would be great tho
toughkid said:
Then how's in the end it goes mate? Do you root your phone? I just wanna root it, if u got any other way except the adb that would be great tho
Click to expand...
Click to collapse
Have you checked all of your USB ports? I know in the past (with other phones), problems arise if you're not using a direct USB port (one soldered into your MoBo).
toughkid said:
Hello, im using O+ 3 and just installed the Oxygen 3.2.2 OS
I wanna root it but got problem because my ADB says unauthorized
Ive already tried to dig some similar case and possible answers thru the internet but none of them work for me
Ive tried to enable disable the debug permission
I also already make sure my ADB is the latest one.
Also already try to delete the 'adb_key' files from my PC (im using windows 7 64bit)
The problem is most user which has similar problem with me got the 'authorized debug prompt' popped up again on their phone, but its not working on my phone.
It appear only one time at the very first time i connect it to my phone, but i accidentaly click 'cancel' on that prompt
But after that it never re-appeared again.
Can someone kindly help me? Thanks a lot
Click to expand...
Click to collapse
Go to Control Panel > Hardware and Sound > Device Manager > expand Universal Serial Bus controllers. Now connect your phone. You'll now see USB Mass Storage Device. Right click on it. Select Properties, then go to Details. In the Details section, under Property, select Hardware ids. You'll then see the device id. It will be shown something like this: USB\VID_2A70&PID_9011&MI_01. From this you have to take the 2A70 code ~ the code between the first _ and &. Now go to desktop and create a new text document and copy paste this using your device id as shown:
Code:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x2A70
Now open the Save As menu. In Save As type select All Files. Save the file as adb_usb.ini
Copy this .ini file from desktop and paste it in C:\Users\YourPCName\.android
Disconnect your phone, reboot your pc. Now with USB Debugging turned on, connect your phone to your pc, you'll surely get the permission thingy popup in your phone.
For completion:
If you DO NOT have access to your phone for any reason but still want to use ADB you can simply boot your phone into TWRP and follow these steps.
Windows:
1. Open %userprofile%\.android
2. Copy "adbkey.pub" to your phone (adb push %userprofile%\.android\adbkey.pub /sdcard/adb_keys)
3. Switch to your phone.
4. Go to Advanced > Open Terminal
5. Type in "stop adbd"
6. Move "adb_keys" from /sdcard to /data/misc/adb (mv /sdcard/adb_keys /data/misc/adb/adb_keys)
7. Type in "start adbd"
8. Switch to computer
9. Type "adb shell setprop persist.service.adb.enable 1"
10. Type "adb shell setprop persist.sys.usb.config mtp,adb"
11. Reboot your phone - DONE
Linux / Maybe Mac:
Same steps, but use "~/" instead of "%userprofile%"
Please note:
You may have to repeat the steps 1-7 after boot when still not having permissions so it makes sense to use cp (copy) instead of mv (move) and only repeat steps 5-7.
Edit: Please also check if your drivers are all installed and enabled.
Sent from my OnePlus 2 using XDA Labs
?k