Database Develop

[Q] General questions about ROMs and the rooting how-to

Hi, many thanks for the great and detailed how-to. However, I think it may lack some answers to a few important questions that people who come from other phones could ask. Until now, I've been used to rooting and flashing my Galaxy Nexus which appears to be rather different from the methods on this phone. Anyway here goes: I just got my Z3 Compact. I'm willing to give the stock UI a try, especially because it has some very nice features (noise removal on camera, STAMINA mode) and a clean enough look, however I need root and don't want to put up with some of the preinstalled apps. I can then either create my own pre-rooted image or flash a custom, stock-based ROM w/ root such as SLiM. Here are my questions:
Based on the how-to, if I want to install a custom ROM such as SLiM, at which step do I need to flash it? In particular, that ROM requires "root and recovery", does that really mean that I first have to root a stock ROM and install a new pre-rooted ROM + recovery, and only then flash SLiM from recovery, or can I install it during the various stages of the how-to?
I was used to TWRP recovery remaining on my Galaxy Nexus for pretty much all its life. I don't understand: why are there so many different recoveries for the Xperia phones and why do you apparently need to flash them so often? Can't you put one there and never touch it again? Why do they sometimes come with the ROM?
Why do some custom ROMs have requirements to be running a specific version of the firmware to be installed? Can't they just be flashed from recovery? Oh and btw, is there a difference between a ROM and a "firmware" as far as Xperia-specific vocabulary goes?
Putting those questions into words, I realize I may be missing something crucial about these phones that ties recovery, ROM and kernel together in a way I'm not used to. If there is any documentation about how these general concepts work on Sony phones, I'd be happy to read it!
Thanks in advance.

