Database Develop

Samsung Galaxy S4 Triband - Sph-720T - Full Domestic Unlock :)

Hi everyone, I've tried for months to find a way of getting my sph-720t unlocked for domestic use.
Pokemon came out and I had to get this phone working.
I tried a combination of two guides and got it working, credit goes to
(http://forum.xda-developers.com/showthread.php?t=2530610)
@autoprime and @nicotheandroidguy
(http://forum.xda-developers.com/galaxy-s4-sprint/general/l720-l720t-gsm-unlock-att-tm-t3189063)
nfsmww ( please donate
paypal: [email protected] )
I decided I would try to make it easier and make a guide for you guys that were having the same trouble as me.
This method is for the sprint sph-720T model, this might work on other galaxy s4s, but the links I provided are specific for the 720T model. (so if your trying this on another model, like the 720 - find your own download links, dont use the ones provided
If you are on 4.4.2 or an older version of android - you are good
if you are on a later version - please download the M919 Rom found here and flash it using Odin
1. Make sure your device is rooted. Boot to Recovery - Open Odin and select AP, then flash the autorooter found here.
3. Open Odin, select AP and flash the MK5 modem found here
4 .open super SU and click on disable knox, if it doesnt work the first time, restart the phone - should work as long as your on 4.4.2
5. install this app, run it and click unlock
3) I went to the dialer and typed *#0011# which brought me to the "service mode" Menu.
4) Hit the soft menu key (bottom left of the phone)
Hit back
hit back again
hit key input
enter capital "Q" hit enter
hit key input again and type "0000"
wait 10 seconds, it should bring up the secret menu.
5. Press 2 (CDMA) > Press 1. (COMMON) > NEXT > NEXT > 8 PREF MODE SET > GSM_WCDMA_ONLY
6) Hit the soft menu key and select back until you reach the main menu and select UMTS
then select [1]DEBUG SCREEN > [6]PHONE CONTROL, > [2]FAKE SECURITY CONTROL > set it to ON
7)Press menu and back and select [3] NAS CONTROL. We are going to check a few different settings in this menu so remember how to get here cause I don’t want to repeat myself.
[1] CIPHERING CONTROL = OFF
[2] INTEGRITY CONTROL =ON
[3] SIM CLASS CONTROL = UMTS
[4] REVISION CONTROL = DO NOT TOUCH
[5] RRC(HSPA) CONTROL = DO NOT TOUCH
[6] DUALMODE IMPROVEMENT CONTROL= DO NOT TOUCH
[7] NAS AVOID SECURITY CONTROL= OFF, 0
[8] BIP BLOCK = 1
8) Press menu and back twice then > PHONE CONTROL > Select [7] NETWORK CONTROL > select [1] GFC and make sure that it is set to [1]GSM/(E)GPRS/WCDMA REL8 .
9) Press menu and back and select [2] BAND SELECTION and select WCDMA/GSM ALL for both WCDMA and GSM band preferences. I selected the ALL choice for LTE as well even though I know it isn’t supported for TMOBILE.
10) Under the NETWORK CONTROL menu we just came from select [4] AQUISITION ORDER and change it to [3]UMTS_GSM
11) Press menu and back until you are in the PHONE CONTROL menu and select [5] SIMULATION , press the [2] SW WATCHDOG button 6(six) times and then the [3] HW WATCHDOG 6(six) times. After you hit both of those 6 times, Hold the power down and reboot immediately.
12 ) If you want 4g LTE you must use odin to install TWRP which you can find here
13 ) turn off your phone and boot in to recovery by holding power, volume up and the home button. This is annoying because if you hold it too long it will power off again.
In here you want to click install from zip, select the M919 file. install it and then go to clear cache davik, go to reboot and you are all good!
enjoy. This fix has been brought to you both by imbmiller and nfsmww
I tried both methods but it didnt work until I combined them

interesting... going to try this and get back to you... but after this unlock.... could you use sprint and had the option to switch sims if need be using this rom?

Jonathanlc2005 said:
interesting... going to try this and get back to you... but after this unlock.... could you use sprint and had the option to switch sims if need be using this rom?
Click to expand...
Click to collapse
You can use any network after this unlock. I upgraded to cyanogens marshmallow rom and still have network service.

It worked, screenshot uploaded later

screenshots

Jonathanlc2005 said:
screenshots
Click to expand...
Click to collapse
going to keep testing and ill get back to you

will this work if your on 5.0.1 ok3 lollipop?

Hello,
I have a problem where my phone only connects to LTE. If i force CDMA mode, it just shows full bars but no 3g symbol. Does anyone know of a fix? LTE only has one bar near my new place.
Thanks

chopchopw said:
Hello,
I have a problem where my phone only connects to LTE. If i force CDMA mode, it just shows full bars but no 3g symbol. Does anyone know of a fix? LTE only has one bar near my new place.
Thanks
Click to expand...
Click to collapse
did you do exactly like it says including the radio?
the radio has to be flashed first before anything. i used to be on OH1, switched the radio and used cyanogenmod stable 4.4. then did this mod and it works so far. i havent had a chance to fully test it as i am on vacation but i will hopefully soon

yeah tmobile doesnt work

Great post! Just what I needed!! Can I make a TWRP backup of my CM12.1 ROM on OK3 modem and then then flash M919 rom and follow your directions? After all the steps, can I restore my TWRP backup of CM12.1 ROM and OK3 modem and will it still have domestic sim unlocked?

nyknight77 said:
Great post! Just what I needed!! Can I make a TWRP backup of my CM12.1 ROM on OK3 modem and then then flash M919 rom and follow your directions? After all the steps, can I restore my TWRP backup of CM12.1 ROM and OK3 modem and will it still have domestic sim unlocked?
Click to expand...
Click to collapse
restoring your modem would wipe out the unlock for sure
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Don't know how to install M919 ROM!!!
I need help installing M919 ROM. I have never done this before, so I do not know how to create the file format needed to use with ODIN. I tarred the boot.img file, but it is only 8MB in size; that isn't the file I'm suppose to load, is it?
Need more details than just "install the M919 rom"...

jkh9081 said:
I need help installing M919 ROM. I have never done this before, so I do not know how to create the file format needed to use with ODIN. I tarred the boot.img file, but it is only 8MB in size; that isn't the file I'm suppose to load, is it?
Need more details than just "install the M919 rom"...
Click to expand...
Click to collapse
Install TWRP with Odin, flash ROM from TWRP. That's a link in step 12.

