Database Info

How to Update to 7.1.1 on a Rooted, Unlocked Bootloader, Google Play Pixel?

I have a rooted, bootloader unlocked Pixel from Google Play. I am currently on 7.1 (NDE63V) November 5th security patch. I have stock recovery and would like to keep it that way if possible.
Can someone please provide step-by-step instructions on how to update to 7.1.1 without losing root or the unlocked bootloader? I used adb and boot-to-root for my current root method if it matters.
Many thanks in advance for any assistance. If a thread with the requested info already exists, please feel free to just post a link to it.

spook2022 said:
I have a rooted, bootloader unlocked Pixel from Google Play. I am currently on 7.1 (NDE63V) November 5th security patch. I have stock recovery and would like to keep it that way if possible.
Can someone please provide step-by-step instructions on how to update to 7.1.1 without losing root or the unlocked bootloader? I used adb and boot-to-root for my current root method if it matters.
Many thanks in advance for any assistance. If a thread with the requested info already exists, please feel free to just post a link to it.
Click to expand...
Click to collapse
You will lose root, but you can re-root easily enough. Bootloader doesn't relock on its own. Plus, you have the Google Store version, so it's easy to unlock BL anyway. To me, the cleanest and easiest method is to use the flash-all method, with the -w switch removed. Download the 7.1.1 image from the Google developers site and go at it. You can search for 'flash-all google pixel' here or on the web in general to get directions. It's easy as pie.

quangtran1 said:
You will lose root, but you can re-root easily enough. Bootloader doesn't relock on its own. Plus, you have the Google Store version, so it's easy to unlock BL anyway. To me, the cleanest and easiest method is to use the flash-all method, with the -w switch removed. Download the 7.1.1 image from the Google developers site and go at it. You can search for 'flash-all google pixel' here or on the web in general to get directions. It's easy as pie.
Click to expand...
Click to collapse
I've got an unlocked Verizon Pixel running the non Verizon stock ROM (I know the bootloader won't relock itself with the non-Verizon ROM, right?). what if you are using a computer that can't use the ./flash-all.sh script? My only 2 computers are a Chromebook (1GB RAM) and a Raspberry Pi 3 (again, 1GB RAM). The flash-all script always gives an error saying it can't allocate enough memory, and with my old Nexus 6P, before I started using Custom ROMs, I'd just extract the image zip and manually flash the .img files inside it. With the Pixel however, there are a lot of img files (aboot.img, apdp.img, etc) and I'm not sure if I should try flashing these or not. I've read a couple less than reliable guides out there that basically said to just flash the same .img files as the Nexus 6P used, but I feel that those other ones are probably their for a reason and might need to be flashed too.
Also, should I flash both _a and _b partitions when updating, or just whichever is active? Seems that there is an _a and _b for almost every single partition on it.

lightmastertech said:
I've got an unlocked Verizon Pixel running the non Verizon stock ROM (I know the bootloader won't relock itself with the non-Verizon ROM, right?). what if you are using a computer that can't use the ./flash-all.sh script? My only 2 computers are a Chromebook (1GB RAM) and a Raspberry Pi 3 (again, 1GB RAM). The flash-all script always gives an error saying it can't allocate enough memory, and with my old Nexus 6P, before I started using Custom ROMs, I'd just extract the image zip and manually flash the .img files inside it. With the Pixel however, there are a lot of img files (aboot.img, apdp.img, etc) and I'm not sure if I should try flashing these or not. I've read a couple less than reliable guides out there that basically said to just flash the same .img files as the Nexus 6P used, but I feel that those other ones are probably their for a reason and might need to be flashed too.
Also, should I flash both _a and _b partitions when updating, or just whichever is active? Seems that there is an _a and _b for almost every single partition on it.
Click to expand...
Click to collapse
I have a ChromeBook but I've never used it to fastboot my phones. Sorry but I'll refrain from giving instructions on something with which I'm not familiar. I can say that the bootloader won't relock by itself. And the boot.img image should be all you need. Those points are universal. Also, you can just flash the 7.1.1 OTA, which is only 260mb.

quangtran1 said:
I have a ChromeBook but I've never used it to fastboot my phones. Sorry but I'll refrain from giving instructions on something with which I'm not familiar. I can say that the bootloader won't relock by itself. And the boot.img image should be all you need. Those points are universal. Also, you can just flash the 7.1.1 OTA, which is only 260mb.
Click to expand...
Click to collapse
If it rooted, and has modified system, doesn't the OTA update method fail?
And I actually use the Raspberry Pi for fastboot. Easier than trying to get my Chromebook's chroot to talk to talk to my phone's bootloader.

