Database Develop

SuperSU & CM13

Is it actually possible to make SuperSU work on CM13 without bricking your device etc?
I have spent the last 2 days googling this and reading various (mostly old, outdated) posts about how it's a bad idea or maybe not, but they are typically from 2.5x or 2.6x or earlier SuperSU versions.
My tablet, the only actively developed non-stock rom available for it is CM13. That is literally it.
However, I would like to have SuperSU features, especially compatibility with SUhide etc.
So, I am wondering if it's possible?
Do the current (2.78+) SuperSU versions play nice with CM13?
Can I just flash it in from the SuperSU app (I have bought pro version if that matters)? or Flashfire? or from TWRP recovery, whichever way is best? And, do I need to do anything else first?

Wellll, I went ahead and did it. Happy to report everything's working fine. So that's that.

DryEagle said:
Wellll, I went ahead and did it. Happy to report everything's working fine. So that's that.
Click to expand...
Click to collapse
Wanna share how you did it ?
. . . I'm running the latest CyanogenMod 13 om my GT-N5100 ( Samsung galaxy note 8 ) and can't get i to work without bricking the device.

Warlock_SVG said:
Wanna share how you did it ?
. . . I'm running the latest CyanogenMod 13 om my GT-N5100 ( Samsung galaxy note 8 ) and can't get i to work without bricking the device.
Click to expand...
Click to collapse
Well, I downloaded the latest supersu zip (2.78), installed the supersu app from market, installed supersu pro from market (i already bought this long ago), then used flashfire to flash the zip. and it just worked. i'm using latest cm13 nightly on nvidia shield.

Got it working I downloaded "BETA-SuperSU-v2.77-20160827190633.zip" and Installed it in TWRP, systemless mode.

Warlock_SVG said:
Got it working I downloaded "BETA-SuperSU-v2.77-20160827190633.zip" and Installed it in TWRP, systemless mode.
Click to expand...
Click to collapse
you can download 2.78 zip here: https://download.chainfire.eu/1001/SuperSU/UPDATE-SuperSU-v2.78-20160905010000.zip the 2.76 or 2.77 had some problem, dont remember which one, but 2.78 is completely solid

How do I install SuperSU in "systemless mode"? I have a google nexus 10 running the latest CM13 Release + gapps.

[Lemmy] said:
How do I install SuperSU in "systemless mode"? I have a google nexus 10 running the latest CM13 Release + gapps.
Click to expand...
Click to collapse
I used supersu-v2.78-201609011115 for my CM13 devices http://forum.supersu.com/topic/152/supersu-v2-78-release/2 the installer decide if it needs to be installed in "systemless mode" so no need to worry about that
You might need to install the SupperSU app from the store yourself.

Warlock_SVG said:
I used supersu-v2.78-201609011115 for my CM13 devices http://forum.supersu.com/topic/152/supersu-v2-78-release/2 the installer decide if it needs to be installed in "systemless mode" so no need to worry about that
You might need to install the SupperSU app from the store yourself.
Click to expand...
Click to collapse
does that work with the "official cyanogen recovery" as well, or should I install TWRP first?
...ok with the cyanogen recovery it did _not_ work, the installer said something about "patching sepolicy failed".
Any other suggestions?

[Lemmy said:
;68885779]does that work with the "official cyanogen recovery" as well, or should I install TWRP first?
...ok with the cyanogen recovery it did _not_ work, the installer said something about "patching sepolicy failed".
Any other suggestions?
Click to expand...
Click to collapse
Install twrp.

Spent my 6 hours in trying this crap.....after installation, my phone doesn't reboot rather says "secure boot error" installed cm13 6 times and faced the same problem.....now I won't install it unless I get a tested and confirmed procedure

Will follow-up with you on the next post...

