Database Develop

[GUIDE] Nexus 5 - How to Unlock Bootloader, Install Custom Recovery and Root

{
"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"
}
Setup, Preparation and Prerequisites
Basic tasks that I may refer to throughout this guide:
Open command prompt - Press Window Key + R, type in "cmd" (without the quotes), and hit enter.
Enter the bootloader - Turn the phone off. Hold volume down + power. The bootloader is also known as fastboot mode.
ADB and Fastboot Installation
Download the full Android SDK here (scroll to the bottom of the page>DOWNLOAD FOR OTHER PLATFORMS>SDK Tools Only) or get a slimmed version containing only the essential components(Thanks @El Daddy)
Link removed since it expired
Extract the zip and place the android-sdk-windows folder on your desktop.
**If you chose to download the slimmed sdk skip to step 5**
Only if you downloaded the full sdk: Go into the android-sdk-windows folder and run SDK Manager.exe. Install the following packages (there are a total of 4 packages):
- Tools > Android SDK Tools, Android SDK Platform-tools
- Extras > Android Support Library, Google USB Driver
Only if you downloaded the full sdk: Go back into the android-sdk-windows directory, and you should see a new folder named platform-tools. If you don't see this new folder, repeat the step above.
To confirm that it is indeed working, open a command prompt window and enter the following commands:
Code:
cd Desktop/android-sdk-windows/platform-tools
adb version
If it displays "Android Debug Bridge version x.x.xx" it is working. If it is gives an error saying that adb is not a recognized command, it has not been successful. Carefully repeat the steps above if this is the case. Close the command prompt window when you are done.
USB Debugging - On your phone go to Settings > About phone > Tap on Build number 7 times. This will enable Developer options. Now go back to Settings > Developer options > Enable USB debugging
Show File Extensions - Open a command prompt window and run "Control folders" (without the quotes). Go to the View tab and uncheck the "Hide extensions for known file types" option. This will help avoid confusion when renaming files.
Battery - Ensure that your phone has at least 60% battery remaining, and that your PC is plugged in and wont shut down spontaneously during the process. The procedure doesn't take very long (5-15 minutes), but its best to have enough charge in case something goes wrong.
Backup (Optional) - Unlocking the bootloader will completely wipe all data from the device. This includes apps, settings and even the contents of the internal sdcard (pictures, music, etc.). Copy all important files off the phone onto a PC or upload them to a cloud.
Driver Installation - Try this first, but if that doesn't work look here. Still having issues? Give this a try. None of these working? Hopefully this does the trick.
Downloads
Download a custom recovery of your choice and the SuperSU zip below. Place both files (recovery image and root zip) in the platform-tools folder located on your desktop within the android-sdk-windows folder.
Custom Recovery:
TeamWin Recovery Project (TWRP) or ClockworkMod (CWM)
Root:
SuperSU
Information
Rooting a nexus device is actually quite a simple and easy process. Before you begin, it is recommended that you at least try to understand what each part of the process will do. Although this guide will elongate each step in order to show all of the details, the method used can be broken up into 3 main steps: Unlocking the Bootloader, Installing a Custom Recovery and finally Rooting. Each new step relies on the previous step to have been completed, and a basic summary of each part is:
Unlocking Bootloader: Opens the door to the internal memory of the device to be written on to. This allows you to flash images onto the main partitions of the phone.
Installing a Custom Recovery: A custom recovery is flashed onto the recovery partition of the device and overwrites the stock recovery that exists by default. Custom recoveries bring lots of functionality and give you the ability to perform wipes, install flashable zips, create full backups of your NAND (Nandroid backup), and various other features. An unlocked bootloader is needed to install a custom recovery.
Rooting: You can gain root by either flashing via recovery a pre rooted custom rom, or flashing a zip containing the SuperSU binaries. A custom recovery is necessary to do this.
After completing these steps your phone will be rooted, the phone will have a custom recovery installed, and the phones bootloader will be unlocked. This, in my opinion, is the most practical and beneficial method for rooting your phone. It gives you some basic adb/fastboot knowledge, and should hopefully help you have a decent understanding of what is going on. Also this method will work regardless of what android version your phone has. Using a toolkit will only make things worse in the long run...learn to do it properly. It has been proven that every time you use a toolkit, god kills a kitten. Save the kittens.
If you are confused by anything in this guide, I would highly suggest getting it clarified being before moving on. Ask your question in this thread and I or someone else will likely answer. Also I'd suggest that you read over the whole thread a few times before actually doing anything to the phone.
Understand? Good...lets begin:
1. Unlocking Bootloader
Turn the phone off. Then boot it into the bootloader/fastboot mode by holding volume down + power.
Plug the phone into your PC, then open a command prompt window window and type:
Code:
cd Desktop/android-sdk-windows/platform-tools
Code:
fastboot devices
This command will list the connected devices. If your phones serial number shows up you are good to go and may continue. If the phone is NOT listed this indicates that your drivers are not installed correctly. In order for you to continue you must fix your drivers so that your phone is listed under fastboot devices.
If the phone has been recognized by the command above, proceed to unlocking the bootloader with the following command:
Remember that this step will wipe EVERYTHING off the phone
Code:
fastboot oem unlock
On the phone a screen should pop up asking whether or not you would like to unlock the bootloader. Use the volume rockers to highlight "Yes" then press power to confirm the action.
After the above command has finished excuting, run the following (DO NOT skip this step, it is more important than you think):
Code:
fastboot reboot
The phone will reboot. Next you will be presented with a screen containing an android logo and a progress bar (this may take up to ten minutes to complete). Wait until the phone has fully booted up into android, then proceed onto the next section of the guide.
Close the command prompt window.
2. Installing a Custom Recovery
Turn the phone off. Then boot it into the bootloader/fastboot mode by holding volume down + power.
Rename the recovery file that you downloaded above to recovery.img. *Make sure that you rename it to recovery.img NOT recovery.img.img* Remember that you should place the file in the platform-tools folder inside of the android-sdk-windows folder on your desktop.
Open command prompt and run the following commands:
Code:
cd Desktop/android-sdk-windows/platform-tools
Code:
fastboot flash recovery recovery.img
On the phone, use the volume buttons to scroll onto "Restart Bootloader" and hit power to select it. After the bootloader reloads, use the volume buttons to scroll onto "Recovery Mode" and power to select it. You should then be greeted with your newly installed custom recovery.
Close the command prompt window.
3. Rooting
Now that your phone has an unlocked bootloader and a custom recovery installed you have a two options to gain root (Pick one or the other. You don't need to do both)
Option A) Flash SuperSU binaries which will give you root with the stock rom
Confirm that you have downloaded the SuperSU zip from the downloads section above and that it is located in the platform-tools folder inside of the android-sdk-windows folder on your desktop.
Turn the phone off then boot into the bootloader. (volume down + power). Once in the bootloader use the volume rockers to scroll onto Recovery Mode, then press power to select it. This should bring you into your newly installed custom recovery. Leave the phone at the home page of the custom recovery.
Open a command prompt window and run the following commands:
Code:
cd Desktop/android-sdk-windows/platform-tools
Code:
adb push UPDATE-SuperSU-v[COLOR="Red"]X[/COLOR].[COLOR="red"]XX[/COLOR].zip /sdcard/
This will copy the SuperSU zip onto your phone. Once the command has completed continue.
Instructions for TeamWin Recovery Project (TWRP):
Install > browse to SuperSU zip and select the it
Swipe to confirm the installation. Then reboot.
Instructions for ClockworkMod (CWM):
install zip from sdcard > choose zip from sdcard.
Next, browse to the location where you previously copied the SuperSU zip and select the it.
To confirm the installation, scroll down to "Yes" and select it. The installation shouldn't take very long, and once it has completed you may reboot.
Option B) Flash a custom rom which will come pre-rooted
Note that not all custom roms will be pre rooted, however the majority of them are. Read the OP of the ROM thread to see what the verdict is.
Copy a custom rom (you can find these in the Nexus 5 Android Development and Nexus 5 Original Android Development section) onto the phone (remember the location where you copy it to)
Turn the phone off then boot into the bootloader. (volume down + power). Once in the bootloader use the volume rockers to scroll onto Recovery Mode, then press power to select it. This should bring you into your newly installed custom recovery. To install a custom rom the general procedure to follow is: factory reset, wipe cache + dalvik cache, flash ROM, flash GApps. Here are the recovery specific instructions:
Instructions for TeamWin Recovery Project (TWRP):
Wipe > Swipe to Factory Reset
Install > browse to the location where you previously copied the ROM zip and select it > Swipe to confirm the installation
Install GApps using same process as ROM, then reboot.
Instructions for ClockworkMod (CWM):
wipe data/factory reset
wipe cache partition
advanced > wipe dalvik cache
install zip from sdcard > choose zip from sdcard > navigate to the location of the rom > select the rom > confirm the installation by selecting "Yes"
After that you may install the GApps using the same method for flashing the rom, and finally reboot the phone.
Keep in mind that the first boot after installing a custom rom & wiping the phone may take longer than usual, as the phone will need to rebuild the dalvik cache and initialize other first boot stuff.
Congrats! That is all! Your phone now has an unlocked bootloader, a custom recovery installed and is rooted...Plus you saved a kitten. Enjoy

Troubleshooting & FAQ
Why am I seeing a red triangle with a dead android when booting into recovery even after I flashed a custom recovery?
What you are seeing is the stock recovery, meaning that the custom recovery that you flashed did not install correctly. Try the following suggestions:
Make sure you are using the USB cable that came with your phone. Only use other ones, if the stock one isn't working
Try using different USB ports. USB 2.0 ports (the ones that ARE NOT blue) are preferable. USB 3.0 ports (the blue ones) may cause problems with connectivity.
If you are on a desktop, use the ports on the back of the tower instead of the ones in the front. These ports are directly connected to the motherboard, rather than the ones in the front which are usually attached to a header cable which then indirectly connects to the motherboard.
My phone wont boot into android. I can only access the bootloader and custom recovery. What do I do?
Suggestion 1: Factory reset via recovery.
TWRP Instructions:
Boot into recovery
Wipe > Swipe to Factory Reset
Reboot
CWM Instructions:
Boot into recovery
wipe data/factory reset
wipe cache partition
advanced > wipe dalvik cache
Reboot
If that doesn't work continue onto Suggestion 2.
Suggestion 2: Push a ROM to your phone and flash it.
Download a ROM onto your computer. If you don't have time to look for a ROM, just download the stock ROM.
Move the downloaded ROM onto your desktop, and rename the file to "ROM.zip" (without the quotation marks)
Boot phone into recovery
Open command prompt and run the following commands:
Code:
cd Desktop
adb push ROM.zip /sdcard/
Wait for it to finish copying the file, then flash the ROM. If you need further details on how to flash a ROM take a look at the OP, section 3. Rooting, Option B)
If that doesn't work continue onto Suggestion 3.
Suggestion 3: Flash the factory images.
Flash the factory images
My phone wont boot into android. I can only access the bootloader. What do I do?
Flash the factory images
My phone exploded. What do I do?
Tape it back together then flash the factory images

Awesome post. Got a question: if I ONLY unlock bootloader will I still be able to get and install OTA updates?
Sent from my Nexus 4 using Tapatalk