Answering myself, hoping it can be helpful to people who are new to the Z3C and wondering about the same questions:
SLiM is a complete ROM, it only requires "Root and Recovery" to mean that it must be flashed from recovery -- and recovery must be installed from root anyway.
If you want to install SLiM on your first root, you must follow the how-to down to the point where you've downgraded, rooted and installed XZDualRecovery. After that you're good to go, you can wipe everything (or not) and flash SLiM.
There aren't in fact that many recoveries. Basically, the CWM recovery and its derivatives (PhilZ Touch) and TWRP. Both have different UIs and a few different extras in the way they manage backups, but they really serve the same purpose.
And then, there are things like XZDualRecovery, which includes both standard recoveries and allows to choose between them. Why include both? I don't know -- it may be related to CM ROMs needing their own recovery or just user preference --. Anyway, I suppose what makes XZDualRecovery the standard on Z2+ Xperia phones is its ease of install and the fact that it works out of the box.
Now, you need to reflash XZDualRecovery after installing a new ROM. There's a part of it that resides in the system partition and you'll lose it when you flash a new ROM; that's a big difference from what I was used to on the GNex, and many custom ROMs already include the necessary files. Be sure to check that before you flash, though.
I was mistaken, no ROM comes with a "previous ROM" requirement. Some packages (debloat releases such as serajr's for example) require an already present and rooted ROM to be installed, as they don't contain the whole system + data. They are not complete ROMs and must be flashed onto an existing, rooted ROM of the same version.
There is no real difference between ROM and "firmware", the latter is mostly what Sony uses to describe their flashable tool format releases while the former is more often used to describe custom releases. As a consequence, you'll more often see Sony's stock .FTF files described as "firmwares", and custom flashable .zip files as "ROMs".
In the end, here is what I ended up doing yesterday to my new Orange FR Z3C:
Follow the how-to to:
install the PC drivers;
downgrade to 23.0.A.2.93 stock firmware;
root the phone;
install XZDualRecovery;
Download Pandemic's pre-rooted stock 5.1.1 rom (23.4.A.0.546), reboot to recovery and flash it;
Download serajr's debloated, pre-rooted system and flash it;
Download and flash RICDefeat just to be safe;
Download and flash/install the Xposed framework and serajr's Xperia Xposed, although right now I only use it for its ability to load custom icon packs.
Huge thanks to everyone involved in the development of these tools, apps and ROMs.

Need help with going back to OOS stable

Right now i am on Open Beta 16 and I am looking to go back to stable and install TWRP to install new custom roms. I have been MIA in the scene for a while now but I am so ready to start again. If someone could guide me on what TWRP to use and how to go back that would be appreciated. I also want to go to the F2fs system unless it is worse, i am not sure on that. Thanks
-kabrty

kabrty said:
Right now i am on Open Beta 16 and I am looking to go back to stable and install TWRP to install new custom roms. I have been MIA in the scene for a while now but I am so ready to start again. If someone could guide me on what TWRP to use and how to go back that would be appreciated. I also want to go to the F2fs system unless it is worse, i am not sure on that. Thanks
-kabrty
Click to expand...
Click to collapse
I assume you know the basics? If not.
https://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-how-to-unlock-bootloader-t3398733
Now you don't want to use the TWRP from that thread. @eng.stk is having the most updated TWRP and I personally did not face any issues with it yet.
https://forum.xda-developers.com/devdb/project/?id=15934#downloads
Now for root. I do recommend Magisk, why? I found it more user friendly and with the correct settings you can pass safety net which means you can play Pokémo GO and such with root. Note: Root is disabled by default if you go to Magisk manager you can enable this in the settings!
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
If you have any more questions feel free to ask.

That would be vdry easy to do. Just follow the steps carefully:
1. I guess you are having a locked bootloader. So first unlock it and install TWRP. To do these follow this thread: here
Instead of using twrp from the above page download it from here: here
2 go though several rom and kernel threads, read the maximum number of pages you can so get kind of idea about what other users are experiencing and figure out what would work best for you. I again insist read. Particularly go though the thread of the rom, kernel or mod or whatever you'd be flashing. You'd be happy to help yourself later.
3 last but surely not the least. Learn to use the search function here on xda. This would help you save your time. For example, all the links i have mentioned above are from oneplus 3 's xda section only. If you had searched efficiently you would have got everything right away.
have a ball

Thanks guys but I figured it out on my own. The real reason why i asked is back when i followed the scence more, there was a problem with twrp and Community builds.

Root Stable OOS 5.0.2 with Magisk?

I'm currently on a stable build of Oxygen OS 5.0.2 Oreo and I was thinking of rooting my phone using Magisk.Most of the guides that I've seen had users root using a nougat based version of OOS or they were on beta. I'll have to unlock the bootloader and flash TWRP but this is where the confusion comes in - Can I root a stable build of OOS? Will I have to switch to beta to root? Also, I'm a little scared about whether this DM-Verity issue will arise or not if I try to root or flash TWRP. So can someone please explain what that Issue really is and will it arise in my case? And if someone can just give me a guide on how to root it, I'll really appreciate it. And are there any known issues which arise after successfully rooting OOS 5.0.2?

No obstacles in rooting stable OOS and no problems should arise after doing it. You just need to make a backup of all your data, unlock bootloader, flash TWRP, flash Magisk and go.
If you trigger dm-verity, tyou have two choices - either ignore it on every reboot or follow a guide about removing it.

anshikohri said:
I'm currently on a stable build of Oxygen OS 5.0.2 Oreo and I was thinking of rooting my phone using Magisk.Most of the guides that I've seen had users root using a nougat based version of OOS or they were on beta. I'll have to unlock the bootloader and flash TWRP but this is where the confusion comes in - Can I root a stable build of OOS? Will I have to switch to beta to root? Also, I'm a little scared about whether this DM-Verity issue will arise or not if I try to root or flash TWRP. So can someone please explain what that Issue really is and will it arise in my case? And if someone can just give me a guide on how to root it, I'll really appreciate it. And are there any known issues which arise after successfully rooting OOS 5.0.2?
Click to expand...
Click to collapse
All things that you are mentioning show clearly that you didn't pay attention to all the basic info for rooting a 3/3T.
Why do u need a guide for Oreo, when you have a guide for nougat?
It's exactly the same method.
Also DM verity is just a warning, so why to be scared.
Maybe you should avoid doing something that you don't understand.
Unleashed by my rooted OP3T on 8.0

RASTAVIPER said:
All things that you are mentioning show clearly that you didn't pay attention to all the basic info for rooting a 3/3T.
Why do u need a guide for Oreo, when you have a guide for nougat?
It's exactly the same method.
Also DM verity is just a warning, so why to be scared.
Maybe you should avoid doing something that you don't understand.
Unleashed by my rooted OP3T on 8.0
Click to expand...
Click to collapse
Well I had a Redmi 2 before this and when I tried to root my lineage Os based on oreo with magisk using the same method I used with Nougat, i bricked my device. So that's why i was a little apprehensive. But thank you for your response.

przemcio510 said:
No obstacles in rooting stable OOS and no problems should arise after doing it. You just need to make a backup of all your data, unlock bootloader, flash TWRP, flash Magisk and go.
If you trigger dm-verity, tyou have two choices - either ignore it on every reboot or follow a guide about removing it.
Click to expand...
Click to collapse
Will I run into trouble with xposed or substratum on OOS?

anshikohri said:
Will I run into trouble with xposed or substratum on OOS?
Click to expand...
Click to collapse
No, if you use compatible modules and themes. I had no problems using both on OOS. Please note that if you install Xposed, you won't be able to use SafetyNet protected apps (Android Pay, Pokemon Go, Snapchat (you have to login before installing Xposed to make it work) etc.).

anshikohri said:
Well I had a Redmi 2 before this and when I tried to root my lineage Os based on oreo with magisk using the same method I used with Nougat, i bricked my device.
Click to expand...
Click to collapse
You aren't being specific enough when you say "same method". The general method is often similar. But you will virtually never use the exact same steps when rooting different Android builds (such as Nouget vs. Oreo). In particular, you always need to use updated versions of files for TWRP and Magisk. By definition, the root exploits will change between Android versions. So using old version Magisk is basically asking for a "soft brick". Not a real brick. It usually just means you need to use the correct version Magisk in order to recover. Or at worst, flash recovery image (or restore TWRP backup - which you should always have a backup of the stock ROM before rooting) then root with the proper files. Don't know anything about your old phone - but I'll guess this is what happened (which is a common enough scenario).
Similarly, you should also use the most current version TWRP. Older versions may sometimes work, depending on the situation. But Oreo (vs. Nougat) in particular, TWRP had to be updated to be compatible. Meaning you must use a Oreo-compatible version of TWRP to avoid problems. Short story, use current version TWRP to avoid problems.
Current versions are:
TWRP 3.2.1-0
Magisk v16.0
Also proceed with the knowledge that this device is very hard to brick. Just flashing TWRP and Magisk will not brick it (not a true brick anyway - a "soft" brick is easy to recover from as already described). Just make sure you are using Magisk for the OP3/3T (not some other device) and the risk is virtually zero. Even in the case of a brick, this device has an unbricking tool. Just be sure to take the following precautions:
- Make a TWRP backup of the stock ROM before you flash Magisk (always amazed at how many folks skip this!) or otherwise have the stock recovery image available in case anything happens. Basically always have a backup plan!
- Find the unbrick tool, and again have it available (at least bookmarked) in case you need it.
- Most importantly, read and understand all the steps and concepts before you begin. As another already mentioned, it seems your knowledge about some of the concepts is a bit lacking.
---------- Post added at 10:30 AM ---------- Previous post was at 10:06 AM ----------
anshikohri said:
Most of the guides that I've seen had users root using a nougat based version of OOS or they were on beta.
Click to expand...
Click to collapse
Beta or Stable doesn't matter. I don't know if I've ever seen a root guide specific to the Beta version, so I'm not even sure what you are talking about.
As far as the guides being for Nougat, I've already addressed that above. Basically, everything is the same, except the file versions (use updated TWRP, Magisk) so that is why nobody has bothered posting new guides for every OOS build.
anshikohri said:
Also, I'm a little scared about whether this DM-Verity issue will arise or not if I try to root or flash TWRP.
Click to expand...
Click to collapse
DM-verity is just a warning screen that appears when you reboot or power-on the phone. It will go away and continue to boot normally after 5 seconds, or just press the power button to dismiss the warning.
Once the phone has TWRP and rooted, you will have the DM-verity warning screen. If you like, you can flash a patched boot image, so you don't see the DM-verity warning screen on reboot/power-on.
You will also have a very similar (but separate) warning screen once the bootloader is unlocked. Unlike the DM-verity screen, the bootloader unlocked warning is impossible to be removed. The only way to remove it is to relock the bootloader, which I would strongly warn you not to do on a modified (TWRP and root) device! The bootloader unlock warning screen is just something you live with if you are rooted (just wait the 5 seconds or press the power button to skip it).
There is also the unlikely event that DM-verity will outright prevent the OS from booting. But this shouldn't happen just from flashing TWRP and Magisk (at least not if you've done it properly). Even if this happens, just restore your TWRP backup, or flash recovery image, and start over - checking what you did (cause you probably did something wrong).
anshikohri said:
And are there any known issues which arise after successfully rooting OOS 5.0.2?
Click to expand...
Click to collapse
This is so vague, as to make it hard to figure out what you are even asking.
In short, No.
Long answer: Some apps will not work with root, such as banking apps and Netflix. But the Magisk "Hide" feature should work to conceal root and make these apps work. It's a whole topic in itself, so read up in existing threads if this applies to you, and you want more info.
Other than that, there isn't anything with Magisk root that I would consider an "issue" and make me want to unroot.

