CD-18781Y (Lenovo ThinkSmart View) Bootloader, Firmware, Zoom/Teams Conversion, Normal Android

[Smc025]

Recently I got two of these devices. Assumed they where just cheap "normal" tablets.
I've learned a lot since then......
Flashed both devices to 201006.099, thanks to the excellent guide in the first post
Deinstalled a whole lot of stuff: (Just stuff I didn´t need for my purpose)
adb shell
pm uninstall -k --user 0 com.microsoft.skype.teams.ipphone
pm uninstall -k --user 0 com.kingston.kioskmodeapp
pm uninstall -k --user 0 jp.co.fsi.fskaren.lenovo
pm uninstall -k --user 0 com.microsoft.windowsintune.companyportal
pm uninstall -k --user 0 com.microsoft.teams.ipphone.admin.agent
pm uninstall -k --user 0 com.kingston.devicesettings
pm uninstall -k --user 0 com.android.music
pm uninstall -k --user 0 com.android.deskclock
pm uninstall -k --user 0 com.android.contacts
pm uninstall -k --user 0 com.android.providers.calendar
pm uninstall -k --user 0 com.android.calendar
pm uninstall -k --user 0 org.codeaurora.snapcam
pm uninstall -k --user 0 com.android.quicksearchbox

Installed F-Droid:
adb install F-Droid.apk

From F-Droid install keymapper and aurora store
Configures the volume keys to home and back.
From Aurora store install the stuff you need from the playstore. As simple as that!

Thanks, this was very helpful. Cheers.

 

[RZomerman]

I can't seem to get the device in debug mode - no matter how often I press the About/Firmware Version
running : CD-18781Y.211116.114
PartnerApp: 20210507-1021-1.37
AdminApp: 1.0.0.202110130735.product
Company Portal: 5.0.5304.0
Teams Version: 1449/1.0.95.2021721103

any other way to switch it to debug / adb mode ?

 

[Larryngolog]

Hi! I'm stuck on flashing - after I do the step 14 I get the following errors:
2023-01-10 09:59:55.449 13: C:\CD-18781Y.200628.084\image\prog_emmc_firehose_8953_ddr.mbn
2023-01-10 09:59:55.449
2023-01-10 09:59:55.449 09:59:55: ERROR: function: port_connect:100 Failed to open com port handle
2023-01-10 09:59:55.449
2023-01-10 09:59:55.465 09:59:55: ERROR: function: port_connect:100 Failed to open com port handle
2023-01-10 09:59:55.465
2023-01-10 09:59:55.465 09:59:55: ERROR: function: port_connect:100 Failed to open com port handle
2023-01-10 09:59:55.465
2023-01-10 09:59:55.465 09:59:55: ERROR: function: port_connect:100 Failed to open com port handle
2023-01-10 09:59:55.465
2023-01-10 09:59:55.465 09:59:55: ERROR: function: port_connect:100 Failed to open com port handle
2023-01-10 09:59:55.465
2023-01-10 09:59:55.465 09:59:55: ERROR: function: port_connect:100 Failed to open com port handle
2023-01-10 09:59:55.465
2023-01-10 09:59:55.465 09:59:55: ERROR: function: port_connect:100 Failed to open com port handle
2023-01-10 09:59:55.465
2023-01-10 09:59:55.479 09:59:55: ERROR: function: port_connect:100 Failed to open com port handle
2023-01-10 09:59:55.479
2023-01-10 09:59:55.479 09:59:55: ERROR: function: port_connect:100 Failed to open com port handle
2023-01-10 09:59:55.479
2023-01-10 09:59:55.479 09:59:55: ERROR: function: port_connect:100 Failed to open com port handle
2023-01-10 09:59:55.479
2023-01-10 09:59:55.479 09:59:55: ERROR: function: main:297 Could not connect to \\.\COM3
2023-01-10 09:59:55.479 Download Fail:Sahara Fail:QSaharaServer Failrocess fail
2023-01-10 09:59:55.479 Finish Download


