Thread has been updated, U9FUK1 (One UI v2.5) DevBase v7.4 (November security patches, changelist 22750344)
(BL update is not necessary if you are on any Q bootloader already)
NOTE1: If your current bootloader is Pie or older - it is mandatory to update bootloader to Q - otherwise ROM will not boot. Flashing order is not very important, but it is much better to flash ROM as first and then BL - one by one - due to auto reboot command at the end of BL flashing script
NOTE2: Note that if something will go wrong then you will not be able to restore standard System backup. To avoid problems with restoring backup(s) you need to perform following backups: (1) "System Image" (NOT "System" !!!), (2) "Data (excl. storage)", (3) "Boot", (4) "Baseband", (5) "Vendor Image", (6) "Carrier Configs" (ODM Image)
I appreciate the link but I will be downloading from original source only.
February 2022 security update is finally available for Note9 -N960F !
Available also for many other countries.
EDIT : also available for Note9 - N960N !
EDIT 2 : N960N Note 9 is receiving January 2022 security update and not February security update... ^^
I use it all recent versions of Magisk (and currently v24.3) and all working perfectly.
If you don't know how to use doesn't mean it's not working.Hi _alexndr
I'm using Magisk v24.3 with a Galaxy A52S 5G and it is a real mess as Magisk Hide is not working as it does with Magisk v23, so no access to Samsung Health or Samsung Secure Folder and most other Samsung proprietaries functions or apps.
Using Magisk v23 leads with Galaxy A52S 5G to fall into a bootloop, so no real choice.
But Magisk v23 is still the best with the galaxy Note 9 !
So, please, don't put Magisk v24.x as default with devBase !!! ^^
If you don't know how to use doesn't mean it's not working.
Magisk 24.3 (known as zygisk) have magisk hide and that is now known as "deny list"
Samsung health and Secure folder has nothing to do with Magisk. Android Q doesn't require fix. What you have mentioned about A52S magisk v23 not working likely have A12. And Samsung health and secure folder on A12 needs fix irrespective of magisk.
Magisk 24.3 (zygisk) is much better than old one. Needs to install zygisk version of Safetynet fix and use "deny list" as magisk hide and everything will be fine.
Still you are misunderstanding. Even Magisk 23.0 would have working, Secure Folder won't work. Not only on A52 but with A12 all devices have working Secure folder (without patch) have stopped working since A12 e.g N10,N20, S21I'm using Magisk v24.x with my A52S and I made a guide to explain how to use it to root this device as I spent many hours and days to test it in different ways. I know about Zygist and the deny list, LSPosed-zygist module and SafetyNet fix but once again this is not enough to get Samsung Health and Secure Folder working all together with AFWall++, Xprivacu=yLua and Firefds Kit S. The second part is working but not the first one.
Still you are misunderstanding. Even Magisk 23.0 would have working, S Health & Secure Folder won't work. Not only on A52 but with A12 all devices have working Secure folder (without patch) have stopped working since A12 e.g N10,N20, S21
Samsung health been checking different way and that can not be hide by Magisk. I have reported this very early on couple of days of samsung have released S Health with new security update, you can read here Same way Secure Folder can't be fix with magisk hide or lsposed on A12 but needs a framework level patch.
Thanks for inviting but I do not have time to support new device nor I have said device, but all my ROM (N10,N20,S21,S22) running A12 (4.0 to 4.1) have running S Health & Secure folder with Magisk 24.+
I guess you have issue reading so before ending discussion last time explain you
Download Magisk-v24.2.apk rename to Magisk-v24.2.zip and flash via TWRP has fixed it for me. After that update to 24.3 vie magisk manager
For some reason I lost root after installing latest C2 version. Magisk is showing not installed and when I try to install the zip from magisk manager I get an error "unable to detect target image. Does anyone know how to fix try
You dont need canary build. Just flash the last official build from github then flash viper (you can download it from github too).
zip -r -9 N960FXXUxxxxx_DevBase.zip META-INF options.prop ALEXNDR