yashsingh1/xdaforums huggingface dataset:
[Google Home] deadman96385:
This guide supports the following devices: SD-8501F, SD-X701B, SD-X501F

How to Bootloader Unlock (Part 1 of 2):

1. You will need a USB A to USB C cable

2. You will need fastboot drivers on your PC

3. Unplug the power cable from your device

4. Remove the silicone cover from the bottom right of your device (Might be hard it has adhesive on the back)

5. Plug the USB C cable into the now revealed USB-C port

6. Hold the volume - button and plug in the power cord keep holding volume - for about 10-15 seconds (It is slow to boot to fastboot) Smart plugs or switches help so you don't damage the ports by replugging them constantly.

7. Keep holding volume - for about 10-15 seconds (It is slow to boot to fastboot)

8. Once the device shows up on your computer in a terminal run the following command:

fastboot flashing unlock

AVB/DM-Verity Unlock (Part 2 of 2)

Unlocking the bootloader really does not give a lot to us because all the partitions are still being verified and the device will not boot if they don't match. Word of warning doing this causes the stock OS not to boot fully.

If you are coming from part 1 you can start right away, if not you need to reboot to fastboot again.

1. Extract the downloaded AVB unlock zip

2. Run either the avb-unlock.bat or this command in a terminal

at_auth_unlock.exe creds\

3. Wait till it finishes

4. Keep in mind the stock system does not boot properly with AVB off (It is weird some UI elements work but the boot animation never goes away)

5. To relock AVB in the future run the following command or the Avb_lock.bat:

fastboot oem at-lock-vboot!

Now that you are AVB unlocked you can flash the firmware/partitions from fastboot using the flash-all scripts located in the firmware zips.

Blueberry 10" Firmware:

Spoiler content hidden.

Amber 8" Firmware:

Spoiler content hidden.

Unified 8" and 10" Debug/Development firmware (Only tested on Blueberry/10" but these should work on Amber/8" as well)

Spoiler content hidden.

AVB Unlock tool:

Here

Amber and Blueberry EDL Firehose:

Here

The firmware provided allows you to have adb and adb root on either debug or user. But the downside is with avb off the device can't access its Tee keys so the user firmware will not finish setup. But you can still install other apps and use root which allows you to fully turn off the security restrictions to allow you to edit files on the device. The commands you need to run are these:

Spoiler content hidden.

Useful adb and android things commands:

Spoiler content hidden.

Various Screenshots:

Spoiler content hidden.
[Google Home] bs3pro:
Is there another forum, or talk about what exactly we can do with this fw?? Thanks. Also my comp not seeing the device in fastboot. Yes I have adb and fastboot tools.
[Google Home] agentdr8:
Also not seeing the device in fastboot while holding Vol + and plugging in the power. Tried Vol -, and got the new USB device notification, but holding Vol - doesn't seem to get to fastboot, and it'll just boot to the normal OS.
[Google Home] bs3pro:
I can see other phones in fastboot, just not this smart display. WTF? I think this is a BS thread.
[Google Home] deadman96385:
Very sorry about the delay, it seems I made a minor typo in the instructions. I said to do Vol+ for fastboot when it is really Vol-. If you do not get a fastboot device after doing that open up device manager and install the google usb driver on the missing driver device. This method very much does work, I had someone test it on the 8" as well as a few people on their 10" and 7" devices before I released it on XDA.
[Google Home] agentdr8:
Will give it another go. Thanks for the reply.
[Google Home] bs3pro:
ok, im in fastboot!

AND....I get this. ugh

C:\Users\Owner>fastboot flashing unlock FAILED (remote: 'oem unlock is not allowed') fastboot: error: Command failed
[Google Home] deadman96385:
Try and just doing the avb part, it seems on some newer firmware's its tied into avb unlock/lock so when that is unlocked it unlocks the BL.
[Google Home] agentdr8:
Holding Vol- makes a QUSB_BULK (VID 05C6, PID 9008) device show up in Device Manager, which I think is EDL mode and not bootloader? I tried changing it to the Android Bootloader Interface driver but fastboot never seems to find it.

