yashsingh1/xdaforums huggingface dataset:
[Google Home] noname_93:
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 ?
[Google Home] 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?
[Google Home] kancept:
Has anyone tried flashing the Lenovo smart Display 8 (Amber) roms to these?
[Google Home] gforums:
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
[Google Home] kancept:
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.
[Google Home] 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
[Google Home] Ranomez:
So wait, are you using Magisk with a locked bootloader or did Magisk allow you to boot with an unlocked bootloader?
[Google Home] garnir4ik:
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
[Google Home] Ranomez:
Yes to which one cause that was an "or" question?

So did you unlock bootloader or not?
[Google Home] 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.
[Google Home] garnir4ik:
the bootloader is blocked
[Google Home] LocoLobo79:
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...
[Google Home] blaz.law:
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
[Google Home] blaz.law:
Could you pls help and describe what you did after you flashed both devices to 201006.099,.. thanks for help!
[Google Home] Drier5829:
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.
[Google Home] blaz.law:
is any tried flashed amber (lenovo smart display) on this lenovo thinksmart view? I want to get google home on lenovo thinksmart view
[Google Home] 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
[Google Home] remrog:
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 🥴
[Google Home] southy44:
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 :-)
[Google Home] southy44:
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!
[Google Home] Xi07:
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.
[Google Home] southy44:
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.
[Google Home] Xi07:
There may be problems with the usb 3.0 port. I couldn't flash through it, but it flashed through usb 2.0
[Google Home] southy44:
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!!
[Google Home] badtown:
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 :)
[Google Home] Xi07:
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/
[Google Home] badtown:
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:
[Google Home] Xi07:
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.
[Google Home] southy44:
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?
[Google Home] LocoLobo79:
I tried. It kept crashing. even tried several different guides on installing gapps, but none worked. I ended up installing the Aurora store.
[Google Home] Xi07:
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
[Google Home] enablerapi:
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?
[Google Home] southy44:
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?
[Google Home] LocoLobo79:
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.
[Google Home] Xi07:
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.
[Google Home] Xi07:
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.
[Google Home] Xi07:
The description of the program specifies the requirement for teams android 8.0 and higher. Firmware 200628.084 has android 8.1
[Google Home] southy44:
Interesting.

How would it work for you but not for me... what Firmware do you have?
[Google Home] southy44:
Thanks, this really sounds promising - will try the next days.
[Google Home] LocoLobo79:
It sounded like you were using the teams firmware. I did it with the teams android app.

That same day I had a meeting and while the blur worked I could not get my mic to work. Not sure why.
[Google Home] LocoLobo79:
You seem to know a lot more about this than me. I installed the apk you included. I added my google account and registered. Yet the play store still crashes every time I open it. Any ideas?
[Google Home] southy44:
Yes I have the Teams firmware...

... which I assumed would be Android + the teams app.

You mean to say you installed it seperately?

Let me check if I can find an apk... perhaps I can install it alongside the one I have...

Thanks for responding btw.
[Google Home] LocoLobo79:
Yes. I used aurora store to download and install the teams app. It is different than the firmware teams app, from what I can tell.
[Google Home] Xi07:
You need to go into the program and put a permission to register the device Google id
[Google Home] southy44:
Thanks for the tipp. But this seems to be harder than I thought.

I have the following steps sucessfully done:

[x] device registered

[x] logged in with a google account.

Self-check shows [x] everywhere EXCEPT the signature-related checks: I don't have "spoofed signature support".

I tried installing the BlankStore, but couldn't log in:

On startup it asked me to "create an account for Adroid Market".

I used a testing google-acc and Password, set a user name and password, but not any of the other details (google-device details - see below *) ). Now it only displays a button "installed apps", but when you click there the app crashes.

So I removed BlankMarket and installed the "real" com.google.vending - which is what I want anyway - from here (number 4 on the list).

(Remember to remove prior google accounts from [settings - users])

Upon enterint the account details, it will show terms & conditions and display "app tries to sign in into account"... but the signin won't get completed: "your device is establishing a connection to google to save information in your account".

I'll find a google-user-coount in the system settings (no play store account), but whenever you try to sign in it'll not get beyond "An App on your device is trying to sign in to a google account".

The sign-in-process won't complete.

Is that due to the lack of a spoofed signature?

Why won't "Blank Market" work?

So coming back full circle:

Did you manage to get "spoofed signature support" sorted out of the device?

And did you use the "Blank Market" or the Phonesky or the google play store?

And how did you manage to log into play store then?

I'm really grateful for any feedback, thanks in advance and have a great day!

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

*) Blank Market:

Abtain Android_ID

adb shell
settings get secure android_id (delivers the andorid ID).

