yashsingh1/xdaforums huggingface dataset:
[Google Home] 54lin45:
Difficult to say really. I think it was successful but only if you know what you are doing. I cant speak for the others who find themselves in the same boat as me, but like the saying says " a little knowledge is dangerous"

I tried following the instructions but I think I got myself tangled by the use of "terminal". To me a terminal is something like Termite whereby 2 way coms is achieved using serial, when I think what someone really meant was "open a command prompt"

Thus I have bricked my unit, or lets say, it is stuck in EDL mode and waits for an upload using QFIL.

However as those including myself have found, QFIL needs the Raw xml file and Firehose.

Firehose we have, its in this thread somewhere, however the XML file we dont.

I have googled around and can see that it is common to roll your own XML file, which necessitates the use of Python.

But I cannot find the relevant files ( in this thread) that need to be included when making the XML.

I guess it was just one step too far for me.

Even if the XML etc was provided by a forum member, I understand that there are further issues relating to the finicky use of QFIL which often throws up various errors when trying to upload.

Maybe it might be a better idea to fit a Raspberry Pi inside and use the onboard display header and investigate if it is compatible with the 8" screen ( in my case 8501F)

However any input would be helpful as the thread seems to have gone cold.

Simon
[Google Home] GnatGoSplat:
I see. So the step you messed up on is "fastboot flashing unlock"? Or did you get past that?

The command-line is called "Terminal" on MacOS, so I could see how someone might call it that.

If this is that easy to screw up, maybe I'd best sell mine intact while it's still worth something, and replace it with a Google Nest Hub Max.