Holding Vol+ makes it boot to what seems to be a missing recovery mode, with the "dead" Android and the red exclamation point icon, but that doesn't lead to any USB devices being seen.

Any thoughts?
[Google Home] bs3pro:
You don't have bootloader drivers installed
[Google Home] bs3pro:
i unlocked, and flashed the universal fw to my 8inch. Now i just have black screen. It always just reboots to fastboot.

EDIT!! The flashall.bat file is corrupt!!!!!!! Need to edit out the format userdata line, otherwise the flash fails!!!
[Google Home] edugaga:
When try to flash the firmware fail with error mke2fs: invalid option -- 'b'

Error: Unknown option ?

If I coment the lines:

#if [[ "${WIPE_USER_DATA}" = true ]]; then

# ARGS+=( format userdata )

#fi

Don't fail, apparently it works fine, I can set it up, connect to google home app.

After this, the update screen appears, when it reaches 100% it restarts and starts the update screen again. And this in an infinite loop.

Any idea how I can fix it? Or just install any linux ?
[Google Home] CatBug:
Can I perform this on Linux PC? I guess not since it requires running .exe file.
[Google Home] lsx90:
I have SD8501F I was able to get it into fastboot mode on both linux and windows pc, but that's about it.

On linux it was recognized right away, on windows I had to manually install google android bootloader driver once it popped in device manager.

It failed to unlock.

fastboot devices return this:

HUA0777K fastboot

--------------------------------------

fastboot flashing unlock:

...

FAILED (remote: oem unlock is not allowed)

finished. total time: 0.012s

----------------------------------------------------

at_auth_unlock.exe creds\

...

FAILED (status read failed (Too many links))

finished. total time: 0.000s

Command 'fastboot oem at-get-vboot-unlock-challenge' returned non-zero exit status 1
[Google Home] CatBug:
No matter what I try, I can't get to the fastboot from neither linux nor windows. I have fastboot drivers installed on windows, I also used fastboot on linux recently with other device. I can get to that broken bootloader while holding vol up without an issue. But holding vol down does not do anything, it just boots to system as usual :(
[Google Home] bg.stefan90:
I figured at least on my device 10-15sec holding vol down is too much it goes into recovery and leaves it and continue normal boot.

Screen is complete black in fastboot mode, so it's hard to tell when it in.

It's easier on windows as you can see sound when usb is recognized. Then you release vol down.

Basically connecting usb cable hold vol down and plug power, in 2-5sec you will hear usb recognized on windows. Release vol down. And now on windows i had to go to device manager and install driver. On linux it just worked.

Trick is to not hold vol down for too long
[Google Home] CatBug:
That was a perfect advice, mate, thx a lot!

As for other people, fastboot flashing unlock failed but I managed to run at_auth_unlock.exe creds\ successfuly. Then I commented that format user data line and ran the flash all script.

Now the device boots to fastboot everytime. What should I do now?
[Google Home] Axh3ll:
Hello, I've flashed firmware with "success" but my device (SmartDisplay 10'') is not reconized by the command adb devices... I'm stuck there after many tries !

I use fastboot and ADB with linuxMint.

Any ideas ?
[Google Home] CatBug:
Does it get recognized by "fastboot devices"? If so then your device is booting to bootloader after flashing the firmware. Just like mine.
[Google Home] Axh3ll:
Yes it is reconized in fastboot devices, I never success to have it in ADB...
[Google Home] smtelegadis:
I have a SD-X701B 10" display and I'm able to connect and see the device "HUA06J40 fastboot" when I execute "fastboot devices" command. However, when I try to execute the " fastboot flashing unlock" command I get the following error.

fastboot : ...
At line:1 char:1
+ fastboot flashing unlock
+ ~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (...:String) [], RemoteException
+ FullyQualifiedErrorId : NativeCommandError

FAILED (remote: oem unlock is not allowed)
finished. total time: 0.006s

I tried to run the "at_auth_unlock.exe creds\" manually but I'm not having any success. I am wondering if the drivers I have for fastboot are correct. I was able to use fastboot with other android phones without issue.