I tried on 2 machines and I get the same error. Any idea what I'm missing?

 

[noname_93]

I can't seem to get the device in debug mode - no matter how often I press the About/Firmware Version
running : CD-18781Y.211116.114
PartnerApp: 20210507-1021-1.37
AdminApp: 1.0.0.202110130735.product
Company Portal: 5.0.5304.0
Teams Version: 1449/1.0.95.2021721103

any other way to switch it to debug / adb mode ?

I am having exactly the same issue. I want to set a boot password so the device will be encrypted but now I do not have adb access. Any ideas how to get enable debuggin on 211116.114 ?

 

[noname_93]

Ok, I figured out that my firmware version was updated automatically. I followed the guide and reinstalled an older firmware which enabled the adb.

It is so weird that we cannot set device pin by default. In my organization there is a intune policy which says all byod devices should have a pin to connect. This prevents my device from connecting, unless I set a pin through ADB...

I guess is the concept is to go to intune and make exceptions for specific devices, right?

 

[kancept]

Has anyone tried flashing the Lenovo smart Display 8 (Amber) roms to these?

 

[gforums]

Has anyone tried flashing the Lenovo smart Display 8 (Amber) roms to these?

I tried but wasn't successful with the tool. Have a dead amber device now, as I tried to install ROM from another thread which ended in a "device updating" boot loop.

Any success storys would be nice to see

 

[kancept]

Hi! I'm stuck on flashing - after I do the step 14 I get the following errors:
2023-01-10 09:59:55.449 13: C:\CD-18781Y.200628.084\image\prog_emmc_firehose_8953_ddr.mbn
2023-01-10 09:59:55.449
2023-01-10 09:59:55.449 09:59:55: ERROR: function: port_connect:100 Failed to open com port handle
2023-01-10 09:59:55.449
2023-01-10 09:59:55.465 09:59:55: ERROR: function: port_connect:100 Failed to open com port handle
2023-01-10 09:59:55.465
2023-01-10 09:59:55.465 09:59:55: ERROR: function: port_connect:100 Failed to open com port handle
2023-01-10 09:59:55.465
2023-01-10 09:59:55.465 09:59:55: ERROR: function: port_connect:100 Failed to open com port handle
2023-01-10 09:59:55.465
2023-01-10 09:59:55.465 09:59:55: ERROR: function: port_connect:100 Failed to open com port handle
2023-01-10 09:59:55.465
2023-01-10 09:59:55.465 09:59:55: ERROR: function: port_connect:100 Failed to open com port handle
2023-01-10 09:59:55.465
2023-01-10 09:59:55.465 09:59:55: ERROR: function: port_connect:100 Failed to open com port handle
2023-01-10 09:59:55.465
2023-01-10 09:59:55.479 09:59:55: ERROR: function: port_connect:100 Failed to open com port handle
2023-01-10 09:59:55.479
2023-01-10 09:59:55.479 09:59:55: ERROR: function: port_connect:100 Failed to open com port handle
2023-01-10 09:59:55.479
2023-01-10 09:59:55.479 09:59:55: ERROR: function: port_connect:100 Failed to open com port handle
2023-01-10 09:59:55.479
2023-01-10 09:59:55.479 09:59:55: ERROR: function: main:297 Could not connect to \\.\COM3
2023-01-10 09:59:55.479 Download Fail:Sahara Fail:QSaharaServer Failrocess fail
2023-01-10 09:59:55.479 Finish Download


I tried on 2 machines and I get the same error. Any idea what I'm missing?

I had the exact same issue in Windows 11. I had to disable driver signing and then it got a lot further. Still hasn't been successful to flash an older version yet (mine is on CD-18781Y.211116.114) , but that got me past this error.

 

[garnir4ik]