redpoint73 said:
You aren't being specific enough when you say "same method". The general method is often similar. But you will virtually never use the exact same steps when rooting different Android builds (such as Nouget vs. Oreo). In particular, you always need to use updated versions of files for TWRP and Magisk. By definition, the root exploits will change between Android versions. So using old version Magisk is basically asking for a "soft brick". Not a real brick. It usually just means you need to use the correct version Magisk in order to recover. Or at worst, flash recovery image (or restore TWRP backup - which you should always have a backup of the stock ROM before rooting) then root with the proper files. Don't know anything about your old phone - but I'll guess this is what happened (which is a common enough scenario).
Similarly, you should also use the most current version TWRP. Older versions may sometimes work, depending on the situation. But Oreo (vs. Nougat) in particular, TWRP had to be updated to be compatible. Meaning you must use a Oreo-compatible version of TWRP to avoid problems. Short story, use current version TWRP to avoid problems.
Current versions are:
TWRP 3.2.1-0
Magisk v16.0
Also proceed with the knowledge that this device is very hard to brick. Just flashing TWRP and Magisk will not brick it (not a true brick anyway - a "soft" brick is easy to recover from as already described). Just make sure you are using Magisk for the OP3/3T (not some other device) and the risk is virtually zero. Even in the case of a brick, this device has an unbricking tool. Just be sure to take the following precautions:
- Make a TWRP backup of the stock ROM before you flash Magisk (always amazed at how many folks skip this!) or otherwise have the stock recovery image available in case anything happens. Basically always have a backup plan!
- Find the unbrick tool, and again have it available (at least bookmarked) in case you need it.
- Most importantly, read and understand all the steps and concepts before you begin. As another already mentioned, it seems your knowledge about some of the concepts is a bit lacking.
---------- Post added at 10:30 AM ---------- Previous post was at 10:06 AM ----------
Beta or Stable doesn't matter. I don't know if I've ever seen a root guide specific to the Beta version, so I'm not even sure what you are talking about.
As far as the guides being for Nougat, I've already addressed that above. Basically, everything is the same, except the file versions (use updated TWRP, Magisk) so that is why nobody has bothered posting new guides for every OOS build.
DM-verity is just a warning screen that appears when you reboot or power-on the phone. It will go away and continue to boot normally after 5 seconds, or just press the power button to dismiss the warning.
Once the phone has TWRP and rooted, you will have the DM-verity warning screen. If you like, you can flash a patched boot image, so you don't see the DM-verity warning screen on reboot/power-on.
You will also have a very similar (but separate) warning screen once the bootloader is unlocked. Unlike the DM-verity screen, the bootloader unlocked warning is impossible to be removed. The only way to remove it is to relock the bootloader, which I would strongly warn you not to do on a modified (TWRP and root) device! The bootloader unlock warning screen is just something you live with if you are rooted (just wait the 5 seconds or press the power button to skip it).
There is also the unlikely event that DM-verity will outright prevent the OS from booting. But this shouldn't happen just from flashing TWRP and Magisk (at least not if you've done it properly). Even if this happens, just restore your TWRP backup, or flash recovery image, and start over - checking what you did (cause you probably did something wrong).
This is so vague, as to make it hard to figure out what you are even asking.
In short, No.
Long answer: Some apps will not work with root, such as banking apps and Netflix. But the Magisk "Hide" feature should work to conceal root and make these apps work. It's a whole topic in itself, so read up in existing threads if this applies to you, and you want more info.
Other than that, there isn't anything with Magisk root that I would consider an "issue" and make me want to unroot.
Click to expand...
Click to collapse
That certainly cleared all my doubts and my inhibitions. Thank you so much for taking the time to address my questions.

anshikohri said:
That certainly cleared all my doubts and my inhibitions. Thank you so much for taking the time to address my questions.
Click to expand...
Click to collapse
You're certainly welcome. There is a "Thanks" button you can click for any posts that you found helpful, if you care to do so.
And a constructive criticism on forum etiquette: please don't quote a whole huge long post, like you did for my response. I know it's the default when responding to include a quote. But simply delete what isn't directly relevant (maybe keep a few lines, as appropriate) in the interest of keeping the forum free of clutter; and avoid folks have having to scroll down a whole screen/page which is just my post in duplicate. You can still edit the previous post, if you like.
Good luck on rooting. I'm sure it will go fine. Welcome to the dark side.

redpoint73 said:
And a constructive criticism on forum etiquette: please don't quote a whole huge long post, like you did for my response. I know it's the default when responding to include a quote. But simply delete what isn't directly relevant (maybe keep a few lines, as appropriate) in the interest of keeping the forum free of clutter; and avoid folks have having to scroll down a whole screen/page which is just my post in duplicate. You can still edit the previous post, if you like.
As you can see, I'm new to this, so forgive me. I'll keep this in mind the next time I post something and Thank You for your advise and your help.
Click to expand...
Click to collapse