Hi
Whats about Flashfire? Can i download the Factory Image, deselect Boot and Recovery in Flashfire and flash it?
After this, can i flash the the SuperSU.zip with TWRP?

spook2022 said:
<snip>
Many thanks in advance for any assistance. If a thread with the requested info already exists, please feel free to just post a link to it.
Click to expand...
Click to collapse
Have you any idea how many threads there are regarding this? How many duplicate posts and the same question about 2 dozen times all in separate threads? And now we have another? Even if you can't search XDA for some unknown reason, here you go.
https://www.google.com/search?q=root+on+unlocked+pixel+7.1.1&ie=utf-8&oe=utf-8
Search terms from your OP ... root. on unlocked pixel 7.1.1
Can we please put an end to this question already?

bobby janow said:
Have you any idea how many threads there are regarding this? How many duplicate posts and the same question about 2 dozen times all in separate threads? And now we have another? Even if you can't search XDA for some unknown reason, here you go.
Search terms from your OP ... root. on unlocked pixel 7.1.1
Can we please put an end to this question already?
Click to expand...
Click to collapse
I went back and read my post again just to make sure I wasn't crazy, and sure enough I couldn't find where I asked how to root 7.1.1...
I did however ask "Can someone please provide step-by-step instructions on how to update to 7.1.1 without losing root or the unlocked bootloader?" So, posting a Google search on how to root 7.1.1 isn't exactly the help I was after. Regardless of your disgruntled, condescending reply to the whole matter, I did manage to achieve the end result I was originally after.

spook2022 said:
I went back and read my post again just to make sure I wasn't crazy, and sure enough I couldn't find where I asked how to root 7.1.1...
I did however ask "Can someone please provide step-by-step instructions on how to update to 7.1.1 without losing root or the unlocked bootloader?" So, posting a Google search on how to root 7.1.1 isn't exactly the help I was after. Regardless of your disgruntled, condescending reply to the whole matter, I did manage to achieve the end result I was originally after.
Click to expand...
Click to collapse
As far as I know you can not update without losing root.. You can however update without losing data and reroot just like you did the first time.

@spook2022 It's just so frustrating to see the same question over and over. It wasn't that condescending, but yes, it was disgruntled. I just like to search for these things myself because I learn a lot along the way. Might take me an hour or so for the answer but then I learned an hours worth of stuff. I do agree though that there should be a sticky like the Heisenberg thread in the n5x forum that gives step by step for everything. One thing I will say that perhaps a few people don't know is that the Pixel and the XL are basically the same regarding root, unlocking and updating. So if you don't find the answers here you might want to head over to that forum. There seems to be a dearth of information here.
Someone suggested that the forums be combined with separate sections for things specific to each device like battery life and display as well as Verizon vs Google brand differences. I originally thought not but I'm changing my mind. Nonetheless, take the frustration from whence it came. I'm sorry I insulted you, that was not my intention. If you found a link to your solution perhaps you can post it for others. There is bound to be a similar question within a day. (oh oh there I go again..)
edit: This is what I was talking about regarding the Pixel vs the XL forums. Anything by Chainfire regarding root is a must read if you are rooted and even if you are not as I am. http://forum.xda-developers.com/pixel-xl/development/root-supersu-t3490156

Download the 7.1.1 NMF260 image from Google.
Extract the zip file into the adb folder on the PC.
Edit the flash-all.bat file to remove the -w switch so user data won't be deleted. You'll find this -w switch easily enough.
Put your Pixel into fastboot mode, using either power+volume down or via adb command.
Plug phone to PC if not already done so. Execute the flash-all batch file.
When that's done, you have 7.1.1 on your phone, along with new radio and new kernel. (actually, I'm not sure if Google even put out a new kernel.)
Then you can go back to re-root with whatever method you used previously.

Konfuzion said:
Download the 7.1.1 NMF260 image from Google.
<snip>
Click to expand...
Click to collapse
Why not the OTA coming from 7.1? Stock recovery according to the OP. Why go thru all the hassle unless you want a dirty flash? I know you say reroot after the install. I haven't been rooted in a few months now but I always used to unroot first for some reason before flashing a new image whether it be full image as you describe or an OTA. I'm sure it's not needed at this point, I was always leery of a bootloop. But with an unlocked bl it probably wouldn't matter since you could always recover if needed.

