Patched Magisk v23 for Galaxy A21s (A11/OneUI 3)

Search This thread

cater2

Senior Member
Aug 4, 2021
82
23
Samsung Galaxy M12
I unrooted my device bro :(, because after rooting my device, the device was lagging badly sometimes the system ui was getting forced stop automatically, and the main reason i unrooted was that, my banking apps was not running because the magisk was showing safety net failed, I did every thing possible to correct it but it always got failed. And finally my knox got tripped :(.
It's weird because to burn knox only if you installed another unofficial rom from Samsung.... Well, it could be bug. ..

anyway thank you

install Knox Status app from Play Store, and see the status of your Knox. The app is from a guy from xda forum
 

Attachments

  • Screenshot_20211009-001155_One UI Home.jpg
    Screenshot_20211009-001155_One UI Home.jpg
    38.8 KB · Views: 22

sahil_bhandari

Senior Member
Aug 14, 2021
157
14
20
Bombay
www.youtube.com
It's weird because to burn knox only if you installed another unofficial rom from Samsung.... Well, it could be bug. ..

anyway thank you

install Knox Status app from Play Store, and see the status of your Knox. The app is from a guy from xda forum
See the attached picture :(, also same in side Bootloader, any way to make it 0x0 because i can not use applications of samsung like samsung pay and health
 

Attachments

  • fe197c64-e968-48fc-a690-9976e46afcec.jpg
    fe197c64-e968-48fc-a690-9976e46afcec.jpg
    36.4 KB · Views: 25

cater2

Senior Member
Aug 4, 2021
82
23
Samsung Galaxy M12
As far as I 've read , there 's no way to go back : ( .

In the topic here about official Magisk , if I 'm not mistaken , they were arguing about it ... <---my mistake here

I 'm on my cell phone , if I find it again I put the link ....
Through adverse, we learned a lesson, that of not going soon to do the procedure, especially if there are not many tests.

Look for ways to cheat Samsung Pay with broken knox
 
Last edited:

sahil_bhandari

Senior Member
Aug 14, 2021
157
14
20
Bombay
www.youtube.com
As far as I 've read , there 's no way to go back : ( .

In the topic here about official Magisk , if I 'm not mistaken , they were arguing about it ... <---my mistake here

I 'm on my cell phone , if I find it again I put the link ....
Through adverse, we learned a lesson, that of not going soon to do the procedure, especially if there are not many tests.

Look for ways to cheat Samsung Pay with broken knox
:( Btw you are nice bro
 

cater2

Senior Member
Aug 4, 2021
82
23
Samsung Galaxy M12
:( Btw you are nice bro
On the other hand, Samsung apps are cool, but there are many cool non-Samsung apps, paid or not, like Samsung's that are also cool.

You can also now , if you like , use any rom on your cell phone . You are now free to do that... but think carefully about what you are going to do to not make your phone a paperweight

good luck on your way :)
 
  • Like
Reactions: sahil_bhandari

sahil_bhandari

Senior Member
Aug 14, 2021
157
14
20
Bombay
www.youtube.com

Patched Magisk v23 for A21s (A11/OneUI 3)​


Since I've seen and tried installing Magisk via the default instructions from the legend topjohnwu himself, I noticed it does not work at all. The phone
just doesn't even boot into Android at all, and after researching I have seen that this is a very specific problem with the phone itself due to weird implementation from Samsung.
Extremely simplified, apparently there is a conflict with skip-initramfs because of System-as-Root and the A/B system partitioning introduced with Project Treble. I will still have to read more into it.

There are already patched Magisk apps/images for this phone available, but I noticed they are not really in active development (last patched Magisk was still v22), so I pulled the latest Magisk from the official repository and implemented the fix from this pull request on the official repo. They are not interested in accepting the pull request, so we'll have to do our own "Magisk" for the time being.

I will try to update this as much as possible and try to incorporate fixes, user feedback and more. This has been only tested on latest A11 and OneUI 3. I will also start working on TWRP soon.

Since the APK isn't signed yet, please uninstall Magisk Manager if present, and install this one. It will display a warning when installing, but don't worry.

Options to install:
  • Flash boot.tar from the ZIP in Odin on AP
  • Install the APK from this thread and patch your own boot image
Sir please can you teach Me how to modify the app from source code because when I am trying to do so there are numerous errors which I can't solve sir if you teach me it will be highly appreciated thank you
 

Top Liked Posts

  • There are no posts matching your filters.
  • 3

    Patched Magisk v23 for A21s (A11/OneUI 3)​


    Since I've seen and tried installing Magisk via the default instructions from the legend topjohnwu himself, I noticed it does not work at all. The phone
    just doesn't even boot into Android at all, and after researching I have seen that this is a very specific problem with the phone itself due to weird implementation from Samsung.
    Extremely simplified, apparently there is a conflict with skip-initramfs because of System-as-Root and the A/B system partitioning introduced with Project Treble. I will still have to read more into it.

    There are already patched Magisk apps/images for this phone available, but I noticed they are not really in active development (last patched Magisk was still v22), so I pulled the latest Magisk from the official repository and implemented the fix from this pull request on the official repo. They are not interested in accepting the pull request, so we'll have to do our own "Magisk" for the time being.

    I will try to update this as much as possible and try to incorporate fixes, user feedback and more. This has been only tested on latest A11 and OneUI 3. I will also start working on TWRP soon.

    Since the APK isn't signed yet, please uninstall Magisk Manager if present, and install this one. It will display a warning when installing, but don't worry.

    Options to install:
    • Flash boot.tar from the ZIP in Odin on AP
    • Install the APK from this thread and patch your own boot image
    2
    magisk app-debug.apk working, but boot.img from
    Model Number : SM-A217M
    Region Code : COB
    Device Version info :->>
    BL version : A217MUBS5CUE2
    AP version : A217MUBS5CUE2
    1
    Flashing this patched_magisk_v23\boot.tar ain't working.

    Error displayed on the DL screen:
    Only official released binaries are allowed to be flashed (BOOT)


    My specs:
    Loading ADB module.............OK
    Starting ADB module...OK
    Searching for SAMSUNG ADB device...OK
    Checking device authorization...OK
    Reading ADB device information...
    ADB Serial Number : R58R52BFNKP
    Model Name : SM-A217F
    Device CodeName : A21S
    Hardware : EXYNOS850 EXYNOS850
    Modem Board : SHANNON318
    HW Version : MP 0.500
    BL version : A217FXXU5CUD6
    AP version : A217FXXU5CUD6
    CP version : A217FXXU5CUD4,A217FXXU5CUD4
    CSC version : A217FOXM5CUD6
    Android version : 11
    Build date : Thu Apr 29 11:41:41 +07 2021
    Country : Poland
    IMEI : 35xxxxxxxx691
    Serial Number : N/A
    Carrier : XEO
    Unlock by IMEI : Unknown
    SIM State : ABSENT,ABSENT
    Debug Level : 0x4f4c
    CP Debug Level : N/A
    Warranty VOID : 1
    SIM operator : N/A
    USB Settings : MTP,ADB

    SamKEY Team (2017)
    1
    Installed app-debug.apk (patched Magisk) onto the phone.

    Downloaded original XEO firmware.
    Samfw.com_SM-A217F_XEO_A217FXXU5CUD6_fac.zip

    Unzipped it.
    Found AP file inside unzipped folder:
    AP_A217FXXU5CUD6_CL21209953_QB39896814_REV00_user_low_ship_MULTI_CERT_meta_RKEY_OS11.tar.md5

    Unpacked the AP file.
    Contents:
    Screenshot 2021-06-12 at 14.24.57.png

    Decoded the boot.img.lz4 file using LZ4 tool:
    Screenshot 2021-06-12 at 15.01.30.png



    Copied boot.img file to the phone internal memory.
    Screenshot 2021-06-12 at 15.03.30.png


    Opened Magisk and patched the boot.img file, which created magisk_patched-23001_nmETW.img in the phone Downloads folder

    Screenshot 2021-06-12 at 15.26.30.png
    Screenshot 2021-06-12 at 15.27.00.png


    Copied patched file (magisk_patched-23001_nmETW.img) from the phone to my laptop - and changed its name to boot.img
    Compressed it into boot.tar file using 7zip.

    Screenshot 2021-06-12 at 15.18.58.png



    Restarted the phone into DOWNLOAD mode (using SamKey, or adb, or key combinantion, whatever).

    Put boot.tar into AP section in ODIN.
    Go to Options tab and disable "Auto Reboot", make sure "Re-Partition" is also disabled.

    Screenshot 2021-06-12 at 15.20.00.png



    Aaand it fails again.
    Screenshot 2021-06-12 at 15.24.44.png


    And the message in phone DL mode says:
    Only official released binaries are allowed to be flashed(boot)
    IMG_20210612_153512.png


    Perhaps vsmeta.img also needs to be included into the tar file?
    No idea how to move on with this subject.
    1
    I have the SM-A215U. I get the impression this method won't work for me.
    I have Developers Options, but do NOT have the OEM option in that menu.
    Is there anyway to unlock it without that menu item?