General TWRP and Magisk prepatched boot for A22 5g Blind Build EXPERIMENTAL

Search This thread

Cheese-ass

Member
Jun 11, 2017
22
45
First of All i dont own this device !!!! so i cant test by myself
Twrp is based on A22 4g and modified for A22 5g


if someone is brave enough to test it please pm me
for flash instructions - Look Here

Boot.img/Recovery.img is from A226BXXU1AUEH Firmware

To Root your device try magisk prepatched boot.img (magiskboot.tar)

TWRP didnt work so i deleted it
 

Attachments

  • stockrecovery.tar
    40 MB · Views: 228
  • stockboot.tar
    32 MB · Views: 185
  • magiskboot.tar
    32 MB · Views: 264
Last edited:

jtownsle

Member
Jan 21, 2012
20
3
Indianapolis
This isn't working for my SM-A226B. It works through step #9 (flash vbmeta & twrpa22, then restart)--ie, flash indicates 'pass' for both. But at step #10, vol+ and power, my phone never goes into TWRP. I've tried several versions of the twrp file, various combinations of having the USB plugged in while I do it, holding for different lengths of time, etc. It just gets stuck in the Samsung logo boot loop. I can't even turn it off with vol- and power. The only response I can get is moving it to download mode with vol+,vol-,usb. The phone is fully charged.
 
  • Like
Reactions: Platypus Enthusiast

LucianGL30

Senior Member
Nov 30, 2010
51
14
Screenshot_20211204-141508_Root Checker Basic.jpg


rooted thru magisk method, not this one posted. also call recording by default activated and screen record enabled.
 

Attachments

  • Screenshot_20211204-162306_Settings.jpg
    Screenshot_20211204-162306_Settings.jpg
    301.9 KB · Views: 118
  • Screenshot_20211204-162340_Call settings.jpg
    Screenshot_20211204-162340_Call settings.jpg
    97.9 KB · Views: 105
  • Screenshot_20211204-162336_Call settings.jpg
    Screenshot_20211204-162336_Call settings.jpg
    206.8 KB · Views: 98
Last edited:
  • Like
Reactions: AlexTECPlayz

frankieuk

Member
May 13, 2016
43
7
Made the root img for you all, odin place it in AB, anyone need help just msg.
 

Attachments

  • magisk_patched-23000_gFm20.tar
    32 MB · Views: 114

Platypus Enthusiast

Senior Member
Apr 6, 2021
77
18
I tried the TWRP and VBMeta tar, it just got into a bootloop like another guy. I tried flashing the Magisk tar, didn't work, so I tried using my own boot image from the stock rom, didn't work either.
 

Marcio.RS

Member
Apr 18, 2013
17
2
This isn't working for my SM-A226B. It works through step #9 (flash vbmeta & twrpa22, then restart)--ie, flash indicates 'pass' for both. But at step #10, vol+ and power, my phone never goes into TWRP. I've tried several versions of the twrp file, various combinations of having the USB plugged in while I do it, holding for different lengths of time, etc. It just gets stuck in the Samsung logo boot loop. I can't even turn it off with vol- and power. The only response I can get is moving it to download mode with vol+,vol-,usb. The phone is fully charged.
Greetings.

I had tried this twrp+vbmeta stuff. I got stucked on it too, because there is no way to go to recovery mode as described in the list.

What I did and that worked for me on my A225M/DSN was downloading fisrt the vbmeta file, without autoreboot, then, gone to power+vol down(-) untill it reboot and gone to download mode again and downloaded the twrp file to the device. When it got finished to download with success, i went to power+vol down(-) again and went into recovery mode and did the rest of the list as written there.... At list it worked this way for me.

I hope I had helped with this...
 

Marcio.RS

Member
Apr 18, 2013
17
2
I tried the TWRP and VBMeta tar, it just got into a bootloop like another guy. I tried flashing the Magisk tar, didn't work, so I tried using my own boot image from the stock rom, didn't work either.
I tried this method too, but in my case, when I connected it to my computer, it showed as a A225F instead of A225M/DSN, so I had undone all, flashed the stock rom back, locked the bootloader and restored it to original form.
After that, I had found a post on the internet, showing how to patch Magisk on the AP file from the stock firmware, and I did it. Now my A225M/DSN is rooted with no problem.

About twrp, there is no official from teamwin and that one I had found here, is kinda bugged.

