Develop Bugs

[Q] Navigation keeps waiting for my location

I have been jumping from one rom to the other for quite a few days now and recently I noticed that my navigation does work anymore
I am currently on Liquid Smooth but have not been able to get this to work on many other ROMs like PA 2.55/ PK 1.40 or Task & Ktoonsez.
I have flashed the latest gapps. I also make sure I do a clean install every time I flash a new rom (wide data/factory, cache, dalvik and then I also did a format /system and format /data).
For some reason, apps like Weather, that need to find my location , are able to get it right and show me correct location results.
Could someone please help ?
_ND_

This might help:
http://forum.xda-developers.com/showthread.php?t=1881660

bsam55 said:
This might help:
http://forum.xda-developers.com/showthread.php?t=1881660
Click to expand...
Click to collapse
thanks, I will try and gvet back

fixed the issue by doing the following -
new titanium backup > Boot into recovery > wipe everything (including format /system) > restore stock / flash stock > factory reset > flash new ROM again > use titanium to get back to normal !
thank you for the responses !

Can't install this package on top of incompatible data

Hello,
I am getting following error when i try to flash a ROM from TWRP 2.7.1 recovery. S3 is on ND8 and just rooted.
"Can't install this package on top of incompatible data. Please try another package or run a factory reset"
I tried to root it again so not sure what is going on. SuperSU working fine!
I couldn't really find any info about this so had to post new thread.
Any help will be appreciated
Thank you

rrrikin said:
Hello,
I am getting following error when i try to flash a ROM from TWRP 2.7.1 recovery. S3 is on ND8 and just rooted.
"Can't install this package on top of incompatible data. Please try another package or run a factory reset"
I tried to root it again so not sure what is going on. SuperSU working fine!
I couldn't really find any info about this so had to post new thread.
Any help will be appreciated
Thank you
Click to expand...
Click to collapse
Use Philz Recovery. It is the only Recovery that hasn't had any problems with ND8.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