dombera said:
Awesome post. Got a question: if I ONLY unlock bootloader will I still be able to get and install OTA updates?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Yes, if you only unlock the bootloader you will still be able to get ota's. The lock state of your bootloader will not affect your ability to receive ota's.

Chromium_ said:
Yes, if you only unlock the bootloader you will still be able to get ota's. The lock state of your bootloader will not affect your ability to receive ota's.
Click to expand...
Click to collapse
Awesome, thx
Sent from my Nexus 4 using Tapatalk

This is awesome, will come in handy.
Sent from my HTC Desire using XDA Premium 4 mobile app

Chromium_ said:
Yes, if you only unlock the bootloader you will still be able to get ota's. The lock state of your bootloader will not affect your ability to receive ota's.
Click to expand...
Click to collapse
What about if you unlock the boot loader and root, will you be able to get OTAs then? I guess a better question is what's the point of no return (without reflashing the factory image) where you break OTA updates? Thanks for the thread btw!

Can people please post confirmation of TWRP or CWM recoveries + rooting working without problems if they've done it? I know it's unofficially supported at this time, but getting some data collected would be useful.
---------- Post added at 01:43 AM ---------- Previous post was at 01:41 AM ----------
Xero258 said:
What about if you unlock the boot loader and root, will you be able to get OTAs then? I guess a better question is what's the point of no return (without reflashing the factory image) where you break OTA updates? Thanks for the thread btw!
Click to expand...
Click to collapse
If you unlock bootloader & root, and modify some system files, OTAs may not be able to pass some pre-install checks, at least this has happened to me on N4 before. I added one line to /etc/build.prop, also one of the older SuperSU versions had to be uninstalled for pre-install OTA checks to pass.

Whyzor said:
Can people please post confirmation of TWRP or CWM recoveries + rooting working without problems if they've done it? I know it's unofficially supported at this time, but getting some data collected would be useful.
Click to expand...
Click to collapse
There isn't *yet* a booting custom recovery for the Nexus 5. Give it a couple of days.

I see some Desire folks
Did u order one chromium?

Is unlocking the bootloader going to be the same as on my GNex, where it wipes the device in the process? If so, this will be the first thing I do when I get it out of the box on Monday.

talz13 said:
Is unlocking the bootloader going to be the same as on my GNex, where it wipes the device in the process? If so, this will be the first thing I do when I get it out of the box on Monday.
Click to expand...
Click to collapse
If you wipe cache exactly after you unlock the bootloader, without booting, no.

Nbsss said:
I see some Desire folks
Did u order one chromium?
Click to expand...
Click to collapse
Not yet. Hoping to eventually get it though.

Whyzor said:
Can people please post confirmation of TWRP or CWM recoveries + rooting working without problems if they've done it? I know it's unofficially supported at this time, but getting some data collected would be useful
Click to expand...
Click to collapse
There are currently no working custom recoveries, so it really only makes sense to unlock the bootloader for now. That way you'll be ready to continue on with the guide right when a stable recovery is released.
Sent using xda-developers app

Nbsss said:
I see some Desire folks
Did u order one chromium?
Click to expand...
Click to collapse
I'm not a really famous desire user but yes I bought it. Did you buy it to? Happy to see some other desire users.
Sent from my HTC Desire using XDA Premium 4 mobile app

Maybe it's a silly question, but can I unlock the bootloader before even booting up the phone for the first time? Can this cause some problems?

boysetsfire said:
Maybe it's a silly question, but can I unlock the bootloader before even booting up the phone for the first time? Can this cause some problems?
Click to expand...
Click to collapse
It should work fine, but whats wrong with booting it up for the first time?

Chromium_ said:
It should work fine, but whats wrong with booting it up for the first time?
Click to expand...
Click to collapse
Nothing wrong, just the laziness of not wanting to do the initial setup two times

Chromium_ said:
There are currently no working custom recoveries, so it really only makes sense to unlock the bootloader for now. That way you'll be ready to continue on with the guide right when a stable recovery is released.
Sent using xda-developers app
Click to expand...
Click to collapse
abaaaabbbb63 said:
There isn't *yet* a booting custom recovery for the Nexus 5. Give it a couple of days.
Click to expand...
Click to collapse
Ok, the wording in OP is:
"Currently neither recovery has official support for the Nexus 5, so the download links below are unofficial and may not be functioning 100% correctly."
and:
"**Warning: Currently there are no officially stable custom recoveries, so i would only recommend unlocking the bootloader for now**"
Which implied that it does work, just not thoroughly tested. Now from the recent replies you're saying it DOES NOT boot at all into recovery?

Whyzor said:
Ok, the wording in OP is:
"Currently neither recovery has official support for the Nexus 5, so the download links below are unofficial and may not be functioning 100% correctly."
and:
"**Warning: Currently there are no officially stable custom recoveries, so i would only recommend unlocking the bootloader for now**"
Which implied that it does work, just not thoroughly tested. Now from the recent replies you're saying it DOES NOT boot at all into recovery?
Click to expand...
Click to collapse
Yes that is correct, they do not boot. I will update the OP now, sorry for the confusion.
Originally I had read the following threads and it seemed that they were somewhat functioning, but it is now confirmed that neither one boots.
TWRP
CWM

[OnePlus 3] How to Unlock Bootloader, Flash TWRP, Root, Nandroid Backup and More !

Credits :- @Snoop05 for 15 sec ADB Installer , @Grarak for TWRP , @Chromium for the thread template !
{
"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"
}

Information​
Rooting this device is actually quite a simple and easy process. Before you begin, it is recommended that you at least try to understand what each part of the process will do. Although this guide will elongate each step in order to show all of the details, the method used can be broken up into 3 main steps: Unlocking the Bootloader, Installing a Custom Recovery and finally Rooting. Each new step relies on the previous step to have been completed, and a basic summary of each part is:
Unlocking Bootloader: Opens the door to the internal memory of the device to be written on to. This allows you to flash images onto the main partitions of the phone.
Installing a Custom Recovery: A custom recovery is flashed onto the recovery partition of the device and overwrites the stock recovery that exists by default. Custom recoveries bring lots of functionality and give you the ability to perform wipes, install flashable zips, create full backups of your NAND (Nandroid backup), and various other features. An unlocked bootloader is needed to install a custom recovery.
Rooting: You can gain root by either flashing via recovery a pre-rooted custom rom, or flashing a zip containing the SuperSU binaries. A custom recovery is necessary to do this.
After completing these steps your phone will be rooted, the phone will have a custom recovery installed, and the phones bootloader will be unlocked. This, in our opinion, is the most practical and beneficial method for rooting your phone. It gives you some basic adb/fastboot knowledge, and should hopefully help you have a decent understanding of what is going on. Also this method will work regardless of what android version your phone has.
If you are confused by anything in this guide, we would highly suggest getting it clarified being before moving on. Ask your question in this thread and we or someone else will likely answer. Also we would suggest that you read over the whole thread a few times before actually doing anything to the phone.
Understood? Good...let's begin

Setup, Preparation and Prerequisites​
Basic tasks that may be referred to throughout this guide:
Open command prompt - Press Shift + Right Click anywhere on the screen and select Open Command Window here/
Enter fastboot mode- Turn the phone off. Hold volume up + power until the "fastboot" screen appears. [Alternatively, if Advanced Reboot is enabled, you can press Reboot -> Bootloader from the power menu.]
Enter recovery mode - Turn the phone off. Hold volume down + power until the "OnePlus Logo" screen appears. [Alternatively, if Advanced Reboot is enabled, you can press Reboot -> Recovery from the power menu.]
ADB and Fastboot Installation​
1. Download the ADB For Windows from here :- https://drive.google.com/open?id=0B0MKgCbUM0itNVB1elljU2NPR0k
2. Run the .exe file downloaded from above as Administrator.
3. Press 'Y' every time the installer asks for.
4. Continue Driver Installation.
Now,ADB and Fastboot have been installed on your PC. Great !
Some Important Things​
Show File Extensions - Open a command prompt window and run "Control folders" (without the quotes). Go to the View tab and uncheck the "Hide extensions for known file types" option. This will help avoid confusion when renaming files.
Battery - Ensure that your phone has at least 60% battery remaining, and that your PC is plugged in and wont shut down spontaneously during the process. The procedure doesn't take very long , but its best to have enough charge in case something goes wrong.
Backup (Optional) - Unlocking the bootloader will/should completely wipe all data from the device. This includes apps, settings and even the contents of the internal sdcard (pictures, music, etc.). Copy all important files off the phone onto a PC or upload them to a cloud.
Downloads
Download a custom recovery and the SuperSU zip below. Place both files on the desktop.
TWRP:
TWRP
Root:
SuperSU​

USB Debugging - On your phone go to Settings > About phone > Tap on Build number 7 times. This will enable Developer options. Now go back to Settings > Developer options > Enable USB debugging
Enable OEM Unlocking - On your phone go to Settings > Developer options. Then enable the 'OEM Unlocking' option. Also,a free advice, make sure that from now on,OEM unlocking option is enabled before you reboot. Sometimes,it might get disabled itself.
Enable Advanced Reboot - On your phone go to Settings > Developer options. Then enable the 'Advanced Reboot' option.
1. Unlocking Bootloader
Turn the phone off. Then boot it into fastboot mode by holding volume up + power. The phone will display "fastboot" text indicating that it has successfully entered fastboot mode.
Plug the phone into your PC, then open a command prompt window on the desktop (Shift + Right Click -> Open Command Window here) and type :-
Code:
fastboot devices
This command will list the connected devices. If your phones serial number shows up you are good to go and may continue. If the phone is NOT listed this indicates that your drivers are not installed correctly. In order for you to continue you must fix your drivers so that your phone is listed under fastboot devices.
If the phone has been recognized by the command above, proceed to unlocking the bootloader with the following command: Remember that this step will/should wipe EVERYTHING off the phone
Code:
fastboot oem unlock
After the above command has finished excuting, run the following
Code:
fastboot reboot
Now, your phone will reboot. Continue to the next step to install Custom Recovery ...

