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

Search This thread
By:
Advanced…
@casper

@casper

Member
Oct 4, 2014
49
13
_alexndr said:
Thread has been updated, S9FVE1 (One UI v2.5) DevBase v7.4 (May security patches, changelist 22750344) :cool:

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)
Click to expand...
Click to collapse
Hello, will you release a new update?
 
  • Like
Reactions: RamHa
_alexndr

_alexndr

Senior Member
Mar 1, 2013
2,850
17,946
Samsung Galaxy S23 Ultra
Thread has been updated, U9FVH1 (One UI v2.5) DevBase v7.4 (July security patches, changelist 24343300) :cool:

Download ROM:

SM-N960F/DS:
>> N960FXXU9FVH1_DevBase_v7.4.zip <<
Click to expand...
Click to collapse

(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)
 
  • Like
Reactions: brusyev, alicavush, Craig_D and 10 others
A

Arobase404

Member
Sep 13, 2022
46
11
_alexndr said:
Thread has been updated, U9FVH1 (One UI v2.5) DevBase v7.4 (July security patches, changelist 24343300) :cool:

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)
Click to expand...
Click to collapse

Youpiiiii !!!

And thank you sooo much _alexndr !!!
 
  • Like
Reactions: brusyev and lezig
lezig

lezig

Member
Jan 7, 2014
21
11
_alexndr said:
Thread has been updated, U9FVH1 (One UI v2.5) DevBase v7.4 (July security patches, changelist 24343300) :cool:

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)
Click to expand...
Click to collapse
Merci !!! Thank you sooo very much @_alexndr !!!
 
B

brusyev

Senior Member
Aug 27, 2010
254
12
_alexndr said:
Thread has been updated, U9FVH1 (One UI v2.5) DevBase v7.4 (July security patches, changelist 24343300) :cool:

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)
Click to expand...
Click to collapse
Alexndr thank you so much for this latest update.
 
  • Like
Reactions: lezig
T

TurricanM3

Senior Member
Feb 4, 2015
922
244
No i meant to reset the cycle counter like samsung service would do to tell the phone there has been a new battery installed. Otherwise you are not using the full potential of it.
 
  • Like
Reactions: lezig
Craig_D

Craig_D

Senior Member
Apr 30, 2015
301
80
Glasgow
Samsung Galaxy S4
Samsung Galaxy Note 3
TurricanM3 said:
Did you reset the charge cycles? Otherwise it will use the old reduced mAh.
Click to expand...
Click to collapse

If you mean, did I fully charge and discharge several times, switching on and letting it die again at 0% before fully charging etc etc, yes I did. I've noticed a dramatic improvement obb
TurricanM3 said:
No i meant to reset the cycle counter like samsung service would do to tell the phone there has been a new battery installed. Otherwise you are not using the full potential of it.
Click to expand...
Click to collapse
No idea 🤷‍♂️
 
Craig_D

Craig_D

Senior Member
Apr 30, 2015
301
80
Glasgow
Samsung Galaxy S4
Samsung Galaxy Note 3
  • Like
Reactions: alicavush
Craig_D

Craig_D

Senior Member
Apr 30, 2015
301
80
Glasgow
Samsung Galaxy S4
Samsung Galaxy Note 3
Clayman_32 said:
How to do that?
Click to expand...
Click to collapse
the info can be found in this thread...


forum.xda-developers.com

Reset battery cycle counter on Samsung Galaxy S7

Hello to the pro's here. Is it possible to reset the phone batt_cycle entry? Reason: after changing the battery I realized that the new one (original Samsung as far as I can tell with man. Date 11/2017) does not perform as expected. The...
forum.xda-developers.com forum.xda-developers.com


It requires translating German (via Google Translate) and editing a text file (again, Google is your friend) I managed it but it threw up some issues of a couple of apps not running properly afterward (no idea why) I just flashed the latest DevBase again and all was fine. My charge cycle is/was 28 now.

NOTE: if you change out the battery for a new one with a different capacity then you will need to follow the advice on this post...


forum.xda-developers.com

How to change your battery capacity

(Must be rooted) Use Root Explorer or Equivalent. (Can adb or command pull/ push with line if your know how inside twrp or on pc) DIRECTORY: /etc/floating_feature.xml Open it and Scroll or search until you see the capacity String value ...
forum.xda-developers.com forum.xda-developers.com


I haven't managed to do this though as, well, I'm not clever enough 🤪

