Database Develop

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

[tutorial] root samsung galaxy a6 plus a605g

DISCLAIMER This is the method which worked personally for me after trying out a number of attempts. Try at your own risk. I am not responsible for any bricked devices.
First of all I would like to appreciate @topjohnwu for his amazing Magisk Project and being wonderful people around in XDA. It is because of the Magisk project that the A6 plus got root although having no stable twrp.
Directions
First of all you need to download the following files :
Latest version of ODIN
7Z Zstandard
Samsung USB Drivers
Stock Firmware of your model ( Use Sammobile or Updato)
Magisk Manager v6.0.0 apk ( https://******************/ or xda thread )
After downloading all of these tools, install 7zip Zstandard , Odin and Samsung USB driver in your Pc or Laptop. After that you need to extract your stock firmware if it's in compressed zip with 7zip. Now , there will be 5 files AP, BL, CSC, HOME CSC and CP. You need to extract AP file to get boot.img of your device . Select the AP file , right click > 7zip Zstandard > Extract Here.
Once decompressed you will find your boot.img.lz4 in there. again extract it using 7zip Zstandard and you will get your boot.img .Now transfer this boot.img to your android device.
Install Magisk Manager latest version (v6.0.0 as of now) in your phone and got to settinngs and select patched boot output format to img.tat . Return to the homepage of app and tap on install now. From the two options, select Patch boot image and browse to your boot.img. From here, a black terminal will appear and Magisk will download the root zip and patch your boot image to be ready for Magisk su. Once it is done with the process, it will show you the location if the patched image file. Now, Copy this patched image to your desktop and make sure you have both, the stock boot.img and the patched boot.img in case something goes wrong. In your device go to Settings > About Phone > Software Information and tap on the Build number for around 7 times until it shows “Developer settings has been turned on” . Now come again to the settings of your device and move to bottom. Below About Phone you will find Developer Settings. Go and tick on OEM Unlock there . It will ask for a reboot , allow it to perform that. Now follow the final steps given below:
1) Download Odin to your laptop/PC.
2) Turn off your phone.
3) Go to download mode (by pressing Volume down+Volume up buttons together and then connect the USB cable)
4)Press the Volume up button to continue.
5)Open Odin on your laptop/pc.
6) Connect your phone to your laptop/PC through USB cable.
7) When ODIN detects your phone, It will show added in the Log.
8) In ODIN click on AP and then select the patched boot.img file you created.
9) Click on start. The flashing process will start.
10) If the flashing succeeds, ODIN will show 'PASS'. That means the boot image flashed successfully.
11) After it finishes, go back and reboot your phone.
Enjoy your rooted Samsung Galaxy A6 PLUS !!!
{
"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"
}

Thanks bro for the root method and detailed tutorial.. will i have to follow the same steps to root my sm-a605f device !!

kifayat83 said:
Thanks bro for the root method and detailed tutorial.. will i have to follow the same steps to root my sm-a605f device !!
Click to expand...
Click to collapse
Ys

kifayat83 said:
Thanks bro for the root method and detailed tutorial.. will i have to follow the same steps to root my sm-a605f device !!
Click to expand...
Click to collapse
Hello
Did you try this method?
Plz inform me if it worked for you

My OEM unlock option gone. try to reflash patched boot img but got an error iyhat only official binary can be flash

