yashsingh1/xdaforums huggingface dataset:
[Google Home] superduperXDA:
I noticed that the device runs AOSP 8.1, however, that is a very dated version. Is there a way to only update the operating system to a later version of Android, without disrupting the other components such as TEAMS or ZOOM that is built into the device? If not, when our organization full cracks down on compliance of outdated Android, I will not be able to use the device. Any help is appreciated.
[Google Home] Sjeck:
What a fantastic job from you and @deadman96385 . I was just about to toss this "piece of c***" in the bin. Just had a hard time doing it as it's so well built.

I have some across a few issues:

1. The MicroG app and Playstore App crashes often during install, but once I have logged into the playstore it disappears. Weird, but it works in the end.

2. I cannot for the life of me get LOCATION settings to work and as such can't install apps that require this information. Anyone else had a problem with this and has a solution?

Once again. Killer job @Chewie610 and @deadman96385 !!
[Google Home] Dismal.:
Has anyone had any success with treble?
[Google Home] Chewie610:
I don't know how to update the OS, from what I know it requires a lot of developing knowledge that I don't have :( Sorry!
[Google Home] Chewie610:
Glad it worked!

In regards to the location settings, I haven't ran into that issue as I haven't used many apps that require location. Is it that the Play Store won't let you install it? Have you tried using an APK of the same app? I'll have to find my device and try it but keep me updated on if you get it to work.
[Google Home] Chewie610:
I haven't checked if the device is treble compatible, haven't messed around in this side of ROMs before. Do you have experience with this?

I also tried altering the build.prop in the past but I believe I wasn't able to alter it properly... I saw you also mentioned "qemu.hw.mainkeys=0" in the other forum. Do you know how to the build.prop correctly to allow soft keys?
[Google Home] Dismal.:
Just add that line to the bottom of the build.prop. I only think the newer smart clock 2 supports treble
[Google Home] mikkofin:
Tried everything (installing magisk without flashing device, with flashing and even flashing with the provided boot.img added to the package) and no luck, magisk complains that it cannot find boot.img when trying to install for example NanoDroid patcher
[Google Home] RZomerman:
hi everyone,

I wanted to convert my device into a home assistant or something as well.. but for whatever I try.. I cant get QFIL to detect the ports..

I'm running Windows 11 (test mode enabled)

Using a USB3->USB2 (my monitor USB hub)

QDLoader HS-USB Driver_64bit_Setup in WWAN mode

installed QPST_2.7.474 but also tested the CD-18781Y.200628.084 stored version

and the device is CD-18781Y.211116.114

pressing that does nothing either.. ..

booting with vol + & - does nothing

the device is detected in Windows as : Lenovo CD-18781Y

help ?
[Google Home] RZomerman:
ha!

So you need to press volume up and down. Plug the power in. Release the buttons in a few seconds (don’t let it completely boot) and put the usb in

My error was that I was waiting for too long for something to show on screen but that’s not the case

And when loading the xml it was asking for a patch. Only patch 0 worked for me

All with usb3.0
[Google Home] CactuJ:
Hello All, and pardon me, as I am a bit new to all off this.

I was able to flash the ROM on these devices using EDL mode. Works great, now it boots up and I have an Android system.

I am having a bit of an issue with some basic functionality though.

I have tried both VirtualSoftKeys and the S9 Navigation bar linked up thread, but no matter what I do the home button does not work. The back button does, but not the home button. Googling this of course gives some terrible results.

I have Nova Launcher, but it is only working on vertical mode.

Can someone point me in the right direction for what I need to make this function semi-close to normal Android ? Working NavBar I think is key, I don't need anything fancy. I will probably remove Nova launcher and just go with the default. VSK also obscures the bottom of the keyboard... which.. is annoying.

Any other tips and tricks for someone that primarily users iPhones, and wants to use this Lenovo for a HomeAssistant dashboard?

Thanks
[Google Home] CactuJ:
Edit, and TLDR: I am a moron. I did not fully follow the provisioning commands. Doing so and everything works as expected.
[Google Home] Chewie610:
Glad you could get it working! If you added the webview patches, you should be able to use the Android HomeAssistant app. If you don't have the updated webview installed, you can just use Google Chrome or another web browser app to access HomeAssitant.

Regarding Nova Launcher, it might be a setting within Nova Launcher to allow the tablet to rotate. I'm not 100% sure if you're able to rotate in the home menu but I'd give that a shot.
[Google Home] Jagsta211:
is there any way to backup the entire flash and restore to another one after everything is done? i have 11 of these to do and looking to make this easier or atleast quicker.

also it seems that my webview is still outdated. i have installed chromium webview or and bowser. in developer options > webView implementaiton nothing is listed besideds the original 61.0.3163.98 .. what am i doing wrong?
[Google Home] ekincaid:
I'm a bit lost. I made it through step 1 above where I install the magisk.apk. I'm unsure where I enable OEM unlocking. I can't seem to find it in Magisk on the device. When I try the fastboot in the command prompt, it tells me "fastboot' is not recognized as an internal or external command. I assuming I need to install something I'm missing on the laptop. However, there is much I don't understand. Any thoughts?
[Google Home] Chewie610:
I believe you could try to create a recovery image in TWRP to flash, but make sure to optimize your system as there is little storage space on the device to make a recovery image.

Regarding Webview, did you install the Magisk package in the guide to update Webview?
[Google Home] Chewie610:
It looks like you're using the 2nd method listed in the guide... I wouldn't recommend using that method as it's slightly more difficult and, though it won't brick your device, you may feel like you're bricking your device. I would recommend the initial method here:

However, if you want to proceed with the 2nd method and use the fastboot commands, I recommend you get familiar with adb before doing so. You may need to add adb commands to your system as well.
[Google Home] heman22union:
I'm thinking about making a video for on how to flash this using various Operating Systems to do the flashing. Is there a way to flash it back to stock so I can do various takes?
[Google Home] Chewie610:
You can flash it back to stock using the firmware files I linked in step 3 provided by @deadman96385. The only difference is I change the recovery image so that Magisk is flashed on with it to allow rooting afterwards.
[Google Home] ekincaid:
I get it now... I had been following all the spoilers and it wasn't clear to me that I didn't need to follow the last one since it was in the boot.img.

I think I'm good now. Thanks
[Google Home] bgroins:
A tip for getting rid of Kiosk mode at boot:

Open Termux and type:

su

pm disable com.kingston.kioskmodeapp

After reboot it will open straight to your defined launcher app.
[Google Home] D200P13:
2024-01-26 20:13:22.895 20:13:22: ERROR: function: sahara_rx_data:237 Unable to read packet header. Only read 0 bytes.

2024-01-26 20:13:22.896 20:13:22: ERROR: function: sahara_main:924 Sahara protocol error

2024-01-26 20:13:22.897 20:13:22: ERROR: function: main:303 Uploading Image using Sahara protocol failed

2024-01-26 20:13:22.898 Download Fail:Sahara Fail:QSaharaServer Fail:process fail

i cant seem to flash it. just got it out of the box and tried it. am i doing something wrong? i have a macro and a smart switch so as soon as it detects the device, the button is clicked like 002 in time difference from the log above

where do i put Firehose/Rawprogram ?
[Google Home] Jagsta211:
got everything working finally! decided to go ahead and just plow through all 11 in one go! I'm running fully kiosk browser with my ha dashboard. I seem to have a problem waking the screen up with my fp2 automation. i toggle it on in fully kiosk entity and i can touch on the screen and it works because i can open my garage door, but the backlight won't come on most of the time requiring a reboot of the device. sometimes it will come on tough. i have attempted to change to swipe lock and have fk open with swipe and that didn't seem to do anything.
[Google Home] deadman96385:
I got a few of the thinksmart view's for super cheap so I took another crack at tinkering with them. Based on the knowledge that magisk and twrp work even when bootloader locked. I attempted to do a GSI and it does work. Which means it is not validating the partitions so you can treat it as bootloader unlocked even if locked.

Currently I have tested the following:

PHH AOSP 8.1 V32 (Arm A-Only Go su) - Boots, camera and wifi do not work

PHH AOSP 9.0 V123 (Arm A-only Gapps su) - Boots, camera and wifi do not work

PHH AOSP 10.0 v222 (Arm A-only Go) - Boots and most everything works except for wifi

PHH AOSP 11.0 v313 (Arm A-only Vanilla) - Boots and most everything works except for wifi

PHH AOSP 11.0 v313 (Arm A-only Go) - System is too large to flash

AndyYan's Lineage 18.1 (Arm A-Only Go su) - System is too large to flash

AndyYan's Lineage 18.1 (Arm A-Only Vanilla su) - Boots but instantly factory resets

Edit:

Wifi works if you push the following files from stock:

system/etc/firmware/ice40.bin

system/etc/firmware/wlan/qca_cld/WCNSS_qcom_cfg.ini

system/etc/firmware/wlan/qca_cld/wlan_mac.bin

Place them in vendor/firmware to keep them in-between gsi flashes or in system and having to redo it.

Here is a vendor img based on the latest Team's firmware, with the above wifi firmware/configs added as well as the following props added to vendor/build.prop first 2 are from stock, noril should disable some telephony stuff on some gsi's.

ro.sf.lcd_density=260

qemu.hw.mainkeys=1

ro.radio.noril=1

https://s3.us-east-1.wasabisys.com/filestash-buk/lenovo-thinksmart-view/kingston_wifi_vendor.img
[Google Home] bassderek:
Dos USB OTG work on the GSI images?
[Google Home] deadman96385:
It does not look like it
[Google Home] D200P13:
on windows 10 i was never able to flash it and i didnt even get a status bar. i got out my old laptop with win7 and worked first try!

all said and done, any way to get google assistant on it? looks like without the google service i cant seem to run things like that, home, or youtube (and youtube tv). as it is i can work with it for my needs but unsure google assistant would be super helpful.
[Google Home] deadman96385:
You can install GSI's that have GAPPS installed already, Play store and everything is working properly it seems. I have added a premade vendor img you can flash to fix wifi and display scaling on GSI's in my previous post.
[Google Home] morgothtdo:
Hi. So I am new at this but have been struggling the last day trying to get my 8" ThinkSmart flashed. I keep getting a failed to open com port error:

2024-01-30 09:47:24.293 Start Download
2024-01-30 09:47:24.302 Program Path:C:\CD-18781Y.200628.084\image\prog_emmc_firehose_8953_ddr.mbn
2024-01-30 09:47:24.306 ***** Working Folder:C:\Users\Doom\AppData\Roaming\Qualcomm\QFIL\COMPORT_10
2024-01-30 09:47:24.338 Binary build date: Nov 21 2017 @ 02:53:37
2024-01-30 09:47:24.339 QSAHARASERVER CALLED LIKE THIS: 'C:\Program Files (x86)\Qualcomm\QPST\bin\QSaharaServer.ex'Current working dir: C:\Users\Doom\AppData\Roaming\Qualcomm\QFIL\COMPORT_10
2024-01-30 09:47:24.340 Sahara mappings:
2024-01-30 09:47:24.341 2: amss.mbn
2024-01-30 09:47:24.342 6: apps.mbn
2024-01-30 09:47:24.343 8: dsp1.mbn
2024-01-30 09:47:24.343 10: dbl.mbn
2024-01-30 09:47:24.344 11: osbl.mbn
2024-01-30 09:47:24.345 12: dsp2.mbn
2024-01-30 09:47:24.345 16: efs1.mbn
2024-01-30 09:47:24.346 17: efs2.mbn
2024-01-30 09:47:24.347 20: efs3.mbn
2024-01-30 09:47:24.347 21: sbl1.mbn
2024-01-30 09:47:24.348 22: sbl2.mbn
2024-01-30 09:47:24.349 23: rpm.mbn
2024-01-30 09:47:24.349 25: tz.mbn
2024-01-30 09:47:24.350 28: dsp3.mbn
2024-01-30 09:47:24.350 29: acdb.mbn
2024-01-30 09:47:24.351 30: wdt.mbn
2024-01-30 09:47:24.352 31: mba.mbn
2024-01-30 09:47:24.352 13: C:\CD-18781Y.200628.084\image\prog_emmc_firehose_8953_ddr.mbn
2024-01-30 09:47:24.354 09:47:24: ERROR: function: port_connect:100 Failed to open com port handle
2024-01-30 09:47:24.369 09:47:24: ERROR: function: main:297 Could not connect to \\.\COM10
2024-01-30 09:47:24.369 Download Fail:Sahara Fail:QSaharaServer Fail:Process fail
2024-01-30 09:47:24.370 Finish Download

I've tried:

Using different USB ports

Using different USB-C cables

Using 2 different computers

Click spamming download as soon as the device is connected

Reinstalling the qualcomm drivers

With testsigning on and off

Running QFIL as admin

If anyone has any other ideas I would love to try them out.

There is a warning flag in device manager, not sure if that is a cause for concern.
[Google Home] bassderek:
Am I totally daft - after flashing system and vendor images and re-locking it will only boot into fastboot by default (recovery if i use vol+, but never boots normally).
[Google Home] bassderek:
If you could share a brief overview of the steps you took to flash the GSI that would be helpful.
[Google Home] badi95:
I'm struggling to get the device to showup in fastboot. I reboot into the bootloader using adb reboot bootloader or power and Vol-, and in Device Manager -> Other devices an device called Android shows up. I'm not able to assign any driver to the device. I think I installed the linked qualcomm drivers. Any help would be appreciated. I'm runnning Windows 11.

I'm running 201006.099 that came with my device. I've successfully accessed developer options and installed a home screen and navigation bar. I'd like to be able to use it as a home assistant dashboard.
[Google Home] shateeel:
Thanks, the steps worked. However the screen abruptly goes off and I can never get it back without rebooting the device. Any workaround for this?
[Google Home] Jagsta211:
I am struggling with this too! i have remapped a button to sleep/wake it works some of the time. using fully kiosk to turn screen off and on doesn't turn the screen back on ever again. Have tried a few different apps. I know that lenovo's support page for the device says you tap the screen to wake it. i wonder if some of the 'bloatware' removal got rid of that feature.

I know that the touch screen is on because i can turn on and off things in home assistant when i hit my remapped power button, but the backlight is what is not on and requires a reboot. i'm still trying to figure this out please let me know if you find a solution.
[Google Home] badi95:
I'm having this same issue as well. I'm running Windows 11 and it won't let me turn off device signing. What os are you running?
[Google Home] morgothtdo:
One machine has Windows 10 and the other has Windows 11
[Google Home] sadsephiroth:
Same here, flashed system and vendor, reboot showed a blip of twrp, but will not boot. Have also wiped after per GSI instructions found online.
[Google Home] bassderek:
I have found that it works if you start with flashing the debug firmware in the first post.
[Google Home] bassderek:
We have had some conversations in discord so tomorrow I will write up the process to get the PHH AOSP 11 GSI working on the device. There is ongoing work to improve other things such as remapping power button and getting WiFi to work without a fix.
[Google Home] sadsephiroth:
Got it. I was on the last Teams version with ADB. Flashing now.
[Google Home] bigjonnee:
Hi you all I have everything up and running one nagging issue left. I cannot turn off auto screen brightness without it turning back on in a few seconds. I uninstalled of all the packages with "kiosk" "mdm" "provisioning" etc. AND I uninstalled all the packages listed in the other thread "CD-18781Y ..Normal Android" Does anyone know if these or any of other packages are responsible for always turning "auto brightness" back on?

***EDIT:

I solved this. The offending package is:

pm uninstall --user 0 com.lenovo.oobe

OOBE = "out of box experience." So it makes sense it contains the gear settings menu you get when you startup. This also allowed me to change the screen to "never" turn off and I think I can do screen saver too.
[Google Home] sadsephiroth:
Got the GSI flashed by starting with the debug rom. Not very Android savvy, I tried flashing the vendor img, the ice40.bin doesn't appear to go, but the other 2 files are there. I am failing at copying this manually, have tried with adb, root file explorer, and terminal on device.
[Google Home] bassderek:
adb root

adb remount

adb shell

cd /system/etc

mkdir -p firmware/wlan/qca_cld

exit (exit shell)

adb push ice40.bin system/etc/firmware

adb push WCNSS_qcom_cfg.ini system/etc/firmware/wlan/qca_cld/WCNSS_qcom_cfg.ini

adb push wlan_mac.bin system/etc/firmware/wlan/qca_cld/wlan_mac.bin

adb reboot
[Google Home] bassderek:
Essentially the process is this, updated to eliminate any unlocking/locking:

use QFIL to flash 191011.0035 Kingston Userdebug (Qcom Diag Mode active) Firmware from the first post.

power cycle device while holding vol+/- to go straight back to EDL

use tools - partition manager - right click on system - load the AOSP rom ( I used system-roar-arm-aonly-vanilla.img (PHH AOSP11 v313))

Exit partition manager and it will reboot on it's own.

You should successfully boot into AOSP after a bit of waiting. If you are prompted for a password you may need to reboot into fastboot and run "fastboot -w" to wipe userdata/cache.

Then push the files for the wifi fix as denoted in post above:
[Google Home] bassderek:
deadman is working on an updated kernel with some fixes such as wifi and remapping the camera slider to power for easier operation.
[Google Home] sadsephiroth:
I have the files in the correct locations, and have confirmed the correct image is flashed. Wifi files located in correct folders as far as I can tell, and verified the build.prop also flashed fine from the vendor.img. Still no wifi after reboot.
[Google Home] bassderek:
Did you try using deadmans kingston_wifi_vendor.img? because that messes this process up. I just did this all over again and these are the exact commands after I flashed debug fw and aosp:

adb root

adb remount

adb shell

mkdir -p /system/etc/firmware/wlan/qca_cld

exit

adb push ice40.bin system/etc/firmware/

adb push WCNSS_qcom_cfg.ini system/etc/firmware/wlan/qca_cld/

adb push wlan_mac.bin system/etc/firmware/wlan/qca_cld/

adb reboot
[Google Home] desidude2000:
Where and how does one get the files ice40.bin, WCNSS_qcom_cfg.ini and wlan_mac.bin? How and where do you extract them from? That is where I am stuck.
[Google Home] h3y0:
That was earlier in the thread: https://xdaforums.com/t/guide-root-...inksmart-view-cd-18781y.4584033/post-89303829

You could copy them from the debug rom before flashing with GSI, extract them from kingston_wifi_vendor.img (but don't flash that to /vendor, doesn't seem to be working as intended), or here I got em for ya:
[Google Home] desidude2000:
thank you so much for putting it in a tarball
[Google Home] sadsephiroth:
Figured it out, was using fastboot to flash system on Arch, there's a bug in platform tools on Arch. Used a Windows machine and QFIL, all is working now. Getting gapps and assistant setup now.
[Google Home] desidude2000:
Let us know if you can get assistant to work, especially invoking it with voice command. I couldn’t get it to work.
[Google Home] desidude2000:
Looks the device sports a 64bit Qualcomm Snapdragon 624 SoC but comes with a 32bit kernel. If we could build a 64bit kernel, we might be able to use even newer GSIs beyond Android 11.
[Google Home] Jagsta211:
thanks got one of mine flashed! i'm wondering if i did something wrong though. if i pull power the next 1 to 2 boots get stuck at lenovo logo indefinitely a 3rd attempt boots into android just fine.
[Google Home] _raydroid:
I'm thinking about picking up one of these due to the plugged-in power nature of the device. Just wanted to confirm that the audio and camera are working when using a video chat app like Skype after flashing a newer version of Android like 8.1 or 11.

Also the Webview instructions in the second post are weird. Why is a Magisk module needed? Couldn't you sideload the latest version of Android System Webview from APKMirror?
[Google Home] iheartwmds:
Hello all,

Having issues @ the Termux step, I have a Playstore apk (39.5.19-21 [0] android 5+) installed but when I attempt to use termux to systemize it i get the following...

"Systemizing google play store

/system/xbin/systemize[579]: awk: not found

package doesn't exist!"

Play store shows on home screen but...

"google play store has stopped"

occurs as soon as opening and also upon boot. I have microG installed and have an account signed in (although not shown in microG setting) and google device registration on.

not sure where I went wrong and any help would be greatly appreciated.
[Google Home] Scags104:
Having wifi issues after following directions above a few times. Wifi toggle wont stay on or scan for networks.

Any help is appreciated.
[Google Home] JarrenC97:
I tried doing everything listed under "You can also technically install Magisk without reflashing your device." but it just leaves me with a Lenovo logo and won't boot, even after re locking the bootloader as instructed. Any idea on why or how that could happen?
[Google Home] Chewie610:
I would not recommend installing Magisk without reflashing your device, but it looks like you've already done it. It looks like I made a typo in the final command. Try running "fastboot oem lock" or "fastboot flashing lock" to lock the bootloader. After you lock the bootloader, the device should be able to power back on.
[Google Home] Chewie610:
I've tried sideloading a new Android System Webview in the past but I don't believe it works. You can try and let me know if it works.
[Google Home] Chewie610:
Whoa... what the heck have I missed... @deadman96385 is back? Are there any performance drops with these new GSIs?

Slightly itching to update mine now... it'll be cool if the camera slider could be used as a power slider...
[Google Home] bassderek:
You're in luck... we are testing it in a discord but he has built an image based on PHH AOSP11 that now has camera slider power, gpu overclock, and google apps!
[Google Home] Chewie610:
Can't wait... if it's a server can I get the link? Otherwise I'll just wait and see when y'all release it...
[Google Home] pepe_lodz1:
Hi all

I am begginer. Today i recived my Lenovo Thinksmart View. Is anybody who can tell me step by step how i can change my FW to usage android ? I flashed this software

https://community.home-assistant.io/t/is-this-the-perfect-standalone-tablet-for-ha/658422/445

but on this i have problem that can not connect to my WIFI in home. When use original FW Lenovo i can connect with no problem.....
[Google Home] desidude2000:
How do you tear open the unit? Any guidance? I believe I have a brick on my hands. Can’t even get to the Lenovo logo any more and I don’t seem to be drawing any current when I plug in the unit.
[Google Home] _raydroid:
I haven't picked up the device yet. I want to make sure that video calling is still working on this device after flashing a newer version of Android. Can anyone verify that video calls are working when using Skype, Whatsapp, etc?
[Google Home] cross-IT:
GREAT writeup New life for the thinksmart

Anychance anyone knows how to boost audio after finishing all things listed here (i did magisk and SU )
[Google Home] protechtedd:
Sounds great, I'm looking forward to this. Any progress lately? I have been waiting to root my ThinkSmart and this seems like the way.
[Google Home] kloodhu:
Probably i'm very dumb, but where can i find the mentioned rom file? I've searched everywhere, but no luck.

Thank You!

Edit: i found it.
[Google Home] yurishouse:
V4A RE might be worth a try?