bilgerryan said:
Use Philz Recovery. It is the only Recovery that hasn't had any problems with ND8.
Click to expand...
Click to collapse
I just tried the Philz recovery and same thing ;(

rrrikin said:
I just tried the Philz recovery and same thing ;(
Click to expand...
Click to collapse
Need more info... What is the zip? I've never seen that error... Can you get a pic of it?

rrrikin said:
I just tried the Philz recovery and same thing ;(
Click to expand...
Click to collapse
are you trying to dirty flash? in TWRP did you try doing a factory reset then flashing the rom? In Philz did you use the second Wipe data flash new rom option, before trying to flash the ROM?

Same here
Not sure what is happening but Im getting the same error. I do have root, but not an insecure image, wondering if that might even matter

tomudei said:
Not sure what is happening but Im getting the same error. I do have root, but not an insecure image, wondering if that might even matter
Click to expand...
Click to collapse
Flash the Permissive stock kernel.
My ROM: WICKED X

Thanks for the tip, I'll try it!

In my mobile also while flashing cm11 in cwm recovery, i got the same dialogue 'can't install the package on top of incompatible data. Try another package or factory rest'. What should I do?

Sameer_br said:
In my mobile also while flashing cm11 in cwm recovery, i got the same dialogue 'can't install the package on top of incompatible data. Try another package or factory rest'. What should I do?
Click to expand...
Click to collapse
If you're flashing a rom from a different carrier or a different rom from the one you have, then do the factory reset. You have to wipe data anyways. Also cwm sucks, use philz or twrp.

I've now installed twrp

thx
madbat99 said:
If you're flashing a rom from a different carrier or a different rom from the one you have, then do the factory reset. You have to wipe data anyways. Also cwm sucks, use philz or twrp.
Click to expand...
Click to collapse
factory reset was helpfull

rrrikin said:
Hello,
I am getting following error when i try to flash a ROM from TWRP 2.7.1 recovery. S3 is on ND8 and just rooted.
"Can't install this package on top of incompatible data. Please try another package or run a factory reset"
I tried to root it again so not sure what is going on. SuperSU working fine!
I couldn't really find any info about this so had to post new thread.
Any help will be appreciated
Thank you
Click to expand...
Click to collapse
I've figured out how to get around this error.
So I've tried updating my version of cyanogenmod from one nightly to another and I get the same problem as you "can't install package on top of incompatible data. Please try another package or run a factory reset" and I didn't want to reset my phone every day an update came out so I decided to test something and it worked.
So here's how to do it:
1. Backup System and Data with twrp (to internal, micro sd, or usb otg)
2. Wipe System, Data, cache, dalvik cache with twrps advance wipe ( wipe/advance wipe
3. Flash the update.
4. Now flash things from what you had had on the system before (EG: Google apps, SuperSU)
5. Restore Data from the backup from before and wipe the cache and dalvik cache
This worked for me and hopefully for you. So this is a work around for this problem but I don't know how to actually fix the "bug".
P.S I've only tested it on twrp so I don't know if you can do this with other recoverys

hi. trying to flash a CM build to a samsung galaxy note 10.1 2014. I get the "can't install package on top of incompatible data. Please try another package or run a factory reset" error. I saw here to try a factory reset before flashing. did that, then flashed (which seemed go really fast - a few seconds). now, after reboot, I get a blank screen. I backed up the system I had, so I think I can get back to working. but why didn't flashing CM work? any ideas?

I had this problem as well.
Solution was to "format data" in the advanced setting in TWRP. I couldn't find a solution in Cyanogenmod recovery.
After that the rom flashed and now it's all working fine.

chaun said:
I had this problem as well.
Solution was to "format data" in the advanced setting in TWRP. I couldn't find a solution in Cyanogenmod recovery.
After that the rom flashed and now it's all working fine.
Click to expand...
Click to collapse
I don't know about Cyangenmod but I overcame this issue in PhilZ by running "Clean to install new ROM" in the wipe menu.

I wiped the whole internal storage with the advanced wipe options of TWRP and was able install Cyangenmod afterwards.

Codisimus said:
I don't know about Cyangenmod but I overcame this issue in PhilZ by running "Clean to install new ROM" in the wipe menu.
Click to expand...
Click to collapse
Thxs it's the solution

^^^^this

Same error on my A700FD running TWRP. Tried resetting /data still says same, tried clearing cache. Tried philosophy recovery too. Same issue. Never seen this before.

CM13 not booting

After flashing TWRP with Odin, I boot into recovery and wipe the dalvik cache. I then go to install the CM13 zip file, and it works. I wipe Dalvik again and reboot in the os. This is where it just shows the CM boot screen infinitely. Nothing else. What is up. I am using the latest TWRP and CM13 release.

Try this:
1. Wipe cache, dalvic cache, data, system
2. Install CM13 again, along with your gapps(google apps if you didn't know, custom ROMs never come with them, optional)
3. Boot it, it should work
You cannot switch ROMs without wiping data. Bad things happen.
You must clean flash when:
1. Switching between a stock ROM to a custom ROM
2. Downgrading Android versions (5.1 to 5.0)
3. Switching custom ROMs (I.E. CM13 to AICP)
4. When the ROM's thread warns to (switching keys)
5. Switching between nightly builds and stable.
When you're updating nightlies, you shouldn't have to though.

RDChase said:
Try this:
1. Wipe cache, dalvic cache, data, system
2. Install CM13 again, along with your gapps(google apps if you didn't know, custom ROMs never come with them, optional)
3. Boot it, it should work
You cannot switch ROMs without wiping data. Bad things happen.
You must clean flash when:
1. Switching between a stock ROM to a custom ROM
2. Downgrading Android versions (5.1 to 5.0)
3. Switching custom ROMs (I.E. CM13 to AICP)
4. When the ROM's thread warns to (switching keys)
5. Switching between nightly builds and stable.
When you're updating nightlies, you shouldn't have to though.
Click to expand...
Click to collapse
Just did it, it still seems to be booting like it previously was. Wiped cache, dalvic, data, and system and then installed CM13 and gapps. Still booting as I write this.

Since that failed, check your download, make sure nothings bad. If its bad, redownload, if not, idk.
If you post your recovery logs, or what the console says, that will help me figure out what's going on.
Also, is your phone the triband model (l710t)?
Are you flashing anything else at the same time?
The more info you give, the better.

RDChase said:
Since that failed, check your download, make sure nothings bad. If its bad, redownload, if not, idk.
If you post your recovery logs, or what the console says, that will help me figure out what's going on.
Also, is your phone the triband model (l710t)?
Are you flashing anything else at the same time?
The more info you give, the better.
Click to expand...
Click to collapse
I've kind of given up at this point. Even CM12 doesn't work. The only thing that seems to work is the stock rom. My phone is the regular SPH-L710 model. I didn't even know the L710t was a thing.

I have the same problem, and sometimes it boot in the system setup mode, but the sensor is not working, i can turn on airplane mode, reboot or power off, and sensor works, what happend i dont know((

ovil101 said:
After flashing TWRP with Odin, I boot into recovery and wipe the dalvik cache. I then go to install the CM13 zip file, and it works. I wipe Dalvik again and reboot in the os. This is where it just shows the CM boot screen infinitely. Nothing else. What is up. I am using the latest TWRP and CM13 release.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2755793
helped)))

1vankill1 said:
http://forum.xda-developers.com/showthread.php?t=2755793
helped)))
Click to expand...
Click to collapse
That just seems to be a stock rom.

yes it stock rom, after it was installed, I was able to install 13 cm

Custom ROMs crashing every couple of minutes...

Hello!
For some reason the custom ROMs Sultans CM13 and Resurrection Remix crash every 5-15 minutes, it freezes then reboots, and does it faster after that. I've tries reinstalling TWRP to no avail...
Stock works fine with Root and Xposed... But Custom ROMs don't want to work... So my guess is it's not a hardware issue...
I really want to get this solved since HOS is being merged with OOS...
help? Thanks!

SynaTech said:
Hello!
For some reason the custom ROMs Sultans CM13 and Resurrection Remix crash every 5-15 minutes, it freezes then reboots, and does it faster after that. I've tries reinstalling TWRP to no avail...
Stock works fine with Root and Xposed... But Custom ROMs don't want to work... So my guess is it's not a hardware issue...
I really want to get this solved since HOS is being merged with OOS...
help? Thanks!
Click to expand...
Click to collapse
This is not a hardware issue..
Back to stock..
Did you wipe all?
Twrp latest better 3.2.0

madsponge26 said:
This is not a hardware issue..
Back to stock..
Did you wipe all?
Twrp latest better 3.2.0
Click to expand...
Click to collapse
_________________________________________________
Back to stock as in... No root, stock bootloader?
Wipe all being Dalvik + Cache + System or Dalvik + Cache + System + Internal?
Also, I'm on the latest version of twrp possible

SynaTech said:
__________________________________________________
Back to stock as in... No root, stock bootloader?
Wipe all being Dalvik + Cache + System or Dalvik + Cache + System + Internal?
Also, I'm on the latest version of twrp possible
Click to expand...
Click to collapse
No that's both dirty flashing. You need to wipe Dalvik + Cache + System + data.
Do not wipe internal because then there's nothing left to flash.
You will lose all your apps wiping data but I suppose you know right?

J_Dutch said:
No that's both dirty flashing. You need to wipe Dalvik + Cache + System + data.
Do not wipe internal because then there's nothing left to flash.
You will lose all your apps wiping data but I suppose you know right?
Click to expand...
Click to collapse
Yes I know, I've flashed before...
Now, when I wipe all but internal (for obvious reasons) I will loose root + xposed correct? I've never flashed any Roms while having root and xposed installed...
Or before I flash do I have to delete/remove both?

SynaTech said:
Yes I know, I've flashed before...
Now, when I wipe all but internal (for obvious reasons) I will loose root + xposed correct? I've never flashed any Roms while having root and xposed installed...
Or before I flash do I have to delete/remove both?
Click to expand...
Click to collapse
When you wipe all but internal you are starting clean and don't need to do anything other then flash ROM+gapps
And optional flash xposed. Root is already included in most roms.

J_Dutch said:
When you wipe all but internal you are starting clean and don't need to do anything other then flash ROM+gapps
And optional flash xposed. Root is already included in most roms.
Click to expand...
Click to collapse
Since I want to flash Sultans CM13, root isn't included... So, my flash order is...
Wipe Dalvik + Cache, System, Data (Everything but system), Flash ROM, GApps, and Root, then Xposed all in one flash?

SynaTech said:
Since I want to flash Sultans CM13, root isn't included... So, my flash order is...
Wipe Dalvik + Cache, System, Data (Everything but system), Flash ROM, GApps, and Root, then Xposed all in one flash?
Click to expand...
Click to collapse
Your doing it correctly.but still facing issues so i will suggest you to do real clean flash that means first flash full rom zip (about 1.3 gb in size) of stock oos via twrp then let device to boot.
Then enter into recovery ( use Official latest one) and wipe cache, data and system partition.
Now flash ROM.zip - supersu -kernel(optional) and now boot the Device and let it optimize all apps.
If you want Xposed now you can flash it ( be careful while selecting xposed zip . flash appropriate zip - sdk23 arm64)

JumboMan said:
Your doing it correctly.but still facing issues so i will suggest you to do real clean flash that means first flash full rom zip (about 1.3 gb in size) of stock oos via twrp then let device to boot.
Then enter into recovery ( use Official latest one) and wipe cache, data and system partition.
Now flash ROM.zip - supersu -kernel(optional) and now boot the Device and let it optimize all apps.
If you want Xposed now you can flash it ( be careful while selecting xposed zip . flash appropriate zip - sdk23 arm64)
Click to expand...
Click to collapse
So, I've flashed CM13 Sultans with root, which I haven't done before... It seems stable, I'll know in an hour or so...

JumboMan said:
Your doing it correctly.but still facing issues so i will suggest you to do real clean flash that means first flash full rom zip (about 1.3 gb in size) of stock oos via twrp then let device to boot.
Then enter into recovery ( use Official latest one) and wipe cache, data and system partition.
Now flash ROM.zip - supersu -kernel(optional) and now boot the Device and let it optimize all apps.
If you want Xposed now you can flash it ( be careful while selecting xposed zip . flash appropriate zip - sdk23 arm64)
Click to expand...
Click to collapse
He didn't mention he wiped data, since I told him to wipe data it will be fine now, there is totally no use in going through all you describe, people just need to read a little and know how to wipe and flash.

SynaTech said:
Yes I know, I've flashed before...
Now, when I wipe all but internal (for obvious reasons) I will loose root + xposed correct? I've never flashed any Roms while having root and xposed installed...
Or before I flash do I have to delete/remove both?
Click to expand...
Click to collapse
Haven't had cause to use xposed for a while, but am assuming it still uses it's own framework? This used to preclude flashing a new rom whilst xposed was activated.

ghostofcain said:
Haven't had cause to use xposed for a while, but am assuming it still uses it's own framework? This used to preclude flashing a new rom whilst xposed was activated.
Click to expand...
Click to collapse
Annnnnd...
IT WORKS!
I'm so happy, I decided to wipe the dalvik and cache after every action... And wipe each party all together, then individually... It works!
And yes, Xposed uses its own framework still, its super easy to install, I would recommend checking it out again!

SynaTech said:
Annnnnd...
IT WORKS!
I'm so happy, I decided to wipe the dalvik and cache after every action... And wipe each party all together, then individually... It works!
And yes, Xposed uses its own framework still, its super easy to install, I would recommend checking it out again!
Click to expand...
Click to collapse
But it does mean you have to do full wipe and or deactivate it before flashing new rom. I probably will get around to using xposed again one day just nothing I need from it at present.

J_Dutch said:
He didn't mention he wiped data, since I told him to wipe data it will be fine now, there is totally no use in going through all you describe, people just need to read a little and know how to wipe and flash.
Click to expand...
Click to collapse
The ROM still crashed, ugh.. I'm worried that I won't be able to get an OTA working, since I can't get them normally because of root, xposed, etc...
I did everything you said, and it still crashed...
To be fair, it took waaaaay longer than normal to crash, so I think we are getting there... Hmmm
Suggestions?
Thanks!
Also, it crashes the same way every time, freeze for 5-10 seconds, then boop, black screen, then reboot...
SElinux is enforcing, and I'm encrypted... Could those have anything to do with it? Thanks!

ghostofcain said:
But it does mean you have to do full wipe and or deactivate it before flashing new rom. I probably will get around to using xposed again one day just nothing I need from it at present.
Click to expand...
Click to collapse
The ROM ended up crashing, ugh.. I'm worried that I won't be able to get an OTA working, since I can't get them normally because of root, xposed, etc...
I did everything you said, and it still crashed...
To be fair, it took waaaaay longer than normal to crash, so I think we are getting there... Hmmm
Suggestions?
Thanks!
Also, it crashes the same way every time, freeze for 5-10 seconds, then boop, black screen, then reboot...
SElinux is enforcing, and I'm encrypted... Could those have anything to do with it? Thanks!

Debugging instability with custom roms, and adding xposed modules into the mix, is a bit of a black art but here goes.
First install your custom ROM, with a clean flash i.e wipe everything. Do Not restore any data, except the stuff Google restores itself. Run the rom in this state for a good while (as a rule of thumb try running it for twice your expected stable period before considering it at stable i.e if it crashes once a day run it for two days) if stable proceed to next stage.
If your chosen custom ROM does not have xposed framework install it and activate now, Do not install any modules run for a while to access stability before proceeding to next step.
One by one install your chosen modules, again running each for a while to access stability.
At any one of these steps stability should degrade if so you have identified your culprit.
I know this process is laborious and likely to take a while to complete but sometimes otherwise rock solid roms can be affected by a combination of things and without carrying out the above steps identifying the culprit is nigh on impossible, do bear in mind that some custom roms are just less stable than stock.

ghostofcain said:
Debugging instability with custom roms, and adding xposed modules into the mix, is a bit of a black art but here goes.
First install your custom ROM, with a clean flash i.e wipe everything. Do Not restore any data, except the stuff Google restores itself. Run the rom in this state for a good while (as a rule of thumb try running it for twice your expected stable period before considering it at stable i.e if it crashes once a day run it for two days) if stable proceed to next stage.
If your chosen custom ROM does not have xposed framework install it and activate now, Do not install any modules run for a while to access stability before proceeding to next step.
One by one install your chosen modules, again running each for a while to access stability.
At any one of these steps stability should degrade if so you have identified your culprit.
I know this process is laborious and likely to take a while to complete but sometimes otherwise rock solid roms can be affected by a combination of things and without carrying out the above steps identifying the culprit is nigh on impossible, do bear in mind that some custom roms are just less stable than stock.
Click to expand...
Click to collapse
Wipe everything but internal correct? And also should I install gapps right away or wait a bit, then install gapps?
Thanks for all the help!

Yes wipe everything bar internal, personally I'd run it without gapps, even, to start with.

ghostofcain said:
Yes wipe everything bar internal, personally I'd run it without gapps, even, to start with.
Click to expand...
Click to collapse
Even without Gapps, it crashed in around 2-3 minutes

Wow, that is poor. You aren't having this problem with stock OS?

Which [Android 8] daily driver to move to from FreedomOS 2.10.4 [7.1.1] ?

Back after a long time.
My OP3
- Freedom OS 2.10.4 [Android 7.1.1]
- BluSpark Recovery v40
On my OP3 I've always been on Freedom OS . Mostly due to
- Being close to stock,
- Debloated
- rooted for ad blocker, cerberus and titanium
However off the late facing lot of issue with network. Frequent drops on VoLTE and 4G networks on both sims. VoLTE sim will often disconnect and I will end with "Dial-> Immediate Call Ended" issue.
=> What would you recommend to use as daily driver ?
Would appreciate if you should add links. Any additional info regarding prerequisites (recovery, firmware etc) will be helpful.

You can try:
1-OxygenOS 5.0.3 with RenderZenith or Derp kernel.(Do not go for open beta OxygenOS builds, they are abandoned.)
2-Paranoid Android 7.3.1(Nougat but it won't upset you)
3-If camera, VoWiFi and OTA updates are not important, OmniDragon.
Everyone's expectations are different. These are just mine experiences.
You should update your TWRP before flashing, i guess it is outdated; PA and OxygenOS contains their own firmware but for OmniDragon you can use Open Beta 39/OxygenOS 5.0.3 firmwares.

qhsusb_bulk said:
You can try:
1-OxygenOS 5.0.3 with RenderZenith or Derp kernel.(Do not go for open beta OxygenOS builds, they are abandoned.)
2-Paranoid Android 7.3.1(Nougat but it won't upset you)
3-If camera, VoWiFi and OTA updates are not important, OmniDragon.
Everyone's expectations are different. These are just mine experiences.
You should update your TWRP before flashing, i guess it is outdated; PA and OxygenOS contains their own firmware but for OmniDragon you can use Open Beta 39/OxygenOS 5.0.3 firmwares.
Click to expand...
Click to collapse
Thanks. Will check OxygenOS 5.0.3
Any reason why you did not suggest LineageOS?
Also will I be able to keep custom recovery and root with OxygenOS 5.0.3

hyperorb said:
Thanks. Will check OxygenOS 5.0.3
Any reason why you did not suggest LineageOS?
Also will I be able to keep custom recovery and root with OxygenOS 5.0.3
Click to expand...
Click to collapse
According to my experiences, unfortunately LineageOS 15.1 is not a daily driver on SD820 phones. Used it on Mi5 and OP3, both of them suffered with lag, overheating, shuttering, deep sleep not working sometimes (lost apx.%30 battery per night), bad camera quality. It is good rom, but this issues must be solved.
You can keep root and TWRP on OOS. Process:
1-Flash TWRP and boot it.
2-Make the wipes(dalvik/data/cache/system are must, if you want full wipe of userdata you can select internal storage too.
3-Install OxygenOS zip, custom kernel zip(optional) and latest Magisk beta zip(16.7 today).
Reboot and profit.

qhsusb_bulk said:
According to my experiences, unfortunately LineageOS 15.1 is not a daily driver on SD820 phones. Used it on Mi5 and OP3, both of them suffered with lag, overheating, shuttering, deep sleep not working sometimes (lost apx.%30 battery per night), bad camera quality. It is good rom, but this issues must be solved.
You can keep root and TWRP on OOS. Process:
1-Flash TWRP and boot it.
2-Make the wipes(dalvik/data/cache/system are must, if you want full wipe of userdata you can select internal storage too.
3-Install OxygenOS zip, custom kernel zip(optional) and latest Magisk beta zip(16.7 today).
Reboot and profit.
Click to expand...
Click to collapse
Thank you for helping with my queries.
So it's just like flashing a custom rom. Also If I wipe internal storage then the ROM zip file will also get wiped. Wonder how do I copy it then?
Last set of queries before I flash this coming weekend
- Whch TWRP ? Latest blu_spark should do ? (I remember blu_spark had specific TWRP for OP3_OP3T
- I remember reading about recovery getting overwritten when flashing OxygenOS.. Will it happen with full rom zip
- Any precautions you would like to suggest ?

hyperorb said:
Thank you for helping with my queries.
So it's just like flashing a custom rom. Also If I wipe internal storage then the ROM zip file will also get wiped. Wonder how do I copy it then?
Last set of queries before I flash this coming weekend
- Whch TWRP ? Latest blu_spark should do ? (I remember blu_spark had specific TWRP for OP3_OP3T
- I remember reading about recovery getting overwritten when flashing OxygenOS.. Will it happen with full rom zip
- Any precautions you would like to suggest ?
Click to expand...
Click to collapse
Yes, if you wipe internal storage, the rom will be wiped. But you can just copy it from your pc while you are in twrp.
Latest Blu_spark twrp works fine for me. Will work for you too.
If recovery is overwritten, you can just flash twrp again via fastboot. It won't be overwritten then.
I think there was a way that after you can avoid having to fastboot by just installing twrp again right after you have flashed oos rom and then reboot. But I am not quite sure if it works. Maybe someone else with experience can elaborate. Anyways, the fastboot method will definitely work.

@hyperorb , If you flash Magisk right after OOS, your recovery won't be replaced by Oxygen one.
For recovery, you can use Official TWRP or OmniDragon TWRP.

many thanks @qhsusb_bulk @Harsh862
will try wit latest blu_spark first but will also keep others handy. Will not refresh internal storage for now. Maybe once I get a bit comfortable with this part. Will revert once I update.

OP3 OOS 5.0.3
Attaching link in case someone else need

Easy breezy.
Thanks to @qhsusb_bulk @Harsh862 Upgraded to OOS 5.0.3
1) Backups ( whatsapp, titanium, nandroid)
2) Remove all security - pin , fingerprint
3) Reboot to recovery
4) Upgrade TWRP to 8.6.1 blu_stark
5) Reboot to recovery
6) Full wipe except internal storage
7) Flash OOS
8) Wipe dalvik / cache
-------
9) Flash Magisk 16 (1600). I'm not sure what happened but it froze at a point with some message about /Vendor . Screen went black which white LED on.
10) Waited for 30 sec
11) Manual reboot to recovery
12) Wipe dalvik / cache
13) Flash Magisk 15.6.3
14) Wipe dalvik / cache
15) Reboot to recovery
------
16) All Ok
17) Reboot to System

