Database Develop

[Tutorial][How to] Unlock Bootloader and Install Custom Recovery and Root

Hello,
I know there are some tutorials for this already but I felt like they missed out a few steps that might not be obvious to some who are new to this.
This tutorial applies to all of Android One Device (Micromax Canvas A1, Karbonn Sparkle V Blue, Spice Mi-498 Dream Uno).
Unlocking bootloader will lead to formating of your phone. The stuff inside your sd card is safe but all your apps and their data will be deleted.
Unlocking bootloader:
1. Download Universal ADB Driver installer from here.
2. Connect your phone and run the Universal ADB Driver installer. Click 'Install' button and a warning should pop up. Just click "Install anyway" and it should look like this:
{
"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"
}
3. Download ADT Bundle from here for Win-32 Bit and from here for 64-Bit . If you are unsure which version of windows you have just download the 32-Bit one.
4. Extract the zip file in your C:\ drive like this (You can install it wherever you like but this tutorials assumes this location for simplicity). Add adb and fastboot to system path by following this tutorial . This will allow you to run adb and fastboot commands from any location on cmdline.
3. Switch off your phone. Now, Press POWER BUTTON + VOLUME UP button for about 5 seconds. A menu should appear. Note: VOLUME UP allows to navigate the menu (move down the menu). Press VOLUME DOWN button for selecting/choosing fastboot. On your phone, it should say something like
Code:
=> FASTBOOT MODE...
Connect your phone to the computer if it wasn't already.
4. (Assuming Win 7) Click on start menu > Search for 'Command Prompt' and right click and select 'Run as Administrator'.
5. On command prompt, Type:
Code:
fastboot devices
If it shows something, that means we can proceed to unlocking bootloader. Otherwise, it means that the driver was not installed correctly.
6. Now, Type the following commands:
Code:
fastboot oem unlock
fastboot format userdata
fastboot reboot
Now, your bootloader is unlocked.
Install a custom recovery.
1. Download custom recovery from this thread.
2. Place the download file, 'recovery.img' file in C:\ drive. (Again, you can place it anywhere but this tutorial assumes this path).
3. Run the following command (Assuming already in fastboot mode again. If not, follow the above steps to go to fastboot mode). :
Code:
fastboot flash recovery c:\recovery.img
After doing so, it should look like this:
4. Reboot your phone and you are done by typing:
Code:
fastboot reboot
Now, you have installed CWM custom recovery. On to installing root.
Rooting your phone:
1. After installing custom recovery, download Super-Su .zip file.
2. Place the .zip file on your sd-card. If your computer doesn't show your phone as MTP device, download the drivers from here.
3. Boot into recovery, by pressing POWER OFF + Volume UP button for 5 secs and choosing Recovery by pressing Volume Down (NOTE: Use Volume UP for menu navigation)
4. After booting into recovery, Choose 'Install Zip'. You can use Volume UP and Volume Down for navigating here and Power Off button for selecting a menu item.
5. Now, select 'choose zip from /external_sd' and not '/sdcard'
6. Select the Super-Su zip file you placed on your sd card and install it.
Now, Reboot your phone. It might say something like 'su may have been removed' but ignore and press 'No'.
Tutorial Complete
Let me know if there are any errors in this Tutorial.

Hi, thanks for the tutorial. Can you explain the necessity for using "fastboot format userdata" given "oem unlock" command in addition to unlocking the bootloader clears user data.

littleromeo said:
Hi, thanks for the tutorial. Can you explain the necessity for using "fastboot format userdata" given "oem unlock" command in addition to unlocking the bootloader clears user data.
Click to expand...
Click to collapse
Someone in this thread reported that they got stuck on the recovery, meaning the phone boot normally.
The port maker for recovery for our phone mentioned formatting userdata command in his post, so I did the same. I didn't want newbies to experience any trouble.

nice guide ..
but I guess "add adb and fastboot to system path " shall be made optional .. this will make guide little simpler and shorter ..

Hey
Can anybody please insure any android device that has been successfully rooted by this method ? Also is waiting for towelroot worth it ??

