Database Users

[Q] Andriod 4.2.2 adb on linux

Hi,
Need latest adb and fastboot under linux which works for andriod 4.2.2. Whenever i tried to connect it says. I solved on windows by downloading the latest adb from xda site.
List of devices attached
0062bdd0d056b091 offline
Regards,
Lokesh

lokeshv said:
Hi,
Need latest adb and fastboot under linux which works for andriod 4.2.2. Whenever i tried to connect it says. I solved on windows by downloading the latest adb from xda site.
List of devices attached
0062bdd0d056b091 offline
Regards,
Lokesh
Click to expand...
Click to collapse
Same issue, any help would be great... the sdk says up to date.

I've attached the adb and fastboot binaries from the latest Android SDK for Linux. Also make sure you check the phone for the popup to confirm adding the PC's signature to the device's whitelist.

I assume you're using Ubuntu in which case android-tools is in the Ubuntu Repository for 12.10.
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
If you want a more update ADB and Fastboot use this ppa http://www.webupd8.org/2012/08/install-adb-and-fastboot-android-tools.html
I have the one from Ubuntu repository installed on 13.04 and it works fine with my 4.2.2 devices.
Also, like tuxdude said, make sure you have your PC whitelisted so it is able to connect via adb. New security feature in 4.2.2

Try disabling and re-enabling usb debugging while plugged in. It's the only way i got the rsa verification on osx, which before i had the offline device output message.

I had a same problem, and I found the solution.
If the adb the newest, and RSA windows doesn't appear on phone, check the .android directory (in your Home directory) ownership and permission. Mine was wrong, root was the owner.

Yoga 2 8' - 830L - probably erase bootloader - HELP !

hello, I hope that I write in the right place and I will not be scolded.
I have a big problem. I'll start from the beginning.
I did root my tablet and everything was OK.
Before root I made data backup in TWRP recovery.
I used a moment then something began to manifest errors.
That's why I thought that restore backup.
Everything I've done with the use 'IntelAndroid-FBRL-07-24-2015'.
When I restored a backup system will not boot.
He hang on the logo LENOVO and after a while tablet restarted.
I thought that restore everything as it was at the factory.
I downloaded "YT2-830L_USR_S000067_1410301707_WW21_ROW" and I launched the program "PhoneFlashTool_4.4.4.1_external_win32".
At the beginning everything was ok.
Then there was about 50/60 percent and jumped an error.. Unfortunately, I do not remember what.
The device was restarts and and appeared logo LENOVO + Subtitles "Boot Failed. EFI HARD DRIVE" "Boot Succeed - enter startup"
and then pops up
"VALLEYVIEW C0 PLATFORM
INTEL (R) ATOM ....
...
...
CONTINUE
SELECT LANGUAGE
> BOOT MANAGER
> DEVICE MANAGER
> BOOT MAINTANCE MANAGER
"
I tried again to upload the original tablet software..
and so it looked like:
"12/25/15 23:18:44.251 INFO : Phone Flash Tool V 4.4.4-1 Win32 External (build on Mon Apr 28 09:56:35 UTC 2014)
12/25/15 23:18:44.251 INFO : Using xFSTK version: 1.5.3
12/25/15 23:18:44.361 INFO : Using Android Debug Bridge version 1.0.31
12/25/15 23:18:44.361 INFO : OS version detected: Windows 8 (x64)
12/25/15 23:18:44.580 INFO : Adb and fastboot binaries OK
12/25/15 23:18:44.580 INFO : Phone Flash Tool initialized successfully
12/25/15 23:18:44.595 INFO : Loading Flash file ...
12/25/15 23:18:44.595 INFO : Ready to flash!
12/25/15 23:19:28.233 INFO : Loading Flash file (C:/Users/X/Desktop/FLASH_LENOVO/YT2-830L_USR_S000067_1410301707_WW21_ROW/YT2-830L_USR_S000067_1410301707_WW21_ROW/YT2_8_row_lte-blankphone-user-YT2-830L_USR_S000067_1410301707_WW21_ROW/flash.xml)
12/25/15 23:19:28.233 INFO : GP_Flag is set to 0x80000045
12/25/15 23:19:28.249 INFO : Ready to flash!
12/25/15 23:19:30.689 INFO : Port 1/1: Flashing OS
12/25/15 23:19:30.689 INFO : Port 1/1: fastboot -s BaytrailF0B3F8A3 -S 500M flash osloader "C:/Users/X/Desktop/FLASH_LENOVO/YT2-830L_USR_S000067_1410301707_WW21_ROW/YT2-830L_USR_S000067_1410301707_WW21_ROW/YT2_8_row_lte-blankphone-user-YT2-830L_USR_S000067_1410301707_WW21_ROW/efilinux.efi"
12/25/15 23:19:32.830 INFO : Port 1/1: fastboot -s BaytrailF0B3F8A3 -S 500M boot "C:/Users/X/Desktop/FLASH_LENOVO/YT2-830L_USR_S000067_1410301707_WW21_ROW/YT2-830L_USR_S000067_1410301707_WW21_ROW/YT2_8_row_lte-blankphone-user-YT2-830L_USR_S000067_1410301707_WW21_ROW/droidboot.img"
12/25/15 23:19:35.537 INFO : Port 1/1: sleep 25000 ms"
AND THE TABLET RESTART AND SEE AGAIN WINDOW
"VALLEYVIEW C0 PLATFORM
INTEL (R) ATOM ....
...
...
CONTINUE
SELECT LANGUAGE
> BOOT MANAGER
> DEVICE MANAGER
> BOOT MAINTANCE MANAGER
"
(in THE PROGRAMME IS 23 %)
So I run again tablet and TO FASTBOOT AND IN THE PROGRAM POPS ERROR
"12/25/15 23:20:00.538 INFO : Port 1/1: fastboot -s BaytrailF0B3F8A3 -S 500M oem wipe ESP
12/25/15 23:23:32.881 WARNING: Port 1/1: Failed to execute ""C:/Program Files (x86)/Intel/Phone Flash Tool/fastboot.exe" -s BaytrailF0B3F8A3 -S 500M oem wipe ESP":
< waiting for device >
...
FAILED (remote: unknown command)
finished. total time: 0.003s
12/25/15 23:23:34.884 WARNING: Port 1/1: Retry to execute fastboot -s BaytrailF0B3F8A3 -S 500M oem wipe ESP
12/25/15 23:23:34.978 WARNING: Port 1/1: Failed to execute ""C:/Program Files (x86)/Intel/Phone Flash Tool/fastboot.exe" -s BaytrailF0B3F8A3 -S 500M oem wipe ESP":
...
FAILED (remote: unknown command)
finished. total time: -0.000s
12/25/15 23:23:36.994 WARNING: Port 1/1: Failed to execute non mandatory command fastboot -s BaytrailF0B3F8A3 -S 500M oem wipe ESP, ignoring error
12/25/15 23:23:36.994 INFO : Port 1/1: fastboot -s BaytrailF0B3F8A3 -S 500M oem start_partitioning
12/25/15 23:23:37.088 WARNING: Port 1/1: Failed to execute ""C:/Program Files (x86)/Intel/Phone Flash Tool/fastboot.exe" -s BaytrailF0B3F8A3 -S 500M oem start_partitioning":
...
FAILED (remote: unknown command)
finished. total time: 0.000s
12/25/15 23:23:39.098 WARNING: Port 1/1: Retry to execute fastboot -s BaytrailF0B3F8A3 -S 500M oem start_partitioning
12/25/15 23:23:39.207 WARNING: Port 1/1: Failed to execute ""C:/Program Files (x86)/Intel/Phone Flash Tool/fastboot.exe" -s BaytrailF0B3F8A3 -S 500M oem start_partitioning":
...
FAILED (remote: unknown command)
finished. total time: -0.000s
12/25/15 23:23:41.223 ERROR : Port 1/1: Flash failure"
ON THE TABLET IS "FASTBOOT STARTING ..."
when I choose continue on this screen
VALLEYVIEW C0 PLATFORM
INTEL (R) ATOM ....
...
...
CONTINUE
SELECT LANGUAGE
> BOOT MANAGER
> DEVICE MANAGER
> BOOT MAINTANCE MANAGER"
i see this window WHERE WRITE:
"BOOT FAILED. EFI HARD DISK"
"BOOT SUCCEED - ENTER SETUP"
if anyone knows how to solve , how to restore the tablet to work please help !!!
SORRY I did not give photos, but I'm new and I could not INSERT...

