Database Develop

[Root][SM-T380][SM-T385] Samsung Tab A 8.0 (2017) Root Tutorial

Method was kindly shown to me by user Mefody in answer to a thread I posted.
Rooting SM-T380/T385 via Magisk Manager APK v.5.5.3 & Magisk 15.2:
1. Unpack stock firmvare ***.tar.md5 that is currently installed on your tablet (they MUST BE the same!!!).
2. Then unpack AP-block from step 1 to obtain "boot.img" file.
3. Download & install on tablet Magisk Manager APK.
4. Put "boot.img" on SDCARD.
5. Run Magisk Manager, in setiings set "Patch kernel", then setup the Magisk zip (Wi-Fi must be connected to Internet ).
6. When asked, point Magisk Manager to place on SDCARD where "boot.img" saved.
7. After some time You will get "OK".
8. Find on SDCARD file "patched_boot.img". Copy in on PC & rename to "boot.img". Then archive it to "<any name>.tar".
9. Set tablet to download mode & flash above tar-file via AP-slot of Odin-programm.
10. Tablet will reboot & ask to wipe all data to factory's params. Do it... Be noticed, that all passwords, setting, google registry will be wiped.
11. After wiping & rebooting install Magisk Manager APK again... And YEAH!!! You got root!

Thanks for creating this thread. I used the original thread to root my tab, so seeing this as its own thing will be helpful to a lot of people.

a.brooding.mage said:
Thanks for creating this thread. I used the original thread to root my tab, so seeing this as its own thing will be helpful to a lot of people.
Click to expand...
Click to collapse
Now all we need is TWRP and we'll have Xposed and custom rom support

shahmir_k said:
Now all we need is TWRP and we'll have Xposed and custom rom support
Click to expand...
Click to collapse
For TWRP: https://forum.xda-developers.com/galaxy-tab-a/development/recovery-t3426560

I will get this tab.
BTW, can it install Samsung Game Tuner?

mingkee said:
I will get this tab.
BTW, can it install Samsung Game Tuner?
Click to expand...
Click to collapse
Yes... Game Tuner installs & wokrs good.

Could you clarify on these two steps?
1. Unpack stock firmvare ***.tar.md5 that is currently installed on your tablet (they MUST BE the same!!!).
2. Then unpack AP-block from step 1 to obtain "boot.img" file.

Nerd10 said:
Could you clarify on these two steps?
1. Unpack stock firmvare ***.tar.md5 that is currently installed on your tablet (they MUST BE the same!!!).
2. Then unpack AP-block from step 1 to obtain "boot.img" file.
Click to expand...
Click to collapse
You have to open the stock firmware with an archive manager like WinRar or 7zip. Inside you should find an AP-Block folder. Inside of that should be your boot.img file

shahmir_k said:
You have to open the stock firmware with an archive manager like WinRar or 7zip. Inside you should find an AP-Block folder. Inside of that should be your boot.img file
Click to expand...
Click to collapse
Thanks, where can I find the stock firmwares?

Here is another problem
Is OEM unlock in Developer Section required to install patched kernel and TWRP with Odin?
I can't find it even it's updated.

Does anybody know if this rooting method will work with T-585 on Android 7.0 (January 2018 update)? I guess KNOX will be triggered, right?
Yours
WeT-Klb

I say the root is TOTALLY FALSE!!!
I have been waiting for two week and there's no update to enable OEM Unlock option.
I have returned the unit with restocking fee.

mingkee said:
I say the root is TOTALLY FALSE!!!
I have been waiting for two week and there's no update to enable OEM Unlock option.
I have returned the unit with restocking fee.
Click to expand...
Click to collapse
Have you tried this method even without the option in developer settings to OEM Unlock? On my SM-T350, I don't have the option to OEM unlock either. But I can still root and install TWRP anyways.

Delgoth said:
Have you tried this method even without the option in developer settings to OEM Unlock? On my SM-T350, I don't have the option to OEM unlock either. But I can still root and install TWRP anyways.
Click to expand...
Click to collapse
I tried to flash modified kernel or TWRP with Odin and I got error
Only official software can be installed.

Perhaps someone could provide boot.img files and links here?
I for instance found no matching firmwares for mine. The one that had both matching versions numbers, said it was for Cellular US. This is a wifi only model. Confused
Thanks

Barsky said:
Perhaps someone could provide boot.img files and links here?
I for instance found no matching firmwares for mine. The one that had both matching versions numbers, said it was for Cellular US. This is a wifi only model. Confused
Thanks
Click to expand...
Click to collapse
I have that original boot.img and magisk modified one.

There's a 7 days waiting period after you turned it on the first time regardless reboot or not.
I will make a instruction how to root and I will post kernel and modified kernel.

mingkee said:
I have that original boot.img and magisk modified one.
Click to expand...
Click to collapse
I didn't realize it was so effortless to pull the boot.img out. BUt, until I have that oem unlock option in there, doesn't matter.
Come on, 14 days

