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

Search This thread

remrog

New member
Mar 15, 2023
1
0
After hours of trying and failing, I am really struggling with this 😅

The flashing is no problem, I have tried all the versions above - but non of them gives me ADB access.
I got it once when installing the Zoom version, but after a reboot i was never able to access ADB again.

Im now on 200628.084. Developer Mode is activated but PC (several tried) will not connect via ADB.
I never get a question/pop-up to "Allow USB Debugging" either.. (Exept the one time on the Zoom image)

Anybody have any tips on how i can proceed?

EDIT: I got ADB to work, i changed the USB cable to another one and suddenly it worked 🥴
 
Last edited:

southy44

Member
Mar 16, 2023
10
0
Hi,

a somewhat unrelated question:
I have a ThinkSmart View Teams.
However I can't use it because it fails the inTune compliance test. I just recreated the situation to check if I can find out what specific policy it wouldn't pass nbut I can't find it any more, however I believe I remember vaguely having seen once that it lacks (obviously):
- PIN (screen lock)
- encrypted file system
So as this is a corporate policy obviously I can't change it.
Is there a way to configure the device in a way so that it becomes compliant to the corporate policy?
Is there a way to get through to some android settings that enable PIN / FS encryption etc?

As I haven't used an Android device in literally 8 years or so, please excuse my dumbness :)
 

southy44

Member
Mar 16, 2023
10
0
Well, so I decided to try to go the "flash & use for something else" - route.
But that's not overly successfull.

Mine is on firmware CD-18781Y.210507.111
So it propably has no ADB.

"press vol+ & vol- on powerup" is totally unsuccessful - i tried 10 times, it just boots up as regular.
"vol + & power up" brings the diagnostic menu but nothing to gain there.

factore restore -> configuration -> gear icon -> tapping on the firmware version doesn't do anyrthing, no matter how fast or often I tap.
So: I need to flash.

Installed the qualcom drivers (tried both options: WWAN & eth network).
the device is found in windows and I can open it up as USB storage, so the driver seems to work fine.
But it's nowhere to be found in device manager and QFIL shows me no port.

So what did I do wrong?
If the driver allows me to use it as a USB device, it's obviously working, right?
Any hints here?

Thanks!
 

Xi07

Member
Mar 9, 2023
10
5
Well, so I decided to try to go the "flash & use for something else" - route.
But that's not overly successfull.

Mine is on firmware CD-18781Y.210507.111
So it propably has no ADB.

"press vol+ & vol- on powerup" is totally unsuccessful - i tried 10 times, it just boots up as regular.
"vol + & power up" brings the diagnostic menu but nothing to gain there.

factore restore -> configuration -> gear icon -> tapping on the firmware version doesn't do anyrthing, no matter how fast or often I tap.
So: I need to flash.

Installed the qualcom drivers (tried both options: WWAN & eth network).
the device is found in windows and I can open it up as USB storage, so the driver seems to work fine.
But it's nowhere to be found in device manager and QFIL shows me no port.

So what did I do wrong?
If the driver allows me to use it as a USB device, it's obviously working, right?
Any hints here?
Try to check the ADB connection.
Install ADB.
Connect the wire to the Usb 2.0 port (black, NOT BLUE) and to the tablet.
Launch "ADB"
Input the command "adb devices" and press enter
See if there is a name for your device?
If there is, copy "adb shell am start -a android.settings.SETTINGS" into the adb window and click enter.
A real system menu will open on the device.
 

Attachments

  • Adb-devices.png
    Adb-devices.png
    8.2 KB · Views: 38

southy44

Member
Mar 16, 2023
10
0
Try to check the ADB connection.
Install ADB.
Connect the wire to the Usb 2.0 port (black, NOT BLUE) and to the tablet.
Launch "ADB"
Input the command "adb devices" and press enter
See if there is a name for your device?
If there is, copy "adb shell am start -a android.settings.SETTINGS" into the adb window and click enter.
A real system menu will open on the device.

Hi,

thanks so very much for helping.
But somewhere I must have taken a wrong turn:
I have ADB installed.
I don't think my laptop has a USB2-port so I went from USB 3 through a USB 2 hub to the device.
Device is showing as a USB storage device in Explorer, but stil ./adb devices will never show any device.

Is this because the USB 3 - port? Then I would set up an older laptop.
 

Xi07

Member
Mar 9, 2023
10
5
Hi,

thanks so very much for helping.
But somewhere I must have taken a wrong turn:
I have ADB installed.
I don't think my laptop has a USB2-port so I went from USB 3 through a USB 2 hub to the device.
Device is showing as a USB storage device in Explorer, but stil ./adb devices will never show any device.

Is this because the USB 3 - port? Then I would set up an older laptop.
There may be problems with the usb 3.0 port. I couldn't flash through it, but it flashed through usb 2.0
 
  • Like
Reactions: extranatural

southy44

