Related
Hi All,
I bought a Nexus 4 on eBay thinking I could fix it but I am really struggling.
The nexus 4 has TWRP 2.8.6.0 but that is all.
I cannot enable USB debugging as I don't have any rom installed.
I have tried a USB OTG cable with power, but have learned that the phone still cannot output the right power? The light on my usb stick comes on but TWRP does not list any USB OTG.
This phone does not have an SD card slot, so I cannot load anthing this way.
Is it impossible to get this phone working?
Kind Regards,
breaktheblock
Try fastboot from the bootloader, and reflash
ReneX10 said:
Try fastboot from the bootloader, and reflash
Click to expand...
Click to collapse
Hi ReneX10,
Thankyou for the reply, can you tell me the next step after I get to the fastboot screen?
breaktheblock said:
Hi ReneX10,
Thankyou for the reply, can you tell me the next step after I get to the fastboot screen?
Click to expand...
Click to collapse
tbh, going back to stock is a good idea and then the door is open
https://developers.google.com/android/nexus/images?hl=en
there ya go, basically follow the instructions...
ReneX10 said:
tbh, going back to stock is a good idea and then the door is open
there ya go, basically follow the instructions...
Click to expand...
Click to collapse
Will I need adb drivers to be working in windows for me to be able to do this? because so far I have been unable to successfully install any even using NRT to help.
breaktheblock said:
Will I need adb drivers to be working in windows for me to be able to do this? because so far I have been unable to successfully install any even using NRT to help.
Click to expand...
Click to collapse
Afraid I am a Linux baby, can't help you with Windows :/
fastboot etc already on there
my windows computer wont recognize the phone when I plug phone into the PC, driver installation always fails?
how can i connect a phone with just TWPR to my PC, could this be using MTP?
breaktheblock said:
my windows computer wont recognize the phone when I plug phone into the PC, driver installation always fails?
how can i connect a phone with just TWPR to my PC, could this be using MTP?
Click to expand...
Click to collapse
Have a look at this thread ..
http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
(Read the thread thoroughly, and take notes, its real easy to get lost in the middle of the procedure and mess it up, and having to start again).
Flashing the stock rom is done entirely via fastboot, so you shouldnt need to worry about adb.
If you can boot into bootloader you should be able to flash stock image, once you get the windows drivers sorted. Luckily I'm on a Mac, so drivers haven't been an issue. I had a similar scenario sometime ago, and after flashing stock, all was good in the world again. I may be wrong, but you'll probably need the latest platform-tools (which contains fastboot) if you're flashing the latest stock images. (Someone correct me if I'm wrong on that one).
Sent from my LG-V500 using Tapatalk
dsbnz said:
Have a look at this thread ..
http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
(Read the thread thoroughly, and take notes, its real easy to get lost in the middle of the procedure and mess it up, and having to start again).
Flashing the stock rom is done entirely via fastboot, so you shouldnt need to worry about adb.
If you can boot into bootloader you should be able to flash stock image, once you get the windows drivers sorted. Luckily I'm on a Mac, so drivers haven't been an issue. I had a similar scenario sometime ago, and after flashing stock, all was good in the world again. I may be wrong, but you'll probably need the latest platform-tools (which contains fastboot) if you're flashing the latest stock images. (Someone correct me if I'm wrong on that one).
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
This is good information, but I cannot get any further that plugging the phone into the PC, I have tried 4 different usb cables and with them all windows 7 and XP says "unknown device".
I wasn't sent the original cable from the owner which I am asking to do if they have it, but it may be a long shot for them to still have it.
Looks like I need the original usb cable?
breaktheblock said:
This is good information, but I cannot get any further that plugging the phone into the PC, I have tried 4 different usb cables and with them all windows 7 and XP says "unknown device".
I wasn't sent the original cable from the owner which I am asking to do if they have it, but it may be a long shot for them to still have it.
Looks like I need the original usb cable?
Click to expand...
Click to collapse
I don't think the cable needs to be original, I've used a Motorola cable on my N4 to flash stock, with no problems.
Is the phone in fastboot mode when you connect to pc?
Have you tried these drivers?
http://developer.android.com/sdk/win-usb.html
Sent from my LG-V500 using Tapatalk
dsbnz said:
I don't think the cable needs to be original, I've used a Motorola cable on my N4 to flash stock, with no problems.
Is the phone in fastboot mode when you connect to pc?
Have you tried these drivers?
http://developer.android.com/sdk/win-usb.html
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
For information I am using a cable from a usb cable that came from a Nexus 5.
When the phone is connected to the PC it had an android lying down with an open chest.
When pointing to the android developer sdk drivers as above it does it's usual thing of saying it is already up to date below that still saying unknown device. I'm so frustrated right now.
breaktheblock said:
For information I am using a cable from a usb cable that came from a Nexus 5.
When the phone is connected to the PC it had an android lying down with an open chest.
When pointing to the android developer sdk drivers as above it does it's usual thing of saying it is already up to date below that still saying unknown device. I'm so frustrated right now.
Click to expand...
Click to collapse
Can you reboot to the main bootloader screen?
The reason i ask is .. When you see the android lying down is there a list below showing the phone stats? If not, possibly this is why windows is reporting an unknown device.
You should try to get back into fastboot
This has the info to get to bootloader if youre not sure how..
http://www.androidcentral.com/how-unlock-nexus-4-bootloader
When you're in fastboot, try to connect to pc again.
Sent from my LG-V500 using Tapatalk
dsbnz said:
Can you reboot to the main bootloader screen?
The reason i ask is .. When you see the android lying down is there a list below showing the phone stats? If not, possibly this is why windows is reporting an unknown device.
You should try to get back into fastboot
This has the info to get to bootloader if youre not sure how..
http://www.androidcentral.com/how-unlock-nexus-4-bootloader
When you're in fastboot, try to connect to pc again.
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
Underneath the android lying down it has:
FASTBOOT MODE (in red text)
PRODUCT_NAME
HW VERSION
BOOTLOADER VERSION
BASEBAND VERSION
CARRIER INFO
SERIAL NUMBER
SIGNING
SECUREBOOT (in green text - enabled)
LOCK STATE (in red text - unlocked)
Above the android lying down I can use the hardware buttons to toggle between "Start | Restart bootloader | Recovery mode | Power off"
Am I in fastboot?
breaktheblock said:
Underneath the android lying down it has:
FASTBOOT MODE (in red text)
PRODUCT_NAME
HW VERSION
BOOTLOADER VERSION
BASEBAND VERSION
CARRIER INFO
SERIAL NUMBER
SIGNING
SECUREBOOT (in green text - enabled)
LOCK STATE (in red text - unlocked)
Above the android lying down I can use the hardware buttons to toggle between "Start | Restart bootloader | Recovery mode | Power off"
Am I in fastboot?
Click to expand...
Click to collapse
Sounds like youre in the right mode. The problem would likely be on the pc/driver side.
P.S. in fastboot mode, you only need to use fastboot on pc .
Sent from my LG-V500 using Tapatalk
dsbnz said:
Sounds like youre in the right mode. The problem would likely be on the pc/driver side.
P.S. in fastboot mode, you only need to use fastboot on pc .
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
The driver issue is a massive stumbling block.
I'm still not sure if the cable will work.
I understand I can use fastboot after the PC recognises the nexus 4.
I have a Lubuntu PC this may help me but I have no idea where to start in terms of the drivers.
breaktheblock said:
The driver issue is a massive stumbling block.
I'm still not sure if the cable will work.
I understand I can use fastboot after the PC recognises the nexus 4.
I have a Lubuntu PC this may help me but I have no idea where to start in terms of the drivers.
Click to expand...
Click to collapse
I use a mac, so im no use when it comes to linux variants etc.
Depending on the power of your pc, you could try using a virtual machine (i.e. virtualbox running windows xp if you have xp disk, or even windows 7). Ive done this before on the mac (xp virtual machine) and it works. This way you can install the correct drivers on a fresh install of windows, without messing with the host OS.
Otherwise, best bet is to uninstall any drivers in your current windows, and install divers from google link i posted earlier.
Sent from my LG-V500 using Tapatalk
breaktheblock said:
The driver issue is a massive stumbling block.
I'm still not sure if the cable will work.
I understand I can use fastboot after the PC recognises the nexus 4.
I have a Lubuntu PC this may help me but I have no idea where to start in terms of the drivers.
Click to expand...
Click to collapse
just outta curiosity, when you plug the phone in (in bootloader mode) change dir to the one with fastboot.exe in and type (in command prompt):
fastboot devices
what output do you get?
ReneX10 said:
just outta curiosity, when you plug the phone in (in bootloader mode) change dir to the one with fastboot.exe in and type (in command prompt):
fastboot devices
what output do you get?
Click to expand...
Click to collapse
nothing happens at all.
I think I have something similar to this http://forum.xda-developers.com/nexus-4/help/twrp-os-installed-connect-to-pc-t2538794
as in i'm stuffed. :crying:
As in "no devices detected" ...what is the output? Pfffft I tried!
ReneX10 said:
As in "no devices detected" ...what is the output? Pfffft I tried!
Click to expand...
Click to collapse
Just to check I am doing it correctly, I launch cmd in windows, change the directory to the location where fastboot is and type "fastboot devices". The result of this is it just gives the directory name again waiting for another command.
I hope I'm not coming across as ungrateful, I assure you this is not the case.
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!
After moving to Lineage 14 from stock 21s, I came to realize Android Pay will not work if the bootloader is unlocked.
So I went to go and lock the bootloader (with TWRP and Lineage still installed) and for some reason when I do a "adb devices" the phone is not seen.
I uninstalled the driver, reinstalled.
Tried unplugging, launching ADB, then plugging in..
Plugging in then launching ADB...
Then i put ADB on my wife's laptop (A PC I have never plugged the leeco pro 3 on to), then plugged in for the first time already in fast boot. Still no dice.
Anyone have any ideas?
How about using Magisk to bypass SafetyNet check instead of locking your bootloader?
kaneorotar said:
How about using Magisk to bypass SafetyNet check instead of locking your bootloader?
Click to expand...
Click to collapse
That is what I am doing, but I am still concerned about the ADB not seeing the phone in fastboot mode. If I have some type of catastrophic issue where i need to restore from fastboot i will be screwed.
ekeefe41 said:
That is what I am doing, but I am still concerned about the ADB not seeing the phone in fastboot mode. If I have some type of catastrophic issue where i need to restore from fastboot i will be screwed.
Click to expand...
Click to collapse
If you boot into fastboot mode (Volume Up + Power), does the phone show up in 'fastboot devices'?
If so, then IMHO you should be fine in catastrophic situation.
kaneorotar said:
How about using Magisk to bypass SafetyNet check instead of locking your bootloader?
Click to expand...
Click to collapse
kaneorotar said:
If you boot into fastboot mode (Volume Up + Power), does the phone show up in 'fastboot devices'?
If so, then IMHO you should be fine in catastrophic situation.
Click to expand...
Click to collapse
No, that is the issue, lol
Do you have adb drivers, and did you try completely deleting your device drivers from Device Manager, then reinstalling them by plugging your phone in via USB Debugging? Are you using the platform-tools package? Did you connect via USB Debugging, and did you authorize the computer (the message should pop up on your phone)? I can't fathom why your phone wouldn't be recognized...
sk8223 said:
Do you have adb drivers, and did you try completely deleting your device drivers from Device Manager, then reinstalling them by plugging your phone in via USB Debugging? Are you using the platform-tools package? Did you connect via USB Debugging, and did you authorize the computer (the message should pop up on your phone)? I can't fathom why your phone wouldn't be recognized...
Click to expand...
Click to collapse
Yes to everything, lol
And when I am connected to the phone while in the OS, ADB works fine, shows in when I "ADB devices"
Where'd you get your phone from? Banggood, Geekbuying, Gearbest? Did it come with a vendor ROM? Did it not pass SafetyNet on the original ROM it came with?
Are you following these instructions? Of course, replace the required stock ROM with the one for your version (x720 or x727). So does the issue come up when you reboot the phone via ADB while in the OS?
In any case, try asking on the http://www.leeco.re/ forums as well.
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