[ROM][N960F/DS/N][ALEXNDR] * U9FVC2 * DevBase v7.4 * DeX, Gear & Encryption support

[@casper]

Hi all, I'm wondering if it is still a requirement to use twrp 3.2.3 to utilize encryption feature or if it works with twrp 3.6.0_9?

It s working on twrp 3.6.0_9. I have tired.

 

[brusyev]

Thread has been updated, U9FUK1 (One UI v2.5) DevBase v7.4 (November security patches, changelist 22750344)

Download ROM:

SM-N960F/DS:

(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

SM-N960F/DS:


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)

Thank you for this update _alexndr. Unfortunately like others on here have stated the link to rom says there are no servers available for download.

 

[francois095]

Thank you for this update _alexndr. Unfortunately like others on here have stated the link to rom says there are no servers available for download.

N960FXXU9FUK1_DevBase_v7.4

MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.

www.mediafire.com

 

[brusyev]

N960FXXU9FUK1_DevBase_v7.4

MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.

www.mediafire.com

I appreciate the link but I will be downloading from original source only.

 

[jollmo]

I appreciate the link but I will be downloading from original source only.

Why not check the MD5 after download? Should be d1c12327f5a5a3c586170fd901e2ff55

 

[kramer04]

Hello,
sorry to be OT but how to clean dalvik cache on recovery as we can't mount data into recovery ?

 

[lezig]

Hi Alexndr,

Tks, like usual it's working like a charm !
Happy new year to you (& all of you out there).

 

[Arobase40]

February 2022 security update is finally available for Note9 -N960F !

https://samfrew.com/model/SM-N960F/region/DBT/

N960FXXS9FVB1-N960FOXM9FUK1-N960FXXS9FVB3

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... ^^

Good day

 

[zfk110]

I have written " (November security patches, changelist 22750344)", not December, so where is the problem?

Download​

N960FXXU9FUK1_DevBase_v7.4.zip​

for the Samsung Galaxy Note 9(SM-N960F), by alexndr



OOPS!
no mirrors found.



I have been trying since morning

 

[jet_iso]

Download​

N960FXXU9FUK1_DevBase_v7.4.zip​

for the Samsung Galaxy Note 9(SM-N960F), by alexndr



OOPS!
no mirrors found.



I have been trying since morning

You can download from mediafire link that a user shared. You can check the md5.

 

[@casper]

Any update ?

 

[_alexndr]

February 2022 security update is finally available for Note9 -N960F !

https://samfrew.com/model/SM-N960F/region/DBT/

N960FXXS9FVB1-N960FOXM9FUK1-N960FXXS9FVB3

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... ^^

Good day

Does anybody tested Magisk v24.3 update with DevBase ?? I'm wondering if it's worh to put it as default in DevBase installer

Can't test it myself because my current device is S21 Ultra (not rooted)

 

[Clayman_32]

Does anybody tested Magisk v24.3 update with DevBase ?? I'm wondering if it's worh to put it as default in DevBase installer

Can't test it myself because my current device is S21 Ultra (not rooted)

I use it all recent versions of Magisk (and currently v24.3) and all working perfectly.

 

[Arobase40]

Does anybody tested Magisk v24.3 update with DevBase ?? I'm wondering if it's worh to put it as default in DevBase installer

Can't test it myself because my current device is S21 Ultra (not rooted)

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 !!! ^^

 

[dr.ketan]

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.

 

[Arobase40]

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.

If you don't know what I have done it doesn't mean what I know what is working or not !
Magisk v23 doesn't work with A52S whether with A11 and A12 because of a fstab issue with Magisk POINT

I'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.
Samsung Health is working only partly as it works in the background and we can see how many steps we are walking in the notification bar, but we can't access the app in itself (once after each reboot and we can't change any settings in the app).
I even tested pre alpha versions of Magisk after v23, then alpha version and so on... ^^

I didn't wait after you to get Samsung Secure Folder working on the Note 9 when other Recognized users said it shouldn't work.
With A52S it's not only a matter of A12 because we got the same issue with A11 and Then Samsung decided to lock the camera when bootloader is unlocked in some countries and not some others !!! ^^
Samsung did the same with Flip 3 and Fold 3 devices but Samsung did finally released the bootloader unlocked for those devices but not with A52S !
There is even not logic of Samsung decision as we have different behaviors in different countries within the same Region such as in E.U.

Watch at this survey with A52S and you will be surprised about Samsung !

Survey of SM-A528B A52S 5g phones

Anyone who has disabled the bootloader of your phone only to find the camera has be rendered useless, please respond with your country and csc please. I'll start: I'm in the luxembourg region with csc LUX. This may be way to show Samsung how...

forum.xda-developers.com

If you think you know everything better than me I invite you to participate in our section and I won't feel upset.

I also invite you to build a custom ROM for this device as it is asked by many users...

I also invite any modders/dev capable to build a working TWRP for the same device to join us.

 

[dr.ketan]

I'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, 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
While S Health have different story, Security increased with App itself. 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 .Also to note that new security implement affects newer OS but not too old and non samsung devices. 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.+

 

[Arobase40]

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.+

Sorry mate, but you know nothing about A52S issue as using Magisk v23 with this device whether with A11 or A12 leads it to fall into a bootloop !!!! ^^

Then I guess you are messing up between A52 and A52S models ! ^^

Finally you recognize I was right about A12 and Samsung Health and Secure folder which won't work with Magisk v24 and the denyList... lol

I know about the framework level patch and I was about investigating it probably with the Smali patcher tool, but if you have another solution feel free to release your knowledge.

Now back on Note 9, I guess it is better to let users decide which version of Magisk he wants to install !

 

[Arobase40]

Still you are misunderstanding. Even Magisk 23.0 would have working, S Health & Secure Folder won't work.

Forgot to tell I have S Health & Secure Folder working with Magisk v23.0 BUT on Note 9 with Android 10 ! ^^

 

[dr.ketan]

Forgot to tell I have S Health & Secure Folder working with Magisk v23.0 BUT on Note 9 with Android 10 ! ^^

I guess you have issue reading so before ending discussion last time explain you
What I have said about S Health? Read again
"Also to note that new security implement affects newer OS but not too old"
That simply means A10 is not affected but A11 & A12 does (irrespective of Magisk version) and Note 9 still on A10 and that's why working.(Nothing to do with magisk)
If you use S Health version before this changes applied by Samsung, it will work with any version of Magisk. For example Samsung Health 6.19.5.017 or earlier to that will work on Magisk 24+ too.

Secure Folder working on N9 because it is still on A10 (Secure folder stopped working on rooted device without patch since A12) and will work with any version of Magisk.
Period.