Konfuzion said:
Download the 7.1.1 NMF260 image from Google.
Extract the zip file into the adb folder on the PC.
Edit the flash-all.bat file to remove the -w switch so user data won't be deleted. You'll find this -w switch easily enough.
Put your Pixel into fastboot mode, using either power+volume down or via adb command.
Plug phone to PC if not already done so. Execute the flash-all batch file.
When that's done, you have 7.1.1 on your phone, along with new radio and new kernel. (actually, I'm not sure if Google even put out a new kernel.)
Then you can go back to re-root with whatever method you used previously.
Click to expand...
Click to collapse
Thank you so much.

bobby janow said:
...I was always leery of a bootloop. But with an unlocked bl it probably wouldn't matter since you could always recover if needed.
Click to expand...
Click to collapse
That right there is why I always unlock my bootloader's and hack Verizon's phones to have unlocked bootloaders. Always great to have the assurance that you can easily fix it if something ever breaks.
Sorry if that's a little off topic.

bobby janow said:
Why not the OTA coming from 7.1? Stock recovery according to the OP. Why go thru all the hassle unless you want a dirty flash? I know you say reroot after the install. I haven't been rooted in a few months now but I always used to unroot first for some reason before flashing a new image whether it be full image as you describe or an OTA. I'm sure it's not needed at this point, I was always leery of a bootloop. But with an unlocked bl it probably wouldn't matter since you could always recover if needed.
Click to expand...
Click to collapse
He's on 7.1.0...63V..he can't apply the latest ota to 63V..he would have to apply each ota in order of their release.

kyle4269 said:
He's on 7.1.0...63V..he can't apply the latest ota to 63V..he would have to apply each ota in order of their release.
Click to expand...
Click to collapse
I don't believe that to be correct. I think the 7.1.1 is cumulative. I'll double check though and edit later.
edit: You can go directly to the latest without incremental OTA flashes. Just sideload the OTA from recovery. Easy, peasy.
---------- Post added at 03:50 PM ---------- Previous post was at 03:22 PM ----------
lightmastertech said:
That right there is why I always unlock my bootloader's and hack Verizon's phones to have unlocked bootloaders. Always great to have the assurance that you can easily fix it if something ever breaks.
Sorry if that's a little off topic.
Click to expand...
Click to collapse
I always, always unlocked first thing I did. I even unlocked the unlockable S4 before the VZW firmware update. But lately I've been running locked. I have a banking app that will not run without passing SafetyNet. I know there are a couple of kernels that will bypass that check but I believe they will close that too eventually. The only thing I miss at this point is what you describe above. But the Pixel even from vzw, which I now have with the O update and therefore totally locked for now, is not full of bloat and runs rather well. So although I do root around these threads (no pun intended) it's merely for entertainment now and general knowledge.

bobby janow said:
I don't believe that to be correct. I think the 7.1.1 is cumulative. I'll double check though and edit later.
edit: You can go directly to the latest without incremental OTA flashes. Just sideload the OTA from recovery. Easy, peasy.
.
Click to expand...
Click to collapse
That makes it so much easier then.. Download the latest ota zip from https://developers.google.com/android/ota then you need to flash the 63V boot. Reboot to recovery. Follow the directions on the Google ota site to sideload the ota. Reboot back to Bootloader and flash the twrp boot image to boot.. Reboot to recovery. Install the supersu zip and reboot.. All rooted and to the latest build.

