Database Develop

need help, installing ota zip to my nexus 6

Hello guys,
i was following this article, from yahoo, i cannot post it
and reached the point of
The fastboot menu will appear and you should see Start in the top right. Press Volume Up till it changes to Recovery. Press the Power button to select it.
You will see an Android with a red exclamation point icon, press and hold the Power key, then press the Volume up key to show the Recovery Menu.
You will get a new menu. Navigate to apply update from adb and select it by pressing the Power button.
but it says this in the cmd
device <null> NOT attached.
the phone is still connected, what do i do now?
please help

hendyanto said:
Hello guys,
i was following this article, from yahoo, i cannot post it
and reached the point of
The fastboot menu will appear and you should see Start in the top right. Press Volume Up till it changes to Recovery. Press the Power button to select it.
You will see an Android with a red exclamation point icon, press and hold the Power key, then press the Volume up key to show the Recovery Menu.
You will get a new menu. Navigate to apply update from adb and select it by pressing the Power button.
but it says this in the cmd
device <null> NOT attached.
the phone is still connected, what do i do now?
please help
Click to expand...
Click to collapse
Where does it say this and at what point? Your phone is 100% stock then, correct? You set up adb correctly?
We'll need more information than supplied. You should walk us through step by step

hendyanto said:
Hello guys,
i was following this article, from yahoo, i cannot post it
and reached the point of
The fastboot menu will appear and you should see Start in the top right. Press Volume Up till it changes to Recovery. Press the Power button to select it.
You will see an Android with a red exclamation point icon, press and hold the Power key, then press the Volume up key to show the Recovery Menu.
You will get a new menu. Navigate to apply update from adb and select it by pressing the Power button.
but it says this in the cmd
device <null> NOT attached.
the phone is still connected, what do i do now?
please help
Click to expand...
Click to collapse
I was having the exact same problem last night, following the same instructions. I still could not figure out how to sideload the OTA, so I ended up just flashing the update and starting from fresh. Wish I had the answer for you.
Here was my thread asking pretty much the same thing: http://forum.xda-developers.com/nexus-6/help/disconnects-computer-entering-bootloader-t3230705

danarama said:
Where does it say this and at what point? Your phone is 100% stock then, correct? You set up adb correctly?
We'll need more information than supplied. You should walk us through step by step
Click to expand...
Click to collapse
100% Stock, yes! 1 week old.
Yes i have set up ADB
I have followed the instruction until this part (i cannot post any link sorry, not authorized by xda)
The following ADB commands are for Windows machines. If you’re using a Mac, just add “./” before each command, for example: “./adb reboot bootloader”.
Assuming you device is already connected to your computer via USB and USB Debugging is enabled, you need to re-start it in fastboot mode. Follow one of the two methods below. Option A may be preferable because it’s another confirmation that your computer recognizes your Nexus device.
A) Type “adb reboot bootloader”
B) Turn your device off, then turn it back on while holding down the relevant key combinations for your device. For many devices it’s Volume Up + Volume Down + Power. You can see what your device’s key combinations are here.
The fastboot menu will appear and you should see Start in the top right. Press Volume Up till it changes to Recovery. Press the Power button to select it.
You will see an Android with a red exclamation point icon, press and hold the Power key, then press the Volume up key to show the Recovery Menu.
You will get a new menu. Navigate to apply update from adb and select it by pressing the Power button.
In the command window — make sure you are in the directory where ADB and Fastboot reside — type: “adb sideload [the full name of the file].zip” without the brackets around the file name.
The update will install and reach 100 percent.
Reboot and enjoy the latest version of Android Marshmallow.
Click to expand...
Click to collapse
(red arrow) and then the cmd says the null error, i am trying this now
I had the same problem. Turned MTP on and then it worked. You're told to turn it off but don't... Its in Settings-Storage-touch the ... Menu top right corner, USB settings and turn ON MTP mode. It worked well for me. I also used the Nexus Root Toolkit - makes things much easier!
Click to expand...
Click to collapse
My phone is able to rebooot (the options comes out sometimes after i did not do anything) and now optimising app (like it usually did after an OTA update)

hendyanto said:
100% Stock, yes! 1 week old.
Yes i have set up ADB
I have followed the instruction until this part (i cannot post any link sorry, not authorized by xda)
(red arrow) and then the cmd says the null error, i am trying this now
My phone is able to rebooot (the options comes out sometimes after i did not do anything) and now optimising app (like it usually did after an OTA update)
Click to expand...
Click to collapse
There are lots of additional steps in that guide and not always the simplest way of doing it.
First thing to do is boot into recovery.
- Turn off the phone.
- Hold volume down + power
- At the bootloader screen, use volume keys to navigate to recovery and press power to select#
- At the Red warning triangle, hold power then press volume up.
At this stage, type "adb devices" in your command prompt and see if it returns your serial number or not. If it does, you can follow the steps to use adb to flash the update.
Please note, the guide talks about USB debugging. This only works in android. Nothing you need to do needs to be done via android so this is nonsense. Also the MTP option only works in android, so setting this in settings as a fix is also nonsense.

danarama said:
There are lots of additional steps in that guide and not always the simplest way of doing it.
First thing to do is boot into recovery.
- Turn off the phone.
- Hold volume down + power
- At the bootloader screen, use volume keys to navigate to recovery and press power to select#
- At the Red warning triangle, hold power then press volume up.
At this stage, type "adb devices" in your command prompt and see if it returns your serial number or not. If it does, you can follow the steps to use adb to flash the update.
Please note, the guide talks about USB debugging. This only works in android. Nothing you need to do needs to be done via android so this is nonsense. Also the MTP option only works in android, so setting this in settings as a fix is also nonsense.
Click to expand...
Click to collapse
I cannot get my windows to detect the phone during recovery mode, it always disconnected at that point.
I'll try again when i have the time, thank you all.

hendyanto said:
I cannot get my windows to detect the phone during recovery mode, it always disconnected at that point.
I'll try again when i have the time, thank you all.
Click to expand...
Click to collapse
Could be a driver issue. You'll need to check device manager. Perhaps uninstall the existing drivers and let it auto detect.
Failing that, install the Naked driver from my adb and fastboot thread (Nexus 6 general > Sticky roll-up thread > Adb and fastboot. What is it?)

