运行CTS后安卓设备要求输入未设置的PIN码，寻求解决方案

Hey there, let's tackle this frustrating issue you're facing—unexpected PIN prompts on three Android devices after running CTS via script, even though you never set a lock PIN. Based on the fact this is happening across multiple devices and you're using an automated script, the script itself is almost certainly the root cause. Here's how to diagnose and fix it:

First: Verify the Script's Impact #

CTS often requires specific security configurations to run, and automated scripts might enforce these without explicit notification. Check your script for:

• Commands using dpm (Device Policy Manager), like dpm set-device-owner or dpm set-profile-owner. These can trigger a mandatory PIN lock when setting up a managed device/profile, even if you don't specify one.
• Any calls to locksettings that might set a PIN silently in the background.

Fix 1: Unlock via ADB (If USB Debugging Is Still Enabled) #

If you can still connect the device to your computer via ADB, try these steps:

1. Confirm the device is recognized by your system:

   adb devices
   

2. Try common auto-generated CTS PINs to clear the lock (these are defaults used in many CTS configurations):

   adb shell locksettings clear --old 0000
   

   If 0000 doesn't work, test 1234, 1111, or 000000 next.
3. If the lock is tied to a CTS-managed device admin, remove the admin component:

   adb shell dpm remove-active-admin com.android.cts.priv.ctsshim/.CTSShimDeviceAdminReceiver
   

   This is the standard CTS admin component; adjust the package/class path if your script uses a custom one.

Fix 2: Factory Reset (If ADB Is Blocked) #

If the PIN lock prevents USB debugging access, your only fallback is a factory reset. Make sure to back up any critical data first, as this will wipe all device content. Since this affects three devices, this confirms the script is applying a universal setting that's causing the lock.

Prevent This From Happening Again #

To avoid future surprises, modify your CTS script to explicitly set a known PIN before running the test plan:

# Set a predefined PIN before starting CTS execution
adb shell locksettings set-pin 1234

This way, you'll always know the PIN to use if the device prompts you. Also, audit your script to remove any unintended dpm commands that enforce managed profiles unless they're strictly required for your test plan.

内容的提问来源于stack exchange，提问作者dvir