Finally, mine has successfully rooted with Magisk.
I will post a guide.

Trouble rooting SM-t380
shahmir_k said:
Method was kindly shown to me by user Mefody in answer to a thread I posted.
Rooting SM-T380/T385 via Magisk Manager APK v.5.5.3 & Magisk 15.2:
1. Unpack stock firmvare ***.tar.md5 that is currently installed on your tablet (they MUST BE the same!!!).
2. Then unpack AP-block from step 1 to obtain "boot.img" file.
3. Download & install on tablet Magisk Manager APK.
4. Put "boot.img" on SDCARD.
5. Run Magisk Manager, in setiings set "Patch kernel", then setup the Magisk zip (Wi-Fi must be connected to Internet ).
6. When asked, point Magisk Manager to place on SDCARD where "boot.img" saved.
7. After some time You will get "OK".
8. Find on SDCARD file "patched_boot.img". Copy in on PC & rename to "boot.img". Then archive it to "<any name>.tar".
9. Set tablet to download mode & flash above tar-file via AP-slot of Odin-programm.
10. Tablet will reboot & ask to wipe all data to factory's params. Do it... Be noticed, that all passwords, setting, google registry will be wiped.
11. After wiping & rebooting install Magisk Manager APK again... And YEAH!!! You got root!
Click to expand...
Click to collapse
When I try to flash the archived boot.tar via Odin it just hangs and sits there. Any help would be much appreciated. Thank You.

Need root. Global version

Hey guys, I bought RM3 few days ago.
I want to root it.
It's the global version. Can anyone please make a video on how to root global version of RM3? PLEASE

Thread is here - https://forum.xda-developers.com/red-magic-3/how-to/red-magic-3-root-guide-t3933148

Texan1 said:
Thread is here - https://forum.xda-developers.com/red-magic-3/how-to/red-magic-3-root-guide-t3933148
Click to expand...
Click to collapse
Can you please make a video?
I'm on global version. Why do I have to install Chinese version?

Saurabh Kash said:
Can you please make a video?
I'm on global version. Why do I have to install Chinese version?
Click to expand...
Click to collapse
Easy setup
Download magisk
Search magisk on google
Sorry can't post links
Download your current global zip file
Extract zip file , copy boot.img and put it into you internal storage phone
Now open magisk and press install, Then batch boot file. Then select your boot.img
A new boot file will be added to your download folder named. Boot_patced.img
Now open you cmd , and flash your new boot_patched.img
And thats it your rooted

em902566 said:
Easy setup
Download magisk
Search magisk on google
Sorry can't post links
Download your current global zip file
Extract zip file , copy boot.img and put it into you internal storage phone
Now open magisk and press install, Then batch boot file. Then select your boot.img
A new boot file will be added to your download folder named. Boot_patced.img
Now open you cmd , and flash your new boot_patched.img
And thats it your rooted
Click to expand...
Click to collapse
I'm new to this kinda stuff and don't wanna mess things up. Can you please make a video?

em902566 said:
Easy setup
Download magisk
Search magisk on google
Sorry can't post links
Download your current global zip file
Extract zip file , copy boot.img and put it into you internal storage phone
Now open magisk and press install, Then batch boot file. Then select your boot.img
A new boot file will be added to your download folder named. Boot_patced.img
Now open you cmd , and flash your new boot_patched.img
And thats it your rooted
Click to expand...
Click to collapse
Please make a video for international Asia version. And I couldn't find link to global rom

em902566 said:
Easy setup
Download magisk
Search magisk on google
Sorry can't post links
Download your current global zip file
Extract zip file , copy boot.img and put it into you internal storage phone
Now open magisk and press install, Then batch boot file. Then select your boot.img
A new boot file will be added to your download folder named. Boot_patced.img
Now open you cmd , and flash your new boot_patched.img
And thats it your rooted
Click to expand...
Click to collapse
And will I still get ota update after root?

Saurabh Kash said:
And will I still get ota update after root?
Click to expand...
Click to collapse
No.
A suggestion: don't. You obviously don't know a lot about rooting and stuff and RM3 is a bit atypical amongst android phones, so it's more risky.
Why do you need root anyway?

Nightpwish said:
No.
A suggestion: don't. You obviously don't know a lot about rooting and stuff and RM3 is a bit atypical amongst android phones, so it's more risky.
Why do you need root anyway?
Click to expand...
Click to collapse
To restore my important backup that I made with titanium and to use theme engines because dark in built theme isn't working on my phone

Saurabh Kash said:
To restore my important backup that I made with titanium and to use theme engines because dark in built theme isn't working on my phone
Click to expand...
Click to collapse
I will say this the above posted is the only way to root global. If an OTA comes out you better not try to update. What you will have to do is BACKUP anything important to you, complete uninstall Magisk and modules, go into fastboot relock the bootloader which will factory reset the phone then update via OTA, re-unlock the bootloader and re-root with the updated boot.img which you will have to download.... Especially important if OTA updates security patch. You have to understand custom ROMs are developed for rooting, stock ROMs are not.... Hence all the trouble.