I wish there was clearer information on all of this. Perhaps there is but I haven't found it.


I AM NOT RESPONSIBLE FOR ANY PROBLEMS YOU MAY ENCOUNTER. I AM SIMPLY OFFERING UP THE INFORMATION I FOUND AND THE DETAILS I FOLLOWED. IT IS ENTIRELY UP TO YOU WHETHER YOU FOLLOW IT OR NOT AND YOU ARE RESPONSIBLE FOR ANY PROBLEMS YOU ENCOUNTER.
 
  • Like
Reactions: Clayman_32
You must log in or register to reply here.

Similar threads

dr.ketan
[23.04.22] [OneUI 2.5] N960F_DS_N I Dr.Ketan ROM I SecureFolder I SPay (Gear) I Dex
Replies
10K
Views
796K
C
Carenlas706
AlexisXDA
[NOBLE ROM 3.4 SERRA OneUI 5.1 FULL PORT][05/23 Patches][19/05/2023][SM-N960F/FD/N--SM-G96xF/FD/N]
Replies
5K
Views
812K
S
sasho_purata
AlexisXDA
[Alexis Rom 3.4_FVh1][22/08/2022][08/2022 Patches][N960F/FD OneUI3.0 Apps Ported]
Replies
845
Views
194K
o0o.paw
o0o.paw
Dovanchuc7521
[ROM] [10] [RC] [SecureFolder]Galaxy Note9 [N960F/DS/N] SUPERSTABLE ROM UI2.5 V19(17/07/2021)
Replies
885
Views
141K
D
Dino-Rhino
freeza
[Kernel|TH4|Android 10]BeastMode Kernel vR154 for N960F (Linux 4.9.236)
Replies
877
Views
111K
dnmull
dnmull

Top Liked Posts