badagila said:
My OEM unlock option gone. try to reflash patched boot img but got an error iyhat only official binary can be flash
Click to expand...
Click to collapse
Hi
Does this method work for you?
pinoy here
thankz
---------- Post added at 13:36 ---------- Previous post was at 13:02 ----------
Dev-sahil (Devil) said:
DISCLAIMER This is the method which worked personally for me after trying out a number of attempts. Try at your own risk. I am not responsible for any bricked devices.
First of all I would like to appreciate @topjohnwu for his amazing Magisk Project and being wonderful people around in XDA. It is because of the Magisk project that the A6 plus got root although having no stable twrp.
Directions
First of all you need to download the following files :
Latest version of ODIN
7Z Zstandard
Samsung USB Drivers
Stock Firmware of your model ( Use Sammobile or Updato)
Magisk Manager v6.0.0 apk ( https://******************/ or xda thread )
After downloading all of these tools, install 7zip Zstandard , Odin and Samsung USB driver in your Pc or Laptop. After that you need to extract your stock firmware if it's in compressed zip with 7zip. Now , there will be 5 files AP, BL, CSC, HOME CSC and CP. You need to extract AP file to get boot.img of your device . Select the AP file , right click > 7zip Zstandard > Extract Here.
Once decompressed you will find your boot.img.lz4 in there. again extract it using 7zip Zstandard and you will get your boot.img .Now transfer this boot.img to your android device.
Install Magisk Manager latest version (v6.0.0 as of now) in your phone and got to settinngs and select patched boot output format to img.tat . Return to the homepage of app and tap on install now. From the two options, select Patch boot image and browse to your boot.img. From here, a black terminal will appear and Magisk will download the root zip and patch your boot image to be ready for Magisk su. Once it is done with the process, it will show you the location if the patched image file. Now, Copy this patched image to your desktop and make sure you have both, the stock boot.img and the patched boot.img in case something goes wrong. In your device go to Settings > About Phone > Software Information and tap on the Build number for around 7 times until it shows “Developer settings has been turned on” . Now come again to the settings of your device and move to bottom. Below About Phone you will find Developer Settings. Go and tick on OEM Unlock there . It will ask for a reboot , allow it to perform that. Now follow the final steps given below:
1) Download Odin to your laptop/PC.
2) Turn off your phone.
3) Go to download mode (by pressing Volume down+Volume up buttons together and then connect the USB cable)
4)Press the Volume up button to continue.
5)Open Odin on your laptop/pc.
6) Connect your phone to your laptop/PC through USB cable.
7) When ODIN detects your phone, It will show added in the Log.
8) In ODIN click on AP and then select the patched boot.img file you created.
9) Click on start. The flashing process will start.
10) If the flashing succeeds, ODIN will show 'PASS'. That means the boot image flashed successfully.
11) After it finishes, go back and reboot your phone.
Enjoy your rooted Samsung Galaxy A6 PLUS !!!
Click to expand...
Click to collapse
Hi sir..
i want to try this method but the problem is when i try to unlock OEM...
its says that it will reset my phone to its factory settings
did this method still works if i do that?
before, unlocking oem will just restart your device but now it will reset to factory defaults..
Im using android security patch level (July 1,2018)

Not sure it worked
Hello,
Thank you for the tutorial.
I tried this method, and seems like it didn't work. I'm not really sure, beause I used one root checker app, and it says it's not rooted, and used another one that said it is :silly:
Anyway I installed titanium backup that said root is not granted, although on the bootup image of the phone the're's something written in yellow.
And more, I cannot log in to my samsung account anymore, seems I'm in to flash again.
Edit : My phone is an a605F, but I think it doesn't matter.

