Supervisor Plugin Deployment for Lenovo K9 (TB305FU) and K11 (TB336FU) on Android 15: Request via Esper Support
Android
If you're using Lenovo K9 (TB305FU) or Lenovo K11 (TB336FU) tablets running Android 15, you may need to request a signed Supervisor Plugin from Esper Support to enable advanced device management features like Remote Control. This article explains the process and what to expect.
Before you begin
The Supervisor Plugin grants elevated system-level permissions that standard device management cannot provide. On Lenovo devices running Android 15, the device firmware requires both a signed plugin and firmware-level whitelisting before the plugin can install and function. This is an OEM security requirement, not an Esper limitation.
You'll need:
- Your exact device model number (Lenovo K9 TB305FU or Lenovo K11 TB336FU)
- Your device's part number (for example, ZAF20096US or ZAFS0399US)
- Your device's Android build version
Step 1: Gather your device information
On your affected device, note the following details:
- Device model (Lenovo K9 or K11)
- Part number (printed on the device or visible in Settings)
- Android version and build number
You can also find this information in the Esper Console. Navigate to Devices & Groups, select your device, and view the device details.
Step 2: Request the signed Supervisor Plugin
Contact Esper Support and provide the device information from Step 1. Let them know you need the Supervisor Plugin signed and whitelisted on your Lenovo device firmware. Esper will coordinate with Lenovo to:
- Create a signed Supervisor Plugin build for your device firmware
- Have Lenovo add the plugin to the firmware-level whitelist
This process may take several days to weeks, depending on Lenovo's timeline.
Step 3: Wait for deployment
Once Esper confirms that the signed plugin is ready and Lenovo has updated the firmware whitelist, Esper will deploy the plugin to your device automatically. You don't need to take any manual steps.
The plugin should install within 30–40 minutes of deployment. Restarting your device will accelerate the installation.
Step 4: Verify the installation
After waiting 30–40 minutes (or after a device restart), verify that the Supervisor Plugin installed successfully:
- In the Esper Console, navigate to Devices & Groups → [Device Name].
- Check the Apps section to confirm the Supervisor Plugin package is listed as installed.
- Navigate to Remote Control and test that it initiates successfully.
If Remote Control still isn't working
If Remote Control doesn't work after 40 minutes and a device restart, follow these steps:
- Confirm with Esper Support that Lenovo has completed both steps: the signed plugin build and the firmware-level whitelist update. Either step alone is insufficient.
- In the Esper Console, navigate to Devices & Groups → [Device Name] → Apps and verify the Supervisor Plugin package appears in the list.
- If the plugin is still not installed, collect a bug report by navigating to Devices & Groups → [Device Name] → Actions → Request Bug Report.
- Provide the bug report, device firmware version, and confirmation of the Lenovo whitelist status to Esper Support.
If your device is running a different firmware version than the one originally whitelisted, a new request targeting that specific firmware build may be needed.
Important notes
Keep the following in mind:
- Both steps are required: A signed plugin alone will not work without the firmware whitelist, and vice versa.
- Part numbers matter: Different regional SKUs may use different firmware branches. Always provide your exact part number to ensure the correct firmware is targeted.
- This process is OEM-specific: The firmware whitelist requirement applies to Lenovo devices on Android 15 and may not apply to other manufacturers or earlier Android versions.
- Device restart accelerates installation: Restarting your device after deployment can speed up the plugin installation.
Still need help?
If you've followed these steps and your Supervisor Plugin still isn't working, contact Esper Support. Provide your device model, part number, Android build version, and the results of your verification steps.
Please sign in to leave a comment.
Comments
0 comments