ALI EHTISHAM BUKHARI said:
Spent my 6 hours in trying this crap.....after installation, my phone doesn't reboot rather says "secure boot error" installed cm13 6 times and faced the same problem.....now I won't install it unless I get a tested and confirmed procedure
Click to expand...
Click to collapse
Here's what I do to get my S3 going...
With the latest TWRP as always since running into issues with flashing when i had CWM quite some time ago.
There are 3 files i place in my external MicroSD...
CM13, Open Gaaps for Android 6 (i use the pico) and the SuperSU 2.78 SR1 zip file directly from the official website (though 2.76 should work).
First, when in TWRP, select wipe then advanced then the top 5 selections leaving the bottom 2 alone. When completed, hit the bottom center home selection to go into the main menu. Again, select wipe then select the data option to the right of the advanced tab you were in before. It requires you to type yes then proceed. Once that is done, go back to the main menu and be sure you do this exactly! Select the reboot and then recovery. Once your back into the TWRP recovery then select install and go to the MicroSD card with the 3 files... Now select the order of files to flash beginning with CM13 then add zip then the GApps then add zip then the SuperSU then begin the flash process. Be sure to wipe the dalvik cache then reboot the system.
SuperSU reboots it again shortly afterwards as part of its installation process.
Once your all done setting up the initial system setup you should go directly to the SuperSU app to set up what you need to.
Though my personal procedure is a bit more involved, this is as basic as it gets.
For your specific system, i can't say that i have ever even used it so please pardon me deeply if I left anything out and if someone can chime in with anything else, I'm sure it would be much appreciated.
Good luck.

Oxygen OS 10.0.5 is now live - Oxygen OS 10.0.5.GM21BA (EU)

Just to match the other threads for issues and discussion :
Official links :
Incremental : https://otafsg1.h2os.com/patch/amaz...OTA_024-025_patch_2003270113_ad17667b654b.zip
Full : https://otafsg1.h2os.com/patch/amaz....25_OTA_025_all_2003270113_4588ebe57af551.zip
Mirror links (AFH) :
Incremental : https://www.androidfilehost.com/?w=files&flid=307735
Full : https://www.androidfilehost.com/?w=files&flid=307737
Oxygen Updater also listing both the incremental update and the full update.
Installing :
For the uninitiated, Download either package and copy it to the root folder of your phone's storage, then go to the following location on your phone :
Settings > System (at the bottom) > System Updates (at the bottom) > Tap on the cog icon on the top right > Tap on local upgrade
The build available in your root folder should be listed, tap that and follow the instructions.
If you are coming from the beta release ring back to the main release ring you will most likely be prompted to wipe your data, ensure you have backed up all data you want to keep beforehand.
If you are upgrading from one release ring build to the next then you may want to clear your cache.
My Android 10 repo :
https://www.androidfilehost.com/?w=files&flid=296897
XDA page updated with official links :
https://www.xda-developers.com/onep...t-pro-5g-oxygenos-updates-march-2020-patches/
(Edit : Fixed the links, helps if you copy it properly :/ )
(Edit : Added official links and re-formatted )

Some users who already received the update previously had reported overheating and higher battery usage, tests on the official forum have shown better benchmark results compared to previous builds, so the heat and battery usage might be caused by this. No confirmation from OnePlus as to whether this was why the update was obviously being delayed.
Post any relevant improvements or reports of heating/battery differences below.
Remember to allow adequate time to gauge any difference in battery usage though.

Would flashing this over Beta 11 wipe my phone? I'm also rooted with TWRP.
Sent from my GM1915 using Tapatalk