progdvb said:
hello, I hope that I write in the right place and I will not be scolded.
Click to expand...
Click to collapse
you were on Lollipop when you bricked and now you are trying to flash a kitkat rom, this will not work as the kiktak rom files (IA32) pushed by the Phone Flash tool are not recognized by the Lollipop bios (x64).
since there is no publicly available (leaked) lollipop stock rom for the 830L model you will have to:
1. downgrade first your bios to the kitkat version using the steps in here, do the steps in 'how to use'
2. now flash your kitkat stock rom, remember to set your country code when finished flashing, on your first boot, or you will fail in the future when attempting to update using an OTA
3. optional, update to lollipop using the OTA when prompted by your (now) running kitkat android

ionioni said:
you were on Lollipop when you bricked and now you are trying to flash a kitkat rom, this will not work as the kiktak rom files (IA32) pushed by the Phone Flash tool are not recognized by the Lollipop bios (x64).
since there is no publicly available (leaked) lollipop stock rom for the 830L model you will have to:
1. downgrade first your bios to the kitkat version using the steps in here, do the steps in 'how to use'
2. now flash your kitkat stock rom, remember to set your country code when finished flashing, on your first boot, or you will fail in the future when attempting to update using an OTA
3. optional, update to lollipop using the OTA when prompted by your (now) running kitkat android
Click to expand...
Click to collapse
I tried this way now and the program stay in position "waiting for access to root shell".
It takes a fewww minutes...
in the video demo it quickly went...
what now?
ON THE TABLET IS WINDOW AND WRITE "CMD 'STOP_PARTITIONING' COMPLETE.

