Related
Description
After always having to search for the latest versions of Android's ADB and Fastboot tools instead of downloading the whole Android SDK for just 1 mb in a few files, I decided to make my own MSI installer using the latest versions of ADB and Fastboot.
You can install it wherever you want and it will work from any path in the command prompt. The installer will append the installation folder location to the system PATH variable, allowing you to run ADB or Fastboot without you having to change the command prompt path to where they are installed.
This installer is 32-bit and 64-bit compatible.
Usage
The default installation path is C:\ADB so you can easily add your flashable files in there.
After installing Android ADB Fastboot you can open a command prompt and type adb or fastboot commands right away, you don't need to change paths. Keep in mind that you need admin privileges, though.
To open a command prompt with administrator rights on Windows 8, just right click on the bottom left corner of the screen or use the Win+X shortcut and then click on Command Prompt (Admin).
Click to expand...
Click to collapse
If you have Windows 7 or Vista, the quickest way to do it is to type CMD on the Start Menu search box and press Ctrl+Shift+Enter instead of just pressing Enter.
Click to expand...
Click to collapse
Requisites
You need to have ADB Debugging under Developer Options on your device. You also need the drivers for every device you want to use with ADB installed and working.
You can type adb devices on a command prompt. If your device is listed, the drivers are working and good to go for ADB and Fastboot use.
Click to expand...
Click to collapse
Download
I will always check the ADB version whenever a new Android SDK is released and I will update my installer when needed.
The download link and screenshots are on my website.
http://rubenalamina.mx/custom-installers/android-adb-fastboot/
Latest version of the installer: 1.5 (ADB 1.0.36) updated on 2016.09.21
Thanks mate, it really help people with lacks internet connection like mine
Sent from my WT19i using xda app-developers app
Installer updated to version 1.2 with the new ADB and Fastboot included in Android SDK 23.0.2.
Installer updated to version 1.3 based on the Android SDK 24.0.2.
no matter what i do it stills says ABD is not reconizedf as an internal or external command. i even downloaded the whole stinking dev kit to make sure nothing missing in these little installers. made sure that a path was put still dose NOT work :/. and yes im running cmd prompt as adminastrator.
Nightmare-Rex420 said:
no matter what i do it stills says ABD is not reconizedf as an internal or external command. i even downloaded the whole stinking dev kit to make sure nothing missing in these little installers. made sure that a path was put still dose NOT work :/. and yes im running cmd prompt as adminastrator.
Click to expand...
Click to collapse
Have you tried running it from the C:\ADB path just in case? Maybe try PowerShell instead of the command prompt. I don't really know what else you can try if even the SDK is not working for you.
ajua said:
Have you tried running it from the C:\ADB path just in case? Maybe try PowerShell instead of the command prompt. I don't really know what else you can try if even the SDK is not working for you.
Click to expand...
Click to collapse
yes ive been trying both Shift open command prompt here, and aslso left click run as adminastrator and CD c:/abd both still says abd not reconized.
Nightmare-Rex420 said:
yes ive been trying both Shift open command prompt here, and aslso left click run as adminastrator and CD c:/abd both still says abd not reconized.
Click to expand...
Click to collapse
Try using PowerShell. Also, see if you are able to run the ADB that comes with the SDK but run it from the folder where it is located.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Setup, Preparation and Prerequisites
Open command prompt - Press Window Key + R, type in "cmd" (without the quotes), and hit enter.
USB Debugging - On your nexus player go to Settings > About > Tap on Build number 7 times. This will enable Developer options. Now go back to Settings > Developer options > Enable USB debugging
Enter bootloader mode - Hold the button on the bottom of the device when you plug in the power cable, or enable developer options and "adb reboot bootloader"
Once you are in fastboot mode, the light below nexus player will be blinking constantly. You can verify by using "fastboot devices"
ADB Installation
Download the full Android SDK here (scroll to the bottom of the page>DOWNLOAD FOR OTHER PLATFORMS>SDK Tools Only) or get a slimmed version containing only the essential components here
Extract the zip and place the android-sdk-windows folder on your desktop.
**If you chose to download the slimmed sdk skip to step 5**
Only if you downloaded the full sdk: Go into the android-sdk-windows folder and run SDK Manager.exe. Install the following packages (there are a total of 4 packages):
- Tools > Android SDK Tools, Android SDK Platform-tools
- Extras > Android Support Library, Google USB Driver
Only if you downloaded the full sdk: Go back into the android-sdk-windows directory, and you should see a new folder named platform-tools. If you don't see this new folder, repeat the step above.
To confirm that it is indeed working, open a command prompt window and enter the following commands:
Code:
cd Desktop/android-sdk-windows/platform-tools
adb version
If it displays "Android Debug Bridge version x.x.xx" it is working. If it is gives an error saying that adb is not a recognized command, it has not been successful. Carefully repeat the steps above if this is the case. Close the command prompt window when you are done.
Show File Extensions - Open a command prompt window and run "Control folders" (without the quotes). Go to the View tab and uncheck the "Hide extensions for known file types" option. This will help avoid confusion when renaming files.
Backup (Optional) - Unlocking the bootloader will completely wipe all data from the device. This includes apps, settings and even the contents of the internal storage (pictures, music, etc.). Copy all important files off the nexus player onto a PC or upload them to a cloud.
Driver Installation
Go to Device Manager, find the Android device, and select Update Driver Software.
Select Browse my computer for driver software
Select Let me pick from a list of device drivers on my computer
Selecting show all devices
Clicking have disk
Finally selecting Desktop\android-sdk-windows\extras\google\usb_driver\android_winusb.inf as the driver
Alternative you can also download and install the Universal ADB Driver.
Downloads
Root:
Android 7.X:
- Coming Soon-
Android 6.X:
http://cord-cutters.wonderhowto.com/how-to/root-nexus-player-0160218/
http://androidflagship.com/16765-root-nexus-player-android-6-0-marshmallow
Android 5.X:
Download the SuperSU zip below. Extract the zip file and you will have (root.img) to platform-tools folder located on your desktop within the android-sdk-windows folder.
SuperSU (Forum Thread) or SuperSU (Direct link)
Information
Rooting this device is actually quite a simple and easy process. Before you begin, it is recommended that you at least try to understand what each part of the process will do. Although this guide will elongate each step in order to show all of the details, the method used can be broken up into 2 main steps: Unlocking the Bootloader and Rooting. Each new step relies on the previous step to have been completed, and a basic summary of each part is:
Unlocking Bootloader: Opens the door to the internal memory of the device to be written on to. This allows you to flash images onto the main partitions of the device in future.
Rooting: You can gain root booting up root.img
1. Unlocking Bootloader
Turn the nexus player off. Then go into bootloader mode by holding the button on the bottom of the device when you plug in the power cable, or enable developer options and "adb reboot bootloader"
Plug nexus player into your PC, then open a command prompt window and type:
Code:
cd Desktop/android-sdk-windows/platform-tools
Code:
fastboot devices
This command will list the connected devices. If your nexus player serial number shows up you are good to go and may continue. If the nexus player is NOT listed this indicates that your drivers are not installed correctly. In order for you to continue you must fix your drivers so that your phone is listed under fastboot devices.
If the nexus player has been recognized by the command above, proceed to unlocking the bootloader with the following command:
Remember that this step will wipe EVERYTHING off the phone
OEM unlock twice
Code:
fastboot oem unlock
Code:
fastboot oem unlock
After you have done, please proceed onto the next section of the guide.
2. Installing a Custom Recovery
http://forum.xda-developers.com/nex...recovery-twrp-2-8-6-0-touch-recovery-t3114717
https://twrp.me/devices/asusnexusplayer.html
3. Rooting
Now that your nexus player has an unlocked bootloader, now this step is to gain root
Android 7.X
- coming soon -
Android 6.X
Require: TWRP, Custom boot.img and flashable supersu
(Refer to above link)
Android 5.0
Warning: This rooting guide is for Android 5.X only!
Boot (not flash) the root image which will give you root with the stock ROM
Confirm that you have downloaded the SuperSU zip from the downloads section above and you have extracted it and it is located in the platform-tools folder inside of the android-sdk-windows folder on your desktop.
Make sure the nexus player is in bootloader mode
Open a command prompt window and run the following commands:
Code:
cd Desktop/android-sdk-windows/platform-tools
Code:
fastboot boot root.img
This will install SuperSU on your device, once the command has completed continue.
Open SuperSU and update the binaries.
Keep in mind that the first boot may take longer than usual.
Congrats! Your nexus player now has an unlocked bootloader, and is rooted.
==================================================
How to flash factory image for Nexus Player?
1) Download image file for your nexus player - https://developers.google.com/android/nexus/images
2) Boot your Nexus device into fastboot mode.
3) On your computer, use 7zip to extract the .tgz file you downloaded from the Android Developer website. Use 7zip a second time to extract the .tar file you extracted from the .tgz. When you’re done, you should have a folder with several files in it.
4) Copy all of these files and paste them in the platform-tools folder in the Android SDK on your computer. If you followed the above tutorial, this should be under the C drive, then under Program Files (x86) on Windows. Linux users, you know where you put it.
5) If you have not already done so, connect your Nexus device to your computer. ADB and Fastboot commands should already work at this point if you’ve been following along.
There are two flash-all files. If you’re in Windows, you’ll want to double click the one that has the gear logo and says “Windows Batch File” on the right. If you’re on Linux, you’ll want to double click the flash-all.sh.
At this point a box should pop up and you should see the installation taking place. While this is going on, do not unplug your device for any reason. Let it do its thing.
6) Once the installation process as finished, your device will automatically reboot and you can now safely disconnect your device from your computer.
==================================================
Credits:
- Chainfire (SuperSU and Rooting guide)
- Chromium (Easy to understand and detailed guide format)
- DevinWatson (USB driver guide)
- androidauthority (Flash firmware image guide)
Nice guide.
What about installing BusyBox?
I have a USB OTG cable but the adapter is female on the available USB side...I am not sure how to go about connecting my laptop/PC to the NP in order to perform ADB commands. Do I need a special cable or is there another way?
arecad said:
I have a USB OTG cable but the adapter is female on the available USB side...I am not sure how to go about connecting my laptop/PC to the NP in order to perform ADB commands. Do I need a special cable or is there another way?
Click to expand...
Click to collapse
Don't use the USB OTG cable, use a micro USB cable (same kind of cable that comes with android phones)
I cannot believe I missed that, how embarrassing. Thanks for the response, now I can follow this guide. I was thinking too hard about the OTG cable being a necessary piece of the puzzle.
I am able to get to the bootloader with no problems, I've got ADB and Fastboot installed on my PC, as well as the drivers. However ADB doesn't pick up my NexusPlayer even though fastboot does. Thoughts?
See Attachments
EDIT: Nevermind, I was expecting different responses from adb/fastboot. When in the bootloader adb will not confirm a connection, only fastboot. Sorry for being a noob...
xDragonZ said:
1. Unlocking Bootloader
[*] Turn the nexus player off. Then go into bootloader mode by holding the button on the bottom of the device when you plug in the power cable, or enable developer options and "adb reboot bootloader"
[*] Plug nexus player into your PC, then open a command prompt window and type:
Code:
cd Desktop/android-sdk-windows/platform-tools
Code:
[COLOR="red"]adb devices[/COLOR]
This command will list the connected devices. If your nexus player serial number shows up you are good to go and may continue. If the nexus player is NOT listed this indicates that your drivers are not installed correctly. In order for you to continue you must fix your drivers so that your phone is listed under adb devices.
Click to expand...
Click to collapse
I could be mistaken, but when you're in the bootloader you're going to use FASTBOOT and not ADB commands. So therefore the command should be "fastboot devices" instead of "adb devices"?
midnightzak said:
I could be mistaken, but when you're in the bootloader you're going to use FASTBOOT and not ADB commands. So therefore the command should be "fastboot devices" instead of "adb devices"?
Click to expand...
Click to collapse
AFAIK ADB is for Android, and Fastboot is for bootloader.
But i have the oposite problem. Mine NP is getting recognized useing ADB when normaly booted, but when i am in fastboot mode, fastboot isent working. I get no output when run 'fastboot devivces'. I have both tried to set the NP in fastboot mode by using the hiod button and plug in power, and with adb rebbot bootloader.
Any one have a clue why adb works, but not fastboot?
Double check to see if you have the latest version of fastboot. I have read that if you don't have the most up to date version the NP is not recognized.
Sleeepy2 said:
Double check to see if you have the latest version of fastboot. I have read that if you don't have the most up to date version the NP is not recognized.
Click to expand...
Click to collapse
+1 this.
goxboxlive said:
AFAIK ADB is for Android, and Fastboot is for bootloader.
But i have the oposite problem. Mine NP is getting recognized useing ADB when normaly booted, but when i am in fastboot mode, fastboot isent working. I get no output when run 'fastboot devivces'. I have both tried to set the NP in fastboot mode by using the hiod button and plug in power, and with adb rebbot bootloader.
Any one have a clue why adb works, but not fastboot?
Click to expand...
Click to collapse
Have you re-installed the Google driver when you are booted in the bootloader? The driver needs to install twice: once when booted into Android, and once when booted into the bootloader
ADB fastboot for Mac Quick Question??
Hey guys does anyone have any idea on how this can be done on a Mac....I know I know. When I initially plug in my Nexus player with the micro usb, nothing happens on my mac or the Nexus so i am guessing that the drivers are not installed. How would i go about getting these for the Mac? I have already downloaded the slim version of the ADB and Fastboot files with the platform tools into a folder on my desktop named Andriod, so i have these already. And i know that if you hold the button down on the nexus and plug the power in it brings up the bootloader screen. I just need help with the commands in terminal and where to access the drivers from. Also, on the Nexus the Developer options have already been enabled and USB debugging has been turned on. If anyone can help, It would be much appricated! Just started to use terminal commands so yes i am a noob in this department . Thanks agin in advance.
-Jason
MrBoostinduced said:
Hey guys does anyone have any idea on how this can be done on a Mac....I know I know. When I initially plug in my Nexus player with the micro usb, nothing happens on my mac or the Nexus so i am guessing that the drivers are not installed. How would i go about getting these for the Mac? I have already downloaded the slim version of the ADB and Fastboot files with the platform tools into a folder on my desktop named Andriod, so i have these already. And i know that if you hold the button down on the nexus and plug the power in it brings up the bootloader screen. I just need help with the commands in terminal and where to access the drivers from. Also, on the Nexus the Developer options have already been enabled and USB debugging has been turned on. If anyone can help, It would be much appricated! Just started to use terminal commands so yes i am a noob in this department . Thanks agin in advance.
-Jason
Click to expand...
Click to collapse
http://developer.android.com/sdk/win-usb.html
"Note: If you're developing on Mac OS X or Linux, then you do not need to install a USB driver. To start developing with your device, read Using Hardware Devices."
http://developer.android.com/tools/device.html
Sleeepy2 said:
http://developer.android.com/sdk/win-usb.html
"Note: If you're developing on Mac OS X or Linux, then you do not need to install a USB driver. To start developing with your device, read Using Hardware Devices."
http://developer.android.com/tools/device.html
Click to expand...
Click to collapse
Hey Sleepy2, I just did a brief read through and it states this:
Set up your system to detect your device.
If you're developing on Windows, you need to install a USB driver for adb. For an installation guide and links to OEM drivers, see the OEM USB Drivers document.
If you're developing on Mac OS X, it just works. Skip this step.
If that is the case, what would you suggest doing next? Thanks again for helping!
MrBoostinduced said:
Hey Sleepy2, I just did a brief read through and it states this:
Set up your system to detect your device.
If you're developing on Windows, you need to install a USB driver for adb. For an installation guide and links to OEM drivers, see the OEM USB Drivers document.
If you're developing on Mac OS X, it just works. Skip this step.
If that is the case, what would you suggest doing next? Thanks again for helping!
Click to expand...
Click to collapse
Open a terminal, navigate to the directory where you downloaded fastboot and go ahead with the commands shown in the first post. You will probably have to add a "./" in front of the commands given that you are on a mac, e.g.,
Code:
fastboot devices
becomes
Code:
./fastboot devices
I seem to be having the same problem as goxboxlive. I have tried installing the drivers about 100x tried on several computers and rebooted many a time. The only thing I can think of from the posts in here was to update fastboot but I dled the android studio and I would assume that has the latest version in there? Otherwise I couldn't find somewhere to download just fastboot from. Any help or recommendations or where I can dl the latest fastboot?
---------- Post added at 02:28 PM ---------- Previous post was at 01:57 PM ----------
Follow up. Got it to work. In the guide it says after booting into fastboot to type "adb devices" in the console. You should instead type "fastboot devices" to see if you have the correct drivers and then go on from there. This worked for me, hopefully it will help someone else too.
knobbs said:
I seem to be having the same problem as goxboxlive. I have tried installing the drivers about 100x tried on several computers and rebooted many a time. The only thing I can think of from the posts in here was to update fastboot but I dled the android studio and I would assume that has the latest version in there? Otherwise I couldn't find somewhere to download just fastboot from. Any help or recommendations or where I can dl the latest fastboot?
---------- Post added at 02:28 PM ---------- Previous post was at 01:57 PM ----------
Follow up. Got it to work. In the guide it says after booting into fastboot to type "adb devices" in the console. You should instead type "fastboot devices" to see if you have the correct drivers and then go on from there. This worked for me, hopefully it will help someone else too.
Click to expand...
Click to collapse
Yep, i posted this earlier in the thread, kinda surprised OP hasn't updated it.
http://forum.xda-developers.com/showpost.php?p=58172001&postcount=7
midnightzak said:
I could be mistaken, but when you're in the bootloader you're going to use FASTBOOT and not ADB commands. So therefore the command should be "fastboot devices" instead of "adb devices"?
Click to expand...
Click to collapse
knobbs said:
In the guide it says after booting into fastboot to type "adb devices" in the console. You should instead type "fastboot devices" to see if you have the correct drivers and then go on from there. This worked for me, hopefully it will help someone else too.
Click to expand...
Click to collapse
midnightzak said:
Yep, i posted this earlier in the thread, kinda surprised OP hasn't updated it.
http://forum.xda-developers.com/showpost.php?p=58172001&postcount=7
Click to expand...
Click to collapse
To avoid further confusion, I've updated the post since the OP hadn't yet.
midnightzak said:
Yep, i posted this earlier in the thread, kinda surprised OP hasn't updated it.
http://forum.xda-developers.com/showpost.php?p=58172001&postcount=7
Click to expand...
Click to collapse
efrant said:
To avoid further confusion, I've updated the post since the OP hadn't yet.
Click to expand...
Click to collapse
Thank you, saw your post that time and wanted to change it but keep forgetting.
Currently working on some basic developer app for Nexus Player.
xDragonZ said:
Thank you, saw your post that time and wanted to change it but keep forgetting.
Currently working on some basic developer app for Nexus Player.
Click to expand...
Click to collapse
It's all good, wasn't terrible let to figure out, and if you're developing even more for the Nexus Player, the more power to ya! Keep it up!
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
I have LE2110. In Settings I've enabled "OEM Unlocking" and also "USB Debugging".
I also instsalled the proper USB drivers but think they are unecessary regardless.
I boot into Fastboot & connect to laptop withofficial USB cable.
From the folder where I installed Android SDK Platform Tools I open command prompt.
Type in fastboot oem unlock and it says 'waiting for devices'.
I've rebooted everything, tried a few times over several days but always same result.
Phone works perfect, no issues otherwise.
Any tips what to try next or possibly what I'm doing wrong?
Thank you
I have a global unlocked 9. I had to use this to unlock bl. Open your command window from this after it installs,make sure to add shortcut to desktop when installing. Then run unlock command. Worked for me back in April when I bought device.
"minimal_adb_fastboot_v1.4.3_setup.exe | by shimp208 for Utilities" https://androidfilehost.com?fid=746010030569952951
For me, I installed every driver while being in testsigning on ("bcdedit /set testsigning on" in cmd as administrator then reboot) and then I rebooted, turned testsigning off, rebooted again then it worked.
100 percent driver issue. Just reinstall the correct drivers and you'll be good to go.
Can you try to install this app on your computer and then try? pdanet this installs also the drivers for your phone. Otherwise try searching on the forum for the correct drivers.
Before any command you should try and see if your device is connected by doing in command prompt: fastboot devices
dotuletz said:
Can you try to install this app on your computer and then try? pdanet this installs also the drivers for your phone. Otherwise try searching on the forum for the correct drivers.
Before any command you should try and see if your device is connected by doing in command prompt: fastboot devices
Click to expand...
Click to collapse
Plus you can reboot edl through adb.
Hi there. We want to install f-droid on HTC U11 on Android 9. Function to enabling 'Unknown Sources' or 'Install Unknown Apps' isn’t available in dev mode!
We reckon you have to unlock the device to install f-droid. Unless spending already many hours we get stucked. Situation: Dev mode enabled + OEM unlocked
Installed Android File Transfer on Linux Mint 19.2 https://www.omgubuntu.co.uk/2017/11/android-file-transfer-app-linux device is shown on pc.
Made account on HTC website. https://www.htcdev.com/bootloader/unlock-instructions
Used Android_File_Transfer-cce42ee-x86_64.AppImage + executed
Started mobile in "download mode" went to ‘fastboot mode”
PC doesn’t show U11 in cli lsblk
Fastboot oem get_identifier_token - FAILED (remote: unknown command)
How on earth can one unlock this device?
[GUIDE] [LINUX] Installing ADB and Fastboot on Linux & Device Detection "Drivers"
[GUIDE] [LINUX] Installing ADB and Fastboot on Linux & Device Detection "Drivers" Installing ADB and Fastboot on Linux & ADB Drivers Tutorial For Debian-based distributions (Debian Ubuntu Mint etc.) Installing ADB CLI tool ( Android Debug Bridge...
forum.xda-developers.com
Hi Golv, we followed instructions in the link given. Now 1 step further we are stucked again. Could you please have a look on our comment here:
https://forum.xda-developers.com/t/...linux-device-detection-drivers.3478678/page-2