Hi,
Two things worth mentioning :
- it seems the procedure indicated to rrot does not work with EU v. 1.15 ; I just tried and phone reboots, but with no root
- rooting the phone will not allow OTA. You will get notified of an update, but the update will not apply to the end.
Regards.

How To Guide Rooting the Mi 11 with the latest Xiaomi.eu ROM

EDIT: This is not for the TWRP version. I will update this thread soon!
Hello!
Since I saw a lot of people asking, I decided to post how to root a Mi 11 (as of 2021-02-11).
Install the Xiaomi.eu ROM. You can find more details in this post. Keep the ROM's files, you will need some of them!
Connect your phone to the PC and put it into file transfer mode.
Download Magisk Manager from the official GitHub repository and install the APK. DO NOT DOWNLOAD MAGISK MANAGER FROM ANYWHERE ELSE. THIS GITHUB REPOSITORY IS THE ONLY OFFICIAL, TRUSTED SOURCE.
In the directory you extracted the ROM zip file to, there's a directory called images. This directory contains a file called boot.img. Copy the boot.img to your phone's Download folder.
Open the Settings app, go to My Device, then tap MIUI Version until it says You are now a developer.
Go back to your Settings app and use the search bar to search for USB Debugging and enable it. Click on Yes when it asks whether you want to trust this computer.
Once the file is completely copied, open Magisk Manager on your phone. There will be 2 categories: Magisk and Manager. On the Magisk category, click on Install and choose Select and Patch a File. Navigate to your downloads and select boot.img. Click on Let's go.
When Magisk has finished patching your boot.img file, it will say Output file written to /storage/emulated/0/Download/magisk_patched_XXXXX.img, where XXXXX is 5 random letters/digits.
Open a command prompt on your computer and run adb pull /sdcard/Download/magisk_patched_XXXXX.img , replacing XXXXX with the random characters Magisk showed you earlier. This will copy the file to the directory you are currently in; on Windows, if you are using cmd, this will be C:\Users\[your username].
Reboot your phone into fastboot mode by turning it off, then holding the power and volume-down buttons until it vibrates.
Run the commands fastboot flash boot_a magisk_patched_XXXXX.img and fastboot flash boot_b magisk_patched_XXXXX.img (notice the difference: boot_a and boot_b). Don't forget to replace XXXXX with the random characters Magisk Manager generated. Run the command fastboot reboot and open the Magisk Manager app when your phone has finished rebooting. The app should say that it needs to install some other components; click yes and let it do its thing. It will reboot the phone, and after that, Magisk and therefore the root should be working!
When I first did this, my SafetyNet check failed. I fixed this by repeating all the steps, except that I updated the ROM instead of reinstalling it. You can update it even if it's the same version; it will just flash everything again. You may need to clear the cache of Google Play and reinstall Google Pay if the SafetyNet check initially failed.

Hi, I tryed fastboot oem unlock after alow it in developer settings but it says token verification failed.
It is my first Xiaomi, afert came from a OnePlus 5.
How can I manage to flash the boot image?

PandaKiller said:
Hi, I tryed fastboot oem unlock after alow it in developer settings but it says token verification failed.
It is my first Xiaomi, afert came from a OnePlus 5.
How can I manage to flash the boot image?
Click to expand...
Click to collapse
You do not need to use the OEM Unlock option in the developer options. Mine is still off even after I unlocked my bootloader. You need to use the Xiaomi Unlock Tool found at https://en.miui.com/unlock/ .
Before using this tool, you need to log in to you Mi account on your phone. Then, reboot the phone into fastboot mode, connect it to your PC, and use the unlock tool. It will tell you to wait 168 hours (1 week) before trying again. DO NOT RETRY BEFORE THE 168 HOURS ARE OVER OR THE TIMER RESETS! Even if you are a single minute early, it will reset the timer.
Once the week has passed, do this again and your phone will be unlocked. Warning: This will erase your data.
You should prepare the boot image BEFORE unlocking, because otherwise you will have to go through the phone's setup, install Magisk, patch the image, and wipe the phone again.
Another warning: Do not re-lock your bootloader. If the bootloader is re-locked with any ROM other than the one the phone shipped with installed, the phone gets bricked.

Thank you for the explanation.
I did everything as you said, now just need to wait for the painfully 168 hours...
Is there already a .zip to flash in order to disable encryption? Just to not risk losing my data in future updates.

PandaKiller said:
Thank you for the explanation.
I did everything as you said, now just need to wait for the painfully 168 hours...
Is there already a .zip to flash in order to disable encryption? Just to not risk losing my data in future updates.
Click to expand...
Click to collapse
If you use the Xiaomi.EU ROM, you can update without wiping your data. They give you 2 scripts - 1 for installing and 1 for updating.