Wait until the phone has fully booted up into android, then adjust the following settings on the phone:
USB Debugging - On your phone go to Settings > About phone > Tap on Build number 7 times. This will enable Developer options. Now go back to Settings > Developer options > Enable USB debugging
Enable OEM Unlocking - On your phone go to Settings > Developer options. Then enable the 'OEM Unlocking' option. Also,a free advice, make sure that from now on,OEM unlocking option is enabled before you reboot. Sometimes,it might get disabled itself. [Most probabaly,it will already be enabled as you did it above.Then,NO NEED to disable and enable it.]
Enable Advanced Reboot - On your phone go to Settings > Developer options. Then enable the 'Advanced Reboot' option.
2. Flashing TWRP
Turn the phone off. Then boot it into fastboot mode by holding volume up + power.
Rename the recovery file that you downloaded above to recovery.img. *Make sure that you rename it to recovery.img NOT recovery.img.img* ,Make sure that this file is placed on the desktop.
Open a new command prompt on desktop and run the following commands:
Code:
fastboot flash recovery recovery.img
Once the flash has completed, Don't use the "Fastboot Reboot" Command Instead Unplug Your phone then Manually boot it into recovery by keeping Power + Volume Down button pressed.
In TWRP, select Reboot and then select System. Now your phone will boot into System and you have cleared Steps 2/3 . Grats.
So, now, time has come to do what we want to achieve through all this. The 'ROOT' . Keep following .
But,before that, take a Nandroid Backup.
3. Making a Nandroid Backup
Warning: before you make a backup with TWRP you must remove all lockscreen security. If you do not do this you will not be able to unlock your device after restoring your backup (entering your pin will result in an "incorrect pin" message), you'll be forced to perform a factory reset to boot into Android. To remove lockscreen security go to Settings>Security>Screen Lock and set it to swipe/none.
A Nandroid Backup is a very important thing to have before installing any custom software on your device. It's basically a backup of your stock system that you can fall back on if anything goes wrong or if you just want your stock ROM back. You can also use Nandroid Bckup to create a backup of your favorite ROM set up exactly the way you like it. The backup you create can be easily restored using the restore tool in TWRP recovery.
Boot into TWRP Recovery .
Go to Backup Menu and select all the listed partitions.
Swipe to take Backup. The process will take some time.
Reboot
Now, let us continue to rooting !

4. Rooting
Now that your phone has an unlocked bootloader and a custom recovery installed, you have two options to gain root (Pick one or the other. You don't need to do both. ).
Option A) Flash SuperSU binaries which will give you root with the stock ROM
Confirm that you have downloaded the SuperSU zip from the downloads section above. Connect OP3 to PC and send SuperSU to your phone.
Turn the phone off. Then boot into recovery mode by holding volume down + power. Leave the phone at the main screen of the custom recovery for now.
Install > browse to SuperSU zip and select it
Swipe to confirm the installation. Then reboot.
Option B) Flash a custom rom which will come pre-rooted
Note that not all custom roms will be pre rooted, however the majority of them are. Read the OP of the ROM thread to see what the verdict is.
Copy a custom rom (you can find these in the OnePlus 3 ROMs, Kernels, Recoveries, & Other Development section of XDA or Custom OP3 Software section on OnePlus Forums) onto the phone (remember the location of where you copy it to)
Turn the phone off then boot into recovery mode by holding volume down + power. To install a custom ROM the general procedure to follow is: wipe Dalvik + System + Data + Cache, flash ROM, flash GApps.
Wipe > Advanced Wipe > Select Dalvik + System + Data + Cache > Swipe to Wipe
Install > browse to the location where you previously copied the ROM zip and select it > Swipe to confirm the installation
Install GApps using same process as ROM, then reboot.
Keep in mind that the first boot after installing a custom ROM & wiping the phone may take longer than usual, as the phone will need to rebuild the dalvik cache and initialize other first boot stuff.
Congrats! That is all! Your phone now has an unlocked bootloader, a custom recovery installed and is rooted. Enjoy !
The very first thing we highly recommend you to do now is to take EFS Backup and save it at your cloud and PC. It is very very important.
5. Making an EFS Backup
All too often, we've seen folks who have a corrupted or missing EFS Partition. This results in your IMEI being lost and no cellular activity on the device at all. This can be a royal PITA to fix, and some folks haven't been able to fix it at all. You can take a precautionary measure to safeguard yourself against this by taking a couple of minutes to back up your modemst files.
Open up Terminal Emulator on your phone (if you don't have it you can download it here).
Once it's open you'll be greeted with a command line prompt, in which you can enter text commands, the first thing you need to do is enable root access by entering this line (press the enter key on your on-screen keyboard after each command to issue it):
Code:
su
If this is the first time you've used Terminal Emulator a Superuser or SuperSU popup will appear, make sure you grant root access.
Now enter these two commands:
Code:
dd if=/dev/block/sdf1 of=/sdcard/modemst1.bin bs=512
Code:
dd if=/dev/block/sdf2 of=/sdcard/modemst2.bin bs=512
This will place two files (modemst1.bin & modemst2.bin) on your internal storage. Make sure you copy them to your PC and other Clouds immediately so that you have a backup there to use if you need to restore it in future.
That's it !! Incase you ever need to restore Nanroid or EFS Backups, continue.
6. Restoring a Nandroid Backup
Note: If you happened to forget to remove lockscreen security (PIN/Pattern/Fingerprint) before creating your backup, and you cannot get into your OS after restoring, you can do the following to fix the issue. Boot into TWRP and use the built in file manager to delete /data/sytem/locksettings.db. This should be enough to get you into your OS again. If it isn't you can also try deleting /data/system/locksettings.db-shm and /data/system/locksettings.db-wal. If this still doesn't fix your issue you can delete /data/system/gatekeeper.password.key and /data/system/gatekeeper.pattern.key.
Boot into TWRP Recovery .
[Only and Only if you want to restore /system and /data too from the Backup] Wipe > Advanced Wipe > Select Dalvik + System + Data + Cache > Swipe to Wipe. Go back to TWRP Home.
Go to Restore Menu and select the backup you want to restore.
Select the partitions you want to restore.
Swipe to Restore. The process will take some time.
Reboot
7. Restoring an EFS Backup
If by chance you end up with a corrupt EFS partition all you need to do is flash the files back to your device using fastboot.
Boot into fastboot mode (power + volume up) and connect your phone to your PC via usb cable.
Keep modemst1.bin and modemst2.bin (backed up earlier) on your desktop and open command window there.
These fastboot commands will restore the files:
Code:
fastboot flash modemst1 modemst1.bin
Code:
fastboot flash modemst2 modemst2.bin
Reboot your device.
Code:
fastboot reboot
Now disconnect phone from PC. Hope your IMEI etc is back.
That's it for the guide. Enjoy !

Source of TWRP image?

anandbibek said:
Source of TWRP image?
Click to expand...
Click to collapse
Oneplus 3 forums. I think it's against XDA rules for me to link it there, so I'll link a similar post
http://forum.xda-developers.com/oneplus-3/how-to/custom-rom-op3-t3398784

Does rooting the op3 voids warrenty ???
just now got the phone .. Need to restore backups from titanium backup
And kindly tell me whether after unlocking bootloader only datas will be erased or the stock rom too ??

Only data
Sent from my LG-D855 using XDA-Developers mobile app

HatRiGt said:
Does rooting the op3 voids warrenty ???
just now got the phone .. Need to restore backups from titanium backup
And kindly tell me whether after unlocking bootloader only datas will be erased or the stock rom too ??
Click to expand...
Click to collapse
#YOLO
yes and yes

HatRiGt said:
Does rooting the op3 voids warrenty ???
just now got the phone .. Need to restore backups from titanium backup
And kindly tell me whether after unlocking bootloader only datas will be erased or the stock rom too ??
Click to expand...
Click to collapse
No. Rotting OP3 doesn't void warranty, as is the case with OPO, OP2, OPX.
Only Data.
Sent from my OnePlus2 using XDA Labs

Has anyone successfully rooted the device with this method yet? Any reports on how you had to modify it or what may have gone wrong and how you corrected it?

i rooted my op3 successfully =) the only bad sideeffect is the "warning bootloader is open" message. this only appears at boot and tells that the devices is not googles trusted anymore.

Dr4g0n said:
i rooted my op3 successfully =) the only bad sideeffect is the "warning bootloader is open" message. this only appears at boot and tells that the devices is not googles trusted anymore.
Click to expand...
Click to collapse
A kernel with dm verity disabled can be flashed. None for now. Will try to get one soon.
Best Regards,
Naman.
Sent from my OnePlus2 using XDA Labs

Dr4g0n said:
i rooted my op3 successfully =) the only bad sideeffect is the "warning bootloader is open" message. this only appears at boot and tells that the devices is not googles trusted anymore.
Click to expand...
Click to collapse
And opening the bootloader probably disables the possibility of getting OTA updates as well? Could it be rooted without opening the bootloader, so OTA updates can still be obtained?

UnnamedFile said:
And opening the bootloader probably disables the possibility of getting OTA updates as well? Could it be rooted without opening the bootloader, so OTA updates can still be obtained?
Click to expand...
Click to collapse
Yes. It is because of dm verity
Sent from my OnePlus2 using XDA Labs

Dr4g0n said:
i rooted my op3 successfully =) the only bad sideeffect is the "warning bootloader is open" message. this only appears at boot and tells that the devices is not googles trusted anymore.
Click to expand...
Click to collapse
UnnamedFile said:
And opening the bootloader probably disables the possibility of getting OTA updates as well? Could it be rooted without opening the bootloader, so OTA updates can still be obtained?
Click to expand...
Click to collapse
BTW You guys rooted from this guide ? Because, ideally, it should disable dm verity.
Sent from my OnePlus2 using XDA Labs

I don't guess you can do a "fastboot boot recovery.img" like on Nexus devices? I'd like to keep stock recovery but will flash twrp if that's the only option once the stock images are available.

lensgrabber said:
I don't guess you can do a "fastboot boot recovery.img" like on Nexus devices?
Click to expand...
Click to collapse
Nope, I just tried:
http://forum.xda-developers.com/showpost.php?p=67349425&postcount=14
I'd like to keep stock recovery but will flash twrp if that's the only option once the stock images are available.
Click to expand...
Click to collapse
Same here.

OnePlus 5: Unlock Bootloader | Flash TWRP | Root | Nandroid & EFS Backup & More !!

OnePlus 5: Unlock Bootloader | Flash TWRP | Root | Nandroid & EFS Backup & More !!
{
"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"
}
Before you start, OTA up to the latest System Update available.
Settings > System Updates > Download & Install the latest available​

Introduction​​
Rooting this device is actually quite a simple and easy process. Before you begin, it is recommended that you at least try to understand what each part of the process will do. Although this guide will elongate each step in order to show all of the details, the method used can be broken up into 3 main steps: ​
Unlocking the Bootloader
Installing a Custom Recovery
Gaining Root Access
Each new step relies on the previous step so please follow the entire process and a basic summary of each part is described as below:
Unlocking Bootloader​​Opens the door to the internal memory of the device to be written on to. This allows you to flash images onto the main partitions of the phone.​
Installing a Custom Recovery​​A custom recovery is flashed onto the recovery partition of the device and overwrites the stock recovery that exists by default. Custom recoveries bring lots of functionality and give you the ability to perform wipes, install flashable zips, create full backups of your device (Nandroid backup), and various other features. An unlocked bootloader is needed to install a custom recovery.
Gaining Root Access​​You can gain root by either flashing via recovery a pre-rooted custom rom, or flashing a zip containing the SuperSU binaries or by Flashing Magisk Zip for a system less root. A custom recovery is necessary to do this.
After completing these steps your phone will be rooted, the phone will have a custom recovery installed and an unlocked bootloader. This, in my opinion, is the a practical and beneficial method for rooting your phone. It will give you some basic adb/fastboot knowledge, and should hopefully help you have a decent understanding of the entire process. This method will work regardless of any android version on the phone.
If you are confused by anything in this guide, I highly suggest getting it clarified being before moving on. Ask your question in this thread and I or someone else will likely answer. Also we would suggest that you read over the whole thread a few times before actually doing anything to the phone.​