tanuj123 said:
Can anybody please insure any android device that has been successfully rooted by this method ? Also is waiting for towelroot worth it ??
Click to expand...
Click to collapse
I have used this method myself, but I am also the OP so.... :victory:

Iam in a weird situation , I did flash many times before but I dont know how it made my device like this ... THE PROBLEM IS WITH DRIVERS and also SDcard
First I unlocked my bootloader then flashed cm11 on it ( Which was on lollipop official) and I forgot to download gapps so in connected my phone to pc only to find my computer doesnt recognise my phone it make sound but nothing shows up I tried clicking MTP again and again but nothing happens , WHEN I TRIED ADB it shows no devices in the list , I took out the sd card to copy files manually and the sd card says its write protected ..... GUYS HELP @stirredo

What are you using to read your SD card on your computer?
If you are using SD card adapter, make the sure write lock is turned off.

Man thankyou but After installing the driver you gave my phone gets detected by pc but only when I turn on usb debugging @stirredo
Sent from my Xperia P using XDA Free mobile app

Kaushik124 said:
Man thankyou but After installing the driver you gave my phone gets detected by pc but only when I turn on usb debugging
Sent from my Xperia P using XDA Free mobile app
Click to expand...
Click to collapse
That is the same issue faced by me .

Saurabh K said:
That is the same issue faced by me .
Click to expand...
Click to collapse
Did you find any solution
Sent from my Xperia P using XDA Free mobile app

Not yet, but trying....
Sent from my Sparkle V

thanks for this awesome tutuorial.... But i have a problem in unlocking the tutorial
The problem is that how can i unlock my bootloader when oem unlocking is turned off...
Recently i tried to flash CM12.1 on my YU YUNIQUE YU4711 without turning on OEM unlocking and now I am stuck at the Fastboot mode so i cant start up my phone.... So i wanted to know that how i can unlock the bootloader when OEM unlocking is turned off..
PS- I cant even go to recovery moded
thanks in advance

Format Userdata
stirredo said:
Someone in this thread reported that they got stuck on the recovery, meaning the phone boot normally.
The port maker for recovery for our phone mentioned formatting userdata command in his post, so I did the same. I didn't want newbies to experience any trouble.
Click to expand...
Click to collapse
I did got stuck at bootloader when I dedn't format Userdata. Thanx for the tip.
---------- Post added at 03:01 PM ---------- Previous post was at 02:53 PM ----------
When I opened SuperSu after installing SuperSu through recovery, it says "There is no SU binary installed, and SuperSU cannot install it. This is a problem! If you just upgraded to Android 4.3, you need to manually re-root - consult the relevant forums for your device!"
What do I do now?