I Tried using the twrp+vbmeta from here to the A225F but no lucky. If there were a way to find a twrp that worked for the A225M/DSN, it would be nice, so I could use another firmware flavor... but... I can only wait and see...
 

lebigmac

Senior Member
Jan 31, 2017
1,072
706
Hi. I tried flashing the twrp.img from first post of this thread to the recovery partition but unfortunately my phone ended up in a very slow, very tricky, annoying and very dark bootloop. Almost as dark as the black hole in the milky way galaxy. The sort of bootloop you don't want to find your device in. Xiaomi bootloops are so much easier to get out of let me tell you! Especially since they ship with a fully working , non-crippled fastboot! Ain't that right @samsung? :ROFLMAO:

Here's the log:
heimdall flash --recovery ./recovery.img --no-reboot
Heimdall v1.4.1

Copyright (c) 2010-2014 Benjamin Dobell, Glass Echidna

This software is provided free of charge. Copying and redistribution is
encouraged.

If you appreciate this software and you would like to support future
development please consider donating:

Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...

Initialising protocol...
Protocol initialisation successful.

Beginning session...

Some devices may take up to 2 minutes to respond.
Please be patient!

Session begun.

Downloading device's PIT file...
PIT file download successful.

Uploading recovery
100%
recovery upload successful

Ending session...
Releasing device interface...

