[AC Question]

I'm trying to unlock the bootloader for my OP2, and from what people say online it's relatively easy, but I installed all appropriate drivers (OPO drivers, Google ADB drivers) and I also installed the adb and fast boot all-in-one setup utility that 'should' install everything necessary for unlocking.

The problem occurs when I go to fastboot and then run ADB devices or fastboot devices. Adb stays blank and Fastboot says <waiting for device> I have been literally hours searching in google for many solutions but none seem to work for me. I tried to manually update drivers from 'device management' but the 'other devices' doesn't appear at all, and even when I 'enable show hidden devices' the android icon appears with a question mark and not with a yellow exclamation mark like others in forums have gotten. I have no idea what to do anymore, I've reinstalled all drivers numerous times and restarted my computer many times.
Im just trying to unlock the bootloader, it's never been so difficult for me like it is now and I don't know why.

Thanks in advance,

[meattray]

Have you turned ADB debugging on?

[ystefanov]

Yes, USB debugging is on from the OP2. I suppose thats what you meant.

[meattray]

Does your computer recognize the device when you plug it in? What happens at that point?

[Golfdriver97]

When in fastboot try typing fastboot devices.

Edit: this should give you a response. The PC should report the serial number of the device.

[ystefanov]

Yes, so when it's plugged in and it's COMPLETELY booted up to lockscreen, then the computer finds it. The problem occurs only when I go to either recovery or fastboot mode, then the adb devices shows nothing again and neither does fastbot

[ystefanov]

I did that but it does nothing, blank. Only when its completely booted up does it show my phone in cmd.
( in reply to Golfdriver97)

[Golfdriver97]

There is a difference between ADB commands and Fastboot. ADB commands won't work in fastboot mode.

Did you alter your PATH for fastboot and ADB?

[ystefanov]

There is a difference between ADB commands and Fastboot. ADB commands won't work in fastboot mode.

Did you alter your PATH for fastboot and ADB?

I dont believe I altered the path of either. And even fastboot just says either waiting or nothing at all.

[Golfdriver97]

You then need to be in the specific folder where ADB is. Jerry did an article for the blog on how to do that. Give me a few minutes to find it.

[Golfdriver97]

This may help: http://m.androidcentral.com/installi...linux-tutorial

[ystefanov]

You then need to be in the specific folder where ADB is. Jerry did an article for the blog on how to do that. Give me a few minutes to find it.

I believe I am in the specified folder, which in my case it's "C:\adb

EDIT: It says my posts wont be approved until a moderator sees them so for now here are the instructions I followed :

https://forums.oneplus.net/threads/2...d-more.345478/

[Golfdriver97]

Can you post the instructions you followed?

[ystefanov]

Can you post the instructions you followed?

Sure, here: https://forums.oneplus.net/threads/2...d-more.345478/

[Golfdriver97]

Do you have a folder called C:\Android\platform-tools ?

[ystefanov]

Nope


EDIT: I also haven't installed android SDK, but because from the looks of the guide it wasn't necessary.

[Golfdriver97]

The SDK is necessary, as I recall. Try this method: https://www.google.com/amp/lifehacke...1586992378/amp

[ystefanov]

Still wont work... Same problem.

[xocomaox]

Forget fastboot for now.

What happens when you run ADB Devices command when the phone is connected and unlocked at the home screen? Should give you something. If not, please install the SDK and run the same command out of that platform-tools folder where ADB.exe lives.

You may need to update the adb drivers from the SDK tools. That updater is really simple.