Thanks for the write-up. Worked like a charm (Y)

Hi Lucavon,
Thx for the guide. I did it twice and after reboot and launch Magisk Manager I got no message asking that other components need to be installed. Did I miss something?

Giova19 said:
Hi Lucavon,
Thx for the guide. I did it twice and after reboot and launch Magisk Manager I got no message asking that other components need to be installed. Did I miss something?
Click to expand...
Click to collapse
Magisk manager has changed a bit in version 22. It may no longer require this extra step. If everything works as expected, it should be fine.

Lucavon said:
Magisk manager has changed a bit in version 22. It may no longer require this extra step. If everything works as expected, it should be fine.
Click to expand...
Click to collapse
Ok noted. I rooted following the full process 3 times and cannot get the safenet.

If i pdate the eurom how i root again? i must the process again? Sry for my Bad English!

Giova19 said:
Ok noted. I rooted following the full process 3 times and cannot get the safenet.
Click to expand...
Click to collapse
That's weird, it works perfectly fine for me. Maybe you need to re-download your Xiaomi.eu ROM.
xXSkylinexX said:
If i pdate the eurom how i root again? i must the process again? Sry for my Bad English!
Click to expand...
Click to collapse
Yes, you need to repeat it. After updating, copy the boot image, patch it again, etc, like in this post.

Hi.
I follow step by step with stable 12.5. (clean install)
Safetynet failed (cts profile failed)
I try safetynet fix 1.1.1 or 2.0.0 and nothing work.
Any solution ?

Plathoon said:
Hi.
I follow step by step with stable 12.5. (clean install)
Safetynet failed (cts profile failed)
I try safetynet fix 1.1.1 or 2.0.0 and nothing work.
Any solution ?
Click to expand...
Click to collapse
Do you have magisk hide enabled?
If you do and you're checking safetynet status with a different app than magisk manager, you need to add it to hide.

Magisk hide is enabled too

SOLVED
- enable magiskhide
- download "magiskhide props config"
- use app like termux and follow steps :
* "su"
* "props"
* "1" (edit device fingerprint)
* "f" (pick a certified fingerprint)
* select your phone
* accept and reboot.
and now it work.

Hello,
I followed all the steps in the root guide. I also have root access. However, I do not have write access to the root directory. What I have done wrong? I have no more idea what it could be. Can someone help me?
Note: I installed the Rom Version xiaomi.eu_multi_MI11_21.3.31_v12-11-fastboot
After installing the Rom, the following error message appeared at the end.
fastboot: error: Cannot generate image for userdata
Can it have anything to do with it?

Lucavon said:
Run the commands fastboot flash boot_a magisk_patched_XXXXX.img and fastboot flash boot_b magisk_patched_XXXXX.img (notice the difference: boot_a and boot_b).
Click to expand...
Click to collapse
Why don't write directly fastboot flash boot_ab magisk_patched_XXXXX.img ? Is that intended ?

bert4711 said:
I followed all the steps in the root guide. I also have root access. However, I do not have write access to the root directory. What I have done wrong? I have no more idea what it could be. Can someone help me?
Click to expand...
Click to collapse
Idk if I was having and same issues, but for me on 3.31 xiaomi.eu I was having issues with the superuser prompt not appearing. I found it happened only when the magisk app was repackaged. Approving prompts while it was unhidden then hiding magisk worked great.

Edited

I use the root explorer, the root query also appears with Magisk. But I still don't get write access to the root directory. I originally had the Global Rom V12.0.4.0.RKBMIXM on it. After the bootloader was open, I flashed the Rom Version xiaomi.eu_multi_MI11_21.3.31_v12-11-fastboot. The following error message occurred at the end of the flash process. fastboot: error: Cannot generate image for userdata I am currently assuming that the problem with root has something to do with it. I have already tried the Version xiaomi.eu_multi_MI11_V12.5.1.0.RKBCNXM_v12-11-fastboot. The result is the same... fastboot: error: Cannot generate image for userdata and no write permissions in the root directory ...

[OOS][ALL][Stock boot][Stock recovery] OxygenOS 11.0.0

Here are all the boot.img and recovery.img of OxygenOS 11.0.0. Since TWRP isn't ready yet, I guess a lot of people need it if they didn't keep their root permissions.
As I only have a EU device I can only provide a patched boot.img for that device. But with the original .img files it should be easy to patch and flash it yourself. To make it clear: boot.img and recovery.img are stock unless said otherwise. They've just been extracted from the payload.bin inside the respective OOS update zip file.
OOS 11.0.0 EU:
boot.img
boot.img (Magisk v22 patched)
recovery.img
OOS 11.0.0 GLOBAL:
boot.img
recovery.img
OOS 11.0.0 INDIA:
boot.img
recovery.img
Please note: I'm not responsible for anything you do to your device. You use these files at your own risk. I will not provide any further .img files nor ask me for patched files. Any contribution with patched boot.img files is welcome of course. Also note although I'm a moderator, this thread is neither official nor in any way more or less trustworthy than any other contribution by other awesome members!

