OnePlus 5T Oreo OTA Updating - OnePlus 5T Questions & Answers

OnePlus 5T Oreo OTA Updating - OnePlus 5T Questions & Answers

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

Related

OnePlus 3 OOS N beta 10 bootloop with supersu

With modified twrp 28 i flashed ROM -> reboot to system -> system->reboot recovery -> flashed supersu 2.79 -> reboot to system gets stuck at the boot animation for about 20 minutes. i re flashed the ROM and using it without root. Followed the same for beta 9 without any issues(2.78 SR5 then).
Now, I tried with 2.79 and 2.79 SR1, both same issue. I see couple of people mentioning root is working with 2.79, so looks like i am have some issue with my phone or missing something

Try wiping cache/dalvik. If that doesnt work wipe system and reflash the rom and supersu. Good luck!

Are you on the latest firmware? Because I'm on the Sultan ROM, which requires the latest firmware, and I'm having a ton of issues with root and the supersu app. I finally got supersu to install, but it's just unstable

Working for me:
flash ROM
flash TWRP. img
reboot to recovery
flash supersu (and other system mod eg. Viper...)
wipe dalvik/art and cache
than reboot to system.

Use Phh superuser. For some reason other superusers break F2FS. I have no clue how you guys get TWRP 28 to work but it keeps asking for a pin even when my phone is decrypted.

papzi57 said:
Working for me:
flash ROM
flash TWRP. img
reboot to recovery
flash supersu (and other system mod eg. Viper...)
wipe dalvik/art and cache
than reboot to system.
Click to expand...
Click to collapse
So right
Sent from my ONEPLUS A3003 using Tapatalk

Puddi_Puddin said:
Use Phh superuser. For some reason other superusers break F2FS. I have no clue how you guys get TWRP 28 to work but it keeps asking for a pin even when my phone is decrypted.
Click to expand...
Click to collapse
I always use TWRP and SuperSU, when it comes to rooting.
But that sounds interesting !
Could you elaborate ?? Could you give all very steps you've done ? Any success rate ?

You should never flash OOS Rom with TWRP, you must restore the stock recovery before then after you can flash TWRP and SuperSU.
http://downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_openbeta_10/

I just flashed SuperSU 2.79 SR1 on my Open Beta 10.
I followed the same procedure I did when I rooted Open Beta 9:
adb sideload SR1-SuperSU-v2.79-SR1.zip
Did this under TWRP mod28 (Advanced/ADB_Sideload), not OnePlus recovery.
And...
Yes ! I'm now rooted on Open Beta 10 !
That was successful... on my encrypted F2FS filesystem.

Does anyone know if xposed is working with open beta 10?
Skickat från min ONEPLUS A3003 via Tapatalk

nabeelio said:
Are you on the latest firmware? Because I'm on the Sultan ROM, which requires the latest firmware, and I'm having a ton of issues with root and the supersu app. I finally got supersu to install, but it's just unstable
Click to expand...
Click to collapse
You don't need the last one.
You need the 3.2.6 at least if I remember right.
I'm using the 3.2.7 because I plan to upgrade to OP3T's battery (incompatible with the last one, the 3.2.8) and all is fine for me.
I'm rooted with SuperSU too.

REiced said:
Does anyone know if xposed is working with open beta 10?
Skickat från min ONEPLUS A3003 via Tapatalk
Click to expand...
Click to collapse
Xposed isn't compatible with android nougat regardless of what ROM you are on

Fixed my bootloop issue - removed xposed and all modules, removed magisk and all modules. Removing magisk was also causing bootloops, so I had to reinstall supersu afterwards, which seemed to cure it. And woops, you're on Nougat, but cleaning everything out might help