24 Hours 30 Days All time
  • There are no posts matching your filters.
  • 1
    J
    jet_iso
    dj_ooms said:
    I have a weird issue. I had been using the DevBase 7.4 based on FVH1 for some time without any issues and then decided to upgrade to DevBase 7.4 based on SAFWB3. I did a dirty flash and had been experiencing random reboots for a few days and then decided to do a clean flash of the SAFWB3 base. When I did this, the phone started up without any mobile reception and had a popup about no IMEI number. I thought it might be the firmware so tried again using the FVH1 base and still had the same issue. I then tried to put "Rescue" in the filename for the SAFWB3 base and this gave me reception but I was still experiencing random reboots on a clean install. I then tried "Rescue" in the filename for the FVH1 base but ended up with no reception again.

    I thought I would then try and AOSP based ROM to see if I had any issues and reception worked fine on these ROMs so I thought it might be something corrupted when flashing the DevBase ROMs. I thought I would do what I normally do when I break something and that is to do a clean install of the OS using Odin. When I did this I had the same issue and ended up with no IMEI number. This has normally worked for me in the past when I have broken something but I can't get it to work. I even tried restoring my EFS from a TWRP backup but ended up with a bootloop so had to wipe and do a fresh install to get the phone to startup again.

    I have now had to settle with using an AOSP based ROM as this is my only phone and I need to be contactable. I really want to go back to stock but don't really know what to do now. Is anyone able to advise what I can do to get the phone running normally with this ROM?

    Thanks in advance and sorry for the long post.
    Click to expand...
    Click to collapse
    Try install the last official firmware with home_csc in odin. Check your cable too. It may caused by data transfer... I've resolved a same problem once. Good luck.
    View
    1
    A
    Arobase404
    oldman20 said:
    Why need unmount system before install magisk?
    Click to expand...
    Click to collapse
    Because this is how it should be done, otherwise you'll get an error and Magisk won't install !!!

    oldman20 said:
    And what's base off DevBase 7.4? FVK1 (lastest) or older? @_alexndr Sir?
    Click to expand...
    Click to collapse
    FVK1 is older than FWB3 !

    oldman20 said:
    After odin to stock FVK1 From DevBase 7.4 my IMEI gone, i used efs backup from devbase create, or backed up from twrp but still cant get back IMEI. How can i get it back now?
    Click to expand...
    Click to collapse

    First make sure the options.prop file is correctly setup as described in OP !

    If you're still with a Devbase custom rom with TWRP, and if you still have an older TWRP backup, then restore the EFS partition from there and reboot.

    If your IMEI is still missing, remove you SIM card and reboot. Wait a while and put your SIM card back and see if you retrieve your IMEI.

    If not, make sure you have a full TRWP backup (including your data partition), and optionally a SmartWitch backup to an external media : micro SD or USB device.

    Make sure you have internet connection : data mobile and/or wifi

    Download and install an official Samsung firmware with PC Odin (FVK1 with your current CSC). You can try both HOME_CSC or normal CSC ( you may lose your data so the reason of the backup). Do all settings including the OEM and USB debug options in Developer mode.

    Once again make sure you have an internet connection and thus set up your wifi.

    Watch at your IMEI and if it's not back, try to remove your SIM card and put it back after a few minutes. It may take a while before it comes back.

    If all is fine, reboot in Download mode, and flash the latest TWRP available. Once again it may ask you to format your data partition. So do it and reboot. Once again you may have to rebuild all your settings...

    Finally, reboot in TWRP mode and flash the Devbase rom you want and see if all is working fine.

    It may take a few long minutes before it boots up in your working system.

    Reboot in TWRP mode, and flash the Magisk module as described above and optionally restore your latest Data partition backup.

    I understand it's a long and boring procedure but this is what you have to do after messing up your whole system... ;)

    EDIT : Forgot to say all this is available with International Galaxy Note 9 (N960F) !!!
    If you have a GNote 9 from elsewhere then use the official firmware and Devbase rom from your actual place.

    This procedure should NOT work with US mobile Phone as you might guess !!!
    View
    1
    A
    Arobase404
    oldman20 said:
    Thank, what is region of FWB3?
    Click to expand...
    Click to collapse

    This is for Great Britain.

    But if you use @_alexndr's Devbase rom make sure you set your options.prop file to keep your current CSC.

    If you flash an official Samsung firmware, then use the HOME_CSC to keep your data and your CSC.

    But for some unknown reasons, it can erase your data randomly... the reason of the need to do a full TWRP backup and more specifically your data partition... ^^


    oldman20 said:
    And after fews way i can get back IMEI 😀
    Click to expand...
    Click to collapse

    Good news then ;)
    View
  • 97
    _alexndr
    _alexndr
    Important notes for Developers / Chefs !!!

    This ROM is NOT based on any other custom ROM. My work contains many original ideas and innovations that I introduced as the first in the ROM development (see "Changelist" in post #2). Of course, it does not mean that I do not need to thank anyone - there are people who helped / inspired me anyhow (see "Credits").

    I will risk the statement that at this moment my "DevBase" is the most tuned and nuanced custom ROM available at XDA Forum :cool:

    I agree to use any part of my work to create other custom ROMs, but it would be great if you add me to the credits :)

    EDIT: Note related to creating "$ZIPFILE" which contains a file larger than ~4GB (e.g. system.img): the order of adding content to "$ZIPFILE" is very important! META-INF need to be added as the first dir in the archive! Example (my DevBase case):
    Code: 
    zip -r -9 N960FXXUxxxxx_DevBase.zip META-INF options.prop ALEXNDR
    It seems that misunderstanding of the above problem is the main reason why many devs give up and do not use my base as a pattern.

    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) :D 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 !!! :D 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.N960FXXSAFWB3:

    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) (*)
    What does it mean and why is it called "safe"?

    - ONLY apps available in stores are removed / skipped in DevBase, so you can easy (re)install any of these app if you like
    - ONLY pre-installed system apps are removed / skipped, DevBase installer will never touch any updated app nor app installed manually from a store
    - By default virtual Safe De-Bloat is applied with exact same effect as physical (completely skips apps at boot). You can force to delete apps physically but it is recommended only if you really need more space in /system

    Thus, the following conclusions can be drawn:

    1. If you install my DevBase directly over stock ROM without performing "Wipe data" - in most cases almost all these apps will remain untouched, because almost all apps have been updated already (stored on /data). But then you will be able to remove any useless app using the "Application manager", like any other app. Removed manually app will not appear again until you use my DevBase while updating.

    2. If you perform "Wipe data" while installing my DevBase - then all apps listed below will be removed. If you would like to use any of these apps - just install it manually from appropriate store. Installed manually app will not be removed during the next DevBase update.

    Removed / skipped apps list:

    Excel
    Facebook
    LinkedIn
    OneDrive
    PowerPoint
    Word

    (*) - 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:

    #
    # DevBase by ALEXNDR (_alexndr @ XDA)
    #
    # Configuration file to allow customize the installation.
    #
    # File inside the ZIP installer is just for reference - please DO NOT modify it!
    # If you want to change some options listed below - edit the copy of this file, then place
    # modified options.prop file in the root directory of internal emulated scdard (/data/media/0)
    # or in the root directory of extSdCard (recommended if you plan to format internal emulated
    # sdcard) and then start the installation.
    #
    # TIP: You do not need to repeat this step every next update I will release. As long as your
    # customized options.prop file is present in the (ext)SdCard - future DevBase installers will
    # "read in your mind" that you want to install with such options again.
    #
    # NOTE: All below variables and values are case sensitive!

    # Enable root access. Allowed values:
    # true - install Magisk as root solution (default)
    # false - do not root device

    root=true

    # Install Xposed framework matched to the ROM (there is also a possibility to detect Xposed profile
    # automatically, but auto-detection will not work if user will perform wipe /system). Allowed values:
    # auto - detect Xposed profile automatically
    # true - force Xposed framework installation
    # false - do not install Xposed framework

    xposed=auto

    # CSC Selection. Allowed values:
    # KCSC - Keep current CSC, recommended in most cases (automatic selection or keep current CSC contents).
    # You can force the use of natively supported CSC by typing (use UPPERCASE!): 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, XME, XNX, XNZ, XSA, XSG, XSP, XTC, XXV, XNF

    CSC=KCSC

    # Custom CSC Features. Allowed value in each line: <Example_line>value</Example_line>

    <CscFeature_Common_SupportWcdmaInSlave>true</CscFeature_Common_SupportWcdmaInSlave>
    <CscFeature_VoiceCall_ConfigRecording>RecordingAllowed</CscFeature_VoiceCall_ConfigRecording>
    <CscFeature_Setting_EnableMenuBlockCallMsg>true</CscFeature_Setting_EnableMenuBlockCallMsg>
    <CscFeature_Setting_CustNetworkSelMenu4>LTEONLY</CscFeature_Setting_CustNetworkSelMenu4>
    <CscFeature_Setting_SupportRealTimeNetworkSpeed>true</CscFeature_Setting_SupportRealTimeNetworkSpeed>
    <CscFeature_SmartManager_ConfigSubFeatures>roguepopup|autoclean|autorestart|applock|trafficmanager</CscFeature_SmartManager_ConfigSubFeatures>
    <CscFeature_SmartManager_DisableAntiMalware>true</CscFeature_SmartManager_DisableAntiMalware>
    <CscFeature_SystemUI_SupportRecentAppProtection>true</CscFeature_SystemUI_SupportRecentAppProtection>
    <CscFeature_Message_DisplaySmsTimeAs>server</CscFeature_Message_DisplaySmsTimeAs>
    <CscFeature_Message_DisplayMmsTimeAs>server</CscFeature_Message_DisplayMmsTimeAs>
    <CscFeature_Camera_ShutterSoundMenu>true</CscFeature_Camera_ShutterSoundMenu>
    <CscFeature_RIL_ForceConnectMMS>true</CscFeature_RIL_ForceConnectMMS>

    # Custom physical debloat list. Allowed value in each line: path to app's directory in /system.
    # (NOTE: wildcards are allowed here)

    /system/*app/SamsungPass*
    /system/*app/SamsungPay*
    /system/*app/SecureFolder*
    /system/app/SecurityLogAgent
    /system/priv-app/Fast
    /system/priv-app/Rlc

    # Custom virtual debloat list. Allowed value in each line: exact app name with .apk extension.
    # (NOTE: without app's path/directory, wildcards are NOT allowed here!)

    Excel_SamsungStub.apk
    Facebook_stub.apk
    FBAppManager_NS.apk
    FBInstaller_NS.apk
    FBServices.apk
    FotaAgent.apk
    LinkedIn_SamsungStub.apk
    OneDrive_Samsung_v3.apk
    PowerPoint_SamsungStub.apk
    Word_SamsungStub.apk

    NEW !!! :D 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:

    How to confirm that your data are encrypted:

    1. Go to TWRP and check if it is possible to mount /data. If NOT - all is ok :) "Failed to mount '/data' (invalid argument)" will be the a frequent message that you need to like in the future ;)

    How to update DevBase ROM to a newer version:

    1. Copy a newer DevBase ROM to extSdCard or OTG storage (you do NOT need to use "encrypt" option in ZIP file name again, if your device is encrypted already - it just remain encypted)
    2. Go to TWRP -> "Install" and flash ZIP file from extSdCard or OTG
    3. That's all :cool:

    The risk of data loss in case of encrypted devices, depending on the ROM scenario:

    1. DevBase only: VERY LOW RISK (*)
    2. Coming from other custom ROM with encrypted data - MEDIUM RISK (recommended backup)
    3. Installing other custom ROM over DevBase - MEDIUM RISK (recommended backup, anyway)
    4. Installing pure stock (using Odin) over DevBase (or over any other custom ROM) - VERY HIGH RISK (not recommended!)

    (*) There is still a risk to get into a bootloop if you install stuffs like: Xposed framework, incompatible Magisk or Xposed module, incompatible systemless MOD in /data/devbase/system, etc. In case of bootloop just try to use "rescue" option described above :)

    EDIT (Dec-01-2019): Very important info!!! Encryption will not be possible if you format /data using new TWRP (3.3.x-x). If you prefer encrypted device - it is highly recommended to use TWRP 3.2.3-x to format /data. If you are not sure which version you have used to format data - it is much better to perform clean install using TWRP 3.2.3-x to format /data before forcing encryption. More info HERE

    Notes related to EFS backup:

    During install, my ROM's installer always performs EFS backup to {storage}/.backup/efs (where {storage} may be /external_sd, /usb-otg, /sdcard - in the preferred order). It is recommended to copy EFS backup occasionally outside the phone and store in safe location (PC, OTG, etc). There are 2 backups - when you first time installed my ROM (efs_backup.tar.gz) and recent, created additionally, just in case (efs_recent.tar.gz). Most useful will be most probably the first one (efs_backup).

    You probably will never need these files, but sometimes s**t happens and restoring EFS backup may be the only one way to rescue your device!

    When do I need to restore EFS backup?
    - lost/invalid IMEI number
    - proper IMEI but unable to connect to the network
    - connected to the network but unable to make a call and/or transfer data
    - unrecoverable bootloop (even after clean DevBase install with default settings)

    NOTE: In contrast to many other custom ROMs - my installer uses gzip compression (*.img.gz) to store EFS backup(s). Restore command for your device is stored in txt file in the same directory with EFS backup. If you forgot command - you can read txt file containing proper command @ PC (Notepad) or even directly form TWRP using Terminal's 'cat' command, e.g.:

    Code: 
    cat /external_sd/.backup/efs/efs_backup.txt

    NOTE: Do not panic, read the txt file peacefully and type command exactly as it is in TWRP's Terminal, then tap blue [enter] button. After all - please reboot device. If the problem was EFS related - your device just has been rescued :cool:

    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&currency_code=EUR

    Due to the fact, that some countries banned PayPal - I have created also Patreon site: https://www.patreon.com/_alexndr
    View
    40
    _alexndr
    _alexndr
    Download ROM

    SM-N960F/DS:
    >> N960FXXSAFWB3_DevBase_v7.4.zip << (Android 10, updated Mar-05-2023, 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.
    View
    27
    _alexndr
    _alexndr
    Thread has been updated, U4DSLB (Android Q) DevBase v7.0 (December security patches, changelist 17594460) :cool:

    As usual - you can dirty flash it over previous version :good: :cool:

    Download ROM:

    SM-N960F/DS:
    >> N960FXXU4DSLB_DevBase_v7.0.zip <<
    Click to expand...
    Click to collapse

    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!
    >> BL_N960FXXU4DSLB.zip <<
    Click to expand...
    Click to collapse

    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 - HERE
    View
    21
    _alexndr
    _alexndr
    Thread has been updated, S4CSK2 DevBase v6.0 (December security patches, changelist 16685647) :cool:

    As usual - you can dirty flash it over previous version -> DONE, that's all :good: :cool:

    Download ROM:

    SM-N960F/DS:
    >> N960FXXS4CSK2_DevBase_v6.0.zip <<
    Click to expand...
    Click to collapse

    (you can find bootloader in my updated repository, but BL update is not mandatory)
    View
    21
    _alexndr
    _alexndr
    Thread has been updated, U5DTCA (Android Q) DevBase v7.3 (April security patches, changelist 18063799) :cool:

    Download ROM:

    SM-N960F/DS:
    >> N960FXXU5DTCA_DevBase_v7.3.zip <<
    Click to expand...
    Click to collapse

    (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
    >> BL_N960FXXU5DTCA.zip <<
    Click to expand...
    Click to collapse

    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"
    View

New posts