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 G960FXXU1xxxx_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 - there is no better alternative I think
ROM for G960F/FD contains slightly modified OXM multi CSC package, list of available CSCs is as follow:
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
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.G960FXXU1ARC5:
1. Base:
- Odexed (original stock files) + stock kernel
- Multi CSC OXM (list of natively supported CSC as above) (*)
- Removed / skipped SecurityLogAgent.apk (annoying on rooted phones)
- Removed / skipped Rlc.apk (to avoid "OEM unlock issue")
- Rooted systemlessly (Magisk v16.1 or SuperSU 2.82 SR5) (*)
- All original features are present and works (except Samsung KNOX related apps)
- 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 "Exit Internet" option to stock browser
- Added "Call/Message block" option in Settings
- Added symbols as secondary keys in Samsung keyboard (may not work for all CSCs)
- 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 (added "Record" button)
- Enabled "Recent App Protection" feature
3. 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 with the selected method. Allowed values:
# magisk - install Magisk & MagiskSU as root solution
# supersu - install SuperSU as root solution & suhide (default)
# noroot - do not root device
root=magisk
# Possibility to remove bloatware physically from /system. Virtual debloat is
# normally applied instead of physical with exact same effect, so please use this
# option only if you really need more free space in /system. Allowed values:
# false - use virtual debloat to remove useless apps (default)
# true - remove bloatware physically from /system
phydebloat=false
# Possibility to skip flashing BL/CP (Exynos devices). It will also skip
# auto-reboot when the installation has finished (it is normally required
# for flashing BL/CP operation to pass successfully). Allowed values:
# false - flash the newest BL/CP matched to the ROM (default)
# true - do NOT update BL/CP and skip installer's auto-reboot
skipblcp=false
# CSC Selection. Allowed values:
# KCSC - Keep current CSC, recommended in most cases (automatic selection or copy your 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" does nothing):
<Example_line1>value</Example_line1>
<Example_line2>value</Example_line2>
# Custom debloat list. Allowed value in each line: exact app name with .apk extension.
# (NOTE: without app's path/directory, without spaces after extension, no wildcards!)
Example_system_app1.apk
Example_system_app2.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: "magisk", "supersu", "noroot", "encrypt", "rescue", "skipblcp", "phydebloat", "CSC_xxxx.zip":
Case 1 (default) - install the ROM with Magisk & MagiskSU as root solution
(just flash ZIP file "as it is")
EDIT: Magisk does not work in G960F (yet), SuperSU is temporarily default root solution..
Case 2 - install the ROM with SuperSU as root solution, without Magisk
(place "supersu" string anywhere in the ZIP file name, e.g. "G960Fxxx_DevBase_v5.x_supersu.zip")
Case 3 - do not root device
(place "noroot" string anywhere in the ZIP file name, e.g. "G960Fxxx_DevBase_v5.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_v5.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. EDIT: Encryption is not supported in G960F (yet)..
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. "G960Fxxx_DevBase_v5.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_G960Fxxx_DevBase_v5.x.zip"
In DevBase ROM v5.0+ there is a "skipblcp" option which allows you to skip BL/CP update (it also disables auto-reboot when the installer finished work as it is just not necessary then). Just place "skipblcp" string anywhere in the ZIP file name, e.g. "G960Fxxx_DevBase_v5.x_skipblcp.zip" and then install the ROM.
In DevBase ROM v5.0+ there is also a "phydebloat" option which allows you to remove apps physically instead of virtually while de-bloating. Virtual de-bloat is a reversible method - you can easy restore any app by editing enforceskippingpackages.txt file. It has exact same effect as removing apps physically (it completely skips apps at boot), so forcing to delete apps physically is recommended only if you really need more space in /system.
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
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 formats before install my DevBase (my installer cleans your system well enough!).
Credits:
@Chainfire for systemless SuperSU and a lot of inspiration
@topjohnwu for Magisk and another inspiration
@Tkkg1994 for pre-patched stock kernel for G96xF
@Duncan1982 & @bennebartsch for initial tests
Hit Thanks button if you like my work. If you really appreciate my work - feel free to buy me a beer
Download ROM
>> G960FXXU1ARC5_DevBase_v5.3.zip << (Android 8.0, updated Mar-19-2018)
>> SM-G960F/FD repository <<
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
v5.3 (starting from G960FXXU1ARC5 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 G960FXXU1ARC5 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 G960F):
- 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 G960F):
- 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 G960F):
- 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_G960FXXU3xxxx_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 G960F):
- 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 G960F):
- 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 G960F):
- "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 G960F):
- 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 G960F):
- 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 G960F):
- 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 G960F):
- Added hexpatch to root_from function (support for SM-N930x, thanks to @Chainfire)
v3.7 (not released for G960F):
- Another major improvement/bugfix in deodex_from function (full support for 64 bit OS)
v3.6 (not released for G960F):
- 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 G960F):
- 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 G960F):
- 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 G960F):
- 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 G960F):
- Potential fix for reported problems with root (rare cases)
v3.3 (not released for G960F):
- 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 G960F):
- 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 G960F):
- 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 G960F):
- 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 G960F):
- 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 G960F):
- 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 G960F):
- 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 G960F):
- 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 G960F):
- 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 G960F):
- 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 G960F):
- 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)
Reserved #4
First again ;D. Welcome!
@_alexndr
Is Knox fully removed and all Samsung Security disabled in build.prop?
iamnotkurtcobain said:
@_alexndr
Is Knox fully removed and all Samsung Security disabled in build.prop?
Click to expand...
Click to collapse
If we are talking about really important Knox content, whose presence is annoying or harmful to the rooted phone - then YES
If we are talking about all apps with *knox* in file name, whose presence just does nothing - then NO
You can of course have your own opinion on this subject - that's why there is a possibility to add your own debloat list to options.prop file (then just place modified options.prop file in the root directory of /sdcard or /external_sd - these settings will be used by the installer as long as it exist)
build.prop changes:
Code:
ro.security.vaultkeeper.feature=0
wlan.wfd.hdcp=disable
ro.config.tima=0
_alexndr said:
If we are talking about really important Knox content, whose presence is annoying or harmful to the rooted phone - then YES
If we are talking about all apps with *knox* in file name, whose presence just does nothing - then NO
You can of course have your own opinion on this subject - that's why there is a possibility to add your own debloat list to options.prop file (then just place modified options.prop file in the root directory of /sdcard or /external_sd - these settings will be used by the installer as long as it exist)
build.prop changes:
Click to expand...
Click to collapse
The vaultkeeper line isn't in build.prop. I checked.
Security Log Agent is also still there. Isn't that bad?
iamnotkurtcobain said:
The vaultkeeper line isn't in build.prop. I checked.
Security Log Agent is also still there. Isn't that bad?
Click to expand...
Click to collapse
You probably checked it wrong
First: You need to check necessary changes in already installed ROM, NOT by extracting system.img
In my ROM concept there are pure stock images in ALEXNDR/images - my installer performs all necessary changes on the fly while installing including changes in build.prop
Secondly: Even if you will see an app in /system which SHOULD be removed - this is not necessarily bad [emoji14] because there are 2 scenarios of removing unnecessary apps in my ROM:
- virtual (default) - unnecessary apps are added to enforceskippingpackages.txt file - that means that these apps will be completely skipped/ignored at boot (even if physically exists)
- physical (may be forced by editing options.prop or by renamig ZIP file) - unnecessary apps will be romoved physically
Please read carefully post #1 (it has been updated)
I have the Rom installed that's why I asked
Security Log Agent is there, RLC too. Removed both.
iamnotkurtcobain said:
I have the Rom installed that's why I asked
Security Log Agent is there, RLC too. Removed both.
Click to expand...
Click to collapse
But it completely does not matter as long as these apps exists in /odm/omc/{your_csc}/etc/enforceskippingpackages.txt
If its presence in /system bother you - you can force "phydebloat" in the future by placing your custom options.prop file in the phone
EDIT: @iamnotkurtcobain, I must admit that you were right about ro.security.vaultkeeper.feature line in build.prop (I just edited post #7) There is NO ro.security.vaultkeeper.feature=1 line in original build.prop, so the installer just was not able to change it to ro.security.vaultkeeper.feature=0
In exact same way works this patch:
https://forum.xda-developers.com/showpost.php?p=75360965&postcount=22
If you flash it - you will see that ro.security.vaultkeeper.feature=0 line also will NOT be added. I will try to discern if it is necessary even if ro.security.vaultkeeper.feature line does not exist at all. Thanks for being vigilant :good:
EDIT2: ro.security.vaultkeeper.feature=1 line exists in original /vendor/build.prop and (starting from v5.3) its value will be changed to "0" during install
_alexndr said:
But it completely does not matter as long as these apps exists in /odm/omc/{your_csc}/etc/enforceskippingpackages.txt
If its presence in /system bother you - you can force "phydebloat" in the future by placing your custom options.prop file in the phone
EDITiamnotkurtcobain, I must admit that you were right about ro.security.vaultkeeper.feature line in build.prop (I just edited post #7) There is NO ro.security.vaultkeeper.feature=1 line in original build.prop, so the installer just was not able to change it to ro.security.vaultkeeper.feature=0
In exact same way works this patch:
https://forum.xda-developers.com/showpost.php?p=75360965&postcount=22
If you flash it - you will see that ro.security.vaultkeeper.feature=0 line also will NOT be added. I will try to discern if it is necessary even if ro.security.vaultkeeper.feature line does not exist at all. Thanks for being vigilant :good:
Click to expand...
Click to collapse
Lol np mate
Another question. Did you encounter any superSU issues?
I use TWRP and superSU the last few days and it worked perfectly (stock Rom, debloated myself). No superSU hangs, crashes.
Today I flashed your Rom (really great btw) because I wanted to install fresh and half an hour ago I had a root problem. Apps that use root started to hang and crash.
Really strange.
Hope magisk is working soon.
I flashed your @_alexndr ROM and everything works perfectly and I'm looking forward to even more mods. :good:
Maybe something which protects the battery more.
:laugh:
if someone has problems: with the SuperSU just flash over it in TWRP again.
Works fine with the current version.
Is secure folder still working with this rom?
mix1987 said:
Is secure folder still working with this rom?
Click to expand...
Click to collapse
As far as I know - these apps will never work with KNOX 0x1 (at least in case of S8 or newer device):
- Samsung Pay
- Samsung Pass
- Secure Folder
Fake KNOX 0x0 status also will not help
Thread has been updated
v5.3:
- 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)
@_alexndr
Looking forward to version 5.4
Due to the fact, that I support both devices (S9/S9+) and S9/S9+ cross device section jus has been created - please move all discussion here:
https://forum.xda-developers.com/galaxy-s9-plus/development/rom-u1arc5-devbase-v5-2-t3764822
(I just sent request to move above thread to S9/S9+ cross-device development)
_alexndr said:
Download ROM
>> G960FXXU1ARC5_DevBase_v5.3.zip << (Android 8.0, updated Mar-19-2018)
>> SM-G960F/FD repository <<
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.
Click to expand...
Click to collapse
Thread closed at OP request:good:
Related
{
"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"
}
What does this rom feature? Well it is based off from the latest G935FXXU2ERG2 (Oreo) base, with all apps removed that can be downloaded threw the playstore, so it is debloated as well. I really like touchwiz as it is on 8.0, that's why I only mode some small modifications to samsungs firmware.
In the future I will add some mods as well, but at the moment I'm confident with the mods I got
You have a question and want to check if it already has been answered? Please check the Q&A Post!
Who should install this rom? All people who like samsungs stock interface with some modifications
Also I'd like to make the super fast experience of the s7 even faster, with even more batterylife, let's see if this can be true
Nobody is allowed to take stuff from my rom without asking me! Thank you.
IF YOU FOLLOW MY STEPS BELOW, YOU WILL MAY LOSE YOUR WARRANTY, KNOX WILL DISPLAY 0x1! I'M NOT RESPONSIBLE FOR ANY DAMAGED DEVICE!
Rom features of V3.0.1 Oreo:
- Based on latest G935FXXU2ERG2 Oreo base
- Latest Busybox installed (1.29.2)
- Aroma installer! with support up to 4GB zip files
- Full edge support features support
- Adblocker enabled or disabled (choose in aroma)
- Full rom control!! V2.1
- Zipaligned
- First fully deodexed rom without odex framework
- Rom informations and logo
- choose IOS or stock emojis in aroma
- DM-Verity disabled
- Force encrypt disabled
- ADB fully working
- Modded SystemUI with many tweaks in RomControl
- Applock feature supported
- Floating Message support
- Many csc tweaks!
- No sms to mms auto convertion
- Auto Call recording
- 3Minit Clock/battery in romcontrol
- Custom clock positions and customizations in romcontrol
- LED indicator in settings
- USB Plug/Unplug disable wake up
- Remove high volume warning for headphones
- Private mode fixed for all kernels
- Enable TouchKey light duration in RomControl
- Knox stuff is removed
- Stock ERH1 Kernel, SuperStock-Kernel or SuperKernel (choose in aroma)
- Based off from latest touchwiz source available at this moment
- Many apps are selectable in aroma debloat menu now
- Selinux permissive on custom kernels
- Sound Mod with lot improvements! (choose in aroma)
- Latest Xposed V90.2 beta 3
- July Security Patch
- Camera Mod included (choose in aroma)
- Many other features, please read changelog to see what changed over the time
Rom review (thanks to @shark jungle):
How to install the rom:
For guys who install roms all day:
1. Be sure you got latest TWRP installed, encryption disabled and OEM Unlock ticked
2. Bootloader and modem should be up to date (can also be updated within aroma installer)
3. Flash rom and don't chose magisk in aroma, it messes with the dalvik-cache build on startup
4. In case you want VoLTE and Wifi calling make sure you got your csc installed
For guys who already have some knowledge about android and Roms:
0. Make sure you have a not encrypted device and OEM unlock is enabled in developer settings!!
1. Download the LATESTTWRP recovery(from here: TWRP) and follow the instructions on the TWRP page to get a working recovery (this step is essential!)
2. Download the rom and put it on your external SD card
3. Backup all your things to your external SD card (apps with Titanium Backup for example)
4. It's recommend to update your bootloader to G930FXXU2ERG2 and modem to G930FXXU2ERG2. You can update manually via odin flashing the files from here or update the Bootloader and modem via the aroma installer (only F/FD models can update BL/CP during flashing progress!)
5. If you have to install the bootloader and modem, boot into download mode and flash the bootloader and modem with latest odin using CP and BL tab
6. After you successfully installed your new bootloader and modem, boot your phone to your TWRP recovery
7. Now wipe everything (in TWRP: wipe, format data (keyboard will pop up), type yes, reboot recovery
8. Install the rom and DON'T chose magisk! That is important as it messes up dalvik-cache build on first boot
9. Install your providers/carriers csc
10. Reboot and wait around 10 minute (deodexed roms need longer to boot the first time)
11. Don't interrupt the process of booting the phone, even when it restarts
12. After successfull boot, setup your phone with the initial screens
13. Reboot your phone into TWRP and flash magisk (find it here)
14. After setting up your account etc. go to romcontrol, grant it root access that my default Settings can be applied!
15. Enjoy the new rom version
For guys who are beginner on android:
1. Start your phone, go to settings, about device, software info and hit build.number around 10 times so developer options will show up
2. Open developer options and tick: OEM unlock
3. Shut your phone off
4. You now need a computer, download latest odin
5. You have two possibilites: 1. Update bootloader and modem during aroma installation of the rom (F/FD/W8 model only!). Or 2. Update bootloader and modem via Odin. To update manually via odin, please do following: Download this two files, BL is bootloader and CP is the modem: Choose your correct model version
6. Boot your phone into download mode by pressing: home+volume down+power on
7. Open the downloaded odin on your windows pc and click on BL tab and add the file that name begins with BL (bootloader), same for CP (modem) tab
8. After this, reboot to download mode again
9. Install TWRP (latest one is needed to support new BL's) will be next step, for this, follow all steps provided in this forum: TWRP Thread (booting into download mode: press home+volume down+power on, booting into recovery mode press: home+volume up+power on)
10. When you got TWRP working: We need to disable encryption, for this you should boot into recovery mode (as described above)
11. To get rid of encryption, go to "wipe", format data (keyboard will pop up) then type "yes" and format it, then reboot to recovery
12. After flashing this, hit wipe, full wipe (this will clean all internal memory and your data will be lost!!)
13. You can test if encryption is still enabled, if TWRP shows error about not mounting /data your phone is still encrypted
14. Now you can download the rom onto your PC and then transfer it via usb to your phone
15. It is rom installing time install the rom! One important thing to mention here: don't chose magisk as root. Why? It messes up dalvik-cache on first boot and that will result in a lagging device. We will setup magisk later on.
16. Install your desired CSC right after rom install! That's the best way. You find the link below.
17. After successfully installing the rom and csc hit reboot and you are good to go!
18. After successfull boot, setup your phone with the initial screens
19. After the initial setup, boot into twrp recovery and install the magisk zip. You can download it from here.
20. After flashing the magisk etc. go to romcontrol, grant it root access that my default Settings can be applied!
21. Enjoy the new rom version
22. If you want you can use my csc selection to get your desired csc, if you want that you can grab it here: CSC Selection V2.4.5
For guys who want to watch with a video (thanks to @aaj!):
Downloads for SM-G930F/FD/K/L/S/W8:
V3.0.1 on Androidfilehost
V3.0.1 via GrifoDev
SM-G935F/FD/K/L/S/W8 Bootloader and Modems
CSC Selection V2.5.0
Latest SuperMan MM release (V1.19.1)
Latest SuperMan N release (V2.9.0)
Useful links:
Question and Answer post
Question and Answer Thread for users under 10 posts
All Changelogs
General useful links and infos
DarkSide of N theme infos
Telegram/GrifoDev Links:
Our own new Forum on grifodev.ch
Telegram SuperMan Chat
Telegram Channel (latest infos)
Known Bugs:
- None
Sources:
- Rom Source
- SuperKernel Source
- SuperStock Source
- RomControl Source
Official XDA signatures made by @Quicksilver:
Credits:
- Samsung for the Source
- SuperR for the Kitchen
- Chainfire for the root access
- Sound mod V19 thanks to zubi182
- amarullz for aroma and nkk71 to make it compatible with bigger zip files
- wubydax and daxgirl for SuperMan control
- topjohnwu for systemless Magisk
- myellow for all the great animations!
- mwilky for his fingerprint after reboot mod and general help
- Asc1977 for all the help on latest N release!
- zeroprobe for his camera mod V8
- "Superman DC Universe Online" by "Fictional-Battle-Omniverse", available under CC BY-SA 3.0
- Credits for settings landscape: Designed by Freepik
- If I forgot someone, please send a private Message to me!
Please hit thanks if you like this work here or you may want to buy me a beer? You can donate down here clicking the image or the link
PayPal
SuperControl Pro on PlayStore
XDA:DevDB Information
SuperMan-Rom for herolte, ROM for the Samsung Galaxy S7
Contributors
Tkkg1994
Source Code: https://gitlab.com/Tkkg1994/SuperMan-Rom
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
ROM Firmware Required: Custom Recovery
Based On: Stock Based
Version Information
Status: Stable
Current Stable Version: V3.0.1
Stable Release Date: 2018-08-31
Created 2016-04-11
Last Updated 2018-09-25
Changelog:
Old Marshmallow V1.X Changelogs:
SuperMan-Rom V1.10:
- Rebased on G935FXXS1APG5 firmware
- all mods remade by zero
- added potato clock into aroma options
- updated xposed to V86.2
- updated xposed application
- fixed s7 splash screen not centred
- fixed USSD codes not working for some users
- removed weather on lockscreen (could not find a good way for romcontrol)
- update OTA icon and romcontrol icon in settings (thanks to @myellow)
- added screenshot and screenrecorder buttons to reboot menu
- added settings and qs observer
- Added aroma option for stock or new message app
- some more things I may forgot
SuperMan-Rom V1.10.5:
- Added new RomControl V2.0
- LockScreen Timeout adjustable
- Updated battery bar to V2
- Updated traffic manager (network speed)
- added a button to statusbar (so reboot menu will appear)
- added data usage to statusbar
- added a switch in rom control for multi user avatar
- made a switch for heads up notifications
- added a switch for on ongoing charging and media connected
- enable gear device infos
- enabled carrier lable (color and custom can be set)
- Notification panel background can be set
- rounded or stock notifications can be set in romcontrol (also background of them)
- custom background for incall UI
- Added weather on lockscreen to rom control
- Next alarm will now only be displayed if a new alarm is set (and the icon will not be there if no alarm is set)
- Many more things I may forgot
SuperMan-Rom V1.11:
- Fully rebased to APGO firmware (not rebased to BPH6, reason: no kernel source, not rootable and no edge build...)
- fully remade all mods from scratch
- 3dot lag solved, finally!
- added torch to reboot menu (rom control entry)
- battery percentage is now colorable (rom control)
- added ram bar to recent (rom control)
- enabled lockscreen rotation (rom control)
- low battery warning is now adjustable (rom control)
- flashlight on camera can now be used on low battery too
- Updated SuperKernel to 1.6
- SuperStock updated to 1.2
- private mode now fully working, even after reboot
- fully customize the brightness slider in statusbar (rom control)
- network speed has now two separate colors for up and download
- magisk v3 with PHH's root added (this option needs a FULL WIPE)
- Xposed V86.4 added (only works with magisk)
- long press back key to kill application (rom control toggle)
- cleaned up rom control in general, was a bit messy
- added adaway and ota to settings (thank to @myellow for the icons!)
- added new modded camera thank to @zeroprobe
- updated CSC to APG1
- updated 3minit app
- added f2fs/ext4 selection to aroma. If you do not understand this, just keep default ext4 and change nothing, f2fs is applied to cache and data, system does result in a bootloop
- more things I may forgot
- I did not have time yet to fix the white on white background on notification, for this just change general background in rom control. same for the weather widget, will do this in next release!
SuperMan-Rom V1.12:
- Fully rebased and remodded on BPH6 source (flat users can use the new BL since we got a twrp update)
- removed colorable battery percentage (because of issues with white on white background)
- new gallery app included
- august security patches applied
- superkernel updated to V1.7 and superstock to V1.3
- Added a toggle to remove emergency mode from reboot menu
- Added rom control option to enable music skip
- Update notification background, it can now also be transparent (should fix white on white issue)
- Added carrier label is now colorable on lockscreen
- you can now change the size of the font in settings (so you can read it better when you got two sections)
- magisk updated to V6
- phh's root updated
- xposed updated to V86.5
- added magisk compatible supersu zip
- virtual lock buttons updated
- weather on lockscreen updated, thanks to @tamirda for his help!
- csc updated to ITV BPH1
SuperMan-Rom V1.13:
- Rebased on official BPHJ base
- all mods remade from scratch
- stock kernel updated (BPHJ), superkernel and superstock updated with latest ramdisk
- added autostart option to settings
- removed FOTA (since we don't get any official updates)
- updated supersu to V2.78
- added magisk busybox
- added magisk viper4android
- updated romcontrol to V2.1
- colorable wifi, LTE, airplane, roaming toggle
- added toast notification who are configurable (romcontrol)
- Superkernel has for this special version NO OC and UC (for testing) if it get's better with freezing
- fixed quicklaunch in recent not appearing
- Fix problem that incallui bg is the same as notification bg
- Camera mod to V5 updated
- September patches
SuperMan-Rom V1.13.1:
- fixed 2 times autostart
- fixed gallery crashing
- fixed gear vr crashing
SuperMan-Rom V1.14:
- Fully rebased and remodded on BPIF
- latest BPIF ZTO csc included
- updated supersu to SR1
- updated xposed installer application
- autocall recorder fixed
- Superstock updated to 1.4 (including BPIF ramdisk)
- SuperKernel updated to 1.8 (Prerelease on rom)
- Enabled launcher rotation
- colorable clear and notif buttons
- colorable user text on lockscreen
- hopefully fix applock
- add torch into settings
- last but best feature: use fingerprint after a reboot, biggest thanks to @mwilky for his awesome work he did there!
SuperMan-Rom V1.14.5:
- iOS 10 emojis added
- screenshots are colorable now in romcontrol
- reworked xposed/supersu selection in aroma
- added phh latest supersuser
- updated magisk to V7
- Updated xposed to V86.6
- Updated all magisk mods
- Added TW swipe to modded launcher
- Updated superkernel to 1.8.5
- Updated superstock 1.4.5
- Romcontrol default values adjusted
- zubis sound mod updated to V18
- Adblocker updated
- Phh's apk updated to latest beta (looks much nicer now)
- xposed apk updated
- magisk apk updated
- samsung music apk updated
SuperMan-Rom V1.15:
- Rebased on latest BPJ7
- Remodded and retweaked everything
- Fixed volume rocker problem
- Install supersu before magisk so magisk is compatible now with supersu
- Magisk updated to V8
- Magiskmanager updated
- Remade aroma installer, hopefully little bit clearer now
- UDS and Screencast toggle in statusbar
- InCallUI colorable
- Fixed superman control FC
- Updated both kernels with latest ramdisk base
- Fixed some synapse stuff (eg after clean flash no UCI support showed)
- October security patches included
- CSC updated to latest INS one
- Replaced potato clock with 3minit clock
- Many more things I already forgot again lol
SuperMan-Rom V1.15.5:
- Fixed toast message not working in romcontrol
- fixed contacts crash
- updated sms application (the patched one, should now support more lanuages)
- updated applock
- updated floating message
- added network powersaving
- updated all kernels (except stock) to fix the urgent security issue
- updated phh superuser apk
- changed to DBT csc as default, hopefully for those who had problem with volte it will work now
- changed debloat title, was confusing before
- remind users at the end of installation to flash csc
SuperMan-Rom V1.16:
- Update to base BPJG
- November security patches
- remodded from scratch
- busybox updated to 1.25
- busybox app updated
- launcher rotation disabled (no one seems to like it)
- magisk app updated
- magisk phh root updated to r266-2
- updated all kernels to BPJE source drop base
- Xposed apk updated
- new smali/baksmali method used for deodex
- hidesu phh root added (r266)
- OperaMax apk as debloat in aroma (and without any launcher icon now)
- UPSM apk as debloat app in aroma (to control apps on UPSM)
- added double tap to sleep on statusbar (credits to @tamirda)
- adaway enabled or disabled in aroma (because of 3minit battery)
- fixed AppLock fcs because of signature
- fixed sms patch apk scheduled settings
- added samsung nougat emojis
- added aroma selection for csc. Default would be ITV as it is the base for it. You can also chose to install no csc when you flash the csc selection right after rom install
- eventually some more things I don't remember
SuperMan-Rom V1.17:
- Based on BPKA firmware
- Remodded and retweaked from scratch
- Updated Magisk to V9
- Updated Magisk Manager to V2.5
- Updated SuperSU to SR4 (I know there is SR5 now but I don't want to reupload the rom just cause of this)
- Updated AdBlocker apk to latest official release
- Updated Host file
- Ask in aroma if you want to update modem, will be flashed if you like (BPJG is still latest), so Modem is now updatable in TWRP
- Added BL (bootloader) update to aroma (I added a warning, WHEN UPDATING BL, PHONE DOES AUTOREBOOT AFTER SUCCESSFUL INSTALLATION) Means you need to flash csc after first boot, so my suggestion is: flash rom without BL and flash it in odin. So you can set up your csc correctly
- All ramdisks updated to BPKA
- Changed CSC to AUT (since we never had issues with it)
- Updated baksmali/smali
- Added some files which will may help for wifi calling (please tell me if it worked)
- Changed operamax with official one from playstore (many of you thought it is a spam app)
- Updated Xposed Installer APK
- Updated Xposed Framework to V87
- some things I forgot
SuperMan-Rom V1.18:
- Rebased on latest BPL3 base
- December security patch
- Phh superuser updated to r275
- Many aroma script changes
- SuperKernel updated to 1.9.5
- SuperStock updated to 1.5.6
- host file updated
- Updated build-in bootloader and modem to BPL3 and BPKG
- Backup function! When you reflash V1.18 you now have to option to restore your configs from last time in aroma installer and jump directly to install screen!
- Added kernel adiutor to kernel selection
- No more model choose! Everything is done by my script
- If you have a K/L/S/W8 model, that will be changed in build.prop accordingly
- Added an option in aroma to install full stock settings apk
SuperMan-Rom V1.18.1:
- Updated SuperStock Kernel to V1.6
- Updated SuperKernel to V1.9.6
- Updated SuperSU to V2.79
- Added W8 bootloader and modems to aroma installation as well (auto update), that's why the zip got bigger again lol
- Updated viper4android magisk installation
- Added magisk viper4android apk file
- Added viper4arise sound mod (untested)
- Good lock SystemUI added in aroma
- Updated Xposed to 87.1 by topjohnwu (xposed will show 87.0 but magisk 87.1)
SuperMan-Rom V1.19:
- Fully rebased and remodded on BPLB base
- Probably the most annoying bug: fixed superman romcontrol not working from stock settings (due to package change)
- fixed not installing synapse and kernel adiutor
- added build.prop tweaks selectable in aroma
- Only display csc warning if you did not install default csc which comes with the rom
- Changed ARISE to deuterium which you guys reported working fine
- Updated samsung browser with fixed secret mode thanks to @mwilky
- Some other scripts cleanups
- Changed xposed 87.1 in xposed.prop as well (87.1 will now be display in xposed app )
- Updated phh superuser apk to latest beta 10 (material)
- Updated adblocker hostfile
- Added phone info app as user app
- Updated Samsung music app (and install as user app as well)
- Updated SuperSU to V2.79 SR1
- Another attempt to fix magisk viper4android.. (included a modded audioconfig file)
- Added TWRP recoveries to aroma. You can now choose if you want to update your recovery during aroma or not!
- Updated nougat emojis from latest samsung beta
- Updated BL's to BPLB (CP is still the same)
- Updated stockkernel to BPLB
- Updated Ramdisk of SuperKernel and SuperStock to BPLB (no source code yet)
- Added scrolling launcher background to romcontrol
- Updated Kernel adiutor
- Check rom info tab for little christmas easer egg by @myellow
SuperMan-Rom V1.19.1:
- Updated magisk to V10.2
- Updated Magisk apk to version from playstore
- Updated phh magisk to r2 version by topjohnwu
- Updated phh superuser apk to latest beta
- Updated SuperSU V2.79 SR2
- Readded normal logo in settings (christmas is over )
- Added an option in aroma to keep force encryption enabled
- Updated SuperStock Kernels to V1.6.5 with new base
- Updated SuperKernel to V1.9.7 with new base
- Updated sqlite binary
- Readded max build.prop tweak (removed a few critical, you tell me how they work)
- Added init.d script for sqlite and zipalign only (no more issues)
- Updated iOS emojis to latest update
- Some scripts clean up
Latest Nougat V2.X Changelogs:
SuperMan-Rom V2.0:
- Updated to DQAS (FULL REBASE TO ANDROID N 7.0)
- All kernels updated to DQAS (Stock, Super and SuperStock)
- Latest Busybox 1.26.2 included
- Latest SuperSU SR3 included
- Latest BL DQAS and CP DQA3 included
- Latest Magisk Manager APK included
- Latest TWRP 3.0.2-5 included
- Latest SuperUser Beta11 apk included
- Latest Sound Mod V19 included (updated for Nougat)
- Latest Camera Mod V7 included (updated for Nougat)
- Removed Xposed (not compatible with Nougat)
- Added many additional apps to bloat selection
- Added support to aroma to support 4GB zip files
- ARISE sound mod updated to V2.4
- DAP sound mod included
- Many Nougat CSC features included
- Floating message working
- AppLock working
- Private Mode working
- Aroma Theme reworked
- All SuperMan icons reworked
- Bootanimation reworked
- Splash screen reworked
- Multi User fully functional
- 3minit clock included (romcontrol option)
- Battery bar included
- Safe volume warning removed
- Weather on lockscreen enabled (can be a bit buggy, N just got released LOL)
- Hide or show lockscreen clock (inclusive seconds)
- Quick launch in recents
- Network speed indicator with tint
- Background colors for QS tiles colorable
- Statusbar icons colorable
- 3minit clock aroma choosable
- Virtual lock buttons
- Ambiente display
- Data usage in statusbar
- Dynamic statusbar
- Reboot to recovery, screenshot toggle, screencast toggle etc added
- Gear reboot on statusbar (romcontrol)
- Gear device info
- Latest adblocker included
- 0.25 animation speed in settings added
- Some more things I maybe forgot again
- For all credits please check my V2.0 release Post
SuperMan-Rom V2.1:
- Rebased and retweaked on latest DQB3 release
- Bootloader updated to DQB3 and modem to DQB1
- CSC updated to most recent BTU version as well
- Updated Magisk to V11.1 (removed phh's apk, root for Magisk is now INSIDE Magisk apk)
- Updated Magisk Manager to 4.1
- Fixed a busybox problem which didn't install it correctly
- Updated all kernels with latest ramdisk and source code (DQB3 isn't released yet)
- Updated adblockers hostfiles
- Removed ARISE sound mod, they have their own aroma installer and everything now, download it here
- Updated Camera Mod to V8
- Updated my own romcontrol a bit, changed colors and stuff hope you like it
- Removed knox entry from settings
- Added custom clock settings
- 3Minit clock can now be enabled and disabled inside RC (no need to choose in aroma)
- Clock can now be moved left, in the middle, right or disabled
- Clock can be colored
- Clock style can be choosen
- Date in statusbar can be choosen etc etc (just check the clock settings in RomControl)
- For lockscreen I've fixed the weather issue, however flat users may have some problems since the display is smaller than on edge phones. I got a S7 flat and I know what I'm talking about (let me know what you think)
- Fixed weather widget displaying time twice
- Added 18 different analog clocks in RomControl (to display on lockscreen)
- Added rambar back to romcontrol (it will be displayed at the top so you can't use it at the same time as recent quick launch)
- Volume skip added (skip tracks with volume control)
- Fixed ambient display not working
- Added auto call recording
- Updated pulldown statusbar colorizing
- Fixed alarm on lockscreen
- Added app shortcuts to romcontrol
- Added launcher gestures (all working fine except enabling flashlight)
- Added touchkey light duration in settings
- Added autostart manager in setting
- Added LED indicator in settings
- Updated all toggles in restart menu to match nougat design
- Updated shutdown animation (looks perfect now)
- Added many default superman wallpapers (will only appear after a clean wipe)
- Added the dark side of superman theme
- Someone requested me to add knox apps in aroma. So there you go, knox is in debloat menu but for sure I did not flash that onto my phone
- Added google assistant in aroma choice (debloat settings)
- Added brightness fix
- Updated all additional (none samsung & google) apps to most recent version
- Added CPU-Z and Tapatalk in debloat settings
- Removed amplify in debloat (sorry for confusion!)
- Disabled signature check for apps
- Probably some more things, but I can't remember sorry guys!
- Before someone ask, all credits can be found on V2.1 Release post!
SuperMan-Rom V2.2:
- Updated to latest DQB7 base with February security patch
- Full rebased and remodded since last base
- All mods have been updated
- Kernel are all updated to DQB7 ramdisk
- Kernels do now fake knox 0x0 on running system
- Added a much better selection of build.prop and init.d tweaks in aroma (you will see what I mean)
- Added new 3d boot animations by
- Moved themes into seperate aroma installer by Check this post here
- Added an aroma choice for ambient display (should fix lockscreen lag, please report back to me)
- Added another google assistant, this hopefully fixes the problems (you have to update the google app after installation in google playstore)
- Updated BL to DQB7 (modem is still the same)
- Added new toast animations in romcontrol
- Changed some default values in romcontrol
- reboot background menu is now colorable
- matrix in recents
- Move signal and wifi to the left in romcontrol
- added an option in romcontrol to change your carrier on lockscreen
- Camera mod updated to V8.1
- Possibly some other things I already forgot again sorry
SuperMan-Rom V2.3:
- Rebased on top of DQBO release
- Updated all kernel with latest ramdisk to version V2.2.1
- Added a note to aroma that busybox is needed for romcontrol/synapse
- Removed the cache init.d in aroma which caused bootloop
- Updated bootloader to DQBO
- Reworked SuperMan Settings app (will now show "free" in addition)
- Free means that this is the app with the rom and not the one on playstore, I will release a "pro" app (same functions) with translations and just to donate me
- Added Back to kill option
- Added Recent to kill option
- Fingerprint unlock without enabling display added (works only as long as fingerprint sensor doesn't go to deepsleep)
- New icons inside the SuperMan settings app
- Added blur effect on pulldown menu
- Added clock on lockscreen is now colorable to different colors (MM/H/SECS)
- Added notification colorable with notification text colorable
- Added search bar colorable and hidden switch
- Added fully working secure folder to the rom (will also be display in pulldown menu)
- Added Samsung Pay to Knox in debloat option (since it works together)
- Updated samsung pay and samsung pay framework with latest apps from sammobile, if that doesn NOT work well just uninstall the updates (those are not system files so you can easily uninstall them)
- Added custom icons for Signal/Alarm/Wifi in romcontrol
- Fixed left clock being displayed on lockscreen, is now hidden
- Added "clear all" and "notification settings" colorable
- Added colorable background the notification pulldown
- Basically everything is colorable now in pulldown
- Updated AdAway to most recent version
- Updated included adblocker files
- Updated included bloat apps (as instagram, snapchat, signal etc)
- Updated Magisk Manager to latest 4.2.6 (which fixed all fc's)
- Fixed OTA/Rom Control icon displaying a grey background
- Updated OTA app to match superman design
- Added new superman gifs in romcontrol (black/blue and red/yellow)
- Possibly more things to mod which I already forgot again (sorry )
SuperMan-Rom V2.4.1:
- Updated base to DQCG
- Reworked from scratch!
- March security update included
- Improved permissions in system/bin (rom should now work even better)
- Update stock kernel to DQC5
- Update SuperStock to V2.4.1 (with flicker free included)
- Update SuperKernel to V2.4.1 (with flicker free included)
- Updated Bootloader and Modem to DQCG / DQCG
- Added W8 BL/CP files to be flashed with the rom
- Added font apk (installs many fonts), it's choosable in debloat menu
- Moved romcontrol and OTA to debloat menu too (if you don't want them, don't install them)
- Removed framework selection, ambient is now called a different way
- Ambient is now also working without AOD (thanks to @mwilky)
- Updated Magisk to V11.6 (safetynet shall pass with usb debugging on now)
- Updated Magisk Manager to latest version
- Updated included bloatware apps
- Updated AirMessage and Applock app
- Updated TWRP to 3.1.0
- Added a switch in SuperMan settings to enable or disable RCS (cloud icon) (thanks to @MisterEvo)
- Added a switch in SuperMan setting to toggle 4G/LTE (thanks to @MisterEvo)
- Added a choice in aroma to include software keys
- If you choose knox, tima and knox will be enabled automatically, if not they will be disabled
- Aroma log will be saved at sdcard/SuperMan/aroma/
- Music and the Simcard notification of the FD variants should be colored too (let me know if it works!)
- Adjusted weather on lockscreen to match better, in next version there will be a big rework
- Fixed alarm icon being weird on theme ( @_alex74_)
- Added blur effect on pulldown colorable
- Added a switch to hide brightness slider on pulldown ( @mwilky)
- Added SystemUI tuner thanks to @lyapota (long press on settings icon in pulldown to activate it)
- Added option to color stock battery icon
- Added a switch to enable rounded notifications (aren't colorable for now)
- Added blur effect on recents
- Added many new items on pulldown menu
- Added back "Torch on Lockscreen", it's now in SuperMan settings under "misc systemui"
- Enabled lockscreen notification limit can be raised from 1-3
- Updated smali/baksmali for deodexing
- Updated all social media bloat apps (for example "signal" got secure video call feature)
SuperMan-Rom V2.5.0:
- Rebased on latest DQD3 release
- Remodded everything from scratch (this base had many changes compared to previous updates)
- April Security patch
- Updated Magisk to V12
- Updated Magisk Manager
- Updated phh superuser to r310
- Updated included adblocker host files
- Updated included BL/CP to DQD3/DQD2
- Fixed barometer displaying weird stuff on lockscreen
- Updated all bloat apps such as telegram/snapchat/titanium etc
- Updated Kernels to V2.5.1 version (new linux and new ramdisk)
- Updated included modded camera thanks to @djb77
- Added S8 camera to aroma, thanks to @_alex74_
- This update is mostly for stability and security!
SuperMan-Rom V2.6.0:
- Rebased on most recent DQG1 release
- Updated all included kernels to latest ramdisk/kernel source
- This update includes the July patch already!
- Updated Magisk to v13.3
- Updated SuperSU to 2.82 SR1
- Updated included bootloader to DQG1 and modem to DQF2 (still latest one)
- Updated included BTU csc
- Readded outdoor mode in settings app
- Removed OEM unlock switch with modded settings (so no one can accidentally turn it off)
- Added a switch in romcontrol for immersive mode
- Added support for calculator unit converter
- Added a switch to romcontrol to enable/disable transparent background
- Notification icons can now be colored too in rc
- SMusic app can also be fully colored thanks to @Thereassad
- Updated busybox installer
- Updated all included bloat apps (telegram, tapatalk etc.)
- Removed the "no csc" choice, since this only messes settings entries
- Removed S8 camera, we have a full port for this and the camera doesn't work perfectly on s7 base anyway
- Removed all needless build.prop and init.d tweaks, in my opinion this is the reason for heating and battery drain!!
- Fake system status to official (before was custom) @mwilky
- I simply didn't had the time to investigate into the SystemUI crashing while moving apps to SD with modded UI, I hope you can forgive me as I already promised it before...
- I hope that was all, maybe I forgot something
SuperMan-Rom V2.7.0:
- Based on latest DQIC release by Samsung (full rebase)
- Includes most recent August security patch (Samsung doesn't release the September patch to any device due to Blueborne fix)
- This base includes blueborne fix for bluetooth vulnerability
- Updated included modem and bootloader to DQIC for F/FD devices and BQH2 for W8 models
- Updated kernels to latest V2.9.0 versions build on DQIC source drop
- Updated Magisk to latest V14.2 beta
- Updated SuperSU to latest SR5 beta
- Updated sound mod with latest sound file, this should fix some issues with wifi calling
- Removed viper4android, due to the fact that it broke sound on s8 roms, you should flash ARISE or similar mods after the rom itself
- Updated busybox to latest 1.27.2
- Added some more apps to debloat selection, edge apps for example and some more voice files and for VR
- Removed OTA due to the fact that it wasn't working anymore, we will come up with a better solution in the future
- Added a switch in romcontrol to enable/disable high volume warning
- Added a new function to clear memory in pulldown menu
- Updated romcontrol application, changed name to SuperControl Free
- Updated included CSC
- Updated AppLock, ScreenRecorder and AirMessage
- Updated included bloat apps such as Telegram, Signal, Hike and Snapchat
- Included all fixes from last time, means Weather and alarm on lock screen works fine without any need to flash a file :good:
SuperMan-Rom V2.8.0:
- Based on latest DQK1 base released just a few days ago!
- Includes the latest November security patch
- This base includes Krack fix (if you want more informations about it, check it here: KRACK Attacks: Breaking WPA2)
- Updated included bootloader to DQK1 for F/FD models (modem is still the same)
- Updated kernels to latest V2.10.1 versions build on DQK1 source drop
- Updated Magisk to latest V14.4 beta
- Added Xposed V88.2 magisk (this xposed variant will only work if you select magisk at the same time!)
- Removed many 3rd party bloat apps, like this we save much space
- Added GBInstagram (modded instagram), GBWhatsapp (modded Whatsapp) and modded Youtube to allow background playing!
- Added listview animations to romcontrol
- Added colorable screenshot text to romcontrol
- Fixed long press on settings icon on pulldown not enabling SystemUI tuner + fc
- Fixed imsservice crash with the switchable RCS icon
- Updated the updater script binary
- Fixed notification panel custom image not sticking after a reboot
SuperMan-Rom V2.9.0:
- Rebased on latest DRAG base
- Includes the latest January security patch
- Updated included bootloader and modem to DRAG for F/FD models
- Updated kernels to latest V2.11.0 versions build on DRAG source drop
- Updated Magisk to latest V15.3 stable
- Updated Xposed to V89.2 magisk
- Install Xposed app as user app, before it got installed as system app
- Updated TWRP to latest 3.2.1-1 version
- Updated GBInstagram, GBWhatsApp and modded Youtube (to play background videos)
- Updated busybox
- Updated included csc
- Updated applock, airmessage, screenrecorder
- Updated zeroprobe camera mod
- Added quicktiles for VoLTE and Wificalling
Useful posts and links
App on PlayStore:
Find my own SuperMan app on PlayStore: SM Settings App
Odin:
Find all latest odin and samsung tools on this link: Samsung-Tools
In case you need help:
Try to take a look at my Q&A Thread where hopefully some general questions are already answered.
TWRP links:
TWRP S7 Thread
Official TWRP website for s7
Bootloader and Modems:
SM-G930F/FD/K/L/S/W8 BL and CP (all models in one folder!)
SM-G930F/FD BL and CP
SM-G930K BL and CP
SM-G930L BL and CP
SM-G930S BL and CP
SM-G930W8 BL and CP
Xposed Threads (MM ONLY):
Wanam Xposed V87
Systemless Magisk Xposed V86.6
Official Xposed V87 (DOES NOT WORK ON SAMSUNG DEVICES) visit this website only for changelogs and infos from rovo!
Material Xposed Installer
General Xposed Discussion
In case you want to use systemless xposed, but don't want to switch to magisk, install last magisk free Xposed V86.2. Download is here.
Magisk related Threads:
Magisk V13.3
Magisk Discussion
How-To create a Magisk module
Phh magiks superuser
Magisk module collection
Root related Threads:
Sound Mod V19
Camera Mod V8.1
How to encrypt on custom rom (MM ONLY)
Phh's superuser
Phh's hidesu
Phh's official apk
Phh's material APK
Stable SuperSU releases
Beta SuperSU releases
Chainfires suhide
Kernels Threads:
Kali Nethunter
TGP Kernel
SuperStock Kernel
Prometheus Kernel
SuperKernel
Voltaqe kernel
Roms made by me:
SuperMan-Rom which you are currently on its thread
HydraRom which is a full note 7 rom compatible with our s7.
SuperStock-Rom which is as close to stock as possible with some nice additions.
Samsung Links:
Sammobile Website
Latest samsung apks
Samsung Opensource Center
Live samsung updates
Fast firmware downloads
Good Lock:
Latest Good Lock APK can always be found on Apk Mirror.
Thread about CSC:
Download latest CSC from CSC Selection V2.4.0
All CSC's ever released
How to donate:
Donation via normal PayPal
Donate via PayPal.me
Batterylife with V1.16:
Geekbench 4 Results with V1.16:
Antutu Benchmark Results:
HERE WE GOOOOOOOOOOOO!!!!!!!!
Sent from my SM-G930F using Tapatalk
Questions and Answers
Basic Questions:
Q: How to get into Download Mode?
A: Power off your phone, than hold: home + volume down + power on button until you see the download mode.
Q: How to get into Recovery Mode?
A: Power off your phone, than hold: home + volume up + power on button until you see the recovery mode.
Q: My Phone is stuck at boot and doesn't start, what to do??
A: Update your bootloader and modem. Also make sure you have made a fresh install of the rom. Bootloader and Modem can be found in the OP. Another problem can be that you are didn't decrypt your phone. To fix this read below how to disable encryption.
Q: Do I need to update bootloader and modem after every update?
A: It's recommend to update your bootloader and modem everytime there is a new base yes. The developer will tell you if necessary on every rom changelog.
Q: I get verification failed at start up!?!? My phone is broken now?
A: Yes, you have to buy a new phone now. Just kidding You did not disable force encryption in TWRP (how to do so you will find below in how to decrypt your phone).
Q: I get verification FRP LOCK? WHYYYYYY???
A: Very simple answer, you did not enable OEM Unlock in developer options. Now you need to flash full rom with odin again and start from scratch. But don't forget to enable OEM Unlock this time!
Q: Which devices are supported at the moment?
A: Current supported devices are: SM-G930F/FD/K/L/S/W8. Snapdragons are NOT supported
Q: Is this rom working on Snapdragon 820 variants?
A: No, sadly not.
Q: I want to change something in my rom setup, how can I do that?
A: Simply reflash the same rom version without any wipe and than choose the correct things you want.
Q: Some features are not present in this rom, but they are on stock rom, so where are they?
A: In aroma installer you have the option to select bloat you want to install or not, you probably didn't select all package, this is why it's missing now.
Q: After a clean install my phone is overblated with many custom settings. What to do?
A: Open my romcontrol, grant it root permissions and then my default settings will be applied.
Q: Will you add X or Y feature?
A: You can kindly ask in the thread for that, if I like your suggestion I will think about adding it to the rom.
Q: You said you fixed SD card RW but Titanium Backup can't write to external SD card, why???
A: This is because of googles changes concerning SD card, to fix this open Titanium Backup, Menu, Preferences, Backup Folder Location, Storage provider and than hit DocumentProvider Storage and select your SD card. Problem solved
Q: I can't find X and Y mod. Please help
A: I've added many links and useful stuff to this post here. Hope that's what you have been looking for!
Q: I want to have my external storage like an internal as well. Google introduced it with android Marshmallow, but I can't see this option?
A: Just follow this Guide here and you can setup your SD card as normal storage
Q: I got a new strange icon appearing after nougat update. What's that?
A: This is a new advanced calling feature introduced in android nougat. Should make your call quality better or something like this. To hide it please visit following forum: Get rid of RCS icon
Q: I installed Viper or other sound mods, but they won't work, why?
A: You most likely missed to freeze sound alive, if you did this and it's still not working you it's due to the kernel. Stock kernel doesn't support these mods since we need a permissive kernel!
Questions concerning rom updates:
Q: Do I have to do a full wipe for the new version?
A: It is always the best option to make a clean install, otherwise please don't come and report bugs!
Q: But I don't want to make a full wipe when only small stuff changed!
A: For updates using the same bases you can install the rom with a dirty flash. BUT with a new base a clean install is highly recommend!
Q: What steps should I do to update to a new version with a full wipe but keep all data?
A: There are some different ways. One way is to make a backup with Titanium Backup, you can backup all Apps and Preferences there. Make sure to store this backup on external SD card (if you have one). Second way would be to save your data onto a google account or samsung cloud and restore it after a clean install.
Q: I miss an apk after rom update, how can I get it back?
A: Simply reflash rom and select "dirty flash" in aroma + select the app this time in aroma.
Q: My battery life is so bad and performance is very poor after an update!?!?
A: This comes actually not form the rom itself, dirty flash can cause problems even if only some small things have been changed. So simply install it clean again and it will solve your problem.
Q: Performance and battery is very poor even after clean install. What should I do now?
A: I assume you installed Xposed than, some modules can cause batterydrain and performance problems. So try to make a clean install of the rom WITHOUT xposed installed.
Questions about log and logcats:
Q: I got FC's and other Problems with the rom, what to do?
A: Take a logcat for me, developers use to say: without a log, it never happened . A logcat can be grabed with a PC and ADB installed, simply type: adb logcat > log.txt while your phone is connected and the error is happening. Same can be done if you have a terminal installed on your phone. Simply type adb logcat > log.txt and you will have the same output as on the PC.
Q: What kind of logs can I provide to help you?
A: Logcat: This one is for general infos about FC's
DMESG: this is for kernel related things
Last_Kmsg: this can be used after a random reboot
Q: How to get logs?
A: 1. Connect your phone to your pc
2. Make sure you got usb debugging enabled
3. Install Minimal ADB tool
4. After install open it and type: adb logcat > logcat.txt, adb shell dmesg > dmesg.log, adb shell cat proc/last_kmsg kmsg.log
5. Send me the file you got
You can also send me a log created by your phones terminal with the exact same commands!
Questions about RomControl:
Q: None of my romcontrol changes do anything, why are you such a bad dev!?!?
A: The problem is not on my end, you installed stock systemUI (which is STOCK and does not support one single mod). Use another one in aroma instead. The same thing can happen with good lock!
Q: Romcontrol gives FC's to me. HELP!
A: Very simple answer here: wipe data and cache from superman control application. Also make sure storage permissions are given to the romcontrol.
Q: Romcontrol still FC after cleaning data and cache!
A: Make sure you allow storage permission in main settings.
Q: I try to backup my current RomControl setup, but it won't work?
A: It works. Just make sure to enable storage permission in main samsung applicatoin settings. You will find it in internal sdcard under RomControl folder.
Q: I can't restore SuperMan control settings after a clean base update, why?
A: Backup for SuperMan control only works as long as you use the same version of the app, I mostly change very much things in new releases that's why it won't work there.
Q: SystemUI reboot doesn't work in SuperMan settings app, why?
A: Since Nougat update, you need to install busybox in order to get this button working. Without busybox the button will just do nothing.
Q: I enabled weather on lockscreen but I can't see anything...
A: You probably didn't setup or even installed samsungs weather widget. Without it weather on lockscreen won't work too. So reflash the rom with the widget installed this time and set it up.
How to go back to stock:
Q: I like to go back to stock rom, how is this possible?
A: I can provide you here all steps which are needed to go back to a full stock rom.
0. Make a backup and than wipe all partitions in TWRP
1. Go to Sammobile and choose your country
2. Download the file and the attached Odin on sammobile
3. After downloading, put your phone into download mode
4. Make sure drivers are installed and your pc can detect your phone in odin
5. If the box in odin turns blue, add the AP file to AP tab, BL file to BL tab, CP file to CP tab and CSC_HOME to CSC tab
6. Hit start and wait until it is finished.
7. Reboot and you have a stock rom again
Questions about Encryption:
Q: On TWRP there is an error about /data mount, what to do?
A: Your device is encrypted, follow the steps below to get rid of your encryption.
Q: Help, I never had a code and now after installing the rom my phone asks for a password??
A: Your device is still encrypted, on step 0 of my rom instructions it tells you to be sure you're not. So, what do you need to to in case you are still encrypted.
A: HOW TO DISABLE ENCRYPTION:
1. Boot into TWRP
2. Select Wipe
3. Select format data
4. Then you manually need to type "yes" with the keyboard
5. Confirm the wipe (this will remove the encryption)
6. Reboot your recovery
Q: Is there a way to get rid of encryption which is simpler?
A: Not really, you could also wipe data with stock recovery but this is quite a big hassle so above method works better.
Q: And if I want to use this rom with encryption?
A: Normally we can use the stock kernel to encrypt our device, but since the Android 7.0 Nougat update samsung makes a check kernel sides to block deodexed roms from booting. This means that even the stock kernel is build by me to disable knox and tima. So encryption won't work there and you have to encrypt your device after you set up your phone. After that go to settings, security, encrypt device. It may need some additional steps to work...
Questions about CSC/Signal:
Q: Where has the CSC selection gone?
A: To include all csc files, the rom get way to big, so it got it's own thread now, take a look here: CSC installer
Q: I have a weak cellular signal, what can I do against it?
A: Two things: first, install your providers CSC using CSC installer and flash in TWRP or flashing stock CSC with Odin. Second Thing: You can install the modem from your provider, also find your modem on Sammobile and install it with Odin in CP tab.
Q: I don't have all sHealth features, how come?
A: Not all CSCs include this feature. I recommend to use AUT or DBT as it has the best compatibility!
Q: Can I flash MM CSC on N and vis a verse?
A: No, this is clearly not recommend! You can and will face call fc's!
Questions about Xposed:
Q: Does Xposed work yet on Android N 7.0?
A: No it does not! You will end up in a bootloop when you flash it on android N
Q: I selected xposed but now I don't see an app for it?
A: Maybe there went something wrong with installing the app to /data/app from my installer script. But xposed is actually installed only the app is missing, so head over to the download page of xposed app: Material Xposed Thread
Q: I selected xposed but the app shows not active or something else with xposed is not working.
A: This can have 2 reasons:
1. You have installed latest xposed version without installing magisk, magisk is required for most recent xposed version!
2. You used 86.2 xposed (which does not need magisk) but you did not install supersu. Since 86.2 does not use magisk to be systemless it uses supersu instead!
Questions about Magisk:
Q: How can I pass safetynet?
A: 1. Make sure to fully uninstall SuperSU by chainfire
2. Flash most recent 2.4.3 SuperStock Kernel
3. Flash Magisk V12
4. install latest Magisk Manager from playstore
5. Open Magiks Manager, go to settings
6. Enable MagiskHide, systemless hosts and systemless busybox
7. Reboot the phone and check safetynet!
Q: I got out of date binary issue?
A: Since Magisk V11.1 there is no need for phh root anymore. Everything is handled inside the MagiskManager apk!
Q: Where can I configure the root settings in Magisk?
A: Since Magisk V11.1 Magisk uses MagiskSU, you can find it in latest Magisk Manager V4.1
Questions about Snapchat:
Q: Even when I did not use xposed during my setup in rom I can't login to snapchat anymore!
A: Snapchat got updated and now detects even root access on your phone!
Q: What to do to login to snapchat then?
A: Clean install the rom without root and xposed and login to your snapchat, save the app with titanium backup, flash back xposed and root. For the next update of the rom just restore snapchat backup in TB.
Q: Any other possibility?
A: You could enable MagiskHide and check Snapchat inside it so root will be hidden from Snapchat. You will be able to perfectly login without any issues.
Q: I want to discuss this problem a bit deeper. Should I do so?
A: Do that, but this has nothing to do with this rom, so please go ahead and post your experience here on this Snapchat Thread.
Questions about Kernels:
Q: I want to switch kernel, how?
A: Since we have systemless xposed and systemless supersu, we have patches in ramdisk of boot.img. This means you have to reflash Magisk and supersu (or any other zip that changes some stuff in ramdisk partition) after every change of kernel!
Q: Synapse shows no UCI support!
A: Most comon issue is that no busybox is installed. Download the one from here: Latest busybox and flash it in recovery.
Q: I got random reboots, heeelp!
A: This is most likely from a custom kernel, if you face random reboots please check if you have the latest kernel installed or switch back to the stock kernel included in the rom.
Q: My screen is kind of yellow/orange and the touchscreen doesn't work at all!
A: You have chosen the wrong kernel in aroma selection. Reflash the rom without any wipe selecting the right kernel version.
Questions about Root:
Q: I lost root after installing this rom. What to do?
A: All mods (like supersu, phh's root, xposed and magisk) are stored in ramdisk of kernel boot.img. So if you flash this rom, and after this another kernel, simply reflash your preferred root method and it will work again!
Q: I selected phh root but my phone tells me I am not rooted!!
A: There are two possibilities:
1. You have mixed supersu/phh with magisk.
2. You did not install phhs root app from playstore.
Q: I get a warning about binary out of date. Help!
A: That happens on latest Magisk V11.1. Reason: Root has fully moved into Magisk Manager, no additional app required. Uninstall phh or supersu apps and only use magisk!
Q: I want to use su hide on my phone, how to do so?
A: Both below variants are outdated, I recommend to use Magisk with its build in MagiskHide. Check the thread: Magisk Thread
Link to phh's hidesu: Phh's thread
Link to chainfires suhide: Chainfires thread
Tkkg1994 said:
Exactly Rom is now online and ready for using
Click to expand...
Click to collapse
God bless you man!!!!! Let's get this show on the road!!
Sent from my SM-G930F using Tapatalk
Hey mate is this rom faster then stock and have better battery and is it stable
broyza said:
Hey mate is this rom faster then stock and have better battery and is it stable
Click to expand...
Click to collapse
It's definitely stable as said in the title of the thread.
Sent from my SM-G930F using Tapatalk
barondebxl said:
God bless you man!!!!! Let's get this show on the road!!
Sent from my SM-G930F using Tapatalk
Click to expand...
Click to collapse
Finally a working S7 rom here on xda
broyza said:
Hey mate is this rom faster then stock and have better battery and is it stable
Click to expand...
Click to collapse
I think so, but I think that anyone can decide by himself. I would say: Try it mate
Stable for sure
Ok great will definitely try it now so do i have to flash bootloader and modem first them rom?
broyza said:
Ok great will definitely try it now so do i have to flash bootloader and modem first them rom?
Click to expand...
Click to collapse
I think the guide on the OP is very clear, or to which step do you have a question?
So i download that bootloader file first and flash through odlin then rom through twrp ? And will it work fine with my network?
---------- Post added at 02:47 AM ---------- Previous post was at 02:35 AM ----------
And the only problem i have is i dont have a sd card installed to move rom and stuff there ??
broyza said:
So i download that bootloader file first and flash through odlin then rom through twrp ? And will it work fine with my network?
---------- Post added at 02:47 AM ---------- Previous post was at 02:35 AM ----------
And the only problem i have is i dont have a sd card installed to move rom and stuff there ??
Click to expand...
Click to collapse
Than you put it on your phone and wipe everything except internal storage
Ok great thanks il try this now
Installed this rom and is working great no problems so far ? when you gonna make some more modern and make this even better ?
Thanks a lot for this rom. If I may suggest to add links to tweaks that are tested and working with the rom. Tweaks like dual speaker, viper, xposed and so on.
Skickat från min SM-G930F via Tapatalk
THX it's seams the rom's start to appear !
Thanks Sir
Great bloatet Rom, but Gear VR doesn't work correctly - representation does not fit.
Som few edge features would be great.
Can someone please help me?
After i installed twrp, the recovery cant mount data,
Please help
MrJiM said:
Thanks a lot for this rom. If I may suggest to add links to tweaks that are tested and working with the rom. Tweaks like dual speaker, viper, xposed and so on.
Skickat från min SM-G930F via Tapatalk
Click to expand...
Click to collapse
I will add some of those mods in my rom by default
AlphaAnimal said:
Great bloatet Rom, but Gear VR doesn't work correctly - representation does not fit.
Som few edge features would be great.
Click to expand...
Click to collapse
I will test this on my own gear vr, thanks.
weedeater84 said:
Can someone please help me?
After i installed twrp, the recovery cant mount data,
Please help
Click to expand...
Click to collapse
You have an encrypted device. You have to decrypt it first
Sent with my Nova powered SM-G901F
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 G930FXXU2xxxx_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 G930FAXX (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.G930FXXU8EUE1:
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. "G930Fxxx_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. "G930Fxxx_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. "G930Fxxx_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_G930Fxxx_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. "G930Fxxx_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
>> G930FXXU8EUE1_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 G930FXXU8EUE1 DevBase):
- Fixed unzip issue which caused unexpected installation termination - applies to TWRP 3.5.0_9-1 and newer
v7.3 (starting from G930FXXU7ETBD 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 G930F):
- Fixed bootloop issue in case of Android Q and encrypted devices (applies to dirty update)
v7.1 (starting from G930FXXS7ETA8 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 G930F):
- Initial support for Android Q / system-as-root devices
v6.0 (starting from G930FXXU3ERL3 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 G930FXXU2ERG2 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 G930FXXU2EREM 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 G930FXXU2ERD5 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 G930FXXS2DRDC 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 G930FXXS2DRCC 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 G930FXXS2DRC3 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 G930F):
- Improved algorithm of search & change "ro.security.vaultkeeper.feature" property to 0 (/system & /vendor)
v5.2 (not released for G930F):
- 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 G930FXXU2DRB7 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 G930FXXU2DRAG 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 G930FXXU1DQLF 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 G930FXXU1DQLA 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 G930FXXS1DQF6 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 G930FXXU1DQD7 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 G930FXXU1DQD2 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.
Auto call recording and applock
Hi,
Does this rom have auto call recording and app lock?
if not, can you please give a flashable zip in mod section?
I like your pure stock based rom.
I will try today.
Thanks
very interesting this is the most recent rom, i'm downloading it.
installation was succesful data is keeped.
rom seems goodkeep it:good:
sudha_manamadurai said:
Hi,
Does this rom have auto call recording and app lock?
if not, can you please give a flashable zip in mod section?
I like your pure stock based rom.
I will try today.
Thanks
Click to expand...
Click to collapse
This ROM contains "SYSTEMLESS DevBase" on-board. See screenshots here:
http://forum.xda-developers.com/s7-edge/development/samsung-systemless-devbase-encryption-t3517178
As you can see - built-in Auto Call Recording will be also activated
It does not contain "AppLock" [...] EDIT: You can add it manually and it works well. More info here:
https://forum.xda-developers.com/showpost.php?p=72094528&postcount=86
Was my daily driver on S5, glad to see you here in S7 forum.
Wil definitely try the ROM. Good luck!
hi @_alexndr.
I am quite surprised at the performance of the stock kernel.
I've attached benchmark results, with default cpu n gpu settings
is it possible to toggle selinux (permissive) with included kernel?
Xposed works on Android 7.0?
MyCephei said:
Xposed works on Android 7.0?
Click to expand...
Click to collapse
Not yet.
Ok,thx. Because he wrote;
v4.1 (starting from G930FXXU1DQD2 DevBase):
- 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
battery very good..
4g always on
no battery-saving settings.
MyCephei said:
Ok,thx. Because he wrote;
v4.1 (starting from G930FXXU1DQD2 DevBase):
- 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
Click to expand...
Click to collapse
Yes on other phones, like the s5, v4. 1 is not nougat.
JJGLive said:
Yes on other phones, like the s5, v4. 1 is not nougat.
Click to expand...
Click to collapse
Now i am a little bit confused
>> G930FXXU1DQD2_DevBase_v4.1.zip << (Android 7.0, updated Apr-19-2017)
Android 7.0 is not Nougat? Sure?
MyCephei said:
Now i am a little bit confused
>> G930FXXU1DQD2_DevBase_v4.1.zip << (Android 7.0, updated Apr-19-2017)
Android 7.0 is not Nougat? Sure?
Click to expand...
Click to collapse
As far is I know there is no xposed for nougat yet.
Maybe @_alexndr can explain it better than I can.
MyCephei said:
Now i am a little bit confused
>> G930FXXU1DQD2_DevBase_v4.1.zip << (Android 7.0, updated Apr-19-2017)
Android 7.0 is not Nougat? Sure?
Click to expand...
Click to collapse
no xposed for nougat.
dev just copy/paste same op for diff devices...
No need to flash modem and bootloader throw Odin? Just flash it on twrp?
@_alexndr
I've heard about your rom being the best there is at this moment. Congratulations.
Unfortunately i am on G935F and i and others can't enjoy it.
Will there be a version for G935x users?
Please consider it
artaniss11k said:
@_alexndr
I've heard about your rom being the best there is at this moment. Congratulations.
Unfortunately i am on G935F and i and others can't enjoy it.
Will there be a version for G935x users?
Please consider it
Click to expand...
Click to collapse
go to edge forum.
https://forum.xda-developers.com/s7...d1-devbase-v4-1-multi-csc-safe-t3591647/page7
{
"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"
}
Code:
/*
* Your warranty is now void.
*
* We're not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Red Wolf Recovery is custom recovery based on TWRP source code however some things are working here slightly different then you might expected. The main objective of this project is to provide stable recovery with features which you have never seen before in a recovery and which have not been accepted for adding to the official source code of TWRP. This recovery is also first recovery on the world with password protection.
Based on TWRP version: 3.2.1
For devices: Chiron
Authors build: yshalsager
Developers: @ATG Droid & @Dadi11
Thanks: z31s1g (for the base of his theme), Ray Li (For his useful advice in the beginnings), osm0sis (for his image scripts), etc.
Features:
Code:
[B]Translated to EN & CZ [/B]
- Password protection
- Flashlight
- MIUI Incremental OTA Support
- Built-in latest Magisk, SuperSU & AromaFM
- Support two screenshot GUI actions - Power+VolDown to save screenshot in to the internal storage &
Power+VolUp to save screenshot in to the external storage (Will be automatically saved in to the internal in case
that external storage doesn't exist).
- Support automatic reboot after the restore process
- Recovery can automatically modify some props in the ROM directly during the installation
- Some built-in scripts from community
- Tap to wake support
- Advanced deactivation of the stock recovery
- Automatic deactivation of the dm-verity & forced encryption directly during the installation of the ROM
- Recovery can notify you about the completed backup/restore/installation using the notification diode & vibration.
- Support "set on boot" settings.
[B]* Changes for security reasons *[/B]
- ADB isn't starting automatically at the start of the recovery. You have to activate it in recovery
- MTP isn't starting until user enter correct password
- Deactivated TWRP theme engine
[/URL]
Some differences to the official version:
Code:
[COLOR="red"]- get out of here if you are pirating apps. this recovery is not for you[/COLOR]
- always up-to-date with the latest TWRP changes
- compiled on omnirom-7.1 source
- kernel compiled inline with the recovery
- There isn't bug with reboot from recovery to recovery
- more languages
- other improvements from Features and Changelog lists
Changelog:
Code:
RedWolf-V3.2_026
- This is just a quick bug fix release for MIUI users. So is highly recommend to update to this build if you are using MIUI.
RedWolf-V3.2_025
- Fixed crash of the recovery while running OTA_RES.. (So MIUI OTA is now working again)
- General bug fixes and improvements
- Fixed bug with MIUI Updater app showing error that installation failed after installation of full ROM
- Deactivation process is now called only when it's really needed
- Updated kernel
RedWolf-V3.2_024
- Fixed GUI color glitch while starting Aroma Installer update-binary
- Optimized pigz runtime process
- Updated recovery base to the AOSP 8.1.0 & TWRP 3.2.1
- Highly improved signature verification for Incremental packages so now we can be really sure if the package is compatible with the ROM.
- Introduced a file based backup/restore engine. Expect it to be improved with the next builds...
- Improved security related to the password protection
- Fixed loading of the AromaFM config file
- System survival process for Incremental packages is now set by default
- Code optimizations
- Removed the dumwolf process
- Added signature check for incremental OTA survival so we won't be unnecessarily creating a new one if it's signed under the same access key
- Magisk updated to the version 15.1
- Added Indonesian language
- Fixed issues with Chinese characters...
- Governor which is changed by the action in the recovery GUI is now automatically set for all cores instead of only four.
RedWolf-V3.2_023
- Updated recovery base to the TWRP version 3.2.0
- Fixed issue with recovery sometimes showing "NO-OS" page even when OS is installed
- Merged: Fstab V2, minui updates, Keymaster 3.0 support, ADB updates, fixes related to the compiling errors...
- Added patch against the pirating applications
RedWolf-V3.1_022
- Small improvements in the installation process
- Recovery will now automatically warn the user in case that user selected to install the zip which contain a bootloader
- You can now wipe installed substratum overlays directly from the "advanced wipe" section
RedWolf-V3.1_021
- Automatically return install error if there is any issue with Incremental OTA Survival
- Added option to also backup system partition for Incremental OTA Survival (It's not always needed, but just in case it's better to backup it.)
- Added support for the compatibility verification of the Incremental Package
- Rebuilded & improved installation process
- Fixed starting process not being disabled correctly in case that we are running ORS
- Translation update
- Added support for devices with 2GB RAM or less... (Check installation process of this build for more info)
- Added checkbox for activation/deactivation of the boot check (Disable only if you really need to).
- Fixed booting problems on some custom ROMs which don't have gzip compressed ramdisk
- Removed bookmark feature
- Added ability to unzip files using the stock filemanager.
- Added search selection for the stock filemanager.
- Fixed 'No OS' on system image restore after wipe
- Merged some latest commits from TWRP gerrit
RedWolf-V3.1_020
- Fixed flashing of the images in the previous 018 build
- Added back support for unpacking of the LZ4 compressed ramdisk
- Fixed bookmark feature
RedWolf-V3.1_019
- Disable TWRP installation directly during the first boot
- Default time zone was set to CEST
- Use military time as default time.
- Support of the custom themes was completely removed from the installation process
- Few fixes & improvements in the strings.
- Default value of the RedWolf specific vibrations was slightly increased
- Improved saving/loading of the AromaFM config file.
- User can now select if recovery should disable stock recovery when system is mounted as read-only.
- Default color of the recovery was set to red.
- Fixed automatic reboot if the installation process was unsuccessful
- Center time in the statusbar as default
- Show CPU temp in statusbar as default
- Added "Red Wolf No-OS search engine". Enable this if you are sometimes getting No-OS installed error even when OS is installed.
- Added back support for extra languages
- Added support for Talian language
- Updated Chinese (simplified) translation of the AromaFM by LiuNian and Pzqqt
- Fixed displaying of the extra languages
- Improved mounting of the partitions during the applying of set on boot values
- Fixes with "stuck at unmounting"
- Highly improved speed of the recovery while setting up a new password, changing accent color or setting a new splash screen
- Magisk updated to the V14.3
- Recovery now won't allow the user to enter special characters while entering the password (Causing issues...)
- Few improvements with the Android Oreo installation
- Updated kernel
- Added ability to select if recovery should automatically disable forced encryption in the ROM
- Recovery will now automatically rename scripts in the system if the "Aggresive stock recovery deactivation" is enabled
- Added ability to select if recovery should automatically enable/disable USB Debugging in the ROM
- Removed some useless files to save the space
- Added support for saving the set on boot values also during the automatic reboot
- Redesigned flashlight icon
- Recovery now won't allow the user to enter the space in to the backup name
- Improved support of the last status checking of the MIUI ROM
- Recovery now won't show any button after the cancelled reboot action untill the sleep action won't be running anymore
- You can now select if recovery should also automaticaly reboot after the successfuly finished restore process
- Recovery will now hide the automatic backup feature if the system partition is mounted as read-only
- Updated recovery base to the AOSP 8.0.0
- Updated image drivers
- Added ability to select if recovery should automatically enable/disable "ro.adb.secure" property in the ROM
- Recovery will now automatically disable starting of the flash_recovery service if the "Aggresive stock recovery deactivation" is enabled (this process is also compatible with the backup of the init.rc by Magisk or SuperSU).
- Added new section called "Special Actions" in to the advanced menu
- Updated & optimized flashlight drivers
- Added ability to select if recovery should automatically enable/disable "ro.secure" property in the ROM
- Added ability to select if recovery should automatically enable/disable "ro.allow.mock.location" property in the ROM
- Highly improved support of the Incremental Package installation, detection etc.
- Updated Chinese (simplified) translation of the recovery by LiuNian and Pzqqt
- Added support for the complete deactivation of the secure boot in the MIUI based ROMs
- ADB is now automatically starting as root
- Added support for the RedWolf update package
- Default theme of the AromaFM was changed to holo black with the sense icons and automount turned on
- SuperSU Updated to the 2.82 SR5
- Updated ramdisk cleaner & added support for more kernels (thanks to @MOVZX's kernel installation scripts...)
- Small fixes with the /WOLF folder in the PartitionManager
- Highly improved speed of the reboot
- 'Deactivation process' is now automatically called during the installation instead of the reboot
- Imroved deactivation of the leds after the installation / backup / restore process.
- Fixed bug with recovery showing on the governor page that the active governor is "Interactive" even when user selected performance/powersave mode.
- Removed some GUI messages while we are installing built-in zips.
- And many other things which i don't remember anymore...
RedWolf-V3.1_018
- Fixed bugs with MIUI OTA Support to make sure that it will work even with newest beta builds of the MIUI
- Updated Polish translation by Daviteusz
- Fixed bugs in the Polish strings & edited the scale of the Russian strings
- Recovery will be now more aggressive if the process of the stock recovery doesn't want to be disconnected (Sometimes happen on some MIUI ROMs).
- Added detection of the installed ROM
RedWolf-V3.1_017
- Magisk updated to the V13.6
- SuperSU updated to the 2.82 SR3
- Added ability to automatically flash SuperSU config before the SuperSU - https://forum.xda-developers.com/apps/supersu/2017-08-13-supersu-config-t3655754
- Deactivated hw keys
- Added some missing back buttons
- Attempted to fix encryption
- Attempted to fix MIUI OTA installation - needs testing
- Removed extra languages (were not displayed properly)
- Small update which fixed deactivation of the dm-verity & forced encryption. Now you really don't have to flash the lazyflasher everytime when you are installing the MIUI ROM.
RedWolf-V3.1_016
- Fixed feature "Backup wifi, bluetooth & hosts" not to work if the user wiped the data partition using the "factory reset".
- TWRP source code was updated to the Aug 15, 2017
- Fixed recovery remembering the wipe list after setting a new gui page.
- Improvements with the mounting of the partitions during the boot
- Fixed led drivers on mido
- Fixed ability to set custom backup folder name & ADB ID
RedWolf-V3.1_015
- Updated with the latest TWRP changes
- Added flashlight switch on mido
RedWolf-V3.1_014
- Fixed recovery not deactivating the dm-verity, forced encryption, & stock recovery if the OS was detected as not installed. This issue was often happening on some MIUI ROMs.
- Improvements with the OTA update system of the MIUI.
- Fixed wrong reboot for some users.
- Added support for automatic deactivation of the dm-verity, forced encryption & stock recovery after finishing the OpenRecoveryScript process.
- Fixed recovery not deactivating the dm-verity & forced encryption during the automatic reboot after the finished installation.
- Better explain the current situation if the OS was detected as not installed.
- osm0sis's scripts "unpackbootimg" & "mkbootimg" can now be easily called from the script or terminal
- Improved the speed of the reboot
- Updated the community script "Fingerprint scanner fix" by Magua. It's now working again!
- Added NTFS & exFAT support
- Added more languages and updated Polish RedWolf translation by @Daviteusz
- Added FGO patch - https://goo.gl/GBkhMN
RedWolf-V3.1_013
- Slightly improved deactivation of the stock recovery during reboot after the zip installation
- Added ability to flash boot logo in the recovery
- Fixed firmware restoring issues
RedWolf-V3.1_012
- added F2FS support for mido
- added Night Mode (kcal) support for mido
RedWolf-V3.1_011
- Updated Polish translation by @Daviteusz
- Added few missing strings from the latest TWRP source
[Red Wolf] Install TWRP and root your device without breaking incremental OTA's!
Known Bugs:
- Flashlight is not working.
Downloads:
Latest build for Xiaomi Mi Mix 2 (chiron)
RedWolf-Unofficial-chiron.img
Warning:
Please remember that recovery with password protection isn't still a full protection for your phone. Red Wolf can only prevent unauthorized access to your device from recovery. But your device can be still reinstalled using fastboot or Miflash.
XDA:DevDB Information
[ABANDONED][CHIRON] Red Wolf Recovery Project, Tool/Utility for the Xiaomi Mi Mix 2
Contributors
yshalsager, ATG Droid, Dadi11
Source Code: https://github.com/RedWolfRecovery
Version Information
Status: Testing
Created 2018-02-21
Last Updated 2018-02-24
Sources
Recovery: https://github.com/RedWolfRecovery/rw_recovery
Device tree: https://github.com/RedWolfRecovery-Xiaomi-Devices/android_device_xiaomi_chiron
Screenshots: Here
Well done ! It's welcome !
Very cool, this recovery was awesome on my Redmi Note 4X. Being able to update official MIUI incremental updates is a great feature.
Sent from my Mi MIX 2 using Tapatalk
mix2 cant use it (dev 8.2.8
Not working for me tried installing it in Oreo twrp as img and also tried with adb from PC. On miui Oreo beta 8.2.22. just stays on the miui loading screen.
with global version nougat doesnt work for me....
yshalsager said:
Code:
/*
* Your warranty is now void.
*
* We're not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Red Wolf Recovery is custom recovery based on TWRP source code however some things are working here slightly different then you might expected. The main objective of this project is to provide stable recovery with features which you have never seen before in a recovery and which have not been accepted for adding to the official source code of TWRP. This recovery is also first recovery on the world with password protection.
Based on TWRP version: 3.2.1
For devices: Chiron
Authors build: yshalsager
Developers: @ATG Droid & @Dadi11
Thanks: z31s1g (for the base of his theme), Ray Li (For his useful advice in the beginnings), osm0sis (for his image scripts), etc.
Features:
Code:
[B]Translated to EN & CZ [/B]
- Password protection
- Flashlight
- MIUI Incremental OTA Support
- Built-in latest Magisk, SuperSU & AromaFM
- Support two screenshot GUI actions - Power+VolDown to save screenshot in to the internal storage &
Power+VolUp to save screenshot in to the external storage (Will be automatically saved in to the internal in case
that external storage doesn't exist).
- Support automatic reboot after the restore process
- Recovery can automatically modify some props in the ROM directly during the installation
- Some built-in scripts from community
- Tap to wake support
- Advanced deactivation of the stock recovery
- Automatic deactivation of the dm-verity & forced encryption directly during the installation of the ROM
- Recovery can notify you about the completed backup/restore/installation using the notification diode & vibration.
- Support "set on boot" settings.
[B]* Changes for security reasons *[/B]
- ADB isn't starting automatically at the start of the recovery. You have to activate it in recovery
- MTP isn't starting until user enter correct password
- Deactivated TWRP theme engine
[/URL]
Some differences to the official version:
Code:
[COLOR="red"]- get out of here if you are pirating apps. this recovery is not for you[/COLOR]
- always up-to-date with the latest TWRP changes
- compiled on omnirom-7.1 source
- kernel compiled inline with the recovery
- There isn't bug with reboot from recovery to recovery
- more languages
- other improvements from Features and Changelog lists
Changelog:
Code:
RedWolf-V3.2_026
- This is just a quick bug fix release for MIUI users. So is highly recommend to update to this build if you are using MIUI.
RedWolf-V3.2_025
- Fixed crash of the recovery while running OTA_RES.. (So MIUI OTA is now working again)
- General bug fixes and improvements
- Fixed bug with MIUI Updater app showing error that installation failed after installation of full ROM
- Deactivation process is now called only when it's really needed
- Updated kernel
RedWolf-V3.2_024
- Fixed GUI color glitch while starting Aroma Installer update-binary
- Optimized pigz runtime process
- Updated recovery base to the AOSP 8.1.0 & TWRP 3.2.1
- Highly improved signature verification for Incremental packages so now we can be really sure if the package is compatible with the ROM.
- Introduced a file based backup/restore engine. Expect it to be improved with the next builds...
- Improved security related to the password protection
- Fixed loading of the AromaFM config file
- System survival process for Incremental packages is now set by default
- Code optimizations
- Removed the dumwolf process
- Added signature check for incremental OTA survival so we won't be unnecessarily creating a new one if it's signed under the same access key
- Magisk updated to the version 15.1
- Added Indonesian language
- Fixed issues with Chinese characters...
- Governor which is changed by the action in the recovery GUI is now automatically set for all cores instead of only four.
RedWolf-V3.2_023
- Updated recovery base to the TWRP version 3.2.0
- Fixed issue with recovery sometimes showing "NO-OS" page even when OS is installed
- Merged: Fstab V2, minui updates, Keymaster 3.0 support, ADB updates, fixes related to the compiling errors...
- Added patch against the pirating applications
RedWolf-V3.1_022
- Small improvements in the installation process
- Recovery will now automatically warn the user in case that user selected to install the zip which contain a bootloader
- You can now wipe installed substratum overlays directly from the "advanced wipe" section
RedWolf-V3.1_021
- Automatically return install error if there is any issue with Incremental OTA Survival
- Added option to also backup system partition for Incremental OTA Survival (It's not always needed, but just in case it's better to backup it.)
- Added support for the compatibility verification of the Incremental Package
- Rebuilded & improved installation process
- Fixed starting process not being disabled correctly in case that we are running ORS
- Translation update
- Added support for devices with 2GB RAM or less... (Check installation process of this build for more info)
- Added checkbox for activation/deactivation of the boot check (Disable only if you really need to).
- Fixed booting problems on some custom ROMs which don't have gzip compressed ramdisk
- Removed bookmark feature
- Added ability to unzip files using the stock filemanager.
- Added search selection for the stock filemanager.
- Fixed 'No OS' on system image restore after wipe
- Merged some latest commits from TWRP gerrit
RedWolf-V3.1_020
- Fixed flashing of the images in the previous 018 build
- Added back support for unpacking of the LZ4 compressed ramdisk
- Fixed bookmark feature
RedWolf-V3.1_019
- Disable TWRP installation directly during the first boot
- Default time zone was set to CEST
- Use military time as default time.
- Support of the custom themes was completely removed from the installation process
- Few fixes & improvements in the strings.
- Default value of the RedWolf specific vibrations was slightly increased
- Improved saving/loading of the AromaFM config file.
- User can now select if recovery should disable stock recovery when system is mounted as read-only.
- Default color of the recovery was set to red.
- Fixed automatic reboot if the installation process was unsuccessful
- Center time in the statusbar as default
- Show CPU temp in statusbar as default
- Added "Red Wolf No-OS search engine". Enable this if you are sometimes getting No-OS installed error even when OS is installed.
- Added back support for extra languages
- Added support for Talian language
- Updated Chinese (simplified) translation of the AromaFM by LiuNian and Pzqqt
- Fixed displaying of the extra languages
- Improved mounting of the partitions during the applying of set on boot values
- Fixes with "stuck at unmounting"
- Highly improved speed of the recovery while setting up a new password, changing accent color or setting a new splash screen
- Magisk updated to the V14.3
- Recovery now won't allow the user to enter special characters while entering the password (Causing issues...)
- Few improvements with the Android Oreo installation
- Updated kernel
- Added ability to select if recovery should automatically disable forced encryption in the ROM
- Recovery will now automatically rename scripts in the system if the "Aggresive stock recovery deactivation" is enabled
- Added ability to select if recovery should automatically enable/disable USB Debugging in the ROM
- Removed some useless files to save the space
- Added support for saving the set on boot values also during the automatic reboot
- Redesigned flashlight icon
- Recovery now won't allow the user to enter the space in to the backup name
- Improved support of the last status checking of the MIUI ROM
- Recovery now won't show any button after the cancelled reboot action untill the sleep action won't be running anymore
- You can now select if recovery should also automaticaly reboot after the successfuly finished restore process
- Recovery will now hide the automatic backup feature if the system partition is mounted as read-only
- Updated recovery base to the AOSP 8.0.0
- Updated image drivers
- Added ability to select if recovery should automatically enable/disable "ro.adb.secure" property in the ROM
- Recovery will now automatically disable starting of the flash_recovery service if the "Aggresive stock recovery deactivation" is enabled (this process is also compatible with the backup of the init.rc by Magisk or SuperSU).
- Added new section called "Special Actions" in to the advanced menu
- Updated & optimized flashlight drivers
- Added ability to select if recovery should automatically enable/disable "ro.secure" property in the ROM
- Added ability to select if recovery should automatically enable/disable "ro.allow.mock.location" property in the ROM
- Highly improved support of the Incremental Package installation, detection etc.
- Updated Chinese (simplified) translation of the recovery by LiuNian and Pzqqt
- Added support for the complete deactivation of the secure boot in the MIUI based ROMs
- ADB is now automatically starting as root
- Added support for the RedWolf update package
- Default theme of the AromaFM was changed to holo black with the sense icons and automount turned on
- SuperSU Updated to the 2.82 SR5
- Updated ramdisk cleaner & added support for more kernels (thanks to @MOVZX's kernel installation scripts...)
- Small fixes with the /WOLF folder in the PartitionManager
- Highly improved speed of the reboot
- 'Deactivation process' is now automatically called during the installation instead of the reboot
- Imroved deactivation of the leds after the installation / backup / restore process.
- Fixed bug with recovery showing on the governor page that the active governor is "Interactive" even when user selected performance/powersave mode.
- Removed some GUI messages while we are installing built-in zips.
- And many other things which i don't remember anymore...
RedWolf-V3.1_018
- Fixed bugs with MIUI OTA Support to make sure that it will work even with newest beta builds of the MIUI
- Updated Polish translation by Daviteusz
- Fixed bugs in the Polish strings & edited the scale of the Russian strings
- Recovery will be now more aggressive if the process of the stock recovery doesn't want to be disconnected (Sometimes happen on some MIUI ROMs).
- Added detection of the installed ROM
RedWolf-V3.1_017
- Magisk updated to the V13.6
- SuperSU updated to the 2.82 SR3
- Added ability to automatically flash SuperSU config before the SuperSU - https://forum.xda-developers.com/apps/supersu/2017-08-13-supersu-config-t3655754
- Deactivated hw keys
- Added some missing back buttons
- Attempted to fix encryption
- Attempted to fix MIUI OTA installation - needs testing
- Removed extra languages (were not displayed properly)
- Small update which fixed deactivation of the dm-verity & forced encryption. Now you really don't have to flash the lazyflasher everytime when you are installing the MIUI ROM.
RedWolf-V3.1_016
- Fixed feature "Backup wifi, bluetooth & hosts" not to work if the user wiped the data partition using the "factory reset".
- TWRP source code was updated to the Aug 15, 2017
- Fixed recovery remembering the wipe list after setting a new gui page.
- Improvements with the mounting of the partitions during the boot
- Fixed led drivers on mido
- Fixed ability to set custom backup folder name & ADB ID
RedWolf-V3.1_015
- Updated with the latest TWRP changes
- Added flashlight switch on mido
RedWolf-V3.1_014
- Fixed recovery not deactivating the dm-verity, forced encryption, & stock recovery if the OS was detected as not installed. This issue was often happening on some MIUI ROMs.
- Improvements with the OTA update system of the MIUI.
- Fixed wrong reboot for some users.
- Added support for automatic deactivation of the dm-verity, forced encryption & stock recovery after finishing the OpenRecoveryScript process.
- Fixed recovery not deactivating the dm-verity & forced encryption during the automatic reboot after the finished installation.
- Better explain the current situation if the OS was detected as not installed.
- osm0sis's scripts "unpackbootimg" & "mkbootimg" can now be easily called from the script or terminal
- Improved the speed of the reboot
- Updated the community script "Fingerprint scanner fix" by Magua. It's now working again!
- Added NTFS & exFAT support
- Added more languages and updated Polish RedWolf translation by @Daviteusz
- Added FGO patch - https://goo.gl/GBkhMN
RedWolf-V3.1_013
- Slightly improved deactivation of the stock recovery during reboot after the zip installation
- Added ability to flash boot logo in the recovery
- Fixed firmware restoring issues
RedWolf-V3.1_012
- added F2FS support for mido
- added Night Mode (kcal) support for mido
RedWolf-V3.1_011
- Updated Polish translation by @Daviteusz
- Added few missing strings from the latest TWRP source
[Red Wolf] Install TWRP and root your device without breaking incremental OTA's!
Known Bugs:
- Flashlight is not working.
Downloads:
Latest build for Xiaomi Mi Mix 2 (chiron)
RedWolf-Unofficial-chiron.img
Warning:
Please remember that recovery with password protection isn't still a full protection for your phone. Red Wolf can only prevent unauthorized access to your device from recovery. But your device can be still reinstalled using fastboot or Miflash.
XDA:DevDB Information
[RECOVERY][UNOFFICIAL][CHIRON][V3.2.1-026] Red Wolf Recovery Project, Tool/Utility for the Xiaomi Mi Mix 2
Contributors
yshalsager, ATG Droid, Dadi11
Source Code: https://github.com/RedWolfRecovery
Version Information
Status: Testing
Created 2018-02-21
Last Updated 2018-02-21
Click to expand...
Click to collapse
Oi, don't work on my mi mix 2,stay in Xiaomi logo
Sent from my [device_name] using XDA-Developers Legacy app
Avoid quoting the OP, we don't want to spend ages scrolling through stuff that's already in post 1
Great! Your recovery seems to b absolutely promising!
(I wish I had learned from the development earlier that would have saved a lot of time )
TwoFour questions:
- is en-/decryption proofed working for MIUI as well as LOS/RR/AOSP/AICP roms based on Android 7.0/7.1/8.0?
- could the theme be deactivated to let it look more stock?
- is touchscreen working for all the above ROM types and versions?
- inline kernel means prebuild? -> is there any possibility to have sources for that kernel and build config? This would help in fine tunig the device/recovery and stay on top in security point of view
If first question could be stated as yes then i can shut down my own research for a good stable recovery and would prefer yours for the community.
raupe said:
Great! Your recovery seems to b absolutely promising!
(I wish I had learned from the development earlier that would have saved a lot of time )
TwoThree questions:
- is en-/decryption proofed working for MIUI as well as LOS/RR/AOSP/AICP roms based on Android 7.0/7.1/8.0?
- could the theme be deactivated to let it look more stock?
- is touchscreen working for all the above ROM types and versions?
If first question could be stated as yes then i can shut down my own research for a good stable recovery and would prefer yours for the community.
Click to expand...
Click to collapse
Unfortunately I don't have the device so I can't test
Mi logo on oreo 8.2.1 by miuipro . Sad
yshalsager said:
Unfortunately I don't have the device so I can't test
Click to expand...
Click to collapse
OK this makes dev & debugging very hard (... have an equal situation with mi mix that has been given to a friend and thats rarely available for debugging new builds).
Could you give some more information what repos/branches you've used for device-common, vedor-device & vedor-common (and maybe others) that are required to build your twrp-image for chiron?
Thanks mate!
---------- Post added at 01:35 PM ---------- Previous post was at 01:30 PM ----------
I'm also stuck at boot logo.
My ROM: xiaomi.eu 8.2.1
raupe said:
OK this makes dev & debugging very hard (... have an equal situation with mi mix that has been given to a friend and thats rarely available for debugging new builds).
Could you give some more information what repos/branches you've used for device-common, vedor-device & vedor-common (and maybe others) that are required to build your twrp-image for chiron?
Thanks mate!
Click to expand...
Click to collapse
All sources are given in 2nd post.
You'll have to use 7.1 build system with RW recovery sources, clone device tree and build.
I'm also stuck at boot logo
miuipro 8.2.x
yshalsager said:
All sources are given in 2nd post.
You'll have to use 7.1 build system with RW recovery sources, clone device tree and build.
Click to expand...
Click to collapse
Hi @yshalsager
followed your instructions an took a omni7.1 build environment with nothing else the repos you provided and got a build error for missing libs
Code:
recoverydevice="chiron" && . build/envsetup.sh && breakfast $recoverydevice && lunch omni_$recoverydevice-eng && croot && make -j8 recoveryimage && mv $OUT/recovery.img $OUT/twrp-3.2.1-0-$recoverydevice-raupe-$(date +%Y%m%d-%H%M)-OMNI.img
including device/xiaomi/chiron/vendorsetup.sh
including sdk/bash_completion/adb.bash
WARNING: device/xiaomi/chiron/omni.dependencies file not found
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=7.1.2
TARGET_PRODUCT=omni_chiron
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm64
TARGET_ARCH_VARIANT=armv8-a
TARGET_CPU_VARIANT=kryo
TARGET_2ND_ARCH=arm
TARGET_2ND_ARCH_VARIANT=armv7-a-neon
TARGET_2ND_CPU_VARIANT=cortex-a53
HOST_ARCH=x86_64
HOST_2ND_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-4.4.0-112-generic-x86_64-with-Ubuntu-16.04-xenial
HOST_CROSS_OS=windows
HOST_CROSS_ARCH=x86
HOST_CROSS_2ND_ARCH=x86_64
HOST_BUILD_TYPE=release
BUILD_ID=NJH47F
OUT_DIR=/home/raupe/android/omni7-1_v8/out
============================================
...
... collecting files, prebuild kernel message and all that stuff ...
...
Starting build with ninja
ninja: Entering directory `.'
ninja: error: '/home/raupe/android/omni7-1_v8/out/target/product/chiron/obj/SHARED_LIBRARIES/libcryptfs_hw_intermediates/export_includes', needed by '/home/raupe/android/omni7-1_v8/out/target/product/chiron/obj/SHARED_LIBRARIES/libcryptfslollipop_intermediates/import_includes', missing and no known rule to make it
make: *** [build/core/ninja.mk:158: ninja_wrapper] Error 1
#### make failed to build some targets (01:05 (mm:ss)) ####
This usually happens when you don't add older device-qcom-common repos (for cm13/cm14) with crypt_hw and if you have no vendor files.
Is it possible you have those files&folders on your build environment from older builds or for other devices?
raupe said:
Hi @yshalsager
followed your instructions an took a omni7.1 build environment with nothing else the repos you provided and got a build error for missing libs
Code:
recoverydevice="chiron" && . build/envsetup.sh && breakfast $recoverydevice && lunch omni_$recoverydevice-eng && croot && make -j8 recoveryimage && mv $OUT/recovery.img $OUT/twrp-3.2.1-0-$recoverydevice-raupe-$(date +%Y%m%d-%H%M)-OMNI.img
including device/xiaomi/chiron/vendorsetup.sh
including sdk/bash_completion/adb.bash
WARNING: device/xiaomi/chiron/omni.dependencies file not found
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=7.1.2
TARGET_PRODUCT=omni_chiron
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm64
TARGET_ARCH_VARIANT=armv8-a
TARGET_CPU_VARIANT=kryo
TARGET_2ND_ARCH=arm
TARGET_2ND_ARCH_VARIANT=armv7-a-neon
TARGET_2ND_CPU_VARIANT=cortex-a53
HOST_ARCH=x86_64
HOST_2ND_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-4.4.0-112-generic-x86_64-with-Ubuntu-16.04-xenial
HOST_CROSS_OS=windows
HOST_CROSS_ARCH=x86
HOST_CROSS_2ND_ARCH=x86_64
HOST_BUILD_TYPE=release
BUILD_ID=NJH47F
OUT_DIR=/home/raupe/android/omni7-1_v8/out
============================================
...
... collecting files, prebuild kernel message and all that stuff ...
...
Starting build with ninja
ninja: Entering directory `.'
ninja: error: '/home/raupe/android/omni7-1_v8/out/target/product/chiron/obj/SHARED_LIBRARIES/libcryptfs_hw_intermediates/export_includes', needed by '/home/raupe/android/omni7-1_v8/out/target/product/chiron/obj/SHARED_LIBRARIES/libcryptfslollipop_intermediates/import_includes', missing and no known rule to make it
make: *** [build/core/ninja.mk:158: ninja_wrapper] Error 1
#### make failed to build some targets (01:05 (mm:ss)) ####
This usually happens when you don't add older device-qcom-common repos (for cm13/cm14) with crypt_hw and if you have no vendor files.
Is it possible you have those files&folders on your build environment from older builds or for other devices?
Click to expand...
Click to collapse
Clone TeamWin/android_device_qcom_common branch android-7.1
to device/qcom/common
yshalsager said:
Clone TeamWin/android_device_qcom_common branch android-7.1
to device/qcom/common
Click to expand...
Click to collapse
OK build was possible with this but also got stuck while booting - even with other prebuild kernel images.
Maybe there are some config scripts in recovery/root that are showstoppers.
... will have a look to that tomorrow/maybe weekend.
raupe said:
OK build was possible with this but also got stuck while booting - even with other prebuild kernel images.
Maybe there are some config scripts in recovery/root that are showstoppers.
... will have a look to that tomorrow/maybe weekend.
Click to expand...
Click to collapse
New build
https://www.androidfilehost.com/?fid=890129502657584829
Please test it
yshalsager said:
New build
https://www.androidfilehost.com/?fid=890129502657584829
Please test it
Click to expand...
Click to collapse
... hmm, sorry did not start too.
Device restarts after mi logo trying to boot recovery.
{
"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"
}
Code:
/*
* Your warranty is now void.
*
* We're not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Red Wolf Recovery is custom recovery based on TWRP source code however some things are working here slightly different then you might expected. The main objective of this project is to provide stable recovery with features which you have never seen before in a recovery and which have not been accepted for adding to the official source code of TWRP. This recovery is also first recovery on the world with password protection.
Based on TWRP version: 3.2.1
For devices: Nitrogen
Authors build: RomFactory
Developers: @ATG Droid & @dadi11
Thanks: z31s1g (for the base of his theme), Ray Li (For his useful advice in the beginnings), osm0sis (for his image scripts), etc.
Features:
Code:
[B]Translated to EN, PL, zh_cn, & CZ [/B]
- Password protection
- Flashlight
- MIUI Incremental OTA Support
- Built-in latest Magisk, SuperSU & AromaFM
- Support two screenshot GUI actions - Power+VolDown to save screenshot in to the internal storage &
Power+VolUp to save screenshot in to the external storage (Will be automatically saved in to the internal in case
that external storage doesn't exist).
- Support automatic reboot after the restore process
- Recovery can automatically modify some props in the ROM directly during the installation
- Some built-in scripts from community
- Tap to wake support
- Advanced deactivation of the stock recovery
- Automatic deactivation of the dm-verity & forced encryption directly during the installation of the ROM
- Recovery can notify you about the completed backup/restore/installation using the notification diode & vibration.
- Support "set on boot" settings.
[B]* Changes for security reasons *[/B]
- ADB isn't starting automatically at the start of the recovery. You have to activate it in recovery
- MTP isn't starting until user enter correct password
- Deactivated TWRP theme engine
Some differences to the official version:
Code:
[COLOR="red"]- get out of here if you are pirating apps. this recovery is not for you[/COLOR]
- always up-to-date with the latest TWRP changes
- compiled on omnirom-8.1 source
- kernel compiled inline with the recovery
- There isn't bug with reboot from recovery to recovery
- more languages
- other improvements from Features and Changelog lists
Changelog:
Code:
RedWolf-V3.2_027
- If screen is turned off then automatically detect AROMA Installer package and unblank screen before starting the update binary which is going to call AROMA GUI, so we won't be stuck at the black screen since AROMA engine require screen to be turned on.
- Added ability to change OTA Survival driver properties from the recovery GUI, allowing recovery to support "out of the box" almost all incremental OTA updates from different OEMs/custom ROMs out there (as long as they have correctly formatted metadata).
- Notify user about the current activity of the deactivation process - that's handled under the console
- Improved dumwolf driver
- Removed the vibration feedback from all GUI elements
- Automatically resize bootable partitions during nandroid backups
- Changed theme to black/white/red style based on @TBO material theme
- Data files aren't anymore saved on the storage partitions, which means that we're now able to survive even encrypted device.
- Some bug fixes and improvements...
RedWolf-V3.2_026
- This is just a quick bug fix release for MIUI users. So is highly recommend to update to this build if you are using MIUI.
RedWolf-V3.2_025
- Fixed crash of the recovery while running OTA_RES.. (So MIUI OTA is now working again)
- General bug fixes and improvements
- Fixed bug with MIUI Updater app showing error that installation failed after installation of full ROM
- Deactivation process is now called only when it's really needed
- Updated kernel
RedWolf-V3.2_024
- Fixed GUI color glitch while starting Aroma Installer update-binary
- Optimized pigz runtime process
- Updated recovery base to the AOSP 8.1.0 & TWRP 3.2.1
- Highly improved signature verification for Incremental packages so now we can be really sure if the package is compatible with the ROM.
- Introduced a file based backup/restore engine. Expect it to be improved with the next builds...
- Improved security related to the password protection
- Fixed loading of the AromaFM config file
- System survival process for Incremental packages is now set by default
- Code optimizations
- Removed the dumwolf process
- Added signature check for incremental OTA survival so we won't be unnecessarily creating a new one if it's signed under the same access key
- Magisk updated to the version 15.1
- Added Indonesian language
- Fixed issues with Chinese characters...
- Governor which is changed by the action in the recovery GUI is now automatically set for all cores instead of only four.
RedWolf-V3.2_023
- Updated recovery base to the TWRP version 3.2.0
- Fixed issue with recovery sometimes showing "NO-OS" page even when OS is installed
- Merged: Fstab V2, minui updates, Keymaster 3.0 support, ADB updates, fixes related to the compiling errors...
- Added patch against the pirating applications
RedWolf-V3.1_022
- Small improvements in the installation process
- Recovery will now automatically warn the user in case that user selected to install the zip which contain a bootloader
- You can now wipe installed substratum overlays directly from the "advanced wipe" section
RedWolf-V3.1_021
- Automatically return install error if there is any issue with Incremental OTA Survival
- Added option to also backup system partition for Incremental OTA Survival (It's not always needed, but just in case it's better to backup it.)
- Added support for the compatibility verification of the Incremental Package
- Rebuilded & improved installation process
- Fixed starting process not being disabled correctly in case that we are running ORS
- Translation update
- Added support for devices with 2GB RAM or less... (Check installation process of this build for more info)
- Added checkbox for activation/deactivation of the boot check (Disable only if you really need to).
- Fixed booting problems on some custom ROMs which don't have gzip compressed ramdisk
- Removed bookmark feature
- Added ability to unzip files using the stock filemanager.
- Added search selection for the stock filemanager.
- Fixed 'No OS' on system image restore after wipe
- Merged some latest commits from TWRP gerrit
RedWolf-V3.1_020
- Fixed flashing of the images in the previous 018 build
- Added back support for unpacking of the LZ4 compressed ramdisk
- Fixed bookmark feature
RedWolf-V3.1_019
- Disable TWRP installation directly during the first boot
- Default time zone was set to CEST
- Use military time as default time.
- Support of the custom themes was completely removed from the installation process
- Few fixes & improvements in the strings.
- Default value of the RedWolf specific vibrations was slightly increased
- Improved saving/loading of the AromaFM config file.
- User can now select if recovery should disable stock recovery when system is mounted as read-only.
- Default color of the recovery was set to red.
- Fixed automatic reboot if the installation process was unsuccessful
- Center time in the statusbar as default
- Show CPU temp in statusbar as default
- Added "Red Wolf No-OS search engine". Enable this if you are sometimes getting No-OS installed error even when OS is installed.
- Added back support for extra languages
- Added support for Talian language
- Updated Chinese (simplified) translation of the AromaFM by LiuNian and Pzqqt
- Fixed displaying of the extra languages
- Improved mounting of the partitions during the applying of set on boot values
- Fixes with "stuck at unmounting"
- Highly improved speed of the recovery while setting up a new password, changing accent color or setting a new splash screen
- Magisk updated to the V14.3
- Recovery now won't allow the user to enter special characters while entering the password (Causing issues...)
- Few improvements with the Android Oreo installation
- Updated kernel
- Added ability to select if recovery should automatically disable forced encryption in the ROM
- Recovery will now automatically rename scripts in the system if the "Aggresive stock recovery deactivation" is enabled
- Added ability to select if recovery should automatically enable/disable USB Debugging in the ROM
- Removed some useless files to save the space
- Added support for saving the set on boot values also during the automatic reboot
- Redesigned flashlight icon
- Recovery now won't allow the user to enter the space in to the backup name
- Improved support of the last status checking of the MIUI ROM
- Recovery now won't show any button after the cancelled reboot action untill the sleep action won't be running anymore
- You can now select if recovery should also automaticaly reboot after the successfuly finished restore process
- Recovery will now hide the automatic backup feature if the system partition is mounted as read-only
- Updated recovery base to the AOSP 8.0.0
- Updated image drivers
- Added ability to select if recovery should automatically enable/disable "ro.adb.secure" property in the ROM
- Recovery will now automatically disable starting of the flash_recovery service if the "Aggresive stock recovery deactivation" is enabled (this process is also compatible with the backup of the init.rc by Magisk or SuperSU).
- Added new section called "Special Actions" in to the advanced menu
- Updated & optimized flashlight drivers
- Added ability to select if recovery should automatically enable/disable "ro.secure" property in the ROM
- Added ability to select if recovery should automatically enable/disable "ro.allow.mock.location" property in the ROM
- Highly improved support of the Incremental Package installation, detection etc.
- Updated Chinese (simplified) translation of the recovery by LiuNian and Pzqqt
- Added support for the complete deactivation of the secure boot in the MIUI based ROMs
- ADB is now automatically starting as root
- Added support for the RedWolf update package
- Default theme of the AromaFM was changed to holo black with the sense icons and automount turned on
- SuperSU Updated to the 2.82 SR5
- Updated ramdisk cleaner & added support for more kernels (thanks to @MOVZX's kernel installation scripts...)
- Small fixes with the /WOLF folder in the PartitionManager
- Highly improved speed of the reboot
- 'Deactivation process' is now automatically called during the installation instead of the reboot
- Imroved deactivation of the leds after the installation / backup / restore process.
- Fixed bug with recovery showing on the governor page that the active governor is "Interactive" even when user selected performance/powersave mode.
- Removed some GUI messages while we are installing built-in zips.
- And many other things which i don't remember anymore...
RedWolf-V3.1_018
- Fixed bugs with MIUI OTA Support to make sure that it will work even with newest beta builds of the MIUI
- Updated Polish translation by Daviteusz
- Fixed bugs in the Polish strings & edited the scale of the Russian strings
- Recovery will be now more aggressive if the process of the stock recovery doesn't want to be disconnected (Sometimes happen on some MIUI ROMs).
- Added detection of the installed ROM
RedWolf-V3.1_017
- Magisk updated to the V13.6
- SuperSU updated to the 2.82 SR3
- Added ability to automatically flash SuperSU config before the SuperSU - https://forum.xda-developers.com/apps/supersu/2017-08-13-supersu-config-t3655754
- Deactivated hw keys
- Added some missing back buttons
- Attempted to fix encryption
- Attempted to fix MIUI OTA installation - needs testing
- Removed extra languages (were not displayed properly)
- Small update which fixed deactivation of the dm-verity & forced encryption. Now you really don't have to flash the lazyflasher everytime when you are installing the MIUI ROM.
RedWolf-V3.1_016
- Fixed feature "Backup wifi, bluetooth & hosts" not to work if the user wiped the data partition using the "factory reset".
- TWRP source code was updated to the Aug 15, 2017
- Fixed recovery remembering the wipe list after setting a new gui page.
- Improvements with the mounting of the partitions during the boot
- Fixed led drivers on mido
- Fixed ability to set custom backup folder name & ADB ID
RedWolf-V3.1_015
- Updated with the latest TWRP changes
- Added flashlight switch on mido
RedWolf-V3.1_014
- Fixed recovery not deactivating the dm-verity, forced encryption, & stock recovery if the OS was detected as not installed. This issue was often happening on some MIUI ROMs.
- Improvements with the OTA update system of the MIUI.
- Fixed wrong reboot for some users.
- Added support for automatic deactivation of the dm-verity, forced encryption & stock recovery after finishing the OpenRecoveryScript process.
- Fixed recovery not deactivating the dm-verity & forced encryption during the automatic reboot after the finished installation.
- Better explain the current situation if the OS was detected as not installed.
- osm0sis's scripts "unpackbootimg" & "mkbootimg" can now be easily called from the script or terminal
- Improved the speed of the reboot
- Updated the community script "Fingerprint scanner fix" by Magua. It's now working again!
- Added NTFS & exFAT support
- Added more languages and updated Polish RedWolf translation by @Daviteusz
- Added FGO patch - https://goo.gl/GBkhMN
RedWolf-V3.1_013
- Slightly improved deactivation of the stock recovery during reboot after the zip installation
- Added ability to flash boot logo in the recovery
- Fixed firmware restoring issues
RedWolf-V3.1_012
- added F2FS support for mido
- added Night Mode (kcal) support for mido
RedWolf-V3.1_011
- Updated Polish translation by @Daviteusz
- Added few missing strings from the latest TWRP source
Known Bugs:
- Flashlight is not working.
Downloads:
Latest build for Xiaomi Mi Max 3 (nitrogen)
RedWolf-027-Unofficial-nitrogen.img
How to install miui OTA updates:
1- Follow this guide [Red Wolf] Install TWRP and root your device without breaking incremental OTA's!
2- Change OTA Survival trigger path from to "META-INF/com/miui_miui_update" to "META-INF/com/google/android/update-binary".
Warning:
Please remember that recovery with password protection isn't still a full protection for your phone. Red Wolf can only prevent unauthorized access to your device from recovery. But your device can be still reinstalled using fastboot or Miflash.
Source link :- https://github.com/RedWolfRecovery
XDA:DevDB Information
[UN-OFFICIAL][NITROGEN][V3.2.1-027][DECRYPTION] Red Wolf Recovery Project, Tool/Utility for the Xiaomi Mi Max 3
Contributors
ROMFACTORY, yshalsager
Source Code: https://github.com/TeamWin/android_device_xiaomi_nitrogen
Version Information
Status: Stable
Stable Release Date: 2018-08-06
Created 2018-08-06
Last Updated 2018-08-06
How to install OTA updates with RedWolf Recovery? - v27 only!
0- Install Redwolf recovery and Reboot recovery.
1- Click on theme icon on the top - section with RedWolf specific settings.
2- Enable this checkbox: "Support OTA Survival trigger package"
If you are using system mods, like cam2api enable system backup.
3- Go to third tab and change OTA Survival trigger path from to "META-INF/com/miui/miui_update" to "META-INF/com/google/android/update-binary".
4- Flash full MIUI ROM and flash ota.
5- Disable Support OTA Survival trigger package before flashing anything.
6- Flash whatever you want after that. Like magisk, etc.
7- Reboot your device in to the system.
8- When you get some update just download it using updater app, reboot to recovery, enable Support OTA Survival trigger package then flash it manually.
9- Don't forget to disable Support OTA Survival trigger package again after flashing ota, it's needed every time you flash.
Enjoy!
another reserved
Why should we use this over the other TWRP that you posted?
Also the other twrp is the latest 3.2.2 and this is 3.2.1
What do you recommend to use for Xiaomi.eu and magisk?
omer919 said:
Why should we use this over the other TWRP that you posted?
Also the other twrp is the latest 3.2.2 and this is 3.2.1
What do you recommend to use for Xiaomi.eu and magisk?
Click to expand...
Click to collapse
It has more features than the standard TWRP.
If you are more fimiliar with TWRP then you should probably go with it. But if you want to test some new things out, go ahead and flash RWRP
Cheers
Thanks for your work. This TWRP works very well. I just could not find the features for not breaking the OTA updates (checked the Red Wolf settings) Are they incorporated into this tWRP (in Redmi yes but this too?) Thanks (maybe a screenshot might help if someone could show me where those settings are)
From the Redmi guide (link in the OP)
"Now click on icon on the top - section with RedWolf specific settings.
Here find and enable this checkbox: "Support OTA Survival trigger package"
(this is what I could not find in this TWRP) even otherwise awesome work!
I have one issue now.
I had this recovery installed before but tried Orange fox.
Now when I installed this recovery again the reboot menu don't work.
Pressing either reboot system, recovery or turn off the phone won't do that.
It just hangs in the process and I have to hold the powerbutton to turn it off.
Can this be fixed?
Very useful application. Now compatible with A11. You can also transfer apps & data from Stock EMUI firmware (of course, only third-party applications, it is logical) .
You will need a "three apks kombo" :
- Basic apk:
https://mega.nz/#!5hkhTYYQ!eTnrXxVdUSodIvzgSMUYRyN5XXz3nKDYE8EzVIz85Ig
- Flasher:
https://mega.nz/#!818XSKAR!ICu8cjjBKkLWqsPGxiuHdIcfDlmP2EIhqwmT6uIEjgs
- Helper:
https://mega.nz/#!YokVhabZ!i6kzt1OZgUQckWdiIp_gFebY7xfF_baSFNQoY2bcalw
Works with SuperUser or Magisk root.
Source:
https://forum.xda-developers.com/t/...20-migrate-custom-rom-migration-tool.3862763/
Thanks for sharing
Null
Typo.