It is not SuperSu that is unstable or an issue with TWRP that causes the problems, such as breaking root, but rather the boot image that comes with 10. After installing ten, my root was broken and then I noticed in TWRP that my data partition wasn't mounting. So I reformatted the data partition to f2fs from emmc that it formats it as. However, when I rebooted, it took an extra long time before starting up and when it did finally boot up, root was broken again. I then reasoned that the problem lies with the boot image as when one reboots, it will then reformat and encrypt your data partition and break root. I simply flashed and older boot image (both beta 8 or 9 work) and the data partition mounts and I have installed SuperSu, Greenify, Root Browser and Root Deleter. All root apps are working fine and when I reboot, I no longer have any issues. Steps I used. install Beta 10, boot to fastboot and flash older boot image (Don't forget to clear the cache/dalvick). Reboot to TWRP and wipe/reformat your data partition. Flash SuperSu and setup as normal, since you will need to go through the setup again after blowing away the data partition.
---------- Post added at 10:18 AM ---------- Previous post was at 09:27 AM ----------
BTW, I tested it by reflashing the boot image from Beta 10 again and it formatted and encrypted the partition once again. So the issue definitely lies in the boot image that is included with Beta 10. Flash an older boot image, such as the one from Beta 9, as a temporary workaround.

jim262 said:
It is not SuperSu that is unstable or an issue with TWRP that causes the problems, such as breaking root, but rather the boot image that comes with 10. After installing ten, my root was broken and then I noticed in TWRP that my data partition wasn't mounting. So I reformatted the data partition to f2fs from emmc that it formats it as. However, when I rebooted, it took an extra long time before starting up and when it did finally boot up, root was broken again. I then reasoned that the problem lies with the boot image as when one reboots, it will then reformat and encrypt your data partition and break root. I simply flashed and older boot image (both beta 8 or 9 work) and the data partition mounts and I have installed SuperSu, Greenify, Root Browser and Root Deleter. All root apps are working fine and when I reboot, I no longer have any issues. Steps I used. install Beta 10, boot to fastboot and flash older boot image (Don't forget to clear the cache/dalvick). Reboot to TWRP and wipe/reformat your data partition. Flash SuperSu and setup as normal, since you will need to go through the setup again after blowing away the data partition.
---------- Post added at 10:18 AM ---------- Previous post was at 09:27 AM ----------
BTW, I tested it by reflashing the boot image from Beta 10 again and it formatted and encrypted the partition once again. So the issue definitely lies in the boot image that is included with Beta 10. Flash an older boot image, such as the one from Beta 9, as a temporary workaround.
Click to expand...
Click to collapse
It looks like I am having the same issue.
Did you just extract the boot.img from the Beta 9 Rom zip and flash it like the following:
Code:
fastboot flash boot boot.img

Tybalt said:
It looks like I am having the same issue.
Did you just extract the boot.img from the Beta 9 Rom zip and flash it like the following:
Code:
fastboot flash boot boot.img
Click to expand...
Click to collapse
Just extracted the image from the zip and flashed it in fastboot using method above.

Best way to upgrade to O from current state? Stock 7.1.1 rooted.

So I have a Play Store Pixel XL running stock 7.1.1, rooted, with TWRP 3.0.2-0-RC1 recovery.
Most upgrade guides I've read seem to assume stock recovery, or no root to start, or some such.
What do I need to do to get to Stock Android O, rooted? If I need to wipe the phone I can, but I'd prefer not to if I can avoid it.
Thanks!

If you don't want to wipe just update through factory image, just open the factory zip, open flash-all file and remove "-w" from last line, then execute it (update without wipe)
But I suggest to flash the stock factory image with the "-w" to make a clean install, flashing major release like 7.x -> 8.x is always better wipe to avoid potential issues.
But yes, you can first give a try without wipe and only if you find bugs try wiping. Your choice.

simply flash the OTA, then re-root

xraystyle said:
So I have a Play Store Pixel XL running stock 7.1.1, rooted, with TWRP 3.0.2-0-RC1 recovery.
Most upgrade guides I've read seem to assume stock recovery, or no root to start, or some such.
What do I need to do to get to Stock Android O, rooted? If I need to wipe the phone I can, but I'd prefer not to if I can avoid it.
Thanks!
Click to expand...
Click to collapse
Use full unroot in supersu. Then take ota. Then root again after upgrading to O

