Develop Bugs

Anyone having trouble installing TWRP on build NBD90W?

Greetings!
After installing the October security updates (bringing my device to NBD90W) I decided to unlock my bootloader and install TWRP. However, I can't seem to get TWRP to "stick" - flashing seems fine, and rebooting into bootloader and into TWRP recovery all proceeds fine. However, as soon as I reboot my system, TWRP seems to disappear and the stock recovery reappears.
Am I doing something wrong here? This is the exact process I followed on my Nexus 7, without any problems.

jerethi said:
Greetings!
After installing the October security updates (bringing my device to NBD90W) I decided to unlock my bootloader and install TWRP. However, I can't seem to get TWRP to "stick" - flashing seems fine, and rebooting into bootloader and into TWRP recovery all proceeds fine. However, as soon as I reboot my system, TWRP seems to disappear and the stock recovery reappears.
Am I doing something wrong here? This is the exact process I followed on my Nexus 7, without any problems.
Click to expand...
Click to collapse
You should be able to run twrp-2.8.7 without any problems. I believe if you want one higher you might need to format data (decrypt is what I do).
Also, here is what instructions on TWRP say to make it stick.
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.

Tulsadiver said:
You should be able to run twrp-2.8.7 without any problems. I believe if you want one higher you might need to format data (decrypt is what I do).
Also, here is what instructions on TWRP say to make it stick.
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
Click to expand...
Click to collapse
Thanks for your response. I am following the directions on TWRP's website, so it must be another issue.
I will try the version you suggest to see if that works. Why would I need to format data to install a later version?

jerethi said:
Thanks for your response. I am following the directions on TWRP's website, so it must be another issue.
I will try the version you suggest to see if that works. Why would I need to format data to install a later version?
Click to expand...
Click to collapse
I believe it requires you to be decrypted. Formatting userdata will wipe your data so make a backup first.
http://forum.xda-developers.com/nexus-5x/general/guide-how-to-install-custom-recovery-t3231143

jerethi said:
Greetings!
After installing the October security updates (bringing my device to NBD90W) I decided to unlock my bootloader and install TWRP. However, I can't seem to get TWRP to "stick" - flashing seems fine, and rebooting into bootloader and into TWRP recovery all proceeds fine. However, as soon as I reboot my system, TWRP seems to disappear and the stock recovery reappears.
Am I doing something wrong here? This is the exact process I followed on my Nexus 7, without any problems.
Click to expand...
Click to collapse
Flash TWRP from bootloader.
While within bootloader use vol down to select recovery and press power to boot into recovery.
Install SuperSU.
TWRP will stick.
If you boot with stock recovery even once, TWRP will get replaced.

sfhub said:
Flash TWRP from bootloader.
While within bootloader use vol down to select recovery and press power to boot into recovery.
Install SuperSU.
TWRP will stick.
If you boot with stock recovery even once, TWRP will get replaced.
Click to expand...
Click to collapse
Thank you. What is the difference between rooting and using the method that TulsaDiver suggests above?

Tulsadiver said:
I believe it requires you to be decrypted. Formatting userdata will wipe your data so make a backup first.
http://forum.xda-developers.com/nexus-5x/general/guide-how-to-install-custom-recovery-t3231143
Click to expand...
Click to collapse
So, just to clarify, I can either flash a modified boot.img (as described in the post you linked) or I could simply flash an older version of TWRP?
Thanks again for your assistance!

jerethi said:
So, just to clarify, I can either flash a modified boot.img (as described in the post you linked) or I could simply flash an older version of TWRP?
Click to expand...
Click to collapse
If you are using NBD90W I suggest you use the unofficial TWRP 3.0.2-3 that was posted a few pages back from the last post on the TWRP thread.
TWRP 3.0.2-0 won't decrypt Android N (will decrypt MM)
TWRP 3.0.2-1 has a major EFS bug that will brick your phone on restore
TWRP 3.0.2-2 has that EFS problem fixed, but has another problem where larger parttitions don't get backed up correctly.
TWRP 3.0.2-3 has both previous problems fixed.
---------- Post added at 10:19 AM ---------- Previous post was at 10:16 AM ----------
jerethi said:
Thank you. What is the difference between rooting and using the method that TulsaDiver suggests above?
Click to expand...
Click to collapse
I didn't read the whole post but decrypted user partition isn't directly related to why your TWRP is disappearing.
When you boot with a stock image, it will replace your recovery with stock.
If there is just 1 byte change with your boot.img, it won't do that.
Installing SuperSU will patch your boot.img, thus it will no longer replace your recovery with stock.
You could flash a modified boot.img instead of SuperSU, but then you are depending on someone else creating a modified boot.img for you (or you creating it yourself). If your goal is to have root installed, then SuperSU will patch boot.img on the fly during install so no need for extra step.
Again, the overwriting of TWRP with stock recovery is not directly related to the modifications done to boot.img either by someone else or by SuperSU install. If you had done any change to boot.img even if it is off by 1 byte, TWRP won't be replaced by stock recovery.
IMO there is no reason to run decrypted with latest OS, but if you wanted to, the only requirement is you have dm-verity disabled in the boot.img. Both the custom boot.img and the SuperSU install would do this for you.
After you have dm-verity disabled (either by SuperSU install or installing custom boot.img), boot back into bootloader and do
fastboot format userdata
From that point on, as long as you *never* boot using stock boot.img your userdata will remain decrypted. If you ever boot with stock boot.img, by mistake, it will proceed to encrypt your userdata. Then you'd have to go through the same procedure again the decrypt (losing your userdata in the format step)
The proper way to upgrade is to flash boot.img, system.img, vendor.img in fastboot, then immediately (from bootloader menu) boot into TWRP recovery, and install SuperSU. Then everything will be preserved.

