Flash at your own Risk !!!
Flash gsi roms
You tell me
How to Flash:
1. Reboot Device to Downloadmode
2. Unlock Bootloader
3. Install adb and Fastboot driver and Device Drivers ( Google will Help )
4. Download the VBMeta-disabled.tar and the twrpa22v3.tar from Attachments
5. Download Odin3 from Attachments and start Odin on PC
6. In Odin Press on Options and untick Auto Reboot
7. Flash VBMeta-disabled.tar with Odin ( In Odin click on AP - select the vbmeta-disabled.tar and press start )
8. After flash vbmeta without errors press on AP and select twrpa22v3.tar and press on start
9. If all is Flashed without errors longpress power and vol- on device
10. instantly after device goes Blackscreen press and hold power and vol+ for 5-8 seconds to boot to TWRP
11. In TWRP press on Advanced - than on Terminal - and write " multidisabler " and press on the blue button
12. repeat step 11
13. press on reboot - than on recovery
How to flash gsi:
Use the google platform tools adb/fastboot Download from Attachments
Boot to TWRP
1. In TWRP press Wipe-Advanced Wipe- select Dalvik, data, cache, metadata and swipe to wipe
2. After wipe go back to main screen and press Reboot- than press Fastboot
3. Device reboots to TWRP with Fastboot Interface
4. now plugin Device to PC open platform tools and execute cmd-here.exe
5. Type : fastboot devices - if no output check your Drivers/Usb connection
6. If device is Found by "fastboot devices" command enter " fastboot flash system PATHTOYOURGSI.img"
maybe it writes :Invalid sparse file format at header magic - but this can be ignored
After flash completed without errors type : fastboot reboot and press enter
GSI Download (Tested and bootable ) :
Only Arm64-BGZ Variants are bootable
( BTW gsi imgs with .xz File Format must be extracted ! Don't simple rename it to .img )
CrDroid 11 (Face-unlock and Fingerprint works)
afaneh92 For the a32x Devicetree
View attachment 5409225View attachment 5409227View attachment 5409229
Device Tree base used : https://github.com/mohammad92/android_device_samsung_a32x
Kernelbase is same as my custom Kernel: https://forum.xda-developers.com/t/root-galaxy-a22-sm-a255f--android-11.4329471/
Fastboot doesn't work because Samsung phones don't have fastboot mode, but it does have Download mode.I as wondering how you guys have unlocked bootloader? I have (my friend's) a22 5g and I just can't find a way to do this. I had tried various methods from google, but it just doesn't show up in developer options. I've read that on MediaTek I could do this with fastboot, but when I open fastboot, it says "Entering fastboot mode..." and on pc it doesn't see my device with "fastboot devices". I tried various drivers, but none of them is working with this phone. And one of them I coudn't even try, because it wasn't signed and I'm to lazy to reboot windows with disabled drivers signing.
I have still a problem. After flashing non-carrier rom, carrier bloatware and logo and everything is still present.Fastboot doesn't work because Samsung phones don't have fastboot mode, but it does have Download mode.
Are you sure there's nothing in developer options with "OEM Unlock"?
Edit: If OEM Unlocking is not visible in the developer options, it's possible the bootloader is completely locked down or already unlocked.
But have you unlocked the bootloader? You gave no sign that you were able to. Assuming you were, flash the empty VBMeta provided to disable verifiedboot, reboot (will reboot to recovery and ask to factory reset and restart a few times), back to Odin mode, flash a tar file with a patched Magisk boot image (if you have one) and reboot. Now just install the debloat module and remove them through the terminal.
No, it's definitely locked. There was "oem lock: on" in download modeBut have you unlocked the bootloader? You gave no sign that you were able to. Assuming you were, flash the empty VBMeta provided to disable verifiedboot, reboot (will reboot to recovery and ask to factory reset and restart a few times), back to Odin mode, flash a tar file with a patched Magisk boot image (if you have one) and reboot. Now just install the debloat module and remove them through the terminal.
If you haven't unlocked the bootloader yet, I really don't know what to do. Give it a try to see if it was already pre-unlocked.
There are carriers which completey lock down the bootloader on their phones, AT&T for instance. I have an S4 from AT&T that I still use and gets custom rom updates because of a bootloader exploit that was mercifully found. Doubt something like that exists for another phone.
https://android.googlesource.com/platform/external/avb/+/master/README.md this is documentation about vbmetaHi there, I'm a noob regarding to this, but I was able to follow this guide successfully for my A225m.
But I'd like to understand what's going on here, can you give an explanation about each step and what does it do?
Also, can the vbmeta flashing be done _without_ Odin? For example using only fastboot (which works on Linux unlike Odin).