After hours upon hours of trying in vain I somehow managed to get the Galaxy device to boot into Download mode :D(y) (don't ask me how - it just happened)

Then I tried to flash the stock recovery.img from first post of this thread and it gave me this result:
Thank god phone is still in Odin mode :D

heimdall flash --recovery ./recovery.img
Heimdall v1.4.1

Copyright (c) 2010-2014 Benjamin Dobell, Glass Echidna

This software is provided free of charge. Copying and redistribution is
encouraged.

If you appreciate this software and you would like to support future
development please consider donating:

Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...

Initialising protocol...
Protocol initialisation successful.

Beginning session...

Some devices may take up to 2 minutes to respond.
Please be patient!

Session begun.

Downloading device's PIT file...
PIT file download successful.

Uploading recovery
100%
recovery upload successful

Ending session...
ERROR: Failed to receive session end confirmation!
Releasing device interface...

And on phone itself it give this error:
SW REV CHECK FAIL : [recovery]
Fused 4 > Binary 1
RP check error : recovery

EDIT: problem solved :D(y)
 
Last edited:

Platypus Enthusiast

Senior Member
Apr 6, 2021
77
18
Hi. I tried flashing the twrp.img from first post of this thread to the recovery partition but unfortunately my phone ended up in a very slow, very tricky, annoying and very dark bootloop. Almost as dark as the black hole in the milky way galaxy. The sort of bootloop you don't want to find your device in. Xiaomi bootloops are so much easier to get out of let me tell you! Especially since they ship with a fully working , non-crippled fastboot! Ain't that right @samsung? :ROFLMAO:

Here's the log:
heimdall flash --recovery ./recovery.img --no-reboot
Heimdall v1.4.1

Copyright (c) 2010-2014 Benjamin Dobell, Glass Echidna

This software is provided free of charge. Copying and redistribution is
encouraged.

If you appreciate this software and you would like to support future
development please consider donating:

Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...

Initialising protocol...
Protocol initialisation successful.

Beginning session...

Some devices may take up to 2 minutes to respond.
Please be patient!

Session begun.

Downloading device's PIT file...
PIT file download successful.

Uploading recovery
100%
recovery upload successful

Ending session...
Releasing device interface...

After hours upon hours of trying in vain I somehow managed to get the Galaxy device to boot into Download mode :D(y) (don't ask me how - it just happened)

Then I tried to flash the stock recovery.img from first post of this thread and it gave me this result:
Thank god phone is still in Odin mode :D

heimdall flash --recovery ./recovery.img
Heimdall v1.4.1

Copyright (c) 2010-2014 Benjamin Dobell, Glass Echidna

This software is provided free of charge. Copying and redistribution is
encouraged.

If you appreciate this software and you would like to support future
development please consider donating:

Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...

Initialising protocol...
Protocol initialisation successful.

Beginning session...

Some devices may take up to 2 minutes to respond.
Please be patient!

Session begun.

Downloading device's PIT file...
PIT file download successful.

Uploading recovery
100%
recovery upload successful

Ending session...
ERROR: Failed to receive session end confirmation!
Releasing device interface...

And on phone itself it give this error:


All these different Samsung firmware websites only offer slow download speed 300 KB/s max. and I don't got premium account!
And whole firmware is 5GB that means I must wait 6 hours +
Should I keep the phone in download mode until then? Then I must leave it plugged in because screen will drain battery fast. I guarantee you that I will never ever be able to get it back into download mode again if I turn it off now. Can I even turn it off?! Nope. I can force reboot with vol down + power (hold for 10 seconds) but there is no key combo for force power off or shutdown 😒

Can someone reading this please upload only the stock recovery of their Samsung Galaxy A22 5G (SM-A226B)? Or upload only the official file that the stock recovery is contained in such as one of those AP, CP or CSC files.
Thank you very much!
I think the firmware my device was running was Android 11 and February 2022 security patch or something. That shouldn't really matter as long as it's stock Android 11.
Maybe it's somehow possible to fix this annoying bootloop without having to download the full 5 GB of the firmware. I only overwrote the recovery partition.

I think next time I will flash using Odin like everyone else and I'll leave Heimdall to the real pro's :D
Does anyone know how to flash only recovery with Odin? Do I flash the AP, CP or CSC file? I guess not the BL that sounds like BOOTLOADER!
Thanks (y)

Now I am very confident that soon I will finally be able to get this phone out of this mess and back up and running! :D(y)
Sorry you didn't get help immediately, I don't check my emails often unless I want a verification code from some website.

I also screwed up my A226B (different cause), I deleted an old copy of firmware files because they were outdated, so I went to Sammobile for a different one, spent 4 hours downloading an archive that turned out to be corrupted. It was already 1 AM at that point so I went to bed. The next day, I tried downloading it again, thinking my slow internet at the time corrupted the download, waited another 4 hours, but same result. I decided to take a risk and try out those sketchy websites. I tried out samfw.com and it worked good, so you might want to try that.

About which files to flash, flash BL, AP, CSC, and CP to do a restore. HOME_CSC is if you want to keep your files, CSC if you want to start out fresh.

Edit: BL is bootloader, CP is the modem, CSC is the region specific features, and AP is the main file. Usually flashing AP will make your phone work again, but you won't be able to get software updates unless you flash the others. Also samfw downloads pretty fast.
 
Last edited:
  • Like
Reactions: lebigmac

lebigmac

Senior Member
Jan 31, 2017
1,072
706
Thanks for the quick reply. (y)
I finally got the phone back up and running by flashing the full firmware with Odin.
Thank god this nightmare is now finally over. What's the best way to root this thing without bricking your device? Thanks (y)
 

physwizz

Senior Member
Sep 16, 2013
3,484
755
Sydney
Thanks for the quick reply. (y)
I finally got the phone back up and running by flashing the full firmware with Odin.
Thank god this nightmare is now finally over. What's the best way to root this thing without bricking your device? Thanks (y)
Recovering from a brick is all part of the samsung learning experience
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    First of All i dont own this device !!!! so i cant test by myself
    Twrp is based on A22 4g and modified for A22 5g


    if someone is brave enough to test it please pm me
    for flash instructions - Look Here

    Boot.img/Recovery.img is from A226BXXU1AUEH Firmware

    To Root your device try magisk prepatched boot.img (magiskboot.tar)

    TWRP didnt work so i deleted it
    1
    This isn't working for my SM-A226B. It works through step #9 (flash vbmeta & twrpa22, then restart)--ie, flash indicates 'pass' for both. But at step #10, vol+ and power, my phone never goes into TWRP. I've tried several versions of the twrp file, various combinations of having the USB plugged in while I do it, holding for different lengths of time, etc. It just gets stuck in the Samsung logo boot loop. I can't even turn it off with vol- and power. The only response I can get is moving it to download mode with vol+,vol-,usb. The phone is fully charged.
    1
    Root works for me, just attached the magiskboot to odin AP, not im rooted!, not bothered about twrp but thanks.
    1
    Screenshot_20211204-141508_Root Checker Basic.jpg


    rooted thru magisk method, not this one posted. also call recording by default activated and screen record enabled.
    1
    Hi. I tried flashing the twrp.img from first post of this thread to the recovery partition but unfortunately my phone ended up in a very slow, very tricky, annoying and very dark bootloop. Almost as dark as the black hole in the milky way galaxy. The sort of bootloop you don't want to find your device in. Xiaomi bootloops are so much easier to get out of let me tell you! Especially since they ship with a fully working , non-crippled fastboot! Ain't that right @samsung? :ROFLMAO:

    Here's the log:
    heimdall flash --recovery ./recovery.img --no-reboot
    Heimdall v1.4.1

    Copyright (c) 2010-2014 Benjamin Dobell, Glass Echidna

    This software is provided free of charge. Copying and redistribution is
    encouraged.

    If you appreciate this software and you would like to support future
    development please consider donating:

    Initialising connection...
    Detecting device...
    Claiming interface...
    Setting up interface...

    Initialising protocol...
    Protocol initialisation successful.

    Beginning session...

    Some devices may take up to 2 minutes to respond.
    Please be patient!

    Session begun.

    Downloading device's PIT file...
    PIT file download successful.

    Uploading recovery
    100%
    recovery upload successful

    Ending session...
    Releasing device interface...

    After hours upon hours of trying in vain I somehow managed to get the Galaxy device to boot into Download mode :D(y) (don't ask me how - it just happened)

    Then I tried to flash the stock recovery.img from first post of this thread and it gave me this result:
    Thank god phone is still in Odin mode :D

    heimdall flash --recovery ./recovery.img
    Heimdall v1.4.1

    Copyright (c) 2010-2014 Benjamin Dobell, Glass Echidna

    This software is provided free of charge. Copying and redistribution is
    encouraged.

    If you appreciate this software and you would like to support future
    development please consider donating:

    Initialising connection...
    Detecting device...
    Claiming interface...
    Setting up interface...

    Initialising protocol...
    Protocol initialisation successful.

    Beginning session...

    Some devices may take up to 2 minutes to respond.
    Please be patient!

    Session begun.

    Downloading device's PIT file...
    PIT file download successful.

    Uploading recovery
    100%
    recovery upload successful

    Ending session...
    ERROR: Failed to receive session end confirmation!
    Releasing device interface...

    And on phone itself it give this error:


    All these different Samsung firmware websites only offer slow download speed 300 KB/s max. and I don't got premium account!
    And whole firmware is 5GB that means I must wait 6 hours +
    Should I keep the phone in download mode until then? Then I must leave it plugged in because screen will drain battery fast. I guarantee you that I will never ever be able to get it back into download mode again if I turn it off now. Can I even turn it off?! Nope. I can force reboot with vol down + power (hold for 10 seconds) but there is no key combo for force power off or shutdown 😒

    Can someone reading this please upload only the stock recovery of their Samsung Galaxy A22 5G (SM-A226B)? Or upload only the official file that the stock recovery is contained in such as one of those AP, CP or CSC files.
    Thank you very much!
    I think the firmware my device was running was Android 11 and February 2022 security patch or something. That shouldn't really matter as long as it's stock Android 11.
    Maybe it's somehow possible to fix this annoying bootloop without having to download the full 5 GB of the firmware. I only overwrote the recovery partition.

    I think next time I will flash using Odin like everyone else and I'll leave Heimdall to the real pro's :D
    Does anyone know how to flash only recovery with Odin? Do I flash the AP, CP or CSC file? I guess not the BL that sounds like BOOTLOADER!
    Thanks (y)

    Now I am very confident that soon I will finally be able to get this phone out of this mess and back up and running! :D(y)
    Sorry you didn't get help immediately, I don't check my emails often unless I want a verification code from some website.

    I also screwed up my A226B (different cause), I deleted an old copy of firmware files because they were outdated, so I went to Sammobile for a different one, spent 4 hours downloading an archive that turned out to be corrupted. It was already 1 AM at that point so I went to bed. The next day, I tried downloading it again, thinking my slow internet at the time corrupted the download, waited another 4 hours, but same result. I decided to take a risk and try out those sketchy websites. I tried out samfw.com and it worked good, so you might want to try that.

    About which files to flash, flash BL, AP, CSC, and CP to do a restore. HOME_CSC is if you want to keep your files, CSC if you want to start out fresh.

    Edit: BL is bootloader, CP is the modem, CSC is the region specific features, and AP is the main file. Usually flashing AP will make your phone work again, but you won't be able to get software updates unless you flash the others. Also samfw downloads pretty fast.