Database Info

Un/Official (Windows) USB Drivers/ADB/Fastboot [Essential PH-1/Mata]

Warning if your intent is to Unlock the Bootloader.
At this time 24 Sept 2017
There are no Stock Firmware Images, No Custom Recovery, No Root Method.
Without any of those available Unlocking Bootloader has little Value, and lots of risks.
Official PH-1 windows drivers are up, with Official builds.
https://essential-live.herokuapp.com/developer/current-builds thanks for update @bmg1001 -14 Nov 2017
I haven't seen any Official Windows USB drivers (adb/fastboot) posted any where so i just used Google Pixel Drivers.
Official Google Drivers
Selecting correct drivers in Device manager
Adb seems to work with Windows default drivers, but i had to update ADB.exe version
SDK Platform-Tools for Windows ~3MB
If you have never used ADB
[Index] Setting up and Using ADB/Fastboot
[TOOL]Minimal ADB and Fastboot [1-6-17] by shimp208
Enabling Dev Options
See post #2
ADB Setup/ Troubleshooting
See post #3

Enable Dev Options..
Settings/About phone
Tap on Build number, until you see "You are now Developer"
Back up one screen (Main Settings Page)
tap Developer options
Optional
Toggle on Stay Awake (if you are new to this)
If you are plan on Unlocking Bootloader
Toggle On OEM unlocking
Select Enable (on popup window)
Required
Toggle On USB debugging
Watch for Allow USB debugging popup on Phone
recommended
check box Always allow from this computer
then OK

Testing ADB setup by booting to bootloader
Code:
adb reboot-bootloader
If that code doesn't work you may need to update adb

Fastboot setup
Fastboot commands only work with the device in Fastboot/Bootloader Mode
Boot the Device to Bootloader Options
Code:
adb reboot-bootloader
Power off, Hold Volume Down Button, Power On
Connect To PC via USB
Open PC Device Manager (Settings/Devices/Device Manager)
Look For Mata
Update Driver (Right Click on Mata)
Browse My Computer for Driver Software
Let Me Pick from a List of Available Drivers
Select your Device's Type: ADB
Select the Driver ypu want to Install
Manufacture: Google
Model: ADB Testing (there may be a better one)
Select: Next
PH-1/Mata should look like this
If You don't see adb drivers in available drivers
Try installing l Google Drivers in post #1

I'm using the minimal adb&fastboot, do you think that's the problem?
edit: see attached thumnail, I looked at your photos and followed the instructions. On my windows I get the following options. I tried the two "ADB testing interface" options and neither seem to allow me to perform fastboot commands. If I type fastboot devices nothing happens while the device is in fastboot mode. The ADB commands while the device is powered on do work though.

elsamuraiguapo said:
I'm using the minimal adb&fastboot, do you think that's the problem?
Click to expand...
Click to collapse
no, you need to select the correct driver in Device Manager

Looks like Minimal ADB and Fastboot hasn't been updated since 6th January 2017
So that could be an issue

Updated post #4
to explain images in post #1