I had the same issue with you until i did the following: I used wugfresh's nexus utility. Then I downloaded the respective file from XDA and saved it in the same folder as the Wugfresh's tool. Restarted in Recovery mode and chose 'update from adb'. Connected the phone with the usb having USB debugging on from before going to recovery. Started the CMD window from Wugfresh's tool (Advanced Utilities -> Launch) and check that the phone is connected (I think "adb devices") . Then "adb sideload xxxx.zip" and waited for the process to finish.
Instruction here: androidpolice 2012/11/13/android-4-2-build-jop40c-rolling-out-to-the-nexus-7-now-manual-download-link-available/
You do not have to install the full Android utility. Just use wugfresh;s cmd screen. Good luck!

danarama said:
Could be a driver issue. You'll need to check device manager. Perhaps uninstall the existing drivers and let it auto detect.
Failing that, install the Naked driver from my adb and fastboot thread (Nexus 6 general > Sticky roll-up thread > Adb and fastboot. What is it?)
Click to expand...
Click to collapse
qwerty1gr said:
I had the same issue with you until i did the following: I used wugfresh's nexus utility. Then I downloaded the respective file from XDA and saved it in the same folder as the Wugfresh's tool. Restarted in Recovery mode and chose 'update from adb'. Connected the phone with the usb having USB debugging on from before going to recovery. Started the CMD window from Wugfresh's tool (Advanced Utilities -> Launch) and check that the phone is connected (I think "adb devices") . Then "adb sideload xxxx.zip" and waited for the process to finish.
Instruction here: androidpolice 2012/11/13/android-4-2-build-jop40c-rolling-out-to-the-nexus-7-now-manual-download-link-available/
You do not have to install the full Android utility. Just use wugfresh;s cmd screen. Good luck!
Click to expand...
Click to collapse
Thank you guys! But after this "happy"night, i woke up to the OTA for marshmallow arrived on my phone, so see you guys on the rooting section instead, Thank you thank you for the help

[GUIDE]Huawei P8 Lite Downgrade/Unlock Bootloader/Root(5.0 and 6.0)/ Enable Gyroscope