Member
Mar 16, 2023
10
0
There may be problems with the usb 3.0 port. I couldn't flash through it, but it flashed through usb 2.0

Aaaand it worked...

I guess it wasn't USB 2/3, but the fact that I did need to use a specific version of the QFIL (the one included in the QPST package and not the one downloaded speerately).
Then I installed Nova launcher, switched to it, installed a button remapper, set my buttons, installed the Amazon App store (I suppose the google play store won't work, right?), installed myself the HomeAssistant App and...
...have myself a great new homeassistant status device.

Thanks!!
 
Last edited:

badtown

New member
Mar 21, 2023
2
1
Hi,
I tried the QFIL included in the QPST package:
same result: no adb
I can have fastboot or COM driver
flashed with 200628.084 Teams & Others (ADB Turned on by default)
But unable to connect via adb (empty devices list )
some help :)
 

Xi07

Member
Mar 9, 2023
10
5
Hi,
I tried the QFIL included in the QPST package:
same result: no adb
I can have fastboot or COM driver
flashed with 200628.084 Teams & Others (ADB Turned on by default)
But unable to connect via adb (empty devices list )
some help :)
Connect the wire to USB 2.0. Install the program - ADB Installer v1.4.3 (including Google driver) from here https://forum .xda-developers.com/t/official-tool-windows-adb-fastboot-and-drivers-15-seconds-adb-installer-v1-4-3.2588979/
 

badtown

New member
Mar 21, 2023
2
1
yeah !!
I pass through a hub: usb3 --> usb2
Boot normally (don't press any button)
In device manager:
Android Composite ADB Interface
USB\VID_18D1&PID_4EE7&REV_0318

And: All is fine, I can use adb
Now, I can install apk (nova launcher, button remapper, radio ..)
THANKS :cool:
 
  • Like
Reactions: southy44

Xi07

Member
Mar 9, 2023
10
5
Made TWRP. Works. The touchscreen starts only after the screen goes off with the + or - button.
- replace it in the folder with the firmware.
- install using qpst.
 

Attachments

  • 20230215_185513.jpg
    20230215_185513.jpg
    1.1 MB · Views: 55
  • recovery.img
    24.2 MB · Views: 35
Last edited:

southy44

Member
Mar 16, 2023
10
0
Well, what a ride:
I initially bought this device to use it for work. However after I switched work places after a few months it turned out not to be compliant with my new place's intune policies.
This is why I was trying to get a proper launcher onto it int the first place - to use it for something else.

Now with the new launcher, I tried to use it with the Homeassistant app. And failed.
It will connect to my HA server and show the URL and promt me to enter a user/pw, but then fail with "unable to connect". I removed the app, re-installed, deleted the cache... nothing. It just doesn't work.

BUT.... Since I now have access to the devices' settings I switched on "PIN"; encryption was already on and then thought... "hmmm... I wonder what other requirements intune might have"... so I tried authenticating in Teams once more and what do you know... It works.

Now the unit doesn't work for HomeAssistant but in exchange it does work for its initial purpose :)

I call that a win :)

Have fun you all with your smarties!


Oh, by the way... did anyone try to install the playstore or are there so many google services missing that it won't work?
 

LocoLobo79

Member
Feb 7, 2023
6
0
Well, what a ride:
I initially bought this device to use it for work. However after I switched work places after a few months it turned out not to be compliant with my new place's intune policies.
This is why I was trying to get a proper launcher onto it int the first place - to use it for something else.

Now with the new launcher, I tried to use it with the Homeassistant app. And failed.
It will connect to my HA server and show the URL and promt me to enter a user/pw, but then fail with "unable to connect". I removed the app, re-installed, deleted the cache... nothing. It just doesn't work.

BUT.... Since I now have access to the devices' settings I switched on "PIN"; encryption was already on and then thought... "hmmm... I wonder what other requirements intune might have"... so I tried authenticating in Teams once more and what do you know... It works.

Now the unit doesn't work for HomeAssistant but in exchange it does work for its initial purpose :)

I call that a win :)

Have fun you all with your smarties!


Oh, by the way... did anyone try to install the playstore or are there so many google services missing that it won't work?
I tried. It kept crashing. even tried several different guides on installing gapps, but none worked. I ended up installing the Aurora store.
 

Xi07

Member
Mar 9, 2023
10
5
I tried. It kept crashing. even tried several different guides on installing gapps, but none worked. I ended up installing the Aurora store.
The gapps will not be installed until the android build on the device is registered.
This device is not registered. and there are 2 possible solutions:
-need to change the build.prop and vendor.prop parameters to the registered ones
- replace the Google ID
 

Attachments

  • 20230306_191653.jpg
    20230306_191653.jpg
    1.6 MB · Views: 77
  • 20230306_191700.jpg
    20230306_191700.jpg
    1.6 MB · Views: 78
  • Like
Reactions: southy44

enablerapi