stirredo said:
Hello,
I know there are some tutorials for this already but I felt like they missed out a few steps that might not be obvious to some who are new to this.
This tutorial applies to all of Android One Device (Micromax Canvas A1, Karbonn Sparkle V Blue, Spice Mi-498 Dream Uno).
Unlocking bootloader will lead to formating of your phone. The stuff inside your sd card is safe but all your apps and their data will be deleted.
Unlocking bootloader:
1. Download Universal ADB Driver installer from here.
2. Connect your phone and run the Universal ADB Driver installer. Click 'Install' button and a warning should pop up. Just click "Install anyway" and it should look like this:
3. Download ADT Bundle from here for Win-32 Bit and from here for 64-Bit . If you are unsure which version of windows you have just download the 32-Bit one.
4. Extract the zip file in your C:\ drive like this (You can install it wherever you like but this tutorials assumes this location for simplicity). Add adb and fastboot to system path by following this tutorial . This will allow you to run adb and fastboot commands from any location on cmdline.
3. Switch off your phone. Now, Press POWER BUTTON + VOLUME UP button for about 5 seconds. A menu should appear. Note: VOLUME UP allows to navigate the menu (move down the menu). Press VOLUME DOWN button for selecting/choosing fastboot. On your phone, it should say something like
Code:
=> FASTBOOT MODE...
Connect your phone to the computer if it wasn't already.
4. (Assuming Win 7) Click on start menu > Search for 'Command Prompt' and right click and select 'Run as Administrator'.
5. On command prompt, Type:
Code:
fastboot devices
If it shows something, that means we can proceed to unlocking bootloader. Otherwise, it means that the driver was not installed correctly.
6. Now, Type the following commands:
Code:
fastboot oem unlock
fastboot format userdata
fastboot reboot
Now, your bootloader is unlocked.
Install a custom recovery.
1. Download custom recovery from this thread.
2. Place the download file, 'recovery.img' file in C:\ drive. (Again, you can place it anywhere but this tutorial assumes this path).
3. Run the following command (Assuming already in fastboot mode again. If not, follow the above steps to go to fastboot mode). :
Code:
fastboot flash recovery c:\recovery.img
After doing so, it should look like this:
4. Reboot your phone and you are done by typing:
Code:
fastboot reboot
Now, you have installed CWM custom recovery. On to installing root.
Rooting your phone:
1. After installing custom recovery, download Super-Su .zip file.
2. Place the .zip file on your sd-card. If your computer doesn't show your phone as MTP device, download the drivers from here.
3. Boot into recovery, by pressing POWER OFF + Volume UP button for 5 secs and choosing Recovery by pressing Volume Down (NOTE: Use Volume UP for menu navigation)
4. After booting into recovery, Choose 'Install Zip'. You can use Volume UP and Volume Down for navigating here and Power Off button for selecting a menu item.
5. Now, select 'choose zip from /external_sd' and not '/sdcard'
6. Select the Super-Su zip file you placed on your sd card and install it.
Now, Reboot your phone. It might say something like 'su may have been removed' but ignore and press 'No'.
Tutorial Complete
Let me know if there are any errors in this Tutorial.
Click to expand...
Click to collapse
bro, my bootloader is already unlocked, so i was using the flash recovery command directly, and i was unable to flash recovery, everytime i go into recovery it opens stock recovery, what should i do to flash recovery now, no method is working, is it compulsary to unlock bootloader every time flashing recovery, mine is already unlocked, but cant able to flash recovery, please help ,its urgent.

I am on a custom ROM right now( Resurrection ) and have unlocked the bootloader
Can I relock the bootloader using Androidone tool
Will it format userdata?
Can I keep the Custom ROM after relocking?
Please help
Device-Mi-498

hi my device is not boot after restart.always need to run fastboot continue. have you any idea how to resolved ?

my phone showing device not found error in ADB driver installer. actually phone is unable to start, it is continuously looping in start logo

is the fastboot format userdata command required? what will happen if i fail to issue the fastboot format command following fastboot oem unlock command?

hello i want the unlocked bootloader file for my Micromax e313 please send me the link to get it please help me

[GUIDE] Gain Root Access v3 (3 Methods!)