Disclaimer:
I am not responsible for what you do to your device, I tested these things for myself and posted it from my own experience, if you point the finger at me for whatever happens to your device, I will laugh at you.
HOWEVER, I am willing to help as long as it is asked kindly, and provided me with enough information.
Requirements:
Huawei P8 Lite ALE-L21 (DUAL-SIM)
5.0 Firmware of choice
Unlocked bootloader
Patience
Correct drivers
SD card of atleast 8 GB
Drivers: Install these before even starting!
Minimal ADB Fastboot drivers
Huawei HiSuite
Kingoroot Windows
TWRP 3.0.2.0 Kirin variant
Preparing environment: Making sure no admin priveledge is necessary
Install all drivers mentioned above in their standard directories, don't change anything.
Go to the following path:
Code:
For x64 OS:
C:\Program Files (x86)\Minimal ADB and Fastboot
For x86_32 OS:
C:\Program Files\Minimal ADB and Fastboot
Copy these files:
Code:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
And paste them on the desktop, in a folder called "rootingtools" so you're easily able to find it.
Then, go to your phone and enable USB debugging mode by going to
settings - about phone - press Build number 7 times
settings - developer options - USB debugging
Copy the content of "TWRP-3.0.0-2_P8-lite_KIRIN_variant.zip" and paste it into the "rootingtools" folder.
Backing up: Even though the unlocking process is not going to wipe your data, atleast it didn't for me, make SURE you have everything that you need backed up from the phone's internal memory.
Backing up your SD card wouldn't hurt neither.
First things first, unlock your bootloader!
I used this: https://emui.huawei.com/en/plugin.php?id=unlock&mod=detail
What you do is: fill in everything correctly and get the number at the end. It should be something in the words of:
Code:
Your unlocking password is: XXXX XXXX XXXX XXXX
(X resembles numbers, 16 numbers in total)
Copy the 16 numbers and go to the "rootingtools" folder on your desktop.
Hold the SHIFT key and right click inside the folder, then press "open command window here"
Now take your phone, power it off and power it on by holding volume DOWN and POWER.
You will get a white screen that says something like fastboot, and an android logo.
Plug your phone into the PC via USB cable.
In the command window write:
Code:
fastboot.exe oem unlock UNLOCKKEY
Where UNLOCKKEY represents the key you just copied, right clicking pastes the key in the command window.
It should return finished, so now your phone should be unlocked!
If you look at the screen, there will be text beneath the green Android logo saying "unlocked".
In this case, the operation has succeeded and you can go to the next step, else you can try again or post a reply.
Now write:
Code:
fastboot.exe reboot
Now the phone will boot up like normal.
Close the command window.
Android 5.0:
If your android version right now is Android 5.0, and you actually WANT to root 5.0 or anything below 6.0 you can proceed with this step, if you have 6.0 or want to root 6.0, skip this step.
Since your android version is 5.0 you're blessed!
You can easily root, but before proceeding you might want to make a backup
Make sure you have about 8GB of free storage either on an SD card or internal memory first.
Connect your phone to your PC in the booted-up state where you can see the homescreen, making sure that USB debugging is enabled.
Shift + right click inside the rootingtools folder to open a command window and write:
Code:
adb.exe reboot-bootloader
Your phone will reboot into the bootloader, a white screen with a green Android logo that says "unlocked" beneath it.
Now on the command window write:
Code:
fastboot.exe flash recovery recovery.img
Wait for it to finish and pull out the USB cable so it is NOT attached.
Power off the device by holding the power button, and power up by pressing volume UP + POWER.
Keep holding volume up until you see the Team Win logo.
Just slide the slider to the right.
Now go to "backup" and check every partition available.
In "name" you write:
Code:
MainBackupURTD
Then, go to the "options" tab and enable compression.
Go back to the "backup" tab and press "select storage".
From here you can choose where to back your data up, whether it be the internal storage or external SD card.
Press OK and swipe the slider to the right to start backing up.
Plug your phone in to make sure it doesn't power off during backing up, this process takes a while and you should let it do its thing.
When done, press "reboot system", your phone will reboot.
Let it fully start up.
Then, run Kingoroot on your PC.
Meanwhile, download the "SuperSU" app from the Play store.
Press the big "ROOT" button in Kingoroot and press "cancel" on every app your phone tries to install.
That way you will not install Kingoroot but SuperSU.
It will say "succeeded".
Now you can go on your phone and open the SuperSU app.
It will ask for an upgrade, press OK and go further with the normal installation (not the TWRP/CWM installation).
Let it do its thing and restart your phone.
Install any root checker and see if you're rooted!
Android 6.0:
Firmware version B188 or higher, below B524/B535 (excluding B524/B535):Upgrade firmware to this one: LINK (Link fixed)
Installation instructions: place file to the "dload" folder in your SD card or internal storage, then go to settings - updates - menu - local update and press the update.zip.
Then, follow the guide reported here: http://rootmygalaxy.net/root-huawei-p8-lite-android-marshmallow-6-0-update/
Enabling Gyro sensor (rooted android 6.0, B524/B535 firmware only! ( sorry :[ ) ):
Download attached file.
Put attached file to SD card.
Open ES file explorer, swipe to the right, enable root browser and click the R/W tab, then set /system as RW.
Then copy the attached file.
Paste the attached file in /system/etc/permissions
Press the search button and search for "gyro" without quotation marks.
Long press the only file that's there - menu and press properties.
Then change the permissions to 644, it should look like this O represents off, X represents on;
X X O
X O O
X O O
Set UID is off, Set GID is off, Sticky bit is off.
Reboot phone and download "Sensor box for Android" on the Play store and enjoy your gyroscope!
Now you can use Google Cardboard, though you have to install the APK...
You can watch 360 videos on youtube too.

Credits, sources and links:
http://forum.xda-developers.com/p8lite/general/twrp-3-0-0-0-p8-lite-kirin-t3343320
http://huaweifirmware.com/huawei-p8-lite
http://www.androidsage.com/2016/02/...-6-0-marshmallow-beta-firmware/#axzz48veWSvTk
http://forum.xda-developers.com/p8lite/general/root-huawei-p8-lite-ale-l21-android-6-0-t3307686
https://www.kingoapp.com/
Subject to change

Hiya, will the gyro hack work on a L02 B130 Android 5.0 as i can't get an update to 6.0 here in New Zealand?

unable to get unlock code
The Huawei ID used to apply for the unlock code has not been used on the device for more than 14 days.

@sevenaudio
As far as I know, the hack is for android 6.0 but there should be no problem in trying it out
It's just that it only worked for me on these FW
@DrLittle
I think Huawei has this policy of using your Huawei ID for 2 weeks (2 weeks online time) before you can unlock it
You could try sending them an email!

always i get the error failed status malformed 1 bytes
finished total 0.005s

eriuzz said:
always i get the error failed status malformed 1 bytes
finished total 0.005s
Click to expand...
Click to collapse
Hi, can you pinpoint what you were trying to do when it got stuck?
As in, what were you trying to flash.
And what is your phone model?

oziboy said:
Hi, can you pinpoint what you were trying to do when it got stuck?
As in, what were you trying to flash.
And what is your phone model?
Click to expand...
Click to collapse
just trying to unlock the bootloader i have my code from huawei and when i try to use it through adb appear that error i said

eriuzz said:
just trying to unlock the bootloader i have my code from huawei and when i try to use it through adb appear that error i said
Click to expand...
Click to collapse
Are the dorrect drivers installed, are you sure you copied the whole key?
Use an other usb porta.

oziboy said:
Disclaimer:
I am not responsible for what you do to your device, I tested these things for myself and posted it from my own experience, if you point the finger at me for whatever happens to your device, I will laugh at you.
HOWEVER, I am willing to help as long as it is asked kindly, and provided me with enough information.
Requirements:
Huawei P8 Lite ALE-L21 (DUAL-SIM)
5.0 Firmware of choice
Unlocked bootloader
Patience
Correct drivers
SD card of atleast 8 GB
Drivers: Install these before even starting!
Minimal ADB Fastboot drivers
Huawei HiSuite
Kingoroot Windows
TWRP 3.0.2.0 Kirin variant
Preparing environment: Making sure no admin priveledge is necessary
Install all drivers mentioned above in their standard directories, don't change anything.
Go to the following path:
Code:
For x64 OS:
C:\Program Files (x86)\Minimal ADB and Fastboot
For x86_32 OS:
C:\Program Files\Minimal ADB and Fastboot
Copy these files:
Code:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
And paste them on the desktop, in a folder called "rootingtools" so you're easily able to find it.
Then, go to your phone and enable USB debugging mode by going to
settings - about phone - press Build number 7 times
settings - developer options - USB debugging
Copy the content of "TWRP-3.0.0-2_P8-lite_KIRIN_variant.zip" and paste it into the "rootingtools" folder.
Backing up: Even though the unlocking process is not going to wipe your data, atleast it didn't for me, make SURE you have everything that you need backed up from the phone's internal memory.
Backing up your SD card wouldn't hurt neither.
First things first, unlock your bootloader!
I used this: https://emui.huawei.com/en/plugin.php?id=unlock&mod=detail
What you do is: fill in everything correctly and get the number at the end. It should be something in the words of:
Code:
Your unlocking password is: XXXX XXXX XXXX XXXX
(X resembles numbers, 16 numbers in total)
Copy the 16 numbers and go to the "rootingtools" folder on your desktop.
Hold the SHIFT key and right click inside the folder, then press "open command window here"
Now take your phone, power it off and power it on by holding volume DOWN and POWER.
You will get a white screen that says something like fastboot, and an android logo.
Plug your phone into the PC via USB cable.
In the command window write:
Code:
fastboot.exe oem unlock UNLOCKKEY
Where UNLOCKKEY represents the key you just copied, right clicking pastes the key in the command window.
It should return finished, so now your phone should be unlocked!
If you look at the screen, there will be text beneath the green Android logo saying "unlocked".
In this case, the operation has succeeded and you can go to the next step, else you can try again or post a reply.
Now write:
Code:
fastboot.exe reboot
Now the phone will boot up like normal.
Close the command window.
Android 5.0:
If your android version right now is Android 5.0, and you actually WANT to root 5.0 or anything below 6.0 you can proceed with this step, if you have 6.0 or want to root 6.0, skip this step.
Since your android version is 5.0 you're blessed!
You can easily root, but before proceeding you might want to make a backup
Make sure you have about 8GB of free storage either on an SD card or internal memory first.
Connect your phone to your PC in the booted-up state where you can see the homescreen, making sure that USB debugging is enabled.
Shift + right click inside the rootingtools folder to open a command window and write:
Code:
adb.exe reboot-bootloader
Your phone will reboot into the bootloader, a white screen with a green Android logo that says "unlocked" beneath it.
Now on the command window write:
Code:
fastboot.exe flash recovery recovery.img
Wait for it to finish and pull out the USB cable so it is NOT attached.
Power off the device by holding the power button, and power up by pressing volume UP + POWER.
Keep holding volume up until you see the Team Win logo.
Just slide the slider to the right.
Now go to "backup" and check every partition available.
In "name" you write:
Code:
MainBackupURTD
Then, go to the "options" tab and enable compression.
Go back to the "backup" tab and press "select storage".
From here you can choose where to back your data up, whether it be the internal storage or external SD card.
Press OK and swipe the slider to the right to start backing up.
Plug your phone in to make sure it doesn't power off during backing up, this process takes a while and you should let it do its thing.
When done, press "reboot system", your phone will reboot.
Let it fully start up.
Then, run Kingoroot on your PC.
Meanwhile, download the "SuperSU" app from the Play store.
Press the big "ROOT" button in Kingoroot and press "cancel" on every app your phone tries to install.
That way you will not install Kingoroot but SuperSU.
It will say "succeeded".
Now you can go on your phone and open the SuperSU app.
It will ask for an upgrade, press OK and go further with the normal installation (not the TWRP/CWM installation).
Let it do its thing and restart your phone.
Install any root checker and see if you're rooted!
Android 6.0:
Firmware version B188 or higher, below B524/B535 (excluding B524/B535):Upgrade firmware to this one: mega:///#!OBVU3RyT!gSDNFMVtWVqA1HyneCuofhFmVVJ6lUDonzfKzjucbFs
Installation instructions: place file to the "dload" folder in your SD card or internal storage, then go to settings - updates - menu - local update and press the update.zip.
Then, follow the guide reported here: http://rootmygalaxy.net/root-huawei-p8-lite-android-marshmallow-6-0-update/
Enabling Gyro sensor (rooted android 6.0, B524/B535 firmware only! ( sorry :[ ) ):
Download attached file.
Put attached file to SD card.
Open ES file explorer, swipe to the right, enable root browser and click the R/W tab, then set /system as RW.
Then copy the attached file.
Paste the attached file in /system/etc/permissions
Press the search button and search for "gyro" without quotation marks.
Long press the only file that's there - menu and press properties.
Then change the permissions to 644, it should look like this O represents off, X represents on;
X X O
X O O
X O O
Set UID is off, Set GID is off, Sticky bit is off.
Reboot phone and download "Sensor box for Android" on the Play store and enjoy your gyroscope!
Now you can use Google Cardboard, though you have to install the APK...
You can watch 360 videos on youtube too.
Click to expand...
Click to collapse
Android B560 will update from b170
---------- Post added at 09:50 AM ---------- Previous post was at 09:40 AM ----------
eriuzz said:
just trying to unlock the bootloader i have my code from huawei and when i try to use it through adb appear that error i said
Click to expand...
Click to collapse
you got to test everything. from changing usb port to changing usb cable. htc is a brand that has this problem alot. and until now there's no right answer.
search around a little.

I'm stupid. I posted on the wrong thread, sorry.

Edit: delete

I have android 6.0 firmware B311 and it doesn't show up the option local update, what should I do?

Attach pictures please

Its in portuguese, I had the option on the stock ROM but i don't have it now.
Should I downgrade to the firmware B300 and then install the new firmware?

do you think this works with ALE-L21 single sim too?

Teixaz said:
I have android 6.0 firmware B311 and it doesn't show up the option local update, what should I do?
Click to expand...
Click to collapse
Local update option has been removed from Marshmallow, you must use *#*#2846579#*#* and go to sd card upgrade to further upgrade it

amageek said:
Local update option has been removed from Marshmallow, you must use *#*#2846579#*#* and go to sd card upgrade to further upgrade it
Click to expand...
Click to collapse
Does not work when its inside the zip and if I extract it when it start to install it fails

anyone?

Please help. I have 5.0.1 Android
So When you say " we are blessed", do we only do that 5th step or all the steps before that and then 5th step?
I am asking because im havin trouble unlocking bootloader. Nobody from Huawei is answering my email where I sent them all neccecary data, and when I go to this link It says there is a server problem. Either that or Im redirected to some site filled with japanese signs http://www.vmall.com/ and I dont know what to press
How do I unlock my bootloader?? What e-mail do I use to contact huawei about this matter?
Thanks

google glass stuck on "glass" text screen

Okay I know I need to wipe the device and/or reinstall the update
But I have no clue how to use android SDK or adb.
I have them both downloaded, not sure if they are installed for google glass access.
I'm using the command prompt and I search for adb or fastboot but no devices come up?
I downloaded the XE22 (latest firmware) but when I open that it asks me to burn a cd?
I'm lost and glass support won't help. Anybody?

phild22 said:
Okay I know I need to wipe the device and/or reinstall the update
But I have no clue how to use android SDK or adb.
I have them both downloaded, not sure if they are installed for google glass access.
I'm using the command prompt and I search for adb or fastboot but no devices come up?
I downloaded the XE22 (latest firmware) but when I open that it asks me to burn a cd?
I'm lost and glass support won't help. Anybody?
Click to expand...
Click to collapse
I just went through this to get to XE23. Did you ever get to the answer? Very similar process to flashing any other android device; identical really. LMK if you're still charging and using or want to.
GH

greddy91 said:
I just went through this to get to XE23. Did you ever get to the answer? Very similar process to flashing any other android device; identical really. LMK if you're still charging and using or want to.
GH
Click to expand...
Click to collapse
Ok... As I am new to the Glass game.... Last night, when I got the unit fully charged (Sitting at SW version XE12), I connected it to the network to update.... This morning, I have a bootloop issue.
I want to flash XE 12 back to the device and try to let it update again.... I have yet to find a clear breakdown on how to falsh this... SDK is installed.... But it appears that I don't have a the proper USB drivetr and have know idea how to install it...
Really could use some help with the entire process...

So, sharing files used on Google drive:
https://drive.google.com/drive/folders/0B3-nca6GSfX1R2h1eDNDUjZwRVk?usp=sharing
Installed Minimal ADB and hit yes all the way through - in the google drive above.
This gives ADB commands functionality anywhere in CMD
I plugged in the glass and it came up as a USB drive - AWESOME.
Enter Command Prompt
Navigate to the directory where I had the Glass EX23 unzipped
Entered "adb devices" to make sure ADB was seeing the Glass (make sure no other android goodies are plugged in)
It was there so...
Enter "adb reboot bootloader"
My glass went blank.
Entered "fastboot devices" ... and nothing.
So opened "Device Manager"
There was a flagged driver standing out for when I flashed an old Note 2. There's the problem...
Right click and chose "Update driver" and pointed it to the "usb driver" directory extracted from the zip file in the google drive above.
Chose Android Composite ADB Interface - Skipped past the unsigned driver warning
Voila - the device is now seen in device manager
I then entered the command in cmd "fastboot devices" - and still blank
Unplugged glass and rebooted.
After it came up, plugged it back in - seen as USB drive again. Still good!
Entered "adb devices" to make sure ADB was seeing the Glass
It was there again so...
Enter "adb reboot bootloader"
My glass went blank again.
Entered "fastboot devices" ... and there it is!!! The Gates of Valhalla are in sight!!!
Assure you're in the directory where the google image has been unzipped...
Now begin by entering:
"fastboot flash boot boot.img"
let it complete
Now "fastboot flash system system.img"
let it complete (this is the longest one... be patient)
Now "fastboot flash recovery recovery.img"
Now "fastboot flash userdata userdata.img"
Now "fastboot erase cache" - takes a bit of time for cleanup
Now "fastboot reboot"
The moment of glory has arrived... watch your glass go through boot - yes the Glass screen turns on and off a few times and flashes some odd colors... again, be patient... took like 5 minutes and ate up 40% of my full battery, but there it was XE23 and full stability.
Note - NONE of these utilities are mine, they were borrowed after researching in hundreds of other threads on how to get this done.
Of note... I came from XE10 straight to XE23 with no issues.

Legobricke said:
Ok... As I am new to the Glass game.... Last night, when I got the unit fully charged (Sitting at SW version XE12), I connected it to the network to update.... This morning, I have a bootloop issue.
I want to flash XE 12 back to the device and try to let it update again.... I have yet to find a clear breakdown on how to falsh this... SDK is installed.... But it appears that I don't have a the proper USB drivetr and have know idea how to install it...
Really could use some help with the entire process...
Click to expand...
Click to collapse
What version of Glass is it? And there is a thread under development about modifying your android_winusb.ini file so you can manually select the driver.

Muskeman16 said:
What version of Glass is it? And there is a thread under development about modifying your android_winusb.ini file so you can manually select the driver.
Click to expand...
Click to collapse
It is model XE-C running version XE-12...

Legobricke said:
It is model XE-C running version XE-12...
Click to expand...
Click to collapse
Have you attempted to re-flash it at all?

Muskeman16 said:
Have you attempted to re-flash it at all?
Click to expand...
Click to collapse
That is was I'm attempting to do.... But I'm not having much luck....
I am sure that USB debugging was not turned on.... When I put the Glass in to fastboot mode (holding down camera button and turning on which gives me short fast bursts from the power light) it doesn't seem to recognize it on the desktop. I get 3 low tones when I plug it in and ADB doesn't see it...
I guess I need a direct breakdown of the process... I have searched the net and forum, but the ones I find seem to drop a process or imply something that I'm not understanding.
I have flashed devices before and I'm familiar with the process, but I'm missing something when it comes to the Glass....
When I power up (normal power up) and the plug it, device manager lists it as Android Device. When I open that, just shows ADB Device Interface... I have tried to update the entry with the USB driver, it is claims the drivers are up to date.
I am using Windows 7.... But it is clear that ADB is not seeing the device... So, I'm stuck until I can findout how to get the device to be recongized.... What is strange is that when I plug the Glass in, it does see it in the tray below... It even allows me the "eject Glass_1... but for the life me, I can't get ADB to see it...
Any help is appreciated!

Ok.... I can finally see the Glass in ADB.... But only if I put the Glass in Fastboot mode prior to plugging in to USB.... I adb "fastboot device" and get a serial number.... Then I adb "fastboot flash boot boot.img and get FAILED (remote failure)...
What am I doing wrong?

I have even tried to unlock the device, but it hangs at erasing userdata.
The very interesting thing is on a few occasions, I have gotten GLASS to work....
I re-set it up.... and then it works fine until I have to charge it again and then it goes back to the freezing on the GLASS screen.
Every time I try to flash Boot/system/ etc image... it fails.... Not sure why....

Ok....
Finally nailed it.... No more GLASS looping....
I took this unit that was experiencing GLASS loop at firmware X12 to X23... What a journey....
To start.... I downloaded the "minimal adb fastboot" and installed....
Then I downloaded the new firmware from google
I dragged the zip folder to my desktop and extracted it....
At this point, I put GLASS in fastboot mode (Hold camera button down then press the power button. Once power light come on, let go of the power button but keep camera pressed. One the light starts to flash (slowly, not fading), you are in fastboot mode).
I then attached the glass via usb cable to computer (I was operating Windows 10).
Open device manager and look for "android devices" and open it. You should see "Android ADB Interface" - Right click on it and select Update Driver Software". Then select Browse my computer for driver software. The select "Let me pick from a list of device drivers on my computer". Look for "Android ADB Interface". Select it and then update it.
Once this is done, got to your icon tray (should be down in the bottom right of your scree) and right click on "Safetly Remove Hardware or Eject Media". It should open a window up. Confirm that glass is there.
Then go to the desktop where you extracted the firmware and open the folder. Once open, Hold shift and right click. This should give you a menu. You are looking for "Open command window here". select it and it should open a command window.
Then follow the instructions listed on the google firmware page.
I didn't follow all the instructions.... The ones I did were enough to fix my boot looping GLASS -
1.) fastboot devices (This should comeback with a serial number. If it doesn't, be sure you have the glass in fastboot mode)
2.) fastboot oem unlock ( I had to do this because the device would fail when I tried flashing to the device. This was the only way I could get it to take the flashing). It will make you type this twice to confirm you wish to unlock.... This will erase all the data (cache and user data) on the device and you have to be patient.... It does take some time... If you think it has hung up (which I did), I just hit a key on my keyboard and then pressed enter.... It then confirmed that the unit had been unlocked.
3.) After I unlocked the unit, I then typed fastboot devices again just to be sure that it was still reading the GLASS.
4.) fastboot flash boot boot.img - This will fail if you don't have the unit unlocked.... The first time I did this, the glass unit went down and I had to start the process again. The second time I did the process, it worked.
5.) fastboot flash system system.img - This did take a few minutes
6.) fastboot flash recovery recovery.img
Once done, I closed the command window and ejected the glass unit from the computer..... I pressed the power button and BOOM! I was back to a working glass...
One key element I must point out.... allot of this process requires allot of patience....
The pages that are linked above will help you through the process.... I took a week of researching.... But it was worth it...
There are risks involved - bricking/etc.... But this is the process that worked for me...
Good luck!

