[ROM][B371] H7cROM (Honor 7 configurable ROM) -> EOL - Honor 7 Android Development

Hello,
Due to the fact that my Honor 7 is broken now and a repair is to expensive I had to make the decision to stop further development regarding H7cROM (with a tear in my eye) => EOL !
this is my first custom ROM that I am publishing here. It's called H7cROM (Honor 7 configurable ROM) and 0.13b(eta) is the current version.
Please take the time to read the whole post so that you get an impression about H7cROM.
Background / Intention
Currently there are several very good custom ROMs avaiable for the H7 device (e. g. H7T by T-Ryder, Yoda-ROM by Ryrzy, MoDaCo-ROM by PaulOBrien, MM+D by WBT). All authors have spend a lot of time and brain work into their ROMs so that I have to be reverent looking to their ROMs.
In order to avoid any kind of misunderstanding I have to emphasize in advance that I don't want to critisize the ROM cookers - it's exactly the opposite because I could take a lot of ideas and approaches and all ROM variants were a great inspiration for me. Because of that I have to say THANK YOU.
But unfortunately all those ROM variants have one weakness and that's the "take it or leave it" attitude. With each of those ROMs the user gets a firmware with a fixed mixture of apps, patches and settings. Only Yoda-ROM and MM+D have some options to choose - but in my opinion that's only a very small number of intervention points.
Approach / Description
H7cROM's approach is to give the users the chance to decide for a wider bunch of options whether to install it or not. Thus Aroma installer is used to provide an interface for the users choices so that you can configure your system more individually.
Unfortunately Aroma installer only supports flashable zip file up to a size of 2GB. Thus I had to devide the installation process into two phases (2 zip files):
Phase 1 (H7cROM-Phase1-B371.zip)
which offers several menus to install and customize a very slimmed version of Honors B371 firmware.
Phase 2 (H7cROM-Phase2-yyyymmdd.zip)
which offers menus with a wide bunch of apps that can be installed in "batch mode" (usually much faster than using Playstore).
Short description of phase 1 (H7cROM-Phase1-B371.zip)
During phase 1 you can install a slim version of the stock firmware B371 that includes busybox already but several apps were deleted in advance. At the beginning the user can decide
which kernel shall be installed (Standard, MoDaCo, Yoda)
to execute a factory reset or to delete caches
how to configure the partitions /recovery and /recovery2 (stock or TWRP)
to root the device
to deactivate the Honor theme engine
to activate several hidden and other options (network speed, 4G menu etc.)
to install system enhancements (init.d support, HTC Beats Audio, Dolby Atmos FX, Vidper4Android)
to prepare the device for flashing Xposed
Furthermore a lot of preinstalled apps can be deleted so that you can decide how your device setup will look like.
To get a better feeling for H7cROM I have attached a flashable dummy zip file for phase 1. This file will definitively install nothing - you can only see the options.
Short description of phase 2 (H7cROM-Phase2-2016mmdd.zip)
During the second phase you can select approximately 100 apps to be installed. Depending on the number of apps that you are selecting this installation process is much faster than using playstore. You select from the following categories:
File managers
Browsers
Honor / Huawei specific apps
Communication apps
Office apps
Launcher
Multimedia apps
Infrared remote control
Navigation
Google Play
Standard Android apps
Root related tools
other tools and useful apps
printer service plugins
Keyboard
Games
To get a better feeling for H7cROM I have attached a flashable dummy zip file for phase 2 as well. Again, this file will definitively install nothing - you can only see the options.
Requirements:
Honor 7 PLK-L01 with
stock firmware PLK-L01C432B370 or PLK-L01C432B371
unlocked bootloader
TWRP 3.0.2
external SD card
Installation:
make a complete backup (Nandroid)
copy both flashable files to your SD card
install TWRP if not done (please deactivate it's screensaver to avoid side effects with Aroma Installer)
Run zip file for the first phase (H7cROM-Phase1-B371.zip) using TWRP (when doing it the first time it is strongly recommended to choose factory reset)
Reboot system
In order to avoid heat issues during the second phase please give your device the chance to cool down
Reboot to TWRP
Run the zip file for the second phase (H7cROM-Phase2-jjjjmmtt.zip)
Reboot (depending on the number of installed apps that can take several minutes - please be patient!)
Screenshots
... are unfortunately not availabe because I wasn't able to make screenshots of Aroma Installer menus by now.
Please test the attached dummy zip files to gain a better feeling and understanding of the approach for H7cROM.
Downloads
The flashable zip files for both phases can be downloaded <here>
general comments (please consider the content):
The flashable zip files are still in an early beta phase! I am publishing it here in order to get further hints and comments from the community to improve the ROM ... but please be aware that beta means that it is not perfect
The phase 1 zip file contains a complete (slimmed) firmware, the corresponding configuration files and several additional enhancements and tweaks
Rooting is done by using Chainfire's zip files; due to some limitations of the stock kernel there are two ways of rooting:
Stock kernel:
The combination of the stock kernel and the Chainfire's update-supersu-v2.76.zip is leading to a bootloop - thus I am using update-supersu-v2.62.zip if stock kernel is installed
MoDaCo kernel and Yoda kernel:
For both kernel variants Chainfire's update-supersu-v2.76.zip is used for rooting
If you decide to root your device during the H7cROM installation the corresponding zip file will be stored in folder /h7cROM on your SD card
The same happens with the Xposed related zip file if you decide that the phone shall be prepared for Xposed - this way not only the Xposed installer will be installed but you will also have the corresponding flashable zip file accessable.
Furthermore H7cROM will generate backups (dumps) of several partitons and store it in folder /H7cROM as well if you run the installation on a device with firmware version B370.
Needless to say: there is no warranty at all for H7cROM
You are using it on your own risk
I don't take responsibility for any kind of hardware problems and/or software issues
Due to very limited spare time I am only able to provide an absolut minimum of support
Publishing H7cROM here does not mean that I promise to continue the ROM for a specific period of time
For German native speakers this ROM is also available on android-hilfe.de.
Beta forever (or banana software that matures on users side)
Why this headline? That's easy to explain. Due to the big number of potential option combinations I am not able to test all combinations. Assuming there would only be 16 combinations to test and each test would take only 5 minutes that would mean that I would have to test 2^16 = 65.526 configurations with a duration of 5 minutes. That would lead to an overall testing time of 227 days ... unrealistic.
Credits:
I would like to say "THANK YOU VERY MUCH" to the following people (in alphabetical order):
@amarullz (Aroma Installer)
@androidexpert35 (HTC Beats Audio mod)
@Chainfire (SuperSU and the corresponding flashable zip files)
@Demeth (increasing the maximum volume of Honor 7)
@DigiGoon (DigiKernal v1.0)
@inside!out (Dual recovery for Honor 7)
@non-toxic (Hint how to hide the nav bar)
@paulobrien (TWRP 3.0.2 for Honor 7, MoDaCo-ROM, MoDaCo Kernel, Stockify ...)
@Speedo.thc (MM+D EMUI ROM)
@revo89 (Xposed framework and Xposed installer)
@Ryrzy (Yoda-ROM and Yoda-Kernel)
@t-ryder on t-ryder.de (H7T-ROM, H7T theme, the H7cROM logo and a lot of hints for my ROM)
@Toldo (Camera Mod)
@walter4991 (Honor 7 multi windows option)
@wanam (Adaption of Xposed for Honors EMUI)
@worstenbrood (Dolby Atmos FX)
@zhuhang (Viper4Android)
and of course to all software engineers and modders who are providing their hard work for free.
Known issues:
The problem that the app Designs does not support downloading themes on some devices is currently not fixed
Unfortunately it might happen that the Aroma Installer stops execution without a visible reason. This happens quite seldom (~3-5%). In that case please repeat the installation process.
During the installation process the H7 device is getting quite hot ... because of that you should not run both phases directly one after the other - give your device the chance to cool down a bit before installing phase 2; as far as I know TWRP will stop execution when the device gets to hot.
Changelog:
Version 0.13b(eta):
+ added support for USB OTG devices (if attached) to store backup and zip files there as well (phase 1)
± replaced Viper4Android with the corresponding material design version (phase 1)
± using supersu.zip version 2.78 instead of version 2.76 (phase 1)
- deleted SuperSu as optional app (phase 2)
± updated all apps (phase 1 and phase 2)
Version 0.12b(eta):
± DigiKernel updated to v1.1 - now with init.d support - Thx to @DigiGoon (phase 1)
± language files for Aroma Installer updated and partly restructured (phase 2)
± updated all apps (phase 1 and phase 2)
Version 0.11b(eta):
- reduced the number of updated partitions to a minimum (phase 1)
+ added DigiKernel as a further kernel option - Thanks to @DigiGoon (phase 1)
+ updated all apps (phase 1 and phase 2)
Version 0.10b(eta):
+ added option to keep recovery configuration as it is (phase 1)
+ added option to delete Huawei clock and weather widget (phase 1)
+ added Calendar+Planner (phase 2)
+ added Sony XPeria Digital Clock Weather widget (phase 2)
+ added Devexpert Weather Clock widget (phase 2)
+ added Transparent Clock Weather widget(phase 2)
± moved Google Calculator to phase 1
± moved Google Calendar to phase 1
± moved Google DeskClock to phase 1
± moved Google Messenger to phase 1
± moved Google Photos to phase 1
± changed menus for the above mentioned Google apps so that you can decide whether the corresponding Huawei app shall be replaced, both apps shall be installed or none of the alternatives (phase 1)
± moved True Phone dialer to phase2
± moved ZenUI dialer and contacts to phase2
± moved CleverDialer to phase2
± moved Drupe dialer to phase2
± moved Fleksy keyboard to phase2
± moved Swiftkey to phase2
Version 0.9b(eta):
± Updated theme H7T to version 4 - Thx to T-Ryder (phase 1)
± Menus regarding kernel and recovery restructured (phase 1)
+ Added TWRP 3.0.2-rc3 as further recovery option (phase 1)
+ Added selection of emojis (One / iOS / N) (phase 1)
± Updated all apps per 2016-08-14 (phase 1 and phase 2)
Version 0.8b(eta):
+ added some dialer apps as additional options (True Phone, ZenUI Phone + Contacts, CleverDialer, DrupeDialer) (phase 1)
+ added Fleksy Keyboard as an option (phase 1)
± moved installation of printer service plugins to phase 2
+ added Canon and Brother printer service plugins as options (phase 2)
+ added the apps Timed Toggles and Fontster to phase 2
± improved installation speed by code optimization (phase 1 and phase 2)
± apps updated (2016-08-13) (phase 1 and phase 2)
Version 0.7b(eta):
+ added some options to delete preinstalled apps (phase 1)
± Huawei Backup transformed from system app to user app (phase 1 and phase 2)
± apps updated (2016-08-08) (phase 1 and phase 2)
Version 0.6b(eta):
+ adopted menu for kernel and recovery selection in order to ensure that a factory reset will only be default when H7cROM wasn't installed before (phase 1)
+ for encrypted /data partition a factory reset was made mandatory
+ added app magnifier (Phase 2)
± deletion of Google playstore and Google mobile services during update process elimated (phase 1)
± Code changes to improve installation process (phase 1 and phase 2)
± several text related changes (phase 1 and phase 2)
± apps updated (2016-08-05) (phase 1 and phase 2)
- unused code deleted (e. g. for native call recorder which is not part of the distribution anymore) (phase 1 and phase 2)
Version 0.5b(eta):
+ option to increase wifi polling intervall (thx T-Ryder)
+ option to enhance number of apps "secured" regarding power management
+ option to disable Huawei disc on Window PCs (thx T-Ryder)
+ inserted a message after the core installation with the appropriate handling when the stock kernel was selected in combination with root
± apps updated (2016-08-01)
- Reboot by Aroma Installer deactivated to ensure that log files will be stored on sd card
Version 0.4b(eta):
+ theme H7T theme made by T-Ryder for the H7T-ROM (t-ryder.de)
+ theme SpectrumPure theme made by PaulOBrien (modaco.com)
+ ACR - call recorder (phase 2)
± some GUI aspects (phase 1)
± xposed zip file to version v86 arm64
± when updating from B370 to B371 more partition backups will be stored on sd card
- native call recorder tweak (phase 1)
Version 0.3b(eta):
± Correction regarding Aroma color themes
+ included VMall again which wasn't included in 0.2b accidentally
Version 0.2b(eta):
This is the first published version:
There are no changes - everything is new
Version 0.1b(eta):
First internal unpublished version
Best regards
m_esser

Hi, thanks for the idea. How are too planning to update the rom? Via ota?

Nop - via download link

THX! Nice to see that your rom has arrived the international forum users too!!!!
I don't know a more flexible custom rom for H7 until now. :good:

I currently have YodaROM v10, how can I install H7cRom?

Installation is described step by step in the first post.

Dummy files??

RicardoArantes said:
Dummy files??
Click to expand...
Click to collapse
To be honest - I don't understand what your question means - but anyhow ...
... the dummy files which are attached to the first post are only for presentation purposes so that you can find out what you can get
... the "real" ROM related zip files can be downloaded via the link that is mentioned in section "Download" in the first post
Best regards
m_esser

Flashed this Rom and now the phones doesn´t turn on.. help!!!

The ROM has been tested by several people in Germany without having that effect in the past.
Needless to say that I would really like to help you but in order to be able to do that you have to be a bit more precise:
Which firmware was installed when you tried to flash the ROM?
Did you get an error message? If yes, please post it here.
Do you have a bootloop or what exactly happens?
Did you interrupt the installation process?
Which version of TWRP did you use?
So, please describe the circumstances to get a specific answer.
Best regards
m_esser

@m_esser
i think, you have written to many text in the first post! nobody like to read a booklet to be able to use his phone!
Now you must live with the result my friend.

Oh - that's something I can live with...
Before publishing H7cROM here I thought about it very intensively because I am currently very busy. And for me there were two options how to do it:
Fast and short
with the risk that I will have to answer a lot of questions and posts to explain the approach
Less fast and with a long explanation
with the risk that people don't want to read it and only a few people will look into it
Due to my very rare spare time at the moment the first option would definitively overload my current capacity. Thus I have made the decision by intention to go ahead with option 2. This is my personal "defense line" to avoid unnecessary and unneeded support effort.
And if nobody is looking into H7cROM that's absolutely OK for me because primarily I have made it for myself (and I have learned a lot during this process ).
Best regards
m_esser

Great ROM! :good:
Finally a ROM that I can configure to my needs. Thanks.
essmgus

Hi, i've installed The 0.7beta.
Now il i want install The Last version, i need to format cache and data, or i can just install The last version?
Thanks

I'll probably install the first release when it'll come out ! Is the beta doing well so far ? any issue spotted ?

@Fi7agi:
If you have already installed a version of H7cROM you can choose "Clearing caches" instead of "Factory reset" so that your data will NOT be deleted. In this way you can update to the latest version.
@warzag:
Then you will have to wait forever ... the reason why is explained in section "Beta forever (or banana software that matures on users side)" in the first post.
Best regards
m_esser

m_esser said:
Nop - via download link
Click to expand...
Click to collapse
hi mate , I need some help , now im using china rom 'Kangvip custom rom b380 '
The rom is great, stable with lot more features. But it did not has the option to lock signal like in the European Rom.
Is it possible to port that feature into this china rom ? can you teach me .??

Without knowing the 'Kangvip custom rom b380 ' deeply I can only assume that you will not be able to get that funktion easily. The only option that might work is to use xposed in combination with a modul that will fit to your needs. That's something you have to test by your own.
SUPPLEMENT:
Perhaps I have an idea for you how to enable the switch for 4G communication.
For the European firmware you have to change the entry "ro.config.hw_hide_lte" from true to false in file "/cust/hw/eu/prop/local.prop". I assume that you will have a similar file in a similar folder and that you only have to replace "eu" in the path where you have to look for the prop file.
Of course you have to have root access on your phone.
Best regards
m_esser

Ok, Thanks.
In The future, web there is a new officia build What i need to do for upgrade?
Thanks

@Fi7agi: You simply have to install the zip file for the 1st phase - but keep in mind not to choose "Factory reset" but "Clearing caches" to ensure that your data including all user apps will be kept.
Best regards
m_esser

Related

[ROM][RK3066][SD] Custom KitKat 4.4.2 by 4pad.ru (RK3066)

Below is a link to some custom firmware form 4pda.ru
https://yadi.sk/d/AzvtZZSkcn8RC
And a translation of the description of the changes :
Just want to warn that this is only a BETA VERSION, so to me very much not happy.
For those who are not satisfied with a set of programs or unhappy that you have something not working, You're not forced to use this firmware and you can install an alternative firmware. And whatever you do, you do so at your own risk.
The basis from firmware Android parts for KLD version of Android part 4.4.2
What added,changed remotely:
1. In the firmware embedded ROOT,is Manager for ROOTа SuperUser (SU) (excellent updated from Play Marketa), busybox.
2. After installing the firmware, the default is English,time zone GMT +4 (Moscow),you can put a third-party application.
3. Section for program installations with 1 GB increased to 2 GB
4. Removed icons when the reverse speed, because personally to me they only interfered with.
5. Added in the Settings Menu Startup folder.
6. Fixed the inaccessibility of some programs in Play Markete (Yandex Navigator,Radar Arrow and others)
7. Added Google services ,CHROME updated to the latest stable version
8. Added file Manager ES File Explorer
9. Added file Manager Root Explorer
10. Added Titanium Backup Pro full
11. Added ® Xposed. You will need to log in and activate Xposed framework (be sure to restart your device)
12. Added XposedMTC. You will need to first run the program Xposed Installer framework itself(see paragraph 11) and activate it XposedMTC the Modules section (be sure to restart your device)
13. Removed standard Musik.apk (system MTCMusic)
14. Removed Chinese and Japanese keyboard.
15.Added in Settings-Screen-traffic Management. Where you can enable,disable,change the display color of traffic in the door notifications.
16.Added in Settings-System-screen Density. Where you will be able to install the appropriate density of the screen. My advice, install 200-220 dpi
17.Added in Settings-Screen-enable the application bar in the dummy notifications.
18 Changed the style of the watch and blinds notifications.
19. Other fixes and additions.
On the photos there is a button to shut down and Restart, I did not add...it made.
And a link to the pre-rooted 1024x600 that Estimilo wanted, done on 4pda.ru (he went on there and got someone to do it !):
https://yadi.sk/d/cEUejmyfcnGdL
Do you still have it?
I have tried to download this file but it is no longer up, can you post it again please?
Regards
Anderson
I have tried to download this file but it is no longer up, can you post it again please?
Regards
Fabio Nicolas

[G920F/FD/W8/...][6.0+] SYSTEMLESS DevBase | Encryption support | Stock OTA updates

SYSTEMLESS DevBase has been developed and physically tested on S7 Edge (G935F), so main thread containing the most detailed description you can find here:
>> [SAMSUNG][6.0+] SYSTEMLESS DevBase | Encryption support | Stock OTA updates <<
However, it should work on ALL SAMSUNG DEVICES running Android 6.0+, so if you are Galaxy S6 flat (G920xx) owner - please place your feedback & discussion here to let me know about device-specific issues or to let me know that everything works perfect
---------------------------------------------------------------------------
Are you tired with traditional custom ROMs?
Do you miss custom ROMs but you would like to have encrypted /data (for privacy/security reasons)?
You are in the right place! I present you SYSTEMLESS DevBase - an SYSTEMLESS equivalent of my previous work (for older devices)
Prerequisites:
- Samsung device running stock or stock-based Android 6.0+ (mandatory!)
- Rooted device - SuperSU v2.76+ installed in SYSTEMLESS mode (mandatory!) (*)
- Stock, untouched /system partition (not mandatory, but recommended for working OTA)
- Stock recovery (not mandatory, but recommended for working OTA)
(*) NOTE: The latest CF-Auto-Root image for G920F contains SuperSU v2.74 which does not support SYSTEMLESS solutions (su.d is not triggered early enough). It is NOT enough to update it via PlayStore to the newest version and update su binaries! You need to update it using TWRP / FlashFire installable ZIP from THIS STABLE or THIS BETA thread. Alternatively you can use "EverRoot" -> "Inject SuperSU" option in FlashFire even if you are rooted already by CF-Auto-Root (it will update SuperSU in the same way as flashing ZIP).
SYSTEMLESS DevBase:
1. Benefits / main features:
- Works with encypted /data partition
- Working official OTA updates! (see Tips & Tricks)
- Does NOT perform any phisical modifications in /system
- Does NOT perform any additional changes/patches to the kernel
- Removed KNOX warnings (systemlessly removed SecurityLogAgent)
- It contains SYSTEMLESS BusyBox (bionic, the most stable and respected release)
- It allows you to easily modify most of files & apps in your /system - SYSTEMLESSLY (see Tips & Tricks)
- It does not interfere with Magisk! You can use Magisk in paralell with SYSTEMLESS DevBase if you need it for your favorite module.
2. Systemless Safe De-Bloat (more info below):
What does it mean and why is it called "safe"?
- ONLY apps available in stores will be systemlessly removed from the ROM, so you can easily (re)install any of these app if you like
- ONLY pre-installed system apps are will be systemlessly removed, DevBase installer never touch any updated app nor app installed manually from store
Thus, the following conclusions can be drawn:
1. If you install my SYSTEMLESS DevBase directly over working stock ROM - in most cases almost all these apps will remain untouched, because almost all apps have been updated already (stored on /data). But then you will be able to remove any useless app using the "Application manager" -> [Name_Of_App_To_Remove] -> MORE -> Uninstall updates. NOTE: App will disappear arter reboot and will be visible even in Titanium Backup!
2. If you perform "Wipe data" directly before installing SuperSU and my SYSTEMLESS DevBase (before you let to install app's updates) - then all apps listed below will be removed. If you would like to use any of these apps - just install it manually from appropriate store. Installed manually app will not be removed during the next DevBase update or re-install.
Removed apps list (depends on the device, should cover all devices starting from Galaxy S5):
ChatON
Chrome
Drive
Dropbox
EditorsDocs
Evernote
Excel
Facebook
FB Messenger
FB Pages Manager
Flipboard
Google+ / Photos
Group Play
Hangouts
Instagram
OneDrive
OneNote
PEN.UP
Play Books
Play Games
Play Movies
Play Music
Play Newsstand
PowerPoint
Skype
Smart Remote
WhatsApp
Word
NEW! Safe De-Bloat feature automatically detects and systemlessly removes apps not listed above, but present in your CSC package
3. Systemless CscFeature MOD (enabled some built-in, hidden features):
- Added shutter sound menu in Camera app
- Sending/receiving MMS without data on
- Show SMS/MMS sending time instead of receiving
- Added "Exit Internet" option to stock browser
- Added call button in Phone Logs (**)
- Added "Call/Message block" option in Settings
- Added symbols as secondary keys in Samsung keyboard (**)
- Call Recording (manual control, added "Record" button)
(**) may not work starting from Android 7.0 Nougat
Installation:
1. FlashFire app (recommended ***):
- Open file using "Flash ZIP or OTA" option
- UNTICK "Mount /system read/write" [extremely important for working OTA!]
- Enable "EverRoot" -> "Inject SuperSU" option if necessary (see NOTE above (*))
- Tap "FLASH"
2. TWRP recovery:
- Tap "Keep Read Only" on the Welcome screen [extremely important for working OTA!]
- Open file using "Install" option (use extSdCard or OTG storage in case of encrypted /data)
- Confirm flash by swiping right
- Tap "Reboot System"
NOTE1: One additional auto-reboot may be performed at first boot. It is not a bug (may be required for systemless build.prop support - see Tips & Tricks for more explanations)
NOTE2: Do not worry about red "mount /data failed..." messages displayed in TWRP in case of encrypted /data (installer will do the work anyway!)
(***) As far as I know - FlashFire is the only flashing tool with full access to /data during flash in case of encrypted devices. It is also the only tool which allows you to perform full backup/restore of partitions, including encrypted /data. It does NOT require custom recovery to work!
Credits: @Chainfire for systemless SuperSU and a lot of inspiration
Hit Thanks button if you like my work. If you really appreciate my work - feel free to buy me a beer
Download
>> Recent SYSTEMLESS DevBase <<
Note:
Check MD5 sum BEFORE flash (useful TOOL), because flashing damaged or incomplete ZIP files can lead to issues! Correct MD5 sum is shown on the AndroidFileHost website while downloading.
Changelog
Please visit MAIN THREAD - post #3
Tips & Tricks
1. OTA updates:
- Basically, the only thing you need to take OTA update is to perform "Full unroot" in the SuperSU app. However, a better way is to use "unroot2ota" terminal command, because this will not remove DevBase boot script from /su/su.d and the only thing you will need to re-activate SYSTEMLESS DevBase (and all your systemless MODs) after performing OTA update is just re-root your device with CF-Auto-Root.
- If you flashed custom recovery like TWRP - it is mandatory to restore your stock recovery (otherwise OTA will not work). You can do it using FlashFire app (the easiest way) - just open recovery.img file (extracted from your original FW) using "Flash firmware package" option, disable "Preserve recovery" option and then tap "FLASH". EDIT: Starting from version v1.2 there is a new "unroot2ota" feature which allow you to restore stock recovery using /system/recovery-fromm-boot.p file. There is no guarantee to perform it successfully (even if there is no error message) but in most cases it works well (tested on Nougat beta). Please go to recovery before you try to get OTA to check if you have stock recovery already after performing "unroot2ota" (if not - you need to use PC Odin to flash recovery.img packed in tar file).
- It is recommended to temporarily disable "Auto-update apps" in Play Store settings before you unroot your device. It will prevent updating applications covered by Safe De-Bloat list, as there apps will temporarily appear until you re-root the phone after performing OTA update.
Note (devices which use dm-verity): You should never allow /system modifications in TWRP, never allow to remount /system r/w in any app (e.g. Root Explorer, FlashFire, etc.) and never flash a ZIP file which could modify your /system or remount it r/w. Failure to follow these recommendations will break dm-verity verification and will cause, that your device may not be able to boot with the stock kernel (you will need to re-flash your original FW using PC Odin to make your device bootable).
2. Making your own modifications:
- You can systemlessly replace any existing system app by modded one. Just put modified app to /data/devbase/system/app or /data/devbase/system/priv-app and then reboot your device
- You can systemlessly replace jar or apk in /system/framework. Just put modified one to /data/devbase/system/framework and then reboot your device (NOTE: framework support has been added for advanced users -> there is high risk of bootloop if you do something wrong!)
- You can systemlessly add or override any line in /system/build.prop. Just put (only new or changed) line to /data/devbase/system/build.prop and then reboot your device (NOTE: one additional auto-reboot will be performed if /data/devbase/system/build.prop file has been added, modified or removed. It is not a bug - it is required for the changes in /data/devbase/system/build.prop to take effect!)
- You can systemlessly replace any existing file in /system/csc and /system/etc (but NOT in subdirectories). Just put modified copy of a file to /data/devbase/system/csc or /data/devbase/system/etc and then reboot device
Limitations: original app or file MUST physically exist with the same name in /system, you can NOT add a new app or file this way!
Example 1 (Ad-Blocking): Download the latest Ad-Blocking ZIP installer from THIS thread. Extract "hosts" file (placed in /system/etc inside ZIP file), then copy it to /data/devbase/system/etc, set rw-r--r-- (644) permissions and then reboot device
Example 2 (modded SystemUI): Create "SystemUI" directory in /data/devbase/system/priv-app and then put modified "SystemUI.apk" file into it. Set rwxr-xr-x (755) permissions to "SystemUI" directory, rw-r--r-- (644) permissions to "SystemUI.apk" and then reboot device
Example 3 (De-Bloating a bit more): You can just create empty directories in /data/devbase/system/app (or priv-app) corresponding to applications in /system/app (or priv-app). Alternatively (more advanced method), you can add an app to modded enforceskippingpackages.txt file (you can find it in /data/devbase/system/etc or /data/devbase/system/csc_contents, depending on the original location in /system) and increase number in the 1st line. Second method should not be used by beginners (without a basic knowledge related to UNIX text format)
3. How to manually maintain the newest ROM version:
If you do not care about OTA - you can manually update your device to the newest ROM available @ Sammobile, keeping your original CSC (you need multi-file original FW, I mean separate files for BL/AP/CP/CSC). You need to download 2 ROMs: ROM with the newest changelist and the latest ROM containing your original CSC. Extract both and open in PC Odin BL/AP/CP files from the ROM with highest changelist but open CSC file from the ROM containing your CSC (I recommend to use HOME_CSC_* file to avoid auto-wipe-data). Flash such "mix", re-root and enjoy
Reserved
There is new version available
Changelog
v1.1:
- Added SYSTEMLESS support for /system/framework
- Added SYSTEMLESS support for /system/build.prop (overrides & additions)
- Added major Android update detection (auto-remove mods for older API to prevent bootloops & FCs)
- Added BusyBox bionic (the most stable and respected release)
- Added logging to /data/devbase/last_boot.log (API & errors)
- Added SuperSU boot patcher version checker (exits su.d boot script if < 2.76)
- Added "Please DO NOT wipe /cache" warning in case of encrypted devices and TWRP recovery
- Minor changes & optimizations in the shell code
- Added SYSTEMLESS DevBase uninstaller
Download link:
>> SYSTEMLESS_DevBase_v1.1.zip <<
Since new version has many more features -> there are more possibilities of bootloop (especially if you are playing with framework mods). I have created DevBase remover to let you get out from bootloop. Of course uninstaller does NOT "know" which mod caused the problem, so it will not remove any file from /data/devbase directory, it will remove only /su/su.d/0000000devbase boot script to make your device bootable (again) so you can manually delete problematic mod:
>> SYSTEMLESS_DevBase_remover.zip <<
Thanks master for this new job.
A little question... The CSC changes on my phone do not apply, none, but the debloat changes are OK. I checked the log in data/devbase but it is empty ... What is wrong?
Enviado desde mi SM-G920I mediante Tapatalk
Another update:
v1.3:
- Fixed CscFeature MOD (e.g. G920I case, now should work with all Samsung devices/variants)
v1.2:
- Added info in Settings/About device/Software info/Build number (can be overrided by editing /data/devbase/system/build.prop)
- unroot2ota: added ability to restore stock recovery using /system/recovery-from-boot.p file (no guarantee)
- unroot2ota: check /system partition for common modifications before unroot
- Minor changes & improvements in the shell code
>> SYSTEMLESS_DevBase_v1.3.zip <<
Deleted
_alexndr said:
Are you tired with traditional custom ROMs?
Do you miss custom ROMs but you would like to have encrypted /data (for privacy/security reasons)?
You are in the right place! I present you SYSTEMLESS DevBase - an SYSTEMLESS equivalent of my previous work (for older devices)
Click to expand...
Click to collapse
I just don't get it. What exactly is it? What is the purpose? It ain't a ROM is it?

[EOL][ROM][STABLE][O][8.0][CRC7][04.05.18][SM-G95XF/FD/N] BatMan-Rom V2.0.0

{
"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"
}
Hey guys! You may ask yourself what this rom is about and what you can expect from it, so it's basically something similar to the SuperMan-Rom on the Galaxy S7/S7 edge! It has many custom featuers, but you will find it below in the feature list :thumbup:
As you maybe know I'm a little fanboy from samsung, means I really love the stock look of the UI and the rom will always be based on most recent version from samsung, current base used is G955FXXU1CRC7 (compatible with S8 and S8+)
I wish you much fun reading through the features and while using this rom! Enjoy
So this rom should be installed by anyone loving to use a rom close to stock BUT with many mods inside aroma/rom control.
Also I'd like to make the already fast galaxy s8 even more faster as it already is! Let's see if we can reach this goal
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 V2.0.0 Oreo:
- Based on latest G955FXXU1CRC7 Nougat base
- Prerooted with SuperSU V2.82 SR5 or MagiskSU (choose in aroma)
- Magisk V16.3 (aroma selectable)
- Latest Busybox installed (aroma selectable)
- Aroma installer! with support up to 4GB zip files
- CSC features can be choosen and installed in aroma (such as Applock, Floating Message, Call recording and more!)
- Adblocker enabled or disabled (choose in aroma)
- Full rom control!! App name is BatMan Settings Free
- Fully deodexed (framework can be chosen odex/deodex in aroma)
- Rom informations and logo inside settings
- LED indicator settings
- choose IOS or stock emojis in aroma
- DM-Verity disabled
- Force encrypt disabled
- ADB fully working
- Modded SystemUI with many tweaks in the BatControl app (like header colors, qs colors and notification colors)
- 3Minit Clock/battery in romcontrol
- Custom clock positions and customizations in romcontrol
- USB Plug/Unplug disable wake up
- Remove high volume warning for headphones
- Torch on lockscreen
- Knox stuff can be choosen in aroma
- Stock CRC7 Kernel or BatStock-Kernel(choose in aroma)
- Based off from latest touchwiz source available at this moment
- Many apps are selectable in aroma debloat menu
- Selinux permissive on custom kernel
- Ram bar in recents
- Matrix animation in recents
- Sound Mod with lot improvements! (choose in aroma)
- Latest March Security Patch
- Many other features, can't list them all, please read changelog to see what changed over the time
How to install the rom:
For advanced users:
0. Make sure to have a backup somewhere on external storage
1. Make sure to be on most recent TWRP, bootloader and modem
2. Flash the rom
3. If you need VoLTE or Wifi Calling, flash your correct carrier CSC
4. Done
For normal users:
0. Boot your phone, enable OEM unlock in developer settings
1. Flash TWRP with Odin (if you don't have odin, download it here), following this thread S8/S8+ TWRP until it works correctly (to access download mode, press bixby+volume down+power on while phone is turned off) (YOU HAVE TO BE ON 3.1.1-2 TWRP OR HIGHER TO SUPPOR THIS ROM)
2. Make sure you are using most recent bootloader and modem, latest one available here on Android File Host (You should have at least an Oreo bootloader/modem installed)
3. Now boot into TWRP by pressing bixby+volume up+power on while phone is turned off
4. If TWRP asks you about allowing system to be edited, swipe yes to confirm
5. In TWRP, go to wipe, format data (a keyboard will pop up now), type "yes" (this will wipe all your data, make sure to have a backup!)
6. After this, reboot recovery and start the rom installer
7. Select your preferences in my aroma installer
8. If you selected to auto update bootloader in aroma, the installer will reboot automatically
9. You can still install my CSC selection if you are customer of a carrier which is not supported by default CSC inside the rom
10. Wait till the rom boots up
11. After setting up, open BatMan Settings Free and let the app apply my default settings!
12. Enjoy the rom!
Downloads for SM-G95XF/FD/N:
V2.0.0 Final on Android File Host
Download via our Server (you need to be signed in)
Bootloader/Modems SM-G95XF/FD/N
CSC Selection V1.2.5
Useful Links:
Our new Grifo Development website
Telegram BatMan News Channel
Telegram BatMan-Rom Chat
Telegram Dark Knight Theme
Known Bugs:
- Knox related features such as secure folder, samsung pay or samsung pass may not work any longer after rooting your phone
Credits:
- Samsung for the base
- SuperR for his awesome Kitchen
- Chainfire for his SuperSU
- topjohnwu for systemless Magisk V12
- amarullz for aroma and nkk71 to make it compatible with bigger zip files
- wubydax and daxgirl for basic RomControl
- myellow for all the great animations!
- TheFreak for his work as designer and his help with the website
- mwilky for his fingerprint after reboot mod, the colors control and other mods
- Asc1977 for a few mods I already used on SuperMan
Support:
If you enjoy this I would be really lucky if you would hit thanks :victory:
And if you really really like it, here is a donation link
​:good:
PayPal
BM Settings App on PlayStore​
XDA:DevDB Information
BatMan-Rom SM-G95XF, ROM for the Samsung Galaxy S8
Contributors
Tkkg1994
Source Code: https://gitlab.com/Tkkg1994/BatMan-Rom
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
ROM Firmware Required: Custom TWRP Recovery
Based On: Stock Based
Version Information
Status: Stable
Current Stable Version: V2.0.0
Stable Release Date: 2018-05-04
Created 2017-07-14
Last Updated 2018-05-25
Changelog:
BatMan-Rom V1.0.0
- Initial Release on XDA
BatMan-Rom V1.1.1
- Rebased on latest AQF7 release
- June security patch
- Fixed the gap in pulldown menu
- readded private mode(thanks to @mwilky for finding the right mount points for private mode! )
- added a switch in RC for immersive mode
- updated csc to AQF7
- added a switch for wake the device with the volume buttons
- fake system status to official
- removed camera mod, it didn't work anyway
- updated magisk to latest v13.1
- updated all kernels with AQF7 base
- updated supersu to v2.82 sr1
- made the rom compatible with s7/s7e edge devices
- added an option to control icon colors/progress bars etc
- added a custom music apk to be colored (thanks to @Therassaad)
- many more things, check out the rom
BatMan-Rom V1.2.0
- Rebased on latest AQGB release (I know AQH3 is out, but until samsung releases a new kernel source it normally takes a few weeks that's why this base is used for now)
- July security patch
- Added navbar icon colors @mwilky
- Added navbar to get colors from statusbar (as long as the app doesn't set a default color) @mwilky
- Added in "misc" batman settings to disable touchkey light (s7 only of course)
- Readded custom color selection for navbar in stock settings
- Removed a few camera mods which weren't working
- Updated CSC to AQGB, also added all CSC in OMX (including BTU)
- Updated all Kernels to latest source and ramdisk
- Updated SuperSU to 2.82 SR3
- Added a the S Power Planning feature (forward ported from galaxy j7 prime), choosable in aroma as a csc mod
- Updated OperaMax apk to not show as chinese apk, many people meant it's a trojan lol
- Updated adblocker host file
- Updated all included modems and bootloaders
- Added a stock kernel even for the s7, so you can choose stock there as well!
- Updated Magisk to latest V13.5 beta version
- Added modded camera into aroma @zeroprobe
- Added 100+ fonts apk into aroma
- Updated busybox to most recent version
- Updated dual speaker mod to most recent version
- Added VoLTE and wificalling into pulldown menu
- Reduced download size to 3GB only (hahahaha only 3GB )
BatMan-Rom V1.3.0
- Rebased on most recent AQH3 firmware update
- August security patch
- Added navbar height tweak @mwilky
- Added force expand notifications @thereassaad
- Updated all kernels to most recent source drop and linux version
- Updated magisk to V13.6
- Updated SuperSU to V2.82 SR3
- Added batman gif animations
- Fixed gif overlapping device informations
- Readded autostart manager in modded settings
- To disable the volume warning, there is now a switch in notification panel options to enable/disable it
- Fixed long press back not bringing up menu @mwilky )
- Removed OTA Updater. This services is outdated and not working anymore.
- Readded touchwiz double tab features! Double tap anywhere on launcher to do custom actions (the only thing which does not work yet is starting the torch light)
- Updated samsung music to most recent version with all the custom mods thanks to @thereassaad
- Fixed next alarm on lockscreen showing the wifi icon
- Fixed heads up display not working when switching in RC
- Added a new custom signal icon
- Edge lightning can now be customized! Choose a custom color OR if it should take the color from the app itself!
- Added alarm volume control to sound
- Fixed adaway app not being installed even if you selected adblocker
- Removed viper mods, since they can easy be outdated it's better to keep them outside. I hope people will go and visit the threads of the sound mods
- Updated included bootloader and modem to most recent version
- Updated csc to AQH3
- Added many new CSC mods, BUT BE AWARE, 5 SIGNAL in statusbar kills Wifi-Calling/VoLTE!
- Removed the last not working camera mod: video collage!
- Maybe some more things I already forgot, have fun!
BatMan-Rom V1.4.0
- Rebased on most recent AQI7 firmware update
- August security patch (there is no single september security patch released by samsung)
- This base fixes blueborne problems (which was samsungs main goal)
- Updated all kernels to most recent source drop and linux version (AQI7 for S8 and DQIC for S7)
- Updated magisk to V14.2
- Updated SuperSU to V2.82 SR5
- Added memory cleaner next to brightness slider
- Added listview animations thanks to @asc1977!
- Added a new telephony icon to romcontrol
- Added quickunlock thanks to @mwilky and @Grouxho
- Added Xposed V88.1 for magisk, why only magisk? Stock xposed can't be installed via an aroma script to-date, hoping rovo will change this in the future
- Updated all busybox to latest 1.27.1
- Updated adblocker
- Fixed lags in notification panel, for custom edge lightning you simply need to update the edge lightning service with samsung store!
- Fixed USB wakeup switch not working
- Updated launcher to support gestures even with latest update
- Updated included bootloader/modems for F/FD models
- Maybe some more things I already forgot again
BatMan-Rom V1.5.0
- Rebased on most recent AQK7 firmware update
- November Security patch included
- This base fixes krack problems (krack explained: Krack)
- Updated all kernels (AQK7)
- Updated Magisk to V14.5
- Updated Xposed to 88.2 (magisk version, aroma choosable)
- Updated Xposed Installer to 3.4
- Updated adblocker host file
- Updated bootloader/modem to AQK7
- Updated zeroprobes camera mod
- Stock camera does now only feature stock camera mods, for advanced camera mods please use the modded app (which includes almost all modes)
- Fix notification background image not sticking after a reboot
- Fix carrier label on pulldown overlapping with navbar
- Fix lag on pulldown, introduced by force expand notifications. THIS MOD HAS BEEN COMPLETELY KILLED
- Add qs panel number counts to romcontrol
- Removed most google apps from debloater, why: the zip file increases all the time, you can download the apps easily via playstore, also you have them installed as user apps then
- Add modded youtube to play background videos and watch videos without ads
- Add modded GBWhatsApp and GBInstagram thanks to the GB team!
- Moved some more bloatware related to Gear VR into Gear folder
- Added "edge panel" to debloat menu
- Update update-binary
- Added googles web view by default, so we don't need google chrome
- Busybox installer updated
BatMan-Rom V2.0.0 Final:
- Updated to CRC7 base (March update). I'm aware that CRD7 is out, but I already finished this base update while the other one rolled out...
- Reworked most mods from Nougat to Oreo, some are new, some I had to leave behind. You'll find out when visiting the romcontrol app
- Included an aroma choice to flash with odex or deodex framework (this is the ONLY change compared to the beta release). If you don't know anything about the odex/deodex issue, I suggest you to read up on that a bit! I talked a lot about it in here
- Updated magisk to latest 16.3 (16.4 magisk is causing issues sometimes)
- Updated included BL/CP to CRC7
- Updated modded camera
- Updated dual speaker sound mod
- Updated busybox
- Updated GBinstagram/GBwhatsapp
- Updated modded youtube
- Updated xposed to latest Oreo beta
- Updated modded samsung music app (thanks to @thereassaad )
- Updated all included kernels to CRC7 base
- Many thanks to @asc1977 and @mwilky who have helped me so much to get this update done! Without them this wouldn't have been possible with all those mods!
Useful posts and links
App on PlayStore:
Find my own BatMan app on PlayStore: BM Settings App
Odin:
Find all latest odin and samsung tools on this link: Samsung-Tools
TWRP links:
TWRP S8+ Thread
Official TWRP website for S8+
Bootloader and Modems:
SM-G955F/FD/N BL and CP (all models in one folder!)
SM-G955F/FD BL and CP
SM-G955N BL and CP
Magisk related Threads:
Magisk V13.2
Magisk Discussion
How-To create a Magisk module
Phh magiks superuser
Magisk module collection
Root related Threads:
Phh's superuser
Phh's hidesu
Phh's official apk
Phh's material APK
Stable SuperSU releases
Beta SuperSU releases
Chainfires suhide
Kernels Threads:
BatStock-Kernel
Notorious Kernel
Roms made by me:
BatMan-Rom which you are currently on its thread
BatStock-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
Thread about CSC:
Download latest CSC from CSC Selection V1.0
All CSC's ever released
How to donate:
Donate via PayPal.me
Donation via normal PayPal
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, modem and TWRP recovery. 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-G95XF/FD/N. Snapdragons are NOT supported
Q: Is this rom working on Snapdragon 835 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 (like a cloud) 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.
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 batman 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 BatMan control settings after a clean base update, why?
A: Backup for BatMan 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 BatMan 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.
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: Encryption does not work anymore on Nougat roms with TWRP installed, sorry to tell...
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: There are some test version of Xposed on N, I don't recomend to install it!
Questions about Magisk:
Q: How can I pass safetynet?
A: 1. Make sure to fully uninstall SuperSU by chainfire
2. Flash most recent BatStock Kernel
3. Flash Magisk V13.3
4. Open Magiks Manager, go to settings
5. Enable MagiskHide, systemless hosts and systemless busybox
6. Reboot the phone and check safetynet!
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: What to do when I can't login to snapchat?
A: Clean install the rom without root and login to your snapchat, save the app with titanium backup, flash back 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.
Questions about Kernels:
Q: I want to switch kernel, how?
A: We have systemless 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: 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.
Hey guys, this isn't anything new, I just moved the BatMan thread into the criss cross development section as it's way more active in here :fingers-crossed: :good:
How can i delete these green android icons? Delete not make them invisible
Gesendet von meinem SM-G950F mit Tapatalk
Hi
Animated scale for french langage is possible To 0,25 ?
Thanks
what about s8 forum i find here only s8+
Sent from my SM-G950F using XDA-Developers Legacy app
spackeddie01 said:
How can i delete these green android icons? Delete not make them invisible
Gesendet von meinem SM-G950F mit Tapatalk
Click to expand...
Click to collapse
Are you using a custom launcher? I assume it's due to this one!
ounerkouks said:
Hi
Animated scale for french langage is possible To 0,25 ?
Thanks
Click to expand...
Click to collapse
English, spanish, german, french and dutch should it be if I'm correct
sielhadi said:
what about s8 forum i find here only s8+
Sent from my SM-G950F using XDA-Developers Legacy app
Click to expand...
Click to collapse
Look at the thread title, it says G95XF, which means G950F and G955F. I moved all my threads into s8/s8+ combined ones
i bought the super setting pro does it adequate with bat setting pro when it will be released
Sent from my SM-G950F using XDA-Developers Legacy app
Hello !
Any way to install App Lock manually ? I reflashed your Rom and selected App Lock in CSC but can't find it...
---------- Post added at 02:30 AM ---------- Previous post was at 02:30 AM ----------
Hello !
Any way to install App Lock manually ? I reflashed your Rom and selected App Lock in CSC but can't find it...
Hi,
Its my first root experience with the s8.
I love the rom.
However, I am unable to control the bixby button. I try to modify it behavior with bxActions or similar but nothing happens.
Is it depend on some of the Samsung apps? If so, which one (or is it possible to just have it working)
Sent from my SM-G950F using Tapatalk
Hi folks, i flashed Dolby atmos in aroma, but if i try to open the app, the process stop working. Viper works fine. Is there a fix?
Sent from my SM-G950F using XDA-Developers Legacy app
tiesto14 said:
Hello !
Any way to install App Lock manually ? I reflashed your Rom and selected App Lock in CSC but can't find it...
---------- Post added at 02:30 AM ---------- Previous post was at 02:30 AM ----------
Hello !
Any way to install App Lock manually ? I reflashed your Rom and selected App Lock in CSC but can't find it...
Click to expand...
Click to collapse
you can find it in advanced settings
Palm Swipe to Capture not working!
Hi there!
I am currently running BatMan-ROM V1.1.1 and kernel version (4.4.13), I'm not sure if that's your kernel or the stock one because I don't remember the aroma choice I made.
I have tried disabling and re-enabling all the advanced features but palm swipe to capture screen still won't work. Any idea as to why that is happening? It's not a big deal but I find that feature useful sometimes, however if it's a hassle I can certainly live without it.
Thanks a lot, Tkkg!
hi, This icon from statusbar would be nice changed with AOSP style.
So recently did a clean install for V1.1.1 since I first did a dirty flash and I noticed my battery draining quicker then it did before. But even with the clean install it does the same.
In both causes AOD is on and I turn the phone screen downwards so it isn't always on and it seems that Android OS and Device idle are always staying awake. Where it went from using 3% battery at night (screen downwards) it went to 10% (screen downwards).
Currently I am on 62% over 15 hours of not using my phone and screen downwards. Where before I only reached that point when I would play PoGo a hour at the end of the day.
Anyone else having those issues?
tiesto14 said:
Hello !
Any way to install App Lock manually ? I reflashed your Rom and selected App Lock in CSC but can't find it...
---------- Post added at 02:30 AM ---------- Previous post was at 02:30 AM ----------
Hello !
Any way to install App Lock manually ? I reflashed your Rom and selected App Lock in CSC but can't find it...
Click to expand...
Click to collapse
If you selected it in aroma and didn't install any other csc after the rom flash it is in advanced featurs
eranyanay said:
Hi,
Its my first root experience with the s8.
I love the rom.
However, I am unable to control the bixby button. I try to modify it behavior with bxActions or similar but nothing happens.
Is it depend on some of the Samsung apps? If so, which one (or is it possible to just have it working)
Sent from my SM-G950F using Tapatalk
Click to expand...
Click to collapse
If you removed the bixby apks you can't control it anymore
Koehlix said:
Hi folks, i flashed Dolby atmos in aroma, but if i try to open the app, the process stop working. Viper works fine. Is there a fix?
Sent from my SM-G950F using XDA-Developers Legacy app
Click to expand...
Click to collapse
I suggest you to post your issues at the dolby atmos thread, as I'm not the author of that mod
TarekElsakka said:
Hi there!
I am currently running BatMan-ROM V1.1.1 and kernel version (4.4.13), I'm not sure if that's your kernel or the stock one because I don't remember the aroma choice I made.
I have tried disabling and re-enabling all the advanced features but palm swipe to capture screen still won't work. Any idea as to why that is happening? It's not a big deal but I find that feature useful sometimes, however if it's a hassle I can certainly live without it.
Thanks a lot, Tkkg!
Click to expand...
Click to collapse
That kernel version you mention is the stock kernel.
That feature definitly works. Tested just now. But you really need to start at the edge of the screen. If you just swipe over it it won't do anything.
I had to start swiping at the very beginning of the edge screen
Borfas said:
hi, This icon from statusbar would be nice changed with AOSP style.
View attachment 4212340
Click to expand...
Click to collapse
I see, don't know if that's so easy doable
RDDraco said:
So recently did a clean install for V1.1.1 since I first did a dirty flash and I noticed my battery draining quicker then it did before. But even with the clean install it does the same.
In both causes AOD is on and I turn the phone screen downwards so it isn't always on and it seems that Android OS and Device idle are always staying awake. Where it went from using 3% battery at night (screen downwards) it went to 10% (screen downwards).
Currently I am on 62% over 15 hours of not using my phone and screen downwards. Where before I only reached that point when I would play PoGo a hour at the end of the day.
Anyone else having those issues?
Click to expand...
Click to collapse
If you just made a clean install, simply wait for a few days. Your phone is currently analyzing your usage and indexing the data and files you got on the sd and internal storage.
Also it you don't use the phone during the night, enable flight mode in order to get better battery (as it doesn't need to be connected all the time, maybe with bad receiption)
Sent from my BatMan powered SM-G955F
I suggest for clear sound and high volume: am3d (Download and install from magiks) and the original player in the app samsung store, now
enjoy with soundalive.... end edgelightning effect.
Installed it, everything is pretty much fine.
Only thing is V4A is not working i did a clean install, did the magisk update that works with it in the aroma installer, but when i turn it on nothing happens on my headset. Aswell on speaker.
Btw, the ''better camera quality'' mod is that zero's mod or should i still patch zeros mod on it?

MTCB/MTCC rk3188 (5.1.1) Firmware with an xposed set of MTC apps

Based on latest LOLLIPOP with MICRO GAPS and OPEN GAPS 1024 x 600 and 800 x 480 from @dsa8310.
Sharing with you my custom modified rom with LP image.
UPDATE 29.8.2017:
MicroG version: 1024 x 600 and 800 x 480
- added screen saver with speed, clock and apps shortcut ported from well known developer @Malaysk (null null still present)
(if someone need: screen saver in the attachement - replace with root explorer: system - app - mtcscreenclock
MTCScreenClock (round)
- 1024 x 600 resolutions has different radio and bluetooth apk
- included all xposed modules and fast google maps
- remember to enable all xposed modules and copy folder contents to external gps card!!!
Enjoy
UPDATE: 3.9.2017 LINKS UP 2019
microGaps version:
Lite 1024x600 microG version.
openGaps version:
Lite 1024 x 600 openG version.
Lite 800 x 480 openG version.
___________________________________________________________________________________
- LITE version of system
- added xposed status bar module for remove status bar items (copy mtc-status bar to external GPS Card)
- new screen saver without null null text (if doesn't show install it manually from: system/app/mtcscreensaver)
- removed all the bloatware callendar, calculator etc...
- added a lot of tweaks to speed the units with 1gb ram
- added new car launcher AG (trial) for me the best - full version 1€
- new xposed mtc manager 2.5 module
LITE VERSION OPTIMIZATIONS:
- kernel tweaks (changed parameters of dalvik vm etc,...)
- better ram management
- faster scrolling
- faster boot
- better responsiveness
- increased performance and app ram management
- better video acceleration
- disable sending android logging stuff
- force gpu&cpu rendering
System now uses less than 470 Mb of ram
BEFORE YOU START:
1. With disable service app find google play store and disable the first 5 services from top including DailyHygiene.
2. Login to MicroG
3. In microG settings enable google device registration
4. Clear data on Google playstore or clear from recents
5. Enjoy fast 5.1.11. playstore (if not showing paid apps just restart HU)
MTCB MCU USERS
- DSA's mtcxp xposed module has to be enabled before the status bar will show.
PREINSTALLED APPS and MODULES:
All these apps and xposed modules are preinstalled and you just have to activate xposed modules you need:
- disable_service
- google-maps-9.2 (you can update it just install as normal apk)
- mtcservice-2.60
- mtcsound-2.0.5 (remove from xposed if you don't have sound mod for better performance)
- mtcxp-1.0
- quickreboot
- RootExplorer
- Titanium_Backup
- xposed-disablefullscreenkeyboard
- xposed-mtc-bt-2.3
- xposed-mtc-keys-5.2 (custom keys for harware buttons)
- xposed-mtc-manager-2.5 (mode button mod and no closing apps when starting the car, etc.)
- xposed-mtc-music-2.8
- xposed-mtc-poweramp-1.4 (working media keys and stopping power amp when mtc app is started)
- xposed-mtc-radio-1.11
- xposed-VolumeBar (replaces original volume bar)
- 7th floor sound mod preinstalled and working
OTHER ADDITIONS: (included in download to copy on external SD (GPS card)
There is also file to copy on SD card (GPS card) that has features for MTCManager:
- hardware mode button can be configured (included in download) as well to switch between apps and auto play them (radio, poweramp, music, pcradio etc)
- mtc screen clock
- mtc status bar
DISABLING THE SCREEN SAVER OR CHANGING TIME:
Edit on external SD/ GPS-Card : Mtc.Manager/settings.ini
# the inclusion of an alternative screen saver, when you specify false will work full-time mechanism:
screenClock=false or true to activate
# Time off the screen if you do not set out full-time settings will be used in sec:
screenTimeout=300
# The name of the screensaver program package
screenPackage=com.microntek.screenclock
# Name Activiti screensaver
screenClass=MainActivity
# If the name of the package and Activiti is not specified, it will use a standard screensaver
MTC MANAGER CAPABILITIES:
capabilities
All configuration files must be on the external map in the mtc-manager directory.
1. The module carries the functionality of xposed-mcu , which does not allow the radio to go to sleep during the scrolling of the starter.
- when receiving a signal to turn off the module delays for 5 seconds, if at that moment the power reappears, nothing happens, in the absence of power, the radio recovers into sleep.
Due to the features of the implementation of the inclusion in our MCU, the screen goes out for the time of voltage failure.
This functionality can be disabled in settings.ini:
Settings.ini
Mcu_power = false
2. The module has a white list of applications that does not allow the system to close necessary services and applications when going to sleep and when pressing the "Acceleration" button in the blind. Thus, the module allows to refuse from using mtc-wakeup-service .
Filename with exceptions whitelist.ini
The file name of the white list application packages must be listed.
#
example
3. Accelerated start of user services. The services are started when the system kernel is loaded.
The list of services should be on the external map in the mtc-manager directory, the file name start_services.ini
each line should contain the service name in the format package name / full service name,
#
example
4. An alternative screensaver with a list of exceptions, running in any (even a non-standard application). The standard screen saver mechanism is activated.
It may not work on all firmware.
Settings in the settings.ini file.
Settings.ini
# Inclusion of an alternative screensaver, if false, the standard mechanism will work:
screenClock = true
# screen off time, if not specified, the value from the
default settings will be used: screenTimeout = 60
# screen saver program name
screenPackage = com.microntek.screenclock
# screen saver activation name
ScreenClass = MainActivity
# if the package name and activations are not specified, then the standard screensaver will be used
The exception list is located in the ss_exceptions.ini file - the package names must be listed, for example:
Ss_exceptions.ini
com.microntek.music
ru.yandex.yandexmaps
Also the screensaver will not start when talking on the phone, the rear view camera, navigation and turning off the radio.
If instead of a beautiful clock MTCSreenClock.apk a screensaver with a standard digital clock on a black background is called, you need to make sure that the MTCScreenClock application is installed.
If the application is installed, you can try setting screenPackage and screenClass parameters in settings.ini
5. Also in the module there is a "backup" for correct sound adjustment in MTC-Volume and MTC-Service .
#
The adjustment of sound in firmware on Android 4.4.4
6. Re-designation of OBD-device bluetooth.
Device names must be listed in the settings.ini file in obd_device parameter, separated by commas, in the form in which they are visible in the standard hands-free application. You can specify not names, but parts of names, for example:
Settings.ini
Obd_device = OBD, DUAL-SPP
7. Set the list of programs that are switched by the MODE button,
In settings.ini, set
Settings.ini
ModeSwitch = true
Programs are switched sequentially one after the other.
For correct sound switching, the applications used must be managed (play / pause) programmatically via intents. If the player does not support the start and stop playback of external intents, then you have to manually switch the sound.
When you click on the MODE button, the active application is searched for in the running list. Next, the application is sent a command (configurable in mode.ini) to close or pause the audio stream. After that, the default activation for the next application is launched and the application is sent a command to start playback (also configured in mode.ini)
#
Mode.ini
8. Disable the launch of the last running program.
Settings.ini
Clear_last_app = true
9. GPS time synchronization.
Settings.ini
Sync_gps_time = true
10. Turn on w-fi at startup.
Settings.ini
Wifi.on = true
Paypal:
https://paypal.me/johnydj?locale.x=en_US
Hello,
Please help me a little, it was a more than one year since I updated my fw.
How do I update to this firmware, I forgot the procedure?
Is it clean install, all apps/data are going to be wiped and must be installed again?
Is there a way to backup current firmware/apps, like twrp image or something (in case something goes wrong)?
Thank you
grgart said:
Hello,
Please help me a little, it was a more than one year since I updated my fw.
How do I update to this firmware, I forgot the procedure?
Is it clean install, all apps/data are going to be wiped and must be installed again?
Is there a way to backup current firmware/apps, like twrp image or something (in case something goes wrong)?
Thank you
Click to expand...
Click to collapse
Backup with titanium backup all your apps you want.
wipe data/factory reset from recovery, then flash the image with clear all
With titanium backup restore your apps back, thats it.
hi johnny,
would like to check if u manage to solve these issues of
1. xposed volume bar in the center of screen instead of bottom
2. misaligned apps buttons in mtcbluetooth mtcwheelstudy etc.
thank you in advance
jun81 said:
hi johnny,
would like to check if u manage to solve these issues of
1. xposed volume bar in the center of screen instead of bottom
2. misaligned apps buttons in mtcbluetooth mtcwheelstudy etc.
thank you in advance
Click to expand...
Click to collapse
1. Did you activate xposed mtc manager module in xposed app ?
2. Can you post picture, I didn't experienced this issue on my unit using the same image...
3. Please note this is 1024 x 600 resolution image...flashing on 800 x 480 can couse this issues you have...
Will post pic once I get a chance. Had no problem with gui using the dsa's last dec 5.1.1 rom.
jun81 said:
Will post pic once I get a chance. Had no problem with gui using the dsa's last dec 5.1.1 rom.
Click to expand...
Click to collapse
I added screen saver in latest version. But still don't know why you have problems with resolution. I can upload stock apps and you can try if there is also problem or not...
What are the performance benefits from the dsa8310 rom on a 1gb ram headunit?
I'm currently running dsa8310 latest 5.1.1. on my 1gb headunit. What sort of advantages will I see if I flash to your rom?
iselfdevi said:
What are the performance benefits from the dsa8310 rom on a 1gb ram headunit?
I'm currently running dsa8310 latest 5.1.1. on my 1gb headunit. What sort of advantages will I see if I flash to your rom?
Click to expand...
Click to collapse
Hard to say without knowing the exact version of his ROM youre running currently, but generally its a good idea to update the software as it is on any computer/smartphone/tablet. You shouldnt have to wipe data if youre already using it.
Read the thread to see the improvements that have been made recently - he lists them all.
Waiting for the 800 x 480 version !
champikasam said:
Waiting for the 800 x 480 version !
Click to expand...
Click to collapse
Done, check it out
Johny DJ said:
Done, check it out
Click to expand...
Click to collapse
Awesome ! Will check and let you know
---------- Post added at 04:39 PM ---------- Previous post was at 04:06 PM ----------
Johny DJ said:
Done, check it out
Click to expand...
Click to collapse
Could you check whether 800 x 480 img file is properly formatted ? I'm unable to mount or extract it. Getting an error saying the img file is corrupted. Will try to download again and try.
champikasam said:
Awesome ! Will check and let you know
---------- Post added at 04:39 PM ---------- Previous post was at 04:06 PM ----------
Could you check whether 800 x 480 img file is properly formatted ? I'm unable to mount or extract it. Getting an error saying the img file is corrupted. Will try to download again and try.
Click to expand...
Click to collapse
Full dropbox, check again...
Johny DJ said:
Full dropbox, check again...
Click to expand...
Click to collapse
Downloaded again. Same error
champikasam said:
Downloaded again. Same error
Click to expand...
Click to collapse
I extracted microg_preinstalled_800x480LP5.1.1rk3188.MTCB-C(20.8.2017) without problems ??
Try to rename it to some short name: update or something...
New link .rar
https://www.dropbox.com/s/95j1iqvqv...0x480LP5.1.1rk3188.MTCB-C(20.8.2017).rar?dl=0
Johny DJ said:
I extracted microg_preinstalled_800x480LP5.1.1rk3188.MTCB-C(20.8.2017) without problems ??
Try to rename it to some short name: update or something...
New link .rar
https://www.dropbox.com/s/95j1iqvqv...0x480LP5.1.1rk3188.MTCB-C(20.8.2017).rar?dl=0
Click to expand...
Click to collapse
Thanks ! i was able to download using the rar file. Most of the functions are working great ! It's fast and responsive. Please check on the following:
1) I'm unable to see the task bar/notification drawer at the top. I'm on the default launcher. Do i need to enable it anywhere ? Check the photos below:
https://ibb.co/hiJM1k
https://ibb.co/f24GZ5
2) I couldn't find google maps installed by default. So i installed the latest version from the play store. Its working fine (fast and responsive), but it doesn't show up in the selection list when i press the navi button on the player (to set it as the default navigation app). I only see the following nav apps in the list:
https://ibb.co/gG4YE5
Thanks !
champikasam said:
Thanks ! i was able to download using the rar file. Most of the functions are working great ! It's fast and responsive. Please check on the following:
1) I'm unable to see the task bar/notification drawer at the top. I'm on the default launcher. Do i need to enable it anywhere ? Check the photos below:
https://ibb.co/hiJM1k
https://ibb.co/f24GZ5
2) I couldn't find google maps installed by default. So i installed the latest version from the play store. Its working fine (fast and responsive), but it doesn't show up in the selection list when i press the navi button on the player (to set it as the default navigation app). I only see the following nav apps in the list:
https://ibb.co/gG4YE5
Thanks !
Click to expand...
Click to collapse
1. Hm...really don't know what happend to statusbar... try to disable / untick all xposed modules and reboot to see if some of xposed modules is cousing problems... I hope you did wipe all data / factory reset and then clear all and install from usb/sd and after that you can try wipe all data again and reboot, but everything should work because it's the same image from dsa's just added all the xposed modules...,
2. Yes, I forgot it, I updated image again and here: just copy folder in the rar with root explorer to system/app and change permisions just Maps.apk to r-r-w (664) reboot.
Try just to find your launcher in the android settings - apps and clear data.
Maps: https://www.dropbox.com/s/m44hv1189is36fr/Maps.rar?dl=0
Hello !
First I have to thank you @Johny DJ for this beautiful firmware. It's faster than i ever had on my MTCC-KLD6-V2.97 1024*600.
Also I take this opportunity to thank @dsa8310 and @Malaysk for their brilliant work in this adventure.
I love you guys, all as you are.
This said, i have a question : What's the difference between the first firmware (released 14/08 i think) that works really good on my unit RK 3188 (1024*600) and the release of today ?
Also my only "problem" is the text "null null" (like here : https://ibb.co/dL3dU5) on the screensaver which i think it correspond normally to the weather in Malaysk's rom. So i tried to install the weather app provided by Malaysk called "MTCWeather.apk" but it does not work. I have to precise that the display of the speed works OK.
Does this new release correct this little issue ?
Again thanks for all and have a nice day.
Cheers !
airlink75 said:
Hello !
First I have to thank you @Johny DJ for this beautiful firmware. It's faster than i ever had on my MTCC-KLD6-V2.97 1024*600.
Also I take this opportunity to thank @dsa8310 and @Malaysk for their brilliant work in this adventure.
I love you guys, all as you are.
This said, i have a question : What's the difference between the first firmware (released 14/08 i think) that works really good on my unit RK 3188 (1024*600) and the release of today ?
Also my only "problem" is the text "null null" (like here : https://ibb.co/dL3dU5) on the screensaver which i think it correspond normally to the weather in Malaysk's rom. So i tried to install the weather app provided by Malaysk called "MTCWeather.apk" but it does not work. I have to precise that the display of the speed works OK.
Does this new release correct this little issue ?
Again thanks for all and have a nice day.
Cheers !
Click to expand...
Click to collapse
Thank you!
There is no so much difference, just added new screen clock, but there will be still null null. It won't work because it's settings are part of android settings from Malaysk.
You should try lockclock apk (its related to weather app)
If you find a solution I can update system image to get weather fully working, but I was not bothering with that, because then system will also use more ram etc...I will try to remove the null null item...
here are the apps you can try:
https://www.dropbox.com/s/sukxg16l2z4ygbr/apps.rar?dl=0
Johny DJ said:
Thank you!
There is no so much difference, just added new screen clock, but there will be still null null. It won't work because it's settings are part of android settings from Malaysk.
You should try lockclock apk (its related to weather app)
If you find a solution I can update system image to get weather fully working, but I was not bothering with that, because then system will also use more ram etc...I will try to remove the null null item...
here are the apps you can try:
https://www.dropbox.com/s/sukxg16l2z4ygbr/apps.rar?dl=0
Click to expand...
Click to collapse
@Hal9k_'s MTCD ROM has a screen lock, I asked him how he did it and he said he just added back the original Android code.
EDIT : Lol, stupid me you said "lockclock" not screen lock ! Doh !

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

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 N960FXXUxxxxx_DevBase.zip META-INF options.prop ALEXNDR
It seems that misunderstanding of the above problem is the main reason why many devs give up and do not use my base as a pattern.
Hello
I have decided to create a pure base with my unified installer (should work with many other Samsung devices), which can be a pattern for ROM Chefs (not only for beginners) ROM is initially safe de-bloated (read below what does it exactly mean), but all features are present and works!
ROM can be installed by normal users as well. If you like a little de-bloated ROMs, clean, but with all working features - there is no better alternative I think
ROM for N960F/DS contains OXM multi CSC package, list of available CSCs is as follow:
ACR, AFG, AFR, ATO, AUT, BGL, BNG, BRI, BTC, BTU, CAC, CAM, CPW, DBT, DKR, ECT, EGY, EUR, GLB, ILO, INS, ITV, KSA, LAO, LUX, LYS, MAT, MID, MM1, MTL, MWD, MYM, NEE, NPL, NZC, OPS, ORX, PAN, PAK, PHE, PHN, PNG, PRO, ROM, SEB, SEE, SEK, SIN, SKZ, SLK, SMA, SMP, STH, TEB, TEL, THL, THR, TMC, TNZ, TPH, TUN, TUR, VAU, VFJ, VNZ, WTL, XEF, XEH, XEO, XEU, XEZ, XFA, XFE, XID, XME, XNX, XNZ, XSA, XSG, XSP, XTC, XXV, XNF
ROM for N960N contains OKR multi CSC package, list of available CSCs is as follow: KOO, KTC, LUC, SKC
NEW !!! I present you new, unique option: "Keep current CSC", so you can install my DevBase keeping your original CSC even if it is not listed above! Note that in such case this option has some limitations - more informations you can find in related older threads, e.g. HERE
ALEXNDR.N960FXXSAFWB3:
1. Base:
- Odexed (original stock files) + stock kernel
- Multi CSC OXM (list of natively supported CSC as above) (*)
- Removed KNOX related content (useless on rooted phones)
- Removed Rlc.apk & vaultkeeperd (to avoid "OEM unlock issue")
- Rooted systemlessly (Magisk v23.0) (*)
- All original features are present and works (except KNOX related apps)
- Added "App Lock" feature (Settings -> Advanced features)
- No visual changes (100% stock look)
2. CscFeature MOD (enabled some built-in, hidden features):
- Added shutter sound menu in Camera app
- Sending/receiving MMS without data on
- Show SMS/MMS sending time instead of receiving
- Added "Call/Message block" option in Settings
- Added "Show network speed" toggle (Settings -> Display -> Status bar)
- Added "LTE Only" network mode (NOTE: voice calls may not work in this mode)
- 4G/3G network support in any CSC (master/slave SIM, applies to dual SIM variants)
- Call Recording (via "Record" button or "Auto record calls" option)
- Enabled "Recent App Protection" feature
3. Xposed framework & Xposed Installer app [optional] (*)
- NOTE: Applies to Oreo DevBase. There is no Xposed for Pie yet
4. Virtual / physical Safe De-Bloat (more info below) (*)
What does it mean and why is it called "safe"?
- ONLY apps available in stores are removed / skipped in DevBase, so you can easy (re)install any of these app if you like
- ONLY pre-installed system apps are removed / skipped, DevBase installer will never touch any updated app nor app installed manually from a store
- By default virtual Safe De-Bloat is applied with exact same effect as physical (completely skips apps at boot). You can force to delete apps physically but it is recommended only if you really need more space in /system
Thus, the following conclusions can be drawn:
1. If you install my DevBase directly over stock ROM without performing "Wipe data" - in most cases almost all these apps will remain untouched, because almost all apps have been updated already (stored on /data). But then you will be able to remove any useless app using the "Application manager", like any other app. Removed manually app will not appear again until you use my DevBase while updating.
2. If you perform "Wipe data" while installing my DevBase - then all apps listed below will be removed. If you would like to use any of these apps - just install it manually from appropriate store. Installed manually app will not be removed during the next DevBase update.
Removed / skipped apps list:
Excel
Facebook
LinkedIn
OneDrive
PowerPoint
Word
(*) - these options can be controlled by editing options.prop file (you can find such file in ZIP's root directory). Just place modified options.prop file (use e.g. Notepad++ to edit) in the root directory of internal emulated scdard (/data/media/0) or extSdCard (recommended if you plan to format internal emulated sdcard) and then start the installation. More info below:
#
# DevBase by ALEXNDR (_alexndr @ XDA)
#
# Configuration file to allow customize the installation.
#
# File inside the ZIP installer is just for reference - please DO NOT modify it!
# If you want to change some options listed below - edit the copy of this file, then place
# modified options.prop file in the root directory of internal emulated scdard (/data/media/0)
# or in the root directory of extSdCard (recommended if you plan to format internal emulated
# sdcard) and then start the installation.
#
# TIP: You do not need to repeat this step every next update I will release. As long as your
# customized options.prop file is present in the (ext)SdCard - future DevBase installers will
# "read in your mind" that you want to install with such options again.
#
# NOTE: All below variables and values are case sensitive!
# Enable root access. Allowed values:
# true - install Magisk as root solution (default)
# false - do not root device
root=true
# Install Xposed framework matched to the ROM (there is also a possibility to detect Xposed profile
# automatically, but auto-detection will not work if user will perform wipe /system). Allowed values:
# auto - detect Xposed profile automatically
# true - force Xposed framework installation
# false - do not install Xposed framework
xposed=auto
# CSC Selection. Allowed values:
# KCSC - Keep current CSC, recommended in most cases (automatic selection or keep current CSC contents).
# You can force the use of natively supported CSC by typing (use UPPERCASE!): ACR, AFG, AFR, ATO, AUT, BGL,
# BNG, BRI, BTC, BTU, CAC, CAM, CPW, DBT, DKR, ECT, EGY, EUR, GLB, ILO, INS, ITV, KSA, LAO, LUX, LYS, MAT,
# MID, MM1, MTL, MWD, MYM, NEE, NPL, NZC, OPS, ORX, PAN, PAK, PHE, PHN, PNG, PRO, ROM, SEB, SEE, SEK, SIN,
# SKZ, SLK, SMA, SMP, STH, TEB, TEL, THL, THR, TMC, TNZ, TPH, TUN, TUR, VAU, VFJ, VNZ, WTL, XEF, XEH, XEO,
# XEU, XEZ, XFA, XFE, XME, XNX, XNZ, XSA, XSG, XSP, XTC, XXV, XNF
CSC=KCSC
# Custom CSC Features. Allowed value in each line: <Example_line>value</Example_line>
<CscFeature_Common_SupportWcdmaInSlave>true</CscFeature_Common_SupportWcdmaInSlave>
<CscFeature_VoiceCall_ConfigRecording>RecordingAllowed</CscFeature_VoiceCall_ConfigRecording>
<CscFeature_Setting_EnableMenuBlockCallMsg>true</CscFeature_Setting_EnableMenuBlockCallMsg>
<CscFeature_Setting_CustNetworkSelMenu4>LTEONLY</CscFeature_Setting_CustNetworkSelMenu4>
<CscFeature_Setting_SupportRealTimeNetworkSpeed>true</CscFeature_Setting_SupportRealTimeNetworkSpeed>
<CscFeature_SmartManager_ConfigSubFeatures>roguepopup|autoclean|autorestart|applock|trafficmanager</CscFeature_SmartManager_ConfigSubFeatures>
<CscFeature_SmartManager_DisableAntiMalware>true</CscFeature_SmartManager_DisableAntiMalware>
<CscFeature_SystemUI_SupportRecentAppProtection>true</CscFeature_SystemUI_SupportRecentAppProtection>
<CscFeature_Message_DisplaySmsTimeAs>server</CscFeature_Message_DisplaySmsTimeAs>
<CscFeature_Message_DisplayMmsTimeAs>server</CscFeature_Message_DisplayMmsTimeAs>
<CscFeature_Camera_ShutterSoundMenu>true</CscFeature_Camera_ShutterSoundMenu>
<CscFeature_RIL_ForceConnectMMS>true</CscFeature_RIL_ForceConnectMMS>
# Custom physical debloat list. Allowed value in each line: path to app's directory in /system.
# (NOTE: wildcards are allowed here)
/system/*app/SamsungPass*
/system/*app/SamsungPay*
/system/*app/SecureFolder*
/system/app/SecurityLogAgent
/system/priv-app/Fast
/system/priv-app/Rlc
# Custom virtual debloat list. Allowed value in each line: exact app name with .apk extension.
# (NOTE: without app's path/directory, wildcards are NOT allowed here!)
Excel_SamsungStub.apk
Facebook_stub.apk
FBAppManager_NS.apk
FBInstaller_NS.apk
FBServices.apk
FotaAgent.apk
LinkedIn_SamsungStub.apk
OneDrive_Samsung_v3.apk
PowerPoint_SamsungStub.apk
Word_SamsungStub.apk
NEW !!! Starting from DevBase v3.0 there is a new customization method - you can change frequently switched root options or encrypt your device just by renaming installer's ZIP file name (instead of editing options.prop file). Currently supported "strings" in the file name: "noroot", "encrypt", "rescue", "xposed", "CSC_xxxx.zip":
Case 1 (default) - install the ROM with Magisk & MagiskSU as root solution
(just flash ZIP file "as it is")
Case 2 - do not root device
(place "noroot" string anywhere in the ZIP file name, e.g. "N960Fxxx_DevBase_v6.x_noroot.zip")
Regardless of the above root options, starting from DevBase v4.4+, you can also use "encrypt" option (place "encrypt" string anywhere in the ZIP file name, e.g. "N960Fxxx_DevBase_v6.x_encrypt.zip"). All your data will be encrypted "on-the-fly" at next boot after ROM update/reinstall. Wipe data is NOT necessary to use this option. You will NOT lose your data & apps but it is extremely important - do not interrupt encryption process during this "special" boot! Booting can take much longer and you may think it is a bootloop, but it isn't! If you have a large amount of used data - it is recommended to connect your phone to the charger during boot (and open a beer to avoid heart attack while waiting). You do not need to use "encrypt" option again in case of another DevBase update(s) - please read carefully notes below.
In DevBase ROM v4.5+ there is a "rescue" option, which may be especially helpful in case of encrypted device if you experienced bootloop caused by e.g. systemless mod/module/xposed stored on /data (without access to /data from TWRP). In case of bootloop just place "rescue" string anywhere in the ZIP file name, e.g. "N960Fxxx_DevBase_v6.x_rescue.zip" and then (re)install the ROM - should help in case of (probably) all possible bootloop reasons. In addition to the normal (re)installation of the ROM (thus restoring the original /system, kernel, modem, etc.) this option will also force "Core Only Mode" in Magisk and will move all SYSTEMLESS DevBase modifications to /data/devbase/system/.backup, before performing bind mounts, so original files will be used.
In DevBase ROM v4.6+ there is a possibility to force CSC by renaming ZIP file name - this is the only case-sensitive variable which have to be put at the beginning of ZIP file name and must be folloed by "_" (due to the fact that there is a high risk that ZIP file name may contain CSC code accidentally). Example (to force CSC DBT): "DBT_N960Fxxx_DevBase_v6.x.zip"
In DevBase ROM v5.6+ there is "xposed" option which allows you to force Xposed framework installation. It is NOT forced by default - you need to force it manually while installing ROM with Xposed first time, renaming ZIP's file name to e.g. "N960Fxxx_DevBase_v6.x_xposed.zip". Next ROM's updates will detect and apply Xposed profile automatically, unless you wipe /system - then auto detection is not possible.
Notes related to encrypted devices:
How to confirm that your data are encrypted:
1. Go to TWRP and check if it is possible to mount /data. If NOT - all is ok "Failed to mount '/data' (invalid argument)" will be the a frequent message that you need to like in the future
How to update DevBase ROM to a newer version:
1. Copy a newer DevBase ROM to extSdCard or OTG storage (you do NOT need to use "encrypt" option in ZIP file name again, if your device is encrypted already - it just remain encypted)
2. Go to TWRP -> "Install" and flash ZIP file from extSdCard or OTG
3. That's all
The risk of data loss in case of encrypted devices, depending on the ROM scenario:
1. DevBase only: VERY LOW RISK (*)
2. Coming from other custom ROM with encrypted data - MEDIUM RISK (recommended backup)
3. Installing other custom ROM over DevBase - MEDIUM RISK (recommended backup, anyway)
4. Installing pure stock (using Odin) over DevBase (or over any other custom ROM) - VERY HIGH RISK (not recommended!)
(*) There is still a risk to get into a bootloop if you install stuffs like: Xposed framework, incompatible Magisk or Xposed module, incompatible systemless MOD in /data/devbase/system, etc. In case of bootloop just try to use "rescue" option described above
EDIT (Dec-01-2019): Very important info!!! Encryption will not be possible if you format /data using new TWRP (3.3.x-x). If you prefer encrypted device - it is highly recommended to use TWRP 3.2.3-x to format /data. If you are not sure which version you have used to format data - it is much better to perform clean install using TWRP 3.2.3-x to format /data before forcing encryption. More info HERE
Notes related to EFS backup:
During install, my ROM's installer always performs EFS backup to {storage}/.backup/efs (where {storage} may be /external_sd, /usb-otg, /sdcard - in the preferred order). It is recommended to copy EFS backup occasionally outside the phone and store in safe location (PC, OTG, etc). There are 2 backups - when you first time installed my ROM (efs_backup.tar.gz) and recent, created additionally, just in case (efs_recent.tar.gz). Most useful will be most probably the first one (efs_backup).
You probably will never need these files, but sometimes s**t happens and restoring EFS backup may be the only one way to rescue your device!
When do I need to restore EFS backup?
- lost/invalid IMEI number
- proper IMEI but unable to connect to the network
- connected to the network but unable to make a call and/or transfer data
- unrecoverable bootloop (even after clean DevBase install with default settings)
NOTE: In contrast to many other custom ROMs - my installer uses gzip compression (*.img.gz) to store EFS backup(s). Restore command for your device is stored in txt file in the same directory with EFS backup. If you forgot command - you can read txt file containing proper command @ PC (Notepad) or even directly form TWRP using Terminal's 'cat' command, e.g.:
Code:
cat /external_sd/.backup/efs/efs_backup.txt
NOTE: Do not panic, read the txt file peacefully and type command exactly as it is in TWRP's Terminal, then tap blue [enter] button. After all - please reboot device. If the problem was EFS related - your device just has been rescued
Installation:
TWRP recovery (KNOX 0x1): open file using "Install (Zip)" option and confirm operation. If you want to perform "clean install' - perform "wipe data/factory reset" BEFORE flashing Zip!
Wipe data is NOT required if you are coming from stock ROM (already rooted) or a previous version of my DevBase (if you leave "Keep current CSC" option untouched in /options.prop or if you choose same CSC as you are currently using). In other cases - wipe data is highly recommended!
I do not recommend using any additional "superwipes" or format /system before install my DevBase (my installer cleans your system well enough!).
Credits:
@samsung for awesome device & stock firmware base
@Chainfire for systemless SuperSU and a lot of inspiration
@topjohnwu for Magisk and another inspiration
@rovo89 for Xposed framework & Xposed Installer app
@dr.ketan for being helpful whenever needed
@Zackptg5, @osm0sis & @jcadduono for no-verity*
@corsicanu & @geiti94 for TWRP recovery
@fei-ke for omc-decoder
Hit Thanks button if you like my work. If you really appreciate my work - feel free buy me a coffee/beer (or flowers/wine for my wife who is patiently enduring my hobbies) https://www.paypal.com/donate/?business=RFGVQYRC34RVQ&currency_code=EUR
Due to the fact, that some countries banned PayPal - I have created also Patreon site: https://www.patreon.com/_alexndr
Download ROM
SM-N960F/DS:
>> N960FXXSAFWB3_DevBase_v7.4.zip << (Android 10, updated Mar-05-2023, more info HERE)
SM-N960N:
>> N960NKSU3FVA1_DevBase_v7.4.zip << (Android 10, updated Mar-25-2022, more info HERE)
SM-N96xF/DS/FD/N repository:
>> Note 9 repository << [ AFH | MediaFire ]
Note:
Check MD5 sum BEFORE flash (useful TOOL), because flashing damaged or incomplete ZIP files could (soft) brick your phone! Correct MD5 sum is shown on the AndroidFileHost website while downloading.
Changelog
v7.4 (starting from N960NKSU3FUC1 DevBase):
- Fixed unzip issue which caused unexpected installation termination - applies to TWRP 3.5.0_9-1 and newer
v7.3 (starting from N960FXXU5DTCA DevBase):
- Fixed bootloop issue in case of Android Q and "noroot" scenario - thanks to @Zackptg5 for the up to date dm-verity disabler
v7.2 (starting from N960FXXS5DTB6 DevBase):
- Fixed bootloop issue in case of Android Q and encrypted devices (applies to dirty update)
v7.1 (starting from N960NKSU3DSLC DevBase):
- Potential fix for "make_ext4fs: not found" error in newer TWRP versions and in result "Failed! Not enough space..." message appears while applying CSC during install (applies to N960x devices)
v7.0 (starting from N960FXXU4DSLB DevBase):
- Initial support for Android Q / system-as-root devices
v6.0 (starting from N960FXXS2ARL3 DevBase):
- Introduced logging entire installation process (to devbase_install.log file, placed in /data or /cache in case of encrypted devices). These logs may significantly increase the possibility of my help in case of problems with/after installation
- Major imrovements/bugfixes/optimizations related to Android Pie support (e.g. takes care about special SELinux contexts for /odm content, introduced in Pie)
- Removed SuperSU support. Changed allowed "root" variable value in options.prop to true/false (backward compatible with old options.prop)
- Removed "skipblcp" option - baseband/modem will be always updated, bootloader need to be flashed separately (update is usually not mandatory)
v5.9 (starting from N960FXXS2ARH6 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 (not released for N960F):
- Improved unzip_flash function in the installer to detect properly more flashing errors (e.g. EXT4 partition mismatch)
v5.7 (not released for N960F):
- 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 (not released for N960F):
- 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 (not released for N960F):
- Added support for flashing optional, CSC related partitions ($OMR, $PRELOAD)
- Added possibility to update recovery (optional, performs update if exists $NAME/images/recovery.img)
- Return to using only the original XML files in the CSC package (thanks to @fei-ke for omc-decoder)
- Partition(s) may be wiped only by writing new block's image
- Minor optimizations / improvements in the installer
v5.4 (not released for N960F):
- 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 N960F):
- Improved algorithm of search & change "ro.security.vaultkeeper.feature" property to 0 (/system & /vendor)
v5.2 (not released for N960F):
- 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 N960F):
- 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 N960F):
- 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 N960F):
- 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_N960FXXU3xxxx_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 N960F):
- 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 N960F):
- 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 N960F):
- "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 N960F):
- 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 N960F):
- 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 N960F):
- 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 N960F):
- Added hexpatch to root_from function (support for SM-N930x, thanks to @Chainfire)
v3.7 (not released for N960F):
- Another major improvement/bugfix in deodex_from function (full support for 64 bit OS)
v3.6 (not released for N960F):
- 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 N960F):
- 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 N960F):
- 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 N960F):
- 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 N960F):
- Potential fix for reported problems with root (rare cases)
v3.3 (not released for N960F):
- 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 N960F):
- 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 N960F):
- 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 N960F):
- 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 N960F):
- 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 N960F):
- 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 N960F):
- 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 N960F):
- 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 N960F):
- 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 N960F):
- 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 N960F):
- Built without using a kitchen. All set_metadata* / symlink entries are result of arduous manual analysis. For more info about the method - see hidden content for Devs / Chefs in THIS thread.
- New customization method without using Aroma (options.prop)
- Many useful scripts for easy installation: CSC applying/autodetection, backup/restore of security files, backup/restore of existing CSC package, XML modding on the fly, root, init.d support
- Many small changes and improvements "in the meantime" which I simply do not remember...
- Safe De-Bloated (see post #1 for details)
Optional MODs
[WORK IN PROGRESS, MODDING HAS LOW PRIORITY]
These modifications I have done personally using (bak)smali tools - these are NOT "borrowed" from other custom ROM, nor from someone else's thread (thanks to @BlackMesa123, @corsicanu, @Grouxho & @yash92duster for their excellent modding guides). All ZIP files are TWRP flashable:
>> MODs for SM-N960F/DS <<
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 "N960FXXx2ARxx_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.
Okie :good:
holy crap
nice to see you here too Alex.
i can be your tester
downloading now
hopefully you can give us a patch kernel
note 9 can't be booted without root if twrp is installed.
also there's a bug with gear app which is pissing off a lot of devs here lol
---------- Post added at 12:56 AM ---------- Previous post was at 12:20 AM ----------
HOLY SHtttt
first rom that fixed the gear issue
it paired!!!!!
TheUndertaker21 said:
holy crap
nice to see you here too Alex.
i can be your tester
downloading now
hopefully you can give us a patch kernel
note 9 can't be booted without root if twrp is installed.
also there's a bug with gear app which is pissing off a lot of devs here lol
---------- Post added at 12:56 AM ---------- Previous post was at 12:20 AM ----------
HOLY SHtttt
first rom that fixed the gear issue
it paired!!!!!
Click to expand...
Click to collapse
After reboot as well?
Jenanga said:
After reboot as well?
Click to expand...
Click to collapse
yes
glad more devs are coming over
but this is the best one so far
---------- Post added at 01:14 AM ---------- Previous post was at 01:06 AM ----------
sadly SPAY for gear is being detected for root
worked on GSI roms
might be due to the kernel.
checked /data there's no su folder or anything
hopefully the dev can chin in
TheUndertaker21 said:
[...]
note 9 can't be booted without root if twrp is installed
Click to expand...
Click to collapse
This statement is not totally true Proper statement is as follows:
"Note 9 can't be booted with TWRP without necessary patches in the stock kernel"
In case of "noroot" scenario - some additional patches are applied to the stock kernel during install (on the fly), for example jesec's special dtb+fstab patch. Of course, without having device to test, I'm still not 100% sure if it works, but it SHOULD
TheUndertaker21 said:
HOLY SHtttt
first rom that fixed the gear issue
it paired!!!!!
Click to expand...
Click to collapse
Great to know
TheUndertaker21 said:
[...]sadly SPAY for gear is being detected for root
worked on GSI roms
might be due to the kernel.
Click to expand...
Click to collapse
Have you tried just to enable MagiskHide for this app manually? (NOTE: reboot is required afterwards)
I really doubt that there is something to do with the kernel to make it work.
_alexndr said:
This statement is not totally true Proper statement is as follows:
"Note 9 can't be booted with TWRP without necessary patches in the stock kernel"
In case of "noroot" scenario - some additional patches are applied to the stock kernel during install (on the fly), for example jesec's special dtb+fstab patch. Of course, without having device to test, I'm still not 100% sure if it works, but it SHOULD
Great to know
Have you tried just to enable MagiskHide for this app manually? (NOTE: reboot is required afterwards)
I really doubt that there is something to do with the kernel to make it work.
Click to expand...
Click to collapse
Hope you will get the device ??
Jenanga said:
Hope you will get the device
Click to expand...
Click to collapse
Hope he does too. But he does work without the device
_alexndr said:
This statement is not totally true Proper statement is as follows:
"Note 9 can't be booted with TWRP without necessary patches in the stock kernel"
In case of "noroot" scenario - some additional patches are applied to the stock kernel during install (on the fly), for example jesec's special dtb+fstab patch. Of course, without having device to test, I'm still not 100% sure if it works, but it SHOULD
Great to know
Have you tried just to enable MagiskHide for this app manually? (NOTE: reboot is required afterwards)
I really doubt that there is something to do with the kernel to make it work.
Click to expand...
Click to collapse
You should make one anyway lol.
Yeah, that's statement is what they told me I just poorly paraphrased it lol
Hiding magisk and spay don't work because the rom still detected root.
It worked for another stock rom because that rom was fully debloated
I'm not sure what else is being detected because spay doesn't provide the logs that it usually does
It does on gsi roms for some reason.
twrp, root (magisk 17.1) and encryption - all done in less than 40 minutes SUPER!!
I was a little bit scared to try this new rom on my new and expensive note 9 with 512 GB because the rom named with "TEST" - and I am by far not a PRO.
So I downloaded the stock ROM ( SM-N960F Region "LUX" ) with samfirm....just in case (it was not needed).
The Procedure is unbelievable easy:
I installed TWRP with ODIN, after the installation I disconnected usb connection, interrupted the download mode and switched directly into the recovery mode to start TWRP.
In TWRP I formated data partition and wiped all (dalvik/system/data/internal storage/cache). After that I directly
installed this ROM ( N960FXXS2ARH6_DevBase_v5.9.zip ) from SD card.
Next step was system start/setup incl. wifi (without waiting/problems) and the google login/setup. I installed titanium pro and root explorer (YES!! its rooted)
And the last step was flashing the renamed ROM ( N960FXXS2ARH6_DevBase_v5.9__encrypt.zip ) once more to get the encryption of my data partition.
Now I have a rooted AND encrypted Note 9 N960F/DS
SUPER!!!
Thanks a lot Alexander! :good: You really deserve a big donation on your account!
Some notes:
my note 9 forced to a factory reset when switched in developer options the OEM unlock. There was no way to avoid that (but at least there is no 7 days waiting period as it is reported for other devices).
Installing TWRP and avoiding a system reboot with many other samsung devices is soooo annoying.
With note 9 download and recovery mode are very easy to start and to switch.
This rom makes automatically efs backup on sd card - this is a VERY good security addon - "just in case"
I like to have multiuser support. Any idea how to get it?
steven1a said:
I was a little bit scared to try this new rom on my new and expensive note 9 with 512 GB because the rom named with "TEST" - and I am by far not a PRO.
So I downloaded the stock ROM ( SM-N960F Region "LUX" ) with samfirm....just in case (it was not needed).
The Procedure is unbelievable easy:
I installed TWRP with ODIN, after the installation I disconnected usb connection, interrupted the download mode and switched directly into the recovery mode to start TWRP.
In TWRP I formated data partition and wiped all (dalvik/system/data/internal storage/cache). After that I directly
installed this ROM ( N960FXXS2ARH6_DevBase_v5.9.zip ) from SD card.
Next step was system start/setup incl. wifi (without waiting/problems) and the google login/setup. I installed titanium pro and root explorer (YES!! its rooted)
And the last step was flashing the renamed ROM ( N960FXXS2ARH6_DevBase_v5.9__encrypt.zip ) once more to get the encryption of my data partition.
Now I have a rooted AND encrypted Note 9 N960F/DS
SUPER!!!
Thanks a lot Alexander! :good: You really deserve a big donation on your account!
Some notes:
my note 9 forced to a factory reset when switched in developer options the OEM unlock. There was no way to avoid that (but at least there is no 7 days waiting period as it is reported for other devices).
Installing TWRP and avoiding a system reboot with many other samsung devices is soooo annoying.
With note 9 download and recovery mode are very easy to start and to switch.
This rom makes automatically efs backup on sd card - this is a VERY good security addon - "just in case"
I like to have multiuser support. Any idea how to get it?
Click to expand...
Click to collapse
if you turn on OEM unlock it will force you to wipe
yeah there aren't any OEM jailb for FD model
i agree his rom is the best here so far
j̶u̶s̶t̶ ̶w̶a̶i̶t̶i̶n̶g̶ ̶f̶o̶r̶ ̶h̶i̶m̶ ̶t̶o̶ ̶m̶a̶k̶e̶ ̶t̶h̶a̶t̶ ̶k̶e̶r̶n̶e̶l̶ ̶i̶f̶ ̶h̶e̶ ̶h̶a̶s̶ ̶t̶i̶m̶e̶.̶ ̶ ̶s̶o̶ ̶g̶e̶a̶r̶ ̶s̶p̶a̶y̶ ̶c̶a̶n̶ ̶s̶t̶o̶p̶ ̶d̶e̶t̶e̶c̶t̶i̶n̶g̶ ̶r̶o̶o̶t̶
TheUndertaker21 said:
[...]
Hiding magisk and spay don't work because the rom still detected root.
It worked for another stock rom because that rom was fully debloated[...]
Click to expand...
Click to collapse
Are you sure that it is related to debloat? If you know what exactly need to be removed to make "spay" work - please let me know
(I'm an opponent of heavy debloat - I'm going to remove only really unnecessary stuff - harmful in case of rooted devices)
What do you mean by "... because the rom still detected root"? Do you mean "Custom" status instead of "Official" ?? If yes - I just prepared modified SysScope.apk for Note 9.
Please download the attachment, then replace original apk in /system/app/SysScope, then reboot device. Please let me know if it helps for "spay" (even if not - at least please let me know if "Device status" is "Official" with attached apk)
steven1a said:
[...]
Thanks a lot Alexander! :good: You really deserve a big donation on your account!
Click to expand...
Click to collapse
Big thanks :good:
BTW: I'm going to remove "TEST" word soon as it seems to be unnecessary
I'm going to re-upload the final version of this ROM soon with AppLock on board (just forgot about it). I also need a confirmation if attached "Official" status MOD works well in Note 9 (not placed it in initial version intentionally, but now it's time to put it in the final version).
steven1a said:
[...]
I like to have multiuser support. Any idea how to get it?
Click to expand...
Click to collapse
I never needed it, even never tested it, but just found this:
https://forum.xda-developers.com/galaxy-note-8/how-to/add-guest-mode-multiple-users-easy-t3756128
Im Bit confused after the last Statements. Whats now recommend for clean Flash (the rename stuff)
_alexndr said:
This statement is not totally true Proper statement is as follows:
"Note 9 can't be booted with TWRP without necessary patches in the stock kernel"
In case of "noroot" scenario - some additional patches are applied to the stock kernel during install (on the fly), for example jesec's special dtb+fstab patch. Of course, without having device to test, I'm still not 100% sure if it works, but it SHOULD
Great to know
Have you tried just to enable MagiskHide for this app manually? (NOTE: reboot is required afterwards)
I really doubt that there is something to do with the kernel to make it work.
Click to expand...
Click to collapse
i fixed that issue
i debloated the rom.
the error will popup if there are any trace of crappy knox apps there
i can use spay for gear now
Thanks for this Alex
---------- Post added at 10:08 PM ---------- Previous post was at 09:59 PM ----------
_alexndr said:
Are you sure that it is related to debloat? If you know what exactly need to be removed to make "spay" work - please let me know
(I'm an opponent of heavy debloat - I'm going to remove only really unnecessary stuff - harmful in case of rooted devices)
What do you mean by "... because the rom still detected root"? Do you mean "Custom" status instead of "Official" ?? If yes - I just prepared modified SysScope.apk for Note 9.
Please download the attachment, then replace original apk in /system/app/SysScope, then reboot device. Please let me know if it helps for "spay" (even if not - at least please let me know if "Device status" is "Official" with attached apk)
Big thanks :good:
BTW: I'm going to remove "TEST" word soon as it seems to be unnecessary
I'm going to re-upload the final version of this ROM soon with AppLock on board (just forgot about it). I also need a confirmation if attached "Official" status MOD works well in Note 9 (not placed it in initial version intentionally, but now it's time to put it in the final version).
I never needed it, even never tested it, but just found this:
https://forum.xda-developers.com/galaxy-note-8/how-to/add-guest-mode-multiple-users-easy-t3756128
Click to expand...
Click to collapse
also note this is for the gear spay not spay for phone
doubt we can get that to work lol
Jenanga said:
Im Bit confused after the last Statements. Whats now recommend for clean Flash (the rename stuff)
Click to expand...
Click to collapse
According to @steven1a's report - there is no lags/freezes after clean install at first boot in case of Note 9. Seems like the issue applies only to Android 8.0 (my other devices case)
TheUndertaker21 said:
i fixed that issue
i debloated the rom.
the error will popup if there are any trace of crappy knox apps there
i can use spay for gear now
Thanks for this Alex
Click to expand...
Click to collapse
My ROM has removed KNOX app.
Would you like to have more tuned/nuanced DevBase ROM? Could you point me which one I missed?
_alexndr said:
According to @steven1a's report - there is no lags/freezes after clean install at first boot in case of Note 9. Seems like the issue applies only to Android 8.0 (my other devices case)
My ROM has removed KNOX app.
Would you like to have more tuned/nuanced DevBase ROM? Could you point me which one I missed?
Click to expand...
Click to collapse
security agents, samsung pay framework
gonna flash your rom again and make a titaniumback and will let you know which stuff got deleted.
Jenanga said:
Im Bit confused after the last Statements. Whats now recommend for clean Flash (the rename stuff)
Click to expand...
Click to collapse
At first you format and wipe , so it is a "clean installation"
then flash the zip file with TWRP "as it is" from AFH
and for the encryption just add the word -encrypt- in the existing filename and "dirty" flash it on top (without format and wiping).
or/and just read again above
@_alexndr,
Here's the list of all the apps I removed.
View attachment 4605806

Categories

Resources