Setup, Preparation & Prerequisites​​Basic tasks that may be referred to throughout this guide:​​Open Command Prompt: Press Shift + Right Click anywhere on the screen and select Open Command Window here
Enter Fastboot/Bootloader Mode: Turn the phone off. Hold volume up + power until the "fastboot" screen appears. [Alternatively, if Advanced Reboot is enabled, you can press Reboot > Bootloader from the power menu.]
Enter Recovery Mode: Turn the phone off. Hold volume down + power until the "OnePlus Logo" screen appears. [Alternatively, if Advanced Reboot is enabled, you can press Reboot -> Recovery from the power menu.]
ADB and Fastboot Installation​1. Download the ADB For Windows from here Credits @Snoop05 his Original XDA Thread Here
Or You can manually update Fastboot and ADB binaries here Credits @lj50036 his Original XDA Thread Here
2. Run the .exe file downloaded from above as Administrator.
3. Press 'Y' every time the installer asks for.
4. Continue Driver Installation.
Now, ADB and Fastboot have been installed on your PC and should be Working as desired.
Things To Remember​Show File Extensions :good:
Open a command prompt window and run "Control folders" (without the quotes). Go to the View tab and uncheck the "Hide extensions for known file types" option. This will help avoid confusion when renaming files.
Battery :good:
Ensure that your phone has at least 60% battery remaining, and that your PC is plugged in and wont shut down spontaneously during the process. The procedure doesn't take very long , but its best to have enough charge in case something goes wrong.
Backup (Optional) :good:
Unlocking the bootloader will/should completely wipe all data from the device. This includes apps, settings and even the contents of the internal sdcard (pictures, music, etc.). Copy all important files off the phone onto a PC or upload them to a cloud.
USB Debugging :good:
On your phone go to Settings > About phone > Tap on Build number 7 times. This will enable Developer options. Now go back to Settings > Developer options > Enable USB debugging
Enable OEM Unlocking :good:
On your phone go to Settings > Developer options. Then enable the 'OEM Unlocking' option. Also make sure that from now on, OEM unlocking option is enabled before you reboot as sometimes, it might get disabled itself.
Enable Advanced Reboot :good:
On your phone go to Settings > Developer options. Then enable the 'Advanced Reboot' option.

Unlocking Bootloader​
Turn the phone off. Then boot it into fastboot mode by holding volume up + power or select reboot to bootloader if advanced reboot is activated via developer options. The phone will display "fastboot" text indicating that it has successfully entered fastboot mode.
Plug the phone into your PC, then open a command prompt window on the desktop (Shift + Right Click -> Open Command Window here) and type:
Code:
fastboot devices
This command will list the connected devices. If your phones serial number shows up you are good to go and may continue. If the phone is NOT listed this indicates that your drivers are not installed correctly. In order for you to continue you must fix your drivers so that your phone is listed under fastboot devices.
If the phone has been recognized by the command above, proceed to unlocking the bootloader with the following command:
Remember this Step will WIPE EVERYTHING off the phone so Backup all your Data
Code:
fastboot oem unlock
You would be greeted with a Unlock Bootloader Warning page, Hit the Vol button to select Yes and turn it Blue and Hit the Power Button to Execute the selection
Your device will reboot, show you a Secure boot warning, reboot into stock recovery and wipe all data. Once done, your phone will reboot into the OS.
Please continue and follow the next post to install Custom Recovery

Flashing TWRP Recovery
Downloads:
Recovery:
Codeworkx TWRP | Blu_Spark TWRP
Magisk​
Wait until the phone has fully booted up into android, then adjust the following settings on the phone:
USB Debugging:
On your phone go to Settings > About phone > Tap on Build number 7 times. This will enable Developer options. Now go back to Settings > Developer options > Enable USB debugging
Enable OEM Unlocking:
On your phone go to Settings > Developer options. Then enable the 'OEM Unlocking' option and make sure that from now on, OEM unlocking option is enabled before you reboot. Sometimes, it might get disabled itself.
Enable Advanced Reboot:
On your phone go to Settings > Developer options. Then enable the 'Advanced Reboot' option.
Download all the files, place SuperSU or Magisk on Device Internal Memory and TWRP img in the Android Folder under the Platform Tools folder in C Drive
Then boot it into fastboot/bootloader mode by holding volume up + power or selecting the reboot to bootloader via advanced reboot options.
Open a new command prompt in the same location and run the following commands:
Code:
fastboot flash recovery (file name).img
Once the flash has completed, Don't use the "Fastboot Reboot" Command Instead Unplug Your phone then Manually boot it into recovery by keeping Power + Volume Down button pressed or you can also use the command:
Code:
fastboot boot recovery.img
PS: DO NOT BOOT IN OS JUST YET & CONTINUE TO THE ROOTING POST

Gaining Root Access​
This is a continued post from the above post...
For Users who want to remain Encrypted: :fingers-crossed:
1. Boot into TWRP Recovery and allow system modifications.
2. Swipe right and enable modifications.
3. Select your preferred Language, Tap “Never show this screen on boot again,” and Swipe allow modification.
4. Navigate to Install and select Magisk Or SuperSU to root OnePlus 5.
5. Swipe to confirm the flash
6. Reboot System
Keep in mind that the first boot after wiping the phone may take longer than usual, as the phone will need to rebuild the dalvik cache and initialize other first boot and would reboot a few times due to SuperSU Flash.
For Users who want to Decrypt Data have to Format Data & Flash No Verity OP5 Zip :fingers-crossed:
1. Boot into TWRP Recovery and allow system modifications.
2. Swipe right and enable modifications.
3. Select your preferred Language, Tap “Never show this screen on boot again,” and Swipe allow modification.
Go to “Wipe” section and tap “Format Data”, and type “yes” to mount internal storage
4. Download & Transfer no_verity_op5.zip to the device over MTP from here Credits @snowwolf725
5. Go to “Install” section, select no_verity_op5.zip, and swipe to confirm the flash
6. Transfer latest Magisk/SuperSU to the device over MTP to your Oneplus 5 & Swipe to confirm the flash
7. Reboot System
* MTP, known as Media Transfer Protocol, is the same way you transfer files from your PC to your device when booted into system.
Congrats! That is all! Your Device now has an unlocked bootloader, a custom recovery installed and is rooted along with your preference of staying encrypted or decrypted.
Warning: Do not flash partial update OTAs (under 1 GB) on a modified device! If you want to use partial OTAs, you must first flash a full OTA that it applies to, and then flash the partial OTA from stock recovery. Flashing partial OTAs from TWRP will either fail or soft brick your device. You can return to a usable state by flashing full zips in recovery.
Enjoy :fingers-crossed:

Making a Nandroid Backup​Warning: before you make a backup with TWRP you must remove all Lockscreen Security. If you do not do this you will not be able to unlock your device after restoring your backup (entering your pin/pattern/password will result in an "incorrect pin/pattern/password" message), you'll be forced to perform a factory reset to boot into Android.
To remove lockscreen security go to
Settings > Security > Screen Lock and set it to Swipe/None.
A Nandroid Backup is a very important thing to have before installing any custom software on your device. It's basically a backup of your stock system that you can fall back on if anything goes wrong or if you just want your stock ROM back.
You can also use Nandroid Bckup to create a backup of your favorite ROM set up exactly the way you like it. The backup you create can be easily restored using the restore tool in TWRP recovery.
To Create Nandroid Backup:
1. Boot into TWRP Recovery .
2. Go to Backup Menu and select all the listed partitions.
3. Name the Backup if needed (Optional)
4. Swipe to take Backup.
This proces should take 4 to 8 minutes depending upon the size of data.
5. Reboot System when done.
Your Nandroid will be stored in the Backup Folder inside TWRP Folder /sdcard/TWRP/BACKUPS

