UPDATE
Flash at your own Risk !!!
Tested Working:
Backup
Flash zip
Fastbootd support
Flash gsi roms
Not Working:
Usb Otg
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)
android 12
Bliss 11
caos11
Credits:
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/
Greetings.
First place, thanks for this how to. I was looking for something like it for my A225M/DS.
But there are some steps, at the first part, that are misleading people to go chasing its own tail.... The part where it says to first download the vbmeta to the device and right after, download the twrp file using the same AP button.
Since you had mentioned the author of the original thread
afaneh92, i decided to take a look at his post and i had find out the following...
As written by him on his "how to" for A32x, as follow ...
"
3. Put the TWRP TAR for your device with Odin in the AP slot,
vbmeta_disabled_R.tar in USERDATA slot and click start.
4. Reboot to recovery via recovery key combo (Vol up + power + USB connected).
5. Disable encryption:
- Go to Advanced > Terminal, type: multidisabler.
If vendor complain about free space left on device, will attempt to resize vendor. and it ask to - Run multidisabler again!.
- Type: multidisabler again. will see - Finished. when done.
- Go back to Wipe > Format Data > type yes.
- Reboot to recovery.
6. Flash magisk apk in twrp.
7. Reboot to system, Enjoy.
"
He says to put the TWRP.tar file in the AP slot and the vbmeta_disable.tar in USERDATA slot, not to put twrp and then vbmeta one after the other using AP. That's why people here, including me, gone confused. I tried lots of times and did it using a diferent way but it did not worked as expected.
Please, I am not trying to create a confusion here with you or with anybody, but I believe you could have checked that before.... I am not a developer nor a wizard with the mighty knowledge, far from it. I am a single user here, trying to put some life on my device.
The other part, worked fine, the part to flash the other firmware into the device using fastboot. About it, If anyone had a problem trying to use fastboot on windows due to the device does not recognizes on windows, i suggest to use 7zip and extract the samsung usb drivers to a separated folder, then go to the Windows Device Manager and check for the A225F device with a Yellow exclamation. If that appears, then people should right click on the A225F device on the list, choose Driver Update and go to the update option... then choose "I want to search on my computer" and right after click on With Disk option. Then go to the folder where you had extracted the drivers and look for a folder called 25_escape. Inside there are all the drivers.inf files. click on open folder and when the devices lists appears, choose the Samsung ADB option and then click update. Windows will complait about those not signed stuff, just ignore and click ok. Driver and Device uptaded and connected.
Now you can perform the fastboot devices command and it will show your device there... and just continue the procedures as described.
I once again say... I am not here to cause any kind of harm.. Just writting what I had found.
By the way, I had installed the "caos-v316-220321-arm64-bvZ-lite.img" on my A225M and it worked fine up to this moment. I had not tested the digital finger stuff, but the system is working good on my wireless.. I will post a print screen of it here... when I have finished to test it and will test the others firmware here too, to check which one will fit better for the A225M.
And thank you once again,
Cheese-ass, for your work too!
Peace!