Would I be able to keep my phone rooted with this after updating?

This is very useful
thanks

jman12311 said:
Would I be able to keep my phone rooted with this after updating?
Click to expand...
Click to collapse
No, unless you use the Magisk patched EU version. Otherwise always install the update, then use the Magisk Manager to patch the inactive slot and then (only then!) reboot. Then you'll keep root.
Otherwise use the stock boot.img and patch with Magisk Manager. Then flash the patched image via fastboot. There are plenty of tutorials on XDA

Hi i installed the update already but didn't reboot what is the solution to keep root ?

Janusk22 said:
Hi i installed the update already but didn't reboot what is the solution to keep root ?
Click to expand...
Click to collapse
1. Install Magisk manager app
2. Open the app and choose "Install to inactive slot (After OTA)"
3. Reboot!

already now i have a magisk module who is making bootloop i already have access to adb via recovery how to remove it

Janusk22 said:
already now i have a magisk module who is making bootloop i already have access to adb via recovery how to remove it
Click to expand...
Click to collapse
Use USB debugging and a PC with the code:
Code:
adb wait-for-device shell magisk --remove-modules
If USB debugging isn't enabled, flash the stock boot.img (without root), boot it, enable ADB debugging and allow the connection to the PC. Then flash the patched boot.img and execute the command above
That is assuming you have a OnePlus 7T Pro which doesn't have a decryptable recovery. Otherwise you can simply flash the Magisk uninstaller

But i have a error I think that i cannot write in system
I have always : cannot be accessible

Thanks i just had to run the command when i rebooted

Is just me or GPS takes more time to "fix" satellites?

FSadino said:
Is just me or GPS takes more time to "fix" satellites?
Click to expand...
Click to collapse
Not longer than usual. But I often had GPS fix issues with my 7T Pro where it takes 5-10 minutes despite using A-GPS.

Macusercom said:
Not longer than usual. But I often had GPS fix issues with my 7T Pro where it takes 5-10 minutes despite using A-GPS.
Click to expand...
Click to collapse
I calibrated the A-Gps again, let's see if that was it. Thank you

Hi I was wondering if you could possibly share the android 11 update file I have a Oneplus 7T Pro HD1910 currently on OOS 10.1.14 It would be awesome if you can PM me. I've tried downloading from Oygen Updater it fails at 98% also on XDA forum the download fails. I'd really appreciate it. Thanks

Macusercom said:
As I only have a EU device I can only provide a patched boot.img for that device. But with the original .img files it should be easy to patch and flash it yourself. To make it clear: boot.img and recovery.img are stock unless said otherwise. They've just been extracted from the payload.bin inside the respective OOS update zip file.
Click to expand...
Click to collapse
Hey, could you please share the payload.bin extract procedure?

Ia possible to use this files to back to stock rom from lineageos 18.1? If yes, can someone help me and give me the procedure how to do this?

For all the "EU" and "global" files, I get "fastboot: error: boot partition is smaller than boot image". The Magisk version can be installed, but then I get a Qualcomm crash screen when I try to actually start it.

How To Guide (Guide) Rooting, payload dumper, magisk_patched guides NE2213