Restoring a Nandroid Backup​
1. Boot into TWRP Recovery
2. Go to Restore Menu and select the backup you want to restore.
3. Select the partitions you want to restore.
4. Swipe to Restore. The process will take 6 to 10 minutes.
5. Reboot system once done
Note: If you happened to forget to remove lockscreen security (PIN/Pattern/Password) before creating your backup, and you cannot get into your OS after restoring, you can do the following to fix the issue.
Boot into TWRP
Use the TWRP File Manager and Navigate to /data/sytem/ and delete the following files:
locksettings.db
locksettings.db-shm
locksettings.db-wal.
gatekeeper.password.key
gatekeeper.pattern.key
You may or may not have all the above files so delete the ones you have.
Reboot the phone and (if you've set a PIN) enter it to decrypt the storage one more time. After that you can simply unlock your phone with a swipe.
Upon Boot > Go into Settings > Security > set your preferred unlock method
Android will ask you if you want to set a boot-time code too so select as per convenience.

Making an EFS Backup​All too often, we've seen folks who have a corrupted or missing EFS Partition. This results in your IMEI being lost and no cellular activity on the device at all. This can be a royal PITA to fix, and some folks haven't been able to fix it at all. You can take a precautionary measure to safeguard yourself against this by taking a couple of minutes to back up your modemst files.
Download & Open up Terminal Emulator on your phone from here
Once it's open you'll be greeted with a command line prompt, in which you can enter text commands, the first thing you need to do is enable root access by entering this line (press the enter key on your on-screen keyboard after each command to issue it):
Code:
su
If this is the first time you've used Terminal Emulator a Superuser or SuperSU popup will appear, make sure you grant root access.
Now enter these two commands:
Code:
dd if=/dev/block/sdf1 of=/sdcard/modemst1.bin bs=512
Code:
dd if=/dev/block/sdf2 of=/sdcard/modemst2.bin bs=512
This will place two files (modemst1.bin & modemst2.bin) on your internal storage.
Make sure you copy them to your PC and Cloud immediately so that you have a backup there to use if you need to restore it in future.
That's it !! In case you ever need to restore Nanroid or EFS Backups, please continue and follow the next post...
Restoring an EFS Backup​If by chance you end up with a corrupt EFS partition all you need to do is flash the files back to your device using fastboot.
Boot into fastboot mode (power + volume up) and connect your phone to your PC via usb cable.
Keep modemst1.bin and modemst2.bin (backed up earlier) on your desktop and open command window there.
These fastboot commands will restore the files:
Code:
fastboot flash modemst1 modemst1.bin
Code:
fastboot flash modemst2 modemst2.bin
Reboot your device.
Code:
fastboot reboot
Now disconnect phone from PC. Your IMEI should be back.
That's it for this guide, Enjoy :highfive:

Thank you for your support !!

First OTA 4.5.1

Theoretically unlocking the bootloader and flashing TWRP should be identical to the OnePlus 3/3T and previous devices, i.e. just like a Nexus (R.I.P.).

jmazzamj said:
Theoretically unlocking the bootloader and flashing TWRP should be identical to the OnePlus 3/3T and previous devices, i.e. just like a Nexus (R.I.P.).
Click to expand...
Click to collapse
Indeed its similar. Just making it clear for the new users here in one thread so there is no confusion.

Funk Wizard said:
Indeed its similar. Just making it clear for the new users here in one thread so there is no confusion.
Click to expand...
Click to collapse
Thank you for this! I'm going to get this device as soon as it's back in stock. It will be my first ever OnePlus device (coming from a Pixel XL). I'll still be using that but the dev support seems to be the highest with these devices.
Definitely going to use this guide to get all setup, so thanks again!
Just wondering though, I've never dealt with this dm-verity thing, what is this exactly?
Also, the day I decide to sell this phone for the next generation OnePlus (6), is it relatively simple to get back to stock and relock the bootloader?
Sorry for all the questions, just want to be thorough before doing all of this and potentially bricking my new device lol

Thank you!

Link to TWRP?
Sent from my OnePlus 3T using XDA Labs

rickysidhu_ said:
Thank you for this! I'm going to get this device as soon as it's back in stock. It will be my first ever OnePlus device (coming from a Pixel XL). I'll still be using that but the dev support seems to be the highest with these devices.
Definitely going to use this guide to get all setup, so thanks again!
Just wondering though, I've never dealt with this dm-verity thing, what is this exactly?
Also, the day I decide to sell this phone for the next generation OnePlus (6), is it relatively simple to get back to stock and relock the bootloader?
Sorry for all the questions, just want to be thorough before doing all of this and potentially bricking my new device lol
Click to expand...
Click to collapse
First of all Welcome to the Oneplus Community Buddy, hope your get the device soon, i am also waiting for my unit likewise :fingers-crossed:
DM Verity is just another screen warning just like the secure boot screen, which depicts an unlocked bootloader and a modified recovery, it can be taken care off easily and even if you dont it wont harm in any way just take some addition 5 to 7 seconds on boot. I am here to help so it will be taken care off.
Also its easy to get back to stock as all full zips and both TWRP and Stock Recovery Flashable so just a process of 5 minutes to be precise once you have the required downloads and once stock bootloader can also be locked again via fastboot command.
If you just follow the steps on the guide, everything will be fine. Just wait for the official TWRP source to be released, should not be long though.
Thanks again for supporting Oneplus and Welcome to the Community :highfive:

MrMeeseeks said:
Link to TWRP?
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
Will update when released, waiting for the official maintainer to be assigned, or if someone can build an unofficial build to begin with :fingers-crossed:

Funk Wizard said:
Thread Under Construction...
Waiting for hands on experience with the device !!​
Click to expand...
Click to collapse
So fast?
You guys are the best!

Hey, many thanks for the guide.
I will be coming from an LG G6.
Question: since there is no external SD card, if we place SuperSU, DM-Verify etc on our internal memory...when we unlock the bootloader will the phone also wipe the internal sd memory??

How To Guide [GUIDE] [Magisk] [Unlock / ROOT / Keep Root]

Magisk VariantStable / Beta / CanaryReleaseOfficialAndroid / OOSOOS 11 and aboveMaintainertopjohnwuProject LinkGitHubZygiskNoDenyListNoMagiskHideYesModules RepoYesDownload LinkGitHub
This tutorial will :
provide you with all the steps to root your Oneplus 10 Pro (with your bootloader already unlocked)
provide you with all the steps to unlock your Oneplus 10 Pro bootloader
provide you with all the steps to keep root during/after an OTA (system update)
provide you with a lot tricks if you have troubleshooting questions
provide you with a lot of solutions of you have softbricked your Oneplus 10 Pro
provide you with all the ways if you want to bring back your Oneplus 10 Pro to unroot & lock back the bootloader
STEPS to root your device:
I recommand to update first your device with all OTA available using Settings/updates before unlocking & rooting it.
Root your Oneplus 10 Pro (with Bootloader already unlocked)​Step 1 - Booting temporarily root​1. Connect your phone to your pc and boot it into fastboot mode. You can leave it connected throughout this guide.
2. First, enter the following command in the PowerShell/Terminal window to ensure that your PC can communicate with the phone over the fastboot interface.
"fastboot devices"
The command should return your phone’s unique ID. In case it doesn’t, then make sure that you have the required USB drivers installed and restart your PC. You can also use TOOL ALL IN ONE, not officially updated to Oneplus 10 Pro but once install go to Others options and go to Install drivers.
3. Code once in fastboot mode:
"fastboot boot magisk_boot.img" (use the "magisk_boot.img" from the above zip file)
Change to the exact name "magisk_boot.img" of the boot that has been patched in the above zip file
"fastboot reboot"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You could flash this boot.img, but it's safer to temporarily boot from it without overwriting your existing image in case anything went wrong along the way. The effect is that you still get root access without modifying your device, and then you can use the much safer Magisk direct install option, which has some safeguards in place.
By booting with the patched image, you now have temporary root access. To make it permanent open Magisk app.
a. Select the Install option.
b. Use Direct Install (Recommended) to root your internal boot.img
Step 2 - Reboot and your device is now rooted !​Unlock the Bootloader and Root the OnePlus 10 Pro​Step 1 – Enable OEM unlocking​You need to enable OEM unlocking, which can be done by enabling the developer settings on your device. To do so, go to Settings > About phone and repeatedly tap Build number. Developer options will then be added to your system settings, where you can then enable OEM unlocking.
Step 2 – Unlock your phone
Set up adb, reboot into your bootloader, and run the following command. Yes, it’s really that simple!
"fastboot oem unlock"
You can reboot into the bootloader by switching on USB debugging, setting up adb and fastboot and typing “adb reboot bootloader”. Alternatively, you can hold volume down and the power button to boot up your device. USB debugging is also located under the developer options.
Unlocking the bootloader wipes your device :
Step 3 - Booting temporarily root​1. Connect your phone to your pc and boot it into fastboot mode. You can leave it connected throughout this guide.
2. First, enter the following command in the PowerShell/Terminal window to ensure that your PC can communicate with the phone over the fastboot interface.
"fastboot devices"
The command should return your phone’s unique ID. In case it doesn’t, then make sure that you have the required USB drivers installed and restart your PC. You can also use TOOL ALL IN ONE, not officially updated to Oneplus 10 Pro but once install go to Others options and go to Install drivers.
3. Code once in fastboot mode:
"fastboot boot magisk_boot.img" (use the "magisk_boot.img" from the above zip file)
Change to the exact name "magisk_boot.img" of the boot that has been patched in the above zip file
"fastboot reboot"
You could flash this boot.img, but it's safer to temporarily boot from it without overwriting your existing image in case anything went wrong along the way. The effect is that you still get root access without modifying your device, and then you can use the much safer Magisk direct install option, which has some safeguards in place.
Step 4 - Install magisk​Install the latest Magisk Canary apk on your phone. Open it and:
a. Select the Install option.
b. Use Direct Install (Recommended) to root your internal boot.img
Step 5 - Reboot and your device is now rooted !​Keep Root and OTA updates​How to update OTA and KEEP ROOT
It is advised to disable or even uninstall all magisk modules to be safe!
How: go to Magisk application/modules/disable &/or uninstall
Option 1: With full OTA Access (BA/DA) :
Step 1 - Get & install the full OTA zip file​1. Go to System-Update or update get the OTA using Oxygen Updater
2. Tap OK when the message that you are rooted appears
3. Tap "Download and install" or local update if OTA from Oxygen Updater
4. Wait until you are prompted to reboot - DO NOT REBOOT NOW!
5. Open Magisk Manager
a. Select the Install option.
b. Use Install to inactive slot
Step 2 - Reboot and enjoy your device still rooted with latest OTA installed !​​Option 2: with incremental OTA Access (AA) :​Step 1 - Get back your original boot image​1. open the Magisk Manager application, select “Uninstall”, and choose the “Restore Images” option. Magisk will restore your phone’s stock boot image that was backed up during the rooting process.
2. Now go to “Settings” → “System” → “System updates” and select “Download and Install Now” to install the OxygenOS OTA update on your rooted OnePlus 10 Pro
3. Open Magisk Manager
a. Select the Install option.
b. Use Install to inactive slot
Step 2 - Reboot and enjoy your device still rooted with latest OTA installed !​
Troubleshooting questions :​Before reporting any trouble, follow the steps below in order to have GooglePlay certified, keep L1 Widevine & pass CTS :
Step 1 - Magisk Settings​1. Once rooted, in Magisk setting, select MagiskHide and Systemless host
2. In MagiskHide select GMS, Netflix, Google Store & any application you may find sensitive to Magisk detection
For Netflix, go to Settings, Appplications & select Netflix:
a-force stop the app
b-clear cache and storage
c-hide the App in magisk
d-restart phone to recovery and clear cache
If you can't install/update Netflix install the latest Netflix from apkmirror manually (like any other apk file)
Hide everything under Google play services and store.:
3. Reboot
Step 2 - Clear caches​Clear caches of Google Play Service & Play Store
Go to Settings, Applications & select Google Play Service, delete data
Go to Settings, Appplications & select Play Store, delete data
Step 3 - Clear cache from Recovery​Reboot into Recovery and select wipe CACHE. Recovery boot to be activated from Settings/System/developpers options/advanced restart. Once in Recovery select WIPE & WIPE CACHE Only !
Step 4 - Safetynet Fix​Install Safetynet Fix Magisk Module
Phone Bricked ? :​Five options (ranked from the easiest to tougher method):
Option 1 - Reboot to Safe mode & remove Magisk modules​Option A : Safe Mode
1. Hold power until it goes off
2. Boot and wait for the bootloader warning
3. Hold vol up and down until boot animation
4. Once it's booted just reboot again and you're done
Now on boot all magisk modules are disabled
Option B : thru adb command
1. Code with phone connected with USB debugging on (from developpers options):
"adb wait-for-device shell magisk --remove-modules"
2. reboot
Option 2 - Get back the original boot.img​If your device can go to fastboot mode:
Flash back the original boot.img (w/o magisk) and reboot
Code once in fastboot mode:
"fastboot flash Original_boot.img" (use the "Original_boot.img" from the above zip file)
Change to the exact name "Original_boot.img" of the boot that has been posted in the above zip file
"fastboot reboot"
Option 3 - Flash back full OTA file​If you can still go to Settings:
Flash back the OTA RUU full package and reboot
Option 4 - Change the active slot​If your device can go to fastboot mode:
"fastboot getvar current-slot"
This will tell you what (corrupted) slot you are currently booting from (either a or b).
Then just change to the other slot with the following command:
"fastboot --set-active=a"
or
"fastboot --set-active=b"
Then reboot with the command:
"fastboot reboot"
Option 5 - Wipe data in Recovery mode or fastboot command​Option A : If your device can still go to Recovery mode (ie thru fastboot mode: "fastboot reboot recovery")
From Recovery Wipe data and reboot
Option B :
Code once in fastboot mode:
"fastboot- w"
Option 6 - MSM​If none of the above works then go for MSM tool
Option 1 to 4 would normally not alter your personal data, applications and own set-up
Option 5 & 6 will wipe your personal data and applications
Return your phone to unlock and unroot? :​​Option 1 : Original Boot & relock with fastboot command​Step 1 - Restore orignal boot.img​Option A : Thru Magisk App
Open Magisk App on your phone. You will see the Uninstall button in the app. Just click on Uninstall button.
Then you need to click on Complete Uninstall. Your phone will be rebooted automatically.
Option B : Thru fastboot mode
Flash back the original boot.img (w/o magisk) and reboot
Code once in fastboot mode:
"fastboot flash Original_boot.img" (use the "Original_boot.img" from the above zip file)
Change to the exact name "Original_boot.img" of the boot that has been posted in the above zip file
"fastboot reboot"
Once booted, remove Magisk application
Option C : Flash the current or latest full OTA zip twice. Why twice, to ensure both slot have the latest update flashed with original boot.
Step 2 - Relock the bootloader​1. Execute the following command to proceed for bootloader unlocking: "fastboot oem lock"
2. A verification window will appear on your mobile device asking to confirm the action. Just highlight “Relock Bootloader”using volume buttons and hit the power button to confirm.
3. The phone will initialize to relock the bootloader. It will take some time to reboot after resetting the whole phone into a locked stage.
4. Your device is now locked again !
Option 2 : MSM Tool ​MSM tool will relock your boaloader !​Option 1 & 2 will wipe your personal data and applications
Do any process described at your own risk. None Xda none the author are responsible for your own choice to unlock & root your Device.
Attachments​
OnePlus-8T-Rooting-fastboot-devices-command.jpg
15.9 KB · Views: 1,964
OnePlus-8T-Install-OTA-After-Rooting.jpg
62.9 KB · Views: 2,086

Decent.
Tbh though, looks like you just added pics to my one.
(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...
forum.xda-developers.com
Even the categories look the same.
FYI, there is no MSM tool for the 10

dladz said:
Decent.
Tbh though, looks like you just added pics to my one.
(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...
forum.xda-developers.com
Even the categories look the same.
FYI, there is no MSM tool for the 10
Click to expand...
Click to collapse
No MSM yet...

Steve0007 said:
No MSM yet...
Click to expand...
Click to collapse
No mate, fastboot enhance only, which has been hit and miss for most.
I haven't had to use it yet but seemingly it's the only option.
Hope things change but nothing yet

has old outdated info. If you flash, then you can't take ota updates.

Sorry, where is the magisk_boot.img file? I could not find it in this post.

Viewerisland said:
Sorry, where is the magisk_boot.img file? I could not find it in this post.
Click to expand...
Click to collapse
Please refer to this link. I personally used this approach with no issues
click me

use these steps to Unlock the bootloader... https://forum.xda-developers.com/t/root-oneplus-10-pro-color-os-oxygen-os.4401243/
after running through this post.. i would advise caution proceeding with the steps outlined ...
for OnePlus 10 Pro NE2213 & Ne 2215 ... you boot into Bootloader (adb reboot bootloader) and use ' fastboot flashing unlock ' to unlock the bootloader... NOT 'fastboot OEM unlock'
for my OnePlus 8T i would use 'fastboot oemunlock' ... not for the OnePlus10Pro

Steve0007 said:
Magisk VariantStable / Beta / CanaryReleaseOfficialAndroid / OOSOOS 11 and aboveMaintainertopjohnwuProject LinkGitHubZygiskNoDenyListNoMagiskHideYesModules RepoYesDownload LinkGitHub
This tutorial will :
provide you with all the steps to root your Oneplus 10 Pro (with your bootloader already unlocked)
provide you with all the steps to unlock your Oneplus 10 Pro bootloader
provide you with all the steps to keep root during/after an OTA (system update)
provide you with a lot tricks if you have troubleshooting questions
provide you with a lot of solutions of you have softbricked your Oneplus 10 Pro
provide you with all the ways if you want to bring back your Oneplus 10 Pro to unroot & lock back the bootloader
STEPS to root your device:
I recommand to update first your device with all OTA available using Settings/updates before unlocking & rooting it.
Root your Oneplus 10 Pro (with Bootloader already unlocked)​Step 1 - Booting temporarily root​1. Connect your phone to your pc and boot it into fastboot mode. You can leave it connected throughout this guide.
2. First, enter the following command in the PowerShell/Terminal window to ensure that your PC can communicate with the phone over the fastboot interface.
"fastboot devices"
The command should return your phone’s unique ID. In case it doesn’t, then make sure that you have the required USB drivers installed and restart your PC. You can also use TOOL ALL IN ONE, not officially updated to Oneplus 10 Pro but once install go to Others options and go to Install drivers.
3. Code once in fastboot mode:
"fastboot boot magisk_boot.img" (use the "magisk_boot.img" from the above zip file)
Change to the exact name "magisk_boot.img" of the boot that has been patched in the above zip file
"fastboot reboot"
You could flash this boot.img, but it's safer to temporarily boot from it without overwriting your existing image in case anything went wrong along the way. The effect is that you still get root access without modifying your device, and then you can use the much safer Magisk direct install option, which has some safeguards in place.
By booting with the patched image, you now have temporary root access. To make it permanent open Magisk app.
a. Select the Install option.
b. Use Direct Install (Recommended) to root your internal boot.img
Step 2 - Reboot and your device is now rooted !​Unlock the Bootloader and Root the OnePlus 10 Pro​Step 1 – Enable OEM unlocking​You need to enable OEM unlocking, which can be done by enabling the developer settings on your device. To do so, go to Settings > About phone and repeatedly tap Build number. Developer options will then be added to your system settings, where you can then enable OEM unlocking.
Step 2 – Unlock your phone
Set up adb, reboot into your bootloader, and run the following command. Yes, it’s really that simple!
"fastboot oem unlock"
You can reboot into the bootloader by switching on USB debugging, setting up adb and fastboot and typing “adb reboot bootloader”. Alternatively, you can hold volume down and the power button to boot up your device. USB debugging is also located under the developer options.
Unlocking the bootloader wipes your device :
Step 3 - Booting temporarily root​1. Connect your phone to your pc and boot it into fastboot mode. You can leave it connected throughout this guide.
2. First, enter the following command in the PowerShell/Terminal window to ensure that your PC can communicate with the phone over the fastboot interface.
"fastboot devices"
The command should return your phone’s unique ID. In case it doesn’t, then make sure that you have the required USB drivers installed and restart your PC. You can also use TOOL ALL IN ONE, not officially updated to Oneplus 10 Pro but once install go to Others options and go to Install drivers.
3. Code once in fastboot mode:
"fastboot boot magisk_boot.img" (use the "magisk_boot.img" from the above zip file)
Change to the exact name "magisk_boot.img" of the boot that has been patched in the above zip file
"fastboot reboot"
You could flash this boot.img, but it's safer to temporarily boot from it without overwriting your existing image in case anything went wrong along the way. The effect is that you still get root access without modifying your device, and then you can use the much safer Magisk direct install option, which has some safeguards in place.
Step 4 - Install magisk​Install the latest Magisk Canary apk on your phone. Open it and:
a. Select the Install option.
b. Use Direct Install (Recommended) to root your internal boot.img
Step 5 - Reboot and your device is now rooted !​Keep Root and OTA updates​How to update OTA and KEEP ROOT
It is advised to disable or even uninstall all magisk modules to be safe!
How: go to Magisk application/modules/disable &/or uninstall
Option 1: With full OTA Access (BA/DA) :
Step 1 - Get & install the full OTA zip file​1. Go to System-Update or update get the OTA using Oxygen Updater
2. Tap OK when the message that you are rooted appears
3. Tap "Download and install" or local update if OTA from Oxygen Updater
4. Wait until you are prompted to reboot - DO NOT REBOOT NOW!
5. Open Magisk Manager
a. Select the Install option.
b. Use Install to inactive slot
Step 2 - Reboot and enjoy your device still rooted with latest OTA installed !​​Option 2: with incremental OTA Access (AA) :​Step 1 - Get back your original boot image​1. open the Magisk Manager application, select “Uninstall”, and choose the “Restore Images” option. Magisk will restore your phone’s stock boot image that was backed up during the rooting process.
2. Now go to “Settings” → “System” → “System updates” and select “Download and Install Now” to install the OxygenOS OTA update on your rooted OnePlus 10 Pro
3. Open Magisk Manager
a. Select the Install option.
b. Use Install to inactive slot
Step 2 - Reboot and enjoy your device still rooted with latest OTA installed !​
Troubleshooting questions :​Before reporting any trouble, follow the steps below in order to have GooglePlay certified, keep L1 Widevine & pass CTS :
Step 1 - Magisk Settings​1. Once rooted, in Magisk setting, select MagiskHide and Systemless host
2. In MagiskHide select GMS, Netflix, Google Store & any application you may find sensitive to Magisk detection
For Netflix, go to Settings, Appplications & select Netflix:
a-force stop the app
b-clear cache and storage
c-hide the App in magisk
d-restart phone to recovery and clear cache
If you can't install/update Netflix install the latest Netflix from apkmirror manually (like any other apk file)
Hide everything under Google play services and store.:
3. Reboot
Step 2 - Clear caches​Clear caches of Google Play Service & Play Store
Go to Settings, Applications & select Google Play Service, delete data
Go to Settings, Appplications & select Play Store, delete data
Step 3 - Clear cache from Recovery​Reboot into Recovery and select wipe CACHE. Recovery boot to be activated from Settings/System/developpers options/advanced restart. Once in Recovery select WIPE & WIPE CACHE Only !
Step 4 - Safetynet Fix​Install Safetynet Fix Magisk Module
Phone Bricked ? :​Five options (ranked from the easiest to tougher method):
Option 1 - Reboot to Safe mode & remove Magisk modules​Option A : Safe Mode
1. Hold power until it goes off
2. Boot and wait for the bootloader warning
3. Hold vol up and down until boot animation
4. Once it's booted just reboot again and you're done
Now on boot all magisk modules are disabled
Option B : thru adb command
1. Code with phone connected with USB debugging on (from developpers options):
"adb wait-for-device shell magisk --remove-modules"
2. reboot
Option 2 - Get back the original boot.img​If your device can go to fastboot mode:
Flash back the original boot.img (w/o magisk) and reboot
Code once in fastboot mode:
"fastboot flash Original_boot.img" (use the "Original_boot.img" from the above zip file)
Change to the exact name "Original_boot.img" of the boot that has been posted in the above zip file
"fastboot reboot"
Option 3 - Flash back full OTA file​If you can still go to Settings:
Flash back the OTA RUU full package and reboot
Option 4 - Change the active slot​If your device can go to fastboot mode:
"fastboot getvar current-slot"
This will tell you what (corrupted) slot you are currently booting from (either a or b).
Then just change to the other slot with the following command:
"fastboot --set-active=a"
or
"fastboot --set-active=b"
Then reboot with the command:
"fastboot reboot"
Option 5 - Wipe data in Recovery mode or fastboot command​Option A : If your device can still go to Recovery mode (ie thru fastboot mode: "fastboot reboot recovery")
From Recovery Wipe data and reboot
Option B :
Code once in fastboot mode:
"fastboot- w"
Option 6 - MSM​If none of the above works then go for MSM tool
Option 1 to 4 would normally not alter your personal data, applications and own set-up
Option 5 & 6 will wipe your personal data and applications
Return your phone to unlock and unroot? :​​Option 1 : Original Boot & relock with fastboot command​Step 1 - Restore orignal boot.img​Option A : Thru Magisk App
Open Magisk App on your phone. You will see the Uninstall button in the app. Just click on Uninstall button.
Then you need to click on Complete Uninstall. Your phone will be rebooted automatically.
Option B : Thru fastboot mode
Flash back the original boot.img (w/o magisk) and reboot
Code once in fastboot mode:
"fastboot flash Original_boot.img" (use the "Original_boot.img" from the above zip file)
Change to the exact name "Original_boot.img" of the boot that has been posted in the above zip file
"fastboot reboot"
Once booted, remove Magisk application
Option C : Flash the current or latest full OTA zip twice. Why twice, to ensure both slot have the latest update flashed with original boot.
Step 2 - Relock the bootloader​1. Execute the following command to proceed for bootloader unlocking: "fastboot oem lock"
2. A verification window will appear on your mobile device asking to confirm the action. Just highlight “Relock Bootloader”using volume buttons and hit the power button to confirm.
3. The phone will initialize to relock the bootloader. It will take some time to reboot after resetting the whole phone into a locked stage.
4. Your device is now locked again !
Option 2 : MSM Tool ​MSM tool will relock your boaloader !​Option 1 & 2 will wipe your personal data and applications
Do any process described at your own risk. None Xda none the author are responsible for your own choice to unlock & root your Device.
Attachments​
OnePlus-8T-Rooting-fastboot-devices-command.jpg
15.9 KB · Views: 1,964
OnePlus-8T-Install-OTA-After-Rooting.jpg
62.9 KB · Views: 2,086
Click to expand...
Click to collapse
I have read all text, i cant see if this are only for PC or if i can use whit Mac computer.
Do you know somethinhg about that?

lordxcom said:
use these steps to Unlock the bootloader... https://forum.xda-developers.com/t/root-oneplus-10-pro-color-os-oxygen-os.4401243/
after running through this post.. i would advise caution proceeding with the steps outlined ...
for OnePlus 10 Pro NE2213 & Ne 2215 ... you boot into Bootloader (adb reboot bootloader) and use ' fastboot flashing unlock ' to unlock the bootloader... NOT 'fastboot OEM unlock'
for my OnePlus 8T i would use 'fastboot oemunlock' ... not for the OnePlus10Pro
Click to expand...
Click to collapse
It would be great if somehow this (and other) corrections (such as where is the ZIP file that is referenced but not linked) were added to the instructions above. I spent an hour trying to figure out why "fastboot oem unlock" didn't work.

okay, tried updating my phone w/the steps mentioned above w/o, unfortunately disabling my Magisk modules
ended up in Qualcomm Crashdump mode...
I was able to restore back to slot a w/the following command:
fastboot --set-active=a
then used fastboot mode to boot to the following boot image (from this thread: https://forum.xda-developers.com/t/ne2215_11_c22-update.4524469/)
fastboot boot NE2215-C.22_boot_magisk25.2.img
this got me back up & running but I'm still stuck on C21
My question is, how do i upgrade to C22 now w/o losing data/root?

How To Guide (Guide) Install TWRP + Root + Install Magisk + Bypass Safetynet

Please note, the TWRP image used IS NOT the official TWRP image.
I am not responsible for any any harm, such as bricking, or bootloops, which may happen to your device. This is what worked for me.
Warning
As stated by @beatbreakee , do not flash anything on a T-Mobile related device.
Please read beatbreakee's comment regarding this.
Warning
This has only been tested on Android 13. This guide may not work for other Android versions.
Prerequisites
Unlocked Bootloader
Magisk 25.2 Installation ZIP (see attached files)
TWRP Image (download from GDrive)
ADB and Fastboot tools are installed on your machine. Please see this guide
Android 13
Spoiler: Step 1 - Unlocking Bootloader
Step 1 - Unlocking Bootloader:
1.A - Enable OEM Unlocking:
1. Open Settings Application -> About device -> Version -> Tap on Build Number 7 times
2. Open Settings Application -> Additional Settings -> Developer Options
3. Enable OEM Unlocking
4. Enable USB Debugging
1.B - Entering Bootloader
The bootloader must be unlocked in order to flash the recovery.
Ensure the device is connected to the computer via ADB by entering the following command
Code:
adb devices
The output should be something similar to this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(note the device name on the left will not be the same)
Reboot into the bootloader by entering the following command:
Code:
adb reboot bootloader
1.C - Unlock
Once entered, enter the following command:
Code:
fastboot flashing unlock
WARNING: THIS WILL WIPE ALL DATA ON THE DEVICE
Use the volume keys to select unlocking, and then use the power button to confirm.
Once complete, enter the following command:
Code:
fastboot reboot
You will now have to go through the device setup.
Repeat steps 1.A and 1.B to enter back into the bootloader
Spoiler: Step 2 - Flashing TWRP
Step 2 - Flashing TWRP:
2.A - Entering Bootloader
Repeat steps 1.A and 1.B to re-enter the bootloader
2.B - Flashing TWRP:
Again, this IS NOT the official TWRP image. I am not responsible for any harm which this may cause to this device. That being said, it appears to be functional.
The image used is from a leak found on this XDA post
This is not a bootable image. You must flash. fastboot boot img will not work
Enter the following commands to flash the TWRP image:
Code:
fastboot flash recovery_a twrp.img
Code:
fastboot flash recovery_b twrp.img
Code:
fastboot reboot recovery
You should notice you are in TWRP.
You may need to change the language to English.
2.C - Changing TWRP Language:
1. Tap on the button on the Second column, Third Row
2. Tap on the World icon
3. Select your language
4. Tap on the button on the bottom right corner of your display.
2.D - Booting into your phone
1. Select Reboot
2. Select System
You should now have successfully booted in the system with TWRP installed as your recovery
Spoiler: Step 3 - Flashing Magisk
Step 3 - Flashing Magisk:
3.A Preparing the Device:
1. Move the Magisk-v25-2.zip to your device
2. Reboot into your recovery / TWRP
This can be done by entering the following ADB command:
Code:
adb reboot recovery
3.B - Flashing Magisk:
1. Tap Install
2. Select the Magisk-v25-2.zip
3. Swipe to flash (this may take some time)
4. Tap Reboot
5. Tap System
You should now enter the device
3.C - Installing Magisk APK
Install the Magisk APK, click here to download the APK.
Install the APK, and you should have root!
Spoiler: Fixing Data Backup [Optional]
If you encounter a createTarFork() exited with error 255, do the following:
1. Reboot into TWRP
2. Select File Manager
3. Navigate to /data
4. Copy /data/fonts into /sdcard/
5. Copy /data/nandswap into /sdcard/
6. Delete /data/fonts
7. Delete /data/nandswap
The error should now be resolved
The deleted files should not cause any issues. If any issues do occur, then promptly restore them using the backups made to /sdcard/.
Spoiler: Bypassing Safetynet [Optional]
Step - Bypassing Safetynet:
This is optional; however, highly recommend
Note, due to the nature of Safetynet, this can change at anytime and may begin failing in the future.
A - Repackaging Magisk
1. Launch Magisk Manager
2. Tap Settings Icon (Top Right Corner)
3. Tap "Hide The Magisk App"
4. Enter New Application Name
5. Click OK and wait
6. Uninstall original Magisk APK if it has persisted
B - Enable Zygisk & Deny List
1. Launch Magisk Manager
2. Tap Settings Icon (Top Right Corner)
3. Enable "Zygisk"
4. Enable "Enforce Deny List"
C - Configure Deny List
it is recommended to add any application you would like to hide from Magisk here
1. Launch Magisk Manager
2. Tap Settings Icon (Top Right Corner)
3. Tap "Configure DenyList"
4. Tap the 3 dots in the top right and select "Show System Apps"
5. Select the following applications:
~ Android System
~ Google Play Store
~ Google Play Services
~ Google Services Framework
D - Delete App Data
1. Launch Settings Application
2. Select Apps
3. Select App Management
4. Clear data for the following apps:
~ Google Play Store
~ Google Play Services
~ Google Services Framework
5. Reboot the device
E - Flash Universal Safetynet Fix
1. Download the Universal Safetynet Fix
2. Launch Magisk
3. Select Modules
4. Select "Install From Storage"
5. Select Universal Safetynet Fix
6. Wait for Flashing to complete
7. Reboot
F - Test Safetynet
1. Install YASNAC
2. Grant Super User rights
3. Select "Run Safetynet Attestation"
If both checks pass, you successfully have passed Safetynet!

PlasmaTornado said:
Please note, the TWRP image used IS NOT the official TWRP image.
I am not responsible for any any harm, such as bricking, or bootloops, which may happen to your device. This is what worked for me.
Prerequisites
Unlocked Bootloader
Magisk 25.2 Installation ZIP (see attached files)
TWRP Image (download from GDrive)
ADB and Fastboot tools are installed on your machine. Please see this guide
Step 1 - Unlocking Bootloader:
1.A - Enable OEM Unlocking:
1. Open Settings -> About -> Tap on Build Number 7 times
2. Open Developer Settings
3. Enable OEM Unlocking
4. Enable Android Debugging Bridge (ADB)
1.B - Entering Bootloader
The bootloader must be unlocked in order to flash the recovery.
Ensure the device is connected to the computer via ADB by entering the following command
Code:
adb devices
The output should be something similar to this:
View attachment 5792895
(note the device name on the left will not be the same)
Reboot into the bootloader by entering the following command:
Code:
adb reboot bootloader
1.C - Unlock
Once entered, enter the following command:
Code:
fastboot oem unlock
WARNING: THIS WILL WIPE ALL DATA ON THE DEVICE
Then finally:
Code:
fastboot reboot
You will now have to go through the device setup.
Repeat steps 1.A and 1.B to enter back into the bootloader
Step 2 - Flashing TWRP Image:
2.A - Entering Bootloader
Repeat steps 1.A and 1.B to re-enter the bootloader
2.B - Flashing TWRP:
Again, this IS NOT the official TWRP image. I am not responsible for any harm which this may cause to this device. That being said, it appears to be functional.
The image used is from a leak found on this XDA post
! It is HIGHLY recommended that you boot into the twrp.img before flashing to ensure that TWRPworks . I did not, but I recommend you do. !
To test this, enter the following command:
Code:
fastboot boot twrp.img
Enter the following commands to flash the TWRP image:
Code:
fastboot flash recovery_a twrp.image
Code:
fastboot flash recovery_b twrp.image
Code:
fastboot reboot recovery
You should notice you are in TWRP.
You may need to change the language to English.
2.C - Changing TWRP Language:
1. Tap on the button on the Second column, Third Row
2. Tap on the World icon
3. Select your language
4. Tap on the button on the bottom right corner of your display.
2.D - Booting into your phone
1. Select Reboot
2. Select System
You should now have successfully booted in the system with TWRP installed as your recovery
Step 3 - Flashing Magisk:
3.A Preparing the Device:
1. Move the Magisk-v25-2.zip to your device
2. Reboot into your recovery / TWRP
This can be done by entering the following ADB command:
Code:
adb reboot recovery
3.B - Flashing Magisk:
1. Tap Install
2. Select the Magisk-v25-2.zip
3. Swipe to flash (this may take some time)
4. Tap Reboot
You should now enter the device
3.C - Installing Magisk APK
If for some reason the Magisk Installer did not install the Magisk APK, click here to download the APK.
Install the APK, and you should have root!
Click to expand...
Click to collapse
Good post but one problem...to unlock is " fastboot flashing unlock"

Canuck Knarf said:
Good post but one problem...to unlock is " fastboot flashing unlock"
Click to expand...
Click to collapse
Of course! Thank you, used to the old way of unlocking

I wonder about any major issues with this TWRP as of now. Updating ZIP OOS13 with flashing magisk direclty is working etc.?

kouzelnik3 said:
I wonder about any major issues with this TWRP as of now. Updating ZIP OOS13 with flashing magisk direclty is working etc.?
Click to expand...
Click to collapse
Following the method created by @dladz should still work perfectly fine!
There could still be issues with this TWRP as this is not an official image.
AFAIK Switching ROM is still untested, but decryption, backups and flashing are all confirmed working, which for me makes me feel significantly more comfortable

I won't switch ROMs as there aren't any, so this is ok. I was just asking if installing official OOS updates can be done via twrp now with flashing magisk right after for example.
But I glad decryption, backups and flashing zips working fine now. This is great news!

kouzelnik3 said:
I won't switch ROMs as there aren't any, so this is ok. I was just asking if installing official OOS updates can be done via twrp now with flashing magisk right after for example.
But I glad decryption, backups and flashing zips working fine now. This is great news!
Click to expand...
Click to collapse
This has yet to be tested but I have high hopes! If anyone could confirm in the near future it would be fantastic!

PlasmaTornado said:
This has yet to be tested but I have high hopes! If anyone could confirm in the near future it would be fantastic!
Click to expand...
Click to collapse
I will try factory wipe...flash flash from 2213...to 2215...might work

Canuck Knarf said:
I will try factory wipe...flash flash from 2213...to 2215...might work
Click to expand...
Click to collapse
Fantastic news. Let us know the results!

i wouldnt advise ANYONE with an original TMOBILE device, ANY attempt to flash ANY firmware from the official builds just yet. Tmobile embedded a VERY WELL HIDDEN check into the EFS partition that only appeared in builds after 11_A.14 ... This check forcefully activates a lock triggered by the CarrierDevicePolicy.xml in the efs system... and if the Region and model does not match the original build that it came with, all of your apps will be completely disabled and there is nothing accessible but the settings button. It also disables ADB/USB debugging completely, and deauthorizes your computer from the adb wireless keys too... then it removes the USB DEBUGGING toggle from settings, followed by a persistent message that your phone is "Violating Contract Policy... Please contact after sales for support" ... Tmobile cannot remove this warning... and even them sending an UNLOCK request to your phone for APPROVED will get ignored by your phone. You can hear ringing, but cannot accept calls... hear emails but not open them,.. and you dialer is in emergency calls only!...
At this point you will think panic is the only option, but instead just Pull your sim card, and use your buttons to force reboot and enter recovery .... Then do a Format Data ,,,, followed by a reboot, but do not put your sim back in... Until you go thru the whole setup wizard, enable usb debugging, and then flash a rollback package to a fw earlier than the one i listed above, your phone will INSTANTLY lock again any time you insert ANY sim card.
Im very sure that there is a system process that can be disabled which will at least block the lockout.... but i dont have that knowledge as to which process(es) are calling it! A logcat generated about 15 screens on my computer as soon as i plugged a sim in... so that was too much for me to sift thru. This is present on both the 10 Pro and 10 T so be warned.... If you are already not using your original T-MO firmware, but you also have been loading other regions with no problem, that does not matter.... I have found an exact reference to the ORIGINAL FW build and Model # that was loaded by TMO at the factory level, in several different TXT and XML files inside the EFS part. AND my 10T and 10 Pro BOTH have been fully bricked, then formatted and flashed thru an authorized MSM Account.... Doing an ERASE ENTIRE FILE SYSTEM, thru msm, did not get rid of this file, so i doubt a twrp level wipe will do it either... MAYBE an "unlock Critical" in Fastboot, followed by a "Fastboot wipe", "DM-verity disable", and "VB-Meta erasure" MIGHT take out this crazy security system, but i know this .... if you flash an original FW using TWRP, it has protections in it to keep IT (twrp) from being overwritten, so you might find yourself in bootloop territory if you region hop.... cuz the fw might notice the changes to the partitions... For now, until someone is brave enough to challenge the Android 12 kernel and remove these trapdoors, I would just be happy you have TWRP, and wait for the person who finds and slays the Tmobile Dragon hidden in our phones! But this is truly an android 12 function that was put in place for Carrier and Manufacturer benefit ONLY. Another strike against 1+

beatbreakee said:
i wouldnt advise ANYONE with an original TMOBILE device, ANY attempt to flash ANY firmware from the official builds just yet. Tmobile embedded a VERY WELL HIDDEN check into the EFS partition that only appeared in builds after 11_A.14 ... This check forcefully activates a lock triggered by the CarrierDevicePolicy.xml in the efs system... and if the Region and model does not match the original build that it came with, all of your apps will be completely disabled and there is nothing accessible but the settings button. It also disables ADB/USB debugging completely, and deauthorizes your computer from the adb wireless keys too... then it removes the USB DEBUGGING toggle from settings, followed by a persistent message that your phone is "Violating Contract Policy... Please contact after sales for support" ... Tmobile cannot remove this warning... and even them sending an UNLOCK request to your phone for APPROVED will get ignored by your phone. You can hear ringing, but cannot accept calls... hear emails but not open them,.. and you dialer is in emergency calls only!...
At this point you will think panic is the only option, but instead just Pull your sim card, and use your buttons to force reboot and enter recovery .... Then do a Format Data ,,,, followed by a reboot, but do not put your sim back in... Until you go thru the whole setup wizard, enable usb debugging, and then flash a rollback package to a fw earlier than the one i listed above, your phone will INSTANTLY lock again any time you insert ANY sim card.
Im very sure that there is a system process that can be disabled which will at least block the lockout.... but i dont have that knowledge as to which process(es) are calling it! A logcat generated about 15 screens on my computer as soon as i plugged a sim in... so that was too much for me to sift thru. This is present on both the 10 Pro and 10 T so be warned.... If you are already not using your original T-MO firmware, but you also have been loading other regions with no problem, that does not matter.... I have found an exact reference to the ORIGINAL FW build and Model # that was loaded by TMO at the factory level, in several different TXT and XML files inside the EFS part. So this is truly an android 12 function that was put in place for Carrier benefit ONLY. Another strike against 1+
Click to expand...
Click to collapse
Absolutely despicable and such an anti-consumer technique.
This stands against everything OnePlus was. It's sad to see OnePlus turn into such an anti-developer phone
A Carrier should never have this much power over a device. It is absurd

heres a google drive link to my account if anyone wants to see a video of what you will go thru if triggered!
feel free to share or re-upload the link/video to anywhere... ppl need to know this is happening thanks to Tmobile and Oneplus collaboration. I have not seen any reference to another carrier inside any of the device policy files, and my phone was restored to a NON TMO branded build of android 12 for the 2217 NA model, so it should NOT have even recognized the TMO policies cuz i even used a new sim card after the MSM Unbrick, and it still instantly locked in less than a second of plugging it in... heres the vid
https://drive.google.com/file/d/17H6YpGrUCe1Y7PoFji4gperdpTHNX5AI/view?usp=sharing

also everyone should know, that EVERY fw on the internet no matter whether it is labeled, 2213, or 2215... 2217, as well as 2413-2419 ALL have EVERY other model's manifest built in and all of the restrictions / bloatware that each region comes with, saved into the OFP extracted files.... so there really is nothing that expressly was bricking your phones by simply flashing a different labeled FW..... the brick came from the manifest reading the region identifiers that the manifests are labeled under.... it is a file that is again picked by some random hidden check inside the TMO EFS, and as soon as your phone tries to boot the newly flashed FW, the TMO Lock is what bricks your phone, to either a bootloop state, or if you continue to force a flash by using Fastboot , you will have a non responsive phone, thanks to this stupid security issue. If unresponsive, the only way out is MSM Tool... and i can help you locate your test points if your buttons dont work.
I cannot publicly post a picture nor a description of where the test points lie inside the 10T , because i already got a cease and desist letter from BBK and i dont know if they have said anything to the mods here about posting Undisclosed hardware access points.... but ive been a member here almost 10 years, and i aint risking a ban from a tattle tale company! There are test points on the 10 t though,.. just well hidden!
The 2nd pic is of the 2217 Unpacked OFP , yet the build prop shows a 2210-2211 base in one and a 2413-2415 base in the.... with NO 2217 in either prop,or manifest file, yet when my phone was flashed back from Brick status, THIS is the FW that was used, and my phone identifies as a 2217 NA now..... can oneplus be any more clear that they have completely turned against us, by straight SHOWING US that they are being super cryptic and sneaky in something as common as the BUILD.PROP files?!?

The weird thing happened to me. I was doing "fastboot boot twrp.img" and adb gave me an error "Too many links" and the device only shows a OP logo for a half second, then turned off and then again repetatively.
Even if I turned off the device by holding power button + volume up + volume down, then turned on, same behavior happened.
Well, my fastboot was accessible so I did "fastboot boot boot.img" which worked and system booted up. But what happened, what might been wrong?

kouzelnik3 said:
The weird thing happened to me. I was doing "fastboot boot twrp.img" and adb gave me an error "Too many links" and the device only shows a OP logo for a half second, then turned off and then again repetatively.
Even if I turned off the device by holding power button + volume up + volume down, then turned on, same behavior happened.
Well, my fastboot was accessible so I did "fastboot boot boot.img" which worked and system booted up. But what happened, what might been wrong?
Click to expand...
Click to collapse
It could been...cause you might of had to many things open containing the same file...plus you might want to try the command ( fastboot flash recovery_a )....then ( fastboot flash recovery_b )

Canuck Knarf said:
It could been...cause you might of had to many things open containing the same file...plus you might want to try the command ( fastboot flash recovery_a )....then ( fastboot flash recovery_b )
Click to expand...
Click to collapse
Oh. I had opened like two or three folders containing that file, yes. But this can cause it? Wow. And I wanted to try to boot it first instead of flashing it.

kouzelnik3 said:
Oh. I had opened like two or three folders containing that file, yes. But this can cause it? Wow. And I wanted to try to boot it first instead of flashing it.
Click to expand...
Click to collapse
Yeah i hear you but I'm not sure if this a bootable version or a just install version....I will try it on mine to see if i get the same as you

Don't use command "fastboot boot twrp.img"....your phone will keep rebooting to op logo...but fastboot still works

Canuck Knarf said:
Don't use command "fastboot boot twrp.img"....your phone will keep rebooting to op logo...but fastboot still works
Click to expand...
Click to collapse
Yeah, I realised that, this happened to me. Thanks to fastboot I was able to boot into stock boot image, so nothign really happened, but hey. So if I dont want to flash it but only try it, what willl be the command? Fastboot boot recovery twrp.img?

kouzelnik3 said:
Yeah, I realised that, this happened to me. Thanks to fastboot I was able to boot into stock boot image, so nothign really happened, but hey. So if I dont want to flash it but only try it, what willl be the command? Fastboot boot recovery twrp.img?
Click to expand...
Click to collapse
It appears the image is not bootable. As stated, this is the one thing I didn't try.
I have amended the guide. Thank you