Still struggling with unlocking phone.
bilgerryan said:
Install TWRP with Odin, flash ROM from TWRP. That's a link in step 12.
Thanks for the advice on TWRP; I eventually was able to install TWRP and was able to flash the M919 ROM.
I used odin to install the MK5 modem. I rebooted at this point and it updated 35 applications. The phone
is now booting with the new M919 rom, but I constantly get "Unfortunately, the process
com.android.phone has stopped". I'm on the step where you run SuperSU, but there are no
applications listed, so cannot disable knox. I'm so confused and exhausted from this; been messing
with it all day, but I think progress has finally been made. Will continue tomorrow, hopefully somebody
will have posted more help by then. My current question is should I install a stock 4.4.2 rom then
use the auto-rooter program? I'm wondering if the M919 rom is compatible since getting the errors.
I think I read that once rooted, no need to root again, so maybe just install a stock os.
Click to expand...
Click to collapse

jkh9081 said:
bilgerryan said:
Install TWRP with Odin, flash ROM from TWRP. That's a link in step 12.
Thanks for the advice on TWRP; I eventually was able to install TWRP and was able to flash the M919 ROM.
I used odin to install the MK5 modem. I rebooted at this point and it updated 35 applications. The phone
is now booting with the new M919 rom, but I constantly get "Unfortunately, the process
com.android.phone has stopped". I'm on the step where you run SuperSU, but there are no
applications listed, so cannot disable knox. I'm so confused and exhausted from this; been messing
with it all day, but I think progress has finally been made. Will continue tomorrow, hopefully somebody
will have posted more help by then. My current question is should I install a stock 4.4.2 rom then
use the auto-rooter program? I'm wondering if the M919 rom is compatible since getting the errors.
I think I read that once rooted, no need to root again, so maybe just install a stock os.
Click to expand...
Click to collapse
If the ROM is not rooted you will have to root again, but it's not hard.
Click to expand...
Click to collapse