bobby janow said:
I always, always unlocked first thing I did. I even unlocked the unlockable S4 before the VZW firmware update. But lately I've been running locked. I have a banking app that will not run without passing SafetyNet. I know there are a couple of kernels that will bypass that check but I believe they will close that too eventually. The only thing I miss at this point is what you describe above. But the Pixel even from vzw, which I now have with the O update and therefore totally locked for now, is not full of bloat and runs rather well. So although I do root around these threads (no pun intended) it's merely for entertainment now and general knowledge.
Click to expand...
Click to collapse
Luckily I'm with USAA and they are too slow with adopting new technology, just got chip debit cards 2 months ago, and they'd till don't have Android Pay, lol. If they did start using SafetyNet, I'd use the kernel patch in a heartbeat. It'll be a long time before Google fixes that since there's still a lot of devices that can't use verified boot, and Google doesn't want to become the new Apple, abandoning old device just to suit them.
Wife got the Verizon version of the Pixel as an early Xmas present from my parents, and I wouldn't let the Verizon sales person activate it for fear of getting 7.1.1 before I could unlock bootloader. Wouldn't let wife turn it on for a couple hours till I had the bootloader unlocked and had flashed Google's version of Android to keep Verizon from screwing with it. Viper4Android and all the awesome rooted featured are too good to give up. She'll be really happy when Xposed or custom ROMs start coming out for it cuz even the little features are great, like holding power button with screen off to turn on flashlight. (She's been stuck with locked phones for a while while I've had my Nexus 6P and is glad to finally get a rootable phone).

kyle4269 said:
That makes it so much easier then.. Download the latest ota zip from https://developers.google.com/android/ota then you need to flash the 63V boot. Reboot to recovery. Follow the directions on the Google ota site to sideload the ota. Reboot back to Bootloader and flash the twrp boot image to boot.. Reboot to recovery. Install the supersu zip and reboot.. All rooted and to the latest build.
Click to expand...
Click to collapse
Yep, that's about it. Personally I'd reboot right after the OTA flash then go back to bl and do the root process. Probably not needed though.
Sent from my Pixel using XDA-Developers mobile app

kyle4269 said:
That makes it so much easier then.. Download the latest ota zip from https://developers.google.com/android/ota then you need to flash the 63V boot. Reboot to recovery. Follow the directions on the Google ota site to sideload the ota. Reboot back to Bootloader and flash the twrp boot image to boot.. Reboot to recovery. Install the supersu zip and reboot.. All rooted and to the latest build.
Click to expand...
Click to collapse
How is that better or different than flashing the full image by using fastboot to flash bootloader and radio (if updated), then using
Code:
fastboot update <image>.zip
and leave off the -w to keep it from wiping.
Also, correct me if I'm wrong, but doesn't OTA updates fail if you've modified the system partition, like installing Viper4Android or other mods? I know that flashing the whole system image works no matter what which is why I use that method.

Magisk for dummies

Hi all,
I tried to find basic informations about Magisk without success.
Is anyone here could explain what is Magisk, as if I was 5 years old ?
Thanks in advance for your replies.

dont know if you saw this , but here is the thread for magisk. maybe will help. :what:
http://forum.xda-developers.com/showthread.php?t=3473445

mrrocketdog said:
dont know if you saw this , but here is the thread for magisk. maybe will help. :what:
http://forum.xda-developers.com/showthread.php?t=3473445
Click to expand...
Click to collapse
Thanks for your reply.
The thread for Magisk is too technical for me. In a first approach, I want only to understand with simple words, what Magisk can do.

root your device.

iwanttoknow said:
Thanks for your reply.
The thread for Magisk is too technical for me. In a first approach, I want only to understand with simple words, what Magisk can do.
Click to expand...
Click to collapse
I'm with you - that main thread completely lost me - I installed the manager and it errored from twrp and I guess it leads on to something about finding a boot.img to patch - but i'm lost

Lothaen said:
I'm with you - that main thread completely lost me - I installed the manager and it errored from twrp and I guess it leads on to something about finding a boot.img to patch - but i'm lost
Click to expand...
Click to collapse
@iwanttoknow
have you seen this one
https://www.xda-developers.com/what-is-magisk/
&
https://www.xda-developers.com/magisk-hub-2/

IronRoo said:
@iwanttoknow
have you seen this one
https://www.xda-developers.com/what-is-magisk/
&
https://www.xda-developers.com/magisk-hub-2/
Click to expand...
Click to collapse
yeah - i've been through both of those, but mine error during the flash with issue with the boot image, so then I get stuck and have no idea how to fix it or where to go - I tried asking on the Magisk thread but its so chatty I think it got lost very quickly.

IronRoo said:
@iwanttoknow
have you seen this one
https://www.xda-developers.com/what-is-magisk/
&
https://www.xda-developers.com/magisk-hub-2/
Click to expand...
Click to collapse
Thanks a lot IronRoo for your reply !
After reading I have understood that Magisk implies to install a recovery tool like TRWP.
So I have only to unlock the device's bootloader to install a recovery tool and after Magisk. Magisk doesn’t modify system files.
Ok but I don't understand how it's possible the device obtains root access. It's certainly magical

