Database Users

{Guide} How to Root ONEPLUS 3T (Unlock bootloader, TWRP Recovery, SuperSu)

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.
1. Download the ADB For Windows from here :-
https://drive.google.com/file/d/0B0MKgCbUM0itNVB1elljU2NPR0k/view
2. TWRP: https://mega.nz/#!v9MmGQ5C!i5VroRopCVz2_Uoc6Mi2U6N4oDa0HK1SxCrkDrc4mwQ
3. SuperSu: https://mega.nz/#!eh13yLiC!3tkx_RkLg-D8T6mi35zDUB8AYEPLliBsL8yO1dmZbI8
Steps:
1.Backup Data
2.Unlock boot loader
3.Flash Recovery
4.Flash SuperSU
ENJOY
Video:
https://youtu.be/wwd31NU7VC0
Rooting OOS 4.0.3 ONEPLUS 3T
https://youtu.be/0QYp5tkBaao

Thanks for the nice guide!
What would be the clean method to flash future OOS update when rooted and with TWRP recovery?

Midomad said:
Thanks for the nice guide!
What would be the clean method to flash future OOS update when rooted and with TWRP recovery?
Click to expand...
Click to collapse
Simply flash the full ROM.zip manually in recovery, typically 1.4GB.
That means not installing the incremental mini zips. And not installing from the settings menu.
It's up to you whether you want to wipe data or cache.

Midomad said:
Thanks for the nice guide!
What would be the clean method to flash future OOS update when rooted and with TWRP recovery?
Click to expand...
Click to collapse
Download complete zip file n flash using two.

Thanks for nice guide, Just one question so dm verity error would never bother me with this method as I would like to be remain encrypted for some time being.

uttam.ace said:
Thanks for nice guide, Just one question so dm verity error would never bother me with this method as I would like to be remain encrypted for some time being.
Click to expand...
Click to collapse
yes if u follow the steps you wont have DM verity issuse.

uttam.ace said:
Thanks for nice guide, Just one question so dm verity error would never bother me with this method as I would like to be remain encrypted for some time being.
Click to expand...
Click to collapse
Dm verity zip is not needed when you flash SuperSu.

*winces* Ooh, all the files on file hosts? Why not just link to the legit sites?

Very easy to download the required files. Very simple step-by-step video guide. A+
Thanks for putting this together you made my night!

Thanks, I have unlocked bootloader, Installed TWRP, and Super Su.
one question though, when after setting my account going for nandroid backup there I found SYSTEM as well SYSTEM IMAGE.
what is difference between them, What thing should I backup.
Also there is showing your system is Unmounted, so when I should have to mount it.
Thanks to all Once again.

Hello guys, thanks for the guide!
I was wondering if anyone has faced the same problem as me - while trying to root the Oneplus 3T I constantly get a bootloop after flashing SuperSU. The latest TWRP (3.0.4.0) is installed without any problems in fastboot, the system is mounted as r/w, and I don't see any problems during flashing SuperSU package...
I've tried it before and after OOS 4.0.2, I've tried old and new, stable and beta versions of SuperSU, but either way the phone is stuck on bootscreen after flashing.
P. S. If I flash the official ROM after that - it boots up instantly without any errors... And with no root :/

I'm having the same problem

respectableafrican said:
I'm having the same problem
Click to expand...
Click to collapse
So nice to know I'm not alone!
Did you find a way to root your phone?

Try this SuperSU

I heard only SuperSU SR3 works

Just tried both versions (2.79 and the SR3 beta) - unfortunately, the same bootloop happens.

I flash twrp 3.0.4 then flashed RR N rom but twrp is not booting to system it boot again to twrp please help

nishant.roy24 said:
I flash twrp 3.0.4 then flashed RR N rom but twrp is not booting to system it boot again to twrp please help
Click to expand...
Click to collapse
Power off and boot instead of selecting reboot from twrp

hrsa said:
So nice to know I'm not alone!
Did you find a way to root your phone?
Click to expand...
Click to collapse
Oh yeah actually I did, just use the systemless root guide on r/oneplus (cant link because im new)

respectableafrican said:
Oh yeah actually I did, just use the systemless root guide on r/oneplus (cant link because im new)
Click to expand...
Click to collapse
Oh, finally - thank you so much!
Followed the guide on reddit page, and got the Magisk root, with Android Pay compatibility!
I wonder why it was so hard to find