any help would be appreciated.
[Google Home] smtelegadis:
I read in the twitter post that you need to relock the AVB to have it boot properly.
[Google Home] Axh3ll:
Hello, you are right, but I have already re-locked the AVB, but maybe I've done something in the wrong time during my tries...

Thanks for the advice
[Google Home] CatBug:
So I managed to make some progress. I tried to leave the format user data line in the batch file and successfully flashed the firmware. My smartdisplay now boots to system (lenovo logo, than android things booting animation and finally white screen). I can see the device when using adb devices command. However it is unauthorized. How can I authorize it? I tried methods like deleting the key from computer, killing adb server, checking if adb is the latest version. I haven't found solution to this so far - same behavior on windows and linux. Any suggestions? Thx.
[Google Home] <1>:
I Accidentally turn off the power，and so i only see qualcomm HS-USB Diagnostics 900E （COM11）please help me,thanks
[Google Home] bg.stefan90:
How you managed to unlock oem and flash anything.

I get it connected via fastboot, but unlocking fails every time?

Is there something that i miss in the process?

FAILED (remote: oem unlock is not allowed)
[Google Home] Collin Kim:
Plz, Send me a captured image about showing the 8"(SD-8501F)'s USB-C port.

I want to know the exact position of the USB port.

TYSO~*
[Google Home] lsx90:
under the device there are two rubber pads toward the front, under one of these is the port.
[Google Home] CatBug:
Just try to skip this step and continue with next one.
[Google Home] katc81:
I flashed all firmware posted here. Only the Amber 8" Firmware: Stock Debug Firmware could reboot to the Google setup. But it loops from update to reboot infinitely after setup. Any idea how to restore to the original firmware? Thanks!
[Google Home] CatBug:
I successfully flashed Android 8.1 Debug Firmware (using windows computer, it failed on linux - /usr/lib/android-sdk/platform-tools/mke2fs failed with status 1 fastboot: error: Cannot generate image for userdata). ADB works, I managed to change launcher to KISS. I wonder if it is also possible to activate navigation and notification bar. Gestures in KISS launcher do not work.

Overall, I find it sad that OP took the effort to test everything and provide steps and resources but provides zero support afterwards.....
[Google Home] RaZoR No1:
So what can we do with this?

Install apps? use it as a normal tablet? and is it useable or is it still too buggy?

I have two of these devices and if I could convert one (and somehow still be able to keep the smart display functions) it would be great
[Google Home] katc81:
After flashing the Android 8.1, OP opened a window on the second floor for me. I need to climb in with a ladder to this empty house. I sideloaded Home-assistant wall panel app and installed Lovelace Wallpanel Screensaver from HACS. When idle it shows time and weather, otherwise I have full control to my HA besides my bed. Now I have a bedroom and Kitchen. What about a living room....
[Google Home] bg.stefan90:
This is exactly what I want to do with my unit it's collecting dust in the box, but if i could just install browser or wallpanel to run HA dashboard that would be awesome kitchen unit.

I have wall tablets in living room and bedroom, this would br the missing pieces in the kitchen.

I tried to skip failed step, but still no luck with flashing it
[Google Home] edugaga:
I found a solution to my problem.​

In all the linux distributions that I tried I had the same problem. I just had to do the same, but from windows.

I was able to install android 8.1.

The Home Assistant app works perfect for me.
[Google Home] ducksoup18:
Can you provide more information or maybe put together a blog or something with the steps you took? This looks promising for sure!
[Google Home] edugaga:
In my case the audio works perfectly after flashing (before it also worked perfectly), the home assistant app plays the audio well for me. I don't know if flashing will solve your audio problem.
[Google Home] lsx90:
I'm trying from windows, but getting error here as well, first it fails to unlock oem, but as someone suggested I continue with other steps, but it doesn't let me flash the firmware, I used SET FLASH_IF_LOCKED=true as env variable and it starts flashing but after successfully pushing the first file fastboot just stops and shows help desc like what fasboot --help would return. I think it might be version of fasboot or android driver on windows that made it work for you and the other guy.

Can you share fasboot version and which android driver you used when you flashed?

I think this is the only variable everything else is the same, but it worked only for couple of people and doesn't work for rest.
[Google Home] lsx90:
my device got bricked after failed attempt to flash it with FLASH_IF_LOCKED=true

