Yes @sethdot , this alone does not give the stock-recovery the necessary option patch fastboot’D’. And without this patch, the fastboot command cannot be executed with a Samsung Galaxy: fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
1 Like
Thanks for all the info.
stevenx23x uploaded more binaries, here is the one that you were interested in, he said you can use it with lower binaries too:
vbmeta 14 Binary E
https://xdaforums.com/attachments/disable-vbmeta-b14-e-zip.6206347/
I will look for the newer phones to try it out. I successfuly patched Samsung A22 5G and Samsung A71 which were on A13 but I don’t know if that’s only because I disabled vbmeta before or not (they had TWRP).
I’m still a newbie in all of this, it will get clearer when I try it on a fresh stock phone.
Here is this one:
All credits go to stevenx23x from the xdaforums.
Yeah, many thanx to all for the support and all the information.
I will have a try next days.
Best regards.
@sethdot
Thank you for your commitment and your time 
I’m also constantly learning. I know and follow the activities of @stevenx23x on XDA forums. Did you also read this error message regarding vbmeta 14 Binary E?
So far I 've not been able to install stevenx23x’s files T(A13) - BIT-C and U(A14) - BIT-E successfully. Do you’ve a tip for me what I’m doing wrong?
I’ve seen three methods for flashing patched recovery - first one is to put disable-vbmeta.tar in AP slot in Odin, flash it and immediately enter download mode again to flash recovery from the same AP slot.
Second one is to put patched recovery in the AP and disbale-vbmeta in the userdata slot.
Third one is to bundle vbmeta image together with recovery in single tar file and to flash it AP slot.
I don’t know why there are different methods for different phones.
Also, I’m going to try to create my own vbmeta image with disabled verification from magisk. It’s mentioned in xda topic about patching recovery and I’ve seen the same method in telegram channels for various Samsung phones. You don’t have to root phone, just extract your stock vbmeta on which magisk disables verification flag.
1 Like
All right, after a lot (and I do mean A LOT) of tinkering with GSI, a little update.
As you might have seen from other topic, @sam-a managed to install GSI with patched recovery method on his Samsung Xcover Pro.
Now it’s more clear than ever how to do it because he wrote an excellent tutorial but also stevenx23x from xda regularly releses new versions of tool with more and more binaries.
In the latest version he also included tutorial on how to obtain vbmeta with disabled verification for your specific binary with magisk. It’s very simple and it works great.
So with Samsung patched recovery, I managed to install @Colors GSI on a lot of devices I never thought possible -
Samsung A02s
Samsung A03s
Samsung A04s
Samsung A12
Samsung A21s
Samsung A22 5G
Samsung A31
Samsung A32 5G
Samsung A33 5G
Samsung A41
Samsung A52 5G
Samsung A52s
Samsung A53 5G
Samsung A71
And what’s the most important thing - GSI is very stable, there are no reboots and you can use it as your daily driver.
I also installed GSI on Xiaomi and Motorola devices and it’s lot easier because there’s fastboot right away and no recovery modifications are needed.
3 Likes
Hi @sethdot,
i just hoped that my tutorial would be a solution for other Samsung-Devices,
cause i own only two devices and couldn’t test it further.
Now i’m glad to hear that it is and could be a solution for many people.
Best regards
1 Like