Magisk on Oreo

I can't seem to install Magisk 16.0 via TWRP 3.2 on the Oreo update. It installs, but enters a bootloop. Why is that?
Also TWRP said cannot mount /data. How to fix this?
"Failed to mount '/data' (No such process)"
Also cannot format data this way
EDIT: Installed Magisk 16.4, no change. Also just realized that internal storage is inaccessible.

I upgraded and got in a bootloop. Then I remembered I had Nougat substratum themes active. Only way I got it booting is by factory resetting it.
As for installing magisk with root access, you can try the TWRPless method. I got it working on mine. All you need is the stock boot image and a computer to use adb.
Steps on installing magisk on Oreo:
1. Put the boot image somewhere you can easily find it for later use
2. Install the latest magisk manager apk on your phone
3. Enter magisk manager and install magisk (root) using the "patch boot image" method.
4. Send the patched boot image to your computer
5. Now reboot into bootloader
6. Now on your computer install the patched boot image using fastboot flash boot "patched boot image"
7. Reboot and profit!
Hope this helped you out. Good luck

+)KEV1N(+ said:
I upgraded and got in a bootloop. Then I remembered I had Nougat substratum themes active. Only way I got it booting is by factory resetting it.
As for installing magisk with root access, you can try the TWRPless method. I got it working on mine. All you need is the stock boot image and a computer to use adb.
Steps on installing magisk on Oreo:
1. Put the boot image somewhere you can easily find it for later use
2. Install the latest magisk manager apk on your phone
3. Enter magisk manager and install magisk (root) using the "patch boot image" method.
4. Send the patched boot image to your computer
5. Now reboot into bootloader
6. Now on your computer install the patched boot image using fastboot flash boot "patched boot image"
7. Reboot and profit!
Hope this helped you out. Good luck
Click to expand...
Click to collapse
For anyone who tries the above method and has their fingerprint sensor stop working as I did, use a root file manager to remove the following directory/file:
/data/system/users/0/fpdata
/data/system/users/0/settings_fingerprint.xml
and reboot.
Certain modules required me to delete those files again, and some others broke the fingerprint functionality until they were removed and I rebooted twice. I hope someone can find a complete workaround soon.

+)KEV1N(+ said:
I upgraded and got in a bootloop. Then I remembered I had Nougat substratum themes active. Only way I got it booting is by factory resetting it.
As for installing magisk with root access, you can try the TWRPless method. I got it working on mine. All you need is the stock boot image and a computer to use adb.
Steps on installing magisk on Oreo:
1. Put the boot image somewhere you can easily find it for later use
2. Install the latest magisk manager apk on your phone
3. Enter magisk manager and install magisk (root) using the "patch boot image" method.
4. Send the patched boot image to your computer
5. Now reboot into bootloader
6. Now on your computer install the patched boot image using fastboot flash boot "patched boot image"
7. Reboot and profit!
Hope this helped you out. Good luck
Click to expand...
Click to collapse
Already tried. Bootloop also, probably since magisk manager used v 16.0 instead 16.4.
I noticed that 16.4 actually signed the boot image using test keys, as opposed to the 16.0 which didn't.
I'm a bit frustrated here man
EDIT: I have substratum but I don't have any of the themes active, so the first one is a go. Installing magisk however...

GBry said:
Already tried. Bootloop also, probably since magisk manager used v 16.0 instead 16.4.
I noticed that 16.4 actually signed the boot image using test keys, as opposed to the 16.0 which didn't.
I'm a bit frustrated here man
EDIT: I have substratum but I don't have any of the themes active, so the first one is a go. Installing magisk however...
Click to expand...
Click to collapse
So, now you're stuck in a bootloop?
Also, yes I used version 16.0 (you can never go wrong with a stable release)
---------- Post added at 03:17 PM ---------- Previous post was at 03:16 PM ----------
kekley said:
For anyone who tries the above method and has their fingerprint sensor stop working as I did, use a root file manager to remove the following directory/file:
/data/system/users/0/fpdata
/data/system/users/0/settings_fingerprint.xml
and reboot.
Certain modules required me to delete those files again, and some others broke the fingerprint functionality until they were removed and I rebooted twice. I hope someone can find a complete workaround soon.
Click to expand...
Click to collapse
Did you try wiping your cache?

+)KEV1N(+ said:
So, now you're stuck in a bootloop?
Also, yes I used version 16.0 (you can never go wrong with a stable release)
---------- Post added at 03:17 PM ---------- Previous post was at 03:16 PM ----------
Did you try wiping your cache?
Click to expand...
Click to collapse
Technically, I'm not now, since I flashed the original boot.img
But yes, if I installed magisk either via the patched boot.img or TWRP, I get a bootloop
Actually idk if bootloop or nah since I can't access logcat via adb, but it's on the bootlogo for like 5 mins (regular start time is 30-ish sec)

+)KEV1N(+ said:
Did you try wiping your cache?
Click to expand...
Click to collapse
That was the first thing I tried, in fact. I have to use magisk 16.4 as well or else the fingerprint reader refuses to work no matter what. You haven't run into this issue at all? What's your setup if I might ask, and did you patch the boot image from the oreo update zip to install magisk?

kekley said:
That was the first thing I tried, in fact. I have to use magisk 16.4 as well or else the fingerprint reader refuses to work no matter what. You haven't run into this issue at all? What's your setup if I might ask, and did you patch the boot image from the oreo update zip to install magisk?
Click to expand...
Click to collapse
I just watched a video tutorial to root it and keep stock recovery. Another thing to take note of is that I upgraded to Oreo using TWRP instead of stock recovery (yes, I didn't think it was possible on this phone).
Once I upgraded to Oreo, it reverted back to stock recovery. As you read above, I got stuck in a bootloop because I had substratum themes active, but I fixed it by using the stock recovery to factory reset it. (It's also nice to factory reset after a major OS upgrade so that you don't encounter any problems with old files)
If anyone's interested in a video, here's the one I watched:
Note: always make backups of your personal data!!!

+)KEV1N(+ said:
I just watched a video tutorial to root it and keep stock recovery. Another thing to take note of is that I upgraded to Oreo using TWRP instead of stock recovery (yes, I didn't think it was possible on this phone).
Once I upgraded to Oreo, it reverted back to stock recovery. As you read above, I got stuck in a bootloop because I had substratum themes active, but I fixed it by using the stock recovery to factory reset it. (It's also nice to factory reset after a major OS upgrade so that you don't encounter any problems with old files)
If anyone's interested in a video, here's the one I watched:
Note: always make backups of your personal data!!!
Click to expand...
Click to collapse
So you did a factory reset and magisk is working properly? I can boot twrp without installing, but still no go using that method. Yes, I also used TWRP to install oreo, I didn't think it was possible either, but it finished flawlessly. Except the magisk thingy.
Can you mount /data in TWRP after oreo?

GBry said:
So you did a factory reset and magisk is working properly? I can boot twrp without installing, but still no go using that method. Yes, I also used TWRP to install oreo, I didn't think it was possible either, but it finished flawlessly. Except the magisk thingy.
Can you mount /data in TWRP after oreo?
Click to expand...
Click to collapse
To answer your first question: yes, I did the basic setups, restored my apps and then installed magisk the way I explained above.
Secondly, did you try installing the latest TWRP? Because I didn't want to install TWRP until I have the stock recovery and TWRP with the latest Oreo kernels.
I saw this morning that shakalaca uploaded TWRP with the latest kernel, so I boot it through fastboot and saw that by default the following partitions were mounted: /recovery, /data, /cache. I tried /system to see if it works and it does.
I hope this answers your question and good luck!

+)KEV1N(+ said:
To answer your first question: yes, I did the basic setups, restored my apps and then installed magisk the way I explained above.
Secondly, did you try installing the latest TWRP? Because I didn't want to install TWRP until I have the stock recovery and TWRP with the latest Oreo kernels.
I saw this morning that shakalaca uploaded TWRP with the latest kernel, so I boot it through fastboot and saw that by default the following partitions were mounted: /recovery, /data, /cache. I tried /system to see if it works and it does.
I hope this answers your question and good luck!
Click to expand...
Click to collapse
How did you manage to update via twrp? I get an error when I try it.

kekley said:
How did you manage to update via twrp? I get an error when I try it.
Click to expand...
Click to collapse
I don't know man. I was just running the latest release of TWRP at the time and it somehow installed it like any custom rom.

+)KEV1N(+ said:
To answer your first question: yes, I did the basic setups, restored my apps and then installed magisk the way I explained above.
Secondly, did you try installing the latest TWRP? Because I didn't want to install TWRP until I have the stock recovery and TWRP with the latest Oreo kernels.
I saw this morning that shakalaca uploaded TWRP with the latest kernel, so I boot it through fastboot and saw that by default the following partitions were mounted: /recovery, /data, /cache. I tried /system to see if it works and it does.
I hope this answers your question and good luck!
Click to expand...
Click to collapse
Wow, that's great! Can you give me the link? I can't seem to find the one for 553kl...
EDIT: apparently it's this one, isn't it?
https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Also tried live-booting TWRP and installing magisk (leaving stock recovery), left the boot.img unpatched
Installed the latest TWRP, the /data and internal got mounted, but after flashing magisk, bootloop again (still bootlogo after 10 minutes) even after wiping dalvik.
Cache is unwipeable somehow, is this an issue?

GBry said:
Wow, that's great! Can you give me the link? I can't seem to find the one for 553kl...
Click to expand...
Click to collapse
So, I just realized I've been sending the wrong link to everyone so far. (It sent you to the "old" folder)
Here's an updated link: https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w

+)KEV1N(+ said:
So, I just realized I've been sending the wrong link to everyone so far. (It sent you to the "old" folder)
Here's an updated link: https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Click to expand...
Click to collapse
Yes, I searched through my history and then found out that you gave me the same link, so thank you. Updated my 2nd to last post about the condition... Do I REALLY have to factory reset? Sigh...

+)KEV1N(+ said:
So, I just realized I've been sending the wrong link to everyone so far. (It sent you to the "old" folder)
Here's an updated link: https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Click to expand...
Click to collapse
+)KEV1N(+ said:
I don't know man. I was just running the latest release of TWRP at the time and it somehow installed it like any custom rom.
Click to expand...
Click to collapse
kekley said:
How did you manage to update via twrp? I get an error when I try it.
Click to expand...
Click to collapse
Yes, actually I just did update via TWRP, it installs flawlessly. HOWEVER, it only applies to the Oreo ROM, not the N or M ROMs. N and M needs stock recovery (the boot.img contains recovery too)

I was able to reflash the update via twrp by modifying the update script a bit (spat out errors about the twrp recovery having a more recent build date than the update zip) Everything seems so far so good! I haven't had issues with my fingerprint yet.

kekley said:
I was able to reflash the update via twrp by modifying the update script a bit (spat out errors about the twrp recovery having a more recent build date than the update zip) Everything seems so far so good! I haven't had issues with my fingerprint yet.
Click to expand...
Click to collapse
Did you install Magisk though?

GBry said:
Wow, that's great! Can you give me the link? I can't seem to find the one for 553kl...
EDIT: apparently it's this one, isn't it?
https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Also tried live-booting TWRP and installing magisk (leaving stock recovery), left the boot.img unpatched
Installed the latest TWRP, the /data and internal got mounted, but after flashing magisk, bootloop again (still bootlogo after 10 minutes) even after wiping dalvik.
Cache is unwipeable somehow, is this an issue?
Click to expand...
Click to collapse
Did you try clearing it with the stock recovery?

GBry said:
Did you install Magisk though?
Click to expand...
Click to collapse
With the latest twrp, yes! :good:

sideload installation keeps failing.

I'm trying to revert my oneplus 5 back to stock. I done all the steps got stock recovery installed. When I attempt to sideload original oos through adb sideload it keeps failing at 46%. Any advice would be very appreciated.. I've read so much and tried so many different things. I am completely stuck.

TENlll423 said:
I'm trying to revert my oneplus 5 back to stock. I done all the steps got stock recovery installed. When I attempt to sideload original oos through adb sideload it keeps failing at 46%. Any advice would be very appreciated.. I've read so much and tried so many different things. I am completely stuck.
Click to expand...
Click to collapse
Which rom do you want to flash and from which rom are you coming? Maybe there are some updates between you're missing...

strongst said:
Which rom do you want to flash and from which rom are you coming? Maybe there are some updates between you're missing...
Click to expand...
Click to collapse
I got the phone from a friend and it has been completely wiped and formatted through TWRP. He did have a nougat custom ROM on it prior to that.
I tried to sideload to it with TWRP and it wouldn't work. I followed directions from a website that explains how to revert your op5 back to stock using stock recovery. I was trying to put the original oxygen OS ROM on it that came with the phone using the stock recovery and adb and fastboot. I'm thinking maybe I possibly downloaded the wrong OOS version. Who knows. Lol .
It had nougat Pure FusionOS 7.1.2. encrypted...SuperSU root and TWRP blue spark.
Now all it has is stock recovery with No OS
Would like to get OOS pie on it eventually.

TENlll423 said:
I got the phone from a friend and it has been completely wiped and formatted through TWRP. He did have a nougat custom ROM on it prior to that.
I tried to sideload to it with TWRP and it wouldn't work. I followed directions from a website that explains how to revert your op5 back to stock using stock recovery. I was trying to put the original oxygen OS ROM on it that came with the phone using the stock recovery and adb and fastboot. I'm thinking maybe I possibly downloaded the wrong OOS version. Who knows. Lol .
It had nougat Pure FusionOS 7.1.2. encrypted...SuperSU root and TWRP blue spark.
Now all it has is stock recovery with No OS
Would like to get OOS pie on it eventually.
Click to expand...
Click to collapse
Do you want to have root along with your new rom? And which rom do you want?

strongst said:
Do you want to have root along with your new rom? And which rom do you want?
Click to expand...
Click to collapse
New OOS 5.1 7. With Magisk v18 would be great.

TENlll423 said:
New OOS 5.1 7. With Magisk v18 would be great.
Click to expand...
Click to collapse
You need to flash 5.1.4 at first to create the vendor partition like described here https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003 then you can flash 5.1.7. If that fails you need to flash 5.1.5 and 5.1.6 after 5.1.4 and before 5.1.7. You'll find older versions here
https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-mirrors-official-oxygen-os-t3628190
Also you need an actual(latest codeworkx for example) twrp recovery https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723
Please report back

strongst said:
You need to flash 5.1.4 at first to create the vendor partition like described here https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003 then you can flash 5.1.7. If that fails you need to flash 5.1.5 and 5.1.6 after 5.1.4 and before 5.1.7. You'll find older versions here
https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-mirrors-official-oxygen-os-t3628190
Also you need an actual(latest codeworkx for example) twrp recovery https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723
Please report back
Click to expand...
Click to collapse
Thank you... can I do all that by installing TWRP with fastboot and then sideload 5.1.4?

TENlll423 said:
Thank you... can I do all that by installing TWRP with fastboot and then sideload 5.1.4?
Click to expand...
Click to collapse
There's no need of sideload anything when you flashed twrp through fastboot. Just copy the roms on the device and flash through twrp

strongst said:
There's no need of sideload anything when you flashed twrp through fastboot. Just copy the roms on the device and flash through twrp
Click to expand...
Click to collapse
Ok I'll give it a try thanks. And merry Christmas

strongst said:
There's no need of sideload anything when you flashed twrp through fastboot. Just copy the roms on the device and flash through twrp
Click to expand...
Click to collapse
How can I transfer 5.1.4 to phone from pc? My phone is completely wiped. Computer won t recognize phone in PC file explorer? Also, Will I have to fastboot flash recovery twrp img to get new twrp to work? Sorry for all the questions.

strongst said:
There's no need of sideload anything when you flashed twrp through fastboot. Just copy the roms on the device and flash through twrp
Click to expand...
Click to collapse
Keep getting failed to mount/system/ invalid argument in thwrp. Can't transfer rom from pc. Its showing up in PC file explorer but won't transfer

strongst said:
You need to flash 5.1.4 at first to create the vendor partition like described here https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003 then you can flash 5.1.7. If that fails you need to flash 5.1.5 and 5.1.6 after 5.1.4 and before 5.1.7. You'll find older versions here
https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-mirrors-official-oxygen-os-t3628190
Also you need an actual(latest codeworkx for example) twrp recovery https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723
Please report back
Click to expand...
Click to collapse
Can't copy anything to phone. says there's no system and I even tried sideloading rom and said it corrupt
I think it's done. It's beyond me.. I've read so much trying to get this thing fixed I can't even see straight.. lol

It lets me copy small files over like magisk v18. It works. When I attempt to copy 5.1.4 rpm over it says device stopped not responding. Crazy

TENlll423 said:
It lets me copy small files over like magisk v18. It works. When I attempt to copy 5.1.4 rpm over it says device stopped not responding. Crazy
Click to expand...
Click to collapse
You need to mount internal storage, not system. Is your twrp updated to latest codeworkx?

I'm redownloading 5.1.4
I tried to copy over another ROM I had and it started to copy over so it is the file that was corrupted.
Thanks again I really appreciate it ?

strongst said:
You need to mount internal storage, not system. Is your twrp updated to latest codeworkx?
Click to expand...
Click to collapse
Second to latest... I have
TWRP-3.2.3-0-20181031-codeworkx installed.
Latest one wouldn't boot.

It won't install no vendor to mount or something. I'm done... Thanks for everything anyway.

When I reboot to recovery. This what it says.

TENlll423 said:
Second to latest... I have
TWRP-3.2.3-0-20181031-codeworkx installed.
Latest one wouldn't boot.
Click to expand...
Click to collapse
I'm using twrp-3.2.3-0-20181031-codeworkx-cheeseburger.img
You have the same? The vendor partition will be created with 5.1.4.
You can go(in twrp) to mount - > vendor. But the recovery should mount it automatically when it's created by flashing 5.1.4.

strongst said:
I'm using twrp-3.2.3-0-20181031-codeworkx-cheeseburger.img
You have the same? The vendor partition will be created with 5.1.4.
You can go(in twrp) to mount - > vendor. But the recovery should mount it automatically when it's created by flashing 5.1.4.
Click to expand...
Click to collapse
Yeah that's the same one I'm using I'm thinking maybe I don't have TWRP setup right is there any settings I'm supposed to go into?
Even when I check off everything in advanced wipe and do a wipe it comes up fine all the way to the end and then it says failed to mount vendor (invalid argument)
I liked everything again in TWRP I went to flash 514 and it works all the way up to the end and fails to mount vendor invalid argument.
Somehow I need to activate the vendor partition or something.
well I'm going back to reading like a madman and figure out if anybody else had this problem online. Lol thanks

6t mclaren getting back to full stock, please help

quick question,
I am the owner of a Oneplus 6t Mclaren, I installed twrp and magisk to root my device, but at the moment I would like to return to stock, i mean full stock. I thought uninstalling magisk through the itself would be enough to remove root but its not. whenever I try to update i receive a notification saying that my bootloader is unlocked.
What happens if I update my oneplus 6t mclaren, magisk is already uninstalled, I only have twrp bluespark something on my device. Please let me know

abati said:
quick question,
I am the owner of a Oneplus 6t Mclaren, I installed twrp and magisk to root my device, but at the moment I would like to return to stock, i mean full stock. I thought uninstalling magisk through the itself would be enough to remove root but its not. whenever I try to update i receive a notification saying that my bootloader is unlocked.
What happens if I update my oneplus 6t mclaren, magisk is already uninstalled, I only have twrp bluespark something on my device. Please let me know
Click to expand...
Click to collapse
To update a rooted device, you need the full OTA.
You then choose the local update option.

tech_head said:
To update a rooted device, you need the full OTA.
You then choose the local update option.
Click to expand...
Click to collapse
can you ellaborate a bit, my goal is to get rid of root fully, i want to make the phone original.

abati said:
can you ellaborate a bit, my goal is to get rid of root fully, i want to make the phone original.
Click to expand...
Click to collapse
If you are not on the current OS (9.0.11) then download the fullOTA and install it locally from the update menu.
Typically just having your BL unlocked will not prevent an OTA.
TWRP, Magisk will cause the normal OTA to fail.
If you download the full OTA (normally about 1.75GB) and install locally, it will remove TWRP and Magisk and take you back to stock.
A full OTA installed from the system menu will install the factory kernel, system and vendor.
On thing you will want to do is install the OTA, reboot then install the OTA again.
This makes sure that both A & B partitions are flashed.

tech_head said:
If you are not on the current OS (9.0.11) then download the fullOTA and install it locally from the update menu.
Typically just having your BL unlocked will not prevent an OTA.
TWRP, Magisk will cause the normal OTA to fail.
If you download the full OTA (normally about 1.75GB) and install locally, it will remove TWRP and Magisk and take you back to stock.
A full OTA installed from the system menu will install the factory kernel, system and vendor.
On thing you will want to do is install the OTA, reboot then install the OTA again.
This makes sure that both A & B partitions are flashed.
Click to expand...
Click to collapse
I am on oxygen os 9.0.9, after checking update, it says download complete, install now, but i need to skip the part were it says install now right ? if yes where can I find the ota it downloaded ?

abati said:
I am on oxygen os 9.0.9, after checking update, it says download complete, install now, but i need to skip the part were it says install now right ? if yes where can I find the ota it downloaded ?
Click to expand...
Click to collapse
I just found out something, if look on my device for the ota folder there is nothing to be found in the root directory of the device, but when I connect the mclaren to the pc, I can see a folder called .Ota , in that folder there is zip file about 1.62gb that should be the full ota I believe, but on the original oneplus filemanager the .Ota folder is not visible, also on es file manager it is not visible. Could this be the cause of uninstalling magisk ? cuz I uninstalled magisk.

abati said:
I just found out something, if look on my device for the ota folder there is nothing to be found in the root directory of the device, but when I connect the mclaren to the pc, I can see a folder called .Ota , in that folder there is zip file about 1.62gb that should be the full ota I believe, but on the original oneplus filemanager the .Ota folder is not visible, also on es file manager it is not visible. Could this be the cause of uninstalling magisk ? cuz I uninstalled magisk.
Click to expand...
Click to collapse
Download the OTA from here:
https://forum.xda-developers.com/oneplus-6t/how-to/official-oxygenos-9-0-4-ota-oneplus-6t-t3860953
Post #2.
Follow the instructions in Post #3

tech_head said:
Download the OTA from here:
https://forum.xda-developers.com/oneplus-6t/how-to/official-oxygenos-9-0-4-ota-oneplus-6t-t3860953
Post #2.
Follow the instructions in Post #3
Click to expand...
Click to collapse
i will try that thanks

tech_head said:
Download the OTA from here:
https://forum.xda-developers.com/oneplus-6t/how-to/official-oxygenos-9-0-4-ota-oneplus-6t-t3860953
Post #2.
Follow the instructions in Post #3
Click to expand...
Click to collapse
just a simple question that ota frimware from the link you send me, it should not bring harm to the mclaren when I flash it right ? I mean If I flash it, the device will keep its original mclaren theme right?

Only one version of the 9.0.11 firmware as far as I know. Has everything.

tech_head said:
Only one version of the 9.0.11 firmware as far as I know. Has everything.
Click to expand...
Click to collapse
it worked thnx for al the info !

abati said:
it worked thnx for al the info !
Click to expand...
Click to collapse
No problem.

tech_head said:
Only one version of the 9.0.11 firmware as far as I know. Has everything.
Click to expand...
Click to collapse
It Does, just flashed it on my 1+ 6T Mc all is good

Is it safe to flash a OTA a couple versions above yours?

Got a quick question. I'm on OOS 9.0.11 currently with bootloader unlocked, TWRP installed, and rooted with Magisk. I know how to flash correctly and keep root and recovery after. Is it safe for me to install the 9.0.17 OTA without flashing 12-16? Any issues that could arise from me not flashing the other OTAs first?

I jumped several versions without issue. As long as you are using the complete file (the ~1.8 GB) file you should be fine. You'll have issues if you use the incremental file (obviously).

OhioYJ said:
I jumped several versions without issue. As long as you are using the complete file (the ~1.8 GB) file you should be fine. You'll have issues if you use the incremental file (obviously).
Click to expand...
Click to collapse
Thanks. And just to be sure I flash the update, then the TWRP installer, reboot to recovery, and then flash Magisk correct? After that I'm good to go?

DREWHAMM974 said:
Thanks. And just to be sure I flash the update, then the TWRP installer, reboot to recovery, and then flash Magisk correct? After that I'm good to go?
Click to expand...
Click to collapse
That is correct. There is a new feature in TWRP that is supposed to eliminate the reflash, but I haven't tried that yet, I've just been flashing the installer, and rebooting to recovery, then flashing the rest.

OhioYJ said:
That is correct. There is a new feature in TWRP that is supposed to eliminate the reflash, but I haven't tried that yet, I've just been flashing the installer, and rebooting to recovery, then flashing the rest.
Click to expand...
Click to collapse
I appreciate your help. I've been doing this stuff since the HTC Dream but with the way Android and smartphones in general change they're always more to learn