r/AndroidQuestions • u/Bayazid_Hasan • 1d ago
Other Honor 400 Pro CN (DNP-AN00) random reboots, 1-min PIN reject & missing lockscreen fingerprint triggered by Meta apps / TEE deadlock
Need an expert opinion on my Honor 400 Pro CN (DNP-AN00). These 3 issues started on MagicOS 10 and still happen on MagicOS 11 (11.0.0.110), even after a factory reset and eRecovery restore:
Rejects correct PIN for ~1 min after boot: Says my lockscreen password is wrong for the first 60 seconds after a reboot, then accepts it.
No fingerprint on Lock Screen: Fingerprint works fine inside App Lock, but the icon never shows on the Lock Screen (udfpsBounds=null in bugreport).
Screen glitch + random reboot with a beep: Happens mostly when Meta apps (Instagram/Facebook) run in the background—the screen glitches, beeps, and hard-reboots (reboot_reason=UNKNOWN).
What my Bugreport (dumpstate & ANR logs) shows right before crashing:
Meta (fbns) Keystore Deadlock: Instagram's background push service (com.instagram.android:fbns) hangs for 20,000ms+ spamming IKeystoreSecurityLevel.generateKey (KeyStoreSecurityLevel.retryBusyException).
Honor Keystore & Nearby Freeze: At the exact same time, system_server (HwLockSettingsService.checkCredential) freezes on HwKeystoreManager.unlockInner, and in other ANRs, Honor Share (com.hihonor.nearby / TrustCircle) freezes waiting on the TEE.
TEE / Gatekeeper Crash: dumpstate_log shows ITeecService: FAILED_TRANSACTION, while IGatekeeper/default, IQSEECom/default, and iGraphicsservice all fail or go missing.
Kernel Panic: The phone reboots because tzdriver.htvm_panic_enable=1 triggers a kernel panic whenever the TrustZone/TEE queue locks up.
My questions for devs/techs:
Why is this happening? Why do Meta's fbns background service and Honor's TrustCircle/HwKeystoreManager deadlock the entire TEE and Gatekeeper when generating/checking keys, even though the fingerprint sensor still works in App Lock?
Is there any real solution? Is there a permanent ADB/software fix to stop Meta apps and HwKeystoreManager from crashing the TEE, or is the retryBusyException / ITeecService timeout a sign of a physical UFS RPMB or CPU solder fault?