There are no problems with root rights, you can get it through magisk. For example, I use the firmware 210228.109. We flash the device, configure it to access the desktop, all the information is already described in the topic. We connect to the PC, copy magisk and the boot.img file from the firmware files 210228.109. Install magisk, it will offer to patch boot.img, copy the new boot.img to the computer, into the firmware folder (replace). We flash, re-configure the device to access the desktop, copy magisk from the computer again and install it, open the application to complete obtaining root rights (a reboot will occur).
The question is the following, can someone have collected twrp? We have snapdragon-624, it is similar to snapdragon-625, devices on such a processor have twrp.

I would like to activate OTG. The USB OTG Checker application reports that "USB manager" and "USB Device list" are active, but "USB host" is not active. To activate, you need to create a file(android file.hardware.usb.host.xml) along the /system/etc/permissions, with content:

<permissions>
 <feature name="android.hardware.usb.host"/>
</permissions>

follow the path /system/etc/permissions and find the handheld_core_hardware.xml and add the same content. But there is a problem with creating a file, you need to grant the rights "777", when you issue them, the system freezes. It is also not possible to move the file through adb. As I understand it, this is protection and I think it can be circumvented through twrp. Sorry for my english

 

[Ranomez]

There are no problems with root rights, you can get it through magisk. For example, I use the firmware 210228.109. We flash the device, configure it to access the desktop, all the information is already described in the topic. We connect to the PC, copy magisk and the boot.img file from the firmware files 210228.109. Install magisk, it will offer to patch boot.img, copy the new boot.img to the computer, into the firmware folder (replace). We flash, re-configure the device to access the desktop, copy magisk from the computer again and install it, open the application to complete obtaining root rights (a reboot will occur).
The question is the following, can someone have collected twrp? We have snapdragon-624, it is similar to snapdragon-625, devices on such a processor have twrp.

I would like to activate OTG. The USB OTG Checker application reports that "USB manager" and "USB Device list" are active, but "USB host" is not active. To activate, you need to create a file(android file.hardware.usb.host.xml) along the /system/etc/permissions, with content:

<permissions>
 <feature name="android.hardware.usb.host"/>
</permissions>

follow the path /system/etc/permissions and find the handheld_core_hardware.xml and add the same content. But there is a problem with creating a file, you need to grant the rights "777", when you issue them, the system freezes. It is also not possible to move the file through adb. As I understand it, this is protection and I think it can be circumvented through twrp. Sorry for my english

So wait, are you using Magisk with a locked bootloader or did Magisk allow you to boot with an unlocked bootloader?

 

[garnir4ik]

So wait, are you using Magisk with a locked bootloader or did Magisk allow you to boot with an unlocked bootloader?

Yes, If you flash through "fastboot", separately "boot", it does not work. You need to flash through "QFIL", then the system loads and "magisk" works

 

[Ranomez]

Yes, If you flash through "fastboot", separately "boot", it does not work. You need to flash through "QFIL", then the system loads and "magisk" works

Yes to which one cause that was an "or" question?
So did you unlock bootloader or not?

 

[Ranomez]

Also for anyone who cares to use this for music or such install the Google AudioFX from apkmirror to tweak the sound, it can have really great sound if you use the flat preset but then raise the last 2 frequencies.

 

[garnir4ik]

Yes to which one cause that was an "or" question?
So did you unlock bootloader or not?

the bootloader is blocked

 

[LocoLobo79]

Unlock Semi-Normal Android Usage

• On the 201006.099 Teams & Others build you can turn on adb which lets you remove the teams/kiosk launcher and have a normal Android 8.1 interface.
• On the 200628.084 Teams & Others build it already has adb on by default so you can skip Steps 5-8
• If you have a Teams Edition new in box adb should work on that firmware.