I've been on nitrogenos for half a year. Maybe your could give a try

hyperorb said:
Easy breezy.
Thanks to @[email protected] Upgraded to OOS 5.0.3
1) Backups ( whatsapp, titanium, nandroid)
2) Remove all security - pin , fingerprint
3) Reboot to recovery
4) Upgrade TWRP to 8.6.1 blu_stark
5) Reboot to recovery
6) Full wipe except internal storage
7) Flash OOS
8) Wipe dalvik / cache
-------
9) Flash Magisk 16 (1600). I'm not sure what happened but it froze at a point with some message about /Vendor . Screen went black which white LED on.
10) Waited for 30 sec
11) Manual reboot to recovery
12) Wipe dalvik / cache
13) Flash Magisk 15.6.3
14) Wipe dalvik / cache
15) Reboot to recovery
------
16) All Ok
17) Reboot to System
Click to expand...
Click to collapse
Is this offical Rom?

Yes. I downloaded from OnePlus forums

hyperorb said:
Easy breezy.
Thanks to @qhsusb_bulk @Harsh862 Upgraded to OOS 5.0.3
1) Backups ( whatsapp, titanium, nandroid)
2) Remove all security - pin , fingerprint
3) Reboot to recovery
4) Upgrade TWRP to 8.6.1 blu_stark
5) Reboot to recovery
6) Full wipe except internal storage
7) Flash OOS
8) Wipe dalvik / cache
-------
9) Flash Magisk 16 (1600). I'm not sure what happened but it froze at a point with some message about /Vendor . Screen went black which white LED on.
10) Waited for 30 sec
11) Manual reboot to recovery
12) Wipe dalvik / cache
13) Flash Magisk 15.6.3
14) Wipe dalvik / cache
15) Reboot to recovery
------
16) All Ok
17) Reboot to System
Click to expand...
Click to collapse
Step 9 happens to me everytime I flash OOS/OB. I simply wait for the white led to come on, press the Power button for 8+ seconds and phone switches off. Restart in recovery mode and flash Magisk. This time it will install.