Most of the time I don't look for the sort of 'tell me like I'm a 5 y/o' info - but Magisk IS an exception for that, for me.
There is very little that I can find which is written in plain, simple words such that I can even figure out -IF- it is usable as I'd like it to be.
My example:
I have an unlocked Moto E6 - can I even get TWRP installed & working in that phone ??
No clue.
Prior to Android V5.x gaining root access was loads easier to accomplish & I've happily done so for my several older LG devices & our previously daily use Kyocera phones.
BUT:
For my couple of devices with versions of Android newer than V5 - I am only able to de-bloat those somewhat via ADB shell - but they are locked to AT&T which would mean I'd have to fulfill their unlocking requirements to get 'em unlocked - or am I mistaken about that ??
The closest I've found to a VERY simplified guide to using Magisk is here:
Root Android Phone with ADB Command, Magisk & TWRP
Here are 2 different methods to root your Android phone or tablet using ADB and Fastboot commands, Magisk and install TWRP Recovery.
technastic.com
But method 1 is not possible for my devices AFAIK & method 2 requires me to have a stock firmware IMG to patch...but I've zero idea where I might get those for a Moto or a 'modern' LG phone - is there any particularly good way to accomplish that ??
So - as the OP said - please tell me like I'm a 5 year old ?!?
Thanks.

OnePlus 7P Root w/o Magisk/TWRP

Hi,
I'm quite new to rooting. I've jailbroken many iPhones but it's been much easier than rooting Android.
Either way, I have an app to connect my PS3 controller to my OP7pro. This app requires the phone to be rooted. I'm wondering if I have to do everything in the tutorials or just something simple like unlocking the bootloader. I'm also curious if after the root I will be able to install the backup from my pc and keep the root. I do not need nor want Magisk or TWRP at the moment, I will install it at some point.
What do I need to do to make a root-critical app work as simply as possible?

is very simple to root just follow one of the multiples guides in this forum, if you have a T-mobile variant you need to sim unlock first then convert it to intl.
it all sounds complicated but is very easy

piotrekkrzewi said:
Hi,
I'm quite new to rooting. I've jailbroken many iPhones but it's been much easier than rooting Android.
Either way, I have an app to connect my PS3 controller to my OP7pro. This app requires the phone to be rooted. I'm wondering if I have to do everything in the tutorials or just something simple like unlocking the bootloader. I'm also curious if after the root I will be able to install the backup from my pc and keep the root. I do not need nor want Magisk or TWRP at the moment, I will install it at some point.
What do I need to do to make a root-critical app work as simply as possible?
Click to expand...
Click to collapse
If you NEED root then at the moment you NEED magisk
Unlock bootloader first for you need to and it'll wipe all your data...
Twrp is not necessary however it makes things easier such as backing up, flashing from recovery, etc.

HtcOnekid said:
is very simple to root just follow one of the multiples guides in this forum, if you have a T-mobile variant you need to sim unlock first then convert it to intl.
it all sounds complicated but is very easy
Click to expand...
Click to collapse
Aight, but will I be able to restore my backup and keep the root?

What's this app you are using to use your ps3/4 controller?

No point in trying to avoid Magisk. I reckon the same applies to TWRP as well. They're extremely simple to install. Connect your phone to a PC, reboot to bootloader/fastboot mode, then run
fastboot boot TWRP.img (either rename the twrp image or change the filename the command refers to), then in the temporary twrp you flash 2 zip files (twrp installer + Magisk). Done. Rooted with twrp and magisk (After you unlock your bootloader, of course).
Trying to root without Magisk or TWRP will not only be more difficult, but also likely cause you issues (such as no Google Pay).

Magisk is your best XDA friend! Cheers

equlizer said:
What's this app you are using to use your ps3/4 controller?
Click to expand...
Click to collapse
Sixaxis controller is the app

I'd like to thank you all for clarifying the topic. It seems like a really nice forum. But what I need to know is will I be able to restore my OnePlus Switch backup from the app and will i keep the root? The last thing I want is to reinstall all the apps.

Why would you need root to use a bluetooth device?

djsubterrain said:
Why would you need root to use a bluetooth device?
Click to expand...
Click to collapse
You can not pair a ps3 controller with the phone and just make it work. It need some sort of a driver, and this app is one. But for some reason it needs root to show the local bluetooth adress and connect.