progdvb said:
I tried this way now and the program stay in position "waiting for access to root shell".
It takes a fewww minutes...
in the video demo it quickly went...
what now?
Click to expand...
Click to collapse
if it went to that point the bios restoring has not yet started (yet it confirms you are on lollipop bios) so you can close the tool exe window safely
this can mean one of these things:
1. (most likely) your drivers need to be reinstalled, download from here and install both files in the zip (accepting whatever it prompts you and using defaults) and reboot at the end your pc, then try again the downgrading the bios, if it still hangs on that 'waiting for root shell' try when you get ther and some seconds have passed to unplug and replug the usb to force a redetection of the new usb mode (windows does it automatically, never met a case where it didn't yet you can try it)
2. (unlikely) you are using windows in a virtual environment such as virtualbox or vmware (are you?) and it did not detected the usb changing mode, if that is the case (only if you are using windows in virtualbox, i doubt) unplug and replug the usb when it says 'waiting for root shell'
3. (almost impossible) your usb controller is bricked

I did reinstalling drivers.
Went two steps further.
[pc] transfering control to yogatab device for bios restoring.
AND Unfortunately, he jumped error:
adb server is out of date. killing...
abd server didnt ACK
*failed to start daemon *
error:

progdvb said:
I did reinstalling drivers.
Went two steps further.
[pc] transfering control to yogatab device for bios restoring.
AND Unfortunately, he jumped error:
adb server is out of date. killing...
abd server didnt ACK
*failed to start daemon *
error:
Click to expand...
Click to collapse
but the tablet rebooted?
NEVER POWER OFF YOUR TAB AFTER IT SAYS "TRANSFERING CONTROL" ALWAYS WAIT 4-5 MINUTES BEFORE TRYING TO REBOOT THE TAB IF YOU GOT DISCONNECTED SOMEHOW!
that means the bios restore could have been started and you must wait 4-5 minutes and ONLY if it doesn't reboot by itself in 4-5 minutes then you can try to reboot
you must take care with this as if the bios restore is started (and you were disconnected meaning no more messages from your tab) if you power off by force your tab you can hard-brick and nothing can be done to save it (you must send it to a service).
READ THE INSTRUCTIONS IN THE DOWNGRADING POST!
do this:
UNINSTALL everything: adb/fastboot, drivers installed in the past, Intel Phone Flash Tool, everything you installed related to the tab
REBOOT
INSTALL the two files provided in the link
REBOOT
TRY AGAIN to downgrade
also, you should use when flashing your kitkat a more recent stock rom (the one you used is old) download extract and use this (after you managed to downgrade the bios of course)

ionioni said:
but the tablet rebooted?
NEVER POWER OFF YOUR TAB AFTER IT SAYS "TRANSFERING CONTROL"
that means the bios restore could have been started and you must wait 4-5 minutes and ONLY if it doesn't reboot by itself in 4-5 minutes then you can try to reboot
you must take care with this as if the bios restore is started (and you were disconnected meaning no more messages from your tab) if you power off by force your tab you can hard-brick and nothing can be done to save it (you must send it to a service).
READ THE INSTRUCTIONS IN THE DOWNGRADING POST!
Click to expand...
Click to collapse
Yes, I wait 5-6minute and power off tablets.
he did not restarted itself.
Now I try uninstall, and install program and all drivers.
--------------------------------------------------------------------
OK,
I uninstalled and install anew driver, I open program and now is hang on
[pc] transfering control to yogatab device for bios restoring.
========================================
adb server is out of date. killing...
so this situation has been going 5min

progdvb said:
Yes, I wait 5-6minute and power off tablets.
he did not restarted itself.
Now I try uninstall, and install program and all drivers.
Click to expand...
Click to collapse
ok, read above i edited some stuff... the bios restoring is a safe process (as long as you don't do stupid things) but you have issues on your pc, solve them first
after you downgrade the bios use the stock rom i linked in the prev post for your kitkat stock rom flashing, the one you used is old (should work but you will wait forever after for the ota's)
---------- Post added at 11:24 ---------- Previous post was at 11:13 ----------
progdvb said:
Yes, I wait 5-6minute and power off tablets.
he did not restarted itself.
Now I try uninstall, and install program and all drivers.
--------------------------------------------------------------------
OK,
I uninstalled and install anew driver, I open program and now is hang on
[pc] transfering control to yogatab device for bios restoring.
========================================
adb server is out of date. killing...
so this situation has been going 5min
Click to expand...
Click to collapse
reboot and go to the intel phone flash tool folder C:\Program Files (x86)\Intel\Phone Flash Tool Lite and delete the adb.exe file inside and try again
you have some adb.exe (old) file that starts automatically and that makes things go wrong (have you uninstalled your stuff?) also make sure you run the exe as Administrator

ionioni said:
ok, read above i edited some stuff... the bios restoring is a safe process (as long as you don't do stupid things) but you have issues on your pc, solve them first
after you downgrade the bios use the stock rom i linked in the prev post for your kitkat stock rom flashing, the one you used is old (should work but you will wait forever after for the ota's)
---------- Post added at 11:24 ---------- Previous post was at 11:13 ----------
reboot and go to the intel phone flash tool folder C:\Program Files (x86)\Intel\Phone Flash Tool Lite and delete the adb.exe file inside and try again
you have some adb.exe (old) file that starts automatically and that makes things go wrong (have you uninstalled your stuff?) also make sure you run the exe as Administrator
Click to expand...
Click to collapse
OK, I used other computer. Its work.
Program passed with no errors.
Now I have to use 'Phone Flash Tool Lite',
upload a rom from the link you gave me and everything should be ok ?

progdvb said:
OK, I used other computer. Its work.
Program passed with no errors.
Now I have to use 'Phone Flash Tool Lite',
upload a rom from the link you gave me and everything should be ok ?
Click to expand...
Click to collapse
yes, use the rom i linked extract and flash from dnx mode ("fastboot starting" message on screen pwr+volup+voldown to start in dnx)

ionioni said:
yes, use the rom i linked extract and flash from dnx mode ("fastboot starting" message on screen pwr+volup+voldown to start in dnx)
Click to expand...
Click to collapse
when I had to choose a country that updates work later?
and how?
during the first run I introduced tablet in dialer ####6020# ?
next choose my country and tablet restart and next #### 59930# to check the chosen country?

progdvb said:
when I had to choose a country that updates work later?
and how?
during the first run I introduced tablet in dialer ####6020# ?
next choose my country and tablet restart and next #### 59930# to check the chosen country?
Click to expand...
Click to collapse
you open Contacts app and input there

ionioni said:
you open Contacts app and input there
Click to expand...
Click to collapse
OK. For now uploads a rom .
By the way, I ask yet .
Is it possible for me I've loaded rom that will allow me to call from the tablet?
I read this article but I could not quite understand everything
http://forum.xda-developers.com/thi...guide-make-lenovo-tablet-yoga-2-830l-t2950933
Do you know where can I download Lenovo Tablet Yoga 2 830LC to fit what you gave me?
the manual says to replace the file called "esp.img"..

progdvb said:
OK. For now uploads a rom .
By the way, I ask yet .
Is it possible for me I've loaded rom that will allow me to call from the tablet?
I read this article but I could not quite understand everything
http://forum.xda-developers.com/thi...guide-make-lenovo-tablet-yoga-2-830l-t2950933
Do you know where can I download Lenovo Tablet Yoga 2 830LC to fit what you gave me?
the manual says to replace the file called "esp.img"..
Click to expand...
Click to collapse
this is the 830LC stock kitkat rom flash it and see...

ionioni said:
this is the 830LC stock kitkat rom flash it and see...
Click to expand...
Click to collapse
THE TABLET IS WORKING !!!!!!
YOY are GREAT !!!!!!!!!!!!!!!!!!!!!!!!!!!!
Tell me again, which country should I choose for Polish ?
the same Chinese stamps and some strange abbreviations are...

progdvb said:
THE TABLET IS WORKING !!!!!!
YOY are GREAT !!!!!!!!!!!!!!!!!!!!!!!!!!!!
Tell me again, which country should I choose for Polish ?
the same Chinese stamps and some strange abbreviations are...
Click to expand...
Click to collapse
the abbreviations are the standard iso country alpha 2 letter code https://en.wikipedia.org/wiki/ISO_3166-1
if you don't have PL then chose a neighbour one, not sot important (this is not the language in which your Android interface will be shown that you can set with the Language on your Settings)

ionioni said:
the abbreviations are the standard iso country alpha 2 letter code https://en.wikipedia.org/wiki/ISO_3166-1
if you don't have PL then chose a neighbour one, not sot important (this is not the language in which your Android interface will be shown that you can set with the Language on your Settings)
Click to expand...
Click to collapse
ok . I found a country close to the Polish (germany)
if I set this country I will be able to use the system updates ?
I will be able to upgrade to 5.0 android?

progdvb said:
ok . I found a country close to the Polish (germany)
if I set this country I will be able to use the system updates ?
I will be able to upgrade to 5.0 android?
Click to expand...
Click to collapse
yes, as i told you is not so important, whatever you will chose you will be able to complete updates (to lollipop included)

ionioni said:
yes, use the rom i linked extract and flash from dnx mode ("fastboot starting" message on screen pwr+volup+voldown to start in dnx)
Click to expand...
Click to collapse
if I install rom which allows ringing ,
whether later I will be able to update it eg. to 5.0
and still I could call from tablet ?

progdvb said:
if I install rom which allows ringing ,
whether later I will be able to update it eg. to 5.0
and still I could call from tablet ?
Click to expand...
Click to collapse
you can update, if it works in kitkat will work in lollipop

[PSA/FIX] Newest adb doesn't work on WinXP + 5x USB drivers that work

I happen to update platform-tools in the Android SDK from version 23.1 to version 24 on an older PC.
The newest adb.exe included with v24 no longer works on WinXP.
You will get the following error upon startup:
adb.exe - Entry Point Not Found
The procedure entry point WSAPoll could not be located in the dynamic link library WS2_32.dll.
Click to expand...
Click to collapse
In case anyone is curious, I tracked the change down to this one:
https://android-review.googlesource.com/#/c/203387/
ADB
I've attached the v23.1 adb and fastboot to this post in case someone needs the previous version (which works fine with 5x up to at least MTC20F)
Just unzip and you can use adb/fastboot from the resulting platform-tools-v23.1 directory or copy them over to where your normal platform-tools directory is.
USB drivers for 5x
I also included USB drivers that work with 5x. These should work for 32/64-bit for winxp and vista. Win7 is maybe, haven't tested.
They WILL NOT work with win8 and above due to changes in driver enforcement. I am not sure about win8.x but on win10, there is a built-in driver that works with adb. To get bootloader/fastboot driver, just allow win10 to search for drivers. It will load Marshall London Bootloader Interface. This is for a different phone from music company Marshall, but it works fine since it is an Android-based device.
I could never find one official driver from google or lg that would work with adb inside android, adb inside twrp, adb sideload inside stock recovery, and fastboot.
I stopped worrying about why it works for other people and just fixed the problem myself.

Not sure if it matters to that many people these days, but it was confirmed the change in adb is not a bug and will persist going forward, so if you ever need to run adb on a WinXP box or emulator, you'll need to retrieve platform-tools-23.1 or earlier.

WinXP compatible platform-tools also could be downloaded from official repository:
http://dl-ssl.google.com/android/repository/platform-tools_r23.1.0-windows.zip

Thank you so much for this sfhub. This was driving me crazy getting bootloader access with Win 7. Updated to the driver you linked and worked great. I guess most people out there are using Win 8 or 10 now? Minblowing that so few use 7.

Greefus said:
Thank you so much for this sfhub. This was driving me crazy getting bootloader access with Win 7. Updated to the driver you linked and worked great. I guess most people out there are using Win 8 or 10 now? Minblowing that so few use 7.
Click to expand...
Click to collapse
Actually Windows 7 is still installed on nearly half of all desktop and laptop computers: https://www.netmarketshare.com/operating-system-market-share.aspx?qprid=10&qpcustomd=0. Did the most recent SDK drop support for it?

For anyone who wants to use adb on the latest version of Android Studio running on Windows XP use the adb .exe from version 23 and paste it into the platform tool folder. Keep a copy of the new adb.exe just in case you need it. No need to use the entire v23 platform tool folder.

The references in this thread have so far appear to refer to latest adb compatibility, particularly for Windows XP.
Does the latest fastboot still work fine with Windows XP? If not, what was the last known-good or thought to be last known-good version for Windows XP?

Hi
The adb from the v2.3.1 works fine with my win xp, thank you for the file.

Hello,
I am another WinXP user facing the error
"adb.exe - Entry Point Not Found. The procedure entry point WSAPoll could not be located in the dynamic link library WS2_32.dll."
@sfhub & @Sintetix
Thanks for the info and provide the latest version supported by XP ...
Are you aware of any important changes / additions in the future versions to be concerned of?
Regards
---------- Post added at 11:16 ---------- Previous post was at 10:47 ----------
Just to let you know,
C:\v23.1>adb devices
List of devices attached
adb server is out of date. killing...
error: protocol fault (couldn't read status): Invalid argument
error: could not install *smartsocket* listener: cannot bind to 127.0.0.1:5037:
I am trying to connect an Asus Transformer tablet with "MTP file transfer" mode on WinXP Service Pack 3 laptop... cable is fine and the plan is to move from custom ROM (Android 6.0) to Stock (JellyBean) ... Something I already did few years ago having Win10 (I have the receipe used then)
I think I better get a fresh Win7 on my primary Win10 PC and start from there... I never liked W10 anyway ... and since I did mods to [finally &effectively] stop the [annoying, unwanted & plenty of bugs] Win10 updates ... I got funny errors when using dev stuff ... even DotNet ...
And I need to think a better O.S for the XP PC ...
Time to change. Regards

Before jumping to my major O.S actions,
I gave a chance to my Asus Transformer tablet with another cable under the W10 PC and the latest adb (r29.0.2-win) and this second time it worked fine ...
The first time and first cable did not work (reason that drove me to the WinXP PC thinking the cause was Win10)
fastboot devices
was literally returning
???????????? fastboot
But this second time with another cable
fastboot devices
returned
BLAxxIDxxSTRING fastboot
And I was finally able to perform the format and flash series of commands to return my tablet to the stock ROM ...
As I understand this thread is about WinXP, for testing purposes, I hooked my fresh flashed tablet to the WinXP PC with the successful spare cable, and
adb devices
got again
List of devices attached
adb server is out of date. killing...
error: protocol fault (couldn't read status): Invalid argument
error: could not install *smartsocket* listener: cannot bind to 127.0.0.1:5037
Certainly I don't have the explanation of this, but I can tell you is not because a faulty cable or something related to the tablet.
And something scary to add: the first cable looks in good shape and is the one used every day to charge the tablet without any delays or issues ...
Hope someone find this useful and provide more insight. Regards

Nexus 6P not recognized via adb devices on Mac

Hi everyone,
I have a Nexus 6P which simply refuses to connect via USB on my Mac (i.e. it doesn't show up as a valid device under adb devices or via Android File Transfer). I believe it was working at some point but it seems to have stopped now. Might be worth noting, I did try connecting it to my car's charger a few months ago but had the worst time with it, it would charge and disconnect every few seconds (may or may not be relevant in this case as it pertains to the USB). I tried a different charger and it works fine with it though.
I have tried a lot of different things (which I'll list below) but have had no luck getting my Nexus 6P being recognized as a device when I connect it to my Mac (or any other). I do have the Developer settings enabled and I am able to switch to MTP but I never get the prompt to change USB mode. Anytime I connect my device, adb devices doesn't list it at all. I tried ADB File transfer as well and that also says "Please connect your device".
Here are some of the things I have tried so far:
1. Used different cables - no luck
2. Used a different mac - no luck
3. Tried a different Nexus 6P with my cable, it works fine (so it is not a cable issue)
4. Tried a different Nexus 6P with my mac, it works fine (so my Mac seems to be OK too)
5. Restarted in recovery mode - no luck
6. Tried removing a bunch of apps in case there was something conflicting - no luck so far
7. Chatted up Google support - They couldn't tell me much outside of the last option - Factory Reset - I have been holding off on that since I want to be able to transfer my files out first but I really want to avoid having to try that before exhausting all other options. They did offer to replace with a refurb'ed device but I had to decline that.
I did create a bug report dump using the device to see if anything interesting showed up and the only thing noticeable there is an exception related to USB. I am putting that info here in case it is useful in helping with this.
Code:
DUMP OF SERVICE usb:
USB Manager State:
USB Device State:
mCurrentFunctions: mtp,adb
mCurrentFunctionsApplied: true
mConnected: false
mConfigured: false
mUsbDataUnlocked: false
mCurrentAccessory: null
Kernel state: DISCONNECTED
Kernel function list: mtp,ffs
USB Debugging State:
Connected to adbd: true
Last key received: null
User keys:
IOException: java.io.FileNotFoundException: /data/misc/adb/adb_keys: open failed: ENOENT (No such file or directory)
System keys:
IOException: java.io.FileNotFoundException: /adb_keys: open failed: ENOENT (No such file or directory)
USB Host State:
USB Port State:
otg_default: port=UsbPort{id=otg_default, supportedModes=dual}, status=UsbPortStatus{connected=true, currentMode=ufp, currentPowerRole=sink, currentDataRole=device, supportedRoleCombinations=[source:host, sink:device]}, canChangeMode=true, canChangePowerRole=false, canChangeDataRole=false
USB Audio Devices:
USB MIDI Devices:
Settings for user 0:
Device permissions:
Accessory permissions:
Device preferences:
Accessory preferences:
Any help here is really appreciated! Thanks

desimunda42 said:
Code:
USB Debugging State:
Connected to adbd: true
Last key received: null
User keys:
IOException: java.io.FileNotFoundException: /data/misc/adb/adb_keys: open failed: ENOENT (No such file or directory)
System keys:
IOException: java.io.FileNotFoundException: /adb_keys: open failed: ENOENT (No such file or directory)
Click to expand...
Click to collapse
That seems suspicious. Was this taken while the phone was connected to your mac?
Here's my phone's dump while NOT connected to a computer
Code:
USB Manager State:
USB Device State:
mCurrentFunctions: mtp,adb
mCurrentFunctionsApplied: true
mConnected: false
mConfigured: false
mUsbDataUnlocked: false
mCurrentAccessory: null
Kernel state: DISCONNECTED
Kernel function list: mtp,ffs
USB Debugging State:
Connected to adbd: true
[COLOR="red"] Last key received: blahblahblahblah (not null)
User keys: blahblahblahblah (no exception)
[/COLOR] System keys:
IOException: java.io.FileNotFoundException: /adb_keys: open failed: ENOENT (No such file or directory)
Here it is when connected to computer
Code:
DUMP OF SERVICE usb:
USB Manager State:
USB Device State:
mCurrentFunctions: mtp,adb
mCurrentFunctionsApplied: true
[COLOR="red"] mConnected: true
mConfigured: true
[/COLOR] mUsbDataUnlocked: false
mCurrentAccessory: null
[COLOR="red"] Kernel state: CONFIGURED
[/COLOR] Kernel function list: mtp,ffs
USB Debugging State:
Connected to adbd: true
[COLOR="Red"] Last key received: blahblahblahblah (not null)
User keys: blahblahblahblah (no exception)
[/COLOR] System keys:
IOException: java.io.FileNotFoundException: /adb_keys: open failed: ENOENT (No such file or directory)
Are you on a custom rom? Do you get an authorization prompt if you call "adb device" after doing "Revoke USB debugging authorizations" from Develop options?

adotkdotjh said:
That seems suspicious. Was this taken while the phone was connected to your mac?
Are you on a custom rom? Do you get an authorization prompt if you call "adb device" after doing "Revoke USB debugging authorizations" from Develop options?
Click to expand...
Click to collapse
I wasn't connected to my Mac at the time I pulled the report (I confirmed by repeating it just now and still get that 'FileNotFoundException" in the logs for USB device. I don't have a custom rom, I have the standard OEM from the Google Store and didn't do anything else with it.
Also, I did revoke the USB debugging auth multiple times and inspite of that I never get any prompt when I connect.
I also got the report while connected to the Mac and am still seeing the same exception:
Code:
DUMP OF SERVICE usb:
USB Manager State:
USB Device State:
mCurrentFunctions: mtp,adb
mCurrentFunctionsApplied: true
mConnected: false
mConfigured: false
mUsbDataUnlocked: false
mCurrentAccessory: null
Kernel state: DISCONNECTED
Kernel function list: mtp,ffs
USB Debugging State:
Connected to adbd: true
Last key received: null
User keys:
IOException: java.io.FileNotFoundException: /data/misc/adb/adb_keys: open failed: ENOENT (No such file or directory)
System keys:
IOException: java.io.FileNotFoundException: /adb_keys: open failed: ENOENT (No such file or directory)
USB Host State:
USB Port State:
otg_default: port=UsbPort{id=otg_default, supportedModes=dual}, status=UsbPortStatus{connected=true, currentMode=ufp, currentPowerRole=sink, currentDataRole=device, supportedRoleCombinations=[source:host, sink:device]}, canChangeMode=true, canChangePowerRole=false, canChangeDataRole=false
USB Audio Devices:
USB MIDI Devices:
Settings for user 0:
Device permissions:
Accessory permissions:
Device preferences:
Accessory preferences:

desimunda42 said:
Hi everyone,
I have a Nexus 6P which simply refuses to connect via USB on my Mac (i.e. it doesn't show up as a valid device under adb devices or via Android File Transfer). I believe it was working at some point but it seems to have stopped now. Might be worth noting, I did try connecting it to my car's charger a few months ago but had the worst time with it, it would charge and disconnect every few seconds (may or may not be relevant in this case as it pertains to the USB). I tried a different charger and it works fine with it though.
I have tried a lot of different things (which I'll list below) but have had no luck getting my Nexus 6P being recognized as a device when I connect it to my Mac (or any other). I do have the Developer settings enabled and I am able to switch to MTP but I never get the prompt to change USB mode. Anytime I connect my device, adb devices doesn't list it at all. I tried ADB File transfer as well and that also says "Please connect your device".
Here are some of the things I have tried so far:
1. Used different cables - no luck
2. Used a different mac - no luck
3. Tried a different Nexus 6P with my cable, it works fine (so it is not a cable issue)
4. Tried a different Nexus 6P with my mac, it works fine (so my Mac seems to be OK too)
5. Restarted in recovery mode - no luck
6. Tried removing a bunch of apps in case there was something conflicting - no luck so far
7. Chatted up Google support - They couldn't tell me much outside of the last option - Factory Reset - I have been holding off on that since I want to be able to transfer my files out first but I really want to avoid having to try that before exhausting all other options. They did offer to replace with a refurb'ed device but I had to decline that.
I did create a bug report dump using the device to see if anything interesting showed up and the only thing noticeable there is an exception related to USB. I am putting that info here in case it is useful in helping with this.
Code:
DUMP OF SERVICE usb:
USB Manager State:
USB Device State:
mCurrentFunctions: mtp,adb
mCurrentFunctionsApplied: true
mConnected: false
mConfigured: false
mUsbDataUnlocked: false
mCurrentAccessory: null
Kernel state: DISCONNECTED
Kernel function list: mtp,ffs
USB Debugging State:
Connected to adbd: true
Last key received: null
User keys:
IOException: java.io.FileNotFoundException: /data/misc/adb/adb_keys: open failed: ENOENT (No such file or directory)
System keys:
IOException: java.io.FileNotFoundException: /adb_keys: open failed: ENOENT (No such file or directory)
USB Host State:
USB Port State:
otg_default: port=UsbPort{id=otg_default, supportedModes=dual}, status=UsbPortStatus{connected=true, currentMode=ufp, currentPowerRole=sink, currentDataRole=device, supportedRoleCombinations=[source:host, sink:device]}, canChangeMode=true, canChangePowerRole=false, canChangeDataRole=false
USB Audio Devices:
USB MIDI Devices:
Settings for user 0:
Device permissions:
Accessory permissions:
Device preferences:
Accessory preferences:
Any help here is really appreciated! Thanks
Click to expand...
Click to collapse
I usually only get the key prompt for ADB authorzation when I connect my device and type "adb devices"..... If worse comes to worse, You can restore your phone to factory settings without wiping your sd card. Then you could test that option with compromising your data. Just flash each image from the archive yourself when restoring the firmware as opposed to using the flash-all scipt, or resetting the phone from settings... DO NOT flash the "userdata.img" included in the factory firmware archive or issue the command "fastboot format userdata" during the restore process and all of your files will be fine. This may be an option as long as fastboot is still functional on your device. Ive come across so many different devices in so many different conditions over the years, as long as the device could power on and the usb port was functional, fasboot has worked time and time again.
PS adb on Mac can be a bit tricky especially if this is the first time youre attempting to o install and use it. Unless you set the correct enviornment variables during the install process, you will oly be able to access adb from inside the folder that its stored in on your mac. Youll have to pull up your terminal and and direct it to the folder containing adb and fastboot. Its usually ina a folder called "platform-tools" Which can be found in the dictory in whch you installed the Android SDK or SDK Tools packages... Now that I think about it, you have to download adb from the SDK package I just mentioned. After doing so, youll find the platform tools folder and it should contain what you need. As long as java is correctly installed on your mac then everything should work once you issue the "adb devices" command in a terminal session thats points at the "platform-tools" folder. YOU ALSO HAVE TO HAVE JDK INSTALLED in order for it to work with your device. I just looked at what you posted and it looks like youred missing JDK"...
If you havent done any of this yet the thats the problem. If everything I just typed seems confusing then you can try this which explains everything you need to do to set up adb a whole lot better than my attempt above lol buts its going to take some time to accomplish https://seo-michael.co.uk/how-to-setup-adb-on-os-x/
or
You can also install and configure adb a whole lot easier by issuing the following commands from within your mac terminal.... (This will install Brew on your Mac, if you arent familiar with what it is, Its a software distrobution platform. Sort of like git hub and linux software repos. When in doubt, do a little reading first. It'll solve all your problems....
-Install Brew - Copy and paste this command into a mac terminal and follow the prompts that show up.
/usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"
-Once that finishes, next use this command
brew update && brew cask install java
-Once that is complete enter this last command
brew install android-platform-tools
Those 3 commands will do 99 percent of the work. When its done just find the platform tools folder and go from there. Hope this helps.

Sass86oh said:
PS adb on Mac can be a bit tricky especially if this is the first time youre attempting to o install and use it. Unless you set the correct enviornment variables during the install process, you will oly be able to access adb from inside the folder that its stored in on your mac. Youll have to pull up your terminal and and direct it to the folder containing adb and fastboot. Its usually ina a folder called "platform-tools" Which can be found in the dictory in whch you installed the Android SDK or SDK Tools packages... Now that I think about it, you have to download adb from the SDK package I just mentioned. After doing so, youll find the platform tools folder and it should contain what you need. As long as java is correctly installed on your mac then everything should work once you issue the "adb devices" command in a terminal session thats points at the "platform-tools" folder. YOU ALSO HAVE TO HAVE JDK INSTALLED in order for it to work with your device. I just looked at what you posted and it looks like youred missing JDK"...
Click to expand...
Click to collapse
He says he already tried adb devices which didn't list anything. That tells me adb is configured correctly. Otherwise it should've given errors. Plus, he also said another Nexus 6P worked on the same mac.

adotkdotjh said:
He says he already tried adb devices which didn't list anything. That tells me adb is configured correctly. Otherwise it should've given errors. Plus, he also said another Nexus 6P worked on the same mac.
Click to expand...
Click to collapse
Yep
Sass86oh said:
I usually only get the key prompt for ADB authorzation when I connect my device and type "adb devices"..... If worse comes to worse, You can restore your phone to factory settings without wiping your sd card. Then you could test that option with compromising your data. Just flash each image from the archive yourself when restoring the firmware as opposed to using the flash-all scipt, or resetting the phone from settings... DO NOT flash the "userdata.img" included in the factory firmware archive or issue the command "fastboot format userdata" during the restore process and all of your files will be fine. This may be an option as long as fastboot is still functional on your device. Ive come across so many different devices in so many different conditions over the years, as long as the device could power on and the usb port was functional, fasboot has worked time and time again.
PS adb on Mac can be a bit tricky especially if this is the first time youre attempting to o install and use it. Unless you set the correct enviornment variables during the install process, you will oly be able to access adb from inside the folder that its stored in on your mac.
Click to expand...
Click to collapse
Thanks for the detailed steps but like adotkdotjh mentioned, I already have a working adb (and it worked fine with a different Nexus 6P on the same mac). How would 'fastboot' work if the computer does not even see my device under list of devices? I've never done any image flashing before so that would be quite an unfamiliar territory but I'd be willing to explore. Where would I get these image files and how do I issue the command to the device while it is not being recognized? Thanks

desimunda42 said:
Yep
Thanks for the detailed steps but like adotkdotjh mentioned, I already have a working adb (and it worked fine with a different Nexus 6P on the same mac). How would 'fastboot' work if the computer does not even see my device under list of devices? I've never done any image flashing before so that would be quite an unfamiliar territory but I'd be willing to explore. Where would I get these image files and how do I issue the command to the device while it is not being recognized? Thanks
Click to expand...
Click to collapse
Fastboot (also refered to as "download mode") is a tool used to essentially reprogram your device in the event that you are unable to enter into recovery mode in oreder to fix whatever issue your device is having. Android devices have 3 working modes, normal function, recovery mode, and fastboot. Number one is obvious, recovery allows you to completely reset your device without using a computer if every other measure youve tried hasn't worked. When you use this feature everything on your device is erased and your phone is completely restored to factory settings. Its convienet becuase not everyone is computer savvy and its to the point. But say you were updating (system update) your phone and accidently dropped it causing the battery to fall out and the device to shut off in the middle of the update process. What will most likely happen is the system partition will become corrupt, causing the phone to stick at the initial boot screen. Usually if that happens you can still access recovery mode and just reset but if for some reason that didnt work you would go to the manufacturers website and download the latest firmware for your device. You put the phone into fastboot mode by holding volume down and then pressing and holding the power button at the same time (while the phone is off).The process varies bydevice, If done correctly you will see on your screen a bunch of info along with Andy (the Android) chillin with his hatch open. You connect your phone to your computer and as long as your computer is set up correctly with adb and fastboot, you now have the abailty to reprogram (flash) your device using a series of commands that are issued from either the command line (windows) or terminal (linux/mac).
YOUR BOOTLOADER NEEDS TO BE UNLOCKED BEFORE CONTINUING. IF YOU DONT SEE A LITTLE LOCK AT THE BOTTOM OF YOUR DEVICE UNDER THE GOOGLE LOGO WHEN YOU FIRST TURN IT ON THEN YOU NEED TO GO TO SETTINGS, ABOUT DEVICE, FIND BUILD NUMBER AND TAP IT RAPIDLY UNTIL YOU SEE A MESSAGE POP UP SAYING YOU UNLOCKED DEVELOPER OPTIONS. GO BACK TO THE SETTINGS MENU AND SELEC DEVELOPER OPTIONS WHICH SHOULD NOW BE THERE AND INSIDE THERES AN OPTION CALLED "ALLOW OEM UNLOCKING" TURN IT ON. AND CONTINUE
Eextract the firmware archive you downloaded which will produce a folder containing 2 ".img files" files, another ".tar" archive, and some script files that you can use to make the process pretty much automated.
There are two of them, one for Windows (flash-all.bat) and one for Linux and Mac (flash-all.sh)....
Open the folder that was extracted from the firmware archive... Hold shift then right click a blank area in the folder. Select "open command prompt here" (Windows)
or
Type in terminal : cd ~/downloads/xxx where "xxx" is the name of the folder that was extracted but make sure that folder is moved to your "downloads" directory first
Then type the following commands:
IF YOU HAVENT UNLOCkED YOUR BOOTLOADER BEFORE THEN THIS IS WHERE YOU WILL NEED TO:
For Mac/Linux type: ./fastboot flashing unlock **Make sure you use the ./ or the command wont be recognized**
For Windows type: fastboot flashing unlock
Select yes on the phone when it asks if youre sure..... BAM, unlocked bootloader.
Your phone is completely free of restrections if you want to install custom firmware now. If not you can relock it after flashing the stock firmare by enterning fastboot mode again and typing
fastboot flashing lock or ./fastboot flashing lock (mac/linux).....
Now we can proceed with flashing the device...
For Windows: flash-all.bat and hit enter. The computer will do the rest.
Linux/Mac: ./flash-all.sh Make sure you use the ./ or the command wont be recognized.
If youre feeling brave you can do the entire process yourself by extracting the files in that second archive that was produced and flash each of them individually using a series of command in a specific order.
The 2nd extracted archive will give you a folder with five .img files
boot.img
cache.img
system.img
recovery.img
userdata.img ***** DO NOT FLASH THIS IMAGE. FORGET ITS EVEN THERE****
Take all five and move them to the original folder that was extracted. There are 2 other .img files that were extracted from the first archive also like I mentioned above, one that says "BOOTLOADER.xxx.xx.img" and one that says "RADIO.xxx.xxx.img"... Rename RADIO.xxx.xxx.img to | radio.img |and the other to| bootloader.img |ALL LOWER CASE keep them in that folder along with the other five. Now you should have 7 total image files in one folder. (Its smart to use the folder that your command prompt or terminal was opened in, if you decide to use a different folder then you have to direct each fastboot command to the folder where the .img file is located.
from the command line you flash each img individually with the following commands.....
(Mac/Linux need to include ./ before every fastboot command begins like this: ./fastboot or it wont work.
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader (phone will reboot then go back into fastboot mode, dont worry should only take seconds)
fastboot flash radio radio.img
fastboot reboot-bootloader (reboots again)
fastboot flash boot boot.img
fastboot erase cache
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot format userdata (this command takes place of the "userdata.img" file I told you to forget about)
fastboot reboot
As long as you see action on the screen and a "complete" after every command then youre in business. If you get an error check your spelling. THE COMMAND LINE IS CASE SENSETIVE. You might type the correct words but if one letter is capital the command wont work. If theres an extra space between words then the command wont work so check everything. Safe rule: Everything should be in lower case letters with 1 space after every word.... THIS S*** MATTERS
Its not as hard as it seems if you arent familiar with the process, but its also not something to mess with unless youve done your homework. Read up on it, there are so many good posts and people in here so you'll be able to find everything you need without any issue.
Fastboot can also be used to install a custom recovery like TWRP which would then allow you to install custom firmware (roms) on your device as long as theres support for it. Nexus devices are built for that very reason! They tend to have a huge selection of development within the Android community. They come with Android as Google intended it to be! No extra BS.... And its wicked easy to unlock the bootloader. That is why they are, in my opinion, the best Android devices available. But someone who doesnt really care much for things like modding and installing custom firmware might see the Nexus as plain device which lacks the bells and whistles included in other devices. Which is ok! I personally love the simplicity of pure Android and the whole philosophy behind the Nexus Program. To each is own! If you need anything else send me a message!

Have not read it all on here lol install this on your Mac https://www.android.com/filetransfer/ and see if it sees you 6p make sure you plug in them change from charging to file transfer on the phone then exit out of the app and reboot that will tell you if your Mac sees your phone

HD8 Gen 7 (2017) - Not seen by Linux or Windows in Fastboot Mode - help please.

Guys,
I'm on 9920 and need to Brick it. I cant get the tablet into Fastboot mode but then its not responding and the PC (Ubuntu and Windows 10) doesnt 'see' it on the USB port (tried different ports).
ADB sees it fine on both OSes -- I can run any ADB command, like "adb reboot bootloader" and screen goes black and at the bottom I see "=> Fastboot mode..." -- I can also run isusb, etc and it sees the device fine (its the only one on the system)
When I run 'brick-9820.sh' and the script waits at "< waiting for any device > " and nothing ever happens until I break out of it (CTRL-C).
-- rebooting the tablet boots into the OS just fine. I even tried Factory Reset from Recovery mode... did not help
I can run STEP-1.SH but I just get "Platform Not Supported" over and over until I break out of it (I think this is to be expected since I don't have root)
Any help is HIGHLY appreciated!

LivinOne said:
Guys,
I'm on 9920 and need to Brick it. I cant get the tablet into Fastboot mode but then its not responding and the PC (Ubuntu and Windows 10) doesnt 'see' it on the USB port (tried different ports).
ADB sees it fine on both OSes -- I can run any ADB command, like "adb reboot bootloader" and screen goes black and at the bottom I see "=> Fastboot mode..." -- I can also run isusb, etc and it sees the device fine (its the only one on the system)
When I run 'brick-9820.sh' and the script waits at "< waiting for any device > " and nothing ever happens until I break out of it (CTRL-C).
-- rebooting the tablet boots into the OS just fine. I even tried Factory Reset from Recovery mode... did not help
I can run STEP-1.SH but I just get "Platform Not Supported" over and over until I break out of it (I think this is to be expected since I don't have root)
Any help is HIGHLY appreciated!
Click to expand...
Click to collapse
Try it to factory reset by using secret code from Amazon search ;oobe
Try this to use exploit package for Douglas from @k4y0z: https://forum.xda-developers.com/hd8-hd10/orig-development/unlock-fire-hd-8-2017-douglas-t3962846. Follow the steps carefully.

Can anyone help?
I've Factory Reset the HD8 twice and am using @k4y0z Douglas exploit package. I've ran exploits on many older HD8s (2016) & HD10s (2017) but never needed to Brick any... this HD8 2107 firmware is 9920 and I want to let my kid use it and put a custom ROM on it so I can run Google Family Link (which FireOS cannot).
thx for the help!

What device shows is it on lsusb?

Michajin said:
What device shows is it on lsusb?
Click to expand...
Click to collapse
tablet ID shows properly in both Windows 10 & Ubuntu in ADB (and can accept commands just fine too). When in Fastboot mode, it does not show up at all, or accept commands.
Should the tablet show as a USB device when in Fastboot mode? ... and if it should, what would cause it to not show up in FB mode, but work properly in ADB

LivinOne said:
tablet ID shows properly in both Windows 10 & Ubuntu in ADB (and can accept commands just fine too). When in Fastboot mode, it does not show up at all, or accept commands.
Should the tablet show as a USB device when in Fastboot mode? ... and if it should, what would cause it to not show up in FB mode, but work properly in ADB
Click to expand...
Click to collapse
You said it shows up.... What device does it say it is when you do a lsusb at the teminal in ubuntu?

LivinOne said:
Can anyone help?
I've Factory Reset the HD8 twice and am using @k4y0z Douglas exploit package. I've ran exploits on many older HD8s (2016) & HD10s (2017) but never needed to Brick any... this HD8 2107 firmware is 9920 and I want to let my kid use it and put a custom ROM on it so I can run Google Family Link (which FireOS cannot).
thx for the help!
Click to expand...
Click to collapse
Did you update all of the repositories the post calls out?
Also, how are you accessing Ubuntu?
Lastly, I'm sure you've checked this, but make sure it is a Douglas.

Michajin said:
You said it shows up.... What device does it say it is when you do a lsusb at the teminal in ubuntu?
Click to expand...
Click to collapse
It shows the ID. When sending ADB commands it works perfectly.
Kctucka said:
Did you update all of the repositories the post calls out?
Also, how are you accessing Ubuntu?
Lastly, I'm sure you've checked this, but make sure it is a Douglas.
Click to expand...
Click to collapse
Yes, I updated all repo's. I even killed my install and rebuilt the Ubuntu, under Windows Linux Subsystem. I used this exact setup, on the same PC, for 2 other Fire Tablets (HD8 2016 & HD10 2017) and it worked 100% smooth.
using... amonet-douglas-v1.2 and brick-douglas
The issue is the OS does not see the tablet once in Fastboot mode.

LivinOne said:
It shows the ID. When sending ADB commands it works perfectly.
Yes, I updated all repo's. I even killed my install and rebuilt the Ubuntu, under Windows Linux Subsystem. I used this exact setup, on the same PC, for 2 other Fire Tablets (HD8 2016 & HD10 2017) and it worked 100% smooth.
using... amonet-douglas-v1.2 and brick-douglas
The issue is the OS does not see the tablet once in Fastboot mode.
Click to expand...
Click to collapse
Does anything show up in lsusb in fastboot mode or do you see anythign like...
When you say it is in Fatboot mode, but nothing works, but you see a device in lsusb, what is the device called?
Like..
ID 0e8d:2000 MediaTek Inc. MT65xx Preloader
ID 0e8d:0003 MediaTek Inc. MT6227 phone
What is it being called?
---------- Post added at 12:36 PM ---------- Previous post was at 12:34 PM ----------
From my understanding you are trying to downgrade to unlock (which will temp brick your device), is this correct? I can try to help...

LivinOne said:
It shows the ID. When sending ADB commands it works perfectly.
Yes, I updated all repo's. I even killed my install and rebuilt the Ubuntu, under Windows Linux Subsystem. I used this exact setup, on the same PC, for 2 other Fire Tablets (HD8 2016 & HD10 2017) and it worked 100% smooth.
using... amonet-douglas-v1.2 and brick-douglas
The issue is the OS does not see the tablet once in Fastboot mode.
Click to expand...
Click to collapse
Does it recognize your other devices in fastboot mode?
If I recall correctly WLS doesn't work with fastboot. Something related to USB devices without storage.
I'd try booting Ubuntu using a USB stick with persistent storage.

Kctucka said:
Does it recognize your other devices in fastboot mode?
If I recall correctly WLS doesn't work with fastboot. Something related to USB devices without storage.
I'd try booting Ubuntu using a USB stick with persistent storage.
Click to expand...
Click to collapse
Here is a nice live disk pre-set up for the firestick 4k. I have used this on a few tablets.... But seems like it would still show up in fastboot in windows, if that was his issue...
https://github.com/amonet-kamakiri/fireiso/releases

Michajin said:
Here is a nice live disk pre-set up for the firestick 4k. I have used this on a few tablets.... But seems like it would still show up in fastboot in windows, if that was his issue...
https://github.com/amonet-kamakiri/fireiso/releases
Click to expand...
Click to collapse
Does the ISO run in Virtual Box, or something else? I've only been using the Windows Linux Subsystem as I rarely need to use Linux other than for my Synology NAS. Thx for the help!

LivinOne said:
Does the ISO run in Virtual Box, or something else? I've only been using the Windows Linux Subsystem as I rarely need to use Linux other than for my Synology NAS. Thx for the help!
Click to expand...
Click to collapse
It is a live disk. Burn it to a USB and boot from it...

Guys,
I noticed that in Windows 10 vs Ubuntu (Windows Linux Subsystem / WLS), they both work great with ADB... but they seem to be loading different versions...
Windows: adb server version (39) doesn't match this client (41); killing...
Ubuntu WLS: adb server version (41) doesn't match this client (39); killing...
Could this be an issue where Fastboot is a problem due to version?
thx

LivinOne said:
Guys,
I noticed that in Windows 10 vs Ubuntu (Windows Linux Subsystem / WLS), they both work great with ADB... but they seem to be loading different versions...
Windows: adb server version (39) doesn't match this client (41); killing...
Ubuntu WLS: adb server version (41) doesn't match this client (39); killing...
Could this be an issue where Fastboot is a problem due to version?
thx
Click to expand...
Click to collapse
No
Looking through the unlock thread, The OP says it is a fastboot issue and recommends using the live disk i sent a link for see posts #265 and #268
https://forum.xda-developers.com/hd...unlock-fire-hd-8-2017-douglas-t3962846/page27
Everything points to your computer not recognizing the fastboot device- Try the live disk....

I fixed it! Windows will not load the driver when I try to do it in Device Manager, manually. I used this installer THEN I opened Device Manager, right-clicked the unknown item under Android, and pointed it to root of the C Drive! It found and installed the driver.
Hope this helps someone in the future.
thx guys!