Some notes to help others.
Being a newbie, I have no idea what I'm doing. So here are some notes that may help others like myself.
NOTE: My phone was previously rooted before starting this unlocking procedure.
In order to install the M919 rom, I had to install the TWRP (Team Win Recovery Project) tool. This was
accomplished by downloading the recovery.img file that was referenced by the link in this post. I had to use
the ODIN tool to install the file, but it had to be converted to a TAR file first. To convert to a TAR file, the
GNU version of TAR was downloaded and installed; I also set the Windows 7 search path to include the
bin directory of the installed tree (the search path allows running 'tar' without having to type
the full path to the program; the path was added by editing the path through the properties of
"My Computer" (right click the My Computer icon to edit). Once tar is installed, cd to where the recover.img
file resides and to the following command:
tar -cvf recovery.img.tar recovery.img
Now you have a recovery.img.tar file that will work with ODIN; install using the file as 'AP' type.
To use ODIN, put your phone in OS flash mode by powering it up by pressing volume down/home/power
buttons. Start up ODIN then plug the phone into the computer and press the volume up button; you will
see a message that the phone has been connected. Click the start button and the tarred image file will
be flashed to the phone. Now when the phone is booted by pressing the volume up/home/power buttons,
it will run the TWRP tool.
To install the M919 rom, boot phone in recovery mode (run the TWRP tool as mentioned above).
The M919 rom file is in a ZIP file which is the correct format for the TWRP tool to install, but the
ZIP file must first be put on your phone's SD card. To get the file onto the phone, you should be
able to remove the SD card and just copy it to the TWRP directory which should have been
created when TWRP was installed. However, I downloaded ADB on my computer and did
the following command from inside a windows CMD window from the directory where the
M919 rom Zip file resided...
adb push jfltetmo_M919UVUEMK2_Stock_Deodexed.zip /sdcard/TWRP
With the zip file on the sdcard (in the phone), click the 'INSTALL" button in TWRP and select
the /sdcard/TWRP/jflt...Deodexed.zip file path to flash to phone.
Installing the MK5 modem.bin file again requires it to be tarred for use with ODIN...
tar -cvf modem.bin.tar modem.bin
So that's where I'm currently at.
FYI, there seems to be a bug with the TWRP tool. If the phone is left inactive for a few
minutes, the screen will dim then lock and cannot: be unlocked. Once locked, the phone must
be powered down and TWRP restarted. So press the back arrow periodically to prevent the
phone from locking.

jkh9081 said:
Being a newbie, I have no idea what I'm doing. So here are some notes that may help others like myself.
NOTE: My phone was previously rooted before starting this unlocking procedure.
In order to install the M919 rom, I had to install the TWRP (Team Win Recovery Project) tool. This was
accomplished by downloading the recovery.img file that was referenced by the link in this post. I had to use
the ODIN tool to install the file, but it had to be converted to a TAR file first. To convert to a TAR file, the
GNU version of TAR was downloaded and installed; I also set the Windows 7 search path to include the
bin directory of the installed tree (the search path allows running 'tar' without having to type
the full path to the program; the path was added by editing the path through the properties of
"My Computer" (right click the My Computer icon to edit). Once tar is installed, cd to where the recover.img
file resides and to the following command:
tar -cvf recovery.img.tar recovery.img
Now you have a recovery.img.tar file that will work with ODIN; install using the file as 'AP' type.
To use ODIN, put your phone in OS flash mode by powering it up by pressing volume down/home/power
buttons. Start up ODIN then plug the phone into the computer and press the volume up button; you will
see a message that the phone has been connected. Click the start button and the tarred image file will
be flashed to the phone. Now when the phone is booted by pressing the volume up/home/power buttons,
it will run the TWRP tool.
To install the M919 rom, boot phone in recovery mode (run the TWRP tool as mentioned above).
The M919 rom file is in a ZIP file which is the correct format for the TWRP tool to install, but the
ZIP file must first be put on your phone's SD card. To get the file onto the phone, you should be
able to remove the SD card and just copy it to the TWRP directory which should have been
created when TWRP was installed. However, I downloaded ADB on my computer and did
the following command from inside a windows CMD window from the directory where the
M919 rom Zip file resided...
adb push jfltetmo_M919UVUEMK2_Stock_Deodexed.zip /sdcard/TWRP
With the zip file on the sdcard (in the phone), click the 'INSTALL" button in TWRP and select
the /sdcard/TWRP/jflt...Deodexed.zip file path to flash to phone.
Installing the MK5 modem.bin file again requires it to be tarred for use with ODIN...
tar -cvf modem.bin.tar modem.bin
So that's where I'm currently at.
FYI, there seems to be a bug with the TWRP tool. If the phone is left inactive for a few
minutes, the screen will dim then lock and cannot: be unlocked. Once locked, the phone must
be powered down and TWRP restarted. So press the back arrow periodically to prevent the
phone from locking.
Click to expand...
Click to collapse
Mine unlocks fine in TWRP 3.0

if any one need direct unlock contact me via pm

Still needing help.
I thought I had my phone unlocked, but made the mistake to trying to upgrade my android version using the Tmobile installation. Now the phone will not boot. I re-installed the M919 ROM, and the phone gets further along, but it shows a message of starting apps then shuts down. How can I get back to where the phone will boot? Thanks for any ideas. Also, can somebody please post a link to the 3.0 version of TWRP; the version I have will lock the screen and cannot be unlocked.
Correction: Phone will only briefly show the Samsung S4 image, then shuts down. Currently the phone will not even startup the TWRP tool; I can still get to the mode where I should be able to load the TWRP tool; looking like the phone maybe too far gone to save.

How To Guide [Magisk][US/CAN BL Unlock] Root for Galaxy S21 Series (B/N/0/U/U1/W)

Note: this guide copied from topjohnwu's. Original guide here
US/Canada bootloader unlock thread:
here
Before Installing Magisk
Installing Magisk WILL trip KNOX
Unlocking bootloader for the first time will do a data wipe.
Installation
If you already have Magisk installed, it is strongly recommended to upgrade directly via Magisk Manager using the “Direct Install” method. The following tutorial is only for initial installation.
Getting Started
Before you start:
This tutorial assumes you understand how to use adb and fastboot
If you plan to also install custom kernels, install it after Magisk
Your device’s bootloader has to be unlocked
Download and install the latest Magisk app. In the home screen, you should see:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The result of Ramdisk determines whether your device has ramdisk in the boot partition.
Unlocking Bootloader
Unlocking BL on modern Samsung devices have some caveats, so I figure this would be helpful.
Allow bootloader unlocking in Developer options → OEM unlocking
Reboot to download mode: power off your device and press the download mode key combo for your device (Vol Down + Vol Up) while connected to usb.
Long press volume up to unlock the bootloader. This will wipe your data and automatically reboot.
If you think the bootloader is fully unlocked, it is actually not! Samsung introduced VaultKeeper, meaning the bootloader will still reject any unofficial partitions before VaultKeeper explicitly allows it.
Go through the initial setup. Skip through all the steps since data will be wiped again later when we are installing Magisk. Connect the device to Internet during the setup.
Enable developer options, and confirm that the OEM unlocking option exists and is grayed out. This means the VaultKeeper service has unleashed the bootloader.
Your bootloader now accepts unofficial images in download mode.
Patching Boot Image
If your device has boot ramdisk, you need a copy of the boot.img
Instructions
Use either Frija or Samloader to download the latest firmware zip of your device directly from Samsung servers.
Unzip the boot.img from AP and copy the file to your device.
Press the Install button in the Magisk card
Choose “Select and Patch a File” in method, and select the stock boot image
Magisk Manager will patch the image to [Internal Storage]/Download/magisk_patched.img.
Copy the patched image to your PC
Flash the patched boot image to your device.
For most devices, reboot into fastboot mode and flash with command:
fastboot flash boot /path/to/magisk_patched.img or
Rename magisk_patched.img to boot.img and use 7zip to make flashable tar of your boot.img
Reboot to download mode. Open Odin on your PC, and flash boot_patched.tar as AP.
Reboot and voila!
Patching AP
Instructions
Use either Frija or Samloader to download the latest firmware zip of your device directly from Samsung servers.
Unzip the firmware and copy the AP tar file to your device. It is normally named as AP_[device_model_sw_ver].tar.md5
Press the Install button in the Magisk card
Choose “Select and Patch a File” in method, and select the AP tar file
Magisk Manager will patch the whole firmware file to [Internal Storage]/Download/magisk_patched.tar
Start the installation, and copy the patched tar file to your PC using ADB:
adb pull /sdcard/Download/magisk_patched_[random_strings].tar
DO NOT USE MTP as it is known to corrupt large files.
Reboot to download mode. Open Odin on your PC, and flash magisk_patched.tar as AP, together with BL, CP, and CSC (NOT HOME_CSC because we want to wipe data) from the original firmware.
Your device should reboot automatically once Odin finished flashing. Agree to do a factory reset if asked.
Install the Magisk app you’ve already downloaded and launch the app. It should show a dialog asking for additional setup.
Let the app do its job and automatically reboot the device. Voila!
Custom Recovery​Installing using custom recoveries such as TWRP is only possible if your device has boot ramdisk.
Instructions
Download the Magisk APK
Rename the .apk file extension to .zip, for example: Magisk-v2*.*.apk → Magisk-v2*.*.zip. If you have trouble renaming the file extension (like on Windows), use a file manager on Android or the one included in TWRP to rename the file.
Flash the zip just like any other ordinary flashable zip.
Reboot and check whether the Magisk app is installed. If it isn’t installed automatically, manually install the APK.
Thanks
@topjohnwu for magisk and guide, If you appreciate his effort, show some love and support
Donations
https://www.patreon.com/topjohnwu
https://www.paypal.me/topjohnwu

US/Canada devices has no oem unlock toggle!
Unlock service here
How to get OEM Unlock option back for Non US/Canada device?
1. Open the Settings app. Tap on General Management → Date and time.
2. Use the toggle button to disable Automatic date and time.
3. Set date option will be enabled now. Tap on it, and set the date to about 10-20 days earlier.
4. Enable developer options.
4.a Go to your device Settings.
4.b Select ‘About phone’ » tap seven times on ‘Build number’.
└ This will enable Developer options under Settings.
4.c Go back to Settings » scroll down to the bottom and you’ll see Developer options menu.
5. Open developer options (in the Settings app itself), and find the option called ‘Auto update system‘. Use the toggle button to disable it.
6. Now, go back to the main screen of Setting, and then tap on Software update.
7. Disable the option ‘Download updates automatically‘.
8. Tap on ‘Download updates manually‘ option, but it will give you an error because of the wrong date, so it’s fine.
9. Restart the device.
10. Go to Settings > Developer options. The OEM unlock option should be enabled now.

Thank You very much for your awesome work!!

Thanks, but that doesn't apply to the S21

Boomorrow said:
Thanks, but that doesn't apply to the S21
Click to expand...
Click to collapse
Use latest magisk canary, I have rooted my S21 Ultra.

The latest Magisk Canary release (21409) contains the fix needed for the S21 devices, yes (but being a Canary release there are of course other bugs).
But, @afaneh92, since you're just copying @topjohnwu's installation instructions exactly, word for word, wouldn't it just have been easier to link to those instructions and let people know that Magisk Canary releases now can root the S21 Ultra (and maybe also warn people that the Canaries can be buggy)?

Thanks for this amazing valentines gift

thanks - its working

Does this work on all S21+ Ultra variants?

Didgeridoohan said:
The latest Magisk Canary release (21409) contains the fix needed for the S21 devices, yes (but being a Canary release there are of course other bugs).
But, @afaneh92, since you're just copying @topjohnwu's installation instructions exactly, word for word, wouldn't it just have been easier to link to those instructions and let people know that Magisk Canary releases now can root the S21 Ultra (and maybe also warn people that the Canaries can be buggy)?
Click to expand...
Click to collapse
Its not just a copy and paste! I have edited the the guide to suit our S21 series.

afaneh92 said:
Its not just a copy and paste! I have edited the the guide to suit our S21 series.
Click to expand...
Click to collapse
Edited?
These few lines are the only things that do not exactly match John's instructions:
Unzip the boot.img from AP and copy the file to your device.
<Copy of John's flashing boot image instructions>
Rename magisk_patched.img to boot.img and use 7zip to make flashable tar of your boot.img
Reboot to download mode. Open Odin on your PC, and flash boot_patched.tar as AP.
99% of that 1st post is a copy-paste... You should know the rules on this forum. Copying others work, even text, without proper credits is a no-no.
And no: a small "thanks for the guide" isn't proper credits. Be transparent with where you copy stuff from.

Didgeridoohan said:
Edited?
These few lines are the only things that do not exactly match John's instructions:
Unzip the boot.img from AP and copy the file to your device.
<Copy of John's flashing boot image instructions>
Rename magisk_patched.img to boot.img and use 7zip to make flashable tar of your boot.img
Reboot to download mode. Open Odin on your PC, and flash boot_patched.tar as AP.
99% of that 1st post is a copy-paste... You should know the rules on this forum. Copying others work, even text, without proper credits is a no-no.
And no: a small "thanks for the guide" isn't proper credits. Be transparent with where you copy stuff from.
Click to expand...
Click to collapse
Also removed unnecessary instructions!
Thanks for clarification, I will add link to topjohnwu guide and donations

Work hard and I succeeded. Thanks again to the author
Mod Edit : English only !
Google translation :
Work hard and I succeeded. Thanks again to the author,

I recently got a Samsung S21 Ultra 5G from Verizon. I live in the US, and I have read online that the US variants are more difficult to root. The model is SM-G998U, with Snapdragon.
The serial number is R3CR106XBXT, if that helps at all.
The main issue I've been facing is unlocking the bootloader -- it doesn't seem to show up in the Developer Options menu, unfortunately. I am able to enter recovery mode but selecting the option to boot into the bootloader only restarts the phone.
I am able to use ADB in the command prompt, as it detects the phone fine when checking 'adb devices'.
I have tried doing 'adb reboot bootloader' but it only does the same as trying it from recovery mode.
The only other 'mode' that works is Samsung's Download mode' which I think only works with Odin.
Trying 'fastboot devices' during this screen yields no results.
Am I out of luck for trying to get this device rooted?
Thank you!

NuLuumo said:
I recently got a Samsung S21 Ultra 5G from Verizon. I live in the US, and I have read online that the US variants are more difficult to root. The model is SM-G998U, with Snapdragon.
The serial number is R3CR106XBXT, if that helps at all.
The main issue I've been facing is unlocking the bootloader -- it doesn't seem to show up in the Developer Options menu, unfortunately. I am able to enter recovery mode but selecting the option to boot into the bootloader only restarts the phone.
I am able to use ADB in the command prompt, as it detects the phone fine when checking 'adb devices'.
I have tried doing 'adb reboot bootloader' but it only does the same as trying it from recovery mode.
The only other 'mode' that works is Samsung's Download mode' which I think only works with Odin.
Trying 'fastboot devices' during this screen yields no results.
Am I out of luck for trying to get this device rooted?
Thank you!
Click to expand...
Click to collapse
this is exactly what I'm encountering as well. I have the US unlocked version of the s21 ultra. Incredibly annoying - as there's no OEM unlocking option under Dev options. I tried the 'set the date back 7 Days' trick that supposedly makes work. It does absolutely nothing.
I'm dangerously close to returning this phone and going back to my OnePlus 8 pro which was overall much better experience. The 8 pro had way better touch response, much more beautiful screen, and was completely rootable and able to have ROMs.

NuLuumo said:
I recently got a Samsung S21 Ultra 5G from Verizon. I live in the US, and I have read online that the US variants are more difficult to root. The model is SM-G998U, with Snapdragon.
The serial number is R3CR106XBXT, if that helps at all.
The main issue I've been facing is unlocking the bootloader -- it doesn't seem to show up in the Developer Options menu, unfortunately. I am able to enter recovery mode but selecting the option to boot into the bootloader only restarts the phone.
I am able to use ADB in the command prompt, as it detects the phone fine when checking 'adb devices'.
I have tried doing 'adb reboot bootloader' but it only does the same as trying it from recovery mode.
The only other 'mode' that works is Samsung's Download mode' which I think only works with Odin.
Trying 'fastboot devices' during this screen yields no results.
Am I out of luck for trying to get this device rooted?
Thank you!
Click to expand...
Click to collapse
This guide for unlockable bootloader devices, B/N/0 models

I assume this will trip Knox right?

joancolmenares said:
I assume this will trip Knox right?
Click to expand...
Click to collapse
Read the very first bullet, lol

cjrivera04 said:
Read the very first bullet, lol
Click to expand...
Click to collapse
My very very bad... I kinda missed it lol

@afaneh92 By the way, I'm curious: Why have you added the "Patch boot image" section? John's original Samsung instructions only include patching the AP, so I was wondering why you have this section in your text... From what I can see, users are reporting that John's original instructions work just as they should on the S21 devices (as long as you use releases from 21409 onwards).

[Android 11] Unofficial Lineage OS 18.1 for A21s

WARNING + DISCLAIMER:
By installing this custom ROM, you are VOIDING your warranty. Also, installation of this ROM WILL TRIP KNOX PERMANENTLY, and render apps such as Samsung Health, Private Folder, (+ any apps that depend on KNOX) useless until you get the phone's motherboard replaced at the Samsung C/S center.
Although this software is released in the hope that it will be useful, there is NO GUARANTEE that installing this will not cause any harm to your device. I TAKE NO RESPONSIBILITY FOR ANY BRICKED DEVICES, DAMAGED HARDWARE, OR ANY OTHER PROBLEMS CAUSED BY THIS ROM. You are using this ROM at YOUR OWN RISK. I strongly recommend that you DO NOT continue to the steps below UNLESS YOU FULLY UNDERSTAND WHAT YOU ARE DOING.
While this ROM has been tested with South Korean variant of Galaxy A21s (SM-A217N, CSC changed from LUC->SKC), please keep in mind that it hasn't been tested on any other variant (such as A217F, A217M.)
Click to expand...
Click to collapse
I would like to express special thanks to all the developers who contributed to the LineageOS port for Galaxy Tab S6 Lite + all the other developers who contributed to sepolicy & hardware parts for Samsung SLSI (Exynos) devices. Porting LineageOS to A21s would have been much harder without them.
Click to expand...
Click to collapse
After doing some research on this device, I was able to port LineageOS. The original sources are based on Galaxy Tab S6 Lite Wi-Fi version (gta4xlwifi), with some heavy modifications made for the A21s. In the process, I was able to fix some of the problems that were found on GSI (MTP, Fingerprint removal issues, NFC, Wi-Fi hotspot and direct), and added in some enhancements to the kernel.
Unfortunately, installation of this ROM requires Lineage Recovery, and since FBE (File-based-encryption) is enabled by default, it is incompatible with the TWRP.
Screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
NOT WORKING:
- Cell Broadcast (Emergency Messages) is broken in South Korea. The phone shows notifications, but the messages appear broken. Not sure about other countries. FIXED in South Korea as of 2021/9/2. However, its functionality in other countries hasn't been tested.
- Samsung's Proprietary Apps
- In order to use Wi-Fi Direct, you need to install a Wi-Fi direct sharing app from Google Play, as LineageOS doesn't have a sharing app installed by default
- Auto Brightness (The phone doesn't have the sensors for it anyway)
- On very rare occasions(probably once in more than 20 boots), the device's RIL (Phone calls, Data) might start up late when booting. If you see "No service" after booting, please wait for 30-60 seconds.
- VoLTE & VoWifi(not tested) - Unfortunately, this is located deep within Samsung's framework. AOSP-based roms for other Samsung devices don't support it either. Someday, this might be fixed.....
WORKING:
- Everything Else
GITHUB:
Device Source Tree: android_device_samsung_a21s, android_device_samsung_universal3830-common
Kernel: android_kernel_samsung_universal3830-common
Instructions for Installation:
1. BEFORE INSTALLING, make sure that you have UNLOCKED the bootloader of your device. This is a great guide that show how to do it. Also, the phone must be on the Stock ANDROID 11. If you are on binary U6, please use the recovery tar for U6.
2. Download the Lineage Recovery, ROM, Google Apps, ADB, and Odin. Unzip ADB and Odin to somewhere appropriate.
- ROM
- Recovery / Recovery(for U6)
- Google Apps
- ADB
- Odin
3. Enable USB Debugging on the device. Go to settings->About phone->Software information, and tap the build number several times until you see the notification that the devloper settings have been enabled. After enabling developer settings, go to settings->developer settings and check USB debugging.
4. Open Command Prompt, and type "cd <the path where you saved ADB to>".
4-1. As a test, type "adb devices". After typing it, the phone should show a screen that asks you to grant permissions for USB debugging. Select Yes.
5. On the phone, start holding down the Volume Up and Down keys. KEEP THE KEYS PRESSED UNTIL THE PHONE REBOOTS AFTER YOU TYPE THE COMMAND IN THE NEXT STEP.
6. While holding the keys down. type in the command "adb reboot recovery" on the command line.
11. After the phone reboots into download mode, press volume up to continue. Make sure that you see the "OEM LOCK: OFF" before continuing.
12. Open Odin. After opening Odin, click on AP, and select the Lineage Recovery Tar file that you downloaded in the step 2. After that, click on Start.
13. After a few seconds, if everything goes well, Odin should show "PASS" and the device should reboot into Lineage Recovery. After the device enters recovery, tap on Apply update->Apply from ADB. In some cases, touchscreen may be unresponsive or slow. If that happens, use Volume Keys to navigate and Power key to select. KEEP THE DEVICE CONNECTED TO THE COMPUTER.
14. After choosing Apply from ADB, type "adb sideload <the path where you saved the ROM file>" on the command prompt and press enter.
<CONTINUED ON THE NEXT POST>

15. If everything goes right, the device should show "script succeeded: result was [1.000000]" While ADB may show errors such as "Failed to read command" at 47%, this is no problem as long as the device says that the script succeeded.
16. Now it is time to install Google apps. On the phone, tap on Apply from ADB again, and on the computer, type "adb sideload <the path where you saved Google apps to>" and press enter.
17. After about 1-2 minutes, installation should be complete. Again, ADB might show "Failed to read command" errors. As long as the phone says that it was success, this is no problem. After installing, click on the "back" icon shown below.
18. Choose Wipe data/factory reset, and reboot the device.
19. If everything went well, the phone should reboot into LineageOS. Set up the device and Enjoy!

ADDITIONAL TIP: HOW TO ROOT THE PHONE ON LINEAGE 18
On Lineage 18, I patched the kernel so that it would have no problem with the official Magisk app.
Therefore, you DON'T need to use a version that has been modified for A21s.
If you want to have root, you can get the Official Magisk App.
1. Download & Install Magisk from the official source.
2. Select Install. When it asks you to select the boot image, choose the boot image from the Lineage OS ROM file that you downloaded from the step above. After patching the boot image, move & rename it to something you can type easily (ex. /sdcard/rooting.img)
3. Enable developer settings (Settings->About phone->Tap on build number)
4. Go to developer settings and enable USB debugging & root permissions for usb debugging.
5. Connect the phone to the PC.
6. Open the command prompt, and type "cd <the folder where you installed adb>. After that, type "adb root". If the phone asks you for permissions for USB debugging, allow it.
7. After the adb shows "Restarting adbd as root", type "adb shell dd if=/sdcard/<the path to saved boot image>" of=/dev/block/by-name/boot". The output should be something like
" *** records in
*** records out
*** bytes (** M) copied, *** s, **M/s"
8. After seeing the output above, reboot the phone. After rebooting, it should be rooted.

Good news. Thank you very much

Then, my friends, write here how it works and thank you for your observations

Thanks for your work buddy.....
I got Magisk installed an easier way...
Download Magisk Canary .apk
Change .apk to .zip then install the same way as the Rom and Gapps, by ADB sideload.
Factory reset/Format data and reboot.
Done
All we need is a working TWRP.... I've got one working but it shows no files and won't mount anything..... e.g. system, data etc

Pharcanal40 said:
Thanks for your work buddy.....
I got Magisk installed an easier way...
Download Magisk Canary .apk
Change .apk to .zip then install the same way as the Rom and Gapps, by ADB sideload.
Factory reset/Format data and reboot.
Done
All we need is a working TWRP.... I've got one working but it shows no files and won't mount anything..... e.g. system, data etc
Click to expand...
Click to collapse
What is your device model ...is it SM A217F/DS android 11 U6? Pls reply..

Gxzllen said:
What is your device model ...is it SM A217F/DS android 11 U6? Pls reply..
Click to expand...
Click to collapse
A217F on U5

Pharcanal40 said:
A217F on U5
Click to expand...
Click to collapse
Can i download it on u6?i'm afraid my phone brick if i do it

Gxzllen said:
Can i download it on u6?i'm afraid my phone brick if i do it
Click to expand...
Click to collapse
If you're on U6, there's a chance that Odin might fail on vbmeta.
A possible solution is:
1. Download Magisk (version doesn't matter)
2. Download the U6 firmware that you're on
3. Using Magisk, patch the AP tar of U6 firmware
4. In the Lineage recovery tar file that you downloaded from above, replace the vbmeta.img with the one from Magisk-patched AP tar file
5. Proceed with the installation as written above
A more fail-safe method would be:
1. Root the phone using a patched Magisk app
2. unpack the recovery.img in the Lineage recovery tar file and copy it into your device's SD card
3. Enable USB debugging on the phone, and connect the phone to adb
4. Using command prompt, type
"cd <path to adb>"
"adb shell"
"su"
"dd if=/sdcard/<path to lineage recovery image> of=/dev/block/by-name/recovery"
"reboot recovery"
After typing these, your device will reboot into Lineage Recovery. After entering recovery, select apply update->apply from adb, and proceed with the installatiom above from Step 14.

grccorps said:
If you're on U6, there's a chance that Odin might fail on vbmeta.
A possible solution is:
1. Download Magisk (version doesn't matter)
2. Download the U6 firmware that you're on
3. Using Magisk, patch the AP tar of U6 firmware
4. In the Lineage recovery tar file that you downloaded from above, replace the vbmeta.img with the one from Magisk-patched AP tar file
5. Proceed with the installation as written above
A more fail-safe method would be:
1. Root the phone using a patched Magisk app
2. unpack the recovery.img in the Lineage recovery tar file and copy it into your device's SD card
3. Enable USB debugging on the phone, and connect the phone to adb
4. Using command prompt, type
"cd <path to adb>"
"adb shell"
"su"
"dd if=/sdcard/<path to lineage recovery image> of=/dev/block/by-name/recovery"
"reboot recovery"
After typing these, your device will reboot into Lineage Recovery. After entering recovery, select apply update->apply from adb, and proceed with the installatiom above from Step 14.
Click to expand...
Click to collapse
nice thankyou bro

Or you can extract just the boot.img from the AP.tar. Patch it in Magisk then repack in the AP and flash with Odin

Pharcanal40 said:
Or you can extract just the boot.img from the AP.tar. Patch it in Magisk then repack in the AP and flash with Odin
Click to expand...
Click to collapse
Ohh okay its easy this way

Can I use adb fastboot instead of Odin?

Successfully Flashed! Everything work fine.
Model- A217f /DS
U6 binary ,Android 11 latest.

NuzzaimStark said:
Successfully Flashed! Everything work fine.
Model- A217f /DS
U6 binary ,Android 11 latest.
Note: Encountered some problems when I flash (vbmeta) ie, its because of its only for u5.
Odin showed failed at last ,
Phone was unable to boot but
By using hijacking software , bootloader was again running . but when auto reboot lineage recovery was automatically loaded, and tryed your above steps and everything working fine,
Note: pubg is very very better in this ROM.
Close range is also better.
Thankyou grccorps .
Click to expand...
Click to collapse
Thank you for your review. It's such a great news that it's working on U6.
Yes, PUBG is a hell of a game, Krafton has done such a great job with it The kernel has newer mali graphics driver (R26P0 -> R31P0), maybe that could've done the trick (or it may just be due to LineageOS being much, much lighter than One UI)
How is the battery? While I wasn't able to find any abnormal battery drains (both in standby and stress conditions), I'm concered about how it would perform in other devices.

NuzzaimStark said:
Successfully Flashed! Everything work fine.
Model- A217f /DS
U6 binary ,Android 11 latest.
Note: Encountered some problems when I flash (vbmeta) ie, its because of its only for u5.
Odin showed failed at last ,
Phone was unable to boot but
By using hijacking software , bootloader was again running . but when auto reboot lineage recovery was automatically loaded, and tryed your above steps and everything working fine,
Note: pubg is very very better in this ROM.
Close range is also better.
Thankyou grccorps .
Click to expand...
Click to collapse
Can you be a little more specific? my phone U6 but idk how to flash recovery can or you give me email so i can exchange?

Phuc230204 said:
Can you be a little more specific? my phone U6 but idk how to flash recovery can or you give me email so i can exc(hange?
Click to expand...
Click to collapse
First look on A21s LineageOS 18.1

hi,so i get this message "only official released binaries are allowed''in download mode,after the vbmeta failed...
SM-A217F/DSN
and in frp hijacker i get ''check device connection or com ports''

Update:so i succeded to hijack my phone after the error but it wouldn't boot into recovery,and i got everytime a screen with a warning that my phone is not using samsung's official software,and when i press the power button to continue,like it shows,it boots automatically into android.
So what should i do?
And do i need root to do this?

s10 galaxy g973f no boot after flash magisk patched firmware

Ieudhd

i donloaded diud

Hello Sams10, did you make the bootloader before or not as explained in the tutorial.
You said your flasher with odin more detail would be welcome, how did you do there according to your comment your flashed directly in download mode without having done the manipulation for the bootloader and then did what.

bootloader unlocked and kg checking

every instructions for s10 is outdated including the lineage os website and youtube i have checked all

heimdalll latest 1.4.2 doesnt work with samsung s10.

19.9.2022 on latest android firmware new zealand firmware custom rom doesnt work , only europe and americas will work

Hello Sams10, already a little politeness because I said hello to you, you post 4 times without saying hello.
I don't understand the unlock bootloader ok then S10 is good s10 exynos or 5 G, I followed John Wu's tutorial as explained in the magisk thread on this forum no problem.
You have well modified in magisk AP of the official rom then trafer on your pc with adb pull then odin 3.14.4 flash the 4 files BL-AP patched-CP Home CSC.

g973F exynos, not 5g, u must be americas europe firmware , vodafone nz firmware probably doesnt work

this is my current download mode
my screen is cracked thats the purple lines and dead pixel on top left

Not work

Hello Sams10, you start in dowload mode you flash with odin 3.14.4 the official firmware the one mark in my signature me AUT or XEF lash the 4 BL-AP-CP-CSC files it will restart as on the first day. Then install magisk 25.2 you transfer AP on your S10, you modify with magisk you will have a file in internal memory in dowload magisk_patchedxxxx.tar you transfer it with ADB on the pc which in adb must give this adb pull /sdcard/Download/magisk_patched-25200_G3e9K.tar
once transferred ok you put yourself in dowload mode and you put the file BL -AP patched -CP -home CSC you start you let it restart and you open magisk to activate zygisk then you install the modules you will find here https://forum .xda-developers.com/t/discussion-magisk-the-age-of-zygisk.4393877/
instalation look here from john Wu https://topjohnwu.github.io/Magisk/install.html
read the instruction part, then when you have finished and root I will send you the file to remove the warning message at start-up ok

I use ap magisk patched and CSC , not home CSC when I flashed and had boot loop

Does it have to be an adb pull for the patched firmware from Android , I just use file transfer on windows to transfer the magisk patched ap file from the s10 to the windows

Try with home CSC as john wu says you have to do adb from s10 to pc with adb windows not send all.

Start the installation, and copy the patched tar file to your PC using ADB:
adb pull /sdcard/Download/magisk_patched_[random_strings].tar
DO NOT USE MTP as it is known to corrupt large files.

John Wu says CSC not home csc because he want to erase firmware data

Hello Sams10, yes you made a backup of your data before with smart switch or others. For me it worked if you follow the present tutorial look on my tutorial
1- The bootloader follow explanation Use vol down + vol up + USB cable plugged into a PC to boot the phone into download mode;
Long press vol up then confirm that you want to unlock the bootloader (this is only needed once);
* Please note that all your data will be erased, including internal memory, and the phone will restart!!
5- Let the phone start normally, go through the configuration and connect to the Internet (wireless or mobile data) in order to unlock
6- Make sure OEM Unlock is enabled in Developer Settings.
2- Once reboot install magisk 25.2 APK.
3- Download the official firmware on Samobile.com or frija you will find this on the forum.
4- Transfer the official firmware AP to the smartphone.
5- Open magisk recovery mode choose corrective mode choose the AP download press "let's go."
6- Once the modification is finished in the root directory, download a patched_magiskxxxx.img.tar file if found.
7- Transfer it with adb pull like this adb pull /sdcard/Download/patched_patched.magiskxxxx.img[.tar] you can rename it "patched_magisk.img.tar"
8- Put your smartphone in download mode Use vol down + vol up + usb cable connected to a PC to start the phone in download mode, briefly press vol up to
confirm that you want to enter download mode;
9- Open Odin latest version placed 4 files following BL-AP magisk patched.img.tar-CP-home CSC leaves auto start checked in odin option.
10- It will restart open magisk activated Zygisk restart install safetynet modules - shamiko-hidemagisk prop config-busybox nk-lposed see on this page https://forum.xda-developers.com/t/discussion-magisk-the-age -of-zygisk.4393877/
message #3-#6 to #9.
11- Install foxmagiskmodulemanager the catalog of modules for magisk here https://github.com/Fox2Code/FoxMagiskModuleManager/releases
12- Once rooted the security message for the removed open Odin place UP-param.tar in AP and flashed. See attached file
Up_param.tar download link on my mega here to know for S10 exynos for S10e- S10+ versions see 5G I don't know if it works.

Is this normal I have to wait about 30 minutes after power off to try get into download mode??

Maybe something is broken the phone like doesn't turn off properly or something, have to wait sometimes one hour

Magisk 25.2 Installation Failed on Samsung A750GN

First for all before I start I would like to say that Im not good at tech or any stuff like this. I hope you guys can guide me.
This is my 3rd times re-rooted my Samsung A750GN but I don't know what the cause is. Yes I do read the magisk installation docs, what I missing here? In the log file show that failed because of "Permission Denied" but I don't know what should I do.
ISSUES
- Button Superuser and Modules are unable to click.
- Magisk Installed shown N/A.
IMAGES
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

You said third time, does that worked before?
also what is the process you are using to root your phone?

Hello zayne77, you are trying to install magisk by magisk no good must patched with magisk the official firmware AP.
As explained in instalation by John Wu there is a tutorial on this forum how to proceed with a search you find.
Type magisk in the forum search of the aura for the coversation thread dedicated to magisk.
https://topjohnwu.github.io/Magisk/install.html
[Updated September 2022] How to root A7 2018
Disclaimer Do this at your own risk as I will not be responsible for your bricking the phone or rendering it unusable. Proceed with caution! If you want to root stock and for some reason want to have the latest security update, you have a...
forum.xda-developers.com

aiSanaul said:
You said third time, does that worked before?
also what is the process you are using to root your phone?
Click to expand...
Click to collapse
No

meric57 said:
Hello zayne77, you are trying to install magisk by magisk no good must patched with magisk the official firmware AP.
As explained in instalation by John Wu there is a tutorial on this forum how to proceed with a search you find.
Type magisk in the forum search of the aura for the coversation thread dedicated to magisk.
https://topjohnwu.github.io/Magisk/install.html
[Updated September 2022] How to root A7 2018
Disclaimer Do this at your own risk as I will not be responsible for your bricking the phone or rendering it unusable. Proceed with caution! If you want to root stock and for some reason want to have the latest security update, you have a...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you brother, may I ask, in the instructions he giving at Rooting Phones -> steps -> 9. Add the recovery.tar file to the AP slot and press start
where the recovery.tar is coming from? I'm sorry, I know I just look like a idiot

zayne77 said:
No
Click to expand...
Click to collapse
EASIEST METHOD:
Download Magisk Canary Build from here: https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-debug.apk
Install and Open that app.
Go to magisk settings and enable canary.
Transfer AP file from stock firmware to phone.
Then patch the AP fine using Magisk Canary app.
Then flash it to your phone using Magisk.
Enjoy Magisk Root!
NOTE: using canary build because normal build will give patching errors, like one you got.

@aiSanaul right know my phone are already rooted but the issues is like I mentioned above. Do I need to unroot my device first?
EDIT: or I just need to repatch the AP file and flash it using Magisk again?

zayne77 said:
@aiSanaul right know my phone are already rooted but the issues is like I mentioned above. Do I need to unroot my device first?
EDIT: or I just need to repatch the AP file and flash it using Magisk again?
Click to expand...
Click to collapse
yea first flash stock AP file and then the patched one

zayne77 said:
@aiSanaul right know my phone are already rooted but the issues is like I mentioned above. Do I need to unroot my device first?
EDIT: or I just need to repatch the AP file and flash it using Magisk again?
Click to expand...
Click to collapse
I would say, Try both methods.
- Just flash the patched AP file without unrooting.
- First flash Stock AP file then boot into system, reboot to download mode and then flash patched AP file.
and See which one works for you.

Hello zayne77, once the AP patched with magisk must be transferred with adb pull as explained in John wu's installation. Then open odin put the 4 BL-AP files patched_magisk -CP and home CSC as you say it is already rooted so home CSC to not lose data.
ADB pull for the transfer of the patched app open command prompt path on your pc to transfer the patched file, then type this in command prompt
adb pull /sdcard/Download/name of patched .tar file

meric57 said:
Hello zayne77, once the AP patched with magisk must be transferred with adb pull as explained in John wu's installation. Then open odin put the 4 BL-AP files patched_magisk -CP and home CSC as you say it is already rooted so home CSC to not lose data.
ADB pull for the transfer of the patched app open command prompt path on your pc to transfer the patched file, then type this in command prompt
adb pull /sdcard/Download/name of patched .tar file
Click to expand...
Click to collapse
I believe this is mentioned in Magisk installation docs and I think that is how I root my Samsung A750 phone.
INFO: back in the day, I have no issues regarding of this (with older version of magisk) but when upgrade the latest version of magisk I'm not able to hide root from any apps (the button of Superuser is disable) but I just ignore that. Until this weeks I decide to re-root my A7 phone but facing this issues.
How I Root My Samsung A750GN​
This basically install a new firmware (Without Root):
I download new firmware from https://samfw.com/
Long press volume up to unlock the bootloader. For wipe data and automatically reboot.
Open Oden and add BL_A750XXX to BL slot; AP_A750XXX to AP slot and so on (including HOME_CSC to USERDATA slot)
Click Start and done.
Here are actually how I root:
Download the latest version of Magisk apk (version 25.2) and install.
Transfer the AP_A750XXX file from PC to phone by using adb push /file_path/AP_A750XXXX.tar.md5 /sdcard/Download/ (I also tried just using normal transfer).
Press the Install button in the Magisk card.
Choose “Select and Patch a File” in method, and select the AP tar file.
Start the installation and done.
Transfer the magisk_patched_[random_strings].tar to PC by using adb pull /sdcard/Download/magisk_patched_[random_strings].tar.
Open Oden and add BL_A750XXX to BL slot; magisk_pathched_[random_strings].tar file to AP slot; CP_XXX file to CP slot and so on (except I didn't add anything in USERDATA slot).
Click Start and done.
Install the latest version of Magisk app.
Wala, that's it ! I also transfer the magisk_patched_[random_strings].tar back to phone by using adb push /my_pc_path/magisk_patched.tar /sdcard/Download/[/CODE]

Hello zayne77, I put you my tutorial that I converted it into English.
I did like explaining just magisk 25.2 not installing TRWP .
1- The bootloader follow explanation Use vol down + vol up + USB cable plugged into a PC to boot the phone into download mode;
Long press vol up then confirm that you want to unlock the bootloader (this is only needed once);
* Please note that all your data will be erased, including internal memory, and the phone will restart!!
5- Let the phone start normally, go through the configuration and connect to the Internet (wireless or mobile data) in order to unlock
6- Make sure OEM Unlock is enabled in Developer Settings.
2- Once reboot install magisk 25.2 APK.
3- Download the official firmware on Samobile.com or frija you will find this on the forum.
4- Transfer the official firmware AP to the smartphone.
5- Open magisk recovery mode choose corrective mode choose the AP download press "let's go."
6- Once the modification is finished in the root directory, download a patched_magiskxxxx.img.tar file if found.
7- Transfer it with adb pull like this adb pull /sdcard/Download/patched_patched.magiskxxxx.img[.tar] you can rename it "patched_magisk.img.tar"
8- Put your smartphone in download mode Use vol down + vol up + usb cable connected to a PC to start the phone in download mode, briefly press vol up to
confirm that you want to enter download mode;
9- Open Odin latest version placed 4 files following BL-AP magisk patched.img.tar-CP-home CSC leaves auto start checked in odin option.
10- It will restart open magisk activated Zygisk restart install safetynet modules - shamiko-hidemagisk prop config-busybox nk-lposed see on this page https://forum.xda-developers.com/t/discussion-magisk-the-age -of-zygisk.4393877/
message #3-#6 to #9.
11- Install foxmagiskmodulemanager the catalog of modules for magisk here https://github.com/Fox2Code/FoxMagiskModuleManager/releases
12- Once rooted the security message for the removed open Odin place UP-param.tar in AP and flashed. See attached file
Up_param.tar download link on my mega here to know for S10 exynos for S10e- S10+ versions see 5G I don't know if it works.