piotrekkrzewi said:
I'm wondering if I have to do everything in the tutorials or just something simple like unlocking the bootloader.
Click to expand...
Click to collapse
Unlocked bootloader is just an unlocked bootloader. It is not root.
As other have touched upon, Magisk is the root method for this device. I'm not aware of any other root method. Only different variations on flashing Magisk. It's awesome, works great, reliable, and well supported by the developer. So I see no reason to avoid it. Yes, Magisk has some features you may not need. But you can simply opt not to use them. My opinion, it still is a lightweight and unbloated root solution.
You can root using Magisk, without TWRP. But you need to flash a patched boot image (and the correct one for your OOS version, or you will have problems). So you would really be making the process harder for no good reason. And in my opinion, having a modded device (root) without a custom recovery (TWRP) is not a good idea. It is called "recovery" for a reason, as it allows you a lot of options to recover the device if things go wrong. Much more so than the stock recovery (which is nearly useless, really only good for installing stock OTA updates on stock devices).
I don't personally use Oneplus Switch backup app. But I don't see any reason why it would not work once rooted. If you downloaded the apps from the Google Play store, they should just automatically reinstall anyway (after root, and starting up the phone again)?
In any case, losing data (having to setup the phone again, etc.) is always a possibility when unlocking the bootloader and rooting these devices. If you choose to mod the phone, it's just a possibility we all live with.

what are the interesting things I can do after rooting my op6?

After leaving Samsung, I did not root my phone as never felt the need for it, as I used root for battery mods and roms.
So can anyone tell me that what interesting mods I can do after rooting my phone?

You can install custom ROMs which have extended features for your phone like changing what buttons do, having an always on display show different things, have shortcuts mapped etc. Custom kernels can manage your phone better whether you like more battery or more performance. Then you have magisk modules come in that can add further functionality and then Edxposed, F-droid the list goes on and on.

You can get rid of ads in your apps.
You can have modded youtube without any ads and other stuff.
Tons of stuff

i root because a few mods:
Viper4android
Call Recorder - not available in my country.
EdXposed with gravitybox - for little customizing
Youtube Vanced
i also root because i had oneplus 5 before which was not rooted and one day i messed up and couldnt get it to work again. i really tried everything - if i was rooted i probably could have fixed my op5.

How do you install new updates then?

Once the updates are out you can install them directly with your phone as you have been doing with any other phone.
The only thing is that after every update you have to root again your phone as the update 'delete' the root.
Nothing major, don't worry. Trust me, us, once you root you won't be able to have your phone unrooted anymore ?
If you are in doubt I suggest you to root it once and then, after a new update you can decide if root it again or not ?

If ur not willing to walk the mile of getting knowledge, dont root

You can use it to teleport to another dimension.
Jk jokes aside you have full control of your system and can do all kinds of modification which how you modify will make it awesome or perform worse.

@bibop80 @chintu1234 @whizeguy
I have rooted my phones for years when I used Samsung devices.
Samsung had issues with battery and performance so that time I had rooted my device.
But since I am using op6 I am so satisfied with the performance and battery, that's why I never rooted my device.
Now I am bored and want to try few mods, so I will root my phone.
I have never used magisk root method, and as I said it's been almost 2 years I rooted device, so I'll be happy if someone can guide me in detail and best root method, I am currently on latest fw android 10.
Thanks in advance!

I do agree with you about Samsung, that is why I passed to oneplus few years ago, the only thing I do miss is the camera quality.
A part of that, you'll be happy to have your phone rooted (Magisk is amazing!)
I suggest you the section of this forum GUIDES, NEWS AND DISCUSSION; once there you'll find the guide titled "OnePlus 6: Unlock Bootloader | Flash TWRP | Root | Nandroid & EFS Backup !!"
It looks more difficult than with Samsung but it isn't at all!
Good luck man and welcome to the Dark side

bebop80 said:
I do agree with you about Samsung, that is why I passed to oneplus few years ago, the only thing I do miss is the camera quality.
A part of that, you'll be happy to have your phone rooted (Magisk is amazing!)
I suggest you the section of this forum GUIDES, NEWS AND DISCUSSION; once there you'll find the guide titled "OnePlus 6: Unlock Bootloader | Flash TWRP | Root | Nandroid & EFS Backup !!"
It looks more difficult than with Samsung but it isn't at all!
Good luck man and welcome to the Dark side
Click to expand...
Click to collapse
Thanks for the info, I checked the forum.
Kindly help me to understand few things -
Do I need to install Twrp tp install Magisk?
Will I lose any apps like snapchat?

