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
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 G96xFXXU1xxxx_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) 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 - probably there is no better alternative
ROM for G96xF/DS/FD contains OXM multi CSC package, list of available CSCs is as follow:
ACR, AFG, AFR, ATO, AUT, BGL, BNG, BRI, BTC, BTU, CAC, CAM, CAU, CEL, CPW, DBT, DKR, ECT, EGY, EUR, GLB, ILO, INS, ITV, KSA, LAO, LUX, LYS, MAT, MID, MM1, MWD, MYM, NEE, NPL, NZC, OPS, ORX, PAK, PCL, PHE, PHN, PNG, PTR, 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
ROM for G96xN 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.G96xFXXUHFVG4:
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, CEL, CPW, DBT, DKR, ECT, EGY, EUR, GLB, ILO, INS, ITV, KSA, LAO, LUX, LYS,
# MAT, MID, MM1, MWD, MYM, NEE, NPL, NZC, OPS, ORX, PAK, PCL, PHE, PHN, PNG, PTR, 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
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 !!! 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. "G96xFxxx_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. "G960Fxxx_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. "G96xFxxx_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_G96xFxxx_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. "G96xFxxx_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
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 MOD, 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
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
@fei-ke for omc-decoder
@Zackptg5, @osm0sis & @jcadduono for no-verity*
@Tkkg1994 for initial help with stock kernel's patches
@corsicanu & @jesec for TWRP recovery
@Duncan1982 & @bennebartsch for initial tests
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/_alexndr
Download ROM
S9 (SM-G960F/DS/FD):
>> G960FXXUHFVG4_DevBase_v7.4.zip << (Android 10, updated Sep-20-2022, more info HERE)
S9+ (SM-G965F/DS/FD):
>> G965FXXUHFVG4_DevBase_v7.4.zip << (Android 10, updated Sep-20-2021, more info HERE)
SM-G96xF/DS/N repository:
>> S9/S9+ 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.
Changelog
v7.4 (starting from G96xNKSU4FUC1 DevBase):
- Fixed unzip issue which caused unexpected installation termination - applies to TWRP 3.5.0_9-1 and newer
v7.3 (starting from G96xFXXS7DTB5 DevBase):
- Fixed bootloop issue in case of Android Q and "noroot" scenario - thanks to @Zackptg5 for the up to date dm-verity disabler
v7.2 (starting from G96xFXXU7DTB4 DevBase):
- Fixed bootloop issue in case of Android Q and encrypted devices (applies to dirty update)
v7.1 (starting from G96xFXXU7ZTA2 DevBase):
- Potential fix for "make_ext4fs: not found" error in newer TWRP versions and in result "Failed! Not enough space..." message appears while applying CSC during install (applies to N960x devices)
v7.0 (starting from G96xFXXU7ZSLC DevBase):
- Initial support for Android Q / system-as-root devices
v6.0 (starting from G96xFXXU2ZRKN DevBase):
- Introduced logging entire installation process (to devbase_install.log file, placed in /data or /cache in case of encrypted devices). These logs may significantly increase the possibility of my help in case of problems with/after installation
- Major imrovements/bugfixes/optimizations related to Android Pie support (e.g. takes care about special SELinux contexts for /odm content, introduced in Pie)
- Removed SuperSU support. Changed allowed "root" variable value in options.prop to true/false (backward compatible with old options.prop)
- Removed "skipblcp" option - baseband/modem will be always updated, bootloader need to be flashed separately (update is usually not mandatory)
v5.9 (starting from G96xFXXU2BRG6 DevBase):
- Changed device detection method to bootloader's prefix (instead of ro.product.*)
- Improved support for applying custom mods automatically at each ROM's install/update, introduced in v5.6 (added support for etc, fonts, media & usr directories in {storage}/devbase/system)
- Added support for custom {storage}/devbase/post-installation.sh script
v5.8 (starting from G96xFXXU1BRE6 DevBase):
- Improved unzip_flash function in the installer to detect properly more flashing errors (e.g. EXT4 partition mismatch)
- Changed /odm flashing method to file based due to potential /odm partition mismatch (applies to carrier branded treble devices)
- Minor optimizations/improvements in the installer (this time mainly to improve installation speed)
- Busybox has been removed from /system/xbin to run properly some banking apps
v5.7 (starting from G96xFXXU1ARD2 DevBase):
- Improved/expanded built-in RMM lock prevention (thanks to @jesec for idea of overriding properties via factory.prop)
- OEM unlock status will always be displayed correctly in Developer options (to avoid confusion) with stock kernel included in the DevBase ROM
v5.6 (starting from G96xFXXU1ARCC DevBase):
- Added "App Lock" feature (Settings -> Advanced features)
- Added Xposed framework as installation option (it is NOT forced by default - you need to force it manually while installing with Xposed first time, e.g. by "xposed" string in ZIP's file name, but next ROM's updates will detect and apply Xposed profile automatically, unless you wipe /system - then auto detection is not possible)
- Added support for applying custom mods automatically at each ROM's install/update by placing modded apps in {storage}/devbase/system/(priv-)app or placing modded framework files in {storage}/devbase/system/framework (where {storage} may be: /sdcard, /external_sd or /usb-otg)
v5.5 (starting from G96xFXXU1ARCC DevBase):
- Added support for flashing optional, CSC related partitions ($OMR, $PRELOAD)
- Added possibility to update recovery (optional, performs update if exists $NAME/images/recovery.img)
- Return to using only the original XML files in the CSC package (thanks to @fei-ke for omc-decoder)
- Partition(s) may be wiped only by writing new block's image
- Minor optimizations / improvements in the installer
v5.4 (starting from G96xFXXU1ARC5 DevBase):
- Big step forward in DevBase ROM customization ability - almost all current ROM features (hidden up to v5.3) have been moved to options.prop (you will be able to easy add new or remove current feature)
- Return to dm-verity-opt-encrypt boot patcher if necessary (wherever it works well, there are still devices which need "no_verity" function introduced in v5.1)
- Initial support for forcing (changing) CSC in case of devices with /odm as CSC location (NOTE: take care of EFS backup in case something will go wrong)
- Initial support for encryption in case of G96xF/DS/FD (it is optional of course, not default)
- Minor optimizations / improvements in the installer
v5.3 (starting from G96xFXXU1ARC5 DevBase):
- Improved algorithm of search & change "ro.security.vaultkeeper.feature" property to 0 (/system & /vendor)
- Possibility to change CSC in case of S9/S9+ has been temporarily disabled for safety reasons (needs more research)
v5.2 (starting from G96xFXXU1ARC5 DevBase):
- Added support for devices with /odm as CSC location
- Added support for flashing $ODM, $VENDOR, $KEYSTORAGE, $DQMDBG images
- Added support for custom debloat list and custom CscFeature list in options.prop
- options.prop file format has been changed to CR/LF (Windows) - more noob-proof solution, user can edit a copy of options.prop file even in Windows Notepad (the installer still supports ANY text format of options.prop file - Win/Unix/MAC)
v5.1 (not released for G96xF):
- Created new "no_verity" function in the installer, compatible with Samsung's Oreo, based on @Chainfire's patch tool (no-verity-opt-encrypt has been removed).
v5.0 (not released for G96xF):
- SYSTEMLESS DevBase has been removed due to the fact, that in case of modern devices/firmwares we need to perform many changes physically in /system anyway, so it loses the sense of use here. If you liked it - you can still install it separately from HERE (it does not need to be re-installed after ROM update as it is installed in /data)
- Added "skipblcp" option to let users skip BL/CP update (additionally it disables auto-reboot when the installer finished work as it is just not necessary then)
- Added "phydebloat" option to let users choose beetween virtual and physical debloat (to get more space in /system)
- Other (minor) optimizations & improvements
v4.6 (not released for G96xF):
- Initial support for devices with /system/omc as CSC location
- SYSTEMLESS DevBase updated to v2.0 (see changelog HERE)
- Added possibility to force CSC by renamig ZIP filename. Due to the fact that trere are many different CSC and it is possible that $ZIPNAME may contain a CSC accidentally - to force CSC you need to put CSC in $ZIPNAME at the beginning and CSC must be followed by "_". Example $ZIPNAME (to force CSC DBT): "DBT_G96xFXXU3xxxx_DevBase.zip"
- Added auto efs-backup during install. Installer will create first backup (efs_backup.img.gz) and recent backup (efs_recent.img.gz). The installer will prefer external storage as default backup location (/external_sd or /usb-otg) due to encryption support. MD5 sum and restore command will be stored in efs_backup.txt or efs_recent.txt file
- Other (minor) optimizations & improvements, e.g. added more error messages in case of something went wrong during install
v4.5 (not released for G96xF):
- Added new "rescue" option (readable only as string in ZIP file name due to the fact, that we will need this option rarely). It can be a potentially very helpful option in case of bootloop @ encrypted device, caused by a systemless mod/module/xposed stored on /data (without access to /data from TWRP) - more info in post #1
- SYSTEMLESS DevBase updated to v1.14 (see changelog HERE)
v4.4 (not released for G96xF):
- Added new "encrypt" option (readable only as string in ZIP file name due to the fact, that we need to do it only once). Now you can easy encrypt all data in your device, just during the ROM upgrade (without data loss).
- SYSTEMLESS DevBase updated to v1.13 (see changelog HERE)
v4.3 (not released for G96xF):
- "root.supersu" & "root.magisk" variables in the options.prop file have been replaced by one "root" variable (dropped possibility to install both - SuperSU & Magisk - due to the fact that Magisk v13+ does not support SuperSU as root solution)
- SYSTEMLESS DevBase updated to v1.9 v1.12 (see changelog HERE)
v4.2 (not released for G96xF):
- Added possibility to add systemlessly NEW apps to /data/devbase/system/(priv-)app (up to 5 apps in "app" & 5 apps in "priv-app"). The only condition is that you need to rename its directories to CustomApp[1...5] (e.g. CustomApp1, CustomApp2, etc..). These apps will remain even if you flash a new DevBase as corresponding dummy directories will exist in future DevBase updates
- In case of DevBase update or re-installation - installer will not remove your custom entries in /data/devbase/system/build.prop and in *.xml files placed in /data/devbase/system/csc
- SYSTEMLESS DevBase updated to v1.6 v1.8 (see changelog HERE)
v4.1 (not released for G96xF):
- Added full Magisk support - MagiskSU is now default root solution (ROM should pass SafetyNet with Magisk Hide enabled in settings)
- Since systemless Xposed does not need to be re-installed every new DevBase I will release (in case of using the same root solution) - it makes no sense to keep it anymore as installation option
- SYSTEMLESS DevBase updated to v1.5 (see changelog HERE)
v4.0 (not released for G96xF):
- A huge step in the systemless direction! DevBase installer now installs pure odexed stock ROM (just slightly debloated), then systemless SuperSU, then systemless DevBase, then (optionally) systemless Xposed
- All Knox related applications are available again (except SecurityLogAgent, to prevent annoying security alerts)
- Fake KNOX 0x0 status (check it in PhoneINFO app) - most of Knox related apps should work again, like in case of untouched KNOX flag
- All mods known from previous DevBase versions (up to v3.x) now are applied systemlessly - all modified files (including modded apps) are placed in /data/devbase/system instead of physical /system partition. Mods section (#4) has been updated to install mods to /data/devbase/system/(priv-)app if systemless DevBase has been detected (otherwise will be installed as usual, to /system)
- Deodex on-the-fly feature has been removed. If you really need deodexed ROM - you can install someone else's deodexed ROM, then systemless DevBase as an overlay
- Init.d support has been removed as it is deprecated (use su.d instead)
v3.8 (not released for G96xF):
- Added hexpatch to root_from function (support for SM-N930x, thanks to @Chainfire)
v3.7 (not released for G96xF):
- Another major improvement/bugfix in deodex_from function (full support for 64 bit OS)
v3.6 (not released for G96xF):
- Major improvement/bugfix in deodex_from function (added "-g" switch to zip command - finally no issues in case of deodexed Android 6.0.1)
v3.5 (not released for G96xF):
- Improved root_from function (Android 5.1+) - added "setprop selinux.reload_policy 1" removal from init.rc (thanks to @Chainfire)
- Fixed bug in new alghoritm for checking whether stock recovery should be installed or not (introduced in v3.4)
- Added new functionality - installer will store a copy of patched stock kernel in /data for those who flashed custom kernel but for some reasons want to revert to the stock kernel (Android 5.1+)
v3.4 (not released for G96xF):
- Completely changed alghoritm for checking whether stock recovery should be installed or not (it applies to FlashFire users). Now it depends on previously used recovery (instead of checking KNOX flag which was not 100% reliable across devices/recoveries)
v3.32 (not released for G96xF):
- Updated set_csc, kcsc_backup, kcsc_restore functions to support more devices
- Updated partition detection algorithm to support more devices
- Fixed path to options.prop file placed in external sdcard in case of updating Marshmallow while using FlashFire
- Minor intaller's optimizations/bugfixes
v3.31 (not released for G96xF):
- Potential fix for reported problems with root (rare cases)
v3.3 (not released for G96xF):
- Improved method of reading options from ZIP file name (previous was directory/path sensitive also)
- Added support to mod_csc function for other than UNIX text format (it's a little ridiculous, but in case of some CSCs - original /system/csc/other.xml file has Windows or MAC text format!)
- Initial support for options.prop file in CRLF text format (DOS/Windows)
v3.21 (not released for G96xF):
- Fixed installer's issue if there is a [space] present in ZIP filename or a directory containing DevBase (see #1728)
v3.2 (not released for G96xF):
- Another improvements in add_initd function (details - see v1.3)
- Improvements in set_perm, set_perm_rec and root_from functions (recovery-independent structure)
- Improvements in deodex_from function related to Android MM
- New get_con function in the main sh script (useful for devs)
- BusyBox updated to 1.22.1 (bionic) [no, this is NOT a mistake!]
- Minor intaller's optimizations/bugfixes
v3.1 (not released for G96xF):
- Significantly improved "add_initd" function in the update-binary shell script. Added support for (probably) all available Samsung's platforms (e.g. Exynos) and all available firmwares (based on Android 4.4+)
- In case of installation with Xposed framework installer checks if Xposed Installer app is present in /data/app and installs it automatically if necessary
- Minor intaller's optimizations/improvements
v3.0 (not released for G96xF):
- Entire installer has been re-written from the scratch! All "magic" moved to update-binary which is a shell script. It opens up new possibilities never possible before!
- Introduced new customization method - you can change most frequently switched options just by renaming installer's ZIP file name. Currently supported "strings" in the file name:
"noroot" (means "do not root"), "deodex", "xposed", "initd" (no other comments are required, I hope..)
- Starting from v3.0 init.d support is disabled by default
v2.3 (not released for G96xF):
- Added option to install suitable Xposed framework in one step while installing DevBase (for maximum comfort). There is a new xframework.sh script - device independent structure and full Android 5.1+/6.0+ support. Backup method is compatible with well known Xposed uninstallers (tested with @wanam's)
v2.2 (not released for G96xF):
- Significantly improved root_supersu.sh script - device independent structure and full Android 5.1+/6.0+ suport including on the fly kernel/ramdisk/sepolicy patching if necessary. SU binaries are still copied to /system as it is the best choice in case of custom ROMs
- Changed order of performed operations in the updater-script due to new root_supersu.sh script advantages
- Installer wipes partitions designated for RAW content (e.g. kernel / recovery image) before writing to them
- Minor additions in dex_injector.sh script related to Android 6.0+
v2.11 (not released for G96xF):
- Fixed some minor installer's issues ("set_perm" function in set_csc.sh did not work correctly while using wildcards in the path (it was exclusively FlashFire issue! no problem with TWRP / CWM). Fortunately - only /system/etc/csc_*.txt were really "affected" - it didn't cause real issues as these files are empty)
v2.1 (not released for G96xF):
- As some people felt a bit disapointed / worried about DevBase v2.0 ROM file size - finally I have decided to debloat stock system.img (in same way as in v1.x => "Safe De-Bloat") and remove option to install all available bloatware. ROM file size has been reduced from about ~2GB to about ~1.6GB. Note for Devs / Chefs: Do not use Windows tools - you need Linux with "selinux" package installed (to handle SELinux contexts) to mount (rw) system.img safely. If you want to add / change any system content this way - remember about proper chown/chmod/chcon
- Added device check during install as flashing directly to EMMC block is potentially more risky for "other" devices. Installer will abort installation if device is not N910F (trlte(xx)). If you want to try this ROM on other N4 devices - you need to remove this check manually from updater-script (it is more conscious procedure)
v2.0 (not released for G96xF):
- Completely new concept of ROM development that makes it easy to build most tuned and nuanced custom ROMs. No more arduous manual analysis or (often) invalid permissions / SELinux contexts taken from a kitchen. The main idea is to flash original, stock /system image as EMMC block (in same way as PC Odin does) instead of extracting ZIP's contents to mounted partition, then setting permissions, then creating symlinks, etc. However, it requires more knowledge related to sh scripts as ALL necessary changes need to be done on the fly, while installing (e.g. by injecting modified classes.dex and/or modified images/xmls to /res/../* into an apk). There are no limits, all depends on your creativity!
- One common ZIP installer for Odexed and Deodexed ROM - you can control it by new "deodexed.rom" entry in options.prop (there is new dex_injector.sh script which can deodex on the fly the whole ROM using previously processed classes.dex files)
- ROM is still Safe De-Bloated by default but removing bloatware during install is not mandatory - you can control it by new "safe.debloat" entry in options.prop (there is new protection included to avoid overfilling /system in case of large size of additional MODs and/or large multi CSC package)
- Major improvements in csc_detect.sh script - it is able to detect previous CSC even in cases of flashing over e.g. CM based ROM and/or previously formatted system partition. However, if detected CSC is NOT included in my multi CSC package, in both mentioned cases it is still not possible to keep detected CSC (as there is no CSC related content to backup / restore)
- Improvements in all sh scripts - additional "metadata" entries in updater-script (related to processed contents) are not required
- Improvements in root_supersu.sh script - it is suitable for 32 and 64 bit OS
- Added full zip support from the command line
v1.x (initial version, further improvements, not released for G96xF):
- Built without using a kitchen. All set_metadata* / symlink entries are result of arduous manual analysis. For more info about the method - see hidden content for Devs / Chefs in THIS thread.
- New customization method without using Aroma (options.prop)
- Many useful scripts for easy installation: CSC applying/autodetection, backup/restore of security files, backup/restore of existing CSC package, XML modding on the fly, root, init.d support
- Many small changes and improvements "in the meantime" which I simply do not remember...
- Safe De-Bloated (see post #1 for details)
Optional MODs
[WORK IN PROGRESS, MODDING HAS LOW PRIORITY]
These modifications I have done personally using (bak)smali tools - these are NOT "borrowed" from other custom ROM, nor from someone else's thread (thanks to @BlackMesa123, @corsicanu, @Grouxho & @yash92duster for their excellent modding guides). All ZIP files are TWRP flashable:
>> MODs for SM-G96xF/DS/FD << (updated Aug-12-2018, more info HERE)
TIP: Are you tired with re-installing your favorite MODs every time you update this ROM? Just take advantage of the new DevBase feature, intruduced in v5.6 (see "Changelog"). It is enough to put your favorite apks and/or jars in /sdcard/devbase/system/(priv-)app (or ../framework) and these MODs will be detected & applied automatically every time you update this ROM. You can also use your /external_sd to store your favorite MODs (it is mandatory if you are using encryption).
Example for "G96xFXXU2BRxx_DisableHighVolumeWarning.zip" (modded SystemUI.apk):
- unzip SystemUI.apk file from my flashable MOD
- create /sdcard/devbase/system/priv-app/SystemUI directory
- place modded SystemUI.apk in above directory
Next time you will update my ROM - my installer will use modded SystemUI.apk instead of stock app included in my ROM
NOTE: Use this feature consciously and carefully! It may happen that your MOD is not compatible with a newer Samsung's base (especially in case of major Android update)! I will warn you about it, but only in case of MY MODs, I am not able to predict what kind of mods you are using.
First
Awesome stuff buddy. Welcome!
Second maybe hoping to see some action here
Wow thats fast i'm going to try this rom
I did some initial tests for @_alexndr, and finally got DevBase running on my SM-G960F, it works perfect!
Quick work! CSC Unlisted/Non-Original?
Thank you for your hard work on the newest of the new!
I bought my phone in Germany, so it's got the "DTM" CSC.
I need it to be "TMB" so that I can use Samsung Pay and then later use it on T-Mobile back in the States.
Is this possible with DevBase? I've already rooted the phone with TWRP and SuperSU. Knox is reading 0x1, of course.
Thanks Aleandr for letting me test, I can confirm all is running very well and will be very much looking forward to it's progression.
Great that you decided to build for our S9+ devices bro :good:
Stay tuned folks, this will be interesting....:good:
bennebartsch said:
I did some initial tests for @_alexndr, and finally got DevBase running on my SM-G960F, it works perfect!
Click to expand...
Click to collapse
The installer itself worked fine since first try main issues were with Magisk/SuperSU + my workaround for Magisk + pure stock kernel... I finally gave up and used @Tkkg1994 pre-patched kernel
consoneo said:
Thank you for your hard work on the newest of the new!
I bought my phone in Germany, so it's got the "DTM" CSC.
I need it to be "TMB" so that I can use Samsung Pay and then later use it on T-Mobile back in the States.
Is this possible with DevBase? I've already rooted the phone with TWRP and SuperSU. Knox is reading 0x1, of course.
Click to expand...
Click to collapse
I'm not sure about your exact case... CSC change require changes in /efs so it is a bit dangerous operation if performed in the other way than official (especially that you want to change it outside G96xF supported list).
Also, as far as I know - Samsung Pay will never work for you with KNOX 0x1
Sounds about right. It's tough living outside of your home country.
I looked pretty deeply into it, and it seems as if Samsung Pay focuses on the CSC for which country you are in. Samsung Pay is only available in certain countries. Though it would make sense if they're worried about security in payments for Knox to kill it.
Cruddy.
Thank you for the reply.
By the way, I only installed TWRP via this page. That's what tripped Knox.
https://www.theandroidsoul.com/samsung-galaxy-s9-root/
I didn't do the OEM fix, only the DM verity and SuperSU.
I have the Rom installed and its very good no problems at all battery is very good
Isnt there some fuse like thing that goes in the circuitry when knox is tripped? Thus screwing up folder and pay for good (no matter if the counters reset or not?).
Dont use any pay apps or samsung folder my self but there are other non knox dependant alternatives
Nice work dev, will looo later on at getting this installed
ron1974 said:
I have the Rom installed and its very good no problems at all battery is very good
Click to expand...
Click to collapse
I'm really happy too it works without problems :good:
Hello Alexndr
I have your rom installed and i'm really happy with it but i miss the csc feature like call recorder nd shutter sound is it possible for me to get it work.
ron1974 said:
Hello Alexndr
I have your rom installed and i'm really happy with it but i miss the csc feature like call recorder nd shutter sound is it possible for me to get it work.
Click to expand...
Click to collapse
1. What is your CSC ??
2. Could you post here /odm/omc/{your_CSC}/conf/cscfeature.xml file ??
I'm on PHN csc dutch. The file i have to look.
Sorry the other file you want i don't find it.
ron1974 said:
I'm on PHN csc dutch. The file i have to look.
Sorry the other file you want i don't find it.
Click to expand...
Click to collapse
About CSC - have you checked if it is PHN by e.g. entering Download Mode or you just suppose it?
About cscfeature.xml file - you probably got me wrong
In case your CSC is PHN - go to following directory (using any root file manager):
/odm/omc/PHN/conf
You should find there a few *.xml files, I need cscfeature.xml to look into it
(NOTE: there should be also cscfeature.xml.bak - I don't need this one, I need only cscfeature.xml)
_alexndr said:
1. What is your CSC ??
2. Could you post here /odm/omc/{your_CSC}/conf/cscfeature.xml file ??
Click to expand...
Click to collapse
do you know how to decode the csc files ? they seem to be encrypted like note8 ones.
Related
FlashFire is the most advanced on-device firmware flasher available for rooted Android devices. It can flash full firmware packages from various manufacturers, as well as apply over-the-air (OTA) and ZIP updates - all while maintaining root, and without using a custom recovery. It also offers full device backup and restore functionalities in several formats. Relevant files can be stored on internal storage, SD cards, USB connected storage, or can even be streamed directly to and from your computer using USB or Wi-Fi.
FlashFire is the spiritual successor to the Mobile ODIN app, which was a similar solution (using completely different methods under the hood) exclusively for Samsung devices on older Android versions.
FlashFire is an extremely powerful application, it should be used with caution. Data loss, soft-bricks, and even hard-bricks are possible if used incorrectly. Unless you are an expert user, consult FlashFire's website and this thread before doing anything potentially destructive.
If the FlashFire user interface crashes, please attach the logs of the crash to your post. The SysLog app can help.
If you are experiencing an issue while FlashFire is flashing, please post FlashFire's log file to pastebin, and include the link in your post. The log file can be found at /sdcard/FlashFire/lastlog on your device.
FlashFire's website/manual can be found at http://flashfire.chainfire.eu/.
Note: currently all functionality is unlocked without purchasing Pro. This may change in the future!
--- reserved #2 ---
--- reserved #3 ---
--- reserved #4 ---
--- reserved #5 ---
--- reserved #6 ---
--- reserved #7 ---
Changelogs
Please re-report any issues that persist after a new version comes out, even if you already reported them for the previous build. Either include the details again or link to your previous post.
2017.09.21 - v0.73 - RELEASE NOTES
- A/B OTA: Support for yet another streaming variant
- Magisk support: Fix some black screen issues
- Magisk support: Much improved OTA flashing compatibility (excluding A/B devices)
- SuperSU: Updated embedded SuperSU version to v2.82-SR4
- Backup: Exclude paths from backup with /sdcard/FlashFire/userdata_excludes and ./internal_storage_excludes
- Restore: Fix issue where FBE keys sometimes weren't restored
- Wipe: Add option to not wipe files from internal storage that aren't backed up
- ZIP: Open ZIPs from file managers and (Chrome) downloads directly, or share to FlashFire (file must resolvable to reside on /data)
- Adjusted timebomb for non-Pro users to 2018-04-01
2017.09.13 - v0.72 - RELEASE NOTES
- OTA: Fix new style OTA-download-complete marker detection
- A/B OTA: Add suppport for 'streaming' style OTAs
- A/B OTA: Enable pre-mount by default (required for incremental A/B OTAs now)
- Wipe: Fix dalvik-cache wipe greedily removing some files it shouldn't
2017.09.12 - v0.71 - RELEASE NOTES
- A/B OTA: Fix update_engine_flashfire crash in logs
- A/B OTA: Always make update_engine_sideload available
- A/B OTA: Fix fstab availability for new style OTAs
- A/B OTA: Don't automatically delete OTAs after successful install if located on internal storage or sdcard
- A/B OTA: Detect target slot rather than blindly switching to the other one
- FlashUI: More Android Oreo compatibility fixes
2017.09.11 - v0.70 - RELEASE NOTES
- FlashUI: Android Oreo support
2017.08.15 - v0.60 - RELEASE NOTES
- OTA: Implement O-style OTA handling (non-streaming)
- UI: Fix not being able to deselect backup partitions
- UI: Fix partitions listed multiple times in backups sometimes
- FBE: Fix wiping encryption files during restore, triggering factory reset
2017.08.13 - v0.58 - RELEASE NOTES
- Fix (abort) parsing of loki boot images
- Prioritize ZIP/GZIP/BZIP2 detection over other formats
- Fix compatibility with SuperSU in SBIN mode
- OTA: Fix /cache not being available sometimes
- OTA: Fix handling issue with August A/B OTA
- OTA: Show warning on 'OTA found' dialog if not using systemless SuperSU
- Backup/Restore: skip lockscreen security files
- Embedded SuperSU updated to v2.82 SR3
- Adjust timebomb for non-Pro users to January 01, 2018
2017.04.03 - v0.57 - RELEASE NOTES
- Add support for multi-stage OTAs
- Fix possible NPE during OTA uncrypt
- Fix logic failure during OTA uncrypt
- Fix unsupported root detection
- Fix root detection sometimes failing
- Prefer system-supplied reboot binary to our own
- Adjust timebomb for non-Pro users to September 01, 2017
NOTE: Sometimes OTA still reboots to recovery with an error, just reboot manually
2017.01.27 - v0.55 - RELEASE NOTES
- (C) 2017
- Improved 32/64 bit handling (fixes some blackscreens)
- Improved handling of devices that have a /vendor partition
- Add initial support for devices with multiple slots
- Add support for uncrypted OTA ZIPs
- Add support for A/B OTA ZIPs
- Add support for file-based encryption backup/restore (primary user only)
- Add additional Pixel partitions
- Add support for Magisk+SuperSU (preliminary)
- Add support for Magisk+phh (topjohnwu version only) (preliminary)
- Add circular icon (Android 7.1)
- Restrict app usage to primary user
- Make treating system/vendor/oem as original a setting (auto-detection is not completely reliable)
- File selection activity now remembers last location
- Fix drawer closing on back button press on tablets like Pixel C
- Fix overlay display visibility on [email protected]
- Detect and handle screen scaling on [email protected]
- Fix archive scanner freeze when reading password protected ZIPs inside another archive
- Fix seeking issue with custom recovery detector
- Fix archive scanner inconsistency with multiple files targeting the same partition
- Fix archive scanner scanning inside images
- Fix archive creator display inconsistency
- Fix unconditional block update ZIP detection
- Fix busybox/untar not setting SELinux file context on files that already existed
- Hide cache wiping options if no cache partition present
- Restart and re-check for root if root not found initially
- Refactor boot image analysis
- Preserve recovery: option hidden from devices without a dedicated recovery partition
- Replace update_engine service on A/B update devices
- Add intent to flash a specific ZIP file
- Workaround adb restore 'never-finish' issue by using adb push (temporary?)
- Embedded SuperSU updated to v2.79 SR3
- Adjust timebomb for non-Pro users to May 01, 2017
2016.09.19 - v0.53 - RELEASE NOTES
- Embedded SuperSU updated to v2.78 SR1
- Adjust timebomb for non-Pro users to February 01, 2017
2016.07.18 - v0.52 - RELEASE NOTES
- Add option to delay reboot after flash
- Fix mixing of 32/64-bit commands on NP4/64-bit
- Fix re-mounting of lazily unmounted system partition
- Fix partition detection on some Motorolas
- Fix cache wipe breaking subsequent OTA on some devices
- Detect 'full' OTA ZIP, and do not warn about modified /system in that case
- Move 'preserve recovery' option from OTA/ZIP action to Reboot action
- ZIPs: Add 'getprop' command emulation if /system not mounted
- Fastboot: don't use 'fill' chunks
- Credits listing updated
- Embedded SuperSU updated to v2.76
- Getprop harvesting
2016.07.07 - v0.51
- New TriangleAway binary that can read SGS6/7 status
- PIT support
- Wipe: Only remove .supersu if wiping systemless SuperSU
- Wipe: Fix wiping systemless SuperSU from /data
- OTA: Add additional Samsung paths
2016.06.01 - v0.50 - RELEASE NOTES
- Fix compatibility with N Preview 3 (in used libraries)
- Added 'Restore from ADB' option to 'No backups found' dialog
- NP3: Work around ART crash
- NPx: Work around 'adb restore' bug by using 'adb push' instead
- 4.2: Fix StatFs crash
- ADB: Authorize all connections
- ADB: Fix restoring not doing anything on some devices
- Force 'clear cache' option to show UI
- Include filesize in cache validation
- (Temporarily?) Switched back to single-threaded lz4 implementation due to the multi-threaded version occasionally segfaulting
- Add choice for visiting either FlashFire's website or the XDA thread when tapping the top card
2016.05.11 - v0.33 - BETA - RELEASE NOTES
- Add support for backing up to and restoring from ADB, through USB or Wi-Fi (special ZIP format)
- Completely reworked progress code, more info is shown in more places now (current file, speed, progress)
- Improved back key handling
- Improved app startup performance
- If sdcard is adopted, reflect that in location display name
- Fix adopted SD card sometimes not showing up in mixed partition mode
- Attempt to identify external sdcard (rather than calling it USB)
- Adjust storage location display order
- Add warning when using adopted storage
- Rewrote file creation routines to cope better with adopted storages
- Fix reboot card popup title
- Refactor shell commands as root
- Change install location to internal-only
- Fix backup of internal storage not skipping backups in some cases
- Adjust ZIP parser so it can cope with Samsung FOTA ZIPs
- Added warning for Huawei users about brickability
- Add OEM partition to TWRP emergency restore
- Fix backup/restore per-file progress freezing
- Archives: Add suppport for Huawei's UPDATE.APP format
- OTA: Add detection for Samsung
- OTA: Add detection for Huawei
- OTA: Add detection for HTC
- OTA: Add detection for Letv
- OTA: Add multi-zip-file capability
- Partitions: Add various Tegra-specific partitions
- Partitions: Add various Mtk64-specific partitions
- Partitions: Add various Huawei-specific partitions
- Partitions: Add various Pixel-C-specific partitions
- Partitions: Add generic Factory Reset Protection partition
- Partitions: Add support for eMMC boot and general purpose partitions
- Partitions: Attempt r/w unlock before writing
- EverRoot: Updated embedded SuperSU to v2.72 BETA
- EverRoot: Use LESSLOGGING mode, reduces SuperSU output
2016.04.20 - v0.32 - BETA - RELEASE NOTES
- Exclude multirom folder from internal storage backup as well
- Ability to create fastboot flashable backups (read the release notes!)
- Use proper ioctls for partition and block size detection
- Added option to backup recovery before installing ZIP/OTA and restoring it afterwards (automatically enabled when a custom recovery is detected)
- Added a watchdog to detect SurfaceFlinger crashes, fixes some black screen issues
- Prevent repeating OTA flash suggestion on rotate
- Added credits listing
2016.04.05 - v0.31 - BETA - RELEASE NOTES
- Exclude usbStorage folder from internal storage backup as well
- Switched to multi-threaded lz4 implementation (much faster backup/restore)
- Replace gzip with pigz in flash mode
- Set umask to 0 in flash mode
- Use tmpfs for /tmp
- Fix several other issues preventing flash mode from starting (reboots)
- Fix bug in TWRP restore listing (warning: old backups may not restore in TWRP !)
- Fix files present in firmware packages not being shown if the partition cannot be found
- Fix sdcard daemon running multiple times and eating CPU for no reason
- AROMA: prevent reboot call
- AROMA: only do framebuffer emulation if AROMA is actually detected, to prevent running into https://code.google.com/p/android/issues/detail?id=178583
2016.03.31 - v0.30 - BETA - RELEASE NOTES
- Exclude TitaniumBackup folder from internal storage backup as well
- Add location (internal storage, sd card, USB drive, ...) to backup listing
- Improve compatibility with StickMount-based USB mounts
- Fix a number of issues that could cause reboot while switching to flash mode
- Fix display brightness on some devices
- Framebuffer emulation for AROMA Installer (pretends to be a debugger, hijacks graphics calls)
- Fix bug where cache partition could lose data
- Complete refactor of flash mode code
- Improve Samsung CSC handling
- Fix bug where internal storage mounting could fail if external (sdcard/usb) storage present
- Update embedded SuperSU to v2.71
2016.03.22 - v0.29 - BETA - RELEASE NOTES
- Fix some compatibility issues with N Preview
- Fix app_process causing a reboot during startup
- Fix bug which could cause flashing /system to freeze
- Improve partition detection size accuracy
- Reduce app startup time
- Reduce time taken to switch to flash mode
- Add option to format /cache (wipe action)
- Improve external sdcard compatibility
- Improve adopted storage compatibility
- Improve USB drive compatibility
- Add additional OTA paths for NVidia
- Improve partition platform detection
- Add support for backing up internal storage (excludes FlashFire, TWRP and CWM backups)
- Fix error when opening bootloader image not wrapped in an archive
- Add setting to enable flashing primary and secondary bootloaders (automatically disabled)
- EverRoot: "Enable ADB" no longer enabled by default
2016.03.14 - v0.28 - BETA - RELEASE NOTES
- N preview compatibility (requires SuperSU v2.70)
- Properly copy selinux contexts
- Updated embedded SuperSU version to v2.70
2016.02.03 - v0.27 - BETA - RELEASE NOTES
- Copy additional partitions from fstab
- Added NVidia OTA locations
- Mark NVidia devices as somewhat supported
- Partitions: Added various partitions
- Fixed internal storage on Samsung 6.0.1
- Fixed sdcard on NVidia Shield Tablet
- Files named twrp-* or openrecovery-* are now recognized as recoveries
- Added warning about OTAs often requiring an unmodified system
- Attempt to detect block-level OTAs and modified systems, and warn when the flash is likely to fail
- Added some more logging in case of failure/reboot
2016.02.01 - v0.26 - BETA - RELEASE NOTES
- (C) 2016
- Archives: TAR: Fix MD5 warning if no MD5 signature found
- Archives: Added option to ignore MD5 mismatch
- Archives: Added support for Huawei Bootloader packed image format
- Archives: Added support for MSM89xx Bootloader packed image format
- Archives: Added support for Motorola Bootloader packed image format
- Updated embedded SuperSU version to v2.67-3
- Root must be SuperSU or (CM SU + Permissive)
- EverRoot: Enable on boot image modification, if currently systemless
- Firmware: Display partitions in the correct order
- UpdateZIP/OTA: Support progress bars
- UpdateZIP/OTA: Fix several issues with flashing Omni/CM
- OTA: Work-around apply_patch freeze
- OTA: Detect downloaded OTA and suggest flashing
- Partitions: Added various partitions
- M: Fix clear cache not working fully
- M: Update partition detection
- M: Toybox compatibility
- M: Fixed native graphics library
- M: Fixed sdcard mounting
- M: Relocate systemless SuperSU during setup
- M: Do not remove boot image backups or su image on wipe
- M: UpdateZIP/OTA: offer to restore boot and recovery image before flash
- L: UpdateZIP/OTA: mount /system, /vendor and /oem as r/o if unmodified
- L: Backups: Use RAW mode for unmodified /system, /vendor and /oem partitions
- Backups: Use RAW mode for partitions where the filesystem cannot be detected
2015.09.10 - v0.24 - BETA
- Fixed about a dozen FC's caused by Google's new and "improved" compatibility library
2015.09.09 - v0.23 - BETA
- Motorola: sparsechunk format support
- Motorola: MD5 listing/verification support
- Motorola: firmware package support
- Samsung: Fixed brightness slider disappearing from notification shade
2015.06.17 - v0.21 - BETA
- Fixed MD5 issue (showed up when creating a .tar.md5 package)
- Possible fix for mid-operation reboot
2015.06.02 - v0.20 - BETA
- Fix FC on 64-bit
- Disclaimer shown only once (and each update, data wipe)
- Possible fix for backlight issue
2015.06.02 - v0.19 - BETA
- MD5 routines now 30x faster (improves backup, restore, verification)
- Changed faulty warnings
- Updated BETA expiration (sep 1)
2015.05.02 - v0.18 - BETA
- Fix archive creation (for protected partitions) that broke on v0.17
- Split backup files into 1GB chunks
2015.04.30 - v0.17 - BETA
- Updated partition resolution (Motorola)
- Sparsechunk support (Motorola) - DO NOT USE YET
- Motorola ZIP package support (no MD5 checks)
- Fixed LZ4 restore issue
- Fix crash on navigating to '..'
- Updated preview timeout
2015.04.29 - v0.16 - BETA
- Added various partitions
- Experimental CM SU compatibility - not thoroughly tested
- Out of space errors now logged during backup instead of just freezing
- Added corrupt ZIP detection, in turn fixes several crashes caused by attempting to read corrupt ZIPs
- Added LZ4 compression. Now configurable between None, GZIP, and LZ4.
- Made threads used for GZIP configurable
- Added kernel wakelock
- Cache ZIP scans, speeds up file selection
- Fixed several issues on 64-bit devices
- SuperSU updated to v2.49 BETA
2015.04.13 - v0.15 - BETA
- Improved logging
- Improved startup procedure
- Fixed an issue where backup of some files were represented as an error
- Fixed a number of compatibility issues with latest Exynos (SGS6)
- Fixed USB drive support on stock Motorola
- Lowered default compression level and threads to reduce backup time and CPU usage (not yet user configurable)
2015.04.09 - v0.14 - BETA
- Fixed some black screen issues
2015.04.08 - v0.13 - BETA
- Fixed issue with log not being saved to internal storage
- Fixed issue with slow internal storage detection
- Fixed issue with error detection delaying reboot
- Fixed misaligned wordwrap
- AROMA compatibility (only if framebuffer device available)
- External storage and USB storage support
2015-04-08 - v0.12 - BETA
- Auto backup renaming improved
- TWRP restore ZIP added to backups
- Force grow ramdisk
2015-04-07 - v0.11 - BETA
- Initial release
This sounds great, i used mobile odin quite a bit on my last several devices and missed it on the note 4.
Signing up for beta now.
"just say no to spoon feeding"
Note 4. 910T 4.4.4. Tested backup was successful. Going to do more tests when I don't need to wait on a call.
Mobile Odin Pro user here and happy to see this great app almost ready.
THANKS.
sent from tapatalk on my GN4 N910T 4.4.4 rooted
I loved mobile odin made things very simple back in the day....as far as my s2 days....so glad you made root possible up to this point....its 2015 and still rooted
MOP user, this sounds great! Interesting thing to note, however, is that MOP still works fine on my note 3 N900T running lollipop.
Either way, looking forward to the update! Thanks a ton for all you've done for us!
Can not download
I bought the PRO version via app. Thank you for your work!
I have Samsung Galaxy S5 DualSIM (G900FD) with rooted 4.4.2. When I go to the directory where is firmware file to update my phone (for ex. in one file G900FDXXU1BOC1_G900FDOXE1BOC1_SER.zip) application always turns off with error message.
Any ideas? Forgive me if is not a topic to asking questions like this one.
aros1975 said:
I bought the PRO version via app. Thank you for your work!
I have Samsung Galaxy S5 DualSIM (G900FD) with rooted 4.4.2. When I go to the directory where is firmware file to update my phone (for ex. in one file G900FDXXU1BOC1_G900FDOXE1BOC1_SER.zip) application always turns off with error message.
Any ideas? Forgive me if is not a topic to asking questions like this one.
Click to expand...
Click to collapse
Perhaps you have to put a .tar , not a .zip
---------- Post added at 08:32 PM ---------- Previous post was at 08:31 PM ----------
hugoalo said:
Can not download
Click to expand...
Click to collapse
Edit : done
aros1975 said:
I bought the PRO version via app. Thank you for your work!
I have Samsung Galaxy S5 DualSIM (G900FD) with rooted 4.4.2. When I go to the directory where is firmware file to update my phone (for ex. in one file G900FDXXU1BOC1_G900FDOXE1BOC1_SER.zip) application always turns off with error message.
Any ideas? Forgive me if is not a topic to asking questions like this one.
Click to expand...
Click to collapse
What is the error message?
Link to the ZIP?
Chainfire said:
What is the error message?
Link to the ZIP?
Click to expand...
Click to collapse
Uhhhhh. It was a fault of archive which was corrupted (incomplete file).
I'm sorry for my mistake.
Successfully installed in SM-G900K KT(Korea Telecom) Korean version S5. Thanks Chainfire, greatwork. Even though I had MOP, I went ahead and purchased the pro version of Flashfire. At workright now, but I look forward to testing and checking it out a little bit later. I will also post results and comment. Thanks again.
**Update** It seems all 4 back up methods make it to the 2nd black screen and stop. First black screen -good. files load - good. Second black screen - screen stays black and blue LED comes on, it almost appears to be 'breathing' fades from medium light to dim light, back and forth. Almost like it is 'thinking'. Partitions(info) seems to be working well. Also scanning folders for a file works well in the Flash ZIP and OTA and also Flash firmware package. Let me know how I can help.
Sent from my 'towelrooted' SM-G900K using XDA Free mobile app
Going to try this out on my Note 4. Sweet!
Supper.
Dear @Chainfire in futere if in program we can do backup on sd card?
And ib future can we flash recovery as it flashes toll flashify?
Hello
Do you remember my custom ROMs for older devices? Do you remember my "DevBase" and its idea? If not - please read hidden content below:
>> [ROM] DevBase for Note 3 (SM-N9005) <<
>> [ROM] DevBase for Note 4 (SM-N910F) <<
>> [ROM] DevBase for S5 (SM-G900F) <<
>> [ROM] DevBase for S5 Duos (SM-G900FD) <<
Since I created these custom ROMs - many things have changed. Main idea of my previous work was the ability to flash these ROMs over stock ROM without wipe data - to let users simply jump between official ROM and DevBase with most necessary modifications for advanced users. It was relatively simple to implement until Samsung introduced both: dm-verity's boot prevention + forced /data encryption (starting from S7/S7edge series). What does it mean? If you disable /data encryption - you are able to use TWRP like in older devices, you are able to flash custom ROMs available in this section, but you are not able simply switch to official stock ROM. Since I bought my S7 edge I realized, that the most reasonable way is to go in the "systemless direction".
Are you tired with traditional custom ROMs?
Do you miss custom ROMs but do not want to decrypt your device (for privacy/security reasons)? (!)
You are in the right place! I present you SYSTEMLESS DevBase - an SYSTEMLESS equivalent of my previous work (see hidden content above)
SYSTEMLESS DevBase is developed and physically tested on S7 Edge (G935F). However, it should work on ALL UNLOCKED SAMSUNG DEVICES running Android 6.x/7.x/8.x. Exynos? Snapdragon? NO MATTER !!!
Prerequisites:
- Samsung device running stock or stock-based Android 6.x or newer (7.x/8.x)
- Rooted device - Magisk v12+ or SuperSU v2.76+ installed in SYSTEMLESS mode (!)
- Stock, untouched /system partition (not mandatory, but recommended for OTA)
(!) WARNING (related to installing TWRP and/or rooting Nougat - e.g. ZPLN, DPLT or newer): There are confirmed reports that installing TWRP and/or rooting encrypted phones running stock Nougat causes bootloop (even if you just flash TWRP, without rooting). You will need to restore both - stock recovery and stock kernel (if you e.g. tried to flash SuperSU or other ZIP which might modify the kernel) to make your device bootable. You need to remove stock encryption (by formatting /data after rooting). If you need data encryption - you can easy re-encrypt already rooted device (by setting "KEEPFORCEENCRYPT" flag to "true" before (re)flashing Magisk or SuperSU).
SYSTEMLESS DevBase v2.0:
1. Benefits / main features:
- Works with encypted /data partition (**) (!)
- Working official OTA updates! (see Tips & Tricks - post #4)
- Does NOT perform any phisical modifications in /system
- Does NOT perform any additional changes/patches to the kernel
- Removed KNOX warnings (systemlessly removed SecurityLogAgent)
- It contains SYSTEMLESS BusyBox (bionic, the most stable and respected release)
- It allows you to easily modify most of files & apps in your /system - SYSTEMLESSLY (see Tips & Tricks)
2. Systemless Safe De-Bloat (more info below):
What does it mean and why is it called "safe"?
- ONLY apps available in stores will be systemlessly removed from the ROM, so you can easily (re)install any of these app if you like
- ONLY pre-installed system apps are will be systemlessly removed, DevBase installer never touch any updated app nor app installed manually from store
Thus, the following conclusions can be drawn:
1. If you install my SYSTEMLESS DevBase directly over working stock ROM - 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" -> [Name_Of_App_To_Remove] -> MORE -> Uninstall updates. NOTE: App will disappear arter reboot and will be visible even in Titanium Backup!
2. If you perform "Wipe data" directly before installing SuperSU and my SYSTEMLESS DevBase (before you let to install app's updates) - 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 or re-install.
Removed apps list (depends on the device, should cover all devices starting from Galaxy S5):
ChatON
Chrome
Drive
Dropbox
EditorsDocs
Evernote
Excel
Facebook
FB Messenger
FB Pages Manager
Flipboard
Google+ / Photos
Group Play
Hangouts
Instagram
OneDrive
OneNote
PEN.UP
Play Books
Play Games
Play Movies
Play Music
Play Newsstand
PowerPoint
Skype
Smart Remote
WhatsApp
Word
NEW! Safe De-Bloat feature automatically detects and systemlessly removes apps not listed above, but present in your CSC package
3. Systemless 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 "Exit Internet" option to stock browser
- Added call button in Phone Logs (**)
- Added "Call/Message block" option in Settings
- Added symbols as secondary keys in Samsung keyboard (**)
- Added 4G/3G network support (master/slave SIM card - applies to Duos variants)
- Call Recording (added "Record" button, auto record calls - starting from Nougat)
- Enabled "Recent App Protection" feature
(**) may not work starting from Android 7.0 Nougat
Installation:
1. TWRP recovery:
- Tap "Keep Read Only" on the Welcome screen [extremely important for working OTA!]
- Open file using "Install" option (use extSdCard or OTG storage in case of encrypted /data)
- Confirm flash by swiping right
- Tap "Reboot System" (DO NOT wipe /cache after flashing in case of encrypted /data!)
2. FlashFire app (***):
- Open file using "Flash ZIP or OTA" option
- UNTICK "Mount /system read/write" [extremely important for working OTA!]
- Tap "FLASH"
NOTE1: One additional auto-reboot may be performed at first boot. It is not a bug (may be required for systemless build.prop support - see Tips & Tricks for more explanations)
NOTE2: Do not worry about red "mount /data failed..." messages displayed in TWRP in case of encrypted /data (installer will do the work anyway!)
(***) As far as I know - FlashFire is the only flashing tool with full access to /data during flash in case of encrypted devices (!). It is also the only tool which allows you to perform full backup/restore of partitions, including encrypted /data (!). It does NOT require custom recovery to work!
Credits:
@Chainfire for systemless SuperSU and a lot of inspiration
@topjohnwu for Magisk, another inspiration & some binaries used separately
Hit Thanks button if you like my work. If you really appreciate my work - feel free to buy me a beer
Download
>> SYSTEMLESS_DevBase_v2.1.zip <<
>> Recent SYSTEMLESS DevBase <<
Note:
Check MD5 sum BEFORE flash (useful TOOL), because flashing damaged or incomplete ZIP files can lead to issues! Correct MD5 sum is shown on the AndroidFileHost website while downloading.
Changelog
v2.1:
- Fixed potential "Google Play services" FCs in case of S8 or newer device(s)
v2.0:
- Initial support for devices using /system/omc CSC location (e.g. S8 / S8+ / Note 8)
- Added support for /system/preload as app location
- Other improvements & optimizations in the installer
v1.15:
- Added support for BINDSBIN mode (required by latest suhide) in case of SuperSU as root solution
v1.14:
- Added possibility to bypass all systemless mods by creating /cache/.disable_devbase file. It is usefull option especially for encrypted devices (without access to /data from TWRP) in case of you experienced bootloop due to placing a problematic MOD in /data/devbase/system/.. If /cache/.disable_devbase file exists then all systemless mods in ../app ../framework & ../piv-app will be moved to /data/devbase/system/.backup
- Backup all mods (to /data/devbase/system/.backup) instead of delete in case of major Android update has been detected
v1.13:
- Fixed bug with combination Magisk v15+ & SYSTEMLESS DevBase if we are trying to install one by one directly after wipe/format data
v1.12:
- Improved compatibility with Magisk v15+
v1.11:
- Fixed issues and improved compatibility with Magisk v14.5+
v1.10:
- Fixed not working /sbin support after clean installation of Magisk v14+, then SYSTEMLESS DevBase
v1.9:
- Improved/tuned compatibility with Magisk v13+ (which has been re-built from the scratch)
- Updated Magisk's binaries (e.g. resetprop function is now an applet available in magisk binary)
- Systemless BusyBox will be installed even with Magisk (since it has been removed from Magisk v13+)
v1.8:
- Fixed unroot2ota script to work while busybox is NOT in the $PATH (typical Magisk's case)
v1.7:
- Added support for /sbin via /data/devbase/sbin (you can only add a NEW item, e.g. script/binary/executable file). It can be an interesting feature for advanced users which would like to add custom commands, because /sbin is in the $PATH
- resetprop & unroot2ota now are placed in /sbin, in result unroot2ota command will natively work even with Magisk (without SuperSU)
v1.6:
- Improved/fixed Systemless Safe De-Bloat - now it should work in any case (even if enforceskippingpackages.txt file does not exist in your stock FW)
- In case of SYSTEMLESS DevBase update or re-installation - installer will not remove your custom entries in /data/devbase/system/build.prop and in *.xml files placed in /data/devbase/system/csc
- Added new features to Systemless CscFeature MOD: Allow 3G network mode in case of slave SIM card (Duos variant); Enabled "Recent App Protection" feature
v1.5:
- Added full support for MagiskSU as root solution. SuperSU is no longer the only available prerequisite
- Improved build.prop support in case of SuperSU as root solution, without magisk installed (seems like we can't rely on resetprop binary @ Android N)
- unroot2ota: removed SuperSU's sukernel dependency
v1.4:
- Improved/changed support for /data/devbase/system/build.prop file (uses @topjohnwu's resetprop binary)
- "ro.warranty_bit" & "ro.boot.warranty_bit" are set to "0" at boot -> fake KNOX 0x0 status (uses @topjohnwu's resetprop binary)
v1.3:
- Fixed CscFeature MOD (e.g. G920I case, now should work with all Samsung devices/variants)
v1.2:
- Added info in Settings/About device/Software info/Build number (can be overrided by editing /data/devbase/system/build.prop)
- unroot2ota: added ability to restore stock recovery using /system/recovery-from-boot.p file (no guarantee)
- unroot2ota: check /system partition for common modifications before unroot
- Minor changes & improvements in the shell code
v1.1:
- Added SYSTEMLESS support for /system/framework
- Added SYSTEMLESS support for /system/build.prop (overrides & additions)
- Added SYSTEMLESS BusyBox bionic (the most stable and respected release)
- Added major Android update detection (auto-remove mods for older API to prevent bootloops & FCs)
- Added logging to /data/devbase/last_boot.log (API & errors)
- Added SuperSU boot patcher version checker (exits su.d boot script if < 2.76)
- Added "Please DO NOT wipe /cache" warning in case of encrypted devices and TWRP recovery
- Minor changes & optimizations in the shell code
- Added SYSTEMLESS DevBase uninstaller
v1.0:
- Initial version
Tips & Tricks
1. OTA updates:
- Basically, the only thing you need to take OTA update is to perform "Full unroot" in the SuperSU app. However, a better way is to use "unroot2ota" terminal command, because this will not remove DevBase boot script from /su/su.d and the only thing you will need to re-activate SYSTEMLESS DevBase (and all your systemless MODs) after performing OTA update is just re-root your device with CF-Auto-Root.
- If you flashed custom recovery like TWRP - it is mandatory to restore your stock recovery (otherwise OTA will not work). You can do it using FlashFire app (the easiest way) - just open recovery.img file (extracted from your original FW) using "Flash firmware package" option, disable "Preserve recovery" option and then tap "FLASH". EDIT: Starting from version v1.2 there is a new "unroot2ota" feature which allow you to restore stock recovery using /system/recovery-fromm-boot.p file. There is no guarantee to perform it successfully (even if there is no error message) but in most cases it works well (tested on Nougat beta). Please go to recovery before you try to get OTA to check if you have stock recovery already after performing "unroot2ota" (if not - you need to use PC Odin to flash recovery.img packed in tar file).
- It is recommended to temporarily disable "Auto-update apps" in Play Store settings before you unroot your device. It will prevent updating applications covered by Safe De-Bloat list, as there apps will temporarily appear until you re-root the phone after performing OTA update.
Note (devices which use dm-verity): You should never allow /system modifications in TWRP, never allow to remount /system r/w in any app (e.g. Root Explorer, FlashFire, etc.) and never flash a ZIP file which could modify your /system or remount it r/w. Failure to follow these recommendations will break dm-verity verification and will cause, that your device may not be able to boot with the stock kernel (you will need to re-flash your original FW using PC Odin to make your device bootable).
UPDATE: Due to the fact that installing TWRP and/or rooting encrypted phones running stock Nougat is not possible without format /data - the above described advantages applies to stock ROMs based on Android up to 6.0
2. Making your own modifications:
- You can systemlessly replace any existing system app by modded one. Just put modified app to /data/devbase/system/app or /data/devbase/system/priv-app and then reboot your device
- You can systemlessly replace jar or apk in /system/framework. Just put modified one to /data/devbase/system/framework and then reboot your device (NOTE: framework support has been added for advanced users -> there is high risk of bootloop if you do something wrong!)
- You can systemlessly add or override any line in /system/build.prop. Just put (only new or changed) line to /data/devbase/system/build.prop and then reboot your device (NOTE: one additional auto-reboot may be performed if /data/devbase/system/build.prop file has been added, modified or removed (SuperSU case). It is not a bug - it is required for the changes in /data/devbase/system/build.prop to take effect!)
- You can systemlessly replace any existing file in /system/csc and /system/etc (but NOT in subdirectories). Just put modified copy of a file to /data/devbase/system/csc or /data/devbase/system/etc and then reboot device
Limitations: original app or file MUST physically exist with the same name in /system, you can NOT add a new app or file this way!
Example 1 (Ad-Blocking): Download the latest Ad-Blocking ZIP installer from THIS thread. Extract "hosts" file (placed in /system/etc inside ZIP file), then copy it to /data/devbase/system/etc, set rw-r--r-- (644) permissions and then reboot device
Example 2 (modded SamsungCamera6): Create "SamsungCamera6" directory in /data/devbase/system/priv-app and then put modified "SamsungCamera6.apk" file into it. Set rwxr-xr-x (755) permissions to "SamsungCamera6" directory, rw-r--r-- (644) permissions to "SamsungCamera6.apk" and then reboot device
Example 3 (De-Bloating a bit more): You can just create empty directories in /data/devbase/system/app (or priv-app) corresponding to applications in /system/app (or priv-app). Alternatively (more advanced method), you can add an app to modded enforceskippingpackages.txt file (you can find it in /data/devbase/system/etc or /data/devbase/system/csc_contents, depending on the original location in /system) and increase number in the 1st line. Second method should not be used by beginners (without a basic knowledge related to UNIX text format)
3. How to manually maintain the newest ROM version:
If you do not care about OTA - you can manually update your device to the newest ROM available @ Sammobile, keeping your original CSC (you need multi-file original FW, I mean separate files for BL/AP/CP/CSC). You need to download 2 ROMs: ROM with the newest changelist and the latest ROM containing your original CSC. Extract both and open in PC Odin BL/AP/CP files from the ROM with highest changelist but open CSC file from the ROM containing your CSC (I recommend to use HOME_CSC_* file to avoid auto-wipe-data). Flash such "mix", re-root and enjoy
Optional MODs
I put some of my favorite MOD's. These modifications I have done personally using (bak)smali tools - these are NOT "borrowed" from other custom rom, nor from someone else's thread (thanks to @majdinj & @tdunham for their excellent modding guides). All files are FlashFire / TWRP flashable ZIPs.
These MODs are compatible with SYSTEMLESS DevBase - installer will try to detect if your /system has been moddified (or not) already. If the installer will not detect any popular /system modifications like SuperSU / busybox / Xposed (installed to /system) then will try to install app systemlessly to /data/devbase/system/(priv-)app
1. Modified Camera app:
- Full functionality of the Camera app in low battery
2. Modified Messages app:
- Disabled SMS delivery notifications (*)
(*) If you long press a message you can still check if the message has been delivered or not, we do not need to see and hear notifications for every sms. It's annoying to me!
>> MODs for G935F (Marshmallow) << (**)
>> MODs for G935F (Nougat) << (**)
(**) Original apps come from stock ROM for G935F, but these MODs should work on all S7 flat & edge variants (Exynos based)
In case of MODs installed to /system - you can restore original apk using backup stored in /data/alexndr/backup
Incredible work, man! Thanks
I'm HAPPY to see you in this Forum with an S7edge !
@_alexndr
Congrats mate! Great job I will test it in a few days
# 1 question
What about framework folder support with modded files ?
# 2 question
Modded deodex apps putted in /data/devbase/system folders will work on odex system ?
For example:
/data/devbase/system/priv-app/SystemUI/SystemUI.apk
will be deodexed
but orginal one:
/system/priv-app/SystemUI/SystemUI.apk
will be odex (with arm folders)
# 3 question
For example if I put systemui.apk the modded will be run and original no ? Or they collaborate toggether ?
Edit:
If I correct understand examples they are colaborate
# 4 question
system/etc/permissions files not supported too ? For exapmle platform.xml
••••
This tool have a BIG potential to be the greatest !
Have a nice day
ambasadii said:
@_alexndr
Congrats mate! Great job I will test it in a few days
# 1 question
What about framework folder support with modded files ?
# 2 question
Modded deodex apps putted in /data/devbase/system folders will work on odex system ?
For example:
/data/devbase/system/priv-app/SystemUI/SystemUI.apk
will be deodexed
but orginal one:
/system/priv-app/SystemUI/SystemUI.apk
will be odex (with arm folders)
# 3 question
For example if I put systemui.apk the modded will be run and original no ? Or they collaborate toggether ?
Edit:
If I correct understand examples they are colaborate
# 4 question
system/etc/permissions files not supported too ? For exapmle platform.xml
����
This tool have a BIG potential to be the greatest !
Have a nice day
Click to expand...
Click to collapse
#2: Deodexed apps works great in odexed rom, but odexed apps will not work at all in case of deodexed framework!
SYSTEMLESS DevBase uses bind mounts so entire /system/priv-app/SystemUI directory (and its content) will be virtually replaced by /data/devbase/system/priv-app/SystemUI => it means you will not see oat/arm directory => entire app will act as deodexed in /system/...
See attached screenshots - first is with moded SamsungCamera5 present in /data/devbase/system/priv-app, second is after deleting /data/devbase/system/priv-app/SamsungCamera5 (and reboot)
Now it is good time to answer #1: With framework I intentionally dropped possibility to replace systemlessly files in .../framework (for security reasons @ to avoid unintentional bootloops). Imagine that you "systemlessly" replace ../framework/oat directory by empty one => then all jars corresponding to *.odex files in oat/arm(64) will immediately require classes*.dex files inside jars (otherwise will not work). Even if you replace entire framework by deodexed (with classes.dex inside jars) -> as I stated above (answer #2) -> almost all apps in /system/app & priv-app will stop working as almost all apps are originally ODEXED.
Imagine also that you leaded device into bootloop by replacing files in framework AND you have encrypted /data. There is no easy way out for normal users (which are not able to play with "fake" /cache/su.img to make workaround matched to the problem) they will not be able just remove files (causing the problem) from /data/devbase/system/framework using TWRP
In sum - thats why I have not introduced such possibility for normal users, but you as the DEV may extend this idea and try to systemlessly replace entire framework, app & priv-app by deodexed content (I have not tested it personally, IMO it does not worth the effort)
#3: The answer is now clear from the answer to question #2 - modded will run and original will NOT (original will "virtually disappear")
#4: It is easy to extend support for etc/permissions/* files by editing 0000000devbase, I will think about it
Now almost everything is clear
so for example if i put /data/devbase/system/framework/services.jar and delete from system/framework/oat/arm64/services.odex file should work ?
add support for etc/permissions/* files to fix ext-card permissions (platform.xml)
ambasadii said:
Now almost everything is clear
so for example if i put /data/devbase/system/framework/services.jar and delete from system/framework/oat/arm64/services.odex file should work ?
add support for etc/permissions/* files to fix ext-card permissions (platform.xml)
Click to expand...
Click to collapse
The only way to "virtually remove" files using this method is "fake" (e.g. empty) parent directory. Another way is to create "fake" file with same name (but size 0 bytes).
There is a chance that it will work for services.jar - but such "fun/play" is only for advanced DEVs, like you :good: you need to extend support for framework and subdirectories in 0000000devbase su.d script. Then you can try to systemlessly replace jar by deodexed&modded one in /data/devbase/system/framework... and odex file by "fake 0 sized" odex in /data/devbase/system/framework/oat/arm64/...
EDIT: @ambasadii, there is no need to "remove" (whatever it means) odex file as it will be ignored in case of jar or apk contains classes*.dex inside
Ok I will test it
Sent from my SM-G935F using XDA-Developers mobile app
_alexndr said:
you need to extend support for framework and subdirectories in 0000000devbase su.d script. Then you can try to systemlessly replace jar by deodexed&modded one in /data/devbase/system/framework...
Click to expand...
Click to collapse
correct ?
Code:
if [ -d "/data/devbase/system/framework" ] ; then
for i in `ls /data/devbase/system/framework` ; do
mount -o bind /data/devbase/system/framework/$i /system/framework/$i 2>/dev/null
done
fi
if [ -d "/data/devbase/system/etc/permissions" ] ; then
for i in `ls /data/devbase/system/etc/permissions` ; do
if [ -f "/data/devbase/system/etc/permissions/$i" ] ; then
mount -o bind /data/devbase/system/etc/permissions/$i /system/etc/permissions/$i 2>/dev/null
fi
done
fi
EDIT: @ambasadii, there is no need to "remove" (whatever it means) odex file as it will be ignored in case of jar or apk contains classes*.dex inside
Click to expand...
Click to collapse
good news, remove it means delete
ambasadii said:
correct ?
Code:
if [ -d "/data/devbase/system/framework" ] ; then
for i in `ls /data/devbase/system/framework` ; do
mount -o bind /data/devbase/system/framework/$i /system/framework/$i 2>/dev/null
done
fi
if [ -d "/data/devbase/system/etc/permissions" ] ; then
for i in `ls /data/devbase/system/etc/permissions` ; do
if [ -f "/data/devbase/system/etc/permissions/$i" ] ; then
mount -o bind /data/devbase/system/etc/permissions/$i /system/etc/permissions/$i 2>/dev/null
fi
done
fi
Click to expand...
Click to collapse
Basically correct but you need to add bind mounts only for files (just in case)
I will send you today new (pre-release v1.1) version with "slightly tuned code" and with support for framework
good news, remove it means delete
Click to expand...
Click to collapse
Nice joke :silly: "whatever it means" => FYI => it may also mean bind mounts with files (0 bytes size)
Welcome to the S7 bro
Hi alexndr
I love you from 9005 to now.
Plz add a option in cmera mod,that under i geting 60fps video,i can get pic.
Mean, camcorder 60fps and camera pictures together .
I cant write eng.plz exercise me.
Sent from my SM-G935F using Tapatalk
Awesome to see you here! Thanks @_Alexandr
Gesendet von meinem SM-G935F mit Tapatalk
Nice to see a familiar face in the S7 (E) section! Good luck with all your plans here.
Verstuurd vanaf mijn SM-G935F met Tapatalk
Nice to find you here Alexandr, been using your Roms on my old note 3 about 8 months ago and they were the most stable "custom Roms". But then you were providing a full unmodified ROM with root access, can you do something like this here for those of us that wish it? I personally don't have access to a PC so I can't flash newer firmwares with Odin, so I'm stuck using flashable ROMs.
It is possible to install magisk and work hide magisk for apps, for example bank apps?
SYSTEMLESS DevBase has been developed and physically tested on S7 Edge (G935F), so main thread containing the most detailed description you can find here:
>> [SAMSUNG][6.0+] SYSTEMLESS DevBase | Encryption support | Stock OTA updates <<
However, it should work on ALL SAMSUNG DEVICES running Android 6.0+, so if you are Galaxy S6 Edge+ (G928xx) owner - please place your feedback & discussion here to let me know about device-specific issues or to let me know that everything works perfect
---------------------------------------------------------------------------
Are you tired with traditional custom ROMs?
Do you miss custom ROMs but you would like to have encrypted /data (for privacy/security reasons)?
You are in the right place! I present you SYSTEMLESS DevBase - an SYSTEMLESS equivalent of my previous work (for older devices)
Prerequisites:
- Samsung device running stock or stock-based Android 6.0+ (mandatory!)
- Rooted device - SuperSU v2.76+ installed in SYSTEMLESS mode (mandatory!) (*)
- Stock, untouched /system partition (not mandatory, but recommended for working OTA)
- Stock recovery (not mandatory, but recommended for working OTA)
(*) NOTE: The latest CF-Auto-Root image for G928F contains SuperSU v2.74 which does not support SYSTEMLESS solutions (su.d is not triggered early enough). It is NOT enough to update it via PlayStore to the newest version and update su binaries! You need to update it using TWRP / FlashFire installable ZIP from THIS STABLE or THIS BETA thread. Alternatively you can use "EverRoot" -> "Inject SuperSU" option in FlashFire even if you are rooted already by CF-Auto-Root (it will update SuperSU in the same way as flashing ZIP).
SYSTEMLESS DevBase:
1. Benefits / main features:
- Works with encypted /data partition
- Working official OTA updates! (see Tips & Tricks)
- Does NOT perform any phisical modifications in /system
- Does NOT perform any additional changes/patches to the kernel
- Removed KNOX warnings (systemlessly removed SecurityLogAgent)
- It contains SYSTEMLESS BusyBox (bionic, the most stable and respected release)
- It allows you to easily modify most of files & apps in your /system - SYSTEMLESSLY (see Tips & Tricks)
- It does not interfere with Magisk! You can use Magisk in paralell with SYSTEMLESS DevBase if you need it for your favorite module.
2. Systemless Safe De-Bloat (more info below):
What does it mean and why is it called "safe"?
- ONLY apps available in stores will be systemlessly removed from the ROM, so you can easily (re)install any of these app if you like
- ONLY pre-installed system apps are will be systemlessly removed, DevBase installer never touch any updated app nor app installed manually from store
Thus, the following conclusions can be drawn:
1. If you install my SYSTEMLESS DevBase directly over working stock ROM - 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" -> [Name_Of_App_To_Remove] -> MORE -> Uninstall updates. NOTE: App will disappear arter reboot and will be visible even in Titanium Backup!
2. If you perform "Wipe data" directly before installing SuperSU and my SYSTEMLESS DevBase (before you let to install app's updates) - 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 or re-install.
Removed apps list (depends on the device, should cover all devices starting from Galaxy S5):
ChatON
Chrome
Drive
Dropbox
EditorsDocs
Evernote
Excel
Facebook
FB Messenger
FB Pages Manager
Flipboard
Google+ / Photos
Group Play
Hangouts
Instagram
OneDrive
OneNote
PEN.UP
Play Books
Play Games
Play Movies
Play Music
Play Newsstand
PowerPoint
Skype
Smart Remote
WhatsApp
Word
NEW! Safe De-Bloat feature automatically detects and systemlessly removes apps not listed above, but present in your CSC package
3. Systemless 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 "Exit Internet" option to stock browser
- Added call button in Phone Logs (**)
- Added "Call/Message block" option in Settings
- Added symbols as secondary keys in Samsung keyboard (**)
- Call Recording (manual control, added "Record" button)
(**) may not work starting from Android 7.0 Nougat
Installation:
1. FlashFire app (recommended ***):
- Open file using "Flash ZIP or OTA" option
- UNTICK "Mount /system read/write" [extremely important for working OTA!]
- Enable "EverRoot" -> "Inject SuperSU" option if necessary (see NOTE above (*))
- Tap "FLASH"
2. TWRP recovery:
- Tap "Keep Read Only" on the Welcome screen [extremely important for working OTA!]
- Open file using "Install" option (use extSdCard or OTG storage in case of encrypted /data)
- Confirm flash by swiping right
- Tap "Reboot System"
NOTE1: One additional auto-reboot may be performed at first boot. It is not a bug (may be required for systemless build.prop support - see Tips & Tricks for more explanations)
NOTE2: Do not worry about red "mount /data failed..." messages displayed in TWRP in case of encrypted /data (installer will do the work anyway!)
(***) As far as I know - FlashFire is the only flashing tool with full access to /data during flash in case of encrypted devices. It is also the only tool which allows you to perform full backup/restore of partitions, including encrypted /data. It does NOT require custom recovery to work!
Credits: @Chainfire for systemless SuperSU and a lot of inspiration
Hit Thanks button if you like my work. If you really appreciate my work - feel free to buy me a beer
Download
>> Recent SYSTEMLESS DevBase <<
Note:
Check MD5 sum BEFORE flash (useful TOOL), because flashing damaged or incomplete ZIP files can lead to issues! Correct MD5 sum is shown on the AndroidFileHost website while downloading.
Changelog
Please visit MAIN THREAD - post #3
Tips & Tricks
1. OTA updates:
- Basically, the only thing you need to take OTA update is to perform "Full unroot" in the SuperSU app. However, a better way is to use "unroot2ota" terminal command, because this will not remove DevBase boot script from /su/su.d and the only thing you will need to re-activate SYSTEMLESS DevBase (and all your systemless MODs) after performing OTA update is just re-root your device with CF-Auto-Root.
- If you flashed custom recovery like TWRP - it is mandatory to restore your stock recovery (otherwise OTA will not work). You can do it using FlashFire app (the easiest way) - just open recovery.img file (extracted from your original FW) using "Flash firmware package" option, disable "Preserve recovery" option and then tap "FLASH". EDIT: Starting from version v1.2 there is a new "unroot2ota" feature which allow you to restore stock recovery using /system/recovery-fromm-boot.p file. There is no guarantee to perform it successfully (even if there is no error message) but in most cases it works well (tested on Nougat beta). Please go to recovery before you try to get OTA to check if you have stock recovery already after performing "unroot2ota" (if not - you need to use PC Odin to flash recovery.img packed in tar file).
- It is recommended to temporarily disable "Auto-update apps" in Play Store settings before you unroot your device. It will prevent updating applications covered by Safe De-Bloat list, as there apps will temporarily appear until you re-root the phone after performing OTA update.
Note (devices which use dm-verity): You should never allow /system modifications in TWRP, never allow to remount /system r/w in any app (e.g. Root Explorer, FlashFire, etc.) and never flash a ZIP file which could modify your /system or remount it r/w. Failure to follow these recommendations will break dm-verity verification and will cause, that your device may not be able to boot with the stock kernel (you will need to re-flash your original FW using PC Odin to make your device bootable).
2. Making your own modifications:
- You can systemlessly replace any existing system app by modded one. Just put modified app to /data/devbase/system/app or /data/devbase/system/priv-app and then reboot your device
- You can systemlessly replace jar or apk in /system/framework. Just put modified one to /data/devbase/system/framework and then reboot your device (NOTE: framework support has been added for advanced users -> there is high risk of bootloop if you do something wrong!)
- You can systemlessly add or override any line in /system/build.prop. Just put (only new or changed) line to /data/devbase/system/build.prop and then reboot your device (NOTE: one additional auto-reboot will be performed if /data/devbase/system/build.prop file has been added, modified or removed. It is not a bug - it is required for the changes in /data/devbase/system/build.prop to take effect!)
- You can systemlessly replace any existing file in /system/csc and /system/etc (but NOT in subdirectories). Just put modified copy of a file to /data/devbase/system/csc or /data/devbase/system/etc and then reboot device
Limitations: original app or file MUST physically exist with the same name in /system, you can NOT add a new app or file this way!
Example 1 (Ad-Blocking): Download the latest Ad-Blocking ZIP installer from THIS thread. Extract "hosts" file (placed in /system/etc inside ZIP file), then copy it to /data/devbase/system/etc, set rw-r--r-- (644) permissions and then reboot device
Example 2 (modded SystemUI): Create "SystemUI" directory in /data/devbase/system/priv-app and then put modified "SystemUI.apk" file into it. Set rwxr-xr-x (755) permissions to "SystemUI" directory, rw-r--r-- (644) permissions to "SystemUI.apk" and then reboot device
Example 3 (De-Bloating a bit more): You can just create empty directories in /data/devbase/system/app (or priv-app) corresponding to applications in /system/app (or priv-app). Alternatively (more advanced method), you can add an app to modded enforceskippingpackages.txt file (you can find it in /data/devbase/system/etc or /data/devbase/system/csc_contents, depending on the original location in /system) and increase number in the 1st line. Second method should not be used by beginners (without a basic knowledge related to UNIX text format)
3. How to manually maintain the newest ROM version:
If you do not care about OTA - you can manually update your device to the newest ROM available @ Sammobile, keeping your original CSC (you need multi-file original FW, I mean separate files for BL/AP/CP/CSC). You need to download 2 ROMs: ROM with the newest changelist and the latest ROM containing your original CSC. Extract both and open in PC Odin BL/AP/CP files from the ROM with highest changelist but open CSC file from the ROM containing your CSC (I recommend to use HOME_CSC_* file to avoid auto-wipe-data). Flash such "mix", re-root and enjoy
Reserved
hello，alexdr
how are you?
i had flashed your nice rom in s5
do you make. rom for s6 edge plus?
_alexndr said:
Download
>> Recent SYSTEMLESS DevBase <<
Click to expand...
Click to collapse
I'm a little bit confused as the download link refers to S7edge SM-G935F
Androidwizzard said:
I'm a little bit confused as the download link refers to S7edge SM-G935F
Click to expand...
Click to collapse
Yes, agrees - DL link refers to S7edge, but only because there is no just "Samsung" device (generally, without number) to choose @ AndroidFileHost
That's why I put such big NOTE at the top of post #1:
SYSTEMLESS DevBase has been developed and physically tested on S7 Edge (G935F), so main thread containing the most detailed description you can find here:
>> [SAMSUNG][6.0+] SYSTEMLESS DevBase | Encryption support | Stock OTA updates <<
However, it should work on ALL SAMSUNG DEVICES running Android 6.0+, so if you are Galaxy S6 Edge+ (G928xx) owner - please place your feedback & discussion here to let me know about device-specific issues or to let me know that everything works perfect
Click to expand...
Click to collapse
merry xmas ,mate
alexndr
There is new version available
Changelog
v1.1:
- Added SYSTEMLESS support for /system/framework
- Added SYSTEMLESS support for /system/build.prop (overrides & additions)
- Added major Android update detection (auto-remove mods for older API to prevent bootloops & FCs)
- Added BusyBox bionic (the most stable and respected release)
- Added logging to /data/devbase/last_boot.log (API & errors)
- Added SuperSU boot patcher version checker (exits su.d boot script if < 2.76)
- Added "Please DO NOT wipe /cache" warning in case of encrypted devices and TWRP recovery
- Minor changes & optimizations in the shell code
- Added SYSTEMLESS DevBase uninstaller
Download link:
>> SYSTEMLESS_DevBase_v1.1.zip <<
Since new version has many more features -> there are more possibilities of bootloop (especially if you are playing with framework mods). I have created DevBase remover to let you get out from bootloop. Of course uninstaller does NOT "know" which mod caused the problem, so it will not remove any file from /data/devbase directory, it will remove only /su/su.d/0000000devbase boot script to make your device bootable (again) so you can manually delete problematic mod:
>> SYSTEMLESS_DevBase_remover.zip <<
Another update:
v1.3:
- Fixed CscFeature MOD (e.g. G920I case, now should work with all Samsung devices/variants)
v1.2:
- Added info in Settings/About device/Software info/Build number (can be overrided by editing /data/devbase/system/build.prop)
- unroot2ota: added ability to restore stock recovery using /system/recovery-from-boot.p file (no guarantee)
- unroot2ota: check /system partition for common modifications before unroot
- Minor changes & improvements in the shell code
>> SYSTEMLESS_DevBase_v1.3.zip <<
DEV ,
tahnks for your hard work .
can you make a s7 edge nougat mod for samsung s6 edge plus ?
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
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 G935FXXU2xxxx_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) 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 - probably there is no better alternative
ROM contains my extended CSC package, which I called G935FAXX (this is a combination of OXX, OXA, OXE, OLB, OJV, OJK + some additional). Final list of available CSC is as follows:
ACR, AFG, AFR, ALE, ARO, ATO, AUT, BGL, BNG, BTC, BTU, BVO, CAC, CAM, CAU, CEL, CHK, CHO, CHP, CHQ, COO, CPW, CYO, DBT, DKR, DRC, ECT, EGY, EON, ETL, EUR, GLB, ILO, INS, INU, ITV, KOR, KSA, LUX, LYS, MAT, MAX, MID, MM1, MRT, MRU, MTZ, MWD, MYM, NEE, NPL, NZC, ORX, PAK, PCL, PCT, PCW, PHE, PHN, PTR, ROM, SEB, SEE, SEK, SER, SIN, SIO, SLI, SLK, SMA, SMG, SKZ, STH, THL, THR, TMC, TPA, TPH, TPL, TRG, TTR, TTT, TUN, TUR, TWO, UPO, UYO, VIM, WTL, XEF, XEH, XEO, XEU, XFA, XFE, XFM, XFU, XID, XME, XSA, XSG, XSP, XTC, XTE, XXV, ZTO
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.G935FXXU8EUE1:
1. Base:
- Odexed (original stock files) + stock kernel
- Multi CSC (list of natively supported CSC as above) (*)
- Removed KNOX related content (useless on rooted phones)
- 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] (*)
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, ALE, ARO, ATO,
# AUT, BGL, BNG, BTC, BTU, BVO, CAC, CAM, CAU, CEL, CHK, CHO, CHP, CHQ, COO, CPW, CYO, DBT, DKR, DRC, ECT,
# EGY, EON, ETL, EUR, GLB, ILO, INS, INU, ITV, KOR, KSA, LUX, LYS, MAT, MAX, MID, MM1, MRT, MRU, MTZ, MWD,
# MYM, NEE, NPL, NZC, ORX, PAK, PCL, PCW, PHE, PHN, PTR, ROM, SEB, SEE, SEK, SER, SIN, SIO, SKZ, SLI, SLK,
# SMA, SMG, STH, THL, THR, TMC, TPA, TPH, TPL, TRG, TTR, TTT, TUN, TUR, TWO, UPO, UYO, VIM, WTL, XEF, XEH,
# XEO, XEU, XFA, XFE, XFM, XFU, XME, XSA, XSG, XSP, XTC, XTE, XXV, ZTO
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/KnoxCore
# 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
FBInstagram_stub.apk
FBServices.apk
FotaAgent.apk
Hangouts.apk
MSSkype_stub.apk
Music2.apk
OneDrive_Samsung_v2.apk
OneNote.apk
Photos.apk
PowerPoint_SamsungStub.apk
Videos.apk
WhatsApp.apk
Word_SamsungStub.apk
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 (NOTE: you will get unmodified ROM!)
(place "noroot" string anywhere in the ZIP file name, e.g. "G935Fxxx_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. "G935Fxxx_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. "G935Fxxx_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_G935Fxxx_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. "G935Fxxx_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
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
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
Installation:
CWM / 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
@Tkkg1994 for TWRP for Oreo (quota support)
@Zackptg5, @osm0sis & @jcadduono for no-verity*
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/_alexndr
Download ROM
>> G935FXXU8EUE1_DevBase_v7.4.zip << (updated Jul-10-2021, more info HERE)
>> SM-G93xF/FD repository (recent ROMs & BL packages) << (MEGA)
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.
Changelog
v7.4 (starting from G935FXXU8EUE1 DevBase):
- Fixed unzip issue which caused unexpected installation termination - applies to TWRP 3.5.0_9-1 and newer
v7.3 (starting from G935FXXU7ETBD DevBase):
- Fixed bootloop issue in case of Android Q and "noroot" scenario - thanks to @Zackptg5 for the up to date dm-verity disabler
v7.2 (not released for G935F):
- Fixed bootloop issue in case of Android Q and encrypted devices (applies to dirty update)
v7.1 (starting from G935FXXS7ETA8 DevBase):
- Potential fix for "make_ext4fs: not found" error in newer TWRP versions and in result "Failed! Not enough space..." message appears while applying CSC during install (applies to N960x devices)
v7.0 (not released for G935F):
- Initial support for Android Q / system-as-root devices
v6.0 (starting from G935FXXU3ERL3 DevBase):
- Introduced logging entire installation process (to devbase_install.log file, placed in /data or /cache in case of encrypted devices). These logs may significantly increase the possibility of my help in case of problems with/after installation
- Major imrovements/bugfixes/optimizations related to Android Pie support (e.g. takes care about special SELinux contexts for /odm content, introduced in Pie)
- Removed SuperSU support. Changed allowed "root" variable value in options.prop to true/false (backward compatible with old options.prop file)
- Removed "skipblcp" option - baseband/modem will be always updated, bootloader need to be flashed separately (update is usually not mandatory)
v5.9 (starting from G935FXXU2ERG2 DevBase):
- Changed device detection method to bootloader's prefix (instead of ro.product.*)
- Improved support for applying custom mods automatically at each ROM's install/update, introduced in v5.6 (added support for etc, fonts, media & usr directories in {storage}/devbase/system)
- Added support for custom {storage}/devbase/post-installation.sh script
v5.8 (starting from G935FXXU2EREM DevBase):
- Improved unzip_flash function in the installer to detect properly more flashing errors (e.g. EXT4 partition mismatch)
- Changed /odm flashing method to file based due to potential /odm partition mismatch (applies to carrier branded treble devices)
- Minor optimizations/improvements in the installer (this time mainly to improve installation speed)
- Busybox has been removed from /system/xbin to run properly some banking apps
v5.7 (starting from G935FXXU2ERD5 DevBase):
- Improved/expanded built-in RMM lock prevention (thanks to @jesec for idea of overriding properties via factory.prop)
- OEM unlock status will always be displayed correctly in Developer options (to avoid confusion) with stock kernel included in the DevBase ROM
v5.6 (starting from G935FXXS2DRDC DevBase):
- Added "App Lock" feature (Settings -> Advanced features)
- Added Xposed framework as installation option (it is NOT forced by default - you need to force it manually while installing with Xposed first time, e.g. by "xposed" string in ZIP's file name, but next ROM's updates will detect and apply Xposed profile automatically, unless you wipe /system - then auto detection is not possible)
- Added support for applying custom mods automatically at each ROM's install/update by placing modded apps in {storage}/devbase/system/(priv-)app or placing modded framework files in {storage}/devbase/system/framework (where {storage} may be: /sdcard, /external_sd or /usb-otg)
v5.5 (starting from G935FXXS2DRCC DevBase):
- Added support for flashing optional, CSC related partitions ($OMR, $PRELOAD)
- Added possibility to update recovery (optional, performs update if exists $NAME/images/recovery.img)
- Partition(s) may be wiped only by writing new block's image
- Minor optimizations / improvements in the installer
v5.4 (starting from G935FXXS2DRC3 DevBase):
- Big step forward in DevBase ROM customization ability - almost all current ROM features (hidden up to v5.3) have been moved to options.prop (you will be able to easy add new or remove current feature)
- Return to dm-verity-opt-encrypt boot patcher if necessary (wherever it works well, there are still devices which need "no_verity" function introduced in v5.1)
- Initial support for forcing (changing) CSC in case of devices with /odm as CSC location
- Minor optimizations / improvements in the installer
v5.3 (not released for G93xx):
- Improved algorithm of search & change "ro.security.vaultkeeper.feature" property to 0 (/system & /vendor)
v5.2 (not released for G93xx):
- Added support for devices with /odm as CSC location
- Added support for flashing $ODM, $VENDOR, $KEYSTORAGE, $DQMDBG images
- Added support for custom debloat list and custom CscFeature list in options.prop
- options.prop file format has been changed to CR/LF (Windows) - more noob-proof solution, user can edit a copy of options.prop file even in Windows Notepad (the installer still supports ANY text format of options.prop file - Win/Unix/MAC)
v5.1 (starting from G935FXXU2DRB7 DevBase):
- Created new "no_verity" function in the installer, compatible with Samsung's Oreo, based on @Chainfire's patch tool (no-verity-opt-encrypt has been removed). In case of Oreo & Magisk as root solution - "no_verity" function will be used as additional support for patching fstab* (as long as Magisk does not do it correctly)
v5.0 (not released for G93xx):
- SYSTEMLESS DevBase has been removed due to the fact, that in case of modern devices/firmwares we need to perform many changes physically in /system anyway, so it loses the sense of use here. If you liked it - you can still install it separately from HERE (it does not need to be re-installed after ROM update as it is installed in /data)
- Added "skipblcp" option to let users skip BL/CP update (additionally it disables auto-reboot when the installer finished work as it is just not necessary then)
- Added "phydebloat" option to let users choose beetween virtual and physical debloat (to get more space in /system)
- Other (minor) optimizations & improvements
v4.6 (starting from G935FXXU2DRAG DevBase):
- Initial support for devices with /system/omc as CSC location
- SYSTEMLESS DevBase updated to v2.0 (see changelog HERE)
- Added possibility to force CSC by renamig ZIP filename. Due to the fact that trere are many different CSC and it is possible that $ZIPNAME may contain a CSC accidentally - to force CSC you need to put CSC in $ZIPNAME at the beginning and CSC must be followed by "_". Example $ZIPNAME (to force CSC DBT): "DBT_G93xFXXU1xxxx_DevBase.zip"
- Added auto efs-backup during install. Installer will create first backup (efs_backup.img.gz) and recent backup (efs_recent.img.gz). The installer will prefer external storage as default backup location (/external_sd or /usb-otg) due to encryption support. MD5 sum and restore command will be stored in efs_backup.txt or efs_recent.txt file
- Other (minor) optimizations & improvements, e.g. added more error messages in case of something went wrong during install
v4.5 (starting from G935FXXU1DQLF DevBase):
- Added new "rescue" option (readable only as string in ZIP file name due to the fact, that we will need this option rarely). It can be a potentially very helpful option in case of bootloop @ encrypted device, caused by a systemless mod/module/xposed stored on /data (without access to /data from TWRP) - more info in post #1
- SYSTEMLESS DevBase updated to v1.14 (see changelog HERE)
v4.4 (starting from G935FXXU1DQL8 DevBase):
- Added new "encrypt" option (readable only as string in ZIP file name due to the fact, that we need to do it only once). Now you can easy encrypt all data in your device, just during the ROM upgrade (without data loss).
- SYSTEMLESS DevBase updated to v1.13 (see changelog HERE)
v4.3 (starting from G935FXXS1DQF6 DevBase):
- "root.supersu" & "root.magisk" variables in the options.prop file have been replaced by one "root" variable (dropped possibility to install both - SuperSU & Magisk - due to the fact that Magisk v13+ does not support SuperSU as root solution)
- SYSTEMLESS DevBase updated to v1.9 v1.12 (see changelog HERE)
v4.2 (starting from G935FXXU1DQD7 DevBase):
- Added possibility to add systemlessly NEW apps to /data/devbase/system/(priv-)app (up to 5 apps in "app" & 5 apps in "priv-app"). The only condition is that you need to rename its directories to CustomApp[1...5] (e.g. CustomApp1, CustomApp2, etc..). These apps will remain even if you flash a new DevBase as corresponding dummy directories will exist in future DevBase updates
- In case of DevBase update or re-installation - installer will not remove your custom entries in /data/devbase/system/build.prop and in *.xml files placed in /data/devbase/system/csc
- SYSTEMLESS DevBase updated to v1.6 v1.8 (see changelog HERE)
v4.1 (starting from G935FXXU1DQD1 DevBase):
- Added full Magisk support - MagiskSU is now default root solution (ROM should pass SafetyNet with Magisk Hide enabled in settings)
- Since systemless Xposed does not need to be re-installed every new DevBase I will release (in case of using the same root solution) - it makes no sense to keep it anymore as installation option
- SYSTEMLESS DevBase updated to v1.5 (see changelog HERE)
v4.0 (not released for G93xx):
- A huge step in the systemless direction! DevBase installer now installs pure odexed stock ROM (just slightly debloated), then systemless SuperSU, then systemless DevBase, then (optionally) systemless Xposed
- All Knox related applications are available again (except SecurityLogAgent, to prevent annoying security alerts)
- Fake KNOX 0x0 status (check it in PhoneINFO app) - most of Knox related apps should work again, like in case of untouched KNOX flag
- All mods known from previous DevBase versions (up to v3.x) now are applied systemlessly - all modified files (including modded apps) are placed in /data/devbase/system instead of physical /system partition. Mods section (#4) has been updated to install mods to /data/devbase/system/(priv-)app if systemless DevBase has been detected (otherwise will be installed as usual, to /system)
- Deodex on-the-fly feature has been removed. If you really need deodexed ROM - you can install someone else's deodexed ROM, then systemless DevBase as an overlay
- Init.d support has been removed as it is deprecated (use su.d instead)
v3.8 (not released for G93xx):
- Added hexpatch to root_from function (support for SM-N930x, thanks to @Chainfire)
v3.7 (not released for G93xx):
- Another major improvement/bugfix in deodex_from function (full support for 64 bit OS)
v3.6 (not released for G93xx):
- Major improvement/bugfix in deodex_from function (added "-g" switch to zip command - finally no issues in case of deodexed Android 6.0.1)
v3.5 (not released for G93xx):
- Improved root_from function (Android 5.1+) - added "setprop selinux.reload_policy 1" removal from init.rc (thanks to @Chainfire)
- Fixed bug in new alghoritm for checking whether stock recovery should be installed or not (introduced in v3.4)
- Added new functionality - installer will store a copy of patched stock kernel in /data for those who flashed custom kernel but for some reasons want to revert to the stock kernel (Android 5.1+)
v3.4 (not released for G93xx):
- Completely changed alghoritm for checking whether stock recovery should be installed or not (it applies to FlashFire users). Now it depends on previously used recovery (instead of checking KNOX flag which was not 100% reliable across devices/recoveries)
v3.32 (not released for G93xx):
- Updated set_csc, kcsc_backup, kcsc_restore functions to support more devices
- Updated partition detection algorithm to support more devices
- Fixed path to options.prop file placed in external sdcard in case of updating Marshmallow while using FlashFire
- Minor intaller's optimizations/bugfixes
v3.31 (not released for G93xx):
- Potential fix for reported problems with root (rare cases)
v3.3 (not released for G93xx):
- Improved method of reading options from ZIP file name (previous was directory/path sensitive also)
- Added support to mod_csc function for other than UNIX text format (it's a little ridiculous, but in case of some CSCs - original /system/csc/other.xml file has Windows or MAC text format!)
- Initial support for options.prop file in CRLF text format (DOS/Windows)
v3.21 (not released for G93xx):
- Fixed installer's issue if there is a [space] present in ZIP filename or a directory containing DevBase (see #1728)
v3.2 (not released for G93xx):
- Another improvements in add_initd function (details - see v1.3)
- Improvements in set_perm, set_perm_rec and root_from functions (recovery-independent structure)
- Improvements in deodex_from function related to Android MM
- New get_con function in the main sh script (useful for devs)
- BusyBox updated to 1.22.1 (bionic) [no, this is NOT a mistake!]
- Minor intaller's optimizations/bugfixes
v3.1 (not released for G93xx):
- Significantly improved "add_initd" function in the update-binary shell script. Added support for (probably) all available Samsung's platforms (e.g. Exynos) and all available firmwares (based on Android 4.4+)
- In case of installation with Xposed framework installer checks if Xposed Installer app is present in /data/app and installs it automatically if necessary
- Minor intaller's optimizations/improvements
v3.0 (not released for G93xx):
- Entire installer has been re-written from the scratch! All "magic" moved to update-binary which is a shell script. It opens up new possibilities never possible before!
- Introduced new customization method - you can change most frequently switched options just by renaming installer's ZIP file name. Currently supported "strings" in the file name:
"noroot" (means "do not root"), "deodex", "xposed", "initd" (no other comments are required, I hope..)
- Starting from v3.0 init.d support is disabled by default
v2.3 (not released for G93xx):
- Added option to install suitable Xposed framework in one step while installing DevBase (for maximum comfort). There is a new xframework.sh script - device independent structure and full Android 5.1+/6.0+ support. Backup method is compatible with well known Xposed uninstallers (tested with @wanam's)
v2.2 (not released for G93xx):
- Significantly improved root_supersu.sh script - device independent structure and full Android 5.1+/6.0+ suport including on the fly kernel/ramdisk/sepolicy patching if necessary. SU binaries are still copied to /system as it is the best choice in case of custom ROMs
- Changed order of performed operations in the updater-script due to new root_supersu.sh script advantages
- Installer wipes partitions designated for RAW content (e.g. kernel / recovery image) before writing to them
- Minor additions in dex_injector.sh script related to Android 6.0+
v2.11 (not released for G93xx):
- Fixed some minor installer's issues ("set_perm" function in set_csc.sh did not work correctly while using wildcards in the path (it was exclusively FlashFire issue! no problem with TWRP / CWM). Fortunately - only /system/etc/csc_*.txt were really "affected" - it didn't cause real issues as these files are empty)
v2.1 (not released for G93xx):
- As some people felt a bit disapointed / worried about DevBase v2.0 ROM file size - finally I have decided to debloat stock system.img (in same way as in v1.x => "Safe De-Bloat") and remove option to install all available bloatware. ROM file size has been reduced from about ~2GB to about ~1.6GB. Note for Devs / Chefs: Do not use Windows tools - you need Linux with "selinux" package installed (to handle SELinux contexts) to mount (rw) system.img safely. If you want to add / change any system content this way - remember about proper chown/chmod/chcon
- Added device check during install as flashing directly to EMMC block is potentially more risky for "other" devices. Installer will abort installation if device is not N910F (trlte(xx)). If you want to try this ROM on other N4 devices - you need to remove this check manually from updater-script (it is more conscious procedure)
v2.0 (not released for G93xx):
- Completely new concept of ROM development that makes it easy to build most tuned and nuanced custom ROMs. No more arduous manual analysis or (often) invalid permissions / SELinux contexts taken from a kitchen. The main idea is to flash original, stock /system image as EMMC block (in same way as PC Odin does) instead of extracting ZIP's contents to mounted partition, then setting permissions, then creating symlinks, etc. However, it requires more knowledge related to sh scripts as ALL necessary changes need to be done on the fly, while installing (e.g. by injecting modified classes.dex and/or modified images/xmls to /res/../* into an apk). There are no limits, all depends on your creativity!
- One common ZIP installer for Odexed and Deodexed ROM - you can control it by new "deodexed.rom" entry in options.prop (there is new dex_injector.sh script which can deodex on the fly the whole ROM using previously processed classes.dex files)
- ROM is still Safe De-Bloated by default but removing bloatware during install is not mandatory - you can control it by new "safe.debloat" entry in options.prop (there is new protection included to avoid overfilling /system in case of large size of additional MODs and/or large multi CSC package)
- Major improvements in csc_detect.sh script - it is able to detect previous CSC even in cases of flashing over e.g. CM based ROM and/or previously formatted system partition. However, if detected CSC is NOT included in my multi CSC package, in both mentioned cases it is still not possible to keep detected CSC (as there is no CSC related content to backup / restore)
- Improvements in all sh scripts - additional "metadata" entries in updater-script (related to processed contents) are not required
- Improvements in root_supersu.sh script - it is suitable for 32 and 64 bit OS
- Added full zip support from the command line
v1.x (initial version, further improvements, not released for G93xx):
- Built without using a kitchen. All set_metadata* / symlink entries are result of arduous manual analysis. For more info about the method - see hidden content for Devs / Chefs in THIS thread.
- New customization method without using Aroma (options.prop)
- Many useful scripts for easy installation: CSC applying/autodetection, backup/restore of security files, backup/restore of existing CSC package, XML modding on the fly, root, init.d support
- Many small changes and improvements "in the meantime" which I simply do not remember...
- Safe De-Bloated (see post #1 for details)
Optional MODs
[WORK IN PROGRESS, MODDING HAS LOW PRIORITY]
These modifications I have done personally using (bak)smali tools - these are NOT "borrowed" from other custom ROM, nor from someone else's thread (thanks to @majdinj, @tdunham, @Grouxho & @yash92duster for their excellent modding guides). All ZIP files are TWRP flashable:
>> MODs for SM-G93xF/FD <<
TIP: Are you tired with re-installing your favorite MODs every time you update this ROM? Just take advantage of the new DevBase feature, intruduced in v5.6 (see "Changelog"). It is enough to put your favorite apks and/or jars in /sdcard/devbase/system/(priv-)app (or ../framework) and these MODs will be detected & applied automatically every time you update this ROM. You can also use your /external_sd to store your favorite MODs (it is mandatory if you are using encryption).
Example for "G93xF_DisableHighVolumeWarning.zip" (modded SystemUI.apk):
- unzip SystemUI.apk file from my flashable MOD
- create /sdcard/devbase/system/priv-app/SystemUI directory
- place modded SystemUI.apk in above directory
Next time you will update my ROM - my installer will use modded SystemUI.apk instead of stock app included in my ROM
NOTE: Use this feature consciously and carefully! It may happen that your MOD is not compatible with a newer Samsung's base (especially in case of major Android update)! I will warn you about it, but only in case of MY MODs, I am not able to predict what kind of mods you are using.
Welcome
Sent from my SM-G955F using Tapatalk
DQD1?
Very nice can't wait
Why no roms have Canadian CSC lol. Iv will give this a try?
Sent from my SM-G935F using XDA-Developers Legacy app
Hi @_alexndr and thanks for the new base, just a couple of questions, could be possible to add UUB CSC or TTT or TPA? this are to be used in Latinamerica
For the other side, is it possible to give indications how to disable safety volume, with this option I will very glad to test your ROM!!! I know I have to modify services.jar, but the question will be where!!
S-Health not working, Knox tripped message.
civato said:
S-Health not working, Knox tripped message.
Click to expand...
Click to collapse
You can add:
Code:
ro.config.tima=0
to /data/devbase/system/build.prop (then reboot)
The advantage of systemless build.prop support is that you need to add it only ONCE.
Your favorite entries stored in /data/devbase/system/build.prop will be used even after another DevBase update (this file will not be touched while the installer run next time)
I will consider to add this line by default by the installer if it does not exists already in /data/devbase/system/build.prop
thanx.
how to use on flat.G930F?
_alexndr said:
You can add:
Code:
ro.config.tima=0
to /data/devbase/system/build.prop (then reboot)
The advantage of systemless build.prop support is that you need to add it only ONCE.
Your favorite entries stored in /data/devbase/system/build.prop will be used even after another DevBase update (this file will not be touched while the installer run next time)
I will consider to add this line by default by the installer if it does not exists already in /data/devbase/system/build.prop
Click to expand...
Click to collapse
Some questions if I may?
1*Is there a way you can do it on installation of the rom. Like adding it in the option.prop or in the update binairy of the devbase.zip?
2*Using a kernel with dm verify disabled (like a custom kernel), what will be the disadvantages of that?
3*Is there a way of installing directly to data/devbase/system (like a modded app) with a zip installed with recovery?
I would also like to say this is a very smooth rom and a good solid way of installing a rom to your needs, Thanks for that!
Calvin.manneson said:
thanx.
how to use on flat.G930F?
Click to expand...
Click to collapse
edit:tried to rename zip and replace images inside the zip....how to fool installer?
@civato.. if you come out of your 'cave' occasionally...hope you tempted to share ...:victory:
edit:success!!
edited update_binary inside zip...flashed ok
:laugh:
Calvin.manneson said:
@civato.. if you come out of your 'cave' occasionally...hope you tempted to share ...:victory:
:laugh:
Click to expand...
Click to collapse
Sorry it is nice and quiet here in the man cave. No time to do a lot of android stuff. I just am reading up on my edge s7.
Can you put bootloader and modem in zip file so we can flash via recovery?
civato said:
Some questions if I may?
1*Is there a way you can do it on installation of the rom. Like adding it in the option.prop or in the update binairy of the devbase.zip?
2*Using a kernel with dm verify disabled (like a custom kernel), what will be the disadvantages of that?
3*Is there a way of installing directly to data/devbase/system (like a modded app) with a zip installed with recovery?
I would also like to say this is a very smooth rom and a good solid way of installing a rom to your needs, Thanks for that!
Click to expand...
Click to collapse
1*I will think about it in the next release
2*Should work with any kernel which can be successfully patched by Magisk or SuperSU (systemless). If you flash a custom kernel - you basically need to reinstall Magisk (or systemless SuperSU) to apply all necessary patches to your new kernel.
There is another way, for advanced users - if your just flashed custom kernel supports init.d (but it is mandatory that scripts need to be executed in post-fs-data) - you can manually put 0000000devbase script to /system/etc/init.d, but you need to remove check for init.supersu.rc / init.magisk.rc file(s) (as there is no official support for this) - in such case systemless mods should work even without systemless root
3*Of course you can do it directly or via ZIP. You can also see my method (slightly expanded for encrption support via /cache) - see MODs for Nougat in post #5 here:
https://forum.xda-developers.com/showthread.php?p=70036256&postcount=5
Calvin.manneson said:
thanx.
how to use on flat.G930F?
Click to expand...
Click to collapse
Calvin.manneson said:
[...]edit:success!!
edited update_binary inside zip...flashed ok
:laugh:
Click to expand...
Click to collapse
I have plan to release also ready to use version for G930F
Work in progress with DQD2 (in both versions - G930F(D)/G935F(D))
This release will contain "ro.config.tima=0" entry in /data/devbase/system/build.prop by default (but only in case of fresh installation, if you install it over previous DQD1 DevBase -> you need to add this line manually as the installer never touch existing file) - due to issue with S-Health reported by @civato
_alexndr said:
1*I will think about it in the next release
Click to expand...
Click to collapse
Also possible to add the
"wlan.wfd.hdcp=disable"
This for screenmirroring support.
I did the things above on my own in the devbase.zip and added the LUX csc as there is still no official support for it. I created one so I got autocorrection in mu csc region on the keyboard. ANd added it to the zip package and made the changes on the option.prop and SW_Configuration.xml so it installs just fine.
One problem I got when I create my own system.img (with the new DQD2) it boots just fine (full clean install) but it got stuck on the Network status checking right after you confirm the samsung legal stuff on the installation wizard.
It just keeps spinning there and doesn't go any further. Any tips?
Edit:
The private mode is it working I did not test it yet or do I need to add a modded "PersonalPageService"
civato said:
Also possible to add the
"wlan.wfd.hdcp=disable"
This for screenmirroring support.
I did the things above on my own in the devbase.zip and added the LUX csc as there is still no official support for it. I created one so I got autocorrection in mu csc region on the keyboard. ANd added it to the zip package and made the changes on the option.prop and SW_Configuration.xml so it installs just fine.
One problem I got when I create my own system.img (with the new DQD2) it boots just fine (full clean install) but it got stuck on the Network status checking right after you confirm the samsung legal stuff on the installation wizard.
It just keeps spinning there and doesn't go any further. Any tips?
Click to expand...
Click to collapse
Good idea to add also "wlan.wfd.hdcp=disable", I forgot about screen mirroring fix :good:
I will add LUX CSC if such CSC will be released oficially with Nougat (I had some bad experience with using old xmls in case of major Android update)
_alexndr said:
Good idea to add also "wlan.wfd.hdcp=disable", I forgot about screen mirroring fix :good:
I will add LUX CSC if such CSC will be released oficially with Nougat (I had some bad experience with using old xmls in case of major Android update)
Click to expand...
Click to collapse
Maybe you can add the official dutch (NL t9) in the T9DB folder so you get autocorrection for the NL typing people. (I extracted that on a official samsung Nougat rom and confirmed it working.
See attachments.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Huawei P8 Custom ROM
*MagicArrow*
3.Version
based on Huawei EMUI European Firmware b399
Magisk-Edition and SuperSU-Edition
Teamwork by Tecalote and KangV
Release-Date: 15.02.2018
Status: stable
Tested and developed on: GRA-L09 c432
should work also on: GRA-UL10 und GRA-UL00
flashed over Firmware: b399 und b398 - clean und dirty
cust in this ROM: only for c432
(if somebody need, I can make cust-patches for other regions)
German-Thread: https://www.android-hilfe.de/forum/root-custom-roms-modding-fuer-huawei-p8.2257/huawei-p8-gra-b399-rom-6-0-emui-4-0-3-magicarrow-v3-bytecalote.866753.html
Known issues/not really a Bug:
A) AdAway is working as preinstalled apk for blocking ads (just enable it after first start) - but if you want to use TCPDUMP or Webserver, please install this apk over the existing one in the ROM as Update: https://androidfilehost.com/?fid=313042859668275788
B) If you flash clean and setup-assistant ask you for WLan Network Connection and you cancle it for the moment - it occurs sometimes on the Magisk Edition an error message like: "No SIM Card found - shoutdown or confirm..." - You just go to confirm and in the next second your SIM Network will be recogniced
C) If you install a new App or change something in settings you may receive from time to time a message: "Dropezone for K-Settings blocked... you can add K-Settings in Phonemanager to Dropezone Apps..." But it is not possible to add K-Settings into Dropezone in European Cust (because Phonemanager does not allow...) So, just ignore this message
Requirements:
- Huawei P8 GRA Phone without branding and with Unlocked Bootloader
- not flashable over Android 5 Lollipop
- for best results: Latest possible Android 6 Firmware for your device
- ore if you come from MagicArrow v2 or v1
- read Install-Instructions
- latest TWRP (see Download-Section)
Features/Infos:
- K-Settings by KangV for b399
- Viper4Android and DolbyAtmos with preinstalled Driver, working with Huawei Musicplayer (and with other Players)
- all the other Apps I have included are uninstallable with native settings /Apps (you dont need systemapp-remover!)
- PMPlus and Kernel Audiutor Mod (reborn) for Advanced Users (just uninstall with settings /Apps, if you dont know what to do with this apps)
- Kernel Audiutor can emulate init.d (without loose green safetynet)
- PMPlus can enable App-Auto-Launch in Phonemanager (but its not easy to configure!!)
Phone Manager and the app PMPlus:
Phone Manager does not include the Autostart Manager in European Firmware. The advantage is: you do not have to worry about anything, everything is controlled automatically - and also works. But the battery consumption is slightly more, since all apps wait in the background to be called.
With the app PMPlus, you can activate the Autostart Manager in the Phone Manager. To do this, start the app, go to Installation and as soon as the succesful message comes, close the app (can be uninstalled thereafter). Now, on screen two of the Phone Manager, the entry "App auto-launch" appears!
But NOTICE - through this upgrade will initially set ALL Autostarts to 0 ! You must manually enable the most important apps in App auto-launch - all apps that should receive push notifications - and, most importantly, SuperSU in the Classic Edition and Magisk Manager in the Magisk edition. Otherwise Root permissions do not work!
Advantage: You have control over which apps should not start at system start or in the background (if you need it rarely)
But you must always remember to activate a newly installed app there if necessary. Example: Amazon, E-Bay, PayPal - some of these apps are coupled and not only need the autostart to work , but also the so-called " app activation " (which appears in Autostart Manager when such apps are installed)
Disadvantage: If the apps are not configured correctly in the mask, you have more trouble than good. So, if you're not control freaks, then let's keep your fingers out of it.
But if you want to activate this function, it is recommended to do it at the end, if you have already installed all the apps you are using and not before!
- Facebook lite (original): I recommend to use this App instead of the BigBrother App Facebook - because it saves a lot of battery on Huawei P8!
- most of Google Apps from system are deleted, only the required Core-Apps not - so if you need more Google Apps - dont flash any GApps, just install it with Playstore (like Maps, Google Play Music.... )
- some nice Designs/Themes onboard (Themes will be copied to your internal storage/HWThemes - you can delete what you dont need)
- App-Clone is supported (in Huawei Launcher)
- VoLTE can be enabled in mobile network settings (if your Provider / SIM support it)
- Magisk-Edition: Magisk 15.3 with Magisk Manager 5.6.0 (please enable Magisk Manager as protected App in Phonemanager)
- Magisk Manager comes with pre-enabled settings for safetynet, dont change them. For example: AdAway works now without systemless host setting in Magisk Manager!
- Enabling systemless host in Magisk Manager Settings would break safetynet!
- Magisk v16 Update available - do it with this steps: https://forum.xda-developers.com/showpost.php?p=75656403&postcount=22
Do not update yet to Magisk v16.1 - it would cause big problems - I will provide a patch zip for the update
- You dont need Universal Safetynet Fix anymore - it break safetynet
- If you install Apps which requires safetynet, enable them first in Magisk Hide before you start them first time.
- Busybox 1.27.2 stable by YashdSaraf and SELinux Permissive Script installed as Magisk Module (required)
- In Superuser Section of Magisk Manager is one component pre-allowed for Root-Rights: com.android.inputdevices (its for communication between Magisk and KangV settings)
- If you receive Root-Request from Kernel Audiutor or another Huawei App if you have uninstalled Kernel Audiutor App - then allow this Root Request too
- The system-partition in Magisk Edition must be untouched after Rom Installation, or you loose cts and basicintegrity=true
- means: dont delete or change anything in system partition (with Root Explorer or system-app remover)
- Xposed Framework systemless by topjohnwu (SDK 23) can work with this Rom (not installed) - but it breaks safetynet!
- SuperSU-Edition: SuperSU 2.82 SR5 with modified launch_daemonsu.sh (for SELinux permissive and init.d support - note: you dont need to enable init.d with Kernel Audiutor in SuperSU-Edition)
- SuperSU-Root systemless with boot.img patching (Phone cancle first reboot after ROM Installation and boot up twice)
- Please enable SuperSU App in Phonemanager /Akkumanager as protected App!
- Known issues: In MagicArrow v1 was SuperSU-Root in system - this can make problems if you update directly to MagicArrow v3, because of the CR-Backup Script in v1. MagicArrow v1 must be 100% unrooted before installing v3
- Busybox 1.27.2 stable by YashdSaraf installed to su/xbin
- Xposed Framework v89 by rovo89 integrated in K-Settings /Xposed Settings: If you like to enable just use button "Install xposed" and confirm (same, if you want to uninstall Xposed Framework...)
- First reboot after Xposed Installing needs about 20 min
- PCB (Perfect Color Bar) module comes together with Xposed Framework (but its not enabled - enable it in Xposed Installer, if you like or uninstall it in settings/ apps...)
Download ROM:
P8-b399_MAv3-magisk.zip: https://www.androidfilehost.com/?fid=890129502657583539
MD5: 0394de70a5c3765914371ba4f5f0164b
FIX for the Network-Information-Query (for both Editions): https://forum.xda-developers.com/showpost.php?p=76416139&postcount=167
P8-b399_MAv3-supersu.zip: https://www.androidfilehost.com/?fid=818070582850493154
MD5: 27074686bfff020977ec09e68f80b0fe
You need this Version of TWRP: twrp-3.1.1-0-grace.img
- if you dont have it already... : https://eu.dl.twrp.me/grace/twrp-3.1.1-0-grace.img
Installation-Guide:
1) Make a TWRP Backup from your current system just for to be sure - use latest TWRP!
2) If you decide to flash clean or dirty, in both cases - Backup your stuff
3) IF YOUR CURRENT SYSTEM IS ROOTED - you must flash Unroot Script with TWRP
- For Magisk use Magisk Uninstaller: http://tiny.cc/latestuninstaller
- for SuperSU use UPDATE-unSU-signed.zip: https://forum.xda-developers.com/showpost.php?p=63615067
4) Soon you flashed Unroot Script, go back to main menu to WIPE /ADVANCED WIPE
- if you want to flash dirty, then wipe: Dalvik/ARTCache - Cache - Cust - System
- if you want to flash clean, then wipe: Dalvik/ARTCache - Cache - Cust - Data - System
5) After wipes flash MagicArrow-ROM and soon its finished, reboot your Phone without wipe Dalvik/Cache (Wipes must be done before flashing!)
6) Note - first Reboot can take up to 20 min, so stay tuned and trink some coffee, tea or beer
Disable Chinese Letters:
The Rom is European, but the K-Settings are from KangV. Thats why the Lunar component is installed in K-Settings (these are the only Chinese letters in this Rom).
To disable Lunar, go to K-Settings:
1) Lockscreen and desktop settings and disable: "Lunar Calendar" and at "Desktop weather lunar"
2) Notification settings - disable: "Show statusbar lunar"
Save Battery:
- NFC (with Google Pay) ist enabled by default - disable it and enable it only for the time you need it
- Location Settings (menu: scan settings) disable WLan and Bluetooth Search while Wlan and Bluetooth is disabled, Navi Apps are working also without this setting.
- You can change Location Service to WLan and mobile Network and enable GPS only if you need it
- Performance is enabled by default - change this in Akku-Manager (part of Phone Manager) to SMART
- Bluetooth enable it - if you use it and disable it - if you dont need it at the moment
- Close Apps in the background you dont use at the moment
Have much fun with this ROM
Many thanks to KangV for his K-Settings Framework
If you like K-Settings - please support KangV: https://www.paypal.me/KangVIP
If you like MagicArrow, you can support this project here: https://www.paypal.me/Tecalote
Many thanks and credits:
@guitarededhero (Viper/Atmos) https://forum.xda-developers.com/nexus-6/themes-apps/viper4android-t2952137
@wanam and @rovo89 and @DVDandroid for the Xposed Framework Development
@HootanParsa (MiXplorer) and @YashdSaraf (BusyBox arm64)
@topjohnwu (systemless Xposed Framework and Magisk)
@Chainfire - SuperSU
@AD2076 for TWRP-Recovery twrp-3.1.1-0-grace.img for Huawei p8 marshmallow
@Blackball - BlackPyramid Theme and Custom Roms for P8 - P9 - P10 - P10 Plus - Mate 9
reserved for updates
reserved for additional Guides
Tecalote said:
Huawei P8 Custom ROM
*MagicArrow*
3.Version
based on Huawei EMUI European Firmware b399
Magisk-Edition and SuperSU-Edition
Teamwork by Tecalote and KangV
Release-Date: 15.02.2018
Status: stable
Tested and developed on: GRA-L09 c432
should work also on: GRA-UL10 und GRA-UL00
flashed over Firmware: b399 und b398 - clean und dirty
cust in this ROM: only for c432
(if somebody need, I can make cust-patches for other regions)
German-Thread:https://www.android-hilfe.de/forum/...ui-4-0-3-magicarrow-v3-bytecalote.866753.html
Known issues/not really a Bug:
A) AdAway is working as preinstalled apk for blocking ads (just enable it after first start) - but if you want to use TCPDUMP or Webserver, please install this apk over the existing one in the ROM as Update: https://androidfilehost.com/?fid=313042859668275788
B) If you flash clean and setup-assistant ask you for WLan Network Connection and you cancle it for the moment - it occurs sometimes on the Magisk Edition an error message like: "No SIM Card found - shoutdown or confirm..." - You just go to confirm and in the next second your SIM Network will be recogniced
C) If you install a new App or change something in settings you may receive from time to time a message: "Dropezone for K-Settings blocked... you can add K-Settings in Phonemanager to Dropezone Apps..." But it is not possible to add K-Settings into Dropezone in European Cust (because Phonemanager does not allow...) So, just ignore this message
Requirements:
- Huawei P8 GRA Phone without branding and with Unlocked Bootloader
- not flashable over Android 5 Lollipop
- for best results: Latest possible Android 6 Firmware for your device
- ore if you come from MagicArrow v2 or v1
- read Install-Instructions
- latest TWRP (see Download-Section)
Features/Infos:
-K-Settings by KangV for b399
-Viper4Android and DolbyAtmos with preinstalled Driver, working with Huawei Musicplayer (and with other Players)
- all the other Apps I have included are uninstallable with native settings /Apps (you dont need systemapp-remover!)
- PMPlus and Kernel Audiutor Mod (reborn) for Advanced Users (just uninstall with settings /Apps, if you dont know what to do with this apps)
- Kernel Audiutor can emulate init.d (without loose green safetynet)
- PMPlus can enable App-Auto-Launch in Phonemanager (but its not easy to configure!!)
Phone Manager and the app PMPlus:
Phone Manager does not include the Autostart Manager in European Firmware. The advantage is: you do not have to worry about anything, everything is controlled automatically - and also works. But the battery consumption is slightly more, since all apps wait in the background to be called.
With the app PMPlus, you can activate the Autostart Manager in the Phone Manager. To do this, start the app, go to Installation and as soon as the succesful message comes, close the app (can be uninstalled thereafter). Now, on screen two of the Phone Manager, the entry "App auto-launch" appears!
But NOTICE - through this upgrade will initially set ALL Autostarts to 0 ! You must manually enable the most important apps in App auto-launch - all apps that should receive push notifications - and, most importantly, SuperSU in the Classic Edition and Magisk Manager in the Magisk edition. Otherwise Root permissions do not work!
Advantage: You have control over which apps should not start at system start or in the background (if you need it rarely)
But you must always remember to activate a newly installed app there if necessary. Example: Amazon, E-Bay, PayPal - some of these apps are coupled and not only need the autostart to work , but also the so-called " app activation " (which appears in Autostart Manager when such apps are installed)
Disadvantage: If the apps are not configured correctly in the mask, you have more trouble than good. So, if you're not control freaks, then let's keep your fingers out of it.
But if you want to activate this function, it is recommended to do it at the end, if you have already installed all the apps you are using and not before!
- Facebook lite (original): I recommend to use this App instead of the BigBrother App Facebook - because it saves a lot of battery on Huawei P8!
- most of Google Apps from system are deleted, only the required Core-Apps not - so if you need more Google Apps - dont flash any GApps, just install it with Playstore (like Maps, Google Play Music.... )
- some nice Designs/Themes onboard (Themes will be copied to your internal storage/HWThemes - you can delete what you dont need)
- App-Clone is supported (in Huawei Launcher)
- VoLTE can be enabled in mobile network settings (if your Provider / SIM support it)
- Magisk-Edition: Magisk 15.3 with Magisk Manager 5.6.0 (please enable Magisk Manager as protected App in Phonemanager)
- Magisk Manager comes with pre-enabled settings for safetynet, dont change them. For example: AdAway works now without systemless host setting in Magisk Manager!
- Enabling systemless host in Magisk Manager Settings would break safetynet!
- You dont need Universal Safetynet Fix anymore - it break safetynet
- If you install Apps which requires safetynet, enable them first in Magisk Hide before you start them first time.
- Busybox 1.27.2 stable by YashdSaraf and SELinux Permissive Script installed as Magisk Module (required)
- In Superuser Section of Magisk Manager is one component pre-allowed for Root-Rights: com.android.inputdevices (its for communication between Magisk and KangV settings)
- If you receive Root-Request from Kernel Audiutor or another Huawei App if you have uninstalled Kernel Audiutor App - then allow this Root Request too
- The system-partition in Magisk Edition must be untouched after Rom Installation, or you loose cts and basicintegrity=true
- means: dont delete or change anything in system partition (with Root Explorer or system-app remover)
- Xposed Framework systemless by topjohnwu (SDK 23) can work with this Rom (not installed) - but it breaks safetynet!
- SuperSU-Edition: SuperSU 2.82 SR5 with modified launch_daemonsu.sh (for SELinux permissive and init.d support - note: you dont need to enable init.d with Kernel Audiutor in SuperSU-Edition)
- SuperSU-Root systemless with boot.img patching (Phone cancle first reboot after ROM Installation and boot up twice)
- Please enable SuperSU App in Phonemanager /Akkumanager as protected App!
- Known issues: In MagicArrow v1 was SuperSU-Root in system - this can make problems if you update directly to MagicArrow v3, because of the CR-Backup Script in v1. MagicArrow v1 must be 100% unrooted before installing v3
- Busybox 1.27.2 stable by YashdSaraf installed to su/xbin
- Xposed Framework v89 by rovo89 integrated in K-Settings /Xposed Settings: If you like to enable just use button "Install xposed" and confirm (same, if you want to uninstall Xposed Framework...)
- First reboot after Xposed Installing needs about 20 min
- PCB (Perfect Color Bar) module comes together with Xposed Framework (but its not enabled - enable it in Xposed Installer, if you like or uninstall it in settings/ apps...)
Download ROM:
P8-b399_MAv3-magisk.zip: https://www.androidfilehost.com/?fid=890129502657583539
MD5: 0394de70a5c3765914371ba4f5f0164b
P8-b399_MAv3-supersu.zip: https://www.androidfilehost.com/?fid=818070582850493154
MD5: 27074686bfff020977ec09e68f80b0fe
You need this Version of TWRP: twrp-3.1.1-0-grace.img
- if you dont have it already... : https://eu.dl.twrp.me/grace/twrp-3.1.1-0-grace.img
Installation-Guide:
1) Make a TWRP Backup from your current system just for to be sure - use latest TWRP!
2) If you decide to flash clean or dirty, in both cases - Backup your stuff
3) IF YOUR CURRENT SYSTEM IS ROOTED - you must flash Unroot Script with TWRP
- For Magisk use Magisk Uninstaller: http://tiny.cc/latestuninstaller
- for SuperSU use UPDATE-unSU-signed.zip: https://forum.xda-developers.com/showpost.php?p=63615067
4) Soon you flashed Unroot Script, go back to main menu to WIPE /ADVANCED WIPE
- if you want to flash dirty, then wipe: Dalvik/ARTCache - Cache - Cust - System
- if you want to flash clean, then wipe: Dalvik/ARTCache - Cache - Cust - Data - System
5) After wipes flash MagicArrow-ROM and soon its finished, reboot your Phone without wipe Dalvik/Cache (Wipes must be done before flashing!)
6) Note - first Reboot can take up to 20 min, so stay tuned and trink some coffee, tea or beer
Disable Chinese Letters:
The Rom is European, but the K-Settings are from KangV. Thats why the Lunar component is installed in K-Settings (these are the only Chinese letters in this Rom).
To disable Lunar, go to K-Settings:
1) Lockscreen and desktop settings and disable: "Lunar Calendar" and at "Desktop weather lunar"
2) Notification settings - disable: "Show statusbar lunar"
Save Battery:
- NFC (with Google Pay) ist enabled by default - disable it and enable it only for the time you need it
- Location Settings (menu: scan settings) disable WLan and Bluetooth Search while Wlan and Bluetooth is disabled, Navi Apps are working also without this setting.
- You can change Location Service to WLan and mobile Network and enable GPS only if you need it
- Performance is enabled by default - change this in Akku-Manager (part of Phone Manager) to SMART
- Bluetooth enable it - if you use it and disable it - if you dont need it at the moment
- Close Apps in the background you dont use at the moment
Have much fun with this ROM
Many thanks to KangV for his K-Settings Framework
If you like K-Settings - please support KangV:https://www.paypal.me/KangVIP
If you like MagicArrow, you can support this project here:https://www.paypal.me/Tecalote
Many thanks and credits:
@guitarededhero (Viper/Atmos) https://forum.xda-developers.com/nexus-6/themes-apps/viper4android-t2952137
@wanam and @rovo89 and @DVDandroid for the Xposed Framework Development
@HootanParsa (MiXplorer) and @YashdSaraf (BusyBox arm64)
@topjohnwu (systemless Xposed Framework and Magisk)
@Chainfire - SuperSU
@AD2076 for TWRP-Recovery twrp-3.1.1-0-grace.img for Huawei p8 marshmallow
@Blackball - BlackPyramid Theme and Custom Roms for P8 - P9 - P10 - P10 Plus - Mate 9
Click to expand...
Click to collapse
fantastic friend, newly installed, all good without any problem, dirty installation to not lose data, test and I will inform, thank you very much again
hey there
congratz to your new rom, well done!
quick question:
after flash my gallery, files and music app lost the abilty to showme my files..
and i allready figured out thats a problem withthe media-Provider-app
buuuut i cant fix it..
any ideas???
regards
Nice job work fine thanks
Rasenverbraucheramt said:
hey there
congratz to your new rom, well done!
quick question:
after flash my gallery, files and music app lost the abilty to showme my files..
and i allready figured out thats a problem with the media-Provider-app
buuuut i cant fix it..
any ideas???
regards
Click to expand...
Click to collapse
I like to know which Gallery and which music App did you flash and which files ? And which path did you use (which App into which directory?) Did you delete the original Huawei Musicplayer/Mediacenter and the original Huawei Gallery?
lespaul79 said:
fantastic friend, newly installed, all good without any problem, dirty installation to not lose data, test and I will inform, thank you very much again
Click to expand...
Click to collapse
Your welcome my friend
Tecalote said:
Your welcome my friend
Click to expand...
Click to collapse
Thank You, Tecalote!
I'll upgrade from MagicArrow v1 (!) one of the following weekends (I have to force myself to backup everything first ).
Quick question about the upgrading instruction you wrote:
- I want to do a clean install from v1 (b391): don't I have to reflash an official b399 first to update baseband/etc??? I hope not!
hello
my device p8 last update
GRA-UL10_C185B391 ?
aswertya said:
hello
my device p8 last update
GRA-UL10_C185B391 ?
Click to expand...
Click to collapse
The last Firmware is from December 2016 - b382 for c185. There's no newer Update available for c185
You must not update your Firmware, just do steps from OP
chros69 said:
Thank You, Tecalote!
I'll upgrade from MagicArrow v1 (!) one of the following weekends (I have to force myself to backup everything first ).
Quick question about the upgrading instruction you wrote:
- I want to do a clean install from v1 (b391): don't I have to reflash an official b399 first to update baseband/etc??? I hope not!
Click to expand...
Click to collapse
If you really want to do it complete clean, you should flash for L09c432 Full Firmware b399 with Factoryreset after.
I will write in #2 how to do with links and so on...
All perfect my friend
I have version 2 arrow magisk instaled,the correctway to update is uninstall magisk and after that flash with version 3 arrow magisk?
Cientista2018 said:
I have version 2 arrow magisk instaled,the correctway to update is uninstall magisk and after that flash with version 3 arrow magisk?
Click to expand...
Click to collapse
Yes just do Install Guide from Post #1 of this Thread (OP)
I've got GRA-UL00 with MagicArrow v2. Just updated it to v3 (dirty install), works fine.
I'm using version with SuperSU but thinking to switch over to Magisk. Do i need some additional steps than unroot, wipe and flash magisk version?
Thanks for the ROM. Is the missing 2G only option because it's not in the base ROM?
3G/HSDPA seem to display correctly now. I like having the option to force 2G only as there are a couple of areas where the 4G and 3G signal is very low.
Again, thanks for the ROM.
Morun said:
I've got GRA-UL00 with MagicArrow v2. Just updated it to v3 (dirty install), works fine.
I'm using version with SuperSU but thinking to switch over to Magisk. Do i need some additional steps than unroot, wipe and flash magisk version?
Click to expand...
Click to collapse
No additional steps, just as you said
beardedwonder said:
Thanks for the ROM. Is the missing 2G only option because it's not in the base ROM?
3G/HSDPA seem to display correctly now. I like having the option to force 2G only as there are a couple of areas where the 4G and 3G signal is very low.
Again, thanks for the ROM.
Click to expand...
Click to collapse
I have 2G only, 3G only, 2G/3G automatic and 4G/3G/2G automatic... (see screenshot) - but I have updated Firmware before installing the Rom.
Tecalote said:
I have 2G only, 3G only, 2G/3G automatic and 4G/3G/2G automatic... (see screenshot) - but I have updated Firmware before installing the Rom.
Click to expand...
Click to collapse
Which firmware are you on? I'm willing to do a full backup and install of that firmware then your ROM as I've had some dropped calls.