Legobricke said:
Ok.... I can finally see the Glass in ADB.... But only if I put the Glass in Fastboot mode prior to plugging in to USB.... I adb "fastboot device" and get a serial number.... Then I adb "fastboot flash boot boot.img and get FAILED (remote failure)...
What am I doing wrong?
Click to expand...
Click to collapse
Just for clarity - I associate adb and fastboot as two seperate commands.
"adb devices" gives you your android attached devices inventory
"fastboot devices" gives you your attached devices in fastboot
The "adb reboot bootloader" changes the device seen in adb to a device that can be seen in fastboot.
Not sure if that was clear before, but it may help here.

greddy91 said:
Just for clarity - I associate adb and fastboot as two seperate commands.
"adb devices" gives you your android attached devices inventory
"fastboot devices" gives you your attached devices in fastboot
The "adb reboot bootloader" changes the device seen in adb to a device that can be seen in fastboot.
Not sure if that was clear before, but it may help here.
Click to expand...
Click to collapse
Thanks for the clarify....
I attempted to go the adb route, but could never get the system to see the GLASS in adb... and because the GLASS was looping on the GLASS screen, I couldn't activate USB Debugging..
So, I found out in researching that I could manually put the GLASS in fast boot mode....
Once it was unlocked, everything took...

not a tech guy -_-
Hi thanks for clearifying But could you explain step by step and like i know nothing about commad prompt. Im just tring to work my glass but at turkey i cant find any coder who understands this. (sorry for bad english)