sd_shadow said:
no, you need to select the correct driver in Device Manager
Click to expand...
Click to collapse
I did. Check out the picture in my post above. Also I tried to install everything again from the beginning using the [TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3 by*Snoop05 and that didn't work either.
Is yours the Sprint variant?

elsamuraiguapo said:
I did. Check out the picture in my post above. Also I tried to install everything again from the beginning using the [TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3 by*Snoop05 and that didn't work either.
Click to expand...
Click to collapse
Doesn't look like that has been updated since October 2016
i would use the ADB files direct from Google, link in post #1
Is yours the Sprint variant?
Click to expand...
Click to collapse
No, but if bootloader wasn't Unlockable, the OEM unlocking option in Settings should be Greyed out and unselectable

[TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3 by*Snoop05
adb-setup-1.4.3.exe
has adb version Android Debug Bridge version 1.0.32 Revision eac51f2bb6a8-android
and fastboot commands didn't work for me with Mata

ADB version working for me is
Code:
adb version
adb version
Android Debug Bridge version 1.0.39
Revision 3db08f2c6889-android

[TOOL]Minimal ADB and Fastboot [1-6-17] by shimp208
minimal_adb_fastboot_v1.4.2_setup.exe
Android Debug Bridge version 1.0.36
Revision 0e9850346394-android
does appear to be workng

sd_shadow said:
[TOOL]Minimal ADB and Fastboot [1-6-17] by shimp208
minimal_adb_fastboot_v1.4.2_setup.exe
Android Debug Bridge version 1.0.36
Revision 0e9850346394-android
does appear to be workng
Click to expand...
Click to collapse
Okay, I was using an outdated version so I updated to v1.4.2, but still same problem with the fastboot commands. You said to download the google drivers from post #1. I downloaded it and it gives me a ZIP; sorry to sound like a noob but I can't find a .exe in that ZIP to install. I open up the zip and these are the files I see in the usb_driver folder it produces.
Thanks for your quick replies so far by the way.

elsamuraiguapo said:
Okay, I was using an outdated version so I updated to v1.4.2, but still same problem with the fastboot commands. You said to download the google drivers from post #1. I downloaded it and it gives me a ZIP; sorry to sound like a noob but I can't find a .exe in that ZIP to install. I open up the zip and these are the files I see in the usb_driver folder it produces.
Thanks for your quick replies so far by the way.
Click to expand...
Click to collapse
You seem to have the same driver that I have
Adb...1.0.10.0 with 2010 date

sd_shadow said:
You seem to have the same driver that I have
Adb...1.0.10.0 with 2010 date
Click to expand...
Click to collapse
Well I uninstalled all the drivers I could find on my computer to start from scratch. Which should I install? I can't figure out how to install the google usb drivers referenced above

Download latest_usb_driver_windows .zip
Right Click Extract All
Open Folder latest_usb_driver_windows / USB_Driver
Right Click android_winusb.inf
Select Install
Connect Device to PC
adb reboot-bootloader
Select Window menu/Settings/Devices/related Settings/Device Manager
In Device Manager
Right Click Meta/PH-1
Select Update Driver
Browse My Computer for drive Software
Let me Pick From A List of Available drivers
Select Android Device
Select Android ADB Interface
Click Yes at Update driver Warning
Close
Driver selected should be Google 11.0.0.0
If Android ADB Interface is not an option
Uninstall device in Device Manager
Then disconnect and reconnect Device
try again

sd_shadow said:
Download latest_usb_driver_windows .zip
Right Click Extract All
Open Folder latest_usb_driver_windows / USB_Driver
Right Click android_winusb.inf
Select Install
Connect Device to PC
adb reboot-bootloader
Select Window menu/Settings/Devices/related Settings/Device Manager
In Device Manager
Right Click Meta/PH-1
Select Update Driver
Browse My Computer for drive Software
Let me Pick From A List of Available drivers
Select Android Device
Select Android ADB Interface
Click Yes at Update driver Warning
Close
Driver selected should be Google 11.0.0.0
If Android ADB Interface is not an option
Uninstall device in Device Manager
Then disconnect and reconnect Device
try again
Click to expand...
Click to collapse
Okay awesome, I think we're almost done. When I type in fastboot devices I can see the device now. Starts with PM1. What command did you use to unlock the bootloader? I tried fastboot oem unlock and "fastboot flashing unlock" and it failed. (remote: unknown command)
Edit: Never mind it worked now after a few attempts. Weird cause I typed the same command over and over and it kept failing. Anyway looks like it rebooted successfully after the factory reset. Thanks for your help mate. Now I can set up the device to my liking and just wait until we get customer recovery and root.

Hi guys, same issue here with OPENUS version of the MATA PH-1.
I have installed 15 seconds ADB driver 1.43 clean on laptop and can access the phone with ADB and reboot it into bootloader.
However, 'fastboot devices' gives me nothing. I've updated the Mata in device manager first with the options from the 15 seconds ADB, with are 'Android ADB Interface', 'Android Bootloader Interface' and 'Android Composite ADB Interface'. None of them give me any luck when trying 'fastboot devices', nothing found.
Then, uninstalled the ADB driver from device manager so that it showed Mata again, installed Google driver from 1st post, but same thing: version 11.0 of Google drivers (28/08/2014) with same choices, but none of them work.
Does this have to do with the USB A 3.0 --> USB C cable maybe? Or is it just a driver thing?
BTW reason for unlocking is so that I can root later without wiping the device, once root becomes available..

updated post 1 a bit

AARP RealPad MA7BX2 (how to root or unlock bootloader?)

I wasn't able to find this device anywhere on this site, so I'm posting here in general Q&A. I'd like to wipe the default firmware on my RealPad and install a newer/better version of Android. However, I've been unsuccessful in rooting it. (Note that I have jailbroken an iPad and have experience with Linux and remote access tools, but I'm a noob when it comes to Android). I tried a handful of Windows-based tools (e.g., iRoot, Kingo Root) and a few .apk's from sites like "Kingo Root" and "TWRP" but no joy.
I also tried running the commands below (included output) using SDK Tools (v26.1.1) on a Windows 7 laptop. I downloaded this toolset from httpx://developer.android.com/studio/releases/sdk-tools.
c:\fastboot>adb reboot bootloader
* daemon not running; starting now at tcp:5037
* daemon started successfully
c:\fastboot>fastboot oem unlock
< waiting for any device >
command')
fastboot: error: Command failed
c:\fastboot>fastboot flashing unlock
oo many links))
fastboot: error: Command failed
In case anyone is interested in lending a hand, below are a few system specs from "About tablet". I'd be more than happy to try any other tools, commands or instructions, if anyone is curious enough to reply. Also, I am able to boot into some type of boot menu (DROIDBOOT PROVISION OS) by holding volume down + power button when the tablet is turned off. "Recovery" is one of the boot options. When selected, it boots into "Android system recovery <3e>; KOT49H.23834 release-keys".
Tablet Details:
Manufacturer: AARP (no kidding)
Model: RealPad MA7BX2
Android version: 4.4.2
IFWI version: F9.59
Kernel version: 3.10.20-g572bde2
Build number: 23834-000B.00.01.70

Fastboot Issues with Nokia 3

Hey guys, I’ve been trying to turn my old Nokia 3 into a LineageOS device for the last week, mainly as a test before I try it on my main device (a Nokia 8), but I’m not having any luck. I’m trying to follow the steps as described on the board here. While I did have great success installing LOS on an old Samsung Galaxy S5 Neo following the guide on the wiki (wiki.lineageos.org/devices/s5neolte/install), the Nokia 3 is just not having it and I’m running out of ideas. So much for an introduction, let’s get into it …
The device:
Nokia 3—“TA-1020”
Android Version: 8.1.0
USB Debugging is turned on and my laptop has permission.
OEM Unlocking is not available/greyed out in the Dev. Options.
My Laptop:
OS: Windows 10
Nokia USB Drivers are installed.
The Nokia 3 is recognized by the Device Manager, Explorer, and adb.exe.
All commands are used via cmd as administrator from within the adb directory.
The Issues:
“adb devices” finds the device and lists it as “NE… device”—so far so good, I guess, but …
“adb reboot-bootloader” reboots the device, but it does not boot into fastboot mode and instead just reboots normally
“adb devices” after “adb reboot-bootloader” just lists it as “device” again
going into fastboot mode manually by using Power+Volume Up to get into recovery mode works; I then get a black screen with a little “=> FASTBOOT mode…” on the bottom
“adb devices” does no longer find the device, once this black fastboot screen is on
Windows finds the device and lists it in the Device Manager under “ADB Interface” » “Fastboot Device”
“fastboot devices” via cmd does not find the device, however
“fastboot oem unlock” returns “<waiting for device>” and is stuck there until I quit (I tried waiting for about 45 minutes once, but to no avail)
So here I am—stuck. Forget installing LineageOS, it seems like I can’t even unlock the OEM because the device is “invisible.” Does anyone have any suggestions? I would really appreciate the help.

blarkh said:
Hey guys, I’ve been trying to turn my old Nokia 3 into a LineageOS device for the last week, mainly as a test before I try it on my main device (a Nokia 8), but I’m not having any luck. I’m trying to follow the steps as described on the board here. While I did have great success installing LOS on an old Samsung Galaxy S5 Neo following the guide on the wiki (wiki.lineageos.org/devices/s5neolte/install), the Nokia 3 is just not having it and I’m running out of ideas. So much for an introduction, let’s get into it …
The device:
Nokia 3—“TA-1020”
Android Version: 8.1.0
USB Debugging is turned on and my laptop has permission.
OEM Unlocking is not available/greyed out in the Dev. Options.
My Laptop:
OS: Windows 10
Nokia USB Drivers are installed.
The Nokia 3 is recognized by the Device Manager, Explorer, and adb.exe.
All commands are used via cmd as administrator from within the adb directory.
The Issues:
“adb devices” finds the device and lists it as “NE… device”—so far so good, I guess, but …
“adb reboot-bootloader” reboots the device, but it does not boot into fastboot mode and instead just reboots normally
“adb devices” after “adb reboot-bootloader” just lists it as “device” again
going into fastboot mode manually by using Power+Volume Up to get into recovery mode works; I then get a black screen with a little “=> FASTBOOT mode…” on the bottom
“adb devices” does no longer find the device, once this black fastboot screen is on
Windows finds the device and lists it in the Device Manager under “ADB Interface” » “Fastboot Device”
“fastboot devices” via cmd does not find the device, however
“fastboot oem unlock” returns “<waiting for device>” and is stuck there until I quit (I tried waiting for about 45 minutes once, but to no avail)
So here I am—stuck. Forget installing LineageOS, it seems like I can’t even unlock the OEM because the device is “invisible.” Does anyone have any suggestions? I would really appreciate the help.
Click to expand...
Click to collapse
You need to have fatboot drivers to be able to see your device in fastboot. I had the same problem with it connecting to adb devices but not to fastboot devices. I downloaded the driver on this thread https://forum.xda-developers.com/no...-bootloader-nokia-3-pie-t4012285#post82382141 which also shows how to unlock the bootloader. You will not be allowed to flash lineage without unlocking the bootloader first.

Op7pro not responding to fastboot commands

Hey, im having trouble finding working ways to root my op7pro GM1913 (OOS 11.0.4.1 GM21BA)
Ive been trying this https://www.xda-developers.com/unlock-bootloader-root-oneplus-7-pro/
Currently trying to unlock bootloader. (Step 2)
I can connect via adb but when i go to bootloader/fastboot i lose connection to the phone.
Ive tried regular adb command tools and "TOOL ALL IN ONE" When the phone is on it responds to adb commands but when i need fastboot commands its not working and i can see the device id dissapear from the all in one tool.
I have tried multiple usb ports (2.0 and 3.0) and multiple usb C cords (Op oem + Samsung) Tried removing Windows signature verification and installing oneplus usb drivers, but it gets stuck at "Execute the commands..." (99% or so) When i try again it finds some installation files. When im in bootloader, Windows device manager still shows a generic android phone. Oem unlocking and usb debugging is on, also set default usb configuration to file transfer. No help.
I want to keep Oxygen os, but i want to be rooted and have magisk, preferably TWRP too but im open to other ways.
Windows 10 20H2 if that matters. (Latest update for me)
Oneplus 7pro GM1913 (Eu nordic)
Oxygen os 11.0.4.1 GM21BA

Download a Linux distro and install adb and fastboot like this: https://forum.xda-developers.com/t/guide-unlock-flash-root-for-the-pixel-2-xl-taimen.3702418/
Just download adb and fastboot tools package from Google, extract it,open command prompt inside where you extract it and enter these in terminal:
sudo install adb dmtracedump e2fsdroid etc1tool fastboot hprof-conv make_f2fs mke2fs mke2fs.conf sload_f2fs sqlite3 /usr/local/bin
sudo mkdir -p /usr/local/lib64
sudo install lib64/libc++.so /usr/local/lib64
Then adb --version (enter) fastboot --version (enter) like Nathan says in guide. Super easy and I guarantee you if you go this route you won't have any hiccups. Sounds like stupid windblows driver issues or outdated adb/fastboot tools. One of the two. Are you flipping on dev options and check marking little box that pops up on your phone to allow it to communicate with PC? A simple : adb devices (enter) should make it appear on phone screen. You don't even have to install Linux, you can boot it off a live USB. Takes about one minute to make one. If you make one you can boot the live USB , download adb and fastboot, and install as Nathan's guide says then reboot when you are done and your back in windblows. IDK why anyone wouldn't want Linux installed though. Best decision I ever made was switching from windows to Linux about 9 years ago. It really makes anything you do to your devices MUCH easier to do!! This may sound stupid but have you rebooted your PC? Because you will definitely need to , probably more than once on windblows to get it to work.

Thank you for the reply. No stupid questions, yes i tried rebooting pc/phone. Ill try your way and report in a couple days.

Solution is simple. From Android 11 on, OnePlus (and Android phones in general) uses the universal drivers, you just need to install them in Windows in order to use fastboot commands. See my answer in this post.

There are a few things you can try if your OP7 Pro is not responding to fastboot commands:
1. Make sure you have the latest drivers installed for your phone.
2. Try using a different USB cable.
3. If you're using Windows, try running the fastboot commands from a command prompt with administrator privileges.
4. Try booting your phone into recovery mode and running the fastboot commands.

PLEASE HELP

can someone please point me in the right direction on how to root google pixel 1 (not XL). i think its on android 9 or 10. THANK YOU!!!

xdanoob333 said:
can someone please point me in the right direction on how to root google pixel 1 (not XL). i think its on android 9 or 10. THANK YOU!!!
Click to expand...
Click to collapse
In setting press 7 times build number, then you have developer options in settings, go into developer options and find oem unlock and enable it
Go into fastboot mode
https://www.hardreset.info/devices/google/google-pixel/fastboot-mode/
Download these on computer
[OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3
15 seconds ADB Installer v1.4.3 ADB, Fastboot and Drivers What is this? This is All-in-One installer for 3 most needed PC tools for Android. No need to download big SDK for 3 small things. I originaly made it for my Kurdish friend AnGrY DuDe in...
forum.xda-developers.com
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Connect phone to pc
Extract platform tools zip and click inside the one folder in platform tools zip and right click and click open command window or powershell here
Execute "fastboot oem unlock"
If fail then try .\fastboot oem unlock
Or replacing "oem" with "flashing"
Tell me if success or fail and I will tell you more steps.

LR7875 said:
In setting press 7 times build number, then you have developer options in settings, go into developer options and find oem unlock and enable it
Go into fastboot mode
https://www.hardreset.info/devices/google/google-pixel/fastboot-mode/
Download these on computer
[OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3
15 seconds ADB Installer v1.4.3 ADB, Fastboot and Drivers What is this? This is All-in-One installer for 3 most needed PC tools for Android. No need to download big SDK for 3 small things. I originaly made it for my Kurdish friend AnGrY DuDe in...
forum.xda-developers.com
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Connect phone to pc
Extract platform tools zip and click inside the one folder in platform tools zip and right click and click open command window or powershell here
Execute "fastboot oem unlock"
If fail then try .\fastboot oem unlock
Or replacing "oem" with "flashing"
Tell me if success or fail and I will tell you more steps.
Click to expand...
Click to collapse
will do thank you!!

LR7875 said:
In setting press 7 times build number, then you have developer options in settings, go into developer options and find oem unlock and enable it
Go into fastboot mode
https://www.hardreset.info/devices/google/google-pixel/fastboot-mode/
Download these on computer
[OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3
15 seconds ADB Installer v1.4.3 ADB, Fastboot and Drivers What is this? This is All-in-One installer for 3 most needed PC tools for Android. No need to download big SDK for 3 small things. I originaly made it for my Kurdish friend AnGrY DuDe in...
forum.xda-developers.com
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Connect phone to pc
Extract platform tools zip and click inside the one folder in platform tools zip and right click and click open command window or powershell here
Execute "fastboot oem unlock"
If fail then try .\fastboot oem unlock
Or replacing "oem" with "flashing"
Tell me if success or fail and I will tell you more steps.
Click to expand...
Click to collapse
when i type in .\fastboot oem unlock just says waiting for any device. also when im in fastboot mode the very bottom where it says DEVICE it says LOCKED even tho in develop options oem unlock is enabled.

xdanoob333 said:
when i type in .\fastboot oem unlock just says waiting for any device. also when im in fastboot mode the very bottom where it says DEVICE it says LOCKED even tho in develop options oem unlock is enabled.
Click to expand...
Click to collapse
Also enable usb debigging in developer options on your phone in android. You can start backuping too as unlocking bootloader factory resets your device.