1. Flash a Teams & Others build following the firmware flash guide below
2. When it boots up select Teams (Others seems to try and network boot/download files and fails)
3. Go through the setup wizard until you get to the Microsoft Teams (Language > Wifi > Bluetooth > Teams)
4. Select the Gear Icon in the top right of the teams page
5. Select the "About" settings option
6. Tap on "CD-18781Y.200628.084" under firmware version a bunch of times rapidly until a prompt comes up saying developer unlocked.
7. If your usb c cable is plugged in unplug and replug it in
8. You will now have ADB access
9. Download your desired Launcher and use the following command to install it:

   adb install APK_FILE_NAME.apk

10. You will then need to send this adb command to select a new default launcher:

    adb shell am start -a android.intent.action.MAIN -c android.intent.category.HOME

11. I would recommend getting a Button Remap app due to there not being a Nav bar currently. I have found Vol+ single click mapped to back and long press mapped to Home works well.
12. If you get stuck an app before you get a back button, send the command from step 10 to go back to the launcher.

Bootloader Unlocking Do not do it for now

If you unlock the bootloader your device will only boot EDL or Fastboot. Any other mode will drop the device into Qcom 900E. To fix the device boot to fastboot and relock the bootloader (fastboot oem lock or fastboot flashing lock)

1. Unplug the device
2. Hold Vol- and plug in the device (Smart Plugs can make this easier)
3. fastboot oem unlock-go

Convert Teams Edition to Zoom Edition or vice-versa

Follow the flashing guide below just grab either the Zoom or Teams firmware. ADB enable will only work on Teams Versions. I have not found a way to do it on the Zoom firmware.

Flashing the Lenovo firmware

(Windows) QFIL

1. Download and install the Qualcomm drivers from here​
2. Download the teams/zoom flash package from below​
3. Extract the firmware to a folder that you can easily access them from like your desktop​
4. Download and install QPST from here​
5. Open the QFIL application (Find it in your start menu)​
6. In the "Select Build Type" field select Flat Build​
7. In the "Select Programmer" field navigate to the folder you extracted the firmware and support files to and select the prog_emmc_firehose_8953_ddr.mbn file​
8. Select the "Load XML" button and navigate to the folder you extracted the firmware and support files to and select the rawprogram_unsparse.xml and then the patch0.xml when prompted.​
9. Remove the cover on the USB-C port on the bottom right of your device​
10. Plug the Usb C cable into your computer​
11. Unplug the power from the device​
12. Hold vol+ and Vol- and then plug the power into your device (Smart Plugs can make this easier)​
13. If the text at the top of the QFIL application mentions qdloader move on to next step. If it says "No Port Available" click the "Select Port..." option and pick your device. If your device isn't showing up there you most likely didn't install the drivers properly.​
14. Click the Download Button to begin flashing your device​
15. Once complete it should automatically reboot but sometimes it doesn't so you need to replug your device.​

(Linux, Mac, Advanced Windows)
Use Bkerler's Amazing EDL Toolkit Here


Downloads
Firehose/Rawprogram by themselves
here

210602.2103 Zoom Firmware (Latest no ADB)
here

210228.109 Teams Firmware (Latest no ADB)
here

201006.099 Teams & Others (Has the ability too turn on ADB)
here

200628.084 Teams & Others (ADB Turned on by default)
here

191011.0035 Kingston Userdebug (Qcom Diag Mode active, No ADB)
(Designed for developers, limited features DO NOT USE)
here

Credit: @WhyPartyPizza on reddit for the adb enable steps

Thank you so much for this guide. I wfh and my job provided us with Zoom software for phone. Found this device and converted it to zoom. Plus, I was able to add apps like Plex.

I had to get a force landscape app because some apps always want to do portrait. I also found a hidden settings app to access settings the gear won't show.

Now I just need to find an app to disable proximity sensor because some voip apps make the screen go black unless I move far back.

I hope someone figures out how to use OTG because most of the 8gb is used...

 

[blaz.law]

