Using KingRoot on Android 13 is not recommended and is unlikely to work, as the app is severely outdated and generally ineffective for versions beyond Android 5.1 or 6.0. Why You Should Avoid KingRoot on Modern Android (13+):
The utility of KingRoot on Android 13 is effectively non-existent for the vast majority of devices. The convergence of Verified Boot, GKI, and strict SELinux policies has rendered the exploit-based rooting model obsolete. Users attempting to use KingRoot on Android 13 face a high probability of system instability, security compromise, and failure to achieve root access. kingroot android 13
Example for Pixel 6/7 on Android 13:
KingRoot historically worked by finding a security vulnerability in the Android system to force "root" access. It did not unlock the bootloader. Android 13, however, has patched the vast majority of these known vulnerabilities. Modern Android devices are designed to detect and block these types of injection attempts immediately. Using KingRoot on Android 13 is not recommended
KingRoot worked by using a "root daemon" that brute-forced permissions. It didn’t require unlocking the bootloader because it attacked the kernel directly. For many users on Android 5, 6, and 7, it was revolutionary. Keep stock firmware and know how to restore
If you truly need root access on Android 13, you must abandon the "one-click" dream and embrace the modern method: Magisk (maintained by topjohnwu and the open-source community).