Now when connected to usb it shows as qusb_bulk I was able to install qualcomm driver and it's in EDL mode. I see there is a Firehouse file at the first post, assuming for unbricking, but I can't figure out how to flash it.
[Google Home] bg.stefan90:
Yep my device is definitely bricked after failed flash... it does automatically boot into edl diag mode 900E driver, I modified usb cable to boot it into edl download moden 9008 driver.

It does get into edl download according to pid9008... but I'm unable to push anything to it.

Is there a solution for something like this?

Any thoughts. It's completely dead at this point except it's recognized by usb by both win and linux. So willing to try anything to unbrick it. I tried buch of tools for Qualcomm edl protocol. Using one of them reading devices details works but only immediately after reboot it, and it stops after it get cpu info
[Google Home] edugaga:
I have only used the latest version of android studio with the fastboot and adb that it includes, also the google usb drivers that allow you to download from android studio. Change the driver to the device that recognizes windows to Android Bootloader Interface, (the one that Andorid Studio installed when downloading Google USB Driver).
[Google Home] edugaga:
I just followed the steps in this blog. And to install home assistant, I only had to download the apk and install it through adb and uninstall the app that starts every time you start the device. In this way, only the launcher that you have installed starts and from here you can open any app that you install
[Google Home] focuskr:
lose chromecast and g assistant features?
[Google Home] gforums:
Dear all,

I tried now all three different versions, but can't get further:

1.) stock os: successfully flashed, but devices keeps within an infinite "update-restart-update" loop.

2.) android 7 and android 8.1 debug: Flashed both of them, but screen remains black after reboot

I can always get back to fastboot but currently I don't get a working system out of my system.

I am using the 8 inch version ("Amber").

fastboot, adb are present.

no issues during flashing, only the unlock-commands fail.

any idea what to try next?

thanks and best wishes,

Christian
[Google Home] gforums:
Really no one that was able getting this running on the 8 inch version? Or who was able to recover original ROM?

Sadly currently the device is rendered completely useless as none of the versions is working and a restore ROM seems not being available. Therefore thanks for any help.
[Google Home] 54lin45:
Hi

I acquired my SD recently with the audio probems. As is, whilst the stock firmware worked ok, its pretty useless without sound.

I read the above instructions over and over and thought that I would be competant to attempt reflashing a stock image or even android 8.1.

However it all went wrong and it happened so quickly that the process is now all a blur.

Note to self, stick with hardware issues and dont go beyond your own capabilities.

Having spent days trying to get AVB to work, unable to load correct drivers, the penny dropped when I read a comment of someone who said that the machine was in EDL mode and thus "waiting to download"

I searched the web, installed QPST and read some more. I gather that I should be using QFIL which is designed to flash the object when it is in EDL.

Now I am at the point where, Qusb drivers installed and working fine.

Have started QFIL. Found the Firehose code in this thread, downloaded and entered path for the file.

But unable to do anymore since QFIL will not let me proceed without the name and path of the XML file/ files.

I can see stock firmware above and have downloaded, but when unzipped or unpacked these appear as .IMG files. Which the program wont allow.

Are there .IMG files for the 8501F anywhere or is it game over for me?

regards

Simon
[Google Home] Scags104:
Having the same issues described above. I think ive bricked the unit.

Any working steps to restore so i can try again?

At this point im able to flash while in fastboot but seem to be stuck in a loop back to fastboot and no way to re-unlock bootloader?
[Google Home] Scags104:
Guess we have been abandoned by OP

First guide ive followed that ruined a device. Not a good feeling.
[Google Home] deadman96385:
I don't have the rawprogram0.xml, but you can use the partition manager feature under tools in QFIL without it to dump/write partitions to your device. I followed the guide from start to finish to validate that it was correct before posting. I've been away for awhile, and kinda forgot about these devices.
[Google Home] Scags104:
Thanks for the help! hopefully this is one step closer.

1) Found QFIL

2) Installed Drivers

3) Downloaded Programmer

4) Finds Device

5) Fails when trying to open partition manager

"Fails to find QDLoader port after switch to emergency Download mode"