redpoint73 said:
You aren't being specific enough when you say "same method". The general method is often similar. But you will virtually never use the exact same steps when rooting different Android builds (such as Nouget vs. Oreo). In particular, you always need to use updated versions of files for TWRP and Magisk. By definition, the root exploits will change between Android versions. So using old version Magisk is basically asking for a "soft brick". Not a real brick. It usually just means you need to use the correct version Magisk in order to recover. Or at worst, flash recovery image (or restore TWRP backup - which you should always have a backup of the stock ROM before rooting) then root with the proper files. Don't know anything about your old phone - but I'll guess this is what happened (which is a common enough scenario).
Similarly, you should also use the most current version TWRP. Older versions may sometimes work, depending on the situation. But Oreo (vs. Nougat) in particular, TWRP had to be updated to be compatible. Meaning you must use a Oreo-compatible version of TWRP to avoid problems. Short story, use current version TWRP to avoid problems.
Current versions are:
TWRP 3.2.1-0
Magisk v16.0
Also proceed with the knowledge that this device is very hard to brick. Just flashing TWRP and Magisk will not brick it (not a true brick anyway - a "soft" brick is easy to recover from as already described). Just make sure you are using Magisk for the OP3/3T (not some other device) and the risk is virtually zero. Even in the case of a brick, this device has an unbricking tool. Just be sure to take the following precautions:
- Make a TWRP backup of the stock ROM before you flash Magisk (always amazed at how many folks skip this!) or otherwise have the stock recovery image available in case anything happens. Basically always have a backup plan!
- Find the unbrick tool, and again have it available (at least bookmarked) in case you need it.
- Most importantly, read and understand all the steps and concepts before you begin. As another already mentioned, it seems your knowledge about some of the concepts is a bit lacking.
---------- Post added at 10:30 AM ---------- Previous post was at 10:06 AM ----------
Beta or Stable doesn't matter. I don't know if I've ever seen a root guide specific to the Beta version, so I'm not even sure what you are talking about.
As far as the guides being for Nougat, I've already addressed that above. Basically, everything is the same, except the file versions (use updated TWRP, Magisk) so that is why nobody has bothered posting new guides for every OOS build.
DM-verity is just a warning screen that appears when you reboot or power-on the phone. It will go away and continue to boot normally after 5 seconds, or just press the power button to dismiss the warning.
Once the phone has TWRP and rooted, you will have the DM-verity warning screen. If you like, you can flash a patched boot image, so you don't see the DM-verity warning screen on reboot/power-on.
You will also have a very similar (but separate) warning screen once the bootloader is unlocked. Unlike the DM-verity screen, the bootloader unlocked warning is impossible to be removed. The only way to remove it is to relock the bootloader, which I would strongly warn you not to do on a modified (TWRP and root) device! The bootloader unlock warning screen is just something you live with if you are rooted (just wait the 5 seconds or press the power button to skip it).
There is also the unlikely event that DM-verity will outright prevent the OS from booting. But this shouldn't happen just from flashing TWRP and Magisk (at least not if you've done it properly). Even if this happens, just restore your TWRP backup, or flash recovery image, and start over - checking what you did (cause you probably did something wrong).
This is so vague, as to make it hard to figure out what you are even asking.
In short, No.
Long answer: Some apps will not work with root, such as banking apps and Netflix. But the Magisk "Hide" feature should work to conceal root and make these apps work. It's a whole topic in itself, so read up in existing threads if this applies to you, and you want more info.
Other than that, there isn't anything with Magisk root that I would consider an "issue" and make me want to unroot.
Click to expand...
Click to collapse
Hi my oneplus 3t is on Oreo 5.0.2. I flashed twrp recovery nd super su root but when I restarted the phone it's stuck on black screen with white oneplus logo.what should I do now?my phone is going into twrp recovery
Should I flash stock oos 5.0.2 from twrp recovery? Pls guide

mannulko said:
Hi my oneplus 3t is on Oreo 5.0.2. I flashed twrp recovery nd super su root but when I restarted the phone it's stuck on black screen with white oneplus logo.what should I do now?my phone is going into twrp recovery
Should I flash stock oos 5.0.2 from twrp recovery? Pls guide
Click to expand...
Click to collapse
Please don't include page-long quotes in your post. For that matter, don't quote my posts at all, if you aren't going to refer to it, or read it.
And please only post your problem to one thread, per forum rules. It will be answered. Making more posts, will NOT get your question answered any faster. It will just confuse those trying to help you, and confuse you; jumping around to 4 different threads.

Help requested with updating Custom ROM.

Hello,
I currently have the following:
Phone: OnePlus 3T A3003
Recovery: TWRP 3.1.1-x | blu_spark v37
Rom: RR-N-v5.8.3-20170603-oneplus3-official
I installed all of this after hours of googling last year. I now want to upgrade but I am not finding many helping guides are upgrading (rather than installing from scratch).
I downloaded RR-O-v6.1.0-20180627-oneplus3-official and tried to install it via TWRP (after backing up and wiping some stuff). But I got the an error stating something along the lines of "this rom is for oneplus3/t" and your device is "". Googling lead me to believe I needed to update my recovery. So I downloaded TWRP-3.2.2-0oneplus3.img but I really have no idea if I should be installing this? Last time I installed the blu_spark variant but I have no idea why.
Anyway, my question is:
Given the above, please could someone give me a laymans guide to updating my Custom ROM and which things I should install and in which order.
Thank you!

Glendog1 said:
Hello,
I currently have the following:
Phone: OnePlus 3T A3003
Recovery: TWRP 3.1.1-x | blu_spark v37
Rom: RR-N-v5.8.3-20170603-oneplus3-official
I installed all of this after hours of googling last year. I now want to upgrade but I am not finding many helping guides are upgrading (rather than installing from scratch).
I downloaded RR-O-v6.1.0-20180627-oneplus3-official and tried to install it via TWRP (after backing up and wiping some stuff). But I got the an error stating something along the lines of "this rom is for oneplus3/t" and your device is "". Googling lead me to believe I needed to update my recovery. So I downloaded TWRP-3.2.2-0oneplus3.img but I really have no idea if I should be installing this? Last time I installed the blu_spark variant but I have no idea why.
Anyway, my question is:
Given the above, please could someone give me a laymans guide to updating my Custom ROM and which things I should install and in which order.
Thank you!
Click to expand...
Click to collapse
Clean Flash:
1) Latest Official TWRP (Can be done from within old TWRP)
2) Reboot Recovery to new TWRP
3) Wipe
4) Latest Firmware (OB29)
5) ROM
6) OpenGapps Arm64 8.1 Nano or Pico
7) Root Optional
Don't forget to Nandroid first, and it might be a good idea to remove any security measures on your current setup too. (Fingerprint/Pin/Pattern)
Queue up the zips for Firmware/ROM/Gapps and flash in that order together.

