What this is about
The error. After the ColorOS 17.0.0.102 update, a OnePlus 15 stops accepting its own correct PIN, pattern or fingerprint. If no PIN was set, it boots to the home screen but apps crash and your files are missing, because the storage is still encrypted. Either way you are locked out of your own data.
The cause. The root cause is unknown and OnePlus has said nothing. What the logs show: after the update, the security chip that checks the PIN (the embedded secure element, eSE) stops responding. No chip, no PIN check, no decryption.
Does a locked bootloader matter? Stock or modified? Not for getting the bug. My phone was a fully stock US CPH2749: never rooted, bootloader locked, and the update installed itself over the air. Other reports come from unlocked, rooted and region-converted phones. The bootloader only matters for the fix: it needs an unlocked bootloader, and unlocking a locked phone wipes it.
Who is affected. OnePlus 15 going from OxygenOS 16 to ColorOS 17.0.0.102. Reports exist for NA (CPH2749), Global (CPH2747) and converted Chinese units. It does not hit every phone and I do not know what fraction.
If you have not updated yet: don't, and switch off automatic system updates in Developer options.
The rest of this post is only for people who are already locked out.
TL;DR
After the OTA from OxygenOS 16.0.10.601 to ColorOS 17.0.0.102, the embedded secure element (eSE) on my US OnePlus 15 (CPH2749) stopped answering. The PIN is never verified, and even with no PIN the phone boots with its storage still encrypted.
What brought the chip back: install a full 17.0.0.102 OTA into the inactive slot from AERA recovery, let that fresh slot kernel-panic into Qualcomm crash dump mode (900E) on its first boot, force restart, then switch back to the original slot. The original slot booted with the eSE alive, and it stayed alive after reboots, a new PIN and relocking the bootloader.
This needs an unlocked bootloader. On a locked phone that means a full data wipe.
It is the method from an XDA report for a Global CPH2747. This post confirms it on a North American CPH2749 with a locked, never-modified phone as the starting point.
Two data points in total. Nobody knows the root cause. Read the caveats before you try it.
Symptoms and how to confirm it
The phone looks alive but nothing that needs your data works: apps crash or hang, the phone service and SystemUI stop responding, the gallery is empty. If a PIN is set, the correct PIN is rejected after a long wait.
Removing the PIN before the update does not help. The empty-credential key is bound to the same chip, so the storage stays locked anyway.
With USB debugging on, these four checks confirm it:
adb shell dumpsys secure_element
adb shell "dumpsys user | grep State"
adb shell "dumpsys mount | grep unlocked"
adb logcat -d | grep -E "eSE not found|Failed to unwrap"
| Check | Broken | Healthy |
|---|
dumpsys secure_element | only SIM1 and SIM2 | eSE1 with mIsConnected:true |
| User state | RUNNING_LOCKED | RUNNING_UNLOCKED |
CE unlocked users | [] | [0] |
| logcat | OmapiTransport: secure element reader eSE not found, Failed to unwrap synthetic password for unsecured user 0, com.android.se crashing in a loop | GPQeSE-HAL replies ending in 9000 |
What did not work
| Attempt | Result |
|---|
| Normal reboots | no change |
| Forced restarts with Power + Volume Up | no change |
| Draining the battery to 0 % and leaving the phone off for 24 minutes | no change |
| Unlocking the bootloader, which wipes data | storage works again without a PIN, the eSE is still dead |
A wipe alone gives you a usable phone with no PIN and no fingerprint. Others report that rolling back to OxygenOS 16 does not bring the chip back either.
What you need
A PC with a USB cable, and "OEM unlocking" plus "USB debugging" switched on in Developer options.
Use the full OTA for your own model and region when one exists. For North America there is no full 17.0.0.102 package anywhere, only the incremental one, so I used the Global CPH2747 package. It only ever goes into the spare slot.
I compared a dump of my NA slot with the Global package hash by hash. 59 of 65 partitions are byte-identical, including boot, vendor, modem, xbl, abl, tz and keymaster. Only my_stock, my_region, my_manifest, engineering_cdt and splash differ.
Steps
My active slot was b. Replace b with your own active slot (fastboot getvar current-slot).
Unlock the bootloader. This wipes the phone.
Confirm on the phone with the volume and power keys. The phone wipes itself and boots the same 17.0.0.102 clean. Finish setup without a PIN and switch USB debugging back on.
Flash AERA recovery. Extract recovery.img from the AERA zip first.
The image cannot be started with fastboot boot. It has to be flashed.
Back up the active slot. Strongly recommended, and the only safety net if no full package exists for your region. In AERA, adb is a root shell.
Do this for every *_b entry in /dev/block/by-name and every *_b entry in /dev/block/mapper (skip the -cow ones), and compare each hash with the file on the PC. Mine was 54 physical and 17 logical partitions, 9 GiB, about 10 minutes.
Sideload the full OTA. Do not wipe anything.
The first command blocks, so run the second one from another terminal once adb devices shows sideload. It took about 12 minutes. The package is written to the inactive slot, which then becomes the active one. AERA restores itself into that slot's recovery.
Reboot into the fresh slot.
Expected result: a black screen, and the PC shows Qualcomm HS-USB Diagnostics 900E (USB\VID_05C6&PID_900E). The new slot has kernel-panicked. This is the crash you want.
Force restart once. Unplug USB, hold Power + Volume Up until the logo appears, let go. For me it crashed again within a minute.
Enter fastboot. Hold Power + Volume Up again, and as soon as the phone restarts, switch to Power + Volume Down until the fastboot screen shows. Plug USB back in.
Switch back to the original slot and boot it.
The original slot boots normally, in about 15 seconds for me. Check the chip.
Verify
adb shell dumpsys secure_element
adb logcat -d | grep GPQeSE-HAL
eSE1 is listed again with mIsConnected:true, and GPQeSE-HAL shows rApdu received lines ending in 9000. On my phone StrongBox key provisioning also succeeded right away and com.android.se stopped crashing.
Then test it the hard way: reboot normally, set a PIN, reboot again and unlock. All three worked for me. Do this before you put any data back on the phone.
Optional: relock the bootloader
Relocking wipes the phone again. A locked phone with a custom recovery can fail to boot, so restore the stock recovery first.
Get the stock recovery. I extracted recovery.img from the full OTA payload. vbmeta is byte-identical between NA and Global, and recovery is a chained partition, so the Global image is the right one for an NA phone. I checked its AVB signature against the chain key in my phone's vbmeta before flashing.
While AERA is still installed, mark the spare slot unbootable. Here the spare slot is a, which is slot number 0.
Flash the stock recovery to both slots.
I also flashed my dumped NA engineering_cdt and splash back to slot a. That is tidiness, not a requirement.
Check the state in fastboot. Lock only if all of these hold.
Boot once into the stock recovery to see that it starts, then boot Android and confirm the eSE is still there.
Leave "OEM unlocking" switched on, then lock.
The phone wiped itself and was back in Android one minute later: locked, verified boot green, eSE alive, PIN working.
Caveats
Two data points. The XDA author had a Global CPH2747 that was already unlocked. Mine is a North American CPH2749 that was locked and stock. It may not work for you.
It saves the chip, not the data. On a locked phone the unlock in step 1 wipes everything, and with the storage locked you cannot back it up first. The XDA author kept their data only because the bootloader was already unlocked.
The foreign-region package is a tool, not a system. It lives in the spare slot long enough to crash once. Do not run it as your daily system.
Check anti-rollback before flashing another version. Per OnePlus-antirollchecker every OnePlus 15 build up to 17.0.0.102 has ARB index 0.
Nobody knows why this works. It is not the firmware bytes: the reinstalled slot carries the same boot, vendor, TrustZone and keymaster images. A full battery drain and normal reboots did nothing. A kernel panic during a normal system boot did. That is my reading, not a verified cause.
I did not capture the panic log, so I cannot say what crashed in the fresh slot.
The next OTA is an open question. I switched off automatic system updates, left "OEM unlocking" on and will wait for reports before installing anything newer.
OnePlus has not acknowledged the problem as far as I can find.
Sources and credits
The method is not mine. Credit goes to the author of the XDA report and to the people who documented the failure.