Hi,
After a simple restart, I was greeted with this message and I can’t start the phone. I installed the update several weeks ago, so I don’t know what caused it. Is there still a way to recover the data?
Redmi Note 9 Pro
init_user0_failed
This suggests that your userdata is not loadable at start.
Trying to recover data from the encrypted partition would be very hard. You might search the forum for some of those keywords.
Was this a simple update? Similar has been reported with a recent OTA Android version upgrade.
The last update was e-3.6-a15-20260314594290-community-miatoll
I can boot into recovery and there is adb update, do you think it would make any sense to apply the april update?
I can also open log files from the menu, but I understand nothing from those.
These might possibly give a clue to the cause. One could try to extract the log as How to Pull Log Files from an Android Device to Your PC: Step-by-Step Guide — tutorialpedia.org. However even if you had that clue what would be the chance of recovery of any data?
Is this your device Info about Xiaomi POCO M2 Pro / Redmi Note 9S / Redmi Note 9 Pro / Redmi Note 9 Pro Max - miatoll? … but I see joyeuse on your recovery image.
Do you see any mention of joyeuse / miatoll in the logs?
Could you help me with what to type in the cmd on my PC to copy the log files?
Btw I have no idea what is this joyeuse stuff. I always downloaded the miatoll .iso for my phone.
To read the most recent log indicated in your image you would type
adb pull /cache/recovery/last_log
I am mystified how the recovery appears to indicate joyeuse as the 'kmsg` is shown in your image perhaps try also
adb pull /cache/recovery/last_kmsg
The logs will appear in your working directory. Having collected both the above is the first file named recovery.log?
If not, I would be inclined next to type
adb pull /tmp/recovery.log
just in case this revealed anything else (but probably a copy).
Was the update from the System Updater or a manual update / upgrade? Please can you try to identify the before and after builds (as found here /e/OS community miatoll download) using the format
e-3.7-a15-20260411607092-community-miatoll.
One can check back, for instance, to [UnOfficial Build] Q & R | Xiaomi Redmi Note 9 series | MIATOLL (curtana, joyeuse, excalibur, gram) to see a clue to the relationship between miatoll and joyeuse maybe the relationship if further explained by this fragment from your recovery.log
[ 0.373486] ro.bootimage.build.fingerprint=Redmi/joyeuse_global/joyeuse:12/RKQ1.211019.001/V14.0.3.0.SJZMIXM:user/release-keys
[ 0.373560] ro.odm.build.date=Sat Mar 14 07:40:03 UTC 2026
[ 0.373578] ro.odm.build.date.utc=1773474003
[ 0.373598] ro.odm.build.version.incremental=1773474003
[ 0.373611] ro.odm.build.fingerprint=Redmi/joyeuse_global/joyeuse:12/RKQ1.211019.001/V14.0.3.0.SJZMIXM:user/release-keys
[ 0.373622] ro.product.odm.name=lineage_miatoll
[ 0.373633] ro.product.odm.brand=Redmi
[ 0.373643] ro.product.odm.model=Redmi Note 9 Pro
[ 0.373654] ro.product.odm.device=joyeuse
[ 0.373665] ro.product.odm.manufacturer=Xiaomi
[ 0.373675] ro.product.odm_dlkm.brand=Redmi
[ 0.373686] ro.product.odm_dlkm.model=Redmi Note 9 Pro
[ 0.373697] ro.product.odm_dlkm.device=joyeuse
[ 0.373708] ro.odm_dlkm.build.fingerprint=Redmi/joyeuse_global/joyeuse:12/RKQ1.211019.001/V14.0.3.0.SJZMIXM:user/release-keys
It would take someone who knows the device to comment further, but perhaps, with apologies, this is not really a part of your fail.
More background 
Search miatioll + joyeuse
One cause of sudden death can be full storage. Any chance you recently had a warning of “storage getting full”?
In case that it would be of any help for debugging (comparing logs etc), I still have a decommissioned miatoll phone (redmi note 9s) wit 3.7 installed.
I am sorry to hear that recovery of the phone has not been possible by update. Long logs just don’t work pasted to the forum as your whole thread is now almost unreadable 
At a minimum short logs should be as “Preformatted text” otherwise they are difficult to copy. Longer logs should be added by a link to a pastebin service for instance https://paste.tchncs.de/.
this bootloop started after a simple restart.
were you close the the phones storage space constraints?
Not at all. At least half of the storage was still free.
Thank you for reformatting your logs.
There is this (already mentioned)
[ 0.247394] [libfs_mgr] Invalid f2fs superblock on '/dev/block/bootdevice/by-name/userdata'
I am sorry that I cannot read a cause and effect from your log. This however seems significant
[ 0.058351] I:[libfstab] dt_fstab: Skip disabled entry for partition vendor
[ 0.061140] I:Boot command: boot-recovery
[ 0.061205] I:Got 3 arguments from boot message /system/bin/recovery, --prompt_and_wipe_data, --reason=init_user0_failed
[ 0.061419] I:[libfstab] dt_fstab: Skip disabled entry for partition vendor
[ 0.064086] I:Writing BCB boot-recovery recovery
[ 0.064095] --prompt_and_wipe_data
[ 0.064100] --reason=init_user0_failed
But we are not really looking for a build error, because you say that the phone was running fine since the last update.
After any possible
the best I can suggest is a clean reinstall with Format data and hope that the issue was not caused by some hardware fault.
This topic was automatically closed after 60 days. New replies are no longer allowed.