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

Search This thread

cater2

Senior Member
Aug 4, 2021
82
23
Samsung Galaxy M12
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?

If you dont see the OEM unlock
-Disable Auto System Update
-Then desable Automatic date and time (Found in General Management) > then set the time back 14 days
-Connect to the internet
- Go to software update then check for update and wait a long time till it registers the devices on server
- Once it's registered the OEM Unlock should be visible in the Developer Options

then connect phone to pc

Credits to Physwizz from your collection of tips on the Telegram , referring to the galaxy A02s
 
  • Like
Reactions: sahil_bhandari

dbreed53

Senior Member
Jun 13, 2013
79
11
69
Fordland, MO
Samsung Galaxy A21s
If you dont see the OEM unlock
-Disable Auto System Update
-Then desable Automatic date and time (Found in General Management) > then set the time back 14 days
-Connect to the internet
- Go to software update then check for update and wait a long time till it registers the devices on server
- Once it's registered the OEM Unlock should be visible in the Developer Options

then connect phone to pc

Credits to Physwizz from your collection of tips on the Telegram , referring to the galaxy A02s
Thank you. I will try that tomorrow.
Good Night!
 

dbreed53

Senior Member
Jun 13, 2013
79
11
69
Fordland, MO
Samsung Galaxy A21s
It didn't work.
When I select "Download and install,"
it still shows "Security patch level: August 1, 2021" and
"Current version A215USQS5AUG6."

"Last update" still says,
"The last update was installed on September 2, 2021 at 12:43."

Oh, well.
Also, when I checked for update, it didn't take any longer than it normally does, rather quick in fact. I tried going back 14 days AND one full year, same results each time.
 

cater2

Senior Member
Aug 4, 2021
82
23
Samsung Galaxy M12
It didn't work.
When I select "Download and install,"
it still shows "Security patch level: August 1, 2021" and
"Current version A215USQS5AUG6."

"Last update" still says,
"The last update was installed on September 2, 2021 at 12:43."

Oh, well.
Also, when I checked for update, it didn't take any longer than it normally does, rather quick in fact. I tried going back 14 days AND one full year, same results each time.
You can at your own risk give this link a try, but the service is paid. The A21s is not quoted but you can contact him ... Good Luck

 

cater2

Senior Member
Aug 4, 2021
82
23
Samsung Galaxy M12
It didn't work.
When I select "Download and install,"
it still shows "Security patch level: August 1, 2021" and
"Current version A215USQS5AUG6."

"Last update" still says,
"The last update was installed on September 2, 2021 at 12:43."

Oh, well.
Also, when I checked for update, it didn't take any longer than it normally does, rather quick in fact. I tried going back 14 days AND one full year, same results each time.

Or do an internet search. I found this link below , but honestly I do not know it .

 

sahil_bhandari

Senior Member
Aug 14, 2021
157
14
20
Bombay
www.youtube.com
Please , for Galaxy M12 did you use the OP tutorial or did you use some other method to root

thank
bro what is OP method ?, I took AP file and extracted the boot.img.lz and compressed it into .tar file then patched the boot.img file with modified magisk manager and took the odin and placed the boot file in AP block then i flashed it. then my mobile got rebooted and got my mobile rooted.
 
  • Like
Reactions: cater2

cater2

Senior Member
Aug 4, 2021
82
23
Samsung Galaxy M12
bro what is OP method ?, I took AP file and extracted the boot.img.lz and compressed it into .tar file then patched the boot.img file with modified magisk manager and took the odin and placed the boot file in AP block then i flashed it. then my mobile got rebooted and got my mobile rooted.
OP original poster

Have you tried this tutorial?

 

dbreed53

Senior Member
Jun 13, 2013
79
11
69
Fordland, MO
Samsung Galaxy A21s
You can at your own risk give this link a try, but the service is paid. The A21s is not quoted but you can contact him ... Good Luck

If I am reading it right, this is not a BOOTLOADER unlock issue they are working on.
It is the PHONE UNLOCK from their carrier.
 

dbreed53

Senior Member
Jun 13, 2013
79
11
69
Fordland, MO
Samsung Galaxy A21s
?? what you mean bro explain me have I did any thing wrong help me if i did....
No, you did nothing wrong. Many people mistake UNLOCK to mean the wrong type of unlock. I've done it, too
There are two kiinds;
Unlock the PHONE from the CARRIER.
AND
Unlock the BOOTLOADER.

I'm sure you know, WE are looking to UNLOCK the BOOTLOADER.
And I'm sure, in time, someone WILL figure it out.
Adios!
 

Ali70907

New member
Sep 29, 2021
1
0

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
Is this way will work for Samsung M12... It has the same processor exynos 850
 

sahil_bhandari

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

Could you please post a print of your installed magisk according to this post

thanks
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 :(.
 
  • Like
Reactions: cater2

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?