jerethi said:
So, just to clarify, I can either flash a modified boot.img (as described in the post you linked) or I could simply flash an older version of TWRP?
Thanks again for your assistance!
Click to expand...
Click to collapse
Listen to this guy. You can start with the old one if you want then upgrade to the new one later but Supersu modifies your boot.img for you. Like he said, after Fastboot flashing them, Fastboot reboot and before your phone boots up, boot right back into recovery. This will make TWRP stick.

Wow, this post was SO HELPFUL.... Haven't rooted in a while, recently replaced our Nexus 5's with 5x's (on NBD90W) and hadn't felt the need to root. Plus it's gotten so much trickier even with Nexuses.
Anyway totally familiar with ADB/fastboot etc to flash stuff.
I still need to oem unlock and wipe still (bleh).
But after, one thing that's confusing me, to then root is a *custom* kernel (boot.img) needed now? Made specifically for (at this point in time) NBD90W? Or can stock boot.img be flashed then boot straight into TWRP and flash whatever is the latest SuperSU? Are all SuperSI "systemless" now?
Also you stated "IMO there is no reason to run decrypted with latest OS". I have noticed VAST performance improvement with Nougat. Is this why you feel no reason? Would we not still gain even more speed back? (it was so sad watching my wife's old Nexus 5 booting 6.0.1 faster than my 5X).
sfhub said:
If you are using NBD90W I suggest you use the unofficial TWRP 3.0.2-3 that was posted a few pages back from the last post on the TWRP thread.
TWRP 3.0.2-0 won't decrypt Android N (will decrypt MM)
TWRP 3.0.2-1 has a major EFS bug that will brick your phone on restore
TWRP 3.0.2-2 has that EFS problem fixed, but has another problem where larger parttitions don't get backed up correctly.
TWRP 3.0.2-3 has both previous problems fixed.
---------- Post added at 10:19 AM ---------- Previous post was at 10:16 AM ----------
I didn't read the whole post but decrypted user partition isn't directly related to why your TWRP is disappearing.
When you boot with a stock image, it will replace your recovery with stock.
If there is just 1 byte change with your boot.img, it won't do that.
Installing SuperSU will patch your boot.img, thus it will no longer replace your recovery with stock.
You could flash a modified boot.img instead of SuperSU, but then you are depending on someone else creating a modified boot.img for you (or you creating it yourself). If your goal is to have root installed, then SuperSU will patch boot.img on the fly during install so no need for extra step.
Again, the overwriting of TWRP with stock recovery is not directly related to the modifications done to boot.img either by someone else or by SuperSU install. If you had done any change to boot.img even if it is off by 1 byte, TWRP won't be replaced by stock recovery.
IMO there is no reason to run decrypted with latest OS, but if you wanted to, the only requirement is you have dm-verity disabled in the boot.img. Both the custom boot.img and the SuperSU install would do this for you.
After you have dm-verity disabled (either by SuperSU install or installing custom boot.img), boot back into bootloader and do
fastboot format userdata
From that point on, as long as you *never* boot using stock boot.img your userdata will remain decrypted. If you ever boot with stock boot.img, by mistake, it will proceed to encrypt your userdata. Then you'd have to go through the same procedure again the decrypt (losing your userdata in the format step)
The proper way to upgrade is to flash boot.img, system.img, vendor.img in fastboot, then immediately (from bootloader menu) boot into TWRP recovery, and install SuperSU. Then everything will be preserved.
Click to expand...
Click to collapse

jb0ne said:
Wow, this post was SO HELPFUL.... Haven't rooted in a while, recently replaced our Nexus 5's with 5x's (on NBD90W) and hadn't felt the need to root. Plus it's gotten so much trickier even with Nexuses.
Anyway totally familiar with ADB/fastboot etc to flash stuff.
I still need to oem unlock and wipe still (bleh).
But after, one thing that's confusing me, to then root is a *custom* kernel (boot.img) needed now? Made specifically for (at this point in time) NBD90W? Or can stock boot.img be flashed then boot straight into TWRP and flash whatever is the latest SuperSU? Are all SuperSI "systemless" now?
Also you stated "IMO there is no reason to run decrypted with latest OS". I have noticed VAST performance improvement with Nougat. Is this why you feel no reason? Would we not still gain even more speed back? (it was so sad watching my wife's old Nexus 5 booting 6.0.1 faster than my 5X).
Click to expand...
Click to collapse
I've always decrypted but that is my personal choice. All I do to root afterwards is flash SuperSU-v2.7.8. That is it. You can adb sideload it (i use twrp for that) or flash it in twrp if you have it already on your phone).

jb0ne said:
But after, one thing that's confusing me, to then root is a *custom* kernel (boot.img) needed now? Made specifically for (at this point in time) NBD90W? Or can stock boot.img be flashed then boot straight into TWRP and flash whatever is the latest SuperSU? Are all SuperSI "systemless" now?
Click to expand...
Click to collapse
You must have a customized boot.img now for root. What customizations you absolutely need to have in boot.img is dependent on how you want root installed, but since you are modifying boot.img, you might as well just stick all the changes you need in boot.img and leave /system untouched.
The default install for SuperSU will make the required changes to whichever boot.img you currently have installed on your system. Generally that consists of disabling dm-verity (integrity check), making encryption optional (not absolutely required), making sepolicy security changes, and adding init script support to load SuperSU binaries later in the boot process.
There are configuration parameters you can feed into SuperSU install to force it to install root on /system instead of systemless, but I would just suggest systemless. It is a cleaner install IMO.
So install the stock boot.img and boot directly into TWRP from the bootloader menu, then install SuperSU and it will modify the boot.img you have installed (and back up original)
The only requirement to keep TWRP (and/or decrypted userdata) is to NEVER boot the phone using a stock boot.img. If you always immediately install SuperSU after flashing the stock boot.img that will satisfy that requirement.
jb0ne said:
Also you stated "IMO there is no reason to run decrypted with latest OS". I have noticed VAST performance improvement with Nougat. Is this why you feel no reason? Would we not still gain even more speed back? (it was so sad watching my wife's old Nexus 5 booting 6.0.1 faster than my 5X).
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-5x/general/unencrypted-faster-real-world-usage-t3365660

for some reason, when i fastboot installed twrp (after usb debug/unlocking bootloader) I kept getting mount errors when starting twrp. I tried flashing purenexus rom, wipes dalvic, system, data. then my data partition was 0. couldn't mount data part. to copy purenexus or system stock image. I ended up having to use my windows pc to wugfresh it back to life. has been a crazy night. I need coffee.
On coast of SC here, in Charleston. Wishing everybody best of luck with the hurricane.

trentag1988 said:
for some reason, when i fastboot installed twrp (after usb debug/unlocking bootloader) I kept getting mount errors when starting twrp. I tried flashing purenexus rom, wipes dalvic, system, data. then my data partition was 0. couldn't mount data part. to copy purenexus or system stock image. I ended up having to use my windows pc to wugfresh it back to life. has been a crazy night. I need coffee.
On coast of SC here, in Charleston. Wishing everybody best of luck with the hurricane.
Click to expand...
Click to collapse
Did you reboot after unlocking or go ahead and install TWRP right after unlocking?

I tried, but I kept getting the " cannot check for corrupt system because bootloader is unlocked" message, and it never fully booted. I managed to fix the 0data partition by fastboot format userdata, but pure Nexus never worked. It tried to boot, but it stuck on the spinning Google logo thing

Update: followed pure Nexus instruction; unlocked bootloader, then let it boot once to device setup. Restarted in fast boot, flashed twrp. Rebooted, went into twrp, formatted dalvic, system, user data and cache. Flashed pure Nexus from then gapps according to pure Nexus download page. Reformated dalvic and cache. Rebooted, stuck on Google logo, this time did not do its spinning thing. Have I missed a step??
---------- Post added at 03:33 PM ---------- Previous post was at 03:32 PM ----------
Update: followed pure Nexus instruction; unlocked bootloader, then let it boot once to device setup. Restarted in fast boot, flashed twrp. Rebooted, went into twrp, formatted dalvic, system, user data and cache. Flashed pure Nexus from twrp then gapps according to pure Nexus download page. Reformated dalvic and cache. Rebooted, stuck on Google logo, this time did not do its spinning thing. Have I missed a step??

trentag1988 said:
Update: followed pure Nexus instruction; unlocked bootloader, then let it boot once to device setup. Restarted in fast boot, flashed twrp. Rebooted, went into twrp, formatted dalvic, system, user data and cache. Flashed pure Nexus from then gapps according to pure Nexus download page. Reformated dalvic and cache. Rebooted, stuck on Google logo, this time did not do its spinning thing. Have I missed a step?
---------- Post added at 03:33 PM ---------- Previous post was at 03:32 PM ----------
Update: followed pure Nexus instruction; unlocked bootloader, then let it boot once to device setup. Restarted in fast boot, flashed twrp. Rebooted, went into twrp, formatted dalvic, system, user data and cache. Flashed pure Nexus from twrp then gapps according to pure Nexus download page. Reformated dalvic and cache. Rebooted, stuck on Google logo, this time did not do its spinning thing. Have I missed a step?
Click to expand...
Click to collapse
What firmware are you on?

Latest nrd90w(?) I believe
---------- Post added at 04:04 PM ---------- Previous post was at 04:04 PM ----------
NBD90W

sfhub said:
If you are using NBD90W I suggest you use the unofficial TWRP 3.0.2-3 that was posted a few pages back from the last post on the TWRP thread.
TWRP 3.0.2-0 won't decrypt Android N (will decrypt MM)
TWRP 3.0.2-1 has a major EFS bug that will brick your phone on restore
TWRP 3.0.2-2 has that EFS problem fixed, but has another problem where larger parttitions don't get backed up correctly.
TWRP 3.0.2-3 has both previous problems fixed.
---------- Post added at 10:19 AM ---------- Previous post was at 10:16 AM ----------
I didn't read the whole post but decrypted user partition isn't directly related to why your TWRP is disappearing.
When you boot with a stock image, it will replace your recovery with stock.
If there is just 1 byte change with your boot.img, it won't do that.
Installing SuperSU will patch your boot.img, thus it will no longer replace your recovery with stock.
You could flash a modified boot.img instead of SuperSU, but then you are depending on someone else creating a modified boot.img for you (or you creating it yourself). If your goal is to have root installed, then SuperSU will patch boot.img on the fly during install so no need for extra step.
Again, the overwriting of TWRP with stock recovery is not directly related to the modifications done to boot.img either by someone else or by SuperSU install. If you had done any change to boot.img even if it is off by 1 byte, TWRP won't be replaced by stock recovery.
IMO there is no reason to run decrypted with latest OS, but if you wanted to, the only requirement is you have dm-verity disabled in the boot.img. Both the custom boot.img and the SuperSU install would do this for you.
After you have dm-verity disabled (either by SuperSU install or installing custom boot.img), boot back into bootloader and do
fastboot format userdata
From that point on, as long as you *never* boot using stock boot.img your userdata will remain decrypted. If you ever boot with stock boot.img, by mistake, it will proceed to encrypt your userdata. Then you'd have to go through the same procedure again the decrypt (losing your userdata in the format step)
The proper way to upgrade is to flash boot.img, system.img, vendor.img in fastboot, then immediately (from bootloader menu) boot into TWRP recovery, and install SuperSU. Then everything will be preserved.
Click to expand...
Click to collapse
Thanks very much for the detailed assistance. If I wanted to install a custom ROM, do I have to decrypt my user data first? Or can I just install TWRP and then flash?

trentag1988 said:
Latest nrd90w(?) I believe
---------- Post added at 04:04 PM ---------- Previous post was at 04:04 PM ----------
NBD90W
Click to expand...
Click to collapse
I do not believe Pure Nexus is a Nougat Rom. Try starting over and flashing a Rom compatible with your firmware.

Root for OxygenOS 4.1.6

Hello everyone, I am using OOS 4.1.6 on my new 3T, however I am unable to get root even though I have already tried with latest TWRP, magisk 12, and SuperSU 2.82. Nothing worked everytime I've got not rooted on root checker.

Please describe in steps what you did.

AcidNoteZ said:
Please describe in steps what you did.
Click to expand...
Click to collapse
Hi,
We unclocked the bootloader, then we did flash with twrp 3.1.0 and installed SU 2.82.
After doing all this, the phone was not restarting.

mittal.bti said:
Hi,
We unclocked the bootloader, then we did flash with twrp 3.1.0 and installed SU 2.82.
After doing all this, the phone was not restarting.
Click to expand...
Click to collapse
Well first of all, format your whole phone over TWRP. (System too, but make sure you have the full Oxygen OS zip on a computer.)
After formating all partitions, move the full OOS zip and Magisk 12.0 on your phone. Flash the OOS zip, restart your recovery and flash Magisk after it.
That worked 100% for me all the time.
If you still need assistance with that, we can setup Teamviewer so I can guide you through this.

mittal.bti said:
Hi,
We unclocked the bootloader, then we did flash with twrp 3.1.0 and installed SU 2.82.
After doing all this, the phone was not restarting.
Click to expand...
Click to collapse
Same here! The phone freezes in boot animation screen. Even the animation stopped!

Guessing it's about the f2fs file system. I used to have a situation like this with Oneplus 2. My step was to format data and cache partitions back to ext4, and that worked.
Using 3t now, still not rooted. Don't want to start over after bootloader unlocking
Sent from my ONEPLUS A3003 using Tapatalk

I had the same problem and was solved with twrp 3.0.4-1 and SuperSU-v2.82.

AcidNoteZ said:
Well first of all, format your whole phone over TWRP. (System too, but make sure you have the full Oxygen OS zip on a computer.)
After formating all partitions, move the full OOS zip and Magisk 12.0 on your phone. Flash the OOS zip, restart your recovery and flash Magisk after it.
That worked 100% for me all the time.
If you still need assistance with that, we can setup Teamviewer so I can guide you through this.
Click to expand...
Click to collapse
Should I flash whole os using twrp. Or should I flash Via adb sideload?

ajsonofgod said:
Should I flash whole os using twrp. Or should I flash Via adb sideload?
Click to expand...
Click to collapse
If you still want root, twrp, if dont flash it over adb

AcidNoteZ said:
If you still want root, twrp, if dont flash it over adb
Click to expand...
Click to collapse
Ok, I will try and update here then.

I'd say wipe everything possible in TWRP except for system partition, then boot the system and then eventually flash some kind of a root package - either Magisk or SuperSU. I always do it that way and it works. I am not really sure but otherwise it might have something to do with the data encryption.

Use following and you should be all set (just did it 2 days ago):
1st Flash Stock Recovery (go back to stock - https://forums.oneplus.net/threads/...-3-3t-and-go-back-completely-to-stock.456232/
Flash TWRP after you achieve STOCK OS 4.1.6.
Use this TWRP version for now (there is some issue with 3.1.1-2 i saw on forums):
twrp-3.1.1-0-oneplus3t.img
To Root just use Magisk-v13.3.zip (IMO way better than SuperSu + has MagiskHide for AndroidPay/Snapchat/SafetyNet checks):
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
That is it, done!

Showbiz81 said:
I had the same problem and was solved with twrp 3.0.4-1 and SuperSU-v2.82.
Click to expand...
Click to collapse
Thanks you are a life saver

I had the same problem and was solved with twrp 3.0.4-1 and Magisk-v13.3

Oreo update for rooted OnePlus 5t

Pls help me updating my 5t to oreo.i am currently on version 4.7.6 with twrp recovery nd super su root.
After updating to Oreo I again want to root my phone
Pls share links to download compatibile ROM, recovery nd super su.zip

But you already have the OREO OOS ROM installed, why not use it? Flash the Oreo recovery from codeworkx through fastboot, make sure to follow the instructions so it sticks and then flash Magisk or any root solution of your choice. It's not hard if you do some searching.

Check in ROMs' threads and come back what your interested ROM is.

What I did was flash the ota to update me to Oreo. Then had to reflash Magisk and kernel.

jcroy2828 said:
What I did was flash the ota to update me to Oreo. Then had to reflash Magisk and kernel.
Click to expand...
Click to collapse
Kernel?

jcroy2828 said:
What I did was flash the ota to update me to Oreo. Then had to reflash Magisk and kernel.
Click to expand...
Click to collapse
Pls give me link to download magisk nd what does kernel mean?

mannulko said:
Kernel?
Click to expand...
Click to collapse
Il check when I get home. I just used Magisk 15.3 from the Magisk xda thread

jcroy2828 said:
Il check when I get home. I just used Magisk 15.3 from the Magisk xda thread
Click to expand...
Click to collapse
I mean pls tell me step by step what should I do.currently I am on 4.7.6 wth twrp recovery nd rooted.i want to update my phone to Oreo nd root again

mannulko said:
I mean pls tell me step by step what should I do.currently I am on 4.7.6 wth twrp recovery nd rooted.i want to update my phone to Oreo nd root again
Click to expand...
Click to collapse
If you have already installed a custom recovery and rooted your phone then you should be able to follow these instructions.
I can personally confirm that I was able to install the beta versions of Oreo and the final version of Oreo without any issues.
Here's what I did:
1. Download full .zip
2. Download Blu_Spark TWRP or Codeworkx TWRP (I personally used Blu_Spark but both should work).
3. Download Magisk 15.3 (I havent used SuperSu in a while so I can't confirm how well it works on Oreo but in my opinion Magisk is a better root method and it works in this version of android).
4. Make sure you have both ROM and Magisk on a easy to find place on your phone.
5. Boot to fastboot and fastboot flash the recovery you just downloaded.
6. Boot to recovery, wipe dalvik and cache and then install the ROM.
7. Once the installation is done, boot to system and wait till the system to finish updating. Once there you can go to settings > phone status and it should read (android version = 8.0.0 and OxygenOS version = 5.0.2, congrats, you're on the latest OxygenOS version for this phone).
8. Reboot to fastboot, and fastboot flash the custom recovery again.
9. Boot to recovery, wipe dalvik and cache again, and flash Magisk, wipe dalvik and cache once more and reboot to system.
10. Once the phone is booted up, you should be rooted with Magisk and on the latest OS.
9. Boot to recovery, wipe dalvik and cache again, and flash Magisk, wipe dalvik and cache once more and reboot to system.
10. Once the phone is booted up, you should be rooted with Magisk and on the latest OS.
NOTE: Since this is a big version update from Nougat, it's always recommended to do a clean flash although not necessary in most cases unless there are issues like big battery drain or when apps or the OS are not working properly. Also, if you are coming from a custom ROM and not the official OxygenOS, then you should definitely do a clean installation (even if said custom ROM is based on OxygenOS).

HueleSnaiL said:
If you have already installed a custom recovery and rooted your phone then you should be able to follow these instructions.
I can personally confirm that I was able to install the beta versions of Oreo and the final version of Oreo without any issues.
Here's what I did:
1. Download full .zip
2. Download Blu_Spark TWRP or Codeworkx TWRP (I personally used Blu_Spark but both should work).
3. Download Magisk 15.3 (I havent used SuperSu in a while so I can't confirm how well it works on Oreo but in my opinion Magisk is a better root method and it works in this version of android).
4. Make sure you have both ROM and Magisk on a easy to find place on your phone.
5. Boot to fastboot and fastboot flash the recovery you just downloaded.
6. Boot to recovery, wipe dalvik and cache and then install the ROM.
7. Once the installation is done, boot to system and wait till the system to finish updating. Once there you can go to settings > phone status and it should read (android version = 8.0.0 and OxygenOS version = 5.0.2, congrats, you're on the latest OxygenOS version for this phone).
8. Reboot to fastboot, and fastboot flash the custom recovery again.
9. Boot to recovery, wipe dalvik and cache again, and flash Magisk, wipe dalvik and cache once more and reboot to system.
10. Once the phone is booted up, you should be rooted with Magisk and on the latest OS.
9. Boot to recovery, wipe dalvik and cache again, and flash Magisk, wipe dalvik and cache once more and reboot to system.
10. Once the phone is booted up, you should be rooted with Magisk and on the latest OS.
NOTE: Since this is a big version update from Nougat, it's always recommended to do a clean flash although not necessary in most cases unless there are issues like big battery drain or when apps or the OS are not working properly. Also, if you are coming from a custom ROM and not the official OxygenOS, then you should definitely do a clean installation (even if said custom ROM is based on OxygenOS).
Click to expand...
Click to collapse
What is clean flash?

HueleSnaiL said:
If you have already installed a custom recovery and rooted your phone then you should be able to follow these instructions.
I can personally confirm that I was able to install the beta versions of Oreo and the final version of Oreo without any issues.
Here's what I did:
1. Download full .zip
2. Download Blu_Spark TWRP or Codeworkx TWRP (I personally used Blu_Spark but both should work).
3. Download Magisk 15.3 (I havent used SuperSu in a while so I can't confirm how well it works on Oreo but in my opinion Magisk is a better root method and it works in this version of android).
4. Make sure you have both ROM and Magisk on a easy to find place on your phone.
5. Boot to fastboot and fastboot flash the recovery you just downloaded.
6. Boot to recovery, wipe dalvik and cache and then install the ROM.
7. Once the installation is done, boot to system and wait till the system to finish updating. Once there you can go to settings > phone status and it should read (android version = 8.0.0 and OxygenOS version = 5.0.2, congrats, you're on the latest OxygenOS version for this phone).
8. Reboot to fastboot, and fastboot flash the custom recovery again.
9. Boot to recovery, wipe dalvik and cache again, and flash Magisk, wipe dalvik and cache once more and reboot to system.
10. Once the phone is booted up, you should be rooted with Magisk and on the latest OS.
9. Boot to recovery, wipe dalvik and cache again, and flash Magisk, wipe dalvik and cache once more and reboot to system.
10. Once the phone is booted up, you should be rooted with Magisk and on the latest OS.
NOTE: Since this is a big version update from Nougat, it's always recommended to do a clean flash although not necessary in most cases unless there are issues like big battery drain or when apps or the OS are not working properly. Also, if you are coming from a custom ROM and not the official OxygenOS, then you should definitely do a clean installation (even if said custom ROM is based on OxygenOS).
Click to expand...
Click to collapse
Will the official TWRP work with no problem?
I'm already on 4.7.6, offical twrp-3.2.1-1-dumpling and magisk 15.3, and don't really want to flash another recovery.

HueleSnaiL said:
If you have already installed a custom recovery and rooted your phone then you should be able to follow these instructions.
I can personally confirm that I was able to install the beta versions of Oreo and the final version of Oreo without any issues.
Here's what I did:
1. Download full .zip
2. Download Blu_Spark TWRP or Codeworkx TWRP (I personally used Blu_Spark but both should work).
3. Download Magisk 15.3 (I havent used SuperSu in a while so I can't confirm how well it works on Oreo but in my opinion Magisk is a better root method and it works in this version of android).
4. Make sure you have both ROM and Magisk on a easy to find place on your phone.
5. Boot to fastboot and fastboot flash the recovery you just downloaded.
6. Boot to recovery, wipe dalvik and cache and then install the ROM.
7. Once the installation is done, boot to system and wait till the system to finish updating. Once there you can go to settings > phone status and it should read (android version = 8.0.0 and OxygenOS version = 5.0.2, congrats, you're on the latest OxygenOS version for this phone).
8. Reboot to fastboot, and fastboot flash the custom recovery again.
9. Boot to recovery, wipe dalvik and cache again, and flash Magisk, wipe dalvik and cache once more and reboot to system.
10. Once the phone is booted up, you should be rooted with Magisk and on the latest OS.
9. Boot to recovery, wipe dalvik and cache again, and flash Magisk, wipe dalvik and cache once more and reboot to system.
10. Once the phone is booted up, you should be rooted with Magisk and on the latest OS.
NOTE: Since this is a big version update from Nougat, it's always recommended to do a clean flash although not necessary in most cases unless there are issues like big battery drain or when apps or the OS are not working properly. Also, if you are coming from a custom ROM and not the official OxygenOS, then you should definitely do a clean installation (even if said custom ROM is based on OxygenOS).
Click to expand...
Click to collapse
Thanks a lot I have updated nd rooted but now 5.0.3 is out ? how to go from 5.0.2 to 5.0.3 nd root
I also wanna format my 5t

mannulko said:
What is clean flash?
Click to expand...
Click to collapse
Wiping data and system partition which means you're wiping the entire OS and installing the new version on a clean partition. Think of it as formatting a hard drive and installing an OS instead of just upgrading your existing OS.
You obviously lose all apps installed,and it would be like when you first turned on your phone, however as long as you don't wipe internal storage, all your photos,music,etc are not wiped so you can use apps like titanium backup to restore all apps and data .
This method is recommended when switching from different custom ROM's and when upgrading from major version updates, like for example, going to Android 8 from Andorid 7.
---------- Post added at 07:13 PM ---------- Previous post was at 07:09 PM ----------
rockuman_ex said:
Will the official TWRP work with no problem?
I'm already on 4.7.6, offical twrp-3.2.1-1-dumpling and magisk 15.3, and don't really want to flash another recovery.
Click to expand...
Click to collapse
I used that same version of TWRP back during the Oreo beta and it didn't work so I had to switch to blu_spark.

HueleSnaiL said:
Wiping data and system partition which means you're wiping the entire OS and installing the new version on a clean partition. Think of it as formatting a hard drive and installing an OS instead of just upgrading your existing OS.
You obviously lose all apps installed,and it would be like when you first turned on your phone, however as long as you don't wipe internal storage, all your photos,music,etc are not wiped so you can use apps like titanium backup to restore all apps and data .
This method is recommended when switching from different custom ROM's and when upgrading from major version updates, like for example, going to Android 8 from Andorid 7.
---------- Post added at 07:13 PM ---------- Previous post was at 07:09 PM ----------
I used that same version of TWRP back during the Oreo beta and it didn't work so I had to switch to blu_spark.
Click to expand...
Click to collapse
So i took the jump and flashed blu spark and the 5.0.3 full rom.
Yes i lost the recovery to stock, but that's ok. Just want to get OTA in the future and I don't need root at the moment.
So this is what i did (coming from 4.7.6, official twrp, magisk 15.3)
Make sure you have all the necessary files (eg. blu spark img file and the full ota file on your phone
boot the fastboot and "fastboot flash recovery twrp-3.2.1-x_blu_spark_v8.68-op5_op5t.img"
On the phone, choose and go to recovery
(now i'm on blu spark) Wipe Cache and Dalvik cache (i did this 2 times just to make sure)
Choose install and select the full ota rom file
Let it run and install the rom (took less than 5 mins)
Wipe Cache and Dalvik cache again (again, i wiped 2 times just to make sure)
Reboot
Make take a while (less than 10mins) for android to start and do the upgrade etc
Done
So far so good, i don't see any immediate problem. I will play a bit more and will post if I encounter any problem :good:

I have updated to 5.0.3 through system update app. where it downloaded full ota file and installed.Now I want to install twrp nd root my phone so pls confirm my steps
1 boot into fastboot mode and flash bluespark recovery
2 wipe delvik/cache from twrp recovery
3 flash magisk zip
4 again wipe delvik cache
5 reboot
are above steps correct?

Hello,
i have latest (8.69) twrp blue_spark and i try to flash latest oxygen os
1)Oreo 5.0.3: OnePlus5TOxygen_43_OTA_029_all_1802022353_460d.zip
2)magisk 15.3
3)wipe davlik/cache
reboot system and i get stucked at bootanimation of OxygenOS.
Any help guys please ?
Thanks!
Redownloaded Magisk 15.3 and ok

BrollyG4 said:
Hello,
i have latest (8.69) twrp blue_spark and i try to flash latest oxygen os
1)Oreo 5.0.3: OnePlus5TOxygen_43_OTA_029_all_1802022353_460d.zip
2)magisk 15.3
3)wipe davlik/cache
reboot system and i get stucked at bootanimation of OxygenOS.
Any help guys please ?
Thanks!
Redownloaded Magisk 15.3 and ok
Click to expand...
Click to collapse
I'm having the same problem, I think it's version (8.69) twrp blue_spark. I'll try with version 8.68

OnePlus 5T Oreo OTA Updating

Hello,
I have recently purchased my OP5T transitioning from 3 years of iOS and this is one of the best choice I've made when using phones.
I have managed to root my phone on OS 4.7.6 with SuperSU and install TWRP recovery. However, with the new Oreo update out, I want to upgrade my OS and still have root. Reading many tutorials on the OP forums and comments in the XDA forums, I was very confused mainly regarding the TWRP and it's compatibility on Oreo as well as when to flash it (before or after flashing oreo ota??)
I already have the Oreo 5.0.1 file installed on my PC.
Sorry for another pointless thread, but I'm at a loss here.
Thanks.

There are different flavors of TWRP for the 1+5t and some versions of them were unable to decrypt and mount /data partition so that's maybe the issues you read about.
However, I can personally confirm that I was able to install the beta versions of Oreo and the final version of Oreo without any issues.
Here's what I did:
1. Download full .zip
2. Download Blu_Spark TWRP
3. Download Magisk 15.3
4. Make sure you have both ROM and Magisk on a easy to find place on your phone.
5. Boot to fastboot and fastboot flash the recovery you just downloaded.
6. Boot to recovery, wipe dalvik and cache and then install the ROM.
7. Once the installation is done, boot to system and wait till the system to finish updating. Once there you can go to settings > phone status and it should read (android version = 8.0.0 and OxygenOS version = 5.0.2).
8. Reboot to fastboot, and fastboot flash the custom recovery again.
9. Boot to recovery, wipe dalvik and cache again, and flash Magisk, wipe dalvik and cache once more and reboot to system.
10. Once the phone is booted up, you should be rooted with Magisk and on the latest OS.

Did I hear SuperSU is broken in the Official Oreo OTA? I haven't made the jump to Magisk and would rather stick with SuperSU for root.

crakerjac said:
Did I hear SuperSU is broken in the Official Oreo OTA? I haven't made the jump to Magisk and would rather stick with SuperSU for root.
Click to expand...
Click to collapse
Magsik is way better. 95% of people use it. It helps pass safety net which is requires for apps like pokemon go, bank apps, snapchat etc. So if u want to use those apps while rooted. Stick with magisk.
Yeah all the issues with twrp after at the beginning of this phones life. If u stick with oos and don't try custom roms u will have 0 issues.

I used SuperSu for 3-4 years and was too stubborn to try Magisk for quite a while....always saw guys talking about it this module and that module and didnt understand the hype. Then about 4 months ago I gave it a shot and in an instance totally understood the hype. I my opinion it is superior to SuperSu in everyway.

HueleSnaiL said:
There are different flavors of TWRP for the 1+5t and some versions of them were unable to decrypt and mount /data partition so that's maybe the issues you read about.
However, I can personally confirm that I was able to install the beta versions of Oreo and the final version of Oreo without any issues.
Here's what I did:
1. Download full .zip
2. Download Blu_Spark TWRP
3. Download Magisk 15.3
4. Make sure you have both ROM and Magisk on a easy to find place on your phone.
5. Boot to fastboot and fastboot flash the recovery you just downloaded.
6. Boot to recovery, wipe dalvik and cache and then install the ROM.
7. Once the installation is done, boot to system and wait till the system to finish updating. Once there you can go to settings > phone status and it should read (android version = 8.0.0 and OxygenOS version = 5.0.2).
8. Reboot to fastboot, and fastboot flash the custom recovery again.
9. Boot to recovery, wipe dalvik and cache again, and flash Magisk, wipe dalvik and cache once more and reboot to system.
10. Once the phone is booted up, you should be rooted with Magisk and on the latest OS.
Click to expand...
Click to collapse
Following your steps above, will the latest official twrp work?

Dazed No More said:
I used SuperSu for 3-4 years and was too stubborn to try Magisk for quite a while....always saw guys talking about it this module and that module and didnt understand the hype. Then about 4 months ago I gave it a shot and in an instance totally understood the hype. I my opinion it is superior to SuperSu in everyway.
Click to expand...
Click to collapse
lmao same with me, i was so stubborn to try Magisk and always used SU, then i figured it out and I love magisk and would not go back to SU at this time.

I guess I just don't understand Magisk then... I just want to flash a zip and have access to root and Xposed.

I think most confusion from magisk come from modules
I thought magisk was a framework like closed by the way people were talking about it
Finally made the jump
Magisk is root on its own like supersu
But you have the added choice to install systemless modules
And you can add xposed the same way as supersu, its the same procedure

Damn Root......

No matter what I try I am unable to root my P2XL on Android 10......
The process I am taking is to boot up twrp and flash the latest Magisk zip, however it fails right at the end with the error failed to mound system and vendor.....
I have just tried to do it again but with a clean install of the October update but nothing has changed.......
the October update wasn't without issue either as that too failed and I had to factory reset the September image and update OTA.....
anyway, any thoughts or advice on how to achieve it or what might be wrong.......
is there specific TWRP versions I need to boot from etc,,,,

Don't bother with twrp
Just use magisk.
Download the factory pixel image on your PC , unzip the boot.img file and transfer to your phone.
Open magisk manager and install magisk by patching the boot.img file U just transferred.
Copy that new patched boot img back to your PC.
Use ADB to ADB reboot bootloader
Type: fastboot flash boot patched_boot.img
That's it

mediaman123 said:
No matter what I try I am unable to root my P2XL on Android 10......
The process I am taking is to boot up twrp and flash the latest Magisk zip, however it fails right at the end with the error failed to mound system and vendor.....
I have just tried to do it again but with a clean install of the October update but nothing has changed.......
the October update wasn't without issue either as that too failed and I had to factory reset the September image and update OTA.....
anyway, any thoughts or advice on how to achieve it or what might be wrong.......
is there specific TWRP versions I need to boot from etc,,,,
Click to expand...
Click to collapse
Since it has been a few months since I messed with my 2 XL, I followed the upgrade 9x guide in my sig to make sure I didn't forget/skip anything.
I just jumped to 10 last night, root, twrp, and cust kernel.
fastboot latest factory image (I left the -w intact for a clean wipe since going form 9 to 10-but have read it is not necessary)
booted back into bootloader and fastboot boot twrp 3.3.3-0.img
once in twrp I install 3.3.3-0
in twrp installed latest EX kernel for 10
rebooted to system
let it boot up fully for a few minutes
booted into twrp
flashed magisk 19.4
rebooted to trwp (superstition for me)
rebooted to system
checked magisk hide in magisk manager
hit systemless hosts in magisk manager
rebooted
Fresh install of android 10, rooted, with cust kernel.
You mentioned the "failed" notice. I've read several places that TWRP will throw the "failed to mount" warning (or something like that) but that it is a false flag. I got this as well and just continued on.
There may be many diff ways to accomplish this, but THIS method worked for me.

Az Biker said:
[/HIDE]
Since it has been a few months since I messed with my 2 XL, I followed the upgrade 9x guide in my sig to make sure I didn't forget/skip anything.
I just jumped to 10 last night, root, twrp, and cust kernel.
fastboot latest factory image (I left the -w intact for a clean wipe since going form 9 to 10-but have read it is not necessary)
booted back into bootloader and fastboot boot twrp 3.3.3-0.img
once in twrp I install 3.3.3-0
in twrp installed latest EX kernel for 10
rebooted to system
let it boot up fully for a few minutes
booted into twrp
flashed magisk 19.4
rebooted to trwp (superstition for me)
rebooted to system
checked magisk hide in magisk manager
hit systemless hosts in magisk manager
rebooted
Fresh install of android 10, rooted, with cust kernel.
You mentioned the "failed" notice. I've read several places that TWRP will throw the "failed to mount" warning (or something like that) but that it is a false flag. I got this as well and just continued on.
There may be many diff ways to accomplish this, but THIS method worked for me.
Click to expand...
Click to collapse
I used a similar method:
I used Duece's Script to flash and format data with April image ( I wanted to able to decrypt with pattern lock); rebooted to system; then rebooted back into bootloader and used Duece's Script to flash but not format data with October image; booted back into bootloader and fastboot boot twrp 3.3.0-0.img; in twrp, flashed 3.3.0-0 zip, rebooted to system, and did initial phone set up; rebooted to twrp, flashed caesium kernel and magisk 19.3 and rebooted to system. Everything worked fine. I did get failed to mount" warning in twrp but both the kerkel and magisk worked fine.

Az Biker said:
[/HIDE]
Since it has been a few months since I messed with my 2 XL, I followed the upgrade 9x guide in my sig to make sure I didn't forget/skip anything.
I just jumped to 10 last night, root, twrp, and cust kernel.
fastboot latest factory image (I left the -w intact for a clean wipe since going form 9 to 10-but have read it is not necessary)
booted back into bootloader and fastboot boot twrp 3.3.3-0.img
once in twrp I install 3.3.3-0
in twrp installed latest EX kernel for 10
rebooted to system
let it boot up fully for a few minutes
booted into twrp
flashed magisk 19.4
rebooted to trwp (superstition for me)
rebooted to system
checked magisk hide in magisk manager
hit systemless hosts in magisk manager
rebooted
Fresh install of android 10, rooted, with cust kernel.
You mentioned the "failed" notice. I've read several places that TWRP will throw the "failed to mount" warning (or something like that) but that it is a false flag. I got this as well and just continued on.
There may be many diff ways to accomplish this, but THIS method worked for me.
Click to expand...
Click to collapse
Hi, by "checked magisk hide", do you mean that you were able to bypass google's safetynet?
I havn't rooted my P2 XL on A10 since i wasn't sure i will be able to bypass safetynet!
thx

1902 said:
Hi, by "checked magisk hide", do you mean that you were able to bypass google's safetynet?
I havn't rooted my P2 XL on A10 since i wasn't sure i will be able to bypass safetynet!
thx
Click to expand...
Click to collapse
My safety net passes in magisk, but I don't use any apps that I can verify that with.

jlokos said:
I used a similar method:
I used Duece's Script to flash and format data with April image ( I wanted to able to decrypt with pattern lock); rebooted to system; then rebooted back into bootloader and used Duece's Script to flash but not format data with October image; booted back into bootloader and fastboot boot twrp 3.3.3-0.img; in twrp, flashed 3.3.3-0 zip, rebooted to system, and did initial phone set up; rebooted to twrp, flashed caesium kernel and magisk 19.3 and rebooted to system. Everything worked fine. I did get failed to mount" warning in twrp but both the kerkel and magisk worked fine.
Click to expand...
Click to collapse
Hi, for TWRP, are you using 3.3.0.0 or 3.3.3.0
I was only able to find 3.3.0.0
Thanks

docluv01 said:
Hi, for TWRP, are you using 3.3.0.0 or 3.3.3.0
I was only able to find 3.3.0.0
Thanks
Click to expand...
Click to collapse
Sorry; an extra 3; I'm using TWRP 3.3.0.0.
---------- Post added at 07:58 AM ---------- Previous post was at 07:37 AM ----------
1902 said:
Hi, by "checked magisk hide", do you mean that you were able to bypass google's safetynet?
I havn't rooted my P2 XL on A10 since i wasn't sure i will be able to bypass safetynet!
thx
Click to expand...
Click to collapse
I DL magisk hide module and use it for two apps, one for comcast business and the other which regulates my home thermostat.

Wow, thanks guys.....you have all laid out pretty well your processes which I will go through later on....
It's strange, as everything is installed and magisk believes it working it just doesn't pass thee root check..
I'll get back to you with my progress...??