[Bounty €50] Xiaomi 14T – “Couldn’t initialize user 0” after KernelSU / GKI – /data not mounting


J

JAIDO

Members
3 Dec 2024
4
15
Device: Xiaomi 14T
OS: HyperOS / Android 14
Bootloader: Unlocked
Bounty: 50 € for a technically sound solution without data wipe (PayPal / SEPA)

Short summary

After experimenting with KernelSU / GKI, the device no longer boots and always ends with:

“Couldn’t initialize user 0”

/data is not mounted at all, vold never reaches FBE initialization.
Restoring all boot / AVB related partitions via fastboot did not fix it.

I am explicitly looking for deep technical help, not generic “factory reset” advice.

Timeline

OTA upgrade
- Upgrade to build 205
- Update completed successfully
- Device booted normally

Preparing GKI / KernelSU
- Patched the new init_boot (KernelSU)
- Flashed patched init_boot
- Installed KernelFlasher
- Created full backups of all offered partitions

Kernel install
- Installed
6.1.115-android14-2024-12-Normal-AnyKernel3
(matching kernel version) via KernelFlasher
- Device booted
- KernelSU Next 3.0 reported errors:
- Kernel version 14012 < required 22000
- SUSFS / COMP disabled
(despite being KSU Next 3.0)

Critical mistake
- Assuming I could fully revert at any time, I flashed:
android14-6.1.115_2024-12-boot-lz4.img
(from KernelSU-Next releases)
- Expectation: KernelSU error would be resolved

After that
- Device no longer boots
- Error: “Couldn’t initialize user 0”
- Falls back to recovery

What I tried afterwards

- OTA upgrade again (to revert everything)
- Re-flashing and testing:
- original boot
- original init_boot
- patched init_boot
- Full restore of backed-up images via fastboot:
Code: 
boot.img
init_boot.img
vendor_boot.img
vbmeta.img
dtbo.img
system_dlkm.img
vendor_dlkm.img
- No success
 
I can not post the rest of the text because of spam check stuff... ?!


Current technical state
From ADB shell in recovery:
mount → no /data mount
Only /cache is mounted
getprop ro.*****.state → empty
getprop vold.decrypt → empty
vold never reaches encryption or user preparation


What I am looking for
Concrete technical input such as:
Known HyperOS / Xiaomi 14T issues with user 0 / vold / FBE
Specific flashing order, flags, or partitions that matter here
Known incompatibilities between KernelSU-Next and Xiaomi 14T
Recovery, low-level, or EDL-based approaches that do not default to wiping data

I will pay 50 € for:
a plausible technical explanation with a working solution, or
a realistic recovery path (even experimental) that could re-bind /data

Please do not reply with:
“Just wipe data”
“KernelSU is risky”
“You shouldn’t have done that”

Important
I am aware:
A factory reset will likely fix the boot
Data loss is the default answer

Thanks to anyone willing to dig into this.

Post was created with AI, and I tried to get help from it. So some mentions like with getprop vold.decrypt is based on stuff AI put out, not about knowlege from my side that I would know this is important. I tried to be as clear / straight forward what I have done and whats the current problem.
 
Last edited:
I never understood how the decrypt key works in that manner. Where is it stored? can it be backuped up? How can I wipe it while flashing? Why is it los by flashing a "wrong?" image but not with the right image? Can someone link me to some explaination / guidance?

Maybe @Igor Eisberg can you confirm the situation?
 
You must log in or register to reply here.
Top Bottom
Back