Rooting Black Shark 3 / 3 Pro the Correct & Easy Way - BL Unlocking, TWRP & OTA Fix

Rooting Black Shark 3 / 3 Pro the Correct & Easy Way - BL Unlocking, TWRP & OTA Fix
Greetings fellow Black Shark users!
This guide is made for Black Shark 3 Pro Global version, but in theory it should work with any version if the bootloader is unlocked.
Warning: Before you start, backup your phone data as this would wipe your phone!
Do this at your own risk, I'm not responsible if you break your phone!
Prerequisites:
- Update your phone to the latest version possible.
- Download ADB, BOOTLOADER UNLOCK TOOL & TWRP Installer for Black Shark 3 Pro Global or Black Shark 3 Global.
On Phone:
1- Enable Developer Options. (Go to Settings, then About Phone, then Tap on Build number 7 times, then enter your password if needed)
2- Enable OEM unlocking. (Go to Settings, then Additional Settings, then Developer Options, then enable OEM unlocking option, then enter your password if needed)
3- Enable USB Debugging. (Go to Settings, then Additional Settings, then Developer Options, then enable USB Debugging option)
On PC:
4- Run BS3Pro_by_KM Installer. (Use the right version for your device. Right click and choose run as administrator. On driver installation popup click Next, then Install and Finish. Also Install dotNet3.5 if it ask for it. You must reboot your PC after the installation.)
5- Connect your Phone to PC using USB cable.
On Phone:
6- When Allow USB debugging popup appear, tap OK. (Tick Always allow from this computer)
On PC:
7- Make sure google drivers installed correctly and that your PC can see your Phone. (Android ADB Interface)
8- Open Command Prompt as administrator. (Type CMD in Windows search bar, then right click on Command Prompt ‘cmd’ and click on Run as administrator)
9- In CMD type:
Code:
cd c:\adb
Then press Enter key.
10- In CMD type:
Code:
adb devices
Then press Enter key. (If you can see a Device ID with ‘device’ written on its right, then continue to next step, if not then recheck your drivers. If you see a Device ID with ‘unauthorized’ written on its right, then go back to step 6)
11- In CMD type:
Code:
adb reboot edl
Then press Enter key. (To enter EDL mode)
On Phone:
12- You will only see a black screen on your phone. (This is normal, but your phone will be connected to your PC)
On PC:
13- Disconnect and reconnect your Phone to PC using USB cable then make sure the drivers are installed correctly and that your PC can see your Phone. (Qualcomm HS-USB QDLoader 9008)
14- Go to C:\adb and run MiFlash application, then click “refresh”. (You should see your device in the table now)
15- Click “select” and choose “C:\adb\Unlock” folder, then click “OK”, then click “flash”. (When it says done go to next step)
On Phone:
16- Disconnect the USB cable from your Phone, then hold power button and volume down button for 15 seconds until the phone reboots into Fastboot mode.
17- Make sure you see Fastboot mode on your phone screen. (With big green START on top)
On PC:
18- Reconnect your Phone to PC using USB cable then make sure google drivers installed correctly and that your PC can see your Phone. (Android Bootloader Interface)
19- In CMD type:
Code:
fastboot devices
Then press Enter key. (If you can see a Device ID, then continue to next step, if not then recheck your driver setup)
20- In CMD type:
Code:
fastboot flashing unlock
Then press Enter key. (This will unlock the bootloader, if you see an error make sure that your model is supported)
21- In CMD type:
Code:
fastboot erase userdata
Then press Enter key. (This will wipe userdata “Factory Reset”)
22- In CMD type:
Code:
fastboot getvar current-slot
Then press Enter key. (This will show you which slot you’re currently using, note it down)
23- In CMD type:
Code:
fastboot boot twrp.img
Then press Enter key. (This will boot TWRP, if it doesn’t work the first time, then force reboot your phone and repeat steps 16-21, you can skip step 20-22 if you already performed them)
On Phone:
24- Make sure TWRP is booted on your phone.
On PC:
25- In CMD type:
Code:
adb pull /dev/block/bootdevice/by-name/boot_a stock_boot_a.img
Then press Enter key. (This will copy the stock boot_a.img into your current directory)
26- In CMD type:
Code:
adb pull /dev/block/bootdevice/by-name/boot_b stock_boot_b.img
Then press Enter key. (This will copy the stock boot_b.img into your current directory)
On Phone:
27- In TWRP, go to Reboot, then system.
28- Download and install Magisk Manager from here. (Once the phone is booted correctly)
On PC:
29- In CMD type:
Code:
adb push stock_boot_X.img /sdcard/Download
Then press Enter key. Change ‘X’ to your current slot from step 22, mine was ‘stock_boot_a.img’. (This will copy your stock boot.img to your phone’s Downloads directory)
On Phone:
30- Run Magisk Manager, tap on the first INSTALL button on the top right, when it asks you to Install Magisk tap INSTALL, then tap on Select and Patch a File, and choose your stock_boot_X.img from ‘Download’ directory. When it’s done it will create a new file in your ‘Download’ directory named magisk_patch.img. (Don’t tap Reboot, just tap back and close the App)
On PC:
31- In CMD type:
Code:
adb pull /sdcard/Download/magisk_patched.img
Then press Enter key. (This will copy the patched boot.img to your current ‘adb’ directory)
32- In CMD type:
Code:
adb reboot bootloader
Then press Enter key. (To enter Fastboot mode)
33- In CMD type:
Code:
fastboot flash boot_x magisk_patched.img
Then press Enter key. Change ‘X’ to your current slot from step 22, mine was ‘boot_a’. (This will flash Magisk to your boot)
34- In CMD type:
Code:
fastboot reboot
Then press Enter key. (This will reboot your phone)
On Phone:
35- Run Magisk Manager, check if Magisk is installed and you have two green ticks on the left.
Congratulations! Now you have successfully rooted your Black Shark 3 Pro !
Fingerprint Calibration Tutorial (This is needed if the fingerprint sensor is stopped working)
1- Dial this from your phone
Code:
*#*#466349#*#*
This will take you to the fingerprint calibration page.
2- Tap on 售后校准, then you will be ask you to add the FLASH FLA.
3- Now tap START, and then immediately press your thumb on the fingerprint scanner area, keep you finger pressed until the step is completed.
4- Now it will ask you to add the black FLAT. (This means you have to wear a 'black' cloth on your thumb or a black glove before pressing your thumb on the fingerprint scanner, then hold your thumb on the fingerprint scanner area until the calibration is complete.)
5- When done successfully, reboot your device then try to add your fingerprints.
Full OTA Factory Image for Black Shark 3 Pro Global “MBU-H0" - Fix most phone's issues and restore it to factory state. This also fixes OTA updating issues.
1- Download this zip file MOBS2005121OS00MP1.
2- Rename km_update.zip to update.zip and move it to “ota” directory in your phone.
3- Dial this from your phone
Code:
*#*#1027#*#*
Then press "LOCAL UPDATE" and start updating your device. (You might need to do this twice)
4- Update your device to the latest version from the settings.
Special thanks to:
@John Eveline for the Bootloader Unlocking Tools.
@wzsx150 for Black Shark 3 Pro TWRP.
@topjohnwu for Magisk.
@Snoop05 for ADB Installer Code.
PS: I put a lot of time and effort in making this guide, if you want to copy it to somewhere else, then at least give credit!

