Forum Discussion
Android 15 Setup Wizard loops at “Accept Google Services” on Lenovo Tab M11 (TB311FU)
Hi all,
I'm running into a blocking issue provisioning brand-new (and factory-reset) Lenovo Tab M11 - TB311FU devices on Android 15 with Android Management API (fully managed / dedicated, kiosk).
On Android 14 everything worked fine with the exact same policy and enrollment flow.
The issue only started after updating to Android 15. (this is my test device, i constantly factory reset it)
Expected behavior:
Standard QR (6-tap) provisioning to proceed past the “Accept Google Services” screen, install Android Device Policy, enroll to my enterprise, and apply the kiosk policy, install app, and done.
What happens instead:
- After Wi-Fi and scanning the AMAPI QR token, Setup Wizard reaches “Accept Google Services”.
- Tapping Accept shows a spinner, then it returns to the same screen (loop). I simply cannot get past this point.
- If I reboot at this point, on the very first Welcome screen the device sometimes becomes unresponsive (neither 6-tap nor “Next” reacts) until I factory reset again.
- Is there a known Android 15 Setup Wizard issue that can cause a loop at “Accept Google Services” on Lenovo TB311FU?
- Any workarounds you'd recommend to get past the acceptance loop?
When factory resetting, and setting up the tablet without scanning the qr code, i get past the Google Services no problem.
When i install via qr-code on new fresh never used before tablets, that come pre-installed with Android 14, i don't have any issues. Same policy, same everything... except the Android version.
Thanks in advance!
/B
10 Replies
Balslev Were you able to solve this problem?
I have similar issue with Lenovo Tab TB311XU. I'm trying to enroll the device to Soti MobiControl with QR-code. When doing it off the box I had no problems, but now that the device is upgraded to the latest OS version, I get stuck on the Accept Google Services page.
Interesting, i see our helpdesks enrolling this device with success (using ZTE) to the console. The only problem we have is, that the plugin installed afterwards to grant all the permissions to the agent and so on is broken and we waitfor the certification so they provide one which works (on it with our TAM's).
But maybe the versions are different, so please tell me yours, we are using this one: TB311XU_ROW_OPEN_USER_M5.8_V_ZUI_17.0.31.149_ST_250613 (Android 15)
Also maybe worth to compare your QR code settings, may you provide it here (remove sensitive/relevant data like enrollment id and so on).
In ZTE, we only use this:
{
"android.app.extra.PROVISIONING_USE_MOBILE_DATA":true, "android.app.extra.PROVISIONING_ADMIN_EXTRAS_BUNDLE":
{"enrollmentId":"....","PROVISIONING_MODE":"FULLY_MANAGED_DEVICE"}
}Version is Android 15 TB311XU_ROW_OPEN_USER_M5.8_V_ZUI_17.0.31.206_ST_250814, so it is different.
QR code settings are as following (generated from Mobicontrol console):
{"android.app.extra.PROVISIONING_DEVICE_ADMIN_COMPONENT_NAME":"net.soti.mobicontrol.androidwork/net.soti.mobicontrol.admin.DeviceAdminAdapter","android.app.extra.PROVISIONING_DEVICE_ADMIN_PACKAGE_DOWNLOAD_LOCATION":"http://soti.net/apk/ae2
","android.app.extra.PROVISIONING_DEVICE_ADMIN_SIGNATURE_CHECKSUM":"XXX=","android.app.extra.PROVISIONING_WIFI_SSID":"XXX","android.app.extra.PROVISIONING_WIFI_PASSWORD":"XXX","android.app.extra.PROVISIONING_WIFI_HIDDEN":false,"android.app.extra.PROVISIONING_WIFI_SECURITY_TYPE":"WPA","android.app.extra.PROVISIONING_SKIP_ENCRYPTION":false,"android.app.extra.PROVISIONING_LEAVE_ALL_SYSTEM_APPS_ENABLED":true,"android.app.extra.PROVISIONING_LOCALE":"XXX","android.app.extra.PROVISIONING_TIME_ZONE":"XXX","android.app.extra.PROVISIONING_ADMIN_EXTRAS_BUNDLE":{"dpc_company_name":"Soti Inc.","enrollmentId":"XXX"}}Tested also QR code without enrollment ID and based on your hint I disabled automatic plugin install on the enrollment rule, but without a luck. Side note, when the screen is stuck, the device is still enrolled to Mobicontrol and for example I can wipe the device from the console.
When enrolling with afv#mobicontrol tag and then manually entering the enrollment ID it won't get stuck on the Accept Google Services page. But this way we can't leave all the system apps enabled and
Interesting,
we use the same model but LTE version (TB-311XU) and started with Android 15 without any issues yet (using Google Zero-Touch Portal for provisioning).
2 things i would like you to test:
- Flash the device with the Lenovo "Software fix" tool to latest firmware version and test again as it sounds for me like a OEM bug.
- If you don't have keep system apps enabled in your QR, provide it with "true" in your QR but don't expect it to make a really difference.
In general if "1." doesn't help, i recommend reaching out to Lenovo regarding this.