You can root your phone also without installing the twrp (if you are not intended to deep mod your phone). I'd suggest anyway to install the twrp.
Yes, magisk is needed it can be compared as the supersu but with extended feautures.
If I don't mistake (I did unlock my bootloader on my 1st day I owned the oneplus) all data will be wiped and yes... You might loose your data.
If you can make a backup of your photos, videos and any extra file on a PC and after the unlock and root procedure you can restore them.
All other app can just be downloaded again.... ???

for people mentioning about adfree & background youtube, this can be done in a virgin phone also. just install the vanced apk.

JerryGoyal said:
for people mentioning about adfree & background youtube, this can be done in a virgin phone also. just install the vanced apk.
Click to expand...
Click to collapse
I am already using YouTube vanced, it's great.

bebop80 said:
You can root your phone also without installing the twrp (if you are not intended to deep mod your phone). I'd suggest anyway to install the twrp.
Yes, magisk is needed it can be compared as the supersu but with extended feautures.
If I don't mistake (I did unlock my bootloader on my 1st day I owned the oneplus) all data will be wiped and yes... You might loose your data.
If you can make a backup of your photos, videos and any extra file on a PC and after the unlock and root procedure you can restore them.
All other app can just be downloaded again.... ???
Click to expand...
Click to collapse
I guess I'll be doing this on next weekend. I'll post query if I have any doubts. Thanks!

I find that making phone calls with this device seem to be the thing that most people do

bebop80 said:
You can root your phone also without installing the twrp (if you are not intended to deep mod your phone). I'd suggest anyway to install the twrp.
Yes, magisk is needed it can be compared as the supersu but with extended feautures.
If I don't mistake (I did unlock my bootloader on my 1st day I owned the oneplus) all data will be wiped and yes... You might loose your data.
If you can make a backup of your photos, videos and any extra file on a PC and after the unlock and root procedure you can restore them.
All other app can just be downloaded again.... ???
Click to expand...
Click to collapse
I am unable to flash twrp from adb,i ve unlocked the bootloader.any help?

nvrmndryo said:
I am unable to flash twrp from adb,i ve unlocked the bootloader.any help?
Click to expand...
Click to collapse
Follow this guide
h***s://www.xda-developers.com/how-to-install-twrp/
Double check all the adb instructions before confirming them and check that you have all the right files necessary for the operation. (start your pc terminal as administrator)

bebop80 said:
Follow this guide
h***s://www.xda-developers.com/how-to-install-twrp/
Double check all the adb instructions before confirming them and check that you have all the right files necessary for the operation. (start your pc terminal as administrator)
Click to expand...
Click to collapse
Thanks. successfully rooted my phone.

Relocking Bootloader

Could someone help me? I'm currently rooted on OOS, with TWRP and a custom kernel installed. I'd like to unroot and go back to fully stock (in light of the recent development of SafetyNet and CTS; see TopJohnWu's tweets, cause I am by no means an expert, but he makes it clear this is the end of rooting permanently now). I need help on how to do it without bricking my device, and also a method of transferring as much of my current data as possible (obviously Titanium/Swift Backup is out of the question cause I won't have root access). Thank you very much in advance!

pratzyushd said:
Could someone help me? I'm currently rooted on OOS, with TWRP and a custom kernel installed. I'd like to unroot and go back to fully stock (in light of the recent development of SafetyNet and CTS; see TopJohnWu's tweets, cause I am by no means an expert, but he makes it clear this is the end of rooting permanently now). I need help on how to do it without bricking my device, and also a method of transferring as much of my current data as possible (obviously Titanium/Swift Backup is out of the question cause I won't have root access). Thank you very much in advance!
Click to expand...
Click to collapse
I think you con relock the bootloader/unroot with the msm tool. Dont hold me to that I may be wrong
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
This would be a good place to start.

I have done this many times, firstly, install the lastest version using the full package from OP page, this will get rid of the TWRP for you, then restart in fastboot, in fastboot, run "fastboot oem lock" (or would be relock?), confirm in your mobile, reboot, reinstall the last full package and be happy.
Something like it, I don´t remember exactly, but this is the idea.
Tks and good luck!