Hi all,
Thought i'd share a guide on how to get these boot images yourself as well as all the files required, plus the patched boot.img if you just want to go ahead and boot/flash it without obtaining one yourself
Please read the process before committing to proceeding, so you know what's required and what you should and shouldn't use!
Stock and patched images are UK/ EU NE2213 but the guides are universal and could be used on multiple devices.
NOTE:
For these guides the versions used are:
Stable, Canary or BETA depending on firmware, simply change the channel in Magisk settings then select install / update:
NE2213_11_A.12
Magisk Manager v24.3 (24300) Stable
NE2213_11_A.13
Magisk Manager v24.3 (24300) Stable
NE2213_11_A.14
Magisk Manager v25 (25000) Stable this version retains root after a restart, more stable version over previous iterations.
NE2213_11_A.16
Magisk Manager v25.2 (25200) Stable
NE2213_11_C_20
Magisk Manager v25.2 (25200) Stable
NE2213_11_C_21
Magisk Manager v25.2 (25200) Stable
NE2213_13.1.0.520 (EX01)
Magisk Manager v26.1 (25200) Stable
Oxygen OS NE2213_13.1.0.521 (EX01)
Magisk Manager v26.1 Stable
1st
Extracting a boot.img using Fastboot Enhance
Pre-requisites
A device with a working version of magisk manager installed, simply change the channel to the version outlined in the list above relevant to your firmware then select install / update:
A Windows 10 computer / laptop
A full update downloaded firmware zip for your model (recommend oxygen updater)
Payload dumper program for Windows.
An unlocked bootloader.
The local System Update Installer : normal local system update will not allow a reboot during installation, the one I've linked will.
Process
On your computer
1. Download and copy the fastboot enhance folder to your desktop or a location of your choosing.
Download from here: https://github.com/libxzr/FastbootEnhance/releases
2. Download the firmware of your choice (always use full zips, not incremental) and open it using Winrar or a similar zip program, extract the file called payload.bin to a folder of your choosing.
3. Run the program FastbootEnhance.exe, a window will appear, click Payload Dumper, then click browse and point to the payload.bin file, the contents of that payload.bin will now be shown, bare in mind you'll need to check the box "Allow incremental" even if it's a full zip
4. One of the files will be called boot.img, this is the file we'll be patching, click extract then copy this to your phone, root of storage which is called /sdcard.
On your phone
5. Open up Magisk and click Install / Update, if you don't see update then change channel, do this by changing the channel in magisk settings, it'll then show the install/ update buttons.
6. Select "Select and Patch a file" it'll open up a file browser, navigate to the boot.img you copied earlier and select it, allow it to complete (this will output a file called "magisk_patched" which will be output into the Downloads folder)
You now have a patched boot.img ready to boot or flash to either slot with fastboot or boot via fastboot.
I would recommend booting as this is risk free, if it's a bad image for whatever reason and you choose to flash then your phone will bootloop.
NOTE** Some people have noticed that an already patched boot.img when flashed can fail and cause a boot loop when flashed, so if you have downloaded a magisk_patched img from somewhere else then you WILL need to re-patch it on your own device preferably using the afore mentioned magisk manager based on what firmware it's from.
If you intend to follow the guide below with your own patched img then you shouldn't need to patch it twice but it won't hurt if you do.
2nd
Update from XX stable to XX+ stable whilst retaining root
Guide
**NOTE- Although this may work, the system may be unstable, especially when changing bases, eg: Android 11-12 or 12-13, so if you encounter strange behaviour then a factory wipe is advised.
1. Download the relevant firmware for your device via oxygen updater
2. Open Magisk and remove all the modules you have installed, then reboot
**NOTE- At this point I tend to copy out the whole firmware to my computer, incase I need it in the future, the boot img and patched boot img are at the foot of this guide, I'll always upload the latest firmware as soon as it comes out for the UK/EU model
3. Install the OnePlus local install apk listed below in downloads. Click the cog and select "Local Upgrade" the file should be listed on screen, if not then move the file to the root of your phones storage.
4. Click install and allow it to go through the process
**NOTE- DO NOT REBOOT AT THIS POINT YOU WILL LOSE THE ABILITY TO PATCH ON THE FLY, SIMPLY BACK OUT OF THE SCREEN WHICH SAYS "INSTALLATION COMPLETED. RESTART TO EXPERIENCE NEW FEATURES"
5. Open up magisk and click install (you may see two install buttons, top one is magisk and the bottom is magisk manager, we need the top one)
6. You'll be faced with a screen that has several options, you want to select "Install to Inactive slot (After OTA)" then select "LET'S GO" once complete click reboot.
7. Once your phones booted back up your system / files should all remain as they were and you should have root access.
You can now install all your modules again so long as they're compatible with the firmware you've just updated to.
3rd
Rooting using fastboot commands
Method 1
Booting the patched image
1. Obtain a patched boot image for your device variant preferably using payload dumper or download one of mine from the foot of this guide or if you've just performed the above guide you should already have a functional one, copy this file to your fastboot folder on your computer
**NOTE - The above suggested downloads are for the EU / UK variant- if you have another model / firmware please use that instead, If you did not obtain the boot.img from a firmware and patch it yourself, you will need to patch it again in magisk manager to avoid a bootloop, if you still get a bootloop it's best to obtain one yourself using the guide at the top of this post.
2. Reboot your phone to fastboot
and connect to your computer.
3. Boot the magisk patched img
fastboot boot magisk_patched (or name of your patched boot img)
Your phone should now boot automatically, you should now be rooted but we need to make this permanent, if you were to reboot you would lose root.
4. Open magisk manager and click install/update, if you are missing the install/ update buttons, change magisk version to beta in magisk settings and install the update, the buttons should then show.
5. Select Direct install (recommended) then click ok.
6. Allow magisk to permanently root your device then click reboot.
You should now boot and remain rooted.
Method 2
Flashing to both slots
1. Obtain a patched boot img for your device variant or download one of mine from the foot of this guide or if you've just performed the above guide you should already have a functional one, copy this file to your fastboot folder on your computer
**NOTE - Again the above suggested downloads are for the EU/ UK variant- if you have another model / firmware please use that instead, if you did not obtain the boot.img from a firmware and patch it yourself, you will need to patch it again in magisk manager, to avoid a bootloop
2. Reboot your phone to fastboot and connect to your computer.
Command: adb reboot bootloader
3. Open a command prompt on your computer and navigate to your ADB/fastboot folder.
4. Type the following.
fastboot flash boot_a magisk_patched
Press enter.
fastboot flash boot_b magisk_patched
Press enter
fastboot reboot
Press enter
6. Your phone should now boot, open magisk and verify you're rooted.
Troubleshooting
If flashing succeeds but you don't have root and you've followed all the instructions, you may have some magisk modules still active, try performing the following.
1. Connect your phone to your computer.
2. Reboot the phone, then during the boot animation enter this command via ADB.
adb wait-for-device shell magisk --remove-modules
3. Allow to boot, modules will be removed and root should then be active.
If there is no magisk install / update buttons.
1. Make sure you have granted permission to magisk in settings / apps / magisk / permissions
2. Make sure that the update channel is on canary, then force close magisk and then re-open
3. If it still doesn't work then update magisk using canary
4. Last method to check would be to change to the beta channel in magisk settings, then install it.
Or change the update channel, install the version on offer, then change back to canary, install and you should be good to go.
Window's version
Windows 7 will not work with fastboot, please use Windows 10
USB
Use USB 2.0 not 3.0 or 3.1
ADB
These are the files i use for ADB (in the below list) tested these on fresh installs of windows on several windows machines, all win 10
Place them into the root of C so it reads C:\ADB much easier to navigate to that way.
Bootloader unlock
Boot to the bootloader with adb reboot bootloader
type fastboot flashing unlock
Agree to unlock - allow to boot.
If you can't see the device using ADB
Make sure USB Debugging is turned on
Connect your cable to your phone and computer, when asked what you want your phone to do, click on transfer files, a driver will be installed.
After this reconnect your phone and it'll prompt you with a disclaimer with a check box, check the box and click ok, ADB / Fastboot should now work.
Files:
Local System update APK, this must be used as the local OnePlus 10 Pro one will not allow a reboot during the installation, so you cannot install the Magisk boot image during an upgrade, the android 13 local update apk is also required for rolling back to android 12.
Android 13 local update apk
3.27 MB folder on MEGA
mega.nz
Android 12 local update apk
3.27 MB folder on MEGA
mega.nz
ADB Files for Windows 10:
7.69 MB folder on MEGA
5 files
mega.nz
Payload dumper program for Windows-
https://mega.nz/folder/vU00FZDa#PIEfjl5w5wonyNAwHW3FBQ
Oxygen OS NE2213_11_A.12 Stock boot image
0 byte folder on MEGA
mega.nz
Oxygen OS NE2213_11_A.12 Patched boot image
192 MB folder on MEGA
mega.nz
Oxygen OS NE2213_11_A.13 Stock boot image
192 MB folder on MEGA
mega.nz
Oxygen OS NE2213_11_A.13 Patched boot image
192 MB folder on MEGA
mega.nz
Oxygen OS NE2213_11_A.14 Stock boot image
384 MB folder on MEGA
2 files
mega.nz
Oxygen OS NE2213_11_A.14 Patched boot image
192 MB folder on MEGA
mega.nz
Oxygen OS NE2213_11_A.16 Stock boot image
192 MB folder on MEGA
mega.nz
Oxygen OS NE2213_11_A.16 Patched boot image
192 MB folder on MEGA
mega.nz
Android 13
Oxygen OS NE2213_11_C_20 Stock boot image
192 MB folder on MEGA
mega.nz
Oxygen OS NE2213_11_C_20 Patched boot image
192 MB folder on MEGA
mega.nz
Oxygen OS NE2213_11_C_21 Stock boot image https://mega.nz/folder/LNVxTDYA#yly9xpjFjQhe4De_jqyzbw
Oxygen OS NE2213_11_C_21 Patched boot image
192 MB folder on MEGA
mega.nz
Oxygen OS NE2213_13.1.0.520 (EX01) Stock boot image
192 MB folder on MEGA
mega.nz
Oxygen OS NE2213_13.1.0.520 (EX01) Patched boot image
192 MB folder on MEGA
mega.nz
Oxygen OS NE2213_13.1.0.521 (EX01) Stock boot image
192 MB folder on MEGA
mega.nz
Oxygen OS NE2213_13.1.0.521 (EX01) Patched boot image
192 MB folder on MEGA
mega.nz

