[Redmi Note 10S] florian1612:
I'm still trying to find a way to recover the data from Note 10S. I think I have found the reason, because of the bootloop problem. I was able to install TWRP on the Note 10S. So I was able to copy and read an interesting log file. I found the log file uiderrors.txt in the \cachea\mqsas\RescuePartyLog\system directory. Here are some excerpts from the log file:

06.04.23 21:07: Upgrading from Redmi/rosemary_eea/rosemary:12/SP1A.210812.016/V13.0.9.0.SKLEUXM:user/release-keys to 94bad4f019239befbc2e74c021cfae2e1d79c47c

06.04.23 21:07: Upgrading to Redmi/rosemary_eea/rosemary:13/TP1A.220624.014/V14.0.2.0.TKLEUXM:user/release-keys

.

.

.

10.08.23 21:29: No start tag found in package manager settings

10.08.23 21:29: First boot of Redmi/rosemary_eea/rosemary:13/TP1A.220624.014/V14.0.2.0.TKLEUXM:user/release-keys

.

.

.

10.08.23 21:29: Failed to create app data for com.mediatek.op09clib.telecom, but trying to recover: com.android.server.pm.Installer$InstallerException: Failed to prepare /data/user_de/0/com.mediatek.op09clib.telecom

10.08.23 21:29: Recovery succeeded!

10.08.23 21:29: Failed to create app data for com.mediatek.op01.telecom, but trying to recover: com.android.server.pm.Installer$InstallerException: Failed to prepare /data/user_de/0/com.mediatek.op01.telecom

10.08.23 21:29: Recovery succeeded!

10.08.23 21:29: Failed to create app data for com.google.android.inputmethod.latin, but trying to recover: com.android.server.pm.Installer$InstallerException: Failed to prepare /data/user_de/0/com.google.android.inputmethod.latin

10.08.23 21:29: Recovery succeeded!

10.08.23 21:30: Failed rescue level RESET_SETTINGS_UNTRUSTED_DEFAULTS: Failed to reset secure settings for 0: Attempt to invoke interface method 'android.app.ContentProviderHolder android.app.IActivityManager.getContentProvider(android.app.IApplicationThread, java.lang.String, java.lang.String, int, boolean)' on a null object reference

10.08.23 21:30: Failed rescue level RESET_SETTINGS_UNTRUSTED_CHANGES: Failed to reset secure settings for 0: Attempt to invoke interface method 'android.app.ContentProviderHolder android.app.IActivityManager.getContentProvider(android.app.IApplicationThread, java.lang.String, java.lang.String, int, boolean)' on a null object reference

10.08.23 21:31: Failed rescue level RESET_SETTINGS_TRUSTED_DEFAULTS: Failed to reset secure settings for 0: Attempt to invoke interface method 'android.app.ContentProviderHolder android.app.IActivityManager.getContentProvider(android.app.IApplicationThread, java.lang.String, java.lang.String, int, boolean)' on a null object reference

10.08.23 21:31: Finished rescue level WARM_REBOOT

10.08.23 21:32: Finished rescue level CONFIG_RESET for package null

10.08.23 21:32: Preparing to delete files: /data/system/users/0/settings_secure.xml.fallback

10.08.23 21:32: Preparing to delete files: /data/system/users/0/settings_secure.xml

10.08.23 21:32: Preparing to delete files: /data/system/users/0/app_idle_stats.xml

10.08.23 21:32: Preparing to delete files: /data/system/users/0/settings_system.xml

10.08.23 21:32: Preparing to delete files: /data/system/users/0/settings_system.xml.fallback

10.08.23 21:32: Finished rescue level FACTORY_RESET

10.08.23 21:33: Finished rescue level FACTORY_RESET

10.08.23 21:36: Finished rescue level FACTORY_RESET

10.08.23 21:39: Finished rescue level FACTORY_RESET

As I understand it, the Note 10S has been in the process of updating from V13.0.9.0.SKLEUXM to V14.0.2.0.TKLEUXM since April 6, 23, 9:07 p.m.

On August 10, 23, 9:29 p.m., version V14.0.2.0.TKLEUXM was started for the first time. The Note 10S probably restarted itself.

I mean that it was set up this way when updates are available, they should be downloaded but not installed automatically.

I didn't know what the Note 10S was doing at the time and probably interrupted the update process by restarting it at this point. Since then it doesn't start anymore.

I tried a few things. With MTK Client I was able to copy all partitions from the Note 10S to my PC (python mtk rl save)

With MTK and SPFlash I was able to re-flash the Note 10S with stock roms so that the NOTE 10S starts again. I flashed different versions and then the USERDATA Partition with MTK Client. Every time after flashing USERDATA, the Note 10S no longer started. Probably because of the inappropriate encryption etc.

I then flashed all partitions again with python mtk wl save. With the result that it is stuck in the bootloop again.

Slot a should be V14.0.2.0 and slot b should be V13.0.9.0. None of the slots are bootable.

Is it possible to restart the update process manually? There should be a script somewhere about the update process.

Or is it possible to somehow get slot b bootable again?

What's even strange is that mtk client pulled down a partition gpt_backup.bin from the Note 10S. However, if I want to write this back, this partition on the Note 10S, it says there is no partition like that so that it cannot be writed back.

Then I read something about RPMB (replay protected memory block). Will it be deleted if I format the memory with SPflash?

It would be nice if someone could send me a uiderrors.txt from a Note 10S where this update process was successful.

Thanks for reading and any help...

I'm starting to think that it's really hopeless.... :-(