Thank you,
Some follow up questions:
* What should I be wiping during step 3.
* Should I install TWRP 3.2.2, does it matter that I currently have the blu_spark variant? (I don't even know what blu_spark means)
* I am just reading about firmware. I am assuming I need OB29 to work with RR-O-v6.1.0-20180627-oneplus3-official? Is that a simple process?

Glendog1 said:
Thank you,
Some follow up questions:
* What should I be wiping during step 3.
* Should I install TWRP 3.2.2, does it matter that I currently have the blu_spark variant? (I don't even know what blu_spark means)
* I am just reading about firmware. I am assuming I need OB29 to work with RR-O-v6.1.0-20180627-oneplus3-official? Is that a simple process?
Click to expand...
Click to collapse
Just follow the steps. The TWRP you download will be an .img file. In the TWRP Install menu press the button for Image to flash the .img file.
For step 3, from the Wipe menu just swipe to wipe.

DirkGently said:
Just follow the steps. The TWRP you download will be an .img file. In the TWRP Install menu press the button for Image to flash the .img file.
For step 3, from the Wipe menu just swipe to wipe.
Click to expand...
Click to collapse
Thank you, final question. I note you advised to remove security. I changed from 'Pin' to 'None' and gave me a warning about removing it which I agreed to. It still states my phone is encrypted however, and I still need to enter my PIN when restarting. Will this be a problem?
Thank you,

Glendog1 said:
Thank you, final question. I note you advised to remove security. I changed from 'Pin' to 'None' and gave me a warning about removing it which I agreed to. It still states my phone is encrypted however, and I still need to enter my PIN when restarting. Will this be a problem?
Thank you,
Click to expand...
Click to collapse
I believe removing your stored fingerprints removes the boot PIN. Don't stress if you can't do this, it's just an additional precaution.

DirkGently said:
I believe removing your stored fingerprints removes the boot PIN. Don't stress if you can't do this, it's just an additional precaution.
Click to expand...
Click to collapse
Pin/password and fingerprints are two different things. Fingerprints are just a convenient method of authenticating. Removing them does nothing for the actual security with is pin/password.
The reason for removing the lock screen password before taking a backup is that if you install a new ROM and set a password and then restore your older backup, you can't get past the lock screen password. So, remove the password before taking the backup and then you can restore it later and set a new password.
I find the better option is to not remove the password and then, if you need to restore the backup after having changed passwords, you can delete the passwords of the restored backup in TWRP from Advanced>Terminal with these commands:
Code:
cd /data/system
rm -f gatekeeper.* locksettings.*
Changing the pin/password to none doesn't wipe out the on-boot password. However, when setting up a new password and selecting to not set an on-boot password will remove the current on-boot password for some users, but not for others (it doesn't for me).
Sent from my OnePlus 3T using XDA Labs

Thanks guys.
I followed your instructions @DirkGently and it worked a charm.
What you recommend for rooting the device and is as simple as flashing a zip file like above?
Also, is the recovery on a separate partition? So if I mess around flashing firmware/rom/apps and mess up, I'll always be able to boot into the recovery partition and flash again?
Thanks,

Glendog1 said:
What you recommend for rooting the device and is as simple as flashing a zip file like above?
Click to expand...
Click to collapse
Magisk
Glendog1 said:
Also, is the recovery on a separate partition? So if I mess around flashing firmware/rom/apps and mess up, I'll always be able to boot into the recovery partition and flash again?
Click to expand...
Click to collapse
Yes and yes, but firmware may be tricky and messing up too much may render phone unusable. Messing with ROMs is fine though.

Thanks for the reply.
I note that on the Magisk page it states:
"If you plan to flash a custom kernel, flash it AFTER installing Magisk"
I have already installed a custom rom, will this be an issue?
Sorry for so many question. I get really nervous about this stuff!

Glendog1 said:
I have already installed a custom rom, will this be an issue?
Click to expand...
Click to collapse
That's ok of you asking questions, that's what this forum is about.
You should have got no problems if you're running a kernel shipped with custom ROM. Custom kernel is like EX, Mady's Xtended, Franco and so on.

Glendog1 said:
Thanks for the reply.
I note that on the Magisk page it states:
"If you plan to flash a custom kernel, flash it AFTER installing Magisk"
I have already installed a custom rom, will this be an issue?
Sorry for so many question. I get really nervous about this stuff!
Click to expand...
Click to collapse
You don't need to worry about Kernel stuff. RR already includes Caesium Kernel. You chose a good ROM by the way!
Here's a little information about Firmware. The OP3 and OP3T have unified builds. This means that in some cases the same Custom ROM can be used on both. There is some device specific software though so this has to be separated out and treated as independent from the ROM. This is what we refer to as Firmware. When Oneplus release new builds they include the updated Firmware in their Official ROM. If you look at the Firmware thread i linked you to, you'll see that kamilmirza takes the Firmware from the Official OOS builds and makes them available as flashable .zip files that we can use on Custom ROMs. Bookmark his Thread for future use.
There is no need to stress about always being on the latest Firmware for your Custom ROM, just ensure it is the Firmware intended for your device. The version you flashed earlier will probably do you for a while. At the same time, if you do always want to be on the latest, there's no reason not to. There's little to be gained by it though. If you're following the RR thread you'll probably see people mention it when the ROM requires a new Firmware. Again, don't stress about it.
As far as flashing Firmware, you can do it any time. You can do it before flashing an updated build of your ROM, or on it's own in a separate visit to Recovery. It's not particular either way. I would stick with the Open Beta Firmware, which people usually abbreviate to OBXX, i.e OB29. Just remember what you flashed so that you know which version you are using.
Now that you're rocking your Custom ROM you're next questions will be about updating it. This can be done easily and safely by Dirty Flashing. I've done dozens of updated builds since my last clean flash and everything has gone perfectly every single time.
Dirty Flash:
1) Download new ROM build (and Firmware if applicable) to Internal Storage.
2) Boot into Recovery
3) Nandroid Backup
4) From Install Menu, flash Firmware (if applicable), and ROM.
5) Wipe Dalvik & Cache when prompted. (BillGoss will tell you it's not necessary. It doesn't hurt either way, so up to you!)
6) Reboot phone.
For a Dirty Flash, you do not need to use the 'Wipe' Menu at all.
I always take a new Nandroid before flashing an updated build. I will have had a whole week on the previous build so i know i'm not backing up a bug and the backup will be as recent as possible if a problem occurs. Once i boot back into the phone i delete the old Backup. The new one is there if i need it. Always have that one recent Backup, just in case. As i've said, RR is great and i'm yet to run into a problem with it. From now on you can Dirty Flash the updated weekly builds with little to worry about and with a Backup to fall back to if anything goes wrong.
I don't mention Magisk because i don't use it, and i don't advise others use it. Unless you need Root access for something specific, don't bother. Half the threads on XDA are about problems with Magisk. Avoid the added complication if you can. Now this statement will trigger the Magisk fans, but nobody has ever had a bug or failure with something that they did not flash in the first place. Keep it as simple as possible.

Looking to flash OK Pie on P9 Any help would be appreciated.

