Another good thing is that even if you Root magisk uninstall then whenever this room runs without Root ...thank you sooo much...I am using without root this Rom my mobile Note 960f
New Mars 2022 security update is available for Note9 -N960F !
N960FXXU9FVC2
PHN (Netherlands) CSC, and NEE (Nordic countries) CSC For now.
Once again available via Fija, Samfw or Samfrew or maybe any other sources...
N960FXXU9FVC2
PHN (Netherlands) CSC, and NEE (Nordic countries) CSC For now.
Once again available via Fija, Samfw or Samfrew or maybe any other sources...
Last edited:
Thread has been updated, U9FVC2 (One UI v2.5) DevBase v7.4 (February 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
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)
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
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)
Last edited:
You are right, I haven't checked it well enough before posting
so it is just another February update. I just edited mu previous postYou are right, I haven't checked it well enough before posting
I was about to post the same thing : "official" security update is February 2022. So it's not a mistake of mine...
Samsung really f** up !!!
Galaxy Tab S6 : T860 and T865 are locked on March 2022 updates when my A52S 5G is getting April 2022 update. ^^
[Guide] EdXposed - Xposed Framework for Android 9 & 10
||| Why this guide? ||| Since the "EdXposed" project doesn't reveice the attention it should get in our device section, I decided to make a quick guide for you how to get a Xposed Framework on your OnePlus 6 running Android 9 and 10! :highfive...
forum.xda-developers.com
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
I do that, it's work super thank you
How i can install Viper4android on this rom, i need magisk canary or not?
You dont need canary build. Just flash the last official build from github then flash viper (you can download it from github too).
If you fail or viper dont work, remove all, make a restart, flash magisk 23 then install viper from magisk repo. After you see viper without any problem you can update magisk without any problem.
Im using viper with magisk 24 on this rom currently. And there is no issue at all.
Edit: Dont forget to enable 'legacy mode' in viper settings.
New May 2022 security update is available for Note9 -N960F !
N960FXXS9FVE1
CSC DBT (Germany) For now.
I hope this is really May security update now and not March... ^^
Once again available via Fija, Samfw or Samfrew or maybe any other sources...
N960FXXS9FVE1
CSC DBT (Germany) For now.
I hope this is really May security update now and not March... ^^
Once again available via Fija, Samfw or Samfrew or maybe any other sources...
Last edited:
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
10Thread has been updated, S9FVE1 (One UI v2.5) DevBase v7.4 (May 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
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)2
Probably not yet available but you could kindly ask to OP to supply it... ^^1Thread has been updated, S9FVE1 (One UI v2.5) DevBase v7.4 (May 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
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)
Wonderful as I was awaiting after this Devbase update !!!1 -
93Important notes for Developers / Chefs !!!
Hello
I have decided to create a pure base with my unified installer (should work with many other Samsung devices), which can be a pattern for ROM Chefs (not only for beginners) ROM is initially safe de-bloated (read below what does it exactly mean), but all features are present and works!
ROM can be installed by normal users as well. If you like a little de-bloated ROMs, clean, but with all working features - there is no better alternative I think
ROM for N960F/DS contains OXM multi CSC package, list of available CSCs is as follow:
ACR, AFG, AFR, ATO, AUT, BGL, BNG, BRI, BTC, BTU, CAC, CAM, CPW, DBT, DKR, ECT, EGY, EUR, GLB, ILO, INS, ITV, KSA, LAO, LUX, LYS, MAT, MID, MM1, MTL, MWD, MYM, NEE, NPL, NZC, OPS, ORX, PAN, PAK, PHE, PHN, PNG, PRO, ROM, SEB, SEE, SEK, SIN, SKZ, SLK, SMA, SMP, STH, TEB, TEL, THL, THR, TMC, TNZ, TPH, TUN, TUR, VAU, VFJ, VNZ, WTL, XEF, XEH, XEO, XEU, XEZ, XFA, XFE, XID, XME, XNX, XNZ, XSA, XSG, XSP, XTC, XXV, XNF
ROM for N960N contains OKR multi CSC package, list of available CSCs is as follow: KOO, KTC, LUC, SKC
NEW !!! I present you new, unique option: "Keep current CSC", so you can install my DevBase keeping your original CSC even if it is not listed above! Note that in such case this option has some limitations - more informations you can find in related older threads, e.g. HERE
ALEXNDR.N960FXXS9FVE1:
1. Base:
- Odexed (original stock files) + stock kernel
- Multi CSC OXM (list of natively supported CSC as above) (*)
- Removed KNOX related content (useless on rooted phones)
- Removed Rlc.apk & vaultkeeperd (to avoid "OEM unlock issue")
- Rooted systemlessly (Magisk v23.0) (*)
- All original features are present and works (except KNOX related apps)
- Added "App Lock" feature (Settings -> Advanced features)
- No visual changes (100% stock look)
2. CscFeature MOD (enabled some built-in, hidden features):
- Added shutter sound menu in Camera app
- Sending/receiving MMS without data on
- Show SMS/MMS sending time instead of receiving
- Added "Call/Message block" option in Settings
- Added "Show network speed" toggle (Settings -> Display -> Status bar)
- Added "LTE Only" network mode (NOTE: voice calls may not work in this mode)
- 4G/3G network support in any CSC (master/slave SIM, applies to dual SIM variants)
- Call Recording (via "Record" button or "Auto record calls" option)
- Enabled "Recent App Protection" feature
3. Xposed framework & Xposed Installer app [optional] (*)
- NOTE: Applies to Oreo DevBase. There is no Xposed for Pie yet
4. Virtual / physical Safe De-Bloat (more info below) (*)
(*) - these options can be controlled by editing options.prop file (you can find such file in ZIP's root directory). Just place modified options.prop file (use e.g. Notepad++ to edit) in the root directory of internal emulated scdard (/data/media/0) or extSdCard (recommended if you plan to format internal emulated sdcard) and then start the installation. More info below:
NEW !!! Starting from DevBase v3.0 there is a new customization method - you can change frequently switched root options or encrypt your device just by renaming installer's ZIP file name (instead of editing options.prop file). Currently supported "strings" in the file name: "noroot", "encrypt", "rescue", "xposed", "CSC_xxxx.zip":
Case 1 (default) - install the ROM with Magisk & MagiskSU as root solution
(just flash ZIP file "as it is")
Case 2 - do not root device
(place "noroot" string anywhere in the ZIP file name, e.g. "N960Fxxx_DevBase_v6.x_noroot.zip")
Regardless of the above root options, starting from DevBase v4.4+, you can also use "encrypt" option (place "encrypt" string anywhere in the ZIP file name, e.g. "N960Fxxx_DevBase_v6.x_encrypt.zip"). All your data will be encrypted "on-the-fly" at next boot after ROM update/reinstall. Wipe data is NOT necessary to use this option. You will NOT lose your data & apps but it is extremely important - do not interrupt encryption process during this "special" boot! Booting can take much longer and you may think it is a bootloop, but it isn't! If you have a large amount of used data - it is recommended to connect your phone to the charger during boot (and open a beer to avoid heart attack while waiting). You do not need to use "encrypt" option again in case of another DevBase update(s) - please read carefully notes below.
In DevBase ROM v4.5+ there is a "rescue" option, which may be especially helpful in case of encrypted device if you experienced bootloop caused by e.g. systemless mod/module/xposed stored on /data (without access to /data from TWRP). In case of bootloop just place "rescue" string anywhere in the ZIP file name, e.g. "N960Fxxx_DevBase_v6.x_rescue.zip" and then (re)install the ROM - should help in case of (probably) all possible bootloop reasons. In addition to the normal (re)installation of the ROM (thus restoring the original /system, kernel, modem, etc.) this option will also force "Core Only Mode" in Magisk and will move all SYSTEMLESS DevBase modifications to /data/devbase/system/.backup, before performing bind mounts, so original files will be used.
In DevBase ROM v4.6+ there is a possibility to force CSC by renaming ZIP file name - this is the only case-sensitive variable which have to be put at the beginning of ZIP file name and must be folloed by "_" (due to the fact that there is a high risk that ZIP file name may contain CSC code accidentally). Example (to force CSC DBT): "DBT_N960Fxxx_DevBase_v6.x.zip"
In DevBase ROM v5.6+ there is "xposed" option which allows you to force Xposed framework installation. It is NOT forced by default - you need to force it manually while installing ROM with Xposed first time, renaming ZIP's file name to e.g. "N960Fxxx_DevBase_v6.x_xposed.zip". Next ROM's updates will detect and apply Xposed profile automatically, unless you wipe /system - then auto detection is not possible.
Notes related to encrypted devices:
Notes related to EFS backup:
Installation:
TWRP recovery (KNOX 0x1): open file using "Install (Zip)" option and confirm operation. If you want to perform "clean install' - perform "wipe data/factory reset" BEFORE flashing Zip!
Wipe data is NOT required if you are coming from stock ROM (already rooted) or a previous version of my DevBase (if you leave "Keep current CSC" option untouched in /options.prop or if you choose same CSC as you are currently using). In other cases - wipe data is highly recommended!
I do not recommend using any additional "superwipes" or format /system before install my DevBase (my installer cleans your system well enough!).
Credits:
@samsung for awesome device & stock firmware base
@Chainfire for systemless SuperSU and a lot of inspiration
@topjohnwu for Magisk and another inspiration
@rovo89 for Xposed framework & Xposed Installer app
@dr.ketan for being helpful whenever needed
@Zackptg5, @osm0sis & @jcadduono for no-verity*
@corsicanu & @geiti94 for TWRP recovery
@fei-ke for omc-decoder
Hit Thanks button if you like my work. If you really appreciate my work - feel free buy me a coffee/beer (or flowers/wine for my wife who is patiently enduring my hobbies) https://www.paypal.com/donate/?business=RFGVQYRC34RVQ¤cy_code=EUR
Due to the fact, that some countries banned PayPal - I have created also Patreon site: https://www.patreon.com/_alexndr38Download ROM
SM-N960F/DS:
>> N960FXXS9FVE1_DevBase_v7.4.zip << (Android 10, updated Apr-24-2022, more info HERE)
SM-N960N:
>> N960NKSU3FVA1_DevBase_v7.4.zip << (Android 10, updated Mar-25-2022, more info HERE)
SM-N96xF/DS/FD/N repository:
>> Note 9 repository << [ AFH | MediaFire ]
Note:
Check MD5 sum BEFORE flash (useful TOOL), because flashing damaged or incomplete ZIP files could (soft) brick your phone! Correct MD5 sum is shown on the AndroidFileHost website while downloading.27Thread has been updated, U4DSLB (Android Q) DevBase v7.0 (December security patches, changelist 17594460)
As usual - you can dirty flash it over previous version :good:
Download ROM:
SM-N960F/DS:
NOTE1: If you are on Pie or older bootloader, then after flashing the ROM it is mandatory to flash also Android Q bootloader - otherwise device will not boot with Android Q based ROM!
NOTE2: It is highly recommended to use TWRP 3.2.3.0 (e.g. THIS build). For some reason there is "make_ext4fs: not found" error in newer TWRP versions and in result "Failed! Not enough space..." appears while applying CSC (CSC content will be incomplete). Note 9 is the only device with this issue and I'm not able to play with it because I do not have N960F device phisically. More info HERE
NOTE3: If you want to perform clean install with encryption - it is highly recommended to use TWRP 3.2.3.0 to format /data. More info about bug with TWRP 3.3.1.x - HERE21Thread has been updated, U5DTCA (Android Q) DevBase v7.3 (April security patches, changelist 18063799)
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
NOTE2: Dirty flash over Pie BevBase is also possible without issues, but before you try - I would highly recommend you to set default (stock) theme, set default (stock) icons and temporarily disable all Magisk's modules (or just enable "Magisk Core Only Mode") !!! However, before you report any problem, please try if it occurs also after clean install to let me know if it is related to dirty update or the ROM itself.
NOTE3: If you want to perform clean install with encryption - it is highly recommended to use TWRP 3.2.3.0 (e.g. THIS build) to format /data. More info about bug with TWRP 3.3.1.x - HERE
NOTE4: 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"21Thread has been updated, S4CSK2 DevBase v6.0 (December security patches, changelist 16685647)
As usual - you can dirty flash it over previous version -> DONE, that's all :good:
Download ROM:
SM-N960F/DS:
(you can find bootloader in my updated repository, but BL update is not mandatory)
