Development [RECOVERY][UNOFFICIAL] TWRP for Galaxy A22 SM-a225F/a225M Android 11+12

[ljgjm]

Probably not, and also not worth the risk.

ok

 

[Team619]

Can we install Android 13 custom rom on Samsung A22 4g?

 

[Platypus Enthusiast]

Can we install Android 13 custom rom on Samsung A22 4g?

No. I don't even think there are any custom roms for the 4G, yet. The best you can do is a GSI.

 

[Cheese-ass]

Can we install Android 13 custom rom on Samsung A22 4g?

I booted sparkos 13 succesfully

 

[CarlebAstra]

Hello i have a Samsung A225FXXU3AVB1 with a carrier lock that I was able to bypass but it still has kg active and i can't unlock the bootloader due to carrier lock any help i will attach the pictures

 

[fy.fy117]

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 on Android 11

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 on Android 12

1. Reboot Device to Downloadmode
2. Unlock Bootloader
3. Install adb and Fastboot driver and Device Drivers ( Google will Help )
4. Download the magisk patched.tar and the twrp12.1_a225f-A12.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 magisk patched.tar with Odin ( In Odin click on AP - select the magisk patched.tar and press start )
8. After flash magisk patched.tar without errors press on try to reboot download -device reboots to dl mode
9. Flash twrp12.1_a225f-A12.tar with Odin ( In Odin click on AP - select the twrp12.1_a225f-A12.tar and press start )
10. If all is Flashed without errors longpress power and vol- on device
11. instantly after device goes Blackscreen press and hold power and vol+ for 5-8 seconds to boot to TWRP
12. In TWRP press on Advanced - than on Terminal - and write " multidisabler " and press on the blue button
13. repeat step 12
14. 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 5409229KI
Device Tree base used : https://github.com/mohammad92/android_device_samsung_a32x

A22 4g A11 Tree :https://github.com/deader89/galaxy-A22-4g-twrp-Tree
A22 4g A12 Tree :https://github.com/deader89/a22_TWRP12.1_tree.gi in android 12 there is no need to flash vbmeta disabled?

 

[ryukense]

There are three problems with crdroid, the dual card manager cannot work quickly, the hotspot cannot be used, and the system cannot mount the phone storage

I did the same process as you, but it's been a while and it's still on the crDroid logo. does it take that long or do I need to do a reset before booting? I'm thinking it's bootloop

 

[PaulinoBaslio]

I'm on A13, does the A12 process also work??

 

[physwizz]

I'm on A13, does the A12 process also work??

Yes

 

[Muslim for Allah]

Alslamalikom (Peace be upon you) .. I hope you are well.... I had the same problem, in samsung a22 4g after updating Android 13, it only turned on the Samsung logo, then it restart.. Bootloop


I just subscribed.. to warn you so that no one will make same mistake .. My storage size is 128 GB and it is full of family personal and for me, and it was not possible to format it so as not to lose it.. Also, the mobile was under warranty, and I did not want to go to the agency, because they would say format or they would be able to open it, and it contains special family things


So I used Odin and the ROM version a225fxxu3cvk3 and another object such as bootloader and others, and the download began, and all my hope is to open The device does not delete anything


Thank Allah , in any case, the device was opened, but an automatic format was made for the device and everything was lost as if it was new... So I liked that no one did and lost his data as me🥹


And as kind member here called (nanawa) said, try when an update comes out, not the same ROM or Older than on the mobile phone


But everyone who installs the ROM is at her/his own risk


I will put it here and 2 another topics related to the problem and i will leave

Best wishes,, alslamalikom

 

[Xenonionite]

I tried flashing project elixir 3.5 gsi on my a22 4g in twrp and I got the error message "file size is bigger than target device" so would it boot if I used adb instead. And treble info says the bootable gsi are arm64 ab so is that wrong