Basically I agree with you, but /e/OS community builds are without warranty:
It is advisable to flash your device only if you know what you are doing and are ok taking the associated risk. All /e/OS builds are provided as best effort, without any guarantee. The /e/OS project and its project members deny any and all responsibility about the consequences of using /e/OS software and or /e/OS services.
You see, I’m not asking for any guarantees. I reported these issues at least weeks ago with previous versions of the build in the recommended thread for changes in the documentation. No reaction at all, and the documentation remains the same. Even now, I’m trying to document the failure of the installation, hoping for people to find this thread before they can proceed to bootloop and potentially brick their phones.
I thank you, though. You are the first people to reply to me in all this time. Also, I appreciate the builds from the community too, but I’d expect others appreciate being warned about the failure of these builds since at least /e/ OS v2.4
I did try installing again this ROM because I found some fixes for the described message:
dm-verity encryption
Your device is corrupt.
It can't be trusted and may not work properly.
Press power button to continue.
Or, device will power off in 5s.
The fixes include:
fastboot oem cdms
Also tried:
fastboot oem cdms fix
None of this fixes work in this build. There is another one apparently run from adb. Didn’t try it, because this is time consuming, but I doubt it could work.
dm-verity verification enforcing
Hi guys… whoever remains interested in this rosemary build.
I did install the ROM, using a blank vbmeta.img. Flashed the vbmeta.img to vbmeta_a and vbmeta_b partitions, before entering recovery to flash /e/OS. The good news is that the error I shared some messages above is not in my bootsplash screen anymore, the bad news is that /e/OS still won’t boot. I’m absolutely out of ideas. Please don’t get me wrong, but I don’t think these builds should be published anymore.
I know @ronzz98 was involved in the build process at some point. Maybe they can help here.