Glad to see you here bro with the 10 Pro and helpful guide's!!
Cheers

galaxys said:
Glad to see you here bro with the 10 Pro and helpful guide's!!
Cheers
Click to expand...
Click to collapse
Slowly coming around to this phone mate, we desperately need a few custom ROMs..
EvoX on this would be phenomenal.
Nudge nudge @AnierinB

UPDATE: First patched boot image is up, using the latest stable Magisk v24.3 (24300)

dladz said:
Slowly coming around to this phone mate, we desperately need a few custom ROMs..
EvoX on this would be phenomenal.
Nudge nudge @AnierinB
Click to expand...
Click to collapse
Yeh, it's early but hopefully a few Developer's will get this badboy device!

Thank you thank you THAAAANK YOOOOUUUU

meowmeowpewpew said:
Thank you thank you THAAAANK YOOOOUUUU
Click to expand...
Click to collapse
Lol welcome mate

meowmeowpewpew said:
Thank you thank you THAAAANK YOOOOUUUU
Click to expand...
Click to collapse
I honestly hope so..
I'm having a few issues isolating the correct files to make the center clock Magisk mod, but that's in the works. Will have it done soon hopefully.
OnePlus thought it would be a good idea to get rid of OPSystemUI.apk in place of systemui.apk so maybe more in line with stock android. But we'll see