Hello people,
This is for Mi Note Pro (leo)
Disclaimer:
I'm not responsible for any devices being bricked, your device blowing up or world war 3 starting! You are doing this at your own risk.
Click to expand...
Click to collapse
A lot of people ask how to gain root on the Mi Note Pro without actually searching the posts so I decided to make a quick tutorial on how to do it. This is the way I have done it and I have found it to be the easiest way!
1st Method (THE EASIEST AND SAFEST!)
1. Go to http://en.miui.com/download-273.html and download the Developer ROM
{
"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"
}
2. If you have downloaded the file through your phone it will be in the Download folder, if not plug your phone into the PC and move the .zip file over to your device.
3. Open Updater app, tap on 3 dots to open the menu and tap on Choose update package
4. Navigate to where you have put in the zip file and click on it and let the phone update. (This will wipe all your data apart from pictures etc.)
5. Once it has loaded go through the setup. Open Security app > Permissions > Root Access.. There you are all done
Make sure you open an app that requires root access first before going to Security app as it will not show up on there.
2nd Method (Advanced Users!)(Temporary TWRP Recovery)
Requirements:
fastboot driver (Link attached)
twrp.img - https://mega.nz/#!nR0jHZqL!2cksl ... 5H76ut8UVtnu97HHAEo
supersu - https://download.chainfire.eu/740/SuperSU/BETA-SuperSU-v2.49.zip
common sense
mi note pro!
1. First of all download all the things you need. Which are fastboot driver, twrp and supersu. All links are above ^ Copy SuperSu over to your device and keep other files on your PC
2. Power off your device and turn it back on by holding Power button and Volume Down at the same time. This will get you into fastboot menu.
3. Woohoo great now what you will have to do is plug your phone to your PC using a usb cable.
4. Open up the Command Promt and navigate to the location of your fastboot driver. Mine is C:/adb so I would type cd C:/adb in the command promt
5. Now type in fastboot devices just to make sure that your device is listed correctly.
6. Extract the TWRP zip so you have just the .img file. Place it inside same folder as fastboot. I tend to rename it to twrp.img (makes lifes easier)
7. Type fastboot boot twrp.img
8. Now your phone should boot into TWRP!! Go to install and flash the SuperSU zip.
9. Reboot and you are all rooted with Stock Recovery and Stable ROM!
3rd Method (Advanced Users!)(Permanent TWRP Recovery)
Requirements:
fastboot driver
twrp.img - https://mega.nz/#!nR0jHZqL!2ckslQxV-ODWnswRYpfDCp2M5H76ut8UVtnu97HHAEo
supersu - https://download.chainfire.eu/740/SuperSU/BETA-SuperSU-v2.49.zip
common sense
mi note pro!
1. First of all download all the things you need. Which are fastboot driver, twrp and supersu. All links are above ^ Copy SuperSu over to your device and keep other files on your PC
2. Power off your device and turn it back on by holding Power button and Volume Down at the same time. This will get you into fastboot menu.
3.Woohoo great now what you will have to do is plug your phone to your PC using a usb cable.
4. Open up the Command Promt and navigate to the location of your fastboot driver. Mine is C:/adb so I would type cd C:/adb in the command promt
5. Now type in fastboot devices just to make sure that your device is listed correctly.
6. Extract the TWRP zip so you have just the .img file. Place it inside same folder as fastboot. I tend to rename it to twrp.img (makes lifes easier)
7. Type fastboot flash recovery twrp.img
8. Now your phone should boot into TWRP!! Go to install and flash the SuperSU zip.
9. Reboot and you are all rooted with TWRP recovery, the only problem is that your OTA updates will break. You can flash them manually, when Updater downloads an update go into TWRP>Install and navigate to downloaded_rom folder
In case you need to go back to stock Recovery because you have flashed TWRP Permanently please follow instructions on this thread.http://en.miui.com/thread-124319-1-1.html

GREAT! EASY!
Need to wipe cache or data?

Nope no need to do that

nice thanks for the advice

I followed ur step but no show root access...
Did I miss anything?

Absent6775 said:
I followed ur step but no show root access...
Did I miss anything?
Click to expand...
Click to collapse
Yea step 5

Absent6775 said:
I followed ur step but no show root access...
Did I miss anything?
Click to expand...
Click to collapse
Well their Root Access works a bit different to SuperSU instead of popping up with a box promting you to give root access what you have to do is open the app the requires root access, do an action that needs root access then you go to Security > Premissions > Root Access and you have to grant it then.

Is only way to root to do a full wipe?
Can we still do normal updates after installing this developer rom?

Yup you get newest weekly updates and they work perfectly fine! I'm on 5.7.2 currently

Updated.

Is it equally safe to flash the latest 1.0.0 supersu from chainfire? Is there any compatibility constraints? or are all version compatible with all devices? thanks for shedding some light into this

Can you use Flashify and install twrp and supersu or is supersu not needed using method 1? ?
sent from mobile thingy

Super su is not needed using method 1 as they use their own root manager.

Kahun said:
Super su is not needed using method 1 as they use their own root manager.
Click to expand...
Click to collapse
How to unroot in method 2 ?
Incase I want to sell this phone so the warranty still valid to the new owner.

deddo86 said:
How to unroot in method 2 ?
Incase I want to sell this phone so the warranty still valid to the new owner.
Click to expand...
Click to collapse
Just flash stable ROM.

Added a permanent recovery method but "might" break OTA