So my progress currently is that I have uninstalled Kiosk, Lenovo Bloat, Teams & the weird settings thing and installed a button remapper, Nova launcher and Chrome.

Now it works perfectly for playing videos via browser YouTube, havent yet tried getting YouTube itself running. And I have back button via volume plus + volume minus.

Works awesomely and I can't thank this firmware enough. Got the machine for 34eur brand newish.

Hi, how to connect device to pc? I cant connect pc with device via adb.. no devices/emulators. I flashed the version 200628.084. thanks for help! I will send tips for help

So my progress currently is that I have uninstalled Kiosk, Lenovo Bloat, Teams & the weird settings thing and installed a button remapper, Nova launcher and Chrome.

Now it works perfectly for playing videos via browser YouTube, havent yet tried getting YouTube itself running. And I have back button via volume plus + volume minus.

Works awesomely and I can't thank this firmware enough. Got the machine for 34eur brand newish.

 

[blaz.law]

Recently I got two of these devices. Assumed they where just cheap "normal" tablets.
I've learned a lot since then......
Flashed both devices to 201006.099, thanks to the excellent guide in the first post
Deinstalled a whole lot of stuff: (Just stuff I didn´t need for my purpose)
adb shell
pm uninstall -k --user 0 com.microsoft.skype.teams.ipphone
pm uninstall -k --user 0 com.kingston.kioskmodeapp
pm uninstall -k --user 0 jp.co.fsi.fskaren.lenovo
pm uninstall -k --user 0 com.microsoft.windowsintune.companyportal
pm uninstall -k --user 0 com.microsoft.teams.ipphone.admin.agent
pm uninstall -k --user 0 com.kingston.devicesettings
pm uninstall -k --user 0 com.android.music
pm uninstall -k --user 0 com.android.deskclock
pm uninstall -k --user 0 com.android.contacts
pm uninstall -k --user 0 com.android.providers.calendar
pm uninstall -k --user 0 com.android.calendar
pm uninstall -k --user 0 org.codeaurora.snapcam
pm uninstall -k --user 0 com.android.quicksearchbox

Installed F-Droid:
adb install F-Droid.apk

From F-Droid install keymapper and aurora store
Configures the volume keys to home and back.
From Aurora store install the stuff you need from the playstore. As simple as that!

Could you pls help and describe what you did after you flashed both devices to 201006.099,.. thanks for help!

 

[Drier5829]

Could you pls help and describe what you did after you flashed both devices to 201006.099,.. thanks for help!

I just got this working. Initially I was having trouble flashing anything since it would keep disconnecting from the computer as a Qualcomm device. But I realized that when I powered it on with Vol+ and Vol- pressed, it would appear as a Qualcomm device, disappear, and then appear again. Once it appeared again I was able to start the flashing process in QFIL. I also needed to disable driver signing in Windows in order to get it to this stage.

I actually flashed it to 200628.084 Teams & Others since ADB would already be enabled. Once QFIL flashed it, I went through the setup process for Microsoft (not Others). At this point I could see it in adb devices and was able to uninstall the packages in sb0037's post.

Also, I found an app called Fluid NG which is a bit more convenient than keymapping since it uses navigation gestures to emulate back, home, and multitasking buttons.

 

[blaz.law]

I tried but wasn't successful with the tool. Have a dead amber device now, as I tried to install ROM from another thread which ended in a "device updating" boot loop.

Any success storys would be nice to see

is any tried flashed amber (lenovo smart display) on this lenovo thinksmart view? I want to get google home on lenovo thinksmart view

 

[snkk999]

hello, this device fell into my hands as at the beginning of the thread, I can't manage to run a normal android, I installed all the drivers, the device is visible, the software is uploaded to the tablet, but I can't go through point 9, where can I download this program? , I do not know if I accidentally unlocked the bootloader, when holding down the vol - key and connecting the device to the network, it only starts up to its original state, i.e. to select the language