miflash keep says no fastboot
cant recognize my phone

rowihel2012 said:
miflash keep says no fastboot
cant recognize my phone
Click to expand...
Click to collapse
Please redownload it, it should work fine now.

KM7 said:
Please redownload it, it should work fine now.
Click to expand...
Click to collapse
Ok thanks my friend

KM7 said:
Please redownload it, it should work fine now.
Click to expand...
Click to collapse
same problem
no fastboot
all drivers installed

rowihel2012 said:
same problem
no fastboot
all drivers installed
Click to expand...
Click to collapse
Try downloading it again, sorry for this a file was misplaced. Fixed now.

KM7 said:
Try downloading it again, sorry for this a file was misplaced. Fixed now.
Click to expand...
Click to collapse
sorry bro
no fastboot
it cant detect my phone
same problem

when i try to unlock the bootloader
i got an error : the write timed out

rowihel2012 said:
sorry bro
no fastboot
it cant detect my phone
same problem
Click to expand...
Click to collapse
Make sure the drivers are installed correctly and reboot your PC. I've just tried it and everything work just fine on my PC.

stark7i said:
when i try to unlock the bootloader
i got an error : the write timed out
Click to expand...
Click to collapse
You mean in MiFlash or Fastboot? please specify which step # you are stuck in.