Hi guys, like the title says. I'd like to flash OK Pie onto my old but still working P9 but after so, so much time i have forgotten everything I did to my phone to get to where I currently am. I've been searching for specifics to my situation but the guide to go from EMUI 8 to OK Pie is complicated enough as it is. If I have to factor in the "back to stock" procedure etc I think my brain would explode xD
So I'm looking for any links, guides, personal help or WHATEVER may help me at least get to chinese OREO 9I think I'm capable of taking it from there)
My current setup:
EVA-L09
Build number: EVA-L09C432B378
EMUI version: 5.0
Android: 7.0
My phone is from Latin America, So IIRC I unbranded it, changed it to cust 432 and flashed the latest (stock) firmware which at the time was B378.
I also have TWRP (the latest one) installed. If I got it right, I THINK I need to go back to stock recovery, flash the latest FW and go to Chinese OREO from there before trying to flash OK Pie, right?
Could somebody please be so kind as to either help me or at least point me to a thread/guide made for idiots such as myself xD that can walk me through the steps of going from my FW to stock recovery and stock latest FW?
I'll manage to get to oreo and custom after that.
I appreciate your help in advance.
Thanks.
EDIT: Forgot to mention that yes. I kept my unlock code so thats no problem
Thanks again!

SideSkroll said:
Hi guys, like the title says. I'd like to flash OK Pie onto my old but still working P9 but after so, so much time i have forgotten everything I did to my phone to get to where I currently am. I've been searching for specifics to my situation but the guide to go from EMUI 8 to OK Pie is complicated enough as it is. If I have to factor in the "back to stock" procedure etc I think my brain would explode xD
So I'm looking for any links, guides, personal help or WHATEVER may help me at least get to chinese OREO 9I think I'm capable of taking it from there)
My current setup:
EVA-L09
Build number: EVA-L09C432B378
EMUI version: 5.0
Android: 7.0
My phone is from Latin America, So IIRC I unbranded it, changed it to cust 432 and flashed the latest (stock) firmware which at the time was B378.
I also have TWRP (the latest one) installed. If I got it right, I THINK I need to go back to stock recovery, flash the latest FW and go to Chinese OREO from there before trying to flash OK Pie, right?
Could somebody please be so kind as to either help me or at least point me to a thread/guide made for idiots such as myself xD that can walk me through the steps of going from my FW to stock recovery and stock latest FW?
I'll manage to get to oreo and custom after that.
I appreciate your help in advance.
Thanks.
EDIT: Forgot to mention that yes. I kept my unlock code so thats no problem
Thanks again!
Click to expand...
Click to collapse
General link for Open Kirin ROMs
https://openkirin.net/user_guide/openkirin-rom-installation-instructions/
P9 thread for OK ROMs (under the P9 ROMs, Kernels... collection)
https://forum.xda-developers.com/p9/development/roms-openkirin-aosp-collection-t3828806
In short:
1) You must rebrand and update your L09c432 Nougat to AL10c00 Oreo, it is PRECISELY explained in the OP posts (mainly the post #2, but read #1 - #5 to get better picture) in the corresponding thread:
https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849
2) Once you will be on EVA-AL10c00b540 Oreo, you have to follow the OK installation guide from the first link.
You will have to install OK Omni Pie for Android 8, not for Android 9 (there is no stock Pie for P9)
If you search for Pie in the given two XDA threads (Search box at top- right on any XDA page), you will find that many people have undergone (and some returned back from OK Pie to stock Oreo) with no problems - but it is important to carefully follow the guides, first for rebranding and installing the Chinese stock Oreo, then to install OK ROM EXACTLY as described on their site (common guide for all OK ROMs and for all Huawei phones when already updated to the stock Oreo)

zgfg said:
General link for Open Kirin ROMs
https://openkirin.net/user_guide/openkirin-rom-installation-instructions/
P9 thread for OK ROMs (under the P9 ROMs, Kernels... collection)
https://forum.xda-developers.com/p9/development/roms-openkirin-aosp-collection-t3828806
In short:
1) You must rebrand and update your L09c432 Nougat to AL10c00 Oreo, it is PRECISELY explained in the OP posts (mainly the post #2, but read #1 - #5 to get better picture) in the corresponding thread:
https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849
2) Once you will be on EVA-AL10c00b540 Oreo, you have to follow the OK installation guide from the first link.
You will have to install OK Omni Pie for Android 8, not for Android 9 (there is no stock Pie for P9)
If you search for Pie in the given two XDA threads (Search box at top- right on any XDA page), you will find that many people have undergone (and some returned back from OK Pie to stock Oreo) with no problems - but it is important to carefully follow the guides, first for rebranding and installing the Chinese stock Oreo, then to install OK ROM EXACTLY as described on their site (common guide for all OK ROMs and for all Huawei phones when already updated to the stock Oreo)
Click to expand...
Click to collapse
Hi, thanks for replying. I'm aware of the PROCEDURE not so sure about the "how to".
Thats why I posted. Your post basically told me what I already knew (and talked about in my post)
What I'm looking for is help going from my current TWRP/STOCK/ROOTED FW. Back to full stock so I can start updating the ORIGINAL FW. I can't find any info on how to go back to stock recovery for instance. Do I need a specific recovery for the FW I'm running? Is it generic? Where do I find it? How do I flash it? Where do I get the stock firmware? (Huawei firmaware finder?) Which one do I flash? Does flashing the stock firmware automatically flashes the stock recovery? Things like that. I appreciate you trying to help but I already read and knew the things you linked to. My issue is, like I said: going back to stock before I can follow any guide to go up to oreo.
Thanks anyway!