Problem with Method 1
Hi People /Mr. Kahun ,
I'm absolutely new but i would like to root my :
Mi Note Pro
Android 5.0.2.
MIUI 66.55.44.00
because some original programs make me creasy . I tried method 1. I followed your steps, i downloaded different DEVELOPER Rom (5.9.10 and 5.9.17) , but i had always with the step 4 the message GETTING INFO ..... and this is the end of the process .....
PLEASE PLEASE tell ma what can i do to root the device .
Thank you in advance

Try installing HappyMIUI rom from the android development section.

i don't know how to install .....i will try method 2.
thank you Kahun!

where can i find the fastboot driver (Link is NOT attached)

Question How to flash twrp recovery and root redmi note 10s?

I can't install a twrp recovery if I tried
A message appears (remote : this partition doesn't exist)

You wont be able to find rosemary's twrps yet... But you can root this model unlocking bootloader and flashing a modified boot.img from magisk APK, you can follow this instructions to do that; (you'll need the redmi note 10 s original rom firmware to extract the boot img and you can get it from here: https://c.mi.com/es/miuidownload/detail?device=1900397)
First, extract the boot.img file from Redmi Note 10 firmware. You can use 7Zip or WinRAR.​
Now install the Magisk Manager app on your phone.​
Open the Magisk Manager app and click on the Install.
{
"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"
}
In the next step choose ‘Select and Patch a File’ from the option.
Browse and select the boot.img file, and it will start patching the boot image.​
The output file will be stored in the download folder with the name magisk_patched.img.​
Copy the patched boot image file to your computer in folder C:\adb. Also, rename the patched file to boot.img.​
Reboot your Redmi Note 10 to Fastboot mode and connect it to your computer.​
In the C:\adb folder (or platform-tools folder) press Shift + Right click on an empty area and select ‘Open Command window here’ or ‘Open PowerShell window here.’
You can check if the device is connected or not by entering the below command that should return some device id.​
fastboot devices​
Now enter the below command to flash Magisk and root Redmi Note 10.​
fastboot flash boot boot.img​
After flashing the patched boot image. reboot your device to the system.​
Install Magisk Manager if it’s not already installed.​
Complete the in-app instructions, and the device will automatically reboot into the system.​
That’s all, now your phone is rooted. You can check for root access using any root checker app. And once you have root access on your Redmi Note 10, you can enjoy all the apps and features that require root access. As you know Xiaomi phones show ads on some system apps that you can disable with root access. You can use different Xposed Modules to customize your phone. Also, you can install Xposed Framework on your phone to use modules.
Or if your system has an a/b partition you'll have to type this on your command window:
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img

Or follow this page... https://mytechgyangadgets.com/how-to-root-redmi-note-10s-via-magisk-and-supersu/

Ali mohamed 96 said:
I can't install a twrp recovery if I tried
A message appears (remote : this partition doesn't exist)
Click to expand...
Click to collapse
Theres 2 ways to do It explained up but i prefer first one

This is a questionable part I think:
1. If your phone doesn’t have A/B partition system:
fastboot flash boot boot.img
2. If your phone has A/B partition system:
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
Based on the Treble Check app, at least my phone, supported Seamless System Updates and is detected to have an A/B system partition => should be used 2?
This might be a reason of : "this partition doesn't exist" with 1.
Source: https://www.naldotech.com/root-xiaomi-redmi-note-10s-magisk/

#bosr you have to follow the second step pf your post yo success, It seems that note's 10 has an a/b system partition...

!! Success !!
The process I´ve rooted my Redmi Note 10s with V12.5.8.0.RKLEUXM ROM:
(besides all needed drivers, adbs, proper fasboot ROM version, unlocked bootloader, little bit of a fear that the phone could be hard bricked and a few more) :
- patched boot.img via magisk manager v23
- flashed empty vbmeta.img as decribed here https://forum.xda-developers.com/t/root-gained.4290689/
- flashed patched_boot.img (the latest platform-tools flashed it directly to boot_a)
- reboot
Voila, Redmi Note 10s is rooted and Magisk v23 installed

Ricardo 182 said:
You wont be able to find rosemary's twrps yet... But you can root this model unlocking bootloader and flashing a modified boot.img from magisk APK, you can follow this instructions to do that; (you'll need the redmi note 10 s original rom firmware to extract the boot img and you can get it from here: https://c.mi.com/es/miuidownload/detail?device=1900397)
First, extract the boot.img file from Redmi Note 10 firmware. You can use 7Zip or WinRAR.​
Now install the Magisk Manager app on your phone.​
Open the Magisk Manager app and click on the Install.
In the next step choose ‘Select and Patch a File’ from the option.
Browse and select the boot.img file, and it will start patching the boot image.​
The output file will be stored in the download folder with the name magisk_patched.img.​
Copy the patched boot image file to your computer in folder C:\adb. Also, rename the patched file to boot.img.​
Reboot your Redmi Note 10 to Fastboot mode and connect it to your computer.​
In the C:\adb folder (or platform-tools folder) press Shift + Right click on an empty area and select ‘Open Command window here’ or ‘Open PowerShell window here.’
You can check if the device is connected or not by entering the below command that should return some device id.​
fastboot devices​
Now enter the below command to flash Magisk and root Redmi Note 10.​
fastboot flash boot boot.img​
After flashing the patched boot image. reboot your device to the system.​
Install Magisk Manager if it’s not already installed.​
Complete the in-app instructions, and the device will automatically reboot into the system.​
That’s all, now your phone is rooted. You can check for root access using any root checker app. And once you have root access on your Redmi Note 10, you can enjoy all the apps and features that require root access. As you know Xiaomi phones show ads on some system apps that you can disable with root access. You can use different Xposed Modules to customize your phone. Also, you can install Xposed Framework on your phone to use modules.
Or if your system has an a/b partition you'll have to type this on your command window:
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
Click to expand...
Click to collapse
"
First, extract the boot.img file from Redmi Note 10 firmware. You can use 7Zip or WinRAR."
I am not able to see boot.img file in the extracted rom. I used the same link that you had shared to download the rom. This is the file name - miui_ROSEMARYINGlobal_V12.5.5.0.RKLINXM_ab4be8a721_11.0.zip.
What is the mistake I am making?

GildroY said:
"
First, extract the boot.img file from Redmi Note 10 firmware. You can use 7Zip or WinRAR."
I am not able to see boot.img file in the extracted rom. I used the same link that you had shared to download the rom. This is the file name - miui_ROSEMARYINGlobal_V12.5.5.0.RKLINXM_ab4be8a721_11.0.zip.
What is the mistake I am making?
Click to expand...
Click to collapse
Also checked the global rom from here https://xiaomifirmwareupdater.com/miui/rosemary/stable beta/V12.5.12.0.RKLMIXM/
Same thing - cant find the boot.img

GildroY said:
Also checked the global rom from here https://xiaomifirmwareupdater.com/miui/rosemary/stable beta/V12.5.12.0.RKLMIXM/
Same thing - cant find the boot.img
Click to expand...
Click to collapse
You are searching in the wrong type of ROM. It must be the fastboot type.
for example: rosemary_global_images_V12.5.11.0.RKLMIXM_20210618.0000.00_11.0_global_06239807c1.tgz
Unpack (winrar, winzip, 7-zip ...) it, there is a folder images and boot.img in it
Do not forget to flash empty vbmeta.img first, see here

bosr said:
You are searching in the wrong type of ROM. It must be the fastboot type.
Unzip it, there is a folder images and boot.img in it
Click to expand...
Click to collapse
Yeah. Apologies. Just realized it.

I was able to successfully get root access using the additional step mentioned by @bosr (Thanks a lot for that). However post that I literally bricked my device trying to debloat the device by using debloater. Post removing few of the mi bloatware apps, when I rebooted and the device kept on going into default mi recovery (even with power + vol-). I was not able to access the fastboot mode at all, no matter what I do.
Then I did the ultimate blunder ... reset the device from mi recovery. Post that I lost adb privileges as well. Besides the phone would still not boot - MIUI logo flashed with sound, then a white setup screen for a sec and again reboot.
Searching online could not fetch anything. Then I tried moving the phone to mi assistance mode from mi recovery (which is nothing but sideload mode), connect to PC and used 'adb sideload'.
Voila, the phone was detected, from sideload mode, I was able to reboot to fastboot mode, and then flash the stock rom using miflashtool. Whole 4 hours of tussle.
Sharing here, just in case someone else, gets into the same situation.
!! BADLY WAITING FOR A CLEAN ROM FOR THIS DEVICE .... <Prayers>!!

It is strange.
I did it on two "10s" devices with EAA roms w/o problems.
Did you flash flash empty vbmeta.img first and boot.img than?
Did you use the latest platform-tools as previous ones are not able to flash directly to boot_a) automatically and you must use fastboot flash boot_a command instead.

bosr said:
It is strange.
I did it on two "10s" devices with EAA roms w/o problems.
Did you flash flash empty vbmeta.img first and boot.img than?
Did you use the latest platform-tools as previous ones are not able to flash directly to boot_a) automatically and you must use fastboot flash boot_a command instead.
Click to expand...
Click to collapse
Apologies for incorrect use of language. What I meant was that your instructions were 100% correct and accurate. However, post getting root access successfully and magisk installed, I tried to debloat the device using 'debloater' module under Magisk and ended up deleting some rogue apps which Mi wants us to keep. All the issues happened after that.
I have updated my original comment as well.