That seems to be the one that microG shows in "device registration"

BUT: read here - this is apparently NOT the right "android_id", there seem to be two different ones. The one for the playstore *shoul* be obtained by the

dial *#*#8255#*#*

watch out for "Device ID"

remove the leading android-

what remains, is the android_id used by Google Services

So I installed "simple dialer" and tried that... to no effect. It will dial and then abort without showing any result.
[Google Home] Xi07:
I will try to go through all the steps again. Maybe I made a mistake somewhere. But the fact that Google Play is set is 100%. I've already applied the photo.
[Google Home] Chewie610:
TWRP:

Got TWRP set up thanks to @Xi07's recovery file. However, TWRP doesn't seem to be very usable as we are unable to access recovery mode while having bootloader unlocked.

If you want to install TWRP, I can clarify the instructions a little better:

Follow the "Flashing the Lenovo firmware" steps on the original post. Before you flash, open the extracted firmware folder > image. Replace the recovery.img file with @Xi07's recovery image.

If you're getting some Sahara error while flashing, you may be waiting too long to flash. The device must be flashed moments after it is booted into EDL mode (powering on with Vol + and Vol - held down). Once you plug in your device, hit download the moment the port is recognized at the top of QFIL.

Google Play Question to @Xi07:

As per how @Xi07 got the

newest version

of Google Play up and running, I'm not exactly sure... did you change the build.prop and vendor.prop parameters within the device? Or do you also have some Magisk modules...?

If you use microG along with Signature spoofing (requires a couple of Magisk modules, I can point you to how to do that if you need it @LocoLobo79), you can get an

older patched version

of Google Play, but not the newest version. So I was curious how you got the newest version of Google Play to work.
[Google Home] Capne555:
Dear all,

I am happy that other people have the same idea, to use this great-looking product not only for TEAMS.

Have read this thread many time, but can not achieve my goal to run android system and use Smart View like a tablet, to see energy monitor of my home energy management system, on the sideboard of my living room.

I am struggling with step 8 of the manual, first page of the thread.

I followed all steps of Flashing the Lenovo firmware. Worked fine. I used file 201006.099.

After flashing I reboot the Smart View and go step by step until step 7 and 8.

Edit:

At first, I have to find a solution how to use ADB command files. Here I found SDK Platform-Tools for Windows. The next step was, to figure out what it means to download a desired Launcher. I have chosen Nova, downloaded the Nova Launcher apk, and installed it.

After this installation, with the command of step 10, the first time I get a "feedback" from the Smart View device.

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

Now I have to go on, ad first I need buttons to make input.
[Google Home] extranatural:
Did you ever figure this out?! I have the same issue.
[Google Home] Chewie610:
Hey Capne, I can help you with that. I can also provide instructions on how to get the newest Google Play version working if y'all are interested. Lemme write up a guide for that.

To get better access moving around the tablet's UI, you can either use a button remapper or a navigation bar app (I've attached the one I use here). You can install it using adb commands as well, just use command prompt to navigate to the directory of the file and do adb install package_name

I also recommend you either use adb to uninstall/disable the Kiosk mode app or root your device so that you can disable the Kiosk mode app (and all other useless apps). If you plan on using this device to use certain apps like HomeAssistant, you will also need to update your System Webview (which I did using root).

When you plug in your device, do you see the device show up like mentioned in step 13 of the post? If you do, that just means you're too slow when attempting to install the firmware. The device must be flashed moments after it is booted into EDL mode (powering on with Vol + and Vol - held down). Once you plug in your device, hit download the moment the port is recognized at the top of QFIL.
[Google Home] extranatural:
I I

Hey Chewie thanks for the quick reply.

The computer I was using runs Windows 11 only has USB-3 ports. I had seen another comment in the thread suggesting Windows 11 needed to have driver signing disabled so I spent hours figuring out how to disable driver signing, and uninstalling and reinstalling various drivers. In the end the driver stuff was not the issue instead it was the USB port.

In an act of desperation I dug out my 2014 Alienware Alpha R1 from storage, and repeated the same procedure but with a dedicated USB-2 port and it worked great.
[Google Home] Chewie610:
Strange, I was using my USB 3.0 ports just fine. Glad it worked out in the end for you though! I'll send out a guide to getting the official Play Store setup once I have time.
[Google Home] extranatural:
Now I'm stuck at the same step as Chewie and others, I did the same steps using the registration tool, but the Play Store Crashes on boot.

Maybe you could link to the play store APK you successfully installed?
[Google Home] Chewie610:
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://xdaforums.com/t/guide-root-...our-lenovo-thinksmart-view-cd-18781y.4584033/

You can technically get it to work without reflashing the device though
[Google Home] deadman96385:
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.