Dev-sahil (Devil) said:
DISCLAIMER This is the method which worked personally for me after trying out a number of attempts. Try at your own risk. I am not responsible for any bricked devices.
First of all I would like to appreciate @topjohnwu for his amazing Magisk Project and being wonderful people around in XDA. It is because of the Magisk project that the A6 plus got root although having no stable twrp.
Directions
First of all you need to download the following files :
Latest version of ODIN
7Z Zstandard
Samsung USB Drivers
Stock Firmware of your model ( Use Sammobile or Updato)
Magisk Manager v6.0.0 apk ( https://******************/ or xda thread )
After downloading all of these tools, install 7zip Zstandard , Odin and Samsung USB driver in your Pc or Laptop. After that you need to extract your stock firmware if it's in compressed zip with 7zip. Now , there will be 5 files AP, BL, CSC, HOME CSC and CP. You need to extract AP file to get boot.img of your device . Select the AP file , right click > 7zip Zstandard > Extract Here.
Once decompressed you will find your boot.img.lz4 in there. again extract it using 7zip Zstandard and you will get your boot.img .Now transfer this boot.img to your android device.
Install Magisk Manager latest version (v6.0.0 as of now) in your phone and got to settinngs and select patched boot output format to img.tat . Return to the homepage of app and tap on install now. From the two options, select Patch boot image and browse to your boot.img. From here, a black terminal will appear and Magisk will download the root zip and patch your boot image to be ready for Magisk su. Once it is done with the process, it will show you the location if the patched image file. Now, Copy this patched image to your desktop and make sure you have both, the stock boot.img and the patched boot.img in case something goes wrong. In your device go to Settings > About Phone > Software Information and tap on the Build number for around 7 times until it shows “Developer settings has been turned on” . Now come again to the settings of your device and move to bottom. Below About Phone you will find Developer Settings. Go and tick on OEM Unlock there . It will ask for a reboot , allow it to perform that. Now follow the final steps given below:
1) Download Odin to your laptop/PC.
2) Turn off your phone.
3) Go to download mode (by pressing Volume down+Volume up buttons together and then connect the USB cable)
4)Press the Volume up button to continue.
5)Open Odin on your laptop/pc.
6) Connect your phone to your laptop/PC through USB cable.
7) When ODIN detects your phone, It will show added in the Log.
8) In ODIN click on AP and then select the patched boot.img file you created.
9) Click on start. The flashing process will start.
10) If the flashing succeeds, ODIN will show 'PASS'. That means the boot image flashed successfully.
11) After it finishes, go back and reboot your phone.
Enjoy your rooted Samsung Galaxy A6 PLUS !!!
Click to expand...
Click to collapse
done SM-A605GN, thank you and here is binary 8 patched file to help others

''''''Samsung a6 plus sm 605gn root''''''
The Directoins give are 100% correct
Should work with right firmware
Majisk works and updates itself corectly
Majisk patches firmware app file corectly
Odin works corectly
Every 100% ok
'''''THE STUPID QUESTION''''
The Samsung a6 plus sm 605gn was brought ''NEW boxed 2 days ago'12th ..Aug..2022 '''(2019 new and never used)
Phone was flat needed 12 hours charge
As as phone booted it came up as Android 9 with 2019 patch
As soon as it found interest it started to update itself
After a hour it finished update and after final reboot
the a6 plus is now Android 10/10q with 2021 patch
The Stupid question is what firmware do I root with Android 9 or Android 10

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?

How To Guide [GUIDE] Beginner's guide on how to root Redmi Note 10 Pro (sweet) without TWRP