KM7 said:
You mean in MiFlash or Fastboot? please specify which step # you are stuck in.
Click to expand...
Click to collapse
i am stuck at step 13. the miflash cant find my phone. i have re-downloaded everything and still doesnt work. any suggestions?

appless said:
i am stuck at step 13. the miflash cant find my phone. i have re-downloaded everything and still doesnt work. any suggestions?
Click to expand...
Click to collapse
Make sure your drivers are installed correctly as shown above. When in edl mode the drivers are different than fastboot. Try reinstall the application with right click and ‘run as administrator’.

Do you know how to relock the bootloader?

KM7 said:
You mean in MiFlash or Fastboot? please specify which step # you are stuck in.
Click to expand...
Click to collapse
its was in the miflash but it works fine now i have changed my usb cable to an original one and it works fine , i have successfully rooted my BS3 with TWRP thanks alot

KM7 said:
Make sure your drivers are installed correctly as shown above. When in edl mode the drivers are different than fastboot. Try reinstall the application with right click and ‘run as administrator’.
Click to expand...
Click to collapse
still a no go for me. i have reinstalled every driver and still doesnt work. nothing is showing up on miflash. the pc made the sound when i connected but still nothing. my pc sees the device but the miflash cant. any suggestions?

appless said:
still a no go for me. i have reinstalled every driver and still doesnt work. nothing is showing up on miflash. the pc made the sound when i connected but still nothing. my pc sees the device but the miflash cant. any suggestions?
Click to expand...
Click to collapse
Use your original usb cable from blackshark. Mine works and use other cable wont work..

chaict said:
Use your original usb cable from blackshark. Mine works and use other cable wont work..
Click to expand...
Click to collapse
using the original cable still doesnt work. now its just saying no fastboot.

stark7i said:
its was in the miflash but it works fine now i have changed my usb cable to an original one and it works fine , i have successfully rooted my BS3 with TWRP thanks alot
Click to expand...
Click to collapse
Glad that it worked for you, enjoy.

appless said:
using the original cable still doesnt work. now its just saying no fastboot.
Click to expand...
Click to collapse
It seems that there is something wrong with the drivers, or maybe the adb installation. Try to find other fastboot.exe and adb.exe then delete all duplicates except for "C:\adb", and don't forget to restart your PC.