How to update from OB11 to STABLE and keeping root and twrp
BACKUP all you want to keep safe.
I was on ob11 with latest Magisk Canary and twrp 3.3.1-79
Update from OB11 to STABLE 10.0.5 :
1- uninstall ALL Magisk modules. Reboot to System.
2- install Oos 10.0.5 stable with Settings > Local upgrade . DON'T reboot!!!
3- open Magisk > Downloads. Install TWRP A/B Retention Script. DON'T reboot!!!
4- back in Magisk. Touch install. Choose (Install to inactive slot after' OTA)
5- reboot to system.
Let the phone start. Mine at first start to twrp then to system.
This CLEAN istalls 10.05. It ERASES apps messages...

Done. Installed over 10.0.4 with TWRP and Magisk. WORKING.

I was hoping to not lose apps and messages.
Sent from my GM1915 using Tapatalk

Hi Guys,
I have downloaded full OTA update 10.0.5 from above link.
Flashed rom using TWRP, flashed TWRP image (3.3.1-79 by mauronofrio), rebooted to recovery and flashed Magisk 20.4.zip file.
After system reboot it is still showing OOS 10.0.4 with january 2020 security patch....
Did the same three times, initially twice with OTA zip file taken from Oxygen Updater later with ROM from this thead, same outcome - still on 10.0.4.
Is there something I'm doing wrong?? Can you please advice.
Thanks...

Yanoosh_GA said:
Hi Guys,
I have downloaded full OTA update 10.0.5 from above link.
Flashed rom using TWRP, flashed TWRP image (3.3.1-79 by mauronofrio), rebooted to recovery and flashed Magisk 20.4.zip file.
After system reboot it is still showing OOS 10.0.4 with january 2020 security patch....
Did the same three times, initially twice with OTA zip file taken from Oxygen Updater later with ROM from this thead, same outcome - still on 10.0.4.
Is there something I'm doing wrong?? Can you please advice.
Thanks...
Click to expand...
Click to collapse
You've only installed on one slot, use TWRP to change the slot and flash rom, TWRP and Magisk again.
Either that or just use TWRP to change the boot slot.

djsubterrain said:
You've only installed on one slot, use TWRP to change the slot and flash rom, TWRP and Magisk again.
Either that or just use TWRP to change the boot slot.
Click to expand...
Click to collapse
Great, changing the boot slot worked. Thanks.:good:

Hi guys, just updated to this 10.0.5, reinstalled twrp, but when starts WiFi won't stay on & network icons are a mess as in aren't showing correctly, would this be due to twrp needing an update as I've tried several versions & same result, returning to stock everything works perfectly again, any help would be great thanks

NHNXDA said:
Hi guys, just updated to this 10.0.5, reinstalled twrp, but when starts WiFi won't stay on & network icons are a mess as in aren't showing correctly, would this be due to twrp needing an update as I've tried several versions & same result, returning to stock everything works perfectly again, any help would be great thanks
Click to expand...
Click to collapse
Remove all Magisk modules first, restart then added it back, it's call recording module!

Up and running with TWRP 3.3.1-79 and Magisk 20.4.
Only one day of usage, so too early to draw conclusions, but I have seen no overheating or high battery drain.
If anything, it actually looks to have improved from 10.0.4:
BTW, SOT was 2h57

Why does this update wipes, makes factory defaults?

BoroZG said:
Why does this update wipes, makes factory defaults?
Click to expand...
Click to collapse
Did you install from Open Beta?

Hirs_E_Fruit said:
Did you install from Open Beta?
Click to expand...
Click to collapse
Yes beta 11.

BoroZG said:
Yes beta 11.
Click to expand...
Click to collapse
That's why

hoseth0711 said:
That's why
Click to expand...
Click to collapse
So, no way to avoid factory reset?

BoroZG said:
So, no way to avoid factory reset?
Click to expand...
Click to collapse
It's a different release ring so no, that's the way it's always been tbh

metzo32 said:
Remove all Magisk modules first, restart then added it back, it's call recording module!
Click to expand...
Click to collapse
Its the idiot, being me, I was using the wrong command line for twrp, instead of boot, I used flash boot, which of course flashed twrp as my boot.img & messed it up, I blame covid & isolation, realistically it was my silliness.

Flashed on T-Mobile 7pro, then xXx, no issues so far, great battery life.

[OXYGENOS] Android 10 Open Beta 1 for OnePlus 5

Changelog
System
• Brand new UI design brings light and fluid experience
• Updated to Android 10
Instructions
• Download the appropriate package - OnePlus 5
• Open the File Manager and move the downloaded .zip package from the Downloads folder to the root directory.
• Open Settings - System - System updates, press the cogwheel on the top right corner, choose the Local upgrade option, and select the rollback file.
Users who are still on OBT builds for 5/5T can update to this build only via update from recovery. For those, PLEASE NOTE, your entire data will be wiped.
• Turn off the device -> Press power and volume up key simultaneously until the device enters the Fastboot Mode
• Navigate to Recovery option using volume and power button -> Choose English -> Install from Internal storage -> Select the downloaded zip file -> Select 'Yes'
• Wait until the installation is complete -> Reboot
Note:
• Please keep in mind that this is beta software. These builds are not as stable as our official OTAs. By installing this update, you accept the potential risks.

https://forums.oneplus.com/threads/android-10-open-beta-1-for-oneplus-5-5t.1218721/
OnePlus 5 : https://oxygenos.oneplus.net/OnePlus5Oxygen_23_OTA_063_all_2004201835_a1de28fd0bda4c8b.zip
OnePlus 5T : https://oxygenos.oneplus.net/OnePlus5TOxygen_43_OTA_063_all_2004201837_eca63aa919a1477a.zip

Anyone dirty flashed the full zip through twrp and after that installed magisk for root? Does that work?
Im on latest stable.

PhoenixNLx said:
Anyone dirty flashed the full zip through twrp and after that installed magisk for root? Does that work?
Im on latest stable.
Click to expand...
Click to collapse
I don't think so... It's better to perform a clean install

Astur_Torque said:
I don't think so... It's better to perform a clean install
Click to expand...
Click to collapse
Offcourse its better. But just want to know if it works... If i dont have to install all of my apps again. I'll take a chance. So if anybody tried it allready.
Or clean install full zip and magisk after that maybe?

PhoenixNLx said:
Offcourse its better. But just want to know if it works... If i dont have to install all of my apps again. I'll take a chance. So if anybody tried it allready.
Or clean install full zip and magisk after that maybe?
Click to expand...
Click to collapse
I came here looking for this too. I guess I'll have to do a full backup just in case before updating.

Hi, I come from OOS Stable 9.0.11 root, I just uninstalled MAGISK via TWRP then I restarted and I went through settings then system and I did update locally and everything is fine past. I reflashed TWRP via Fastboot then root with Magisk the last via TWRP and it's all good !!!

Ssmiles said:
Hi, I come from OOS Stable 9.0.11 root, I just uninstalled MAGISK via TWRP then I restarted and I went through settings then system and I did update locally and everything is fine past. I reflashed TWRP via Fastboot then root with Magisk the last via TWRP and it's all good !!!
Click to expand...
Click to collapse
Did you dirty flash or?

yes dirty flash
kernel BluSpark OOS v193 error in TWRP
Recovery TWRP 3.3.1-x blu_spark v9.110
ctsProfil Magisk 20.4 false

Astur_Torque said:
I don't think so... It's better to perform a clean install
Click to expand...
Click to collapse
Yes it worked, for me except duo calls not working when google hotword is enabled, everything is working

duo it's desactived

I tried this method https://droidholic.com/fix-cts-profile-mismatch-errors/ but CHROME doesn't work afterwards so I uninstalled everything

I just dirty flashed it in bluspark.
Full zip install
Magisk 20.4
Clear cache
Done

@PierreVicquery02 Request you to please remove the "[OFFICIAL]" from the thread title. The official thread already exists (it is stickied). Thanks for understanding!

shadowstep said:
@PierreVicquery02 Request you to please remove the "[OFFICIAL]" from the thread title. The official thread already exists (it is stickied). Thanks for understanding!
Click to expand...
Click to collapse
My thread was published before the other one, but as you wish

PierreVicquery02 said:
My thread was published before the other one, but as you wish
Click to expand...
Click to collapse
The other one (official thread) was created on 25th November 2017 by Funk Wizard, when the first Open Beta was released. Ever since then, it has been used for announcing all subsequent Open Beta releases as well as gather feedback on them. Nonetheless, thanks for changing the thread title, I appreciate it!

Does any one have any idea how I can enable full screen gestures for OnePlus 5?
I flashed the open beta build and tries enabling on screen navigation buttons but it's giving me the old buttons
I tried using
adb shell settings put secure swipe_up_to_switch_apps_enabled 1
as it used to work on OOS 9, but this has no effect on the current open beta build
Thanks in advance

The wifi is randomly dropping for me then reconnecting. That happens quite often,anyone else experiencing it? I'm full stock with locked bootloader,haven't done a factory reset though.

this beta ROM can pass safety net with magisk?

fedex_742 said:
this beta ROM can pass safety net with magisk?
Click to expand...
Click to collapse
Somebody passes, somebody not. I don't know why.

Open Beta 14 is Out Now

Open Beta 14 is out
Changelog
System
• Fix the problem that some software voice input cannot be recognized
• Fix the problem of the disappearance of contacts in the address book on some devices
• More clock style options now available in ambient display (Settings -- Customization --Clock style)
• Improved system stability and fixed general issues
• Updated Android security patch to 2020.05
Phone
• Now you can view call recording in call history (move to the call history, click the three-dot menu on the upper right to access the call recording)

we need the full rom zip

i6rb said:
we need the full rom zip
Click to expand...
Click to collapse
http://otafsg1.h2os.com/patch/amazo...35_OTA_035_all_2005122203_dfb6c8f59826ca0.zip

just intalled from the stable, works fine, no data lost

I can't get Magisk to work, anyone else? Tried both the normal release and canary.

What are the correct steps to flash from one beta to another, when you are rooted, and would like to keep root?? Thanks.

Went to download and it says beta 13

Tr4il said:
I can't get Magisk to work, anyone else? Tried both the normal release and canary.
Click to expand...
Click to collapse
Works for me. I downloaded the zip from oxegyn updater, flashed it in TWRP, wiped dalvik, flashed TWRP (not sure if necessary), wiped dalvik, flashed magisk, changed partition to B, restarted to recovery again, flashed magisk again and rebooted. All as fine. Dirty install too.

mexiken said:
What are the correct steps to flash from one beta to another, when you are rooted, and would like to keep root?? Thanks.
Click to expand...
Click to collapse
carnivalrejectq said:
Works for me. I downloaded the zip from oxegyn updater, flashed it in TWRP, wiped dalvik, flashed TWRP (not sure if necessary), wiped dalvik, flashed magisk, changed partition to B, restarted to recovery again, flashed magisk again and rebooted. All as fine. Dirty install too.
Click to expand...
Click to collapse
Your doing too many steps...
Install from update(don't reboot)
Install TWRP from magisk manager(install from storage)(don't reboot)
Install magisk( install to inactive slot after OTA)
Reboot

lbcoach3347 said:
Went to download and it says beta 13
Click to expand...
Click to collapse
The file name contains a "13" but it is not beta 13.
Sent from my OnePlus7Pro using XDA Labs

lollyjay said:
The file name contains a "13" but it is not beta 13.
Click to expand...
Click to collapse
Will this wipe everything it just update to 14 from 13

Greatness83 said:
Your doing too many steps...
Install from update(don't reboot)
Install TWRP from magisk manager(install from storage)(don't reboot)
Install magisk( install to inactive slot after OTA)
Reboot
Click to expand...
Click to collapse
I actually make both slots identical.
Local install of OS
Install Magisk after OTA
Reboot
Local install of the OS (might fail the first time, do it again)
Flash TWRP in Magisk
Direct install of Magisk
OTA install of Magisk.
Reboot
Now both slots are bootable with the same OS and rooted.

Greatness83 said:
Your doing too many steps...
Install from update(don't reboot)
Install TWRP from magisk manager(install from storage)(don't reboot)
Install magisk( install to inactive slot after OTA)
Reboot
Click to expand...
Click to collapse
that screwed me up once, now i flash twrp from magisk, then reboot to recovery and flash magisk

lbcoach3347 said:
Will this wipe everything it just update to 14 from 13
Click to expand...
Click to collapse
Just update.
Sent from my OnePlus7Pro using XDA Labs

Did OnePlus pull the update? No longer shows up for me

Pubg automatically closing without any notification on oxygen os beta Latest and even previous beta.. Any fix ??
Please help

It looks like the "clock style" is the first step toward the incoming AOD

Greatness83 said:
Did OnePlus pull the update? No longer shows up for me
Click to expand...
Click to collapse
Yes. I don't know the reason why but hope it's nothing too bad cause I already installed it.
https://www.xda-developers.com/onep...-ambient-display-clocks-may-2020-patches/?r=2

tnmsrkr said:
Pubg automatically closing without any notification on oxygen os beta Latest and even previous beta.. Any fix ??
Please help
Click to expand...
Click to collapse
Happening with me too here.
Found a fix ?

[Pulled back] OnePlus 7 and OnePlus 7T series OxygenOS Open Beta 14
Shortly after this article was published,
OnePlus has pulled back all the builds.(OxygenOS Open Beta 14)
The reason for this is unknown,
but a reasonable guess could be that there may be a showstopper bug present on them.
original link:
https://www.xda-developers.com/oneplus-7-oneplus-7t-series-oxygenos-open-beta-14-4-ambient-display-clocks-may-2020-patches/?r=2

Magisk v22.0 update confusion

So i was minding my own business then i notice "Magisk Manager" have red dot notification on it's icon upon opening there's update for "Magisk Manager" app and "Magisk" itself... so i decided to first Install the "Magisk Manager" update and it went real smooth
but when i try to update Magisk itsaid "Magisk Manager is Dead. Love live the Magisk app" then it ask me for Method
"Select and Patch file" or "Direct Install" now at this point idk what to do. I have at least done 3x Magisk update installation already it never ask me this option also when i try download root checker on playstore itsaid im rooted i just want to update Magisk should i patch my stock boot.img again or what??

For me this has been the case all this time for Magisk updates - I get that choice, and I choose 'direct install'. This time also I chose the same - 'direct install'. It got installed and prompted me to reboot.

scarmage said:
For me this has been the case all this time for Magisk updates - I get that choice, and I choose 'direct install'. This time also I chose the same - 'direct install'. It got installed and prompted me to reboot.
Click to expand...
Click to collapse
clicking Direct Install doesn't do anything

This is what my Magisk Manager look like before i update it to v22.0
https://ibb.co/gvPzDs7
Now after i update it to Magisk Manager V22.0 i can't update Magisk
https://ibb.co/HXLCvLS

You can try going to the Magisk GitHub and download the app and install it through file manager and try updating again. I did that accidentally and had no issues installing.

dl200010 said:
You can try going to the Magisk GitHub and download the app and install it through file manager and try updating again. I did that accidentally and had no issues installing.
Click to expand...
Click to collapse
I have the app already but after they decided to merge Magisk Manager and Magisk in just one apps i can't update Magisk anymore also i have stock boot.img of my device that i have previously patched via Magisk so it's just unusual for Magisk Manager to ask me again ...

ineedroot69 said:
I have the app already but after they decided to merge Magisk Manager and Magisk in just one apps i can't update Magisk anymore also i have stock boot.img of my device that i have previously patched via Magisk so it's just unusual for Magisk Manager to ask me again ...
Click to expand...
Click to collapse
I downloaded the apk from GitHub and installed it over the updated one. I was able to do a direct update. I was just suggesting it. Couldn't hurt to try it.

dl200010 said:
I downloaded the apk from GitHub and installed it over the updated one. I was able to do a direct update. I was just suggesting it. Couldn't hurt to try it.
Click to expand...
Click to collapse
Same here. Worked on Xiaomi Note 10 Pro (Tucana) with Android 10.
Did not work on Xiaomi Mi 10 Lite 5G (Monet) with Android 11. (The phone booted into fastboot-mode, so I had to extract the original boot.img from an original ROM and flashed it via fastboot-command to get the phone back booting to system).

PrussianWolf said:
Same here. Worked on Xiaomi Note 10 Pro (Tucana) with Android 10.
Did not work on Xiaomi Mi 10 Lite 5G (Monet) with Android 11. (The phone booted into fastboot-mode, so I had to extract the original boot.img from an original ROM and flashed it via fastboot-command to get the phone back booting to system).
Click to expand...
Click to collapse
Can you tell more? How did you extract the boot.img? Did you get it from the newest Android full OTA? DId it just straight up work after flashing the new boot.img? I'm asumming it was an unpatched one, right?

PrussianWolf said:
Same here. Worked on Xiaomi Note 10 Pro (Tucana) with Android 10.
Did not work on Xiaomi Mi 10 Lite 5G (Monet) with Android 11. (The phone booted into fastboot-mode, so I had to extract the original boot.img from an original ROM and flashed it via fastboot-command to get the phone back booting to system).
Click to expand...
Click to collapse
How do I flash a ROM from bootloader? I am on Xiaomi Redmi Note 4 (mido) and have the same issue. Device won't boot into anything except fastboot. I tried flashing recovery using fastboot flash recovery <reccovery>.img but it got stuck in bootloop again.

ineedroot69 said:
This is what my Magisk Manager look like before i update it to v22.0
https://ibb.co/gvPzDs7
Now after i update it to Magisk Manager V22.0 i can't update Magisk
https://ibb.co/HXLCvLS
Click to expand...
Click to collapse
Exactly the same experience as OP here.
I am at exactly this stage as well..oneplus 6T; rooted; stock image.
Not sure what to do next?
Thanks in anticipation.
~S.O

where is the "Download zip only" option ?

VangelisGi said:
where is the "Download zip only" option ?
Click to expand...
Click to collapse
There isn't one, because there is no separate zip anymore:
https://topjohnwu.github.io/Magisk/releases/22000.html

Why?
I'm so confused.
I'm on Lineageos 17 on Oneplus 6
I used to install magisk with the zip and it went smoothly now I don't have the option anymore..
How can you do when you use OTA update?

Cygnust said:
Why?
I'm so confused.
I'm on Lineageos 17 on Oneplus 6
I used to install magisk with the zip and it went smoothly now I don't have the option anymore..
How can you do when you use OTA update?
Click to expand...
Click to collapse
It's all explained in the link posted right above your post...
Spoiler: rename the .apk to .zip.

Didgeridoohan said:
It's all explained in the link posted right above your post...
Spoiler: rename the .apk to .zip.
Click to expand...
Click to collapse
Sorry, I skipped that part and when directly to the one saying you had to patch BOOT.IMG..
Many thanks

Didgeridoohan;
I understand that the 'Manager' now has become the 'App'. I also understand to just rename the '.apk' file to '.zip' to flash from an OTA update event. I also understand that the '.apk' now with this latest release has everything you need to install Magisk.
I have had Magisk already installed like this: https://ibb.co/gvPzDs7
So, after I updated, can I ask what do I do about the problem of 'update' indicating via the Magisk Home page on the App?
I mean now I have this: https://ibb.co/HXLCvLS
Just don't worry about it?
Thank-you for your help.

sprocketoctopus said:
Didgeridoohan;
I understand that the 'Manager' now has become the 'App'. I also understand to just rename the '.apk' file to '.zip' to flash from an OTA update event. I also understand that the '.apk' now with this latest release has everything you need to install Magisk.
I have had Magisk already installed like this: https://ibb.co/gvPzDs7
So, after I updated, can I ask what do I do about the problem of 'update' indicating via the Magisk Home page on the App?
I mean now I have this: https://ibb.co/HXLCvLS
Just don't worry about it?
Thank-you for your help.
Click to expand...
Click to collapse
Magisk still consists of two parts, Magisk app and Magisk internals, they're now just distributed together.
What your screenshot shows is that you've now updated the app, but not yet the internals...

Do not update simply as the update is Device bricking.
Magisk 22.0 update killed phone will only boot into fastboot
Have never had an issue went to update to latest Magisk app, followed directions and restored it first, everything seemed fine, then went to flash Magisk itself from the app (Direct install) like always, didn't seem to do anything, checked the...
forum.xda-developers.com

I updated my magisk to version 22, and it looks ok, except for the bottom menu that disappeared, does anyone know where it went or is it a bug?