Thanks for the help everyone, you pointed be in the right direction.
In the event that it might help someone else, here's what I ended up doing:
1. I downloaded the OTA, booted into the TWRP I had currently installed, and then sideloaded the OTA.
2. I used ADB to push the newest TWRP flashable zip, the latest SuperSU, and the latest SU-Hide to /sdcard on the device.
3. I then used the most recent TWRP bootable img, booted into it with fastboot, and used it to flash the TWRP zip I had previously pushed to the phone storage. I then had the OTA with the latest TWRP installed on the phone.
4. Finally, I rebooted to recovery on the phone (latest TWRP now instead of stock), and flashed SuperSU and SU-Hide.
I'm now stock, rooted, on O. No wipe necessary, kept all my apps and data. So far the OS itself has been entirely stable. I had an issue or two with a few apps after the upgrade, but those were fixed with a quick re-install. Except for Better Terminal Emulator Pro, seems it doesn't want to work on Oreo and it's no longer under active development. It's fine though, there's other terminal emulators out there.
Thanks again for the help!

xraystyle said:
3. I then used the most recent TWRP bootable img, booted into it with fastboot, and used it to flash the TWRP zip I had previously pushed to the phone storage. I then had the OTA with the latest TWRP installed on the phone.
Click to expand...
Click to collapse
Which version of TWRP do you have TWRP working with Oreo 8.0?
I can boot into the modded TWRP 3.1 (fastboot boot twrp-3-1-pixel-bootable-mod.img) but AFAIK there is no working flashable recovery for 8.0 yet.

quick question, are the steps the same for stock root 7.1.2? I've never installed twrp. I've fastbooted to it to root and that's it. I'm familiar with that as I've sideloaded all the ota security updates and the re-rooted.
my main question is su-hide required? I have never done it and have no reason to that I'm aware of. Seems all the guides I see involve su-hide and flashing kernels etc. I've never changed kernels since having the pixel. Really just want root for adaway.
I plan to do a clean install of O and then hope to root with fastboot twrp to flash supersu.

gordonlw said:
quick question, are the steps the same for stock root 7.1.2? I've never installed twrp. I've fastbooted to it to root and that's it. I'm familiar with that as I've sideloaded all the ota security updates and the re-rooted.
my main question is su-hide required? I have never done it and have no reason to that I'm aware of. Seems all the guides I see involve su-hide and flashing kernels etc. I've never changed kernels since having the pixel. Really just want root for adaway.
I plan to do a clean install of O and then hope to root with fastboot twrp to flash supersu.
Click to expand...
Click to collapse
That's how I did it. I don't use suhide.

Does the -w in the .bat file format or wipe the data? I want a clean clean , o-fresh in the morning feeling kind of wipe

toknitup420 said:
That's how I did it. I don't use suhide.
Click to expand...
Click to collapse
Thanks! What I ended up doing:
Decided to try and unroot and take the ota. super-su full unroot would not work. so I fastbooted to the mod twrp and flashed UPDATE-unSU. I then took the ota. then fastbooted to mod twrp and flashed super-su. worked perfect!

Twrp and flashing a Rom

So I've done a lot of reading and there are multiple threads with steps that aren't exactly clear or contradict each other or are outdated. I just want clarification on what I believe are the steps to flash a custom rom (7.1.2 since I can wait for 8) on a brand new Pixel XL.
Setup phone to the point of enabling adb debugging and oem unlock
Fastboot unlock
Fastboot boot twrp RC1 img
Flash twrp RC2 zip in twrp
Reboot to installed twrp
Wipe system, data, caches
Flash ROM
Flash twrp again
Reboot to twrp
Flash gapps and root method (magisk working for 7.1.2 or should I be using supersu? Also which versions?)
Flash twrp again??
Boot to ROM then setup and use like normal
Should this give me custom ROM, root and twrp that I can boot directly to without a pc again? As long as I do twrp flashing after a ROM each time it'll stick? Also, I keep seeing things for setting a pin before initial twrp boot but without spending 4 days reading I can't find the reason for it. Should I be flashing vendor, bootloader and radio for the latest Nougat release BEFORE unlocking or can I do it through fastboot prior to unlocking?
Coming from Nexus 6P and that was my first run in with the bootloader, radio and vendors so I want to avoid issues for myself. Phone should be here tomorrow and want to get down to business right away lol.
Any and all information is greatly appreciated. If all of this is answered in a centralized area please point me to it and tell me I'm stupid for missing it.
Sent from my SM-N910P using Tapatalk
Found this over in PN thread. Is it accurate? Seems similar to my process.
https://forum.xda-developers.com/showthread.php?p=73846565