jekz_07 said:
Do you know how to relock the bootloader?
Click to expand...
Click to collapse
This should do it but, I'm not sure if this is going to work on a rooted device.
Code:
fastboot flashing lock_critical
fastboot flashing lock

Revisiting key combinations, and getting to fastbootD

[Sorry, this belongs in the Q & A area, but there's no option to delete or move it.]
Here are the hardware button combinations that work on my OnePlus 6T:
[volume up + power] hold until you see the red dot logo, then release theyour phone will boot to system.
[volume down + power] hold for a few seconds until the black and white keyboard appears (maybe the keyboard is only if you have a login PIN set up?) this will boot the phone to recovery mode.
[volume up + volume down + power] hold for a few seconds until you see the Fastboot label then release. This will put the in bootloader mode.
Starting with the phone powered off and NOT connected to your computer, press and hold [volume up + volume down] as you plug the phone into your computer. This will put the phone into EDL mode, which is required in order to use the MSM tool. The screen of the phone will be black but if you followed the procedure the Qualcomm device should appear under the Ports section of Windows Device Manager.
I was unable to get to FastbootD. Here's what happened when I tried various commands:
1.) when in regular fastboot (bootloader) mode and connected to my PC via USB, from a command prompt I typed "fastboot reboot fastboot" the phone only rebooted to the operating system and not to the fastbootD screen.
2.) when in bootloader, as above, I typed "fastboot reboot bootloader", the phone rebooted to the regular fastboot screen. However, I suspected this was not the same thing as "fastboot reboot fastboot" because why would there be 2 identical commands?
3.) the "adb reboot" command would not work when I was in bootloader mode. Duh! I needed to be in ADB mode for ADB commands to work. In bootloader mode I needed to use a Fastboot command. Still, I had downloaded and unzipped the latest adb/fastboot tools and set up the Windows PATH to point to the unzipped folder. Also, I checked the version numbers of both from the command prompt but still [fastboot reboot fastboot] only rebooted my phone to system. What the heck!?
4.) this all seemed to happen after booting into EDL mode the day before. I booted into EDL mode so I could check if I had the proper Qualcomm driver installed (incase I had to use the MSM tool --yes the driver was installed and functioning). I didn't actually need to use the MSM tool at that time so I didn't ever run it but I'd had some difficulty getting the phone to reboot to system so I assumed my trouble with fastbootD originated with that. Wrong!
SOLUTION: It turned out to be a hidden instance of outdated adb/fastboot that kept running in lieu of the newly downloaded copies, in spite of my having correctly set up the Windows PATH. (more on this below in my reply of Jan 9, 2022).

So adb reboot recovery
And
adb reboot bootloader
Dosent work?

Kenora_I said:
So adb reboot recovery
And
adb reboot bootloader
Dosent work?
Click to expand...
Click to collapse
adb reboot recovery does work. Weirdly, adb reboot bootloader will work ONCE then if I try to issue the command a second time, adb can't see my device. If I unplug the phone from USB, restart the phone then plug it back in, I can again use adb once.

Fastboot logo is showing?

Kenora_I said:
Fastboot logo is showing?
Click to expand...
Click to collapse
what would a fastboot logo look like?

The words fastboot. Will be shown

Kenora_I said:
The words fastboot. Will be shown
Click to expand...
Click to collapse
I can get to fastboot. Just not by using the volume up + power combo and I can't re-enter fastboot by using [fastboot reboot fastboot] from the command line. The command line issue is of more importance, ultimately, but I think it's reasonable to assume the root cause of both is the same since they happened at the same time.

Can you check if System>Developer Options>Advanced Reboot is enabled?

FakeGemstone said:
I can get to fastboot. Just not by using the volume up + power combo and I can't re-enter fastboot by using [fastboot reboot fastboot] from the command line. The command line issue is of more importance, ultimately, but I think it's reasonable to assume the root cause of both is the same since they happened at the same time.
Click to expand...
Click to collapse
It changed at some point and OP never updated their docs. (I think it changed when A10 hit).
To get into fastboot mode. You now have to make sure you're not connected to USB and hold vol+, vol-, and power and that will launch fastboot mode.
Also maybe semi related if it's not launching at all, is to do a factory reset from within the OS. I had a really odd issue recently with recovery mode and it not booting into recovery from fastboot, adb, or key combo press. Factory reset from within the OS somehow fixed it.

psychen6 said:
Can you check if System>Developer Options>Advanced Reboot is enabled?
Click to expand...
Click to collapse
Yes, I have this option enabled. Using this method is one of the ways I am able to get to fastboot. I am just not able to get to fastboot using [fastboot reboot fastboot] from a command prompt (used to work just fine) and I am not able to get to fastboot by holding the [volume up + power] (this also used to work just fine).

hartleyshc said:
It changed at some point and OP never updated their docs. (I think it changed when A10 hit).
To get into fastboot mode. You now have to make sure you're not connected to USB and hold vol+, vol-, and power and that will launch fastboot mode.
Also maybe semi related if it's not launching at all, is to do a factory reset from within the OS. I had a really odd issue recently with recovery mode and it not booting into recovery from fastboot, adb, or key combo press. Factory reset from within the OS somehow fixed it.
Click to expand...
Click to collapse
I don't know about that. A few days ago volume up + power used to work just fine. Also a few days ago, I also used to be able to issue fastboot reboot fastboot from a command line and have it work fine.
Now what happens when issue the command fastboot reboot fastboot is that my phone appears to begin the reboot cycle. A message in the command window appears, "rebooting into fastboot" then on the next line, "< waiting for any device >" and meanwhile my phone just boots into the Oxygen OS. If at that point I select "bootloader" from the advanced power button menu, the phone reboots into fastboot and the message in the command window reads, "fastboot: error: failed to boot into userspace fastboot; one or more components might be unbootable."
If I then issue the command, fastboot reboot bootloader, that reboots promptly into fastboot, but I don't believe "bootloader fastboot" is the same thing as "userspace fastboot", although the states look identical on the screen.

After revisiting this issue again and reading every post I could find I realized the only explanation was outdated fastboot, and since they're packaged together, adb also. This time I did a extra thorough search of all the drives and sure enough there was a super old instance of adb.exe & fastboot.exe in a place I'd never thought to look. So I deleted those files and now adb and fastboot work as expected.
I know, it seems obvious now. But there were references to those old files in windows system settings that took precedence over my PATH setting that I didn't realize were there. Ive since deleted those other references but I wanted to mention this in case other people are wondering why the PATH they set up isn't working.