OK. Apology accepted

Hi Y'all,
I just got a new Note 10s and I'm willing to root device.
I'm still in the phase of waiting for the unlocked bootloader, but already trying to get all the necessary data for root.
While searching for the fastbbot Rom to extract the boot.img I discovered the follwing problem:
I can only find the fastboot Rom for the following SW: V12.5.8.0.RKLEUXM
But my Note 10s is already on V12.5.10.0.RKLEUXM. For this SW only the recovery ROM is available.
How long will it take for Xiaomi to upload the latest fastboot ROM? Or am I doing something wrong,
Any help really appreciated
Andreas

I also got a new Note 10s. I updated it to the latest available version (12.5.8.0 RKLEUXM, EEA).
Downloaded these ROMs (recovery and fastboot):
miui_ROSEMARYEEAGlobal_V12.5.8.0.RKLEUXM_b29e7c6a8a_11.0.zip
rosemary_eea_global_images_V12.5.8.0.RKLEUXM_20210617.0000.00_11.0_eea_6ec37534bb.tgz
But I didn't found any boot.img in the last fastboot one.
Finally I extracted boot.img from the first one (recovery) using payload_dumper - but what's wrong with the easier and usual way to extract it from the fastboot ROM? Isn't it available anymore inside this ROM?
@Agzyx
You could try the payload_dumper method to extract boot.img from recovery ROM.