@galaxys as if my prayers were answered, joined the Evo X TG group and there is now a OnePlus 10 group so it's in the works, seriously hope it's AnierinB, he did so well with the 8 pro.
Literally cannot wait

dladz said:
@galaxys as if my prayers were answered, joined the Evo X TG group and there is now a OnePlus 10 group so it's in the works, seriously hope it's AnierinB, he did so well with the 8 pro.
Literally cannot wait
Click to expand...
Click to collapse
Hey that's great news and something to definitely look forward to!
Cheers

Very happy to see guides! Nice, thank you so much !

dladz said:
@galaxys as if my prayers were answered, joined the Evo X TG group and there is now a OnePlus 10 group so it's in the works, seriously hope it's AnierinB, he did so well with the 8 pro.
Literally cannot wait
Click to expand...
Click to collapse
I cannot find that Evo X 10 Pro channel, have you got a link?

kouzelnik3 said:
I cannot find that Evo X 10 Pro channel, have you got a link?
Click to expand...
Click to collapse
If you have telegram just search for evo x up the top, you'll see the main channel.
The the other is in that, i'm just in the middle of something, i'll send it once i'm done.

kouzelnik3 said:
I cannot find that Evo X 10 Pro channel, have you got a link?
Click to expand...
Click to collapse
Evolution X - OnePlus 10 Series
Telegram: Contact @EvolutionXOnePlus10
t.me

Macke93 said:
Evolution X - OnePlus 10 Series
Telegram: Contact @EvolutionXOnePlus10
t.me
Click to expand...
Click to collapse
Oh I've found it.

Hello All,
Very many thanks for your guide. It really helped me root my OP 10 PRO
I was wondering if it is possible to flash my OP ColorOS with OxygenOS EU/UK version you have uploaded?
I copied the 02b0d1b2508744e3a41115aeb274cccf.zip to the root folder and I tried installing via Oxygen Updater using the automatic method, but it fails every time.
If I try installing it manually, I have to download the Oxygen Updater via oxygenos.oneplus.net/OPLocalUpdate_For_Android12.apk.zip and rename to .apk. - I then launch System Update , click on settings and it says 'Move installation package into root directory' (which it is).
Have I missed a step?

kouzelnik3 said:
Oh I've found it.
Click to expand...
Click to collapse
Ah was just about to post it mate.
Glad you found it, it's only new but that fact that it's here is brilliant . I'm hoping AnierinB is the dev who makes the rom for the 10.

Lynxy0 said:
Hello All,
Very many thanks for your guide. It really helped me root my OP 10 PRO
I was wondering if it is possible to flash my OP ColorOS with OxygenOS EU/UK version you have uploaded?
I copied the 02b0d1b2508744e3a41115aeb274cccf.zip to the root folder and I tried installing via Oxygen Updater using the automatic method, but it fails every time.
If I try installing it manually, I have to download the Oxygen Updater via oxygenos.oneplus.net/OPLocalUpdate_For_Android12.apk.zip and rename to .apk. - I then launch System Update , click on settings and it says 'Move installation package into root directory' (which it is).
Have I missed a step?
Click to expand...
Click to collapse
Honestly mate i'm not sure, you're essentially changing region.
Have you looked into fastboot enhanced?
You can obtain the firmware from oxygen updater (it's 4.15GB the one i uploaded is only the boot image and patched boot image)
Then copy it to your computer and allow it to flash to your phone.
This isn't without risk mate and i've not done this before myself.

dladz said:
Ah was just about to post it mate.
Glad you found it, it's only new but that fact that it's here is brilliant . I'm hoping AnierinB is the dev who makes the rom for the 10.
Click to expand...
Click to collapse
I am hoping too, because in this state oxygen os in this device is bad. Yeah, it is quite new, but hey, it is halfly baked. And not only evo x, but other ROMs I hope will come.

dladz said:
Honestly mate i'm not sure, you're essentially changing region.
Have you looked into fastboot enhanced?
You can obtain the firmware from oxygen updater (it's 4.15GB the one i uploaded is only the boot image and patched boot image)
Then copy it to your computer and allow it to flash to your phone.
This isn't without risk mate and i've not done this before myself.
Click to expand...
Click to collapse
Thanks for your swift reply. I will wait until there is a verified method. For now, I will tread lightly with the rooted version hehe