Although I do wonder if this, running full Android and using Google Assistant Ambient mode, would be equally as functional as a real Google Nest Hub device or not. Or would this even support Ambient mode on full Android?
[Google Home] paulzh5`:
My 10-inch device is bricked. When I flashed the stock degbug firmware, I can only enter 900E. Can anyone tell me how to enter fastboot or 9008. what should I do? Thank you。
[Google Home] paulzh5`:
My device is used by Lenovo employees for testing and cannot be logged in. I think through fastboot, it can be revived because developing firmware used to.
[Google Home] paulzh5`:
me too
[Google Home] Scags104:
Well, this has been a waste of time and a device. For others finding this thread. Dont try it. Youll lose your device. This should be taken down
[Google Home] nucleiis:
Thank you very much OP! I had a bricked LSD10 over a year ago and I could successfully repair it by reflashing the stock debugging firmware. Although commands didn't run well and produced many errors, I could manage to execute every single flashboot command and it did work indeed!
[Google Home] freddy0000:
So is this not even worth attempting
[Google Home] 35mmslr:
I dont think so. This was a good idea but now I have a SD-8501 in a perpetual boot loop.
[Google Home] Sjll:
@bs3pro

@lsx90

@bg.stefan90

I found the way to unlock device if your met

FAILED (remote: oem unlock is not allowed)

The steps via QFIL you can follow ZTE guide.

I provide you the devinfo.img which is unlocked.
[Google Home] deadman96385:
Wow this is pretty cool to know, sorry I didn't get your message in time. Nice work!
[Google Home] i_max2k2:
Hello,

I'm going to attempt this on my 10" Smart display. Seems like some people were able to do this? Is there any revised steps I should follow from the first post? Thank you.
[Google Home] Kianouch:
Yeah I wonder about the same too.

I'd like to buy a Smart Display 8 and flash it to have Nova Launcher and Android apps such as Home Assistant on it but I'm wondering if it will work at all...

I already have a Lenovo Smart Clock running Android apps, it works fine but I dont like having to use volume buttons mapped as Home and Previous keys + their original function, it's annoying.

Or, perhaps it would be better to buy a Lenovo ThinkSmart View ?
[Google Home] mu1111:
Deleted
[Google Home] Sjll:
1.Holding vol + & vol - same time, plug in power, then device will boot into qcom edl mode. Install the qcom 9008 drivers and QPST.

2. You can use QFIL in QPST, restore the image I provided ( for devinfo partition), then the device could be unlocked. (Google it, then you will know how to use QFIL)
[Google Home] zim2dive:
Coming in to this party late...

so if I understand the situation

- you can unlock

- at which point you could sideload some apps (standard adb sideload?)

- modify some startup script

- relock

- and you'd be off and running?

But the details on modifying the startup aren't described well here (ie. as in a full step by step walkthru for the less experienced?)

Is that a fair summary?

(Ive got a 8" Lenovo I was hoping to convert to a kiosk type pointing to a fixed IP (family info web page on local apache server.. at this point the clock is effectively e-waste I guess, but I keep holding out hope)
[Google Home] mu1111:
Hi, thank you for your help. I tried to get to Partition manager in Qfil but "process fail". What should I do please?
[Google Home] _raydroid:
I'm wondering the same thing too.

Lenovo's ThinkSmart View is getting a lot of attention nowadays on XDA and other home automation forums, but Lenovo's Smart Display devices use the same Snapdragon 624 chipset and do not have much activity going.

What are the differences in the devices that is causing a lack of interest in this device? Are the partitions more finicky to deal with on the Smart Display?
[Google Home] larastafarian:
Hi, I should have read on the comments before trying this. I successfully unlocked & I believe I installed the 8.1 firmware but I just get a black screen - ABD commands don’t work, example if I do ADB devices list of devices is blank however If I type Fastboot flashing unlock it’s says device already unlocked! Am I doing something wrong after the flashing element?
[Google Home] larastafarian:
So digging further into this I video recorded installing the 8.1 firmware & it fails saying

Sending ‘system_a’ Failed (remote: ‘data too large’)

Anybody know what causes this?
[Google Home] Sjll:
Be sure you choose 'emmc' in QFIL configurations, not 'ufs'. If it still failed to get GPT, try to use firehouse from here.
[Google Home] mu1111:
Hi Sjll, does not work, but thanx anyway :)
[Google Home] larastafarian:
Somebody please help me😂😂😂
[Google Home] jonathanrob:
Hey, I have had this issue too and I think the issue was the partition was too big? I had to modify the script with the fastboot -S argument and which splits the partition into smaller chunks
[Google Home] larastafarian:
Hi Jonathan, that’s for the reply… any chance you could explain how to modify the script to do this?
[Google Home] jonathanrob:
I'll try my best lol.

Open the flash-all.bat or the .sh version (i didn't test the .sh version but it should be similar)

Go to the lines in the photo and add the -S infront (50M worked for me but it could change for you)

The section does change a bit in the different flash-all files depending on the android version or if you're going back to factory. Hope this helps!
[Google Home] larastafarian:
Hi thank you that, it flashed the system image with those changes..still haven’t got it to work though - it gets to setting to slot A & then quits… I suppose I’m 1 step further 😂
[Google Home] jonathanrob:
That is very strange. I'm not sure what could be causing it as that didn't happen to me if I recall correctly. If you haven't already try changing it from 50M to 20M. Another issue may be that you used the wrong unlock mode for the software version you are trying? (Differs for 7 and 8.1) What's the file name? Blueberry_Prod, Blueberry_Qualcomm or amber-factory? Also make sure you follow the steps in @deadman96385 's post as if you do miss one it usually won't work.
[Google Home] jonathanrob:
Also try editing this line as this is where it was hanging for you (It did set the slot to a since there's the okay message). That should fix it I think? (EDIT: I did some more digging and I don't thing this will help actually. The only issue I'm thinking of would be the wrong mode in the avb_unlock tool?)
[Google Home] larastafarian:
Hi thanks for all your help. The user data line needs to be deleted & it flashed. I got 8.1 working. Next mission try get homeasisstant working on it. Have tried fully kiosk & wall panel apk but I suspect web view is too old.
[Google Home] jonathanrob:
I’m sure you figured this out by now but the 8.1 webview will work from what I remember! Only annoying thing is there’s no settings app like on the 7.0 version so it’s more difficult to change anything but then the 7.0 webview is too old. I also wish you could keep the Google assistant working (just the voice) but use your own dashboard + extras. Let me know how it works for you though as I might try it with mine again!!
[Google Home] ducksoup18:
So i got all this working and loaded up the latest HA apk but after selecting my server, it just shows the HA Icon and a white screen without the ability to login. Any ideas on how to get passed that? I tried using both IP address and domain i have (https) but neither worked. Just sits there with a white screen and just the HA icon. I tried both minimal and full apk installs. Might just install chrome or some browser and use the browser version but would like it to work with an APK. Would also be cool if i could get the custom wake word stuff working on this as well since its got a microphone.

Also, i installed 8.1 using the unified firmware. Should i have used the specific Amber version (i have the 8" version of the device) or is that sufficient? Also, does android 7 work better for launching apps and whatnot?
[Google Home] edugaga:
I think I use the normal H apk. I haven't updated the apk since I installed the app. In a few days I can tell you exactly which version I use. (I'm moving to new house and I don't have access).

A while ago I tried using Fully Kiosk Mode with the HA website. The camera and speaker worked well. The microphone loses quality.

Maybe this will work temporarily for now. I'm not sure, but I think I also have amber with android 8.1.
[Google Home] ducksoup18:
Thanks for the response and congrats on the new place. Keep me posted when you get settled. Would like to repurpose this thing.

Edit: GOT IT! I ran a system update and it looks like the updated webview fixed it. The app is running now so thats pretty cool. Now i gotta just setup some kinda kiosk looking screens instead of what i currently have set up on it.
[Google Home] ducksoup18:
Also, just so i am 100% certain about the next steps. After i have all the apks and launchers installed that i want, i then go back and lock the avb so that it can boot normally or do i have to deal with the weirdness of having it unlocked and launching the app via adb? hopefully its the former.
[Google Home] edugaga:
I think I remember I put HA as Launcher by default, and the same in case of Fully Kiosk Mode.
[Google Home] ducksoup18:
Thanks. And once everything is setup, just relock avb and reboot and you're good to go? It'll just boot up HA on start and be ready to roll?
[Google Home] edugaga:
I don't remember if it blocks the AVB after all this. I think just follow the steps in the guide.
[Google Home] ducksoup18:
The guide doesnt really say what to do after youve got root and installed apks. Just wanna know how to do this so i can set it up in a different location without having to have a usb tether to launch HA. I havent tried just turning it off tho in its current state to see if leaving avb off will just load normally and launch HA as my launcher. Might try that next unless others can chime in.
[Google Home] ducksoup18:
I restarted the device and now im getting: ** Error: Unable to connect to activity manager; is the system running? I ran through all the steps again and its accepting adb commands, but i think since i set HA as the launcher its having an issue actually launching. Im gonna try and set it back to the kiss launcher and see if i can at least get something to display on the screen.
[Google Home] ducksoup18:
Ok so im back to square 1. Have Kiss installed and HA installed but still get the with screen (due to an outdates Webview). I can try and run the updater to get it to work, but i still am not sure what the actual steps i should be doing to get it so i can restart the system without running adb commands to launch things. Any help would be great (@edugaga has been quite helpful btw. thank you duder).
[Google Home] edugaga:
The issue of updates it gave me a lot of problems. List all packages with 'pm list packages'. uninstall the app that activates the updates and some more, with the command 'pm uninstall -k --user 0 NameOfPackage'.

As soon as I have access to my screen I can send you a list of the apps I have installed.

If you want, send me a private message, in case you want me to try something so I don't fill the forum with messages.
[Google Home] ducksoup18:
The issue i keep running into is that i dont believe i can uninstall WebView. I havent fully tried to yet, but the updated webview has a different signature (old: com.android.webview, new com.google.android.webview) and i've installed the newer version thats compatible with 8.1, but i dont know how to set it to the default webview. I see that you can do that with magisk but i have no idea how to do that. I installed magisk and when it asks to install the app when its running it asks for you to select a boot.img file for patching, which i dont know much about. I also see people building a bunch of stuff to inject the new version of webview in there but that doesnt seem super user friendly. I've found bormite: https://github.com/bromite and this thing as well: https://github.com/JonaNorman/WebViewUpgrade/issues but i dont know what to do to get these things to work.
[Google Home] ducksoup18:
Just putting this here if anyone has any issues with how to do this all.

From Stock:

1. hold down Vol - and boot into fastboot mode

2. AVB_unlock.bat

3. Choose Legacy Mode (2) to unlock AVB

4. Reboot back into fastboot mode

5. Flash jasper/unified firmware

6. Reboot. You wont get passed the loading page but things are good to go here now.

7. Do the security steps

8. Install your apks and update your launcher

9. Launch settings and connect to wifi and then run a system update.

10. This will update your webview but it'll also update your default launcher, update that again.

11. I mistakenly uninstalled the com.android.iotlauncher so i couldnt get back into settings to see if there was another system update to run but since HA is working for me now, i feel its good enough.

If you get borked up after flashing:

1. Still unlocked AVB, flash stock. This will lock AVB but get you in a normal default state.

2. Repeat steps above.
[Google Home] edugaga:
I confirm that my device is AMBER 8'' (SD-8501F).

This is the list of packages that I have installed right no.

I hope this helps you, when I have more time I will try to help more.

Android 8.1.0

package:com.android.cts.priv.ctsshim

package:com.google.android.ext.services

package:com.google.android.apps.mediashell

package:com.android.providers.telephony

package:com.android.providers.calendar

package:com.android.providers.media

package:com.google.android.ext.shared

package:com.android.documentsui

package:com.android.externalstorage

package:com.android.htmlviewer

package:com.android.companiondevicemanager

package:com.android.providers.downloads

package:com.google.android.things.internal.media

package:com.google.android.iot.frameworkpackagestubs

package:com.android.defcontainer

package:com.android.pacprocessor

package:com.google.wifisetup

package:com.android.certinstaller

package:com.google.android.marvin.talkback

package:android

package:com.android.mtp

package:com.android.backupconfirm

package:com.android.statementservice

package:com.google.android.things.internal.bluetooth

package:com.android.providers.settings

package:com.android.sharedstoragebackup

package:com.google.android.iot.batterycontrolservice

package:com.android.webview

package:com.android.inputdevices

package:com.google.android.things.checkin

package:com.android.onetimeinitializer

package:com.android.keychain

package:com.google.android.things.internal.devicemanagement

package:com.google.android.gsf

package:com.google.android.tts

package:com.google.android.things.permissions

package:com.android.packageinstaller

package:com.android.proxyhandler

package:com.android.managedprovisioning

package:com.android.iot.systemui

package:com.android.cts.ctsshim

package:com.google.android.things.internal.iotsetupwizard

package:com.google.android.things.sparrow.oem

package:com.android.vpndialogs

package:com.android.iotlauncher

package:com.android.shell

package:com.android.wallpaperbackup

package:com.android.providers.userdictionary

package:com.google.android.things.internal.adb

package:com.google.android.things.internal.net

package:com.android.location.fused

package:com.android.deskclock

package:com.android.bluetoothmidiservice

package:com.google.android.apps.inputmethod.home

package:com.google.android.things.customcheckin

package:com.android.bluetooth

package:com.android.providers.contacts

package:io.homeassistant.companion.android

package:io.homeassistant.companion.android.minimal
[Google Home] ducksoup18:
Thanks ill look closer later today. If you can send me the version of your webview using the command here that would be great as well. I need to update that so the ha app will work i think. https://stackoverflow.com/a/11943078
[Google Home] edugaga:
com.android.webview 87.0.4280.101

for HA is 2022.10.2 https://github.com/home-assistant/android/releases/tag/2022.10.2
[Google Home] ducksoup18:
Thanks for getting this for me. Wow, my webview is way older: 66.0.3359.158

Did you remember if you updated your device through the system updates? My security patch level says 5 Feb 2019. Trying to figure out how i can update webview. I saw you mentioned doing it through pm but the last time i tried, i couldnt install a new webview due to the signatures not matching or something.
[Google Home] edugaga:
I don't update the device because when start the update stay permanently loading/charging, and uninstall the apps that run the update. It does not update the webview or any internal app. They are all the ones that come by default.
[Google Home] ducksoup18:
And you installed the unified firmware? I just dont understand how my webview is so much older. https://s3.us-east-1.wasabisys.com/...2.3+debug.1.1.0.5307861_development_build.zip
[Google Home] ducksoup18:
@edugaga i feel like you somehow compiled your own version of com.android.webview or renamed the com.google.android.webview since i cant even find that version (87.0.4280.101). It only exists for the com.google.android.webview package name. I disabled the com.android.webview version, but since the system is still only looking for that package name (without pre-compiling my own stuff) it doesnt seem to find the com.google.android.webview version i've installed.
[Google Home] edugaga:
I have not compiled any version or made any modifications. How can I buy and see what version of firmware I installed?
[Google Home] edugaga:
Ignore the date the screen is not connected to the internet right now
[Google Home] edugaga:
I have extracted the APK, try to install this
[Google Home] ducksoup18:
Do you know which firmware you flashed to get those updated package? my OEM Version is 2089 using the jasper firmware. build OIM6.190107.017. Yours looks much newer.
[Google Home] edugaga:
@ducksoup18

I don't know, I don't remember well. I have taken everything from the original post. I have not updated anything once flashed. I think 'Unified 8" and 10" Debug/Development firmware' -> 'Android 8.1 Debug Firmware'
[Google Home] ducksoup18:
Thanks again for the reply. Super weird considering that link shows the firmware in the url that i have. I got to the point where i have a default launcher launching appropriately but if im unable to update my webview i wont be able to use homeassistant. @deadman96385 do you have any ideas or suggestions/tips on how to get this updated to a more recent webview? I wish i knew how @edugaga got his device to that version because im completely stuck now.
[Google Home] ducksoup18:
Huzzah! I ran a system update and it does in fact look like @edugaga rand a system update as i am seeing the same settings as you now and HA is launching. This is great! Thanks again for all the feedback @edugaga.
[Google Home] larastafarian:
Hi could you confirm the process to run the system update , I have the same issue with the old webview
[Google Home] johnnnnnnnny:
I understand your post is rather old and you might not be reading this thread anymore... However, since I've had pretty much the same issues I wanted to share some insight on how I was able to revert to stock image. I don't quite remember exactly what I was doing, but it might just be enough to get you started again...

So basically I got myself into EDL mode, the smart display would show as qualcomm device in the device manager. Tried using QFIL but couldn't get into Partition manager, so I downloaded QPST instead. QPST,too, would show my smart display on the proper port. In the active phones tab I simply selected my smart display, right clicked and did "port shutdown". Afterwards I was able to get into fastboot again and apply the amber factory firmware (w/o unlocking avb).
[Google Home] johnnnnnnnny:
One thing im struggling with is that I can't get a navigation bar working, i.e. when I open an app I have no way to close it unless I use adb. Tried several navigation bar apps, but they all seem to require some accessibility settings I can't set. Any ideas?
[Google Home] jonathanrob:
You'll have to set the permissions through adb. It's a bit of a pain but isn't too bad
[Google Home] ducksoup18:
Connect to WIFI if you havent already, go into settings and somewhere in there is a Setting to just do a System Update. It'll run through it and restart. Once thats done you've got an updated webview that works.
[Google Home] larastafarian:
Hi yes I'm connected to WiFi , I don’t have any setting options that allow update however - if I swipe up on my screen in launcher there is a settings button but within that is only info about WiFi / About Device / Open Source licence / Feed back. I wonder is a particular launcher you are using ? Or is the update via android things rather than launcher?
[Google Home] ducksoup18:
Hmmm. I thought it was in the About section. No special launcher, just through normal settings.

Try this:

adb shell monkey -p com.android.iotlauncher -c android.intent.category.HOME 1
[Google Home] larastafarian:
Check for update say’s the unit is up to date… Photos attached of what those screens say….is your build version same as mine ?

View attachment 6081584
[Google Home] ducksoup18:
Ah i see. Your channel is incorrect. Click the gear on the right side of the channels list and select Stable and then give it another try.
[Google Home] larastafarian:
Hi thanks your a legend! have it updated now & home assistant is working….
[Google Home] larastafarian:
Hi would you have step by step to get the navigation to work?
[Google Home] mkden:
how were you able to flash the firmware?

fastboot doesn't load for me after disabling the port
[Google Home] johnnnnnnnny:
worked flawlessly for me, are you sure you're out of EDL? Try to double check in your device manager and if necessary, rerun the steps and make sure to restart the device afterwards
[Google Home] mkden:
After disconnecting the port, do you need to turn it off?

after disconnecting the port, it connects again automatically in a matter of seconds.
[Google Home] Jocaru:
@ducksoup18 how did you set up HA as your launcher?
[Google Home] ducksoup18:
Nah i just installed Kiss launcher. It has the ability to show recent apps and i just select HA on startup. Not perfect, but it works.