wgrant said:
Fastboot boot twrp RC1 img
Flash twrp RC2 zip in twrp
Reboot to installed twrp
Wipe system, data, caches
Flash ROM
Flash twrp again
Reboot to twrp
Flash gapps and root method (magisk working for 7.1.2 or should I be using supersu? Also which versions?)
Flash twrp again??
Boot to ROM then setup and use like normal
https://forum.xda-developers.com/showthread.php?p=73846565
Click to expand...
Click to collapse
Assuming the bootloader is already unlocked and disregarding the unlocking instruction, these instructions are dead on accurate. I personally dont use magisk, but maybe another user will chime in. For 7.1.2 id use supersu 2.82.
You dont have to flash twrp again after flashing gapps and supersu, but its a good practice to have.

noidea24 said:
Assuming the bootloader is already unlocked and disregarding the unlocking instruction, these instructions are dead on accurate. I personally dont use magisk, but maybe another user will chime in. For 7.1.2 id use supersu 2.82.
You dont have to flash twrp again after flashing gapps and supersu, but its a good practice to have.
Click to expand...
Click to collapse
Thank you very much. I'm about to unlock and go nuts on my phone. New phones are so fun to fiddle with!

if you want to use magisk you'll need to flash a custom kernel before you flash magisk. Also you'll need a modified magisk zip. Search around the thread you'll find one, the latest version I found was magisk v13.3.
Edit: Just found out magisk is officially support for pixel on version 14.1 Check out the magisk beta thread.

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?

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

OOS 5.1.0 Bootloop After Flashing Magisk

As the title says I am unable to boot after flashing Magisk (tried v16 and v15.3). It boots fine without magisk but of course no root and no custom recovery. Any help would be appreciated. Didn't have any problems on the previous stable build.

You need to first flash OOS 5.1 let it boot, then go to fastboot and flash twrp then go to twrp and flash magisk, only way to get root

hello, that's what I did and it worked well

this has happened here since 5.0.4

Try to use lastest blu-spark's TWRP, then flash 5.1 & Magisk without extra boot in the middle.

Things I noticed when upgrading:
A) The latest TWRP for dumpling appears to be broken. I get an error mounting /vendor when I use it. I switched to the previous version (20180309) and the error went away and everything seems to work.
B) You may very well have Xposed installed. If you do, there is an SDK bump between OOS 5.0.x and 5.1.x (26 -> 27). You'll need to disable this module either before you install the update (or assuming you already have) remove the module using something like Magisk Manager for Recovery to remove it (reboot to recovery, install module, run mm from terminal, follow prompts).
-Toucan

ToucanSam said:
Things I noticed when upgrading:
A) The latest TWRP for dumpling appears to be broken. I get an error mounting /vendor when I use it. I switched to the previous version (20180309) and the error went away and everything seems to work.
B) You may very well have Xposed installed. If you do, there is an SDK bump between OOS 5.0.x and 5.1.x (26 -> 27). You'll need to disable this module either before you install the update (or assuming you already have) remove the module using something like Magisk Manager for Recovery to remove it (reboot to recovery, install module, run mm from terminal, follow prompts).
-Toucan
Click to expand...
Click to collapse
It's not broken. The vendor error message is because it was recently updated to work better with Project treble, which uses a hidden partition for the vendor. You can simply ignore the error and it will work fine. Or if you flash a treble ROM, the error will then go away.

I just got the phone. Format it in recovery.
Flash latest blu spark twrp (v.8.73).
Flash the Oos ob06.
Reboot to system. Set the phone, instal apps from Play.
Reboot to Fastboot.
Reflash recovery.
Reboot to recovery.
Flash Magisk 15.3. Reboot to system. OK.
Updated Magisk with Magisk.

Hi, Can anyone help me. in my oneplus 5T after installing new rom it is working smooth but i can't upgrade to new updates. in recovery mode the files seems to be decrypted and cant find any folders where i copied the updation . instead new files are found and can't access and find any of the folders of my own. this happened after i input the security lock. i wiped the entire data and installed new roms still it seems so. somebody please help me to find a solution for this

Develop Bugs

welcome