Well done. Clearly the intention was to flash a Stock ROM [1].
Please contact me (TheAirBlow) about this in XDA DMs!
If you would cooperate, we could uncover hidden features!
Maybe this tool will have the ability to extract. Personally I would be prepared to spend some time on how to extract or repair the phone before going with the planned Stock ROM approach.
Thanks @aibd, I have made some progress. I downloaded odin4 for linux, and a complete set of firmware files. (Using odin to avoid having to unpack the many files)
First I tried a restore using HOME_CSC_... but got blocked at āYour DATA is encrypted, please enter your PINā
Next I downloaded CSC_... and have now got the phone booted back into stock Android (This is actually an improvement on last time I tried to revert to stock, when the phone wouldnāt boot into android, but I could then install /e/OS successfully)
Fortunately most of my stuff is backed up to Murena cloud, and I did a manual backup of a few other apps data in March when I did a full upgrade of /e/OS with data wipe.
Next, Installed e recovery using Heimdall, rebooted into that and installed /e/OS via adb sideload, and reboot.
Aaand finally Iām back in e/OS/. Now to restore all my apps, preferences and data that isnāt synced with Murena cloud.
Maybe a workaround for those aware of the problem would be to backup on an sd card using twrp. If the OEM locks, you would reinstall stock rom, unlock it, then reinstall TWRP and restore the backup. That way your data wonāt be lost, but you gotta do the backup before the problem occures. Or maybe you can choose to backup only the data and the system, i donāt know if the OEM state is stored into the boot partition. Otherwise it would be possible to restore system without restoring the boot partition and so the OEM state ?? I might say something dumb that could brick oneās device, so please wait for confirmation of a more experienced user.
If I understand well, there is no way to recover data?
I have actually one phone that is blocked and anotherone that I try not to reboot (not to lose data!!). What are the instructions to recover data? Can I backup without Rebooting or risk to reboot if I try to go to TWRP. And will there be an update that removes the bug?
Regarding backing up without reboot, I have written about my backup process here
Note that this doesnāt back up applications themselves, because they can be reinstalled from App Lounge or F-Droid.
Another manual approach (vs sync to murena.io) is to connect your phone to a PC in file transfer mode, and copy all your documents, photos, app settings etc to the PC.
Perhaps not perfect, but it will preserve personal files, which I assume will be the most valuable to you.
Does anyone have tested to include TWRP (or recovery-e) into āAPā and perhaps vbmeta-e into āBLā associate with a āHOME_CSCā Samsung firmware ?
Iām hesitating to wait for a solution or try to fix it now by the way you describe. If I understand well you suggest to load the āHome_cscā¦ā file and two others with Odin? I could try if I can download the right files (Iām only beginner).
Cheers
Ideally somebody who has a āspareā phone to test on could try this. Iām not willing to try on the phone I use every day, given the hours and angst I went through to get it working again!