@Mac23
payload_dumper may be a solution. I need to wait another 5 days for bootloader unlock anyway, so I have some more time before trying to gain root access.
@All
Is there a way to "downgrade" to V12.5.8.0.RKLEUXM?
Loss of data is no problem, as the phone will be rooted anyway in the future.
Andreas

Agzyx said:
@Mac23
payload_dumper may be a solution. I need to wait another 5 days for bootloader unlock anyway, so I have some more time before trying to gain root access.
@All
Is there a way to "downgrade" to V12.5.8.0.RKLEUXM?
Loss of data is no problem, as the phone will be rooted anyway in the future.
Andreas
Click to expand...
Click to collapse
It should be possible with XiaoMiTool

Mac23 said:
I also got a new Note 10s. I updated it to the latest available version (12.5.8.0 RKLEUXM, EEA).
Downloaded these ROMs (recovery and fastboot):
miui_ROSEMARYEEAGlobal_V12.5.8.0.RKLEUXM_b29e7c6a8a_11.0.zip
rosemary_eea_global_images_V12.5.8.0.RKLEUXM_20210617.0000.00_11.0_eea_6ec37534bb.tgz
But I didn't found any boot.img in the last fastboot one.
Finally I extracted boot.img from the first one (recovery) using payload_dumper - but what's wrong with the easier and usual way to extract it from the fastboot ROM? Isn't it available anymore inside this ROM?
@Agzyx
You could try the payload_dumper method to extract boot.img from recovery ROM.
Click to expand...
Click to collapse
Not sure, what you are looking for, but boot.img is in the fastboot rom:

[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?

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.