Any suggestions?
[Google Home] deadman96385:
Check in device manager to make sure that the driver is loaded. You may see something with a ? Device if so you need to install the driver.
[Google Home] Scags104:
I did check that and comes up properly as a Qualcomm device
[Google Home] Scags104:
I have second device - would it be possible to use it to get this bricked one up and running. How would i go about getting the rawprogram0.xml?
[Google Home] Renk1:
HI, I've been following this thread for some time, my display running fw 40.16.5.426523610 gets recognized on fastboot but can't seem neither to fastboot nor avb unlock on a windows 11 pc, anyone has an update or some tips?
[Google Home] Schizopriest:
Wanted to give my findings here, too:

I had quite some troubles doing the flashing.

First time I used linux and couldn't run `fastboot flashing unlock`, but `python at_auth_unlock.py creds/`.

After flashing Debug 8.1 I was in a boot-loop with the 4 Google-dots.

So I tried flashing the factory build, ended up in a update-loop and was not able to flash anymore (device was locked) and unlock.

-- Switched to Windows here --

I then did the "stupid" thing and flashed without unlock the 8.1 firmware again, ended up with a blacked-out-device, not recognized by fastboot anymore.

Under Windows I had only an unrecognized "Android" in my device manager, nothing else was possible. Plugged into my linux laptop, saw it was recognized by fastboot and flashed the factory build again.

Device ended up in update-loop again, figured out, that when you hold down volume (to go into fastboot) while it is rebooting to install the update, you can unlock the device again (with AVD_unlock.bat).

Installed 8.1 again and I'm back in the boot-loop with the 4 Google dots.

Checked the guide again and saw it won't finish the setup (should have read that the first go), ran the adb commands, as it's now recognized by adb.

I was now able to install a custom Launcher and have it running with it.

Is it somehow possible to still run the Assistant Core launcher somehow, maybe by relocking after flashing the factory image again? I would just like to have a couple of additional apps besides the Assistant Core Launcher.
[Google Home] Schizopriest:
Does anyone happen to have a stock factory image of a EU / DE system? It seems like the one provided by the TO is US, maybe this is the issue why it's in constant update-looping.
[Google Home] jangeenidee:
Hello, it looks like you are active on the subject.

Here is where I stand.

I connected the USB cable and pushed the + button while putting it in my W10 computer. Then I added the following driver : https://support.lenovo.com/in/en/downloads/ds022366-adb-interface-driver-thinkpad-tablet

After this, I was able to use the following commands successfully

fastboot flashing unlock

avb-unlock.bat

→ I see constantly 4 balls turning around

Then I went to the flash-all scripts (located in directory B_User). Nothing happened.

Overnight Windows rebooted.

I tried to recognize the device again by unplugging it and plugging it back in. Now it indicates that it doesn't find the device any more.

Here is what I found in device manager (although when I disconnect the USB cable I don't hear anything)

I don't know what to do at this stage. Please advice
[Google Home] jangeenidee:
Were you able to go back ?
[Google Home] Scags104:
Still waiting for @deadman96385 to confirm if i can use a working unit to get the rawprogram0.xml that we may need to revert the bricked unit
[Google Home] 54lin45:
Hi

Looks like things have gone quiet and many of us havent managed to get any further without the raw program.xml and patch file.

I did some googling on how to create both files, it seemed to require python and a greater understanding than I have. But it should be possible.

A couple of nights back I came across this thread which included both files but for the tablet version of the sd-8501F( I understand from other forum users that the 8" Lenovo tablet also uses the snapdragon and bares an uncanny resemblance)

That said I followed the thread over here: ( relates to the thinksmart version for video conferences, but I understand those apps can then be rmoved)

https://xdaforums.com/t/cd-18781y-l...zoom-teams-conversion-normal-android.4426029/

Needless to say, I didnt get anywhere?

Anyone else on the same level of intellect as me had any luck yet?

Simon
[Google Home] GnatGoSplat:
What is the status of this hack? Looks like most recent posts indicate the hack is no longer working.

I have a couple of these devices that I was thinking of hacking since Google is no longer supporting Android Things and these can no longer browse the web.