SideSkroll said:
Hi, thanks for replying. I'm aware of the PROCEDURE not so sure about the "how to".
Thats why I posted. Your post basically told me what I already knew (and talked about in my post)
What I'm looking for is help going from my current TWRP/STOCK/ROOTED FW. Back to full stock so I can start updating the ORIGINAL FW. I can't find any info on how to go back to stock recovery for instance. Do I need a specific recovery for the FW I'm running? Is it generic? Where do I find it? How do I flash it? Where do I get the stock firmware? (Huawei firmaware finder?) Which one do I flash? Does flashing the stock firmware automatically flashes the stock recovery? Things like that. I appreciate you trying to help but I already read and knew the things you linked to. My issue is, like I said: going back to stock before I can follow any guide to go up to oreo.
Thanks anyway!
Click to expand...
Click to collapse
If rooted by Magisk, there is Uninstall option in Magisk Manager, it will unroot.
Similarly SuperSU had an Unroot/Unistall option.
In both cases you can flaslh back the stock Boot partition but it is cleaner to unroot by using their Uninstall options.
From TWRP or Fastboot you have to flash stock Recovery (corresponding to your current stock Nougat firmware) to revert back from TWRP
Generally, if you download from FirmwareFinder update.zip corresponding to your current stock Nougat (must be from FullOTA-MF or FullOTA-MF-PV), unzip, then by using Huawei Update Extractor, you can extract Boot.img and Recovery.img that you can flash then from Fastboot or from TWRP to go back to stock Boot and to stock Recovery
Once you go back to stock Boot and Recovery, you can boot to eRecovery (switch off, connect to charger, keep pressing Vol+ and boot by Pow) and choose Download latest firmware and recovery
----
But in fact, since you already have TWRP, use the HWOTA method from this post to update to c432b504 or b505:
https://forum.xda-developers.com/showpost.php?p=75787151&postcount=2
You can do the same with HWOTA7 from the corresponding thread I gave you (before you will go to rebrand to AL10c00b399).
In both cases, you have to download three update*.zip files for eg L09c432b504 (must be FullOTA-MF), rename one or two of them as described in the OP posts (be careful, some people have Windows 10 that hides zip extension and they wrongly rename files to have double zip extension and then HWOTA/HWOTA7 scripts cannot find the file and fail to flash resulting with half-brick), put them to DLOAD file on the SD card and follow the guides