New member
Dec 19, 2010
2
0
Hi Guys. I'm trying to use Teams version for zoom, but I get "update" Error. "Zoom rooms must be upgraded to join this meeting. Please contact IT for assistance."

In ZDM I do not see ability to update firmware or software.
FW is CD-18781Y.210602.2103
App version is 5.6.3

Are there any users who use Teams panels converted to zoom normally?
 

southy44

Member
Mar 16, 2023
10
0
One more thing: So as described I have my Thinksmart running teams again, but I'm wondering:
The device does not allow to apply background blur in teams. The option is simply not existing.
Which is obviously available in Teams for android IF the follwoing requirements are met:

Android requirements​

To change your background, your Android device must have the following:
  • Teams mobile app for Android (version 1416/1.0.0.2021143402 or later)
  • Android version 10 or later
  • GPU
    • Qualcomm Adreno 610 or later
    • Arm Mali-G71 or later
    • Arm Mali-T720 or later

That would be a "check" for the App version (interestingly enough the app must have updated itself at some point)
But what sort of GPU is used in these devices? How would I find out?

I have Firmware 200628.084.
What Andorid version is that? Can Android be updated? independently of the firware?

Is there any chance I can get "background blur" or is the thing just not powerfull enough?
 

LocoLobo79

Member
Feb 7, 2023
6
0
One more thing: So as described I have my Thinksmart running teams again, but I'm wondering:
The device does not allow to apply background blur in teams. The option is simply not existing.
Which is obviously available in Teams for android IF the follwoing requirements are met:



That would be a "check" for the App version (interestingly enough the app must have updated itself at some point)
But what sort of GPU is used in these devices? How would I find out?

I have Firmware 200628.084.
What Andorid version is that? Can Android be updated? independently of the firware?

Is there any chance I can get "background blur" or is the thing just not powerfull enough?
I checked for you and blur does work. When I first open teams it says "teams won't run without google play services", but I didn't encounter any issues with the things I did try.

To answer your other question it runs Android Things not stock Android. Android Things was discontinued in 2021 if I remember correctly. I do know the last version was 8.1. From what I can tell there isn't a lot of difference in stock android.

I hope someone writes custom firmware for this, but that is way beyond me.
 

Xi07

Member
Mar 9, 2023
10
5
If there are problems with the navigation buttons. I'm putting it out the navigation button program.set as a regular apk. It is enabled in special features.
 

Attachments

  • NavigationBar.apk
    3.7 MB · Views: 15

Xi07

Member
Mar 9, 2023
10
5
For those who do not want to replace build.prop, I upload a Google id substitution program. set as a regular apk. After installing and running the id substitution, install Google play.
 

Attachments

  • com.google.android.gms.apk
    56.4 MB · Views: 31
  • Like
Reactions: southy44

Xi07

Member
Mar 9, 2023
10
5
One more thing: So as described I have my Thinksmart running teams again, but I'm wondering:
The device does not allow to apply background blur in teams. The option is simply not existing.
Which is obviously available in Teams for android IF the follwoing requirements are met:



That would be a "check" for the App version (interestingly enough the app must have updated itself at some point)
But what sort of GPU is used in these devices? How would I find out?

I have Firmware 200628.084.
What Andorid version is that? Can Android be updated? independently of the firware?

Is there any chance I can get "background blur" or is the thing just not powerfull enough?
The description of the program specifies the requirement for teams android 8.0 and higher. Firmware 200628.084 has android 8.1
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Wrote a separate guide here since I needed to attach a couple of files and since it'd be easier to just flash the device differently from the start: https://forum.xda-developers.com/t/...our-lenovo-thinksmart-view-cd-18781y.4584033/

    You can technically get it to work without reflashing the device though
    Thanks for doing this work! I've added a link to your work in the OP as a note for people who want more tweaks.
  • 4
    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:
      Code:
      adb install APK_FILE_NAME.apk
    10. You will then need to send this adb command to select a new default launcher:
      Code:
      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

    Root, TWRP, Playstore, Custom Webview can be found at @Chewie610's thread
    here

    Credit: @WhyPartyPizza on reddit for the adb enable steps
    3
    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!
    2
    Made TWRP. Works. The touchscreen starts only after the screen goes off with the + or - button.
    - replace it in the folder with the firmware.
    - install using qpst.
    1
    Notes

    Boot buttons
    Vol- plus Power plug in = Fastboot
    Vol+ plus Power plug in = Recovery
    Vol+ and Vol- plus power plug in = EDL

    Even after EDL flashing firmware when unlocked it still drops into 900E. I also tested flashing unsigned images when bootloader locked but it does not boot as expected.
    1
    Wrote a separate guide here since I needed to attach a couple of files and since it'd be easier to just flash the device differently from the start: https://forum.xda-developers.com/t/...our-lenovo-thinksmart-view-cd-18781y.4584033/

    You can technically get it to work without reflashing the device though
    Thanks for doing this work! I've added a link to your work in the OP as a note for people who want more tweaks.