Can anyone help me getting ADB to work for this device. I can get it with every other phone but this one. I have the OnePlus drivers installed but when I type the Command "ADB Devices" The phone isn't listed.
Have you made sure your adb is up to date? Have you tried a different cable or a different port? Also, did you try to see if fastboot detected the device while in the bootloader?
Just trying to get more information so people can help you troubleshoot.
Milly7 said:
Have you made sure your adb is up to date? Have you tried a different cable or a different port? Also, did you try to see if fastboot detected the device while in the bootloader?
Just trying to get more information so people can help you troubleshoot.
Click to expand...
Click to collapse
So I was able to unlock the bootloader while connected. And my ADB is up to date as far as I know. I got it to work with my other devices. I have tried all the ports that I could try and I tried using the stock OnePlus cable as well as a different one but neither worked.
Did you enable adb debugging in developers options?
DaOldMan said:
Did you enable adb debugging in developers options?
Click to expand...
Click to collapse
Yes, ADB Debugging is enabled. Other people have said that switching from File Transfer to PTP solved the issue for them but that didn't work for me.
I solved the issue. I just uninstalled everything then downloaded them again and it fixed the issue.
Related
Hello.
I recently installed the 4.3 ota update. I knew I would have to reroot. After the update I have tried everything I can think of to flash a new recovery or bootloader or anything. All without success. Fastboot simply says "Sending...", the phone says "downloading..." and that's the end of it. They would both sit in that state forever if I let them.
I know I'm not alone on this issue. I have searched and searched without finding a solution. Does anyone know of one?
Thanks.
pfederighi said:
Hello.
I recently installed the 4.3 ota update. I knew I would have to reroot. After the update I have tried everything I can think of to flash a new recovery or bootloader or anything. All without success. Fastboot simply says "Sending...", the phone says "downloading..." and that's the end of it. They would both sit in that state forever if I let them.
I know I'm not alone on this issue. I have searched and searched without finding a solution. Does anyone know of one?
Thanks.
Click to expand...
Click to collapse
1. Usb debugging enabled and bootloader unlocked?
2. Correct drivers installed, try these usb naked drivers for instance https://www.google.nl/url?sa=t&rct=...=RUlfH35SAJki_DdLfo8MeA&bvm=bv.51773540,d.Yms.
3. Used the original usb cable or tried another usb port?
4. If you type fastboot devices in fastboot mode do you see a serialnumber? The same for adb devices in adb mode?
gee2012 said:
1. Usb debugging enabled and bootloader unlocked?
2. Correct drivers installed, try these usb naked drivers for instance https://www.google.nl/url?sa=t&rct=...=RUlfH35SAJki_DdLfo8MeA&bvm=bv.51773540,d.Yms.
3. Used the original usb cable or tried another usb port?
4. If you type fastboot devices in fastboot mode do you see a serialnumber? The same for adb devices in adb mode?
Click to expand...
Click to collapse
USB debugging is enabled.
I've tried the original USB cable and others. I've tried different USB ports.
adb works fine. Fastboot recognizes my phone and prints a serial number. Fastboot even works for locking/unlocking the boot loader.
There are no "drivers" in the Linux world. Should I find someone who has a Windows system and ask to use their computer?
Thanks.
pfederighi said:
USB debugging is enabled.
I've tried the original USB cable and others. I've tried different USB ports.
adb works fine. Fastboot recognizes my phone and prints a serial number. Fastboot even works for locking/unlocking the boot loader.
There are no "drivers" in the Linux world. Should I find someone who has a Windows system and ask to use their computer?
Thanks.
Click to expand...
Click to collapse
Yes, you may try that. I`am talking about a windows pc and never had an issue. I don`t have xperience with linux computers.Good luck bro
Solved
gee2012 said:
Yes, you may try that. I`am talking about a windows pc and never had an issue. I don`t have xperience with linux computers.Good luck bro
Click to expand...
Click to collapse
So. I solved the problem. I now feel like an idiot.
I plugged my phone into a Windows system and a nice notice popped up saying that my device could run faster if it was plugged into a USB 2.0 port. Then it dawned on me that only a few of the ports on my computer are 2.0 and that I had tried one of them previously but with an extension cable (because it's in the back and hard to reach). I unplugged the extension cable and plugged the USB cable directly into the port and all was well.
I hope that others who have had this issue find this useful.
Thank you for your help.
I have followed Heisenbergs instructions to the letter but when I issue the adb devices command it just returns the string "list of devices" and that's it. Fastboot devices doesn't work either.
So I'm stuck at the start. Can anyone help me? From what I can tell I may need drivers but I'm new to this so I don't know.
I can give anyone more info if they need it.
I believe part of the instructions are to install the Platform Tools, which should include drivers. Try running the SDK Manager and updating or installing the drivers again. Also ensure you have USB Debugging ON in your Developer settings and OEM Unlocking enabled. Lastly, tap the notification in your shade about the USB connection (I think it defaults to Charging Only) and change it to various modes. Mine seems to only work on PTP mode. When you run the adb devices command you will need to authorize the connection on the phone end the first time by clicking OK so make sure the screen is on and unlocked so you can see it.
Hope this helps.
peckaldee said:
I have followed Heisenbergs instructions to the letter but when I issue the adb devices command it just returns the string "list of devices" and that's it. Fastboot devices doesn't work either.
So I'm stuck at the start. Can anyone help me? From what I can tell I may need drivers but I'm new to this so I don't know.
I can give anyone more info if they need it.
Click to expand...
Click to collapse
u enable OEM Unlock under developer settings?
You enable USB debugging?
Me personally do not get any strings of data returned when im on fastboot
i open CMD, run ADB DEVICES, get message saying the port is opening, and then listing devices... which is empty
but i am able to flash anything i want using fastboot....
try this command and see if it works after that... fastboot reboot-bootloader
it should reboot bootloader for u.. thats a easy way to know its responding to u
Is the device showing properly in the Device Manager when it's connected to your system?
hEaTLoE said:
Is the device showing properly in the Device Manager when it's connected to your system?
Click to expand...
Click to collapse
It shows up in windows explorer as "Nexus 6p" when I plug in the USB cable.
I have USB debugging and unlock bootloader checked in settings.
My fastboot devices command returns nothing.
peckaldee said:
It shows up in windows explorer as "Nexus 6p" when I plug in the USB cable.
I have USB debugging and unlock bootloader checked in settings.
My fastboot devices command returns nothing.
Click to expand...
Click to collapse
Did you change the USB mode? Mine shows in Explorer as you described but won't work in ADB/Fastboot until I change it to PTP.
fury683 said:
Did you change the USB mode? Mine shows in Explorer as you described but won't work in ADB/Fastboot until I change it to PTP.
Click to expand...
Click to collapse
Yeah I tried every option. Nothing.
The instructions say the fastboot devices command should return my serial number and it does not.
When booted into the bootloader one it tells me on one line phone LOCKED and on another line says download mode DISABLED.
Don't know if this has anything to do with my problems but I still cannot get a return on the fastboot devices command in order to proceed with the unlock command of "fastboot flashing unlock"
remember that u need latest fastboot for this to work.
did u updated the SDK manager to the latest? i had to do that in order to work for 6P
chaco81 said:
remember that u need latest fastboot for this to work.
did u updated the SDK manager to the latest? i had to do that in order to work for 6P
Click to expand...
Click to collapse
I'm using sdk manager revision 24.4.1
peckaldee said:
I have followed Heisenbergs instructions to the letter but when I issue the adb devices command it just returns the string "list of devices" and that's it. Fastboot devices doesn't work either.
So I'm stuck at the start. Can anyone help me? From what I can tell I may need drivers but I'm new to this so I don't know.
I can give anyone more info if they need it.
Click to expand...
Click to collapse
I had the same issue ,it was down to when I plugged the phone into the PC for the first time,it installed the Google.USB driver ,but it didn't install the driver for the adb interface,I had to download it from Google and install it manually
I also had the same issue, I had an old Clockworkmod generic driver that I was using for my Samsung Galaxy S5 installed.
Go to Device manager (either type it in the start menu, or: right click This PC, click manage, and click device manager), plug in your unlocked Nexus 6P phone and watch for a new item to pop up. If it says android something, uninstall it. I had to uninstall 3 times, then reinstall the drivers from the SDK before it would work.
I used the skipsoft toolkit to install the fb drivers; worked for me. http://forum.xda-developers.com/nex...ol-skipsoft-android-toolkit-nexus-6p-t3234159
but like others said, you may have to manually remove any that are already installed in windows, although I think that is one of the options in the toolkit.
mbonus said:
I used the skipsoft toolkit to install the fb drivers; worked for me. http://forum.xda-developers.com/nex...ol-skipsoft-android-toolkit-nexus-6p-t3234159
but like others said, you may have to manually remove any that are already installed in windows, although I think that is one of the options in the toolkit.
Click to expand...
Click to collapse
This worked. Now my commands in terminal are working correctly. thanks all for the help
Got A device to pop up under the command adb devices, but nothing under fastboot devices. Any tips? Had to follow the skipsoft instructions to install adb/fastboot devices. Yes USB Debugging is on and the OEM unlocking is set to allow..
Christ I'm retarded. Sorry boys, thought my phone was in the bootloader when I was trying this command LOL
Same problem
peckaldee said:
When booted into the bootloader one it tells me on one line phone LOCKED and on another line says download mode DISABLED.
Don't know if this has anything to do with my problems but I still cannot get a return on the fastboot devices command in order to proceed with the unlock command of "fastboot flashing unlock"
Click to expand...
Click to collapse
I'm having the same problem. Did you ever figure out what was wrong?
mbonus said:
I used the skipsoft toolkit to install the fb drivers; worked for me. http://forum.xda-developers.com/nex...ol-skipsoft-android-toolkit-nexus-6p-t3234159
but like others said, you may have to manually remove any that are already installed in windows, although I think that is one of the options in the toolkit.
Click to expand...
Click to collapse
Solved my problem as well. Thanks!
Hi all,
I am trying to root my phone, following this guide: http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
However, I am stuck at entering 'fastboot devices' into the command prompt. It will not return my device's serial number. I know this is supposed to be becuase I don't have the correct drivers installed - but I'm pretty sure I do! I've spent hours scouring the internet for solutions and I can't find anything to help. So now I turn to you, please help me
I'm running windows 10.
I've double checked the google usb driver is installed.
I've manually installed the android bootloader interface driver.
The bootloader screen says on my phone says 'Connect USB data cable'. It is already connected and I have tried connecting it to all the ports on my laptop. I'm using the original cable that came with the phone.
Well did you enable USB debugging? I'm assuming you did but you didn't list that in the process you said you did.
Eric214 said:
Well did you enable USB debugging? I'm assuming you did but you didn't list that in the process you said you did.
Click to expand...
Click to collapse
I did indeed. And I also fixed it! I just needed to do some more tinkering. I set the fastboot.exe to recommended defaults. Not sure why it was not already but there you go. You can lock or delete this thread now, thanks!
Hi everyone,
I would like to thank everyone that responds ahead of time.
I recently picked up my ph-1 during the recent amazon sale. Currently I am experiencing some issues trying to unlock the bootloader. I would like to preface my situation by saying I'm not new to the rooting/custom rom scene and do have a rudimentary understanding of adb/fastboot.
As the title states, I am currently on Android Pie with my build number being 091. I have tried the process on 3 computers and switched usb ports to verify. I also bought a usb a to usb c cable from amazon. I have installed the essential phone windows drivers and the most current version of minimal adb and fastboot.
I have followed the guide here . I encountered some issues with getting the phone to be recognized by "adb devices" and "fastboot devices", but this was rectified by putting the phone in usb tethering mode and using "fastboot devices -i 0x2e17" in adb and fastboot mode respectively. The issue I am encountering takes place when I run "fastboot -i 0x2e17 flashing unlock" I get a long page of text that essentially that gives parameters to apply a correct form of code. Essentially, the phone does not respond to the command and does not show the "unlock bootloader" screen.
I don't have an image of the text that comes up after pushing the "fastboot -i 0x2e17 flashing unlock" command, but I can upload one later.
If anyone can be of assistance, it would be greatly appreciated.
I want to assume that you have OEM unlocking enable under developer options right?
Sent from my PH-1 using Tapatalk
TJSteveMX said:
I want to assume that you have OEM unlocking enable under developer options right?
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
Yes sir I do. I have OEM unlocking enabled and usb debugging enabled. However, I am only able to get the device to be recognized by my computer when i set the debugging mode to "usb tethering". Not sure if that helps at all.
rfrick93 said:
Yes sir I do. I have OEM unlocking enabled and usb debugging enabled. However, I am only able to get the device to be recognized by my computer when i set the debugging mode to "usb tethering". Not sure if that helps at all.
Click to expand...
Click to collapse
Then unfortunately I think you don't have installed the drivers properly and atm I can't help without a PC. I don't have one
Sent from my PH-1 using Tapatalk
TJSteveMX said:
Then unfortunately I think you don't have installed the drivers properly and atm I can't help without a PC. I don't have one
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
Right on, thanks for the help anyway.
I tried minimal on another pc (not my usual one) and had lots of issues with the PH1. I didn't have time to explore them properly, to find a fix.
I suggest taking the full latest ADB/fastboot from Google ( selecting only what you need).
Have you tried these? https://support.essential.com/hc/en-us/articles/115015512088-Windows-Drivers-for-Essential-Phone
TJSteveMX said:
I want to assume that you have OEM unlocking enable under developer options right?
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
You also need to unlock_critical.
fastboot flashing unlock_critical
Also see this thread: https://forum.xda-developers.com/essential-phone/how-to/guide-rooting-essential-ph-1-magisk-t3701976
Hi Everyone,
Just wanted to update you all.
As TJSteveMX suggested, I believe he was correct in his diagnosis that I had incorrect drivers.
I attempted the unlock and rooting procedure on a different computer that had no previous adb/fastboot installation or any other device drivers on there and was able to complete the process.
Thanks so much for the help!
try using windows powershell. And also use the CMD PMT ./fastboot flashing unlock,,,, once it's done then do it again after restart but then enter ./fastboot flashing unlock_critical i just did this 10 min ago no issue except i didn't need the ./ mine ran normally through powershell.
So I've been messing with android devices for years now and have never ran into this issue. I'm looking to root my new Oneplus 6t, but can't seem to get ADB to recognize the devices. Here are the details....
-Mac OSX Mojave
-USB Debugging on in Dev options
-Tried Clearing the USB authorizations
-Using stock Oneplus cable, but have tried multiple others
-My old Galaxy s8 connects with no issues.
In PTP mode the device will not prompt to authorize the PC, but if I switch to MIDI or USB Tethering it comes up almost instantly. I've updated my android SDK and installed the newest version of Android Studio.
Also, I'm able to access the device via Fastboot and was able to unlock the boot loader, but I'm stuck from here.
Any ideas?
I'm in the same exact boat. Computer recognizes it when it's booted, but once I'm in the bootloader I get nothing but fastboot. I'm using Windows 10
Sent from my ONEPLUS A6013 using Tapatalk
mentalcase said:
So I've been messing with android devices for years now and have never ran into this issue. I'm looking to root my new Oneplus 6t, but can't seem to get ADB to recognize the devices. Here are the details....
-Mac OSX Mojave
-USB Debugging on in Dev options
-Tried Clearing the USB authorizations
-Using stock Oneplus cable, but have tried multiple others
-My old Galaxy s8 connects with no issues.
In PTP mode the device will not prompt to authorize the PC, but if I switch to MIDI or USB Tethering it comes up almost instantly. I've updated my android SDK and installed the newest version of Android Studio.
Also, I'm able to access the device via Fastboot and was able to unlock the boot loader, but I'm stuck from here.
Any ideas?
Click to expand...
Click to collapse
You didn't mention anything about drivers. are the oneplus ADB drivers installed? (I am not sure how things work on mac though)
mentalcase said:
So I've been messing with android devices for years now and have never ran into this issue. I'm looking to root my new Oneplus 6t, but can't seem to get ADB to recognize the devices. Here are the details....
-Mac OSX Mojave
-USB Debugging on in Dev options
-Tried Clearing the USB authorizations
-Using stock Oneplus cable, but have tried multiple others
-My old Galaxy s8 connects with no issues.
In PTP mode the device will not prompt to authorize the PC, but if I switch to MIDI or USB Tethering it comes up almost instantly. I've updated my android SDK and installed the newest version of Android Studio.
Also, I'm able to access the device via Fastboot and was able to unlock the boot loader, but I'm stuck from here.
Any ideas?
Click to expand...
Click to collapse
Did you get.your device from OnePlus or from T-Mobile?
crzycrkr said:
I'm in the same exact boat. Computer recognizes it when it's booted, but once I'm in the bootloader I get nothing but fastboot. I'm using Windows 10
Click to expand...
Click to collapse
When you're on bootloader only fastboot works. That's working as intended.
I was wondering about that. I've been on Samsung phones the last few years so I'm pretty rusty with these things. But all the guides say to check fastboot and adb before flashing the temp twrp. Didn't want to do it if something was wrong
devilrulz4ever said:
When you're on bootloader only fastboot works. That's working as intended.
Click to expand...
Click to collapse
Sent from my ONEPLUS A6013 using Tapatalk
devilrulz4ever said:
When you're on bootloader only fastboot works. That's working as intended.
Click to expand...
Click to collapse
Not quite as I'm attempting to use adb as the phone is in the os not the bootloader.
Also, this was purchased directly from OnePlus.
mentalcase said:
Not quite as I'm attempting to use adb as the phone is in the os not the bootloader.
Also, this was purchased directly from OnePlus.
Click to expand...
Click to collapse
What about the Oneplus ADB drivers? Do you have them installed?
devilrulz4ever said:
What about the Oneplus ADB drivers? Do you have them installed?
Click to expand...
Click to collapse
Drivers aren't required for Mac os.
You probably need a newer adb version. Get the latest mac platform-tools here: https://dl.google.com/android/repository/platform-tools-latest-darwin.zip