zgfg said:
If rooted by Magisk, there is Uninstall option in Magisk Manager, it will unroot.
Similarly SuperSU had an Unroot/Unistall option.
In both cases you can flaslh back the stock Boot partition but it is cleaner to unroot by using their Uninstall options.
From TWRP or Fastboot you have to flash stock Recovery (corresponding to your current stock Nougat firmware) to revert back from TWRP
Generally, if you download from FirmwareFinder update.zip corresponding to your current stock Nougat (must be from FullOTA-MF or FullOTA-MF-PV), unzip, then by using Huawei Update Extractor, you can extract Boot.img and Recovery.img that you can flash then from Fastboot or from TWRP to go back to stock Boot and to stock Recovery
Once you go back to stock Boot and Recovery, you can boot to eRecovery (switch off, connect to charger, keep pressing Vol+ and boot by Pow) and choose Download latest firmware and recovery
----
But in fact, since you already have TWRP, use the HWOTA method from this post to update to c432b504 or b505:
https://forum.xda-developers.com/showpost.php?p=75787151&postcount=2
You can do the same with HWOTA7 from the corresponding thread I gave you (before you will go to rebrand to AL10c00b399).
In both cases, you have to download three update*.zip files for eg L09c432b504 (must be FullOTA-MF), rename one or two of them as described in the OP posts (be careful, some people have Windows 10 that hides zip extension and they wrongly rename files to have double zip extension and then HWOTA/HWOTA7 scripts cannot find the file and fail to flash resulting with half-brick), put them to DLOAD file on the SD card and follow the guides
Click to expand...
Click to collapse
Thank you. Thats exactly what I was looking for. I really appreciateyour help.
Btw, no one should have the "hide extensions for known file types" checkbox marked...
Edit: Should I flash the same FW version Im currently using and then update regularly? To prevent any issues? (Cause i noticed there are some rules as to the version jumps that can be made flashing like this...

SideSkroll said:
....Should I flash the same FW version Im currently using and then update regularly? To prevent any issues? (Cause i noticed there are some rules as to the version jumps that can be made flashing like this...
Click to expand...
Click to collapse
It must be the same model and cust, c432, but safer if you also apply the same build number (b387 ?)
Once you are back on stock you should start receiving OTA updates (have WiFi and a valid SIM card). Give it some time but check also manually from Settings / System updates.
As mentioned in my previous post, you can also use eRecovery / Install latest fw and recovery (if OTA coming slow), and there is a similar option in HiSuite. You will probably not need to use HWOTA or HWOTA7 to jump from clean stock b386 up to b50x
SideSkroll said:
Thats exactly what I was looking for...
Click to expand...
Click to collapse
Did you go for OK Pie (or you stayed on Nougat, or in between on stock Oreo b540), was it Okay?

zgfg said:
It must be the same model and cust, c432, but safer if you also apply the same build number (b387 ?)
Once you are back on stock you should start receiving OTA updates (have WiFi and a valid SIM card). Give it some time but check also manually from Settings / System updates.
As mentioned in my previous post, you can also use eRecovery / Install latest fw and recovery (if OTA coming slow), and there is a similar option in HiSuite. You will probably not need to use HWOTA or HWOTA7 to jump from clean stock b386 up to b50x
Did you go for OK Pie (or you stayed on Nougat, or in between on stock Oreo b540), was it Okay?
Click to expand...
Click to collapse
Hi again. First of all I would like to thank you agaib for your help. You made the process so much sinpler and quixk for me and I do apprexiate it.
Second, I updated to the latest "original" fw for my c432 phone OTA but then had to modify the HWOTA7 procesa so I could dl and install the latest/latest fw (because it wouldnt even register when searching for it) I used huawei fw finder to verify it and dl.
After that I went to chinese Oreo, flashed the network fixes and installed a TINY OTA update which fixed some sexurity issues apparently (thankfully it went Ok cause I THINK flashing OTA in a "converted" phone is a big nono?)
Anyways, I ended up on omni pie (the latest beta whixh is 5.2 I believe) as going AOSP was the whole point of this endeavor.
So far I'm LOVING it. Its such a refreshing thing not having to deal with all the bs OEMs bake into their roms... But Im experiencing a couple of issues as well. Not sure if its the rom, my phone or the android version (particularly my issue with battery life since I was having issues with the duration way before I updates, actually that was one of my motivations for updating since I read that pie had better battery management)
Anyway, my issues are as follow. Hope you can help (once again)
Battery life SUCKS (like really, it went from bad to terrible... Not sure if stock oreo would make it better, or perhaps omni pie needs some optimizations?)
The camera (huawei one, not sure about the aosp) has issues. Multiple issues. The biggest one being that if I try to go from back to front camera the app locks in a black screen and I have to go into the app, delete data, reboot the phone and relaunch it (and that doesnt fix it everytime)
The last issue is with pop messages from apps and/or settings. Sometimes, when installing and app and/or changing aome setting a white popup shows up with ONLY an OK option. I cant read anything on the popup. Everything is white. Not sure if its an issue with the theme (I changed from default to "hell" or something like that) but it is VERY annoying not knowing what youre agreeing to.
Last but not least I have a question about the stock rexovery, factory reset and flashing new versions of omni (if and wheb they come out)
In one of the steps for flashing omni the guide asks to perfomr a factory reset from the stock rom. Thing is, it doesnt work. I mean, when I confirm the factory reset the process starts and approximately at 15% an exclamation sign appears and the process percentage stops working. I can reboot the system and everything works fine (using the phone to post this actually) but Im left with that feeling of not knowing why something failed... You know what I mean? Is that nornal?(the failure to factory reset, not the feeling ) also, does factory wiping the phone removes root access? Or does it only renove magisk manager?
Also, if I ever wabt to update the rom (not change it mind you, but flash the next beta or stable or whatever they come up with) do I need to flash the stock recovery again? (Currently rooted with magisk) or is it a separate partition? (Sinxe I had to modify the ramdisk and not flash a custom recovery) also, will I need to do the whoooole thing again? (Backup everything, restore tk factory etc etc) or is it just like with lineage for exanple where you could flash and updatr and keep your data untouched?
Thanks for EVERYTHING my friend. And I hope you can answer my questions (particularly the ones about battery life and thebfactory reset issue since Im planning on doing one last factory reset before settling with the rom. Just waiting for my new micro sd. The one that will stay in the phone)
Sorry for the typos. Writing this huge post on a phone is a PITA.

SideSkroll said:
Hi again. First of all I would like to thank you agaib for your help. You made the process so much sinpler and quixk for me and I do apprexiate it.
Second, I updated to the latest "original" fw for my c432 phone OTA but then had to modify the HWOTA7 procesa so I could dl and install the latest/latest fw (because it wouldnt even register when searching for it) I used huawei fw finder to verify it and dl.
After that I went to chinese Oreo, flashed the network fixes and installed a TINY OTA update which fixed some sexurity issues apparently (thankfully it went Ok cause I THINK flashing OTA in a "converted" phone is a big nono?)
Anyways, I ended up on omni pie (the latest beta whixh is 5.2 I believe) as going AOSP was the whole point of this endeavor.
So far I'm LOVING it. Its such a refreshing thing not having to deal with all the bs OEMs bake into their roms... But Im experiencing a couple of issues as well. Not sure if its the rom, my phone or the android version (particularly my issue with battery life since I was having issues with the duration way before I updates, actually that was one of my motivations for updating since I read that pie had better battery management)
Anyway, my issues are as follow. Hope you can help (once again)
Battery life SUCKS (like really, it went from bad to terrible... Not sure if stock oreo would make it better, or perhaps omni pie needs some optimizations?)
The camera (huawei one, not sure about the aosp) has issues. Multiple issues. The biggest one being that if I try to go from back to front camera the app locks in a black screen and I have to go into the app, delete data, reboot the phone and relaunch it (and that doesnt fix it everytime)
The last issue is with pop messages from apps and/or settings. Sometimes, when installing and app and/or changing aome setting a white popup shows up with ONLY an OK option. I cant read anything on the popup. Everything is white. Not sure if its an issue with the theme (I changed from default to "hell" or something like that) but it is VERY annoying not knowing what youre agreeing to.
Last but not least I have a question about the stock rexovery, factory reset and flashing new versions of omni (if and wheb they come out)
In one of the steps for flashing omni the guide asks to perfomr a factory reset from the stock rom. Thing is, it doesnt work. I mean, when I confirm the factory reset the process starts and approximately at 15% an exclamation sign appears and the process percentage stops working. I can reboot the system and everything works fine (using the phone to post this actually) but Im left with that feeling of not knowing why something failed... You know what I mean? Is that nornal?(the failure to factory reset, not the feeling ) also, does factory wiping the phone removes root access? Or does it only renove magisk manager?
Also, if I ever wabt to update the rom (not change it mind you, but flash the next beta or stable or whatever they come up with) do I need to flash the stock recovery again? (Currently rooted with magisk) or is it a separate partition? (Sinxe I had to modify the ramdisk and not flash a custom recovery) also, will I need to do the whoooole thing again? (Backup everything, restore tk factory etc etc) or is it just like with lineage for exanple where you could flash and updatr and keep your data untouched?
Thanks for EVERYTHING my friend. And I hope you can answer my questions (particularly the ones about battery life and thebfactory reset issue since Im planning on doing one last factory reset before settling with the rom. Just waiting for my new micro sd. The one that will stay in the phone)
Sorry for the typos. Writing this huge post on a phone is a PITA.
Click to expand...
Click to collapse
This small OTA bringing Patch02 over b540 installs even over TWRP (but that was not the case for OTA from eg b535 to b540)
Cannot discuss/compare battery for Omni Pie, since not using Omni
Problem with Camera app does not show on stock Oreo. Even if the app was somehow ported from Huawei, there are maybe problems with integration to Omni.
Various Huawei/Mate models come with different cameras, but there is only one OK Omni ROM (with one Camera app) given to work on all Huawei/Mate models
Btw, somebody else also complained about issues with Camera (and GPS) and decided to go back to stock Oreo.
Similarly, issues you described about black notifications or so must be related to the custom ROM, theme or so.
As a general rule:
- for installing OK ROM, you flash System partition, and nothing else
- you also wipe Data partitiom (containing all your installed apps, incl Magisk Manager, also containing your user settings)
It does not affect any other partition.
Therefore, changes given by NW patch persist - without, you will have (also in that OK ROMs) problems with SIM card(s) and connecting to the network
Also, Magisk, which was flashed to Ramdisk, persists. You must only install Magisk Manager again, because it is user apo, installed to Data partition that was wiped
You must check on the OK side how they advice installing the updates of OK ROMs
(It is questionable if they will get updates any more, since OK team switched to development of ROMs which install over the stock Pie, whereas on P9 you have no stock Pie - only Oreo, and most likely, we will never see stock Pie for P9.
Just check when OK team released last ROM for stock Oreo, and compare with their releases of OK ROMs for stock Pie:
https://openkirin.net/download/
Hence IMO, for updating the OK ROM (if/when it comes), you will again just need to flash its System and to wipe Data (and then to reinstall user apps like Magisk Manager).
Hopefully, you can backup and restore some apps and settings by Titanium.
Whether you don't need to wipe Data for such update - check from the OK support.
On the Open Kirin site you will find Support pages (Faq, HowTo) and also a link to the live Telegram channel