I decided to make this guide since I didn't see a guide thread which explains how to root the phone.
DISCLAIMER: I am not responsible for ANY damage that occurs to the phone, you getting fired because the alarm app failed or the world getting nuked, etc...
Requirements:
-A unlocked bootloader (if you don't know how to unlock it, search "How to unlock bootloader Xiaomi"
-boot.img extracted from your phone's fastboot rom (MAKE SURE YOU DOWNLOADED THE EXACT SAME ROM THAT YOUR PHONE HAS (Check "About phone" in settings. Make sure that the version AND the code (RK(something)XM) match, if you have MIUI).
xiaomifirmwareupdater site contains unmodified MIUI roms for your device.
-If you have a custom rom, extract the rom's zip and get the boot.img from there.
-ADB and Fastboot drivers installed on phone and PC
-SDK Platform tools downloaded from official android website. Extract the downloaded zip to desktop and rename it to platform_tools
-A Computer
-Basic understanding of CMD, ADB and Fastboot commands.
-The phone
If you see an error, scroll down to the troubleshooting section.
Steps:
(on the pc)
-Copy the boot.img file to the phone's downloads folder
(in the phone)
-Download the magisk app from the official github site
-Install the app, then open it.
-In the app, select install on the magisk card
{
"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"
}
-Select patch a file, then find and select boot.img.
-Tap "let's go".
(on the pc)
-Connect your phone to your PC and copy magisk_patched.img from the phone (should be in downloads folder) back to the pc.
-Rename the file to magisk.img, then move it to the platform_tools folder which contains fastboot.exe.
-Now reboot the phone and when the screen goes fully black, hold volume down button until you see "fastboot".
-Your phone should now be in fastboot mode. Connect the phone to the pc.
-Press win+r, then type cmd
-Type cd desktop
-Type cd platform_tools
-Type fastboot devices (if you see nothing, make sure you have adb and fastboot drivers, that the phone is connected and is in fastboot mode.)
-Type this carefully: fastboot flash boot magisk.img
-Done! Now reboot the phone by typing: fastboot reboot
-If you did everything correctly, the magisk app should say that it is installed.
TROUBLESHOOTING:
Q:Fastboot says it couldn't find "magisk.img" or CMD says fastboot doesn't exist
A: Make sure that cmd says that its in C:\Users\(name)\Desktop\platform_tools and that magisk.img is also in there.
Q: Phone is in bootloop
A: Hold volume down button until phone is in fastboot and flash stock boot.img with fastboot flash boot.img. (You will not have root access) If the phone is still somehow in a bootloop, execute the flash_all_except_storage.bat script by double clicking it (found in the sweet_(region)_images folder you extracted from the full fastboot rom .tgz file).

usernamenotrequired said:
I decided to make this guide since I didn't see a guide thread which explains how to root the phone.
DISCLAIMER: I am not responsible for ANY damage that occurs to the phone, you getting fired because the alarm app failed or the world getting nuked, etc...
Requirements:
-A unlocked bootloader
-boot.img extracted from your phone's fastboot rom (MAKE SURE YOU DOWNLOADED THE EXACT SAME ROM THAT YOUR PHONE HAS (Check "About phone" in settings. Make sure that the version AND the code (RK(something)XM) match, if you have MIUI).
xiaomifirmwareupdater site contains unmodified MIUI roms for your device.
-If you have a custom rom, extract the rom's zip and get the boot.img from there.
-ADB and Fastboot drivers installed on phone and PC
-SDK Platform tools downloaded from official android website. Extract the downloaded zip to desktop and rename it to platform_tools
-A Computer
-Basic understanding of CMD, ADB and Fastboot commands.
-The phone
If you see an error, scroll down to the troubleshooting section.
Steps:
(on the pc)
-Copy the boot.img file to the phone's downloads folder
(in the phone)
-Download the magisk app from the official github site
-Install the app, then open it.
-In the app, select install on the magisk card
View attachment 5474787
-Select patch a file, then find and select boot.img.
-Tap "let's go".
View attachment 5474793
(on the pc)
-Connect your phone to your PC and copy magisk_patched.img from the phone (should be in downloads folder) back to the pc.
-Rename the file to magisk.img, then move it to the platform_tools folder which contains fastboot.exe.
-Now reboot the phone and when the screen goes fully black, hold volume down button until you see "fastboot".
View attachment 5474801
-Your phone should now be in fastboot mode. Connect the phone to the pc.
-Press win+r, then type cmd
-Type cd desktop
-Type cd platform_tools
-Type fastboot devices (if you see nothing, make sure you have adb and fastboot drivers, that the phone is connected and is in fastboot mode.)
-Type this carefully: fastboot flash boot magisk.img
-Done! Now reboot the phone by typing: fastboot reboot
-If you did everything correctly, the magisk app should say that it is installed.
TROUBLESHOOTING:
Q:Fastboot says it couldn't find "magisk.img" or CMD says fastboot doesn't exist
A: Make sure that cmd says that its in C:\Users\(name)\Desktop\platform_tools and that magisk.img is also in there.
Qhone is in bootloop
A: Hold volume down button until phone is in fastboot and flash stock boot.img with fastboot flash boot.img. (You will not have root access) If the phone is still somehow in a bootloop, execute the flash_all_except_storage.bat script by double clicking it (found in the sweet_(region)_images folder you extracted from the full fastboot rom .tgz file).
Click to expand...
Click to collapse
Very good but easier with unlocked bootloader and flashing twrp via adb flash recovery "name of twrp file". Afterwards you can flash directly magisk (I prefer 23 canary debug apk) to root.

if i may add to the troubleshooting: if it says magisk.img isn't found, just type this (after confirming connection with fastboot devices command:
fastboot flash boot
then drag and drop the patched magisk file onto the cmd window/line where you typed the command above. worked for me.

Tanks you

For beginners, "assuming bootloader is unlocked if not click here" should be mentioned.

hello, I've been trying to login to my account since this morning. after half a day I was able to get in via facebook. problem is when i want to root my phone it shows error 1004. what did I do wrong?

Bastio001 said:
hello, I've been trying to login to my account since this morning. after half a day I was able to get in via facebook. problem is when i want to root my phone it shows error 1004. what did I do wrong?
Click to expand...
Click to collapse
I've searched around, and it seems to be caused by a VPN. If you use a VPN, turn it off and try again. If not, it could be that the Xiaomi unlocking API is down temporarily.

When I root my Redmi Note 10 Pro (sweet) by using twrp to flash magisk 25.2 and lazyflasher-no-verify-opt-encrypt.zip, I receive following message
.
Nevertheless, I reboot my phone which is effectively rooted.
I can then install Magisk manager.
Has someone an idea about the meaning of this error message ?
Thanks in advance.

cocopipou said:
When I root my Redmi Note 10 Pro (sweet) by using twrp to flash magisk 25.2 and lazyflasher-no-verify-opt-encrypt.zip, I receive following message
View attachment 5704507.
Nevertheless, I reboot my phone which is effectively rooted.
I can then install Magisk manager.
Has someone an idea about the meaning of this error message ?
Thanks in advance.
Click to expand...
Click to collapse
No need to flash lazy flasher since you already flashed Magisk. They both do the same which is to disable dm verity. Also, lazy flasher is an old zip intended for old devices so maybe that's why it failed.

BigChungus321 said:
No need to flash lazy flasher since you already flashed Magisk. They both do the same which is to disable dm verity. Also, lazy flasher is an old zip intended for old devices so maybe that's why it failed.
Click to expand...
Click to collapse
I thank You very much.

BigChungus321 said:
No need to flash lazy flasher since you already flashed Magisk. They both do the same which is to disable dm verity. Also, lazy flasher is an old zip intended for old devices so maybe that's why it failed.
Click to expand...
Click to collapse
then what is the solution bro...still i cant install some custom roms showing error 1...please help me.

cocopipou said:
When I root my Redmi Note 10 Pro (sweet) by using twrp to flash magisk 25.2 and lazyflasher-no-verify-opt-encrypt.zip, I receive following message
View attachment 5704507.
Nevertheless, I reboot my phone which is effectively rooted.
I can then install Magisk manager.
Has someone an idea about the meaning of this error message ?
Thanks in advance.
Click to expand...
Click to collapse
bro am facing this erros 1. will u pls help me.

THis is the stupidest guide for beginners, this article assumes you have unlocked your phone in the first place. All the important steps are just skipped and is stuffed in the requirements. And just shows simple screenshots that even a child would know where to click.
No external links to find the sources.

While unlocking the bootloader I'm having the issue linked below, thanks in advance for all and any responses. https://forum.xda-developers.com/t/mi-unlock-country-code-broken.4572339/

r4nchy said:
THis is the stupidest guide for beginners, this article assumes you have unlocked your phone in the first place. All the important steps are just skipped and is stuffed in the requirements. And just shows simple screenshots that even a child would know where to click.
No external links to find the sources.
Click to expand...
Click to collapse
AGREE 100%!!!