I just installed the 4.0.2 update, got this new Android 7.
However, upon booting somehow my device cannot detect any sim card. I went to settings, then selected SIM&Network and suddenly settings crashed. I tried selecting Data Usage / More options which also makes settings crash, while other options work fine.
Along with network related settings crashing, some of the system apps, like the new oneplus community thingy and file manager also crashes upon launching the app.
Also, whenever I boot my phone I get this 'dm-verity not started in enforcing mode' screen.
Anyone have a solution? I am seriously confused right now.
Like any Android version change, you should do a clean install. If you do a factory reset your phone should be fine.
jenil1428569 said:
I just installed the 4.0.2 update, got this new Android 7.
However, upon booting somehow my device cannot detect any sim card. I went to settings, then selected SIM&Network and suddenly settings crashed. I tried selecting Data Usage / More options which also makes settings crash, while other options work fine.
Along with network related settings crashing, some of the system apps, like the new oneplus community thingy and file manager also crashes upon launching the app.
Also, whenever I boot my phone I get this 'dm-verity not started in enforcing mode' screen.
Anyone have a solution? I am seriously confused right now.
Click to expand...
Click to collapse
Check this guide: https://forum.xda-developers.com/oneplus-3/how-to/guide-flashing-oos-v4-0-1-custom-rom-t3537757/
dbabaev21 said:
Check this guide: https://forum.xda-developers.com/oneplus-3/how-to/guide-flashing-oos-v4-0-1-custom-rom-t3537757/
Click to expand...
Click to collapse
I did the hard reset thingy and factory reset whatsoever, and some system apps not launching have been dealt with. However, my sim card is still not being detected and thos horrendous lag is still present.
jenil1428569 said:
I did the hard reset thingy and factory reset whatsoever, and some system apps not launching have been dealt with. However, my sim card is still not being detected and thos horrendous lag is still present.
Click to expand...
Click to collapse
Ok, good.
Now sideload the OOS v4.0.2. So, everything will go back to normal.
How did you upgrade to OOS 4.0.2 ? from OOS 4.0.1 ? Or OOS 3.5.4 ? So did you upgrade from stock recovery or TWRP ?
Kris Chen said:
How did you upgrade to OOS 4.0.2 ? from OOS 4.0.1 ? Or OOS 3.5.4 ? So did you upgrade from stock recovery or TWRP ?
Click to expand...
Click to collapse
I upgraded it from OOS 3.2.8 through TWRP.
OK, May I ask you which one of TWRP version do you use ?
jenil1428569 said:
I upgraded it from OOS 3.2.8 through TWRP.
Click to expand...
Click to collapse
Kris Chen said:
OK, May I ask you which one of TWRP version do you use ?
Click to expand...
Click to collapse
3.0.3_0
The dm-verity problem usually comes if you flash the update and don't flash SuperSU without rebooting, and with the problem with your sim, I would try to insert a different sim and see if the problem persist.
Un saludo.
Thanks!
Let me summarize how to flash OOS 4.0.2: You use TWRP 3.0.3-0 to upgrade your OP3 from OOS 3.5.2 to OOS 4.0.2
Well, I would recommend you do so:
(1)Please use Titanium to backup all your files and then copy to your computer.
(2)Upgrade your TWRP 3.0.3-0 to TWRP 3.0.3-1. TWRP 3.0.3-1 can be downloaded from TWRP official site.
(3)Then download complete OOS 4.0.2 to your computer HDD.
(4)Wipe all partition
(5)Copy OOS 4.0.2 to your phone, including of your Titanium App backup files.
(6)Flashing OOS 4.0.2. Then SuperSU 2.79 and google play store.
(7)Reboot to system and complete all necessary settings.
(8)After that, going to google play store and install Taitanium backup. Then restore all your backup files.
(9)Reboot again. Done
God bless !
jenil1428569 said:
3.0.3_0
Click to expand...
Click to collapse
Kris Chen said:
Thanks!
Let me summarize how to flash OOS 4.0.2: You use TWRP 3.0.3-0 to upgrade your OP3 from OOS 3.5.2 to OOS 4.0.2
Well, I would recommend you do so:
(1)Please use Titanium to backup all your files and then copy to your computer.
(2)Upgrade your TWRP 3.0.3-0 to TWRP 3.0.3-1. TWRP 3.0.3-1 can be downloaded from TWRP official site.
(3)Then download complete OOS 4.0.2 to your computer HDD.
(4)Wipe all partition
(5)Copy OOS 4.0.2 to your phone, including of your Titanium App backup files.
(6)Flashing OOS 4.0.2. Then SuperSU 2.79 and google play store.
(7)Reboot to system and complete all necessary settings.
(8)After that, going to google play store and install Taitanium backup. Then restore all your backup files.
(9)Reboot again. Done
God bless !
Click to expand...
Click to collapse
Can I ask why you recommend flashing google play store, when it's included in the complete OOS 4.0.2 ? Seems redundant...
Related
hello all,
I have a rooted OP3 running the latest TWRP recovery. Using these instructions I am trying to upgrade to 3.2.8 from 3.2.7. There are no errors displayed during OOS or SuperSU install steps.
But when the phone reboots - it stays stuck at the boot animation. This happens across several attempts. I do not have xposed installed, if it helps. Repeating the above steps with a 3.2.7 image works without issues.
Is there any way I can figure out where the 3.2.8 reboot is getting stuck at? I *do not* want to do a fresh install.
Any thoughts/ Suggestions? I have already posted at the above thread and thought I'd try my luck here too.
EDIT: Can a MOD please move this to Q&A forum. Just realized I posted to Guides, News & Discussion.
backup all your data and install 3.2.8 with the official procedure
Sacob said:
backup all your data and install 3.2.8 with the official procedure
Click to expand...
Click to collapse
That's my last option. But that's as good as starting from scratch. In which case, I might as well postpone until Nougat arrives on the OP3
tropicanapure said:
That's my last option. But that's as good as starting from scratch. In which case, I might as well postpone until Nougat arrives on the OP3
Click to expand...
Click to collapse
and wait without a phone?
Flash the new Beta 10. i'm currently using it with root and it works great
Not sure what you mean - without a phone. I was able to roll back to 3.2.7 with zero issues
I was mulling over installing the Beta - but I understand Nougat is due in Jan? Also, is there a process to move to b10 without losing data?
Sacob said:
and wait without a phone?
Flash the new Beta 10. i'm currently using it with root and it works great
Click to expand...
Click to collapse
tropicanapure said:
Not sure what you mean - without a phone. I was able to roll back to 3.2.7 with zero issues
I was mulling over installing the Beta - but I understand Nougat is due in Jan? Also, is there a process to move to b10 without losing data?
Click to expand...
Click to collapse
i got the impression that your phone wasn't booting xD
well, every time i flash those betas (9 and 10) TWRP asks me for a PIN that doesn't exists and to solve that i need wipe everything... so i wouldn't count on that
tropicanapure said:
hello all,
I have a rooted OP3 running the latest TWRP recovery. Using these instructions I am trying to upgrade to 3.2.8 from 3.2.7. There are no errors displayed during OOS or SuperSU install steps.
But when the phone reboots - it stays stuck at the boot animation. This happens across several attempts. I do not have xposed installed, if it helps. Repeating the above steps with a 3.2.7 image works without issues.
Is there any way I can figure out where the 3.2.8 reboot is getting stuck at? I *do not* want to do a fresh install.
Any thoughts/ Suggestions? I have already posted at the above thread and thought I'd try my luck here too.
EDIT: Can a MOD please move this to Q&A forum. Just realized I posted to Guides, News & Discussion.
Click to expand...
Click to collapse
Did you download the full 3.2.8 zip from http://downloads.oneplus.net? I did. And to my surprise, it erases the whole userdata partition, including TWRP backups and downloaded files (including SuperSU zip). So big warning if you try with that zip. I assume that this zip is intended for those reverting from Nougat Beta, to go back from F2FS to EXT4.
My solution was to restore an old TWRP backup that was saved on my PC and then reflash a modified full 3.2.8 zip where the last line in the update script was removed: the one that erases userdata partition. So before flashing full 3.2.8 zip from http://downloads.oneplus.net I recommend you to remove the last line in the update script.
No, I downloaded the Full ZIP from this official thread on the OP3 forums. I was aware of that line though. And from previous experience - the first thing I do when I make a TWRP backup is to move it off the phone. That and I purchased Titanium Backup long time ago. I use it to back up stuff surgically and sync it up to Dropbox every night. The app also seems to have the ability to make a recovery-flashable "update.zip" - something I have yet to try.
Appreciate the heads-up though.
ptblad said:
Did you download the full 3.2.8 zip from http://downloads.oneplus.net? I did. And to my surprise, it erases the whole userdata partition, including TWRP backups and downloaded files (including SuperSU zip). So big warning if you try with that zip. I assume that this zip is intended for those reverting from Nougat Beta, to go back from F2FS to EXT4.
My solution was to restore an old TWRP backup that was saved on my PC and then reflash a modified full 3.2.8 zip where the last line in the update script was removed: the one that erases userdata partition. So before flashing full 3.2.8 zip from http://downloads.oneplus.net I recommend you to remove the last line in the update script.
Click to expand...
Click to collapse
tropicanapure said:
No, I downloaded the Full ZIP from this official thread on the OP3 forums. I was aware of that line though. And from previous experience - the first thing I do when I make a TWRP backup is to move it off the phone. That and I purchased Titanium Backup long time ago. I use it to back up stuff surgically and sync it up to Dropbox every night. The app also seems to have the ability to make a recovery-flashable "update.zip" - something I have yet to try.
Appreciate the heads-up though.
Click to expand...
Click to collapse
OK. I also use TB, and from now on I use cloud storage :laugh:
After the full modified 3.2.8 zip I successfully flashed official SuperSU 2.79, Xposed v87 and Bluspark r25 kernel. I use F2FS on data partition. It boots and runs fine!
The only thing I'm a bit concerned about is that it stays on the bootlogo (OnePlus logo, Powered by Android) for about 25 secs before the bootanimation begins when booting to system. Much faster before. When booting to recovery (TWRP 28, Bluspark) the time on bootlogo is normal (short). Any thoughts on that?
I wish I had, man. You went a number of steps ahead when your phone went past the boot animation
As a afterthought - try looking through your logs.
ptblad said:
OK. I also use TB, and from now on I use cloud storage :laugh:
After the full modified 3.2.8 zip I successfully flashed official SuperSU 2.79, Xposed v87 and Bluspark r25 kernel. I use F2FS on data partition. It boots and runs fine!
The only thing I'm a bit concerned about is that it stays on the bootlogo (OnePlus logo, Powered by Android) for about 25 secs before the bootanimation begins when booting to system. Much faster before. When booting to recovery (TWRP 28, Bluspark) the time on bootlogo is normal (short). Any thoughts on that?
Click to expand...
Click to collapse
https://download.lineageos.org/crackling
The First One!
Do we need su for arm or su for arm64?
Obscurax said:
Do we need su for arm or su for arm64?
Click to expand...
Click to collapse
Arm64
What's the build name of the Swift 2X?
Sent from my Moto G4 using XDA Labs
kartotar said:
What's the build name of the Swift 2X?
Click to expand...
Click to collapse
marmite
M.A.K said:
marmite
Click to expand...
Click to collapse
Thanks. Do you have any idea if LineageOS will be supported on Marmite?
Sent from my Moto G4 using XDA Labs
AFAIK, Swift 2 ks not officially supported by Lineage OS, so no. You may be able to find an unofficial version though.
Cannot dirty flash
I currently have thomson.aa's unofficial lineage os build installed. This update shows up in the updater app, but after I download it, it says the zip is corrupt or unsigned and it does not let me install it. If I manually download it and try to install via TWRP, it fails saying "can't install this package on top of incompatible data. Please try another package or run a factory reset". I would hate to have to reinstall all my stuff, though. Is there some way around this? Or is there something wrong with the update?
Got no problems installing it via TWRP. Works great, stable so far.
crdroid was fine too, lots of special settings (little too much for me), but I prefer a ROM with regular OTA updates. Thank you beroid anyway.
P.S. My grammar help changes "beroid" to "heroic"
Can this be installed over the top of cm13.0 nightly?
Mithodin said:
I currently have thomson.aa's unofficial lineage os build installed. This update shows up in the updater app, but after I download it, it says the zip is corrupt or unsigned and it does not let me install it. If I manually download it and try to install via TWRP, it fails saying "can't install this package on top of incompatible data. Please try another package or run a factory reset". I would hate to have to reinstall all my stuff, though. Is there some way around this? Or is there something wrong with the update?
Click to expand...
Click to collapse
You basically asked the same question in 2 threads??? So as this isn't really thomson.aa's problem, I'll answer you here.
I dirty flashed from stock -> cm13 -> crDroid -> thomson.aa's LOS14 without issue. I tried with the official release and got the same as you. So after editing the installer script to force it to install, it did. But once it booted, everything kept force closing. It just wasn't happening.
So I wiped data and chose to restore my backup from google. I just installs most of your apps but it saves a bit of time. Still need to set things up properly though.
M.A.K said:
You basically asked the same question in 2 threads??? So as this isn't really thomson.aa's problem, I'll answer you here.
Click to expand...
Click to collapse
I figured this might be due to either
- Something being wrong with the currently installed build
- Something being wrong with the one I'm trying to install
That's why I posted in both places. Sorry if that is not the thing to do.
Thanks for your reply. I guess I'll have to do another reinstall then.
Wifi
Installed tonite smoothly however no wifi - anyone else with this?
Same here, just reported a bug to the bugtracker.
Make a clean install three days ago, all works fine
pahesis said:
Same here, just reported a bug to the bugtracker.
Click to expand...
Click to collapse
I have no wifi, too (after trying a dirty install over an old CM13 that resulted in an error). Here's the issue in their bugtracker, I think, in case anyone else experiences this.
Got the same issue when trying to go back to CM13 now -___-
Seems strange that I've had no wifi issues. I've tried turning it on and off with no problems.
A few (maybe patronising) thoughts:
Did you guys check the md5 hash?
Which recovery did you use? I used TWRP 3.0.2.5
Were you previously on COS13.1.2? I was.
I downloaded fresh open-gapps for the install - ARM64, 7.1, nano.
I wiped system, dalvik, cache. Installed LOS14.1, su, gapps in that order.
The dirty boot left me with lots of force closures so I wiped data, dalvik and cache, completed the wizard after booting and all was fine.
M.A.K said:
Did you guys check the md5 hash?
Click to expand...
Click to collapse
Yes
M.A.K said:
Which recovery did you use?
Click to expand...
Click to collapse
TWRP-3.0.3-0
M.A.K said:
Were you previously on COS13.1.2?
Click to expand...
Click to collapse
I was on the latest CyanogenMod snapshot.
I wiped data, dalik and cache, then installed lineage, gapps and su. Restoring a nandroid backup of CM13 did bring the wifi back again.
I then wanted to restore my backup of lineage, because I already transferred most apps and settings and don’t care to much for the wifi (hoping it will be solved in not too far future), but TWRP failed to recover, getting stuck while restoring data, only restoring the system partition. Strangely, after this, the wifi worked, however I experienced many FCs. After wiping data again, the wifi was broken again, the MAC adress showing as 02:00:00:00:00:00.
Wiping system, I tried to reinstall lineage without any extras, but TWRP just got stuck again with no progress being made after detection of the partitions. Strangely, restoration of the lineage backup worked now, including data The original problem persists, of course.
I mentioned COS13.1.2 specifically because it flashes partitions other than system that may affect your situation. CM doesn't. If you've had COS13.1.2 installed previously then these other partitions should be up to date.
If you're having inconsistent results using TWRP3.0.3 it may be worth trying 3.0.2.5.
ES File Explorer
Hello guys! I have a small problem. I installed the LOS 14.1 and now I have error in ES File Explorer, "Sorry test failed. This feature cannot run on your phone".
The su binary I already threw, and all files bin already threw. Help solve the problem!
p.s. sorry for my English
Sup guys,
I have been using the rooted original roms for a while now with the APT-x codec installed though since 4.0.3 this doesn't work any more. So I would like to downgrade to 4.0.2 for the time being. How would I go about doing this ?
Select the version of OOS you want, download it from OnePlus's site and flash it through either the stock or custom recovery.
http://downloads.oneplus.net/devices/oneplus-3/
Anova's Origin said:
Select the version of OOS you want, download it from OnePlus's site and flash it through either the stock or custom recovery.
Click to expand...
Click to collapse
Same way as upgrading to a new version? to keep root I would have to flash Supersu ?
Yep.
Can I just use the current twrp and supersu or would I need to download a older version of either?
tdmike said:
Can I just use the current twrp and supersu or would I need to download a older version of either?
Click to expand...
Click to collapse
Yes, you can.
AptX is working good on 4.0.3 with magisk module.
I'm using it at the moment.
But it's broken since 4.1.
So I just had to restore to the current version. My launcher and keyboard kept crashing and I wasn't able to install apps. Seems something went wrong. Anyone any clues?
What I did: take a nandroid, wipe dalvik cache, install 4.0.3, install most recent SuperSU. Wipe dalvik again and reboot.
Hi,
After updating (without -w), I'm not longer able to mount system and vendor partition in latest TWRP.
It's not a big deal, but I'm bout able to delete system apps and install YouTube vanced ...
Any idea how to solve this?
Sui77 said:
Hi,
After updating (without -w), I'm not longer able to mount system and vendor partition in latest TWRP.
It's not a big deal, but I'm bout able to delete system apps and install YouTube vanced ...
Any idea how to solve this?
Click to expand...
Click to collapse
We all have same issue, twrp needs to be updated. I clean flashed 10 (kept the - w intact), attempted to nandroid backup when I saw the problem and drove myself crazy thinking I did something wrong.
Thanks for the info, I'll wait for the update.
Thought I made a failure, but it is on both of my taimen
Sui77 said:
Thanks for the info, I'll wait for the update.
Thought I made a failure, but it is on both of my taimen
Click to expand...
Click to collapse
No need to wait, just install the non-root version of Vanced YouTube.
The mount issue with system and vendor is annoying; however, YouTube without the vanced mod is atrocious.
Sui77 said:
Hi,
After updating (without -w), I'm not longer able to mount system and vendor partition in latest TWRP.
It's not a big deal, but I'm bout able to delete system apps and install YouTube vanced ...
Any idea how to solve this?
Click to expand...
Click to collapse
Yeah same here. If i roll back to 9 everything works fine. Full wipe and flash of Q and it is a no go in twrp. I even wiped everything one more time and rolled back to 9 and side loaded 9 and still no good. Guess the TWRP team needs a fix for the handful of users that this is happening too.
Can I use the Oxygen Updater to go from OOS. 10.0.9 to 10.0.11? I'm rooted and have Magisk installed. When I went to the Updater it said it used TWRP, which I know still has issues on the 7T. Can I load TWRP 3.3.1-25 and use that? My goal is to move to the new release with out losing all my current installed applications (many!). Or do I have to do this all manually (a link would be nice is there already is a routine). Thanks.
davekaye said:
Can I use the Oxygen Updater to go from OOS. 10.0.9 to 10.0.11? I'm rooted and have Magisk installed. When I went to the Updater it said it used TWRP, which I know still has issues on the 7T. Can I load TWRP 3.3.1-25 and use that? My goal is to move to the new release with out losing all my current installed applications (many!). Or do I have to do this all manually (a link would be nice is there already is a routine). Thanks.
Click to expand...
Click to collapse
There is no working TWRP for the 7T yet. Just something in development. You'll have to do everything manually. Magisk has a guide on how to install an update and keep root. I haven't followed the guide yet myself but it is the method I will be using later tonight.
https://topjohnwu.github.io/Magisk/ota.html
Just make sure to disable/uninstall any magisk modules before you start. And probably any substratum overlays too just to be safe.
jsgraphicart said:
There is no working TWRP for the 7T yet. Just something in development. You'll have to do everything manually. Magisk has a guide on how to install an update and keep root. I haven't followed the guide yet myself but it is the method I will be using later tonight.
https://topjohnwu.github.io/Magisk/ota.html
Just make sure to disable/uninstall any magisk modules before you start. And probably any substratum overlays too just to be safe.
Click to expand...
Click to collapse
This guide works dude
manan001 said:
This guide works dude
Click to expand...
Click to collapse
Yeah, I just did it myself a little earlier. Easy and no issues
When I follow the steps at
When an OTA is available, first go to (Magisk Manager → Uninstall → Restore Images).
Click to expand...
Click to collapse
It says "Stock backup does not exist!" Is there a way I can create stock backups?
adobrakic said:
When I follow the steps at
It says "Stock backup does not exist!" Is there a way I can create stock backups?
Click to expand...
Click to collapse
I'm not an expert on this but as far as I know, it should have made the backup img file during the rooting process before patching the boot.img. If you don't have one then I don't know what happened to it. That step may not be 100% necessary though. I've read people saying you don't have to do that. I think it's mainly so you keep that stock img file backed up. Again, I don't know exactly but that's my understanding of it. I'm just giving you my thoughts on it
Stock backup does not exist
jsgraphicart said:
I'm not an expert on this but as far as I know, it should have made the backup img file during the rooting process before patching the boot.img. If you don't have one then I don't know what happened to it. That step may not be 100% necessary though. I've read people saying you don't have to do that. I think it's mainly so you keep that stock img file backed up. Again, I don't know exactly but that's my understanding of it. I'm just giving you my thoughts on it
Click to expand...
Click to collapse
I got this message -- Stock backup does not exist-- but proceed with the upgrade as per the instructions. Everything worked fine. Just waiting for the day when 7T TWRP will be available so I can use Oxygen Updater once again. Thanks for you comments.
davekaye said:
I got this message -- Stock backup does not exist-- but proceed with the upgrade as per the instructions. Everything worked fine. Just waiting for the day when 7T TWRP will be available so I can use Oxygen Updater once again. Thanks for you comments.
Click to expand...
Click to collapse
I also got this message when trying to uninstall magisk, so my question :
You proceeded with the upgrade - Was this from actual OS upgrade option in settings or from oxygen updater application?
If so, Im wondering if all you did was download the 10.0.11 full update & went to settings and applied it without doing anything in magisk.
Eg: you did not uninstall your modules and obviously did not uninstall magisk as it failed to do so cause there was no stock image.
At that point what did you do? You went to Re-install magisk (from where in magisk manager is the option?) and then selected "Install to inactive slot"
After that, you rebooted from magisk option to reboot and it took abit but rebooted all perfect?
Thanks
Upgrade rooted phone with OTA
JF-GINO said:
I also got this message when trying to uninstall magisk, so my question :
You proceeded with the upgrade - Was this from actual OS upgrade option in settings or from oxygen updater application?
If so, Im wondering if all you did was download the 10.0.11 full update & went to settings and applied it without doing anything in magisk.
Eg: you did not uninstall your modules and obviously did not uninstall magisk as it failed to do so cause there was no stock image.
At that point what did you do? You went to Re-install magisk (from where in magisk manager is the option?) and then selected "Install to inactive slot"
After that, you rebooted from magisk option to reboot and it took abit but rebooted all perfect?
Thanks
Click to expand...
Click to collapse
I downloaded the new OTA version (I think from the Updater app - if I remember it allowed you to download the OTA) to the root of my phone and then just followed the directions from the first reply to my post. I had the latest version of Magisk (Uninstaller, the app, and the Manager) installed in it's own folder in internal memory. After I got the message, just proceeded as if nothing was wrong and in the end, the upgrade worked fine. I didn't document every step, but the instructions worked.
https://topjohnwu.github.io/Magisk/ota.html
Did you uninstall all your modules first? Or leave them alone. I heard a few people didn't uninstall or deactivate there modules. I'm using xxx nolimits and don't want to have to redo everything, but I will if I have to.
Update :
A) I Downloaded 10.0.11 update from oxygen update app (zip on root)
Note - The only module I uninstalled was XXXNolimits and suggest you uninstall anything like this or any theming.
(I did leave busybox, systemless hosts, energized protection & a volume mod installed)
B) I manually updated from settings (Did NOT reboot)
C) I went to Magisk manager and installed Magisk in empty a/b slot as per instructions in link
D) I rebooted from Magisk
E) everything rebooted fine
F) I re-installed XXXNolimits - Rebooted
G) When rebooted, everything was exactly as it was before update and working fine!
So far so good. Phone was hot for awhile but cooled down after 10min and all is good.
Thanks everyone for your helpful posts
Does it pass SafetyNet check?
JF-GINO said:
Did you uninstall all your modules first? Or leave them alone. I heard a few people didn't uninstall or deactivate there modules. I'm using xxx nolimits and don't want to have to redo everything, but I will if I have to.
Update :
A) I Downloaded 10.0.11 update from oxygen update app (zip on root)
Note - The only module I uninstalled was XXXNolimits and suggest you uninstall anything like this or any theming.
(I did leave busybox, systemless hosts, energized protection & a volume mod installed)
B) I manually updated from settings (Did NOT reboot)
C) I went to Magisk manager and installed Magisk in empty a/b slot as per instructions in link
D) I rebooted from Magisk
E) everything rebooted fine
F) I re-installed XXXNolimits - Rebooted
G) When rebooted, everything was exactly as it was before update and working fine!
So far so good. Phone was hot for awhile but cooled down after 10min and all is good.
Thanks everyone for your helpful posts
Click to expand...
Click to collapse
Yep, safety net check pass.