Database Develop

[SAMSUNG][Android 6.x/7.x/8.x] SYSTEMLESS DevBase v2.1 | Encryption support

Hello
Do you remember my custom ROMs for older devices? Do you remember my "DevBase" and its idea? If not - please read hidden content below:
>> [ROM] DevBase for Note 3 (SM-N9005) <<
>> [ROM] DevBase for Note 4 (SM-N910F) <<
>> [ROM] DevBase for S5 (SM-G900F) <<
>> [ROM] DevBase for S5 Duos (SM-G900FD) <<
Since I created these custom ROMs - many things have changed. Main idea of my previous work was the ability to flash these ROMs over stock ROM without wipe data - to let users simply jump between official ROM and DevBase with most necessary modifications for advanced users. It was relatively simple to implement until Samsung introduced both: dm-verity's boot prevention + forced /data encryption (starting from S7/S7edge series). What does it mean? If you disable /data encryption - you are able to use TWRP like in older devices, you are able to flash custom ROMs available in this section, but you are not able simply switch to official stock ROM. Since I bought my S7 edge I realized, that the most reasonable way is to go in the "systemless direction".
Are you tired with traditional custom ROMs?
Do you miss custom ROMs but do not want to decrypt your device (for privacy/security reasons)? (!)
You are in the right place! I present you SYSTEMLESS DevBase - an SYSTEMLESS equivalent of my previous work (see hidden content above)
SYSTEMLESS DevBase is developed and physically tested on S7 Edge (G935F). However, it should work on ALL UNLOCKED SAMSUNG DEVICES running Android 6.x/7.x/8.x. Exynos? Snapdragon? NO MATTER !!!
Prerequisites:
- Samsung device running stock or stock-based Android 6.x or newer (7.x/8.x)
- Rooted device - Magisk v12+ or SuperSU v2.76+ installed in SYSTEMLESS mode (!)
- Stock, untouched /system partition (not mandatory, but recommended for OTA)
(!) WARNING (related to installing TWRP and/or rooting Nougat - e.g. ZPLN, DPLT or newer): There are confirmed reports that installing TWRP and/or rooting encrypted phones running stock Nougat causes bootloop (even if you just flash TWRP, without rooting). You will need to restore both - stock recovery and stock kernel (if you e.g. tried to flash SuperSU or other ZIP which might modify the kernel) to make your device bootable. You need to remove stock encryption (by formatting /data after rooting). If you need data encryption - you can easy re-encrypt already rooted device (by setting "KEEPFORCEENCRYPT" flag to "true" before (re)flashing Magisk or SuperSU).
SYSTEMLESS DevBase v2.0:
1. Benefits / main features:
- Works with encypted /data partition (**) (!)
- Working official OTA updates! (see Tips & Tricks - post #4)
- Does NOT perform any phisical modifications in /system
- Does NOT perform any additional changes/patches to the kernel
- Removed KNOX warnings (systemlessly removed SecurityLogAgent)
- It contains SYSTEMLESS BusyBox (bionic, the most stable and respected release)
- It allows you to easily modify most of files & apps in your /system - SYSTEMLESSLY (see Tips & Tricks)
2. Systemless Safe De-Bloat (more info below):
What does it mean and why is it called "safe"?
- ONLY apps available in stores will be systemlessly removed from the ROM, so you can easily (re)install any of these app if you like
- ONLY pre-installed system apps are will be systemlessly removed, DevBase installer never touch any updated app nor app installed manually from store
Thus, the following conclusions can be drawn:
1. If you install my SYSTEMLESS DevBase directly over working stock ROM - in most cases almost all these apps will remain untouched, because almost all apps have been updated already (stored on /data). But then you will be able to remove any useless app using the "Application manager" -> [Name_Of_App_To_Remove] -> MORE -> Uninstall updates. NOTE: App will disappear arter reboot and will be visible even in Titanium Backup!
2. If you perform "Wipe data" directly before installing SuperSU and my SYSTEMLESS DevBase (before you let to install app's updates) - then all apps listed below will be removed. If you would like to use any of these apps - just install it manually from appropriate store. Installed manually app will not be removed during the next DevBase update or re-install.
Removed apps list (depends on the device, should cover all devices starting from Galaxy S5):
ChatON
Chrome
Drive
Dropbox
EditorsDocs
Evernote
Excel
Facebook
FB Messenger
FB Pages Manager
Flipboard
Google+ / Photos
Group Play
Hangouts
Instagram
OneDrive
OneNote
PEN.UP
Play Books
Play Games
Play Movies
Play Music
Play Newsstand
PowerPoint
Skype
Smart Remote
WhatsApp
Word
NEW! Safe De-Bloat feature automatically detects and systemlessly removes apps not listed above, but present in your CSC package
3. Systemless CscFeature MOD (enabled some built-in, hidden features):
- Added shutter sound menu in Camera app
- Sending/receiving MMS without data on
- Show SMS/MMS sending time instead of receiving
- Added "Exit Internet" option to stock browser
- Added call button in Phone Logs (**)
- Added "Call/Message block" option in Settings
- Added symbols as secondary keys in Samsung keyboard (**)
- Added 4G/3G network support (master/slave SIM card - applies to Duos variants)
- Call Recording (added "Record" button, auto record calls - starting from Nougat)
- Enabled "Recent App Protection" feature
(**) may not work starting from Android 7.0 Nougat
Installation:
1. TWRP recovery:
- Tap "Keep Read Only" on the Welcome screen [extremely important for working OTA!]
- Open file using "Install" option (use extSdCard or OTG storage in case of encrypted /data)
- Confirm flash by swiping right
- Tap "Reboot System" (DO NOT wipe /cache after flashing in case of encrypted /data!)
2. FlashFire app (***):
- Open file using "Flash ZIP or OTA" option
- UNTICK "Mount /system read/write" [extremely important for working OTA!]
- Tap "FLASH"
NOTE1: One additional auto-reboot may be performed at first boot. It is not a bug (may be required for systemless build.prop support - see Tips & Tricks for more explanations)
NOTE2: Do not worry about red "mount /data failed..." messages displayed in TWRP in case of encrypted /data (installer will do the work anyway!)
(***) As far as I know - FlashFire is the only flashing tool with full access to /data during flash in case of encrypted devices (!). It is also the only tool which allows you to perform full backup/restore of partitions, including encrypted /data (!). It does NOT require custom recovery to work!
Credits:
@Chainfire for systemless SuperSU and a lot of inspiration
@topjohnwu for Magisk, another inspiration & some binaries used separately
Hit Thanks button if you like my work. If you really appreciate my work - feel free to buy me a beer

Download
>> SYSTEMLESS_DevBase_v2.1.zip <<
>> Recent SYSTEMLESS DevBase <<
Note:
Check MD5 sum BEFORE flash (useful TOOL), because flashing damaged or incomplete ZIP files can lead to issues! Correct MD5 sum is shown on the AndroidFileHost website while downloading.

Changelog
v2.1:
- Fixed potential "Google Play services" FCs in case of S8 or newer device(s)
v2.0:
- Initial support for devices using /system/omc CSC location (e.g. S8 / S8+ / Note 8)
- Added support for /system/preload as app location
- Other improvements & optimizations in the installer
v1.15:
- Added support for BINDSBIN mode (required by latest suhide) in case of SuperSU as root solution
v1.14:
- Added possibility to bypass all systemless mods by creating /cache/.disable_devbase file. It is usefull option especially for encrypted devices (without access to /data from TWRP) in case of you experienced bootloop due to placing a problematic MOD in /data/devbase/system/.. If /cache/.disable_devbase file exists then all systemless mods in ../app ../framework & ../piv-app will be moved to /data/devbase/system/.backup
- Backup all mods (to /data/devbase/system/.backup) instead of delete in case of major Android update has been detected
v1.13:
- Fixed bug with combination Magisk v15+ & SYSTEMLESS DevBase if we are trying to install one by one directly after wipe/format data
v1.12:
- Improved compatibility with Magisk v15+
v1.11:
- Fixed issues and improved compatibility with Magisk v14.5+
v1.10:
- Fixed not working /sbin support after clean installation of Magisk v14+, then SYSTEMLESS DevBase
v1.9:
- Improved/tuned compatibility with Magisk v13+ (which has been re-built from the scratch)
- Updated Magisk's binaries (e.g. resetprop function is now an applet available in magisk binary)
- Systemless BusyBox will be installed even with Magisk (since it has been removed from Magisk v13+)
v1.8:
- Fixed unroot2ota script to work while busybox is NOT in the $PATH (typical Magisk's case)
v1.7:
- Added support for /sbin via /data/devbase/sbin (you can only add a NEW item, e.g. script/binary/executable file). It can be an interesting feature for advanced users which would like to add custom commands, because /sbin is in the $PATH
- resetprop & unroot2ota now are placed in /sbin, in result unroot2ota command will natively work even with Magisk (without SuperSU)
v1.6:
- Improved/fixed Systemless Safe De-Bloat - now it should work in any case (even if enforceskippingpackages.txt file does not exist in your stock FW)
- In case of SYSTEMLESS DevBase update or re-installation - installer will not remove your custom entries in /data/devbase/system/build.prop and in *.xml files placed in /data/devbase/system/csc
- Added new features to Systemless CscFeature MOD: Allow 3G network mode in case of slave SIM card (Duos variant); Enabled "Recent App Protection" feature
v1.5:
- Added full support for MagiskSU as root solution. SuperSU is no longer the only available prerequisite
- Improved build.prop support in case of SuperSU as root solution, without magisk installed (seems like we can't rely on resetprop binary @ Android N)
- unroot2ota: removed SuperSU's sukernel dependency
v1.4:
- Improved/changed support for /data/devbase/system/build.prop file (uses @topjohnwu's resetprop binary)
- "ro.warranty_bit" & "ro.boot.warranty_bit" are set to "0" at boot -> fake KNOX 0x0 status (uses @topjohnwu's resetprop binary)
v1.3:
- Fixed CscFeature MOD (e.g. G920I case, now should work with all Samsung devices/variants)
v1.2:
- Added info in Settings/About device/Software info/Build number (can be overrided by editing /data/devbase/system/build.prop)
- unroot2ota: added ability to restore stock recovery using /system/recovery-from-boot.p file (no guarantee)
- unroot2ota: check /system partition for common modifications before unroot
- Minor changes & improvements in the shell code
v1.1:
- Added SYSTEMLESS support for /system/framework
- Added SYSTEMLESS support for /system/build.prop (overrides & additions)
- Added SYSTEMLESS BusyBox bionic (the most stable and respected release)
- Added major Android update detection (auto-remove mods for older API to prevent bootloops & FCs)
- Added logging to /data/devbase/last_boot.log (API & errors)
- Added SuperSU boot patcher version checker (exits su.d boot script if < 2.76)
- Added "Please DO NOT wipe /cache" warning in case of encrypted devices and TWRP recovery
- Minor changes & optimizations in the shell code
- Added SYSTEMLESS DevBase uninstaller
v1.0:
- Initial version

Tips & Tricks
1. OTA updates:
- Basically, the only thing you need to take OTA update is to perform "Full unroot" in the SuperSU app. However, a better way is to use "unroot2ota" terminal command, because this will not remove DevBase boot script from /su/su.d and the only thing you will need to re-activate SYSTEMLESS DevBase (and all your systemless MODs) after performing OTA update is just re-root your device with CF-Auto-Root.
- If you flashed custom recovery like TWRP - it is mandatory to restore your stock recovery (otherwise OTA will not work). You can do it using FlashFire app (the easiest way) - just open recovery.img file (extracted from your original FW) using "Flash firmware package" option, disable "Preserve recovery" option and then tap "FLASH". EDIT: Starting from version v1.2 there is a new "unroot2ota" feature which allow you to restore stock recovery using /system/recovery-fromm-boot.p file. There is no guarantee to perform it successfully (even if there is no error message) but in most cases it works well (tested on Nougat beta). Please go to recovery before you try to get OTA to check if you have stock recovery already after performing "unroot2ota" (if not - you need to use PC Odin to flash recovery.img packed in tar file).
- It is recommended to temporarily disable "Auto-update apps" in Play Store settings before you unroot your device. It will prevent updating applications covered by Safe De-Bloat list, as there apps will temporarily appear until you re-root the phone after performing OTA update.
Note (devices which use dm-verity): You should never allow /system modifications in TWRP, never allow to remount /system r/w in any app (e.g. Root Explorer, FlashFire, etc.) and never flash a ZIP file which could modify your /system or remount it r/w. Failure to follow these recommendations will break dm-verity verification and will cause, that your device may not be able to boot with the stock kernel (you will need to re-flash your original FW using PC Odin to make your device bootable).
UPDATE: Due to the fact that installing TWRP and/or rooting encrypted phones running stock Nougat is not possible without format /data - the above described advantages applies to stock ROMs based on Android up to 6.0
2. Making your own modifications:
- You can systemlessly replace any existing system app by modded one. Just put modified app to /data/devbase/system/app or /data/devbase/system/priv-app and then reboot your device
- You can systemlessly replace jar or apk in /system/framework. Just put modified one to /data/devbase/system/framework and then reboot your device (NOTE: framework support has been added for advanced users -> there is high risk of bootloop if you do something wrong!)
- You can systemlessly add or override any line in /system/build.prop. Just put (only new or changed) line to /data/devbase/system/build.prop and then reboot your device (NOTE: one additional auto-reboot may be performed if /data/devbase/system/build.prop file has been added, modified or removed (SuperSU case). It is not a bug - it is required for the changes in /data/devbase/system/build.prop to take effect!)
- You can systemlessly replace any existing file in /system/csc and /system/etc (but NOT in subdirectories). Just put modified copy of a file to /data/devbase/system/csc or /data/devbase/system/etc and then reboot device
Limitations: original app or file MUST physically exist with the same name in /system, you can NOT add a new app or file this way!
Example 1 (Ad-Blocking): Download the latest Ad-Blocking ZIP installer from THIS thread. Extract "hosts" file (placed in /system/etc inside ZIP file), then copy it to /data/devbase/system/etc, set rw-r--r-- (644) permissions and then reboot device
Example 2 (modded SamsungCamera6): Create "SamsungCamera6" directory in /data/devbase/system/priv-app and then put modified "SamsungCamera6.apk" file into it. Set rwxr-xr-x (755) permissions to "SamsungCamera6" directory, rw-r--r-- (644) permissions to "SamsungCamera6.apk" and then reboot device
Example 3 (De-Bloating a bit more): You can just create empty directories in /data/devbase/system/app (or priv-app) corresponding to applications in /system/app (or priv-app). Alternatively (more advanced method), you can add an app to modded enforceskippingpackages.txt file (you can find it in /data/devbase/system/etc or /data/devbase/system/csc_contents, depending on the original location in /system) and increase number in the 1st line. Second method should not be used by beginners (without a basic knowledge related to UNIX text format)
3. How to manually maintain the newest ROM version:
If you do not care about OTA - you can manually update your device to the newest ROM available @ Sammobile, keeping your original CSC (you need multi-file original FW, I mean separate files for BL/AP/CP/CSC). You need to download 2 ROMs: ROM with the newest changelist and the latest ROM containing your original CSC. Extract both and open in PC Odin BL/AP/CP files from the ROM with highest changelist but open CSC file from the ROM containing your CSC (I recommend to use HOME_CSC_* file to avoid auto-wipe-data). Flash such "mix", re-root and enjoy

Optional MODs
I put some of my favorite MOD's. These modifications I have done personally using (bak)smali tools - these are NOT "borrowed" from other custom rom, nor from someone else's thread (thanks to @majdinj & @tdunham for their excellent modding guides). All files are FlashFire / TWRP flashable ZIPs.
These MODs are compatible with SYSTEMLESS DevBase - installer will try to detect if your /system has been moddified (or not) already. If the installer will not detect any popular /system modifications like SuperSU / busybox / Xposed (installed to /system) then will try to install app systemlessly to /data/devbase/system/(priv-)app
1. Modified Camera app:
- Full functionality of the Camera app in low battery
2. Modified Messages app:
- Disabled SMS delivery notifications (*)
(*) If you long press a message you can still check if the message has been delivered or not, we do not need to see and hear notifications for every sms. It's annoying to me!
>> MODs for G935F (Marshmallow) << (**)
>> MODs for G935F (Nougat) << (**)
(**) Original apps come from stock ROM for G935F, but these MODs should work on all S7 flat & edge variants (Exynos based)
In case of MODs installed to /system - you can restore original apk using backup stored in /data/alexndr/backup

Incredible work, man! Thanks

I'm HAPPY to see you in this Forum with an S7edge !

@_alexndr
Congrats mate! Great job I will test it in a few days
# 1 question
What about framework folder support with modded files ?
# 2 question
Modded deodex apps putted in /data/devbase/system folders will work on odex system ?
For example:
/data/devbase/system/priv-app/SystemUI/SystemUI.apk
will be deodexed
but orginal one:
/system/priv-app/SystemUI/SystemUI.apk
will be odex (with arm folders)
# 3 question
For example if I put systemui.apk the modded will be run and original no ? Or they collaborate toggether ?
Edit:
If I correct understand examples they are colaborate
# 4 question
system/etc/permissions files not supported too ? For exapmle platform.xml
••••
This tool have a BIG potential to be the greatest !
Have a nice day

ambasadii said:
@_alexndr
Congrats mate! Great job I will test it in a few days
# 1 question
What about framework folder support with modded files ?
# 2 question
Modded deodex apps putted in /data/devbase/system folders will work on odex system ?
For example:
/data/devbase/system/priv-app/SystemUI/SystemUI.apk
will be deodexed
but orginal one:
/system/priv-app/SystemUI/SystemUI.apk
will be odex (with arm folders)
# 3 question
For example if I put systemui.apk the modded will be run and original no ? Or they collaborate toggether ?
Edit:
If I correct understand examples they are colaborate
# 4 question
system/etc/permissions files not supported too ? For exapmle platform.xml
����
This tool have a BIG potential to be the greatest !
Have a nice day
Click to expand...
Click to collapse
#2: Deodexed apps works great in odexed rom, but odexed apps will not work at all in case of deodexed framework!
SYSTEMLESS DevBase uses bind mounts so entire /system/priv-app/SystemUI directory (and its content) will be virtually replaced by /data/devbase/system/priv-app/SystemUI => it means you will not see oat/arm directory => entire app will act as deodexed in /system/...
See attached screenshots - first is with moded SamsungCamera5 present in /data/devbase/system/priv-app, second is after deleting /data/devbase/system/priv-app/SamsungCamera5 (and reboot)
Now it is good time to answer #1: With framework I intentionally dropped possibility to replace systemlessly files in .../framework (for security reasons @ to avoid unintentional bootloops). Imagine that you "systemlessly" replace ../framework/oat directory by empty one => then all jars corresponding to *.odex files in oat/arm(64) will immediately require classes*.dex files inside jars (otherwise will not work). Even if you replace entire framework by deodexed (with classes.dex inside jars) -> as I stated above (answer #2) -> almost all apps in /system/app & priv-app will stop working as almost all apps are originally ODEXED.
Imagine also that you leaded device into bootloop by replacing files in framework AND you have encrypted /data. There is no easy way out for normal users (which are not able to play with "fake" /cache/su.img to make workaround matched to the problem) they will not be able just remove files (causing the problem) from /data/devbase/system/framework using TWRP
In sum - thats why I have not introduced such possibility for normal users, but you as the DEV may extend this idea and try to systemlessly replace entire framework, app & priv-app by deodexed content (I have not tested it personally, IMO it does not worth the effort)
#3: The answer is now clear from the answer to question #2 - modded will run and original will NOT (original will "virtually disappear")
#4: It is easy to extend support for etc/permissions/* files by editing 0000000devbase, I will think about it

Now almost everything is clear
so for example if i put /data/devbase/system/framework/services.jar and delete from system/framework/oat/arm64/services.odex file should work ?
add support for etc/permissions/* files to fix ext-card permissions (platform.xml)

ambasadii said:
Now almost everything is clear
so for example if i put /data/devbase/system/framework/services.jar and delete from system/framework/oat/arm64/services.odex file should work ?
add support for etc/permissions/* files to fix ext-card permissions (platform.xml)
Click to expand...
Click to collapse
The only way to "virtually remove" files using this method is "fake" (e.g. empty) parent directory. Another way is to create "fake" file with same name (but size 0 bytes).
There is a chance that it will work for services.jar - but such "fun/play" is only for advanced DEVs, like you :good: you need to extend support for framework and subdirectories in 0000000devbase su.d script. Then you can try to systemlessly replace jar by deodexed&modded one in /data/devbase/system/framework... and odex file by "fake 0 sized" odex in /data/devbase/system/framework/oat/arm64/...
EDIT: @ambasadii, there is no need to "remove" (whatever it means) odex file as it will be ignored in case of jar or apk contains classes*.dex inside

Ok I will test it
Sent from my SM-G935F using XDA-Developers mobile app

_alexndr said:
you need to extend support for framework and subdirectories in 0000000devbase su.d script. Then you can try to systemlessly replace jar by deodexed&modded one in /data/devbase/system/framework...
Click to expand...
Click to collapse
correct ?
Code:
if [ -d "/data/devbase/system/framework" ] ; then
for i in `ls /data/devbase/system/framework` ; do
mount -o bind /data/devbase/system/framework/$i /system/framework/$i 2>/dev/null
done
fi
if [ -d "/data/devbase/system/etc/permissions" ] ; then
for i in `ls /data/devbase/system/etc/permissions` ; do
if [ -f "/data/devbase/system/etc/permissions/$i" ] ; then
mount -o bind /data/devbase/system/etc/permissions/$i /system/etc/permissions/$i 2>/dev/null
fi
done
fi
EDIT: @ambasadii, there is no need to "remove" (whatever it means) odex file as it will be ignored in case of jar or apk contains classes*.dex inside
Click to expand...
Click to collapse
good news, remove it means delete

ambasadii said:
correct ?
Code:
if [ -d "/data/devbase/system/framework" ] ; then
for i in `ls /data/devbase/system/framework` ; do
mount -o bind /data/devbase/system/framework/$i /system/framework/$i 2>/dev/null
done
fi
if [ -d "/data/devbase/system/etc/permissions" ] ; then
for i in `ls /data/devbase/system/etc/permissions` ; do
if [ -f "/data/devbase/system/etc/permissions/$i" ] ; then
mount -o bind /data/devbase/system/etc/permissions/$i /system/etc/permissions/$i 2>/dev/null
fi
done
fi
Click to expand...
Click to collapse
Basically correct but you need to add bind mounts only for files (just in case)
I will send you today new (pre-release v1.1) version with "slightly tuned code" and with support for framework
good news, remove it means delete
Click to expand...
Click to collapse
Nice joke :silly: "whatever it means" => FYI => it may also mean bind mounts with files (0 bytes size)

Welcome to the S7 bro

Hi alexndr
I love you from 9005 to now.
Plz add a option in cmera mod,that under i geting 60fps video,i can get pic.
Mean, camcorder 60fps and camera pictures together .
I cant write eng.plz exercise me.
Sent from my SM-G935F using Tapatalk

Awesome to see you here! Thanks @_Alexandr
Gesendet von meinem SM-G935F mit Tapatalk

Nice to see a familiar face in the S7 (E) section! Good luck with all your plans here.
Verstuurd vanaf mijn SM-G935F met Tapatalk

Nice to find you here Alexandr, been using your Roms on my old note 3 about 8 months ago and they were the most stable "custom Roms". But then you were providing a full unmodified ROM with root access, can you do something like this here for those of us that wish it? I personally don't have access to a PC so I can't flash newer firmwares with Odin, so I'm stuck using flashable ROMs.

It is possible to install magisk and work hide magisk for apps, for example bank apps?

[G928F/C/G/L/S/...][6.0+] SYSTEMLESS DevBase | Encryption support | Stock OTA update

SYSTEMLESS DevBase has been developed and physically tested on S7 Edge (G935F), so main thread containing the most detailed description you can find here:
>> [SAMSUNG][6.0+] SYSTEMLESS DevBase | Encryption support | Stock OTA updates <<
However, it should work on ALL SAMSUNG DEVICES running Android 6.0+, so if you are Galaxy S6 Edge+ (G928xx) owner - please place your feedback & discussion here to let me know about device-specific issues or to let me know that everything works perfect
---------------------------------------------------------------------------
Are you tired with traditional custom ROMs?
Do you miss custom ROMs but you would like to have encrypted /data (for privacy/security reasons)?
You are in the right place! I present you SYSTEMLESS DevBase - an SYSTEMLESS equivalent of my previous work (for older devices)
Prerequisites:
- Samsung device running stock or stock-based Android 6.0+ (mandatory!)
- Rooted device - SuperSU v2.76+ installed in SYSTEMLESS mode (mandatory!) (*)
- Stock, untouched /system partition (not mandatory, but recommended for working OTA)
- Stock recovery (not mandatory, but recommended for working OTA)
(*) NOTE: The latest CF-Auto-Root image for G928F contains SuperSU v2.74 which does not support SYSTEMLESS solutions (su.d is not triggered early enough). It is NOT enough to update it via PlayStore to the newest version and update su binaries! You need to update it using TWRP / FlashFire installable ZIP from THIS STABLE or THIS BETA thread. Alternatively you can use "EverRoot" -> "Inject SuperSU" option in FlashFire even if you are rooted already by CF-Auto-Root (it will update SuperSU in the same way as flashing ZIP).
SYSTEMLESS DevBase:
1. Benefits / main features:
- Works with encypted /data partition
- Working official OTA updates! (see Tips & Tricks)
- Does NOT perform any phisical modifications in /system
- Does NOT perform any additional changes/patches to the kernel
- Removed KNOX warnings (systemlessly removed SecurityLogAgent)
- It contains SYSTEMLESS BusyBox (bionic, the most stable and respected release)
- It allows you to easily modify most of files & apps in your /system - SYSTEMLESSLY (see Tips & Tricks)
- It does not interfere with Magisk! You can use Magisk in paralell with SYSTEMLESS DevBase if you need it for your favorite module.
2. Systemless Safe De-Bloat (more info below):
What does it mean and why is it called "safe"?
- ONLY apps available in stores will be systemlessly removed from the ROM, so you can easily (re)install any of these app if you like
- ONLY pre-installed system apps are will be systemlessly removed, DevBase installer never touch any updated app nor app installed manually from store
Thus, the following conclusions can be drawn:
1. If you install my SYSTEMLESS DevBase directly over working stock ROM - in most cases almost all these apps will remain untouched, because almost all apps have been updated already (stored on /data). But then you will be able to remove any useless app using the "Application manager" -> [Name_Of_App_To_Remove] -> MORE -> Uninstall updates. NOTE: App will disappear arter reboot and will be visible even in Titanium Backup!
2. If you perform "Wipe data" directly before installing SuperSU and my SYSTEMLESS DevBase (before you let to install app's updates) - then all apps listed below will be removed. If you would like to use any of these apps - just install it manually from appropriate store. Installed manually app will not be removed during the next DevBase update or re-install.
Removed apps list (depends on the device, should cover all devices starting from Galaxy S5):
ChatON
Chrome
Drive
Dropbox
EditorsDocs
Evernote
Excel
Facebook
FB Messenger
FB Pages Manager
Flipboard
Google+ / Photos
Group Play
Hangouts
Instagram
OneDrive
OneNote
PEN.UP
Play Books
Play Games
Play Movies
Play Music
Play Newsstand
PowerPoint
Skype
Smart Remote
WhatsApp
Word
NEW! Safe De-Bloat feature automatically detects and systemlessly removes apps not listed above, but present in your CSC package
3. Systemless CscFeature MOD (enabled some built-in, hidden features):
- Added shutter sound menu in Camera app
- Sending/receiving MMS without data on
- Show SMS/MMS sending time instead of receiving
- Added "Exit Internet" option to stock browser
- Added call button in Phone Logs (**)
- Added "Call/Message block" option in Settings
- Added symbols as secondary keys in Samsung keyboard (**)
- Call Recording (manual control, added "Record" button)
(**) may not work starting from Android 7.0 Nougat
Installation:
1. FlashFire app (recommended ***):
- Open file using "Flash ZIP or OTA" option
- UNTICK "Mount /system read/write" [extremely important for working OTA!]
- Enable "EverRoot" -> "Inject SuperSU" option if necessary (see NOTE above (*))
- Tap "FLASH"
2. TWRP recovery:
- Tap "Keep Read Only" on the Welcome screen [extremely important for working OTA!]
- Open file using "Install" option (use extSdCard or OTG storage in case of encrypted /data)
- Confirm flash by swiping right
- Tap "Reboot System"
NOTE1: One additional auto-reboot may be performed at first boot. It is not a bug (may be required for systemless build.prop support - see Tips & Tricks for more explanations)
NOTE2: Do not worry about red "mount /data failed..." messages displayed in TWRP in case of encrypted /data (installer will do the work anyway!)
(***) As far as I know - FlashFire is the only flashing tool with full access to /data during flash in case of encrypted devices. It is also the only tool which allows you to perform full backup/restore of partitions, including encrypted /data. It does NOT require custom recovery to work!
Credits: @Chainfire for systemless SuperSU and a lot of inspiration
Hit Thanks button if you like my work. If you really appreciate my work - feel free to buy me a beer

Download
>> Recent SYSTEMLESS DevBase <<
Note:
Check MD5 sum BEFORE flash (useful TOOL), because flashing damaged or incomplete ZIP files can lead to issues! Correct MD5 sum is shown on the AndroidFileHost website while downloading.
Changelog
Please visit MAIN THREAD - post #3

Tips & Tricks
1. OTA updates:
- Basically, the only thing you need to take OTA update is to perform "Full unroot" in the SuperSU app. However, a better way is to use "unroot2ota" terminal command, because this will not remove DevBase boot script from /su/su.d and the only thing you will need to re-activate SYSTEMLESS DevBase (and all your systemless MODs) after performing OTA update is just re-root your device with CF-Auto-Root.
- If you flashed custom recovery like TWRP - it is mandatory to restore your stock recovery (otherwise OTA will not work). You can do it using FlashFire app (the easiest way) - just open recovery.img file (extracted from your original FW) using "Flash firmware package" option, disable "Preserve recovery" option and then tap "FLASH". EDIT: Starting from version v1.2 there is a new "unroot2ota" feature which allow you to restore stock recovery using /system/recovery-fromm-boot.p file. There is no guarantee to perform it successfully (even if there is no error message) but in most cases it works well (tested on Nougat beta). Please go to recovery before you try to get OTA to check if you have stock recovery already after performing "unroot2ota" (if not - you need to use PC Odin to flash recovery.img packed in tar file).
- It is recommended to temporarily disable "Auto-update apps" in Play Store settings before you unroot your device. It will prevent updating applications covered by Safe De-Bloat list, as there apps will temporarily appear until you re-root the phone after performing OTA update.
Note (devices which use dm-verity): You should never allow /system modifications in TWRP, never allow to remount /system r/w in any app (e.g. Root Explorer, FlashFire, etc.) and never flash a ZIP file which could modify your /system or remount it r/w. Failure to follow these recommendations will break dm-verity verification and will cause, that your device may not be able to boot with the stock kernel (you will need to re-flash your original FW using PC Odin to make your device bootable).
2. Making your own modifications:
- You can systemlessly replace any existing system app by modded one. Just put modified app to /data/devbase/system/app or /data/devbase/system/priv-app and then reboot your device
- You can systemlessly replace jar or apk in /system/framework. Just put modified one to /data/devbase/system/framework and then reboot your device (NOTE: framework support has been added for advanced users -> there is high risk of bootloop if you do something wrong!)
- You can systemlessly add or override any line in /system/build.prop. Just put (only new or changed) line to /data/devbase/system/build.prop and then reboot your device (NOTE: one additional auto-reboot will be performed if /data/devbase/system/build.prop file has been added, modified or removed. It is not a bug - it is required for the changes in /data/devbase/system/build.prop to take effect!)
- You can systemlessly replace any existing file in /system/csc and /system/etc (but NOT in subdirectories). Just put modified copy of a file to /data/devbase/system/csc or /data/devbase/system/etc and then reboot device
Limitations: original app or file MUST physically exist with the same name in /system, you can NOT add a new app or file this way!
Example 1 (Ad-Blocking): Download the latest Ad-Blocking ZIP installer from THIS thread. Extract "hosts" file (placed in /system/etc inside ZIP file), then copy it to /data/devbase/system/etc, set rw-r--r-- (644) permissions and then reboot device
Example 2 (modded SystemUI): Create "SystemUI" directory in /data/devbase/system/priv-app and then put modified "SystemUI.apk" file into it. Set rwxr-xr-x (755) permissions to "SystemUI" directory, rw-r--r-- (644) permissions to "SystemUI.apk" and then reboot device
Example 3 (De-Bloating a bit more): You can just create empty directories in /data/devbase/system/app (or priv-app) corresponding to applications in /system/app (or priv-app). Alternatively (more advanced method), you can add an app to modded enforceskippingpackages.txt file (you can find it in /data/devbase/system/etc or /data/devbase/system/csc_contents, depending on the original location in /system) and increase number in the 1st line. Second method should not be used by beginners (without a basic knowledge related to UNIX text format)
3. How to manually maintain the newest ROM version:
If you do not care about OTA - you can manually update your device to the newest ROM available @ Sammobile, keeping your original CSC (you need multi-file original FW, I mean separate files for BL/AP/CP/CSC). You need to download 2 ROMs: ROM with the newest changelist and the latest ROM containing your original CSC. Extract both and open in PC Odin BL/AP/CP files from the ROM with highest changelist but open CSC file from the ROM containing your CSC (I recommend to use HOME_CSC_* file to avoid auto-wipe-data). Flash such "mix", re-root and enjoy

Reserved

hello，alexdr
how are you?
i had flashed your nice rom in s5
do you make. rom for s6 edge plus?

_alexndr said:
Download
>> Recent SYSTEMLESS DevBase <<
Click to expand...
Click to collapse
I'm a little bit confused as the download link refers to S7edge SM-G935F

Androidwizzard said:
I'm a little bit confused as the download link refers to S7edge SM-G935F
Click to expand...
Click to collapse
Yes, agrees - DL link refers to S7edge, but only because there is no just "Samsung" device (generally, without number) to choose @ AndroidFileHost
That's why I put such big NOTE at the top of post #1:
SYSTEMLESS DevBase has been developed and physically tested on S7 Edge (G935F), so main thread containing the most detailed description you can find here:
>> [SAMSUNG][6.0+] SYSTEMLESS DevBase | Encryption support | Stock OTA updates <<
However, it should work on ALL SAMSUNG DEVICES running Android 6.0+, so if you are Galaxy S6 Edge+ (G928xx) owner - please place your feedback & discussion here to let me know about device-specific issues or to let me know that everything works perfect
Click to expand...
Click to collapse

merry xmas ,mate
alexndr

There is new version available
Changelog
v1.1:
- Added SYSTEMLESS support for /system/framework
- Added SYSTEMLESS support for /system/build.prop (overrides & additions)
- Added major Android update detection (auto-remove mods for older API to prevent bootloops & FCs)
- Added BusyBox bionic (the most stable and respected release)
- Added logging to /data/devbase/last_boot.log (API & errors)
- Added SuperSU boot patcher version checker (exits su.d boot script if < 2.76)
- Added "Please DO NOT wipe /cache" warning in case of encrypted devices and TWRP recovery
- Minor changes & optimizations in the shell code
- Added SYSTEMLESS DevBase uninstaller
Download link:
>> SYSTEMLESS_DevBase_v1.1.zip <<
Since new version has many more features -> there are more possibilities of bootloop (especially if you are playing with framework mods). I have created DevBase remover to let you get out from bootloop. Of course uninstaller does NOT "know" which mod caused the problem, so it will not remove any file from /data/devbase directory, it will remove only /su/su.d/0000000devbase boot script to make your device bootable (again) so you can manually delete problematic mod:
>> SYSTEMLESS_DevBase_remover.zip <<

Another update:
v1.3:
- Fixed CscFeature MOD (e.g. G920I case, now should work with all Samsung devices/variants)
v1.2:
- Added info in Settings/About device/Software info/Build number (can be overrided by editing /data/devbase/system/build.prop)
- unroot2ota: added ability to restore stock recovery using /system/recovery-from-boot.p file (no guarantee)
- unroot2ota: check /system partition for common modifications before unroot
- Minor changes & improvements in the shell code
>> SYSTEMLESS_DevBase_v1.3.zip <<

DEV ,
tahnks for your hard work .
can you make a s7 edge nougat mod for samsung s6 edge plus ?

Huawei P8 GRA [ROM][6.0][EMUI 4.0.3][b399]MagicArrow-v3

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Huawei P8 Custom ROM
*MagicArrow*
3.Version
based on Huawei EMUI European Firmware b399
Magisk-Edition and SuperSU-Edition
Teamwork by Tecalote and KangV
Release-Date: 15.02.2018
Status: stable
Tested and developed on: GRA-L09 c432
should work also on: GRA-UL10 und GRA-UL00
flashed over Firmware: b399 und b398 - clean und dirty
cust in this ROM: only for c432
(if somebody need, I can make cust-patches for other regions)
German-Thread: https://www.android-hilfe.de/forum/root-custom-roms-modding-fuer-huawei-p8.2257/huawei-p8-gra-b399-rom-6-0-emui-4-0-3-magicarrow-v3-bytecalote.866753.html
Known issues/not really a Bug:
A) AdAway is working as preinstalled apk for blocking ads (just enable it after first start) - but if you want to use TCPDUMP or Webserver, please install this apk over the existing one in the ROM as Update: https://androidfilehost.com/?fid=313042859668275788
B) If you flash clean and setup-assistant ask you for WLan Network Connection and you cancle it for the moment - it occurs sometimes on the Magisk Edition an error message like: "No SIM Card found - shoutdown or confirm..." - You just go to confirm and in the next second your SIM Network will be recogniced
C) If you install a new App or change something in settings you may receive from time to time a message: "Dropezone for K-Settings blocked... you can add K-Settings in Phonemanager to Dropezone Apps..." But it is not possible to add K-Settings into Dropezone in European Cust (because Phonemanager does not allow...) So, just ignore this message
Requirements:
- Huawei P8 GRA Phone without branding and with Unlocked Bootloader
- not flashable over Android 5 Lollipop
- for best results: Latest possible Android 6 Firmware for your device
- ore if you come from MagicArrow v2 or v1
- read Install-Instructions
- latest TWRP (see Download-Section)
Features/Infos:
- K-Settings by KangV for b399
- Viper4Android and DolbyAtmos with preinstalled Driver, working with Huawei Musicplayer (and with other Players)
- all the other Apps I have included are uninstallable with native settings /Apps (you dont need systemapp-remover!)
- PMPlus and Kernel Audiutor Mod (reborn) for Advanced Users (just uninstall with settings /Apps, if you dont know what to do with this apps)
- Kernel Audiutor can emulate init.d (without loose green safetynet)
- PMPlus can enable App-Auto-Launch in Phonemanager (but its not easy to configure!!)
Phone Manager and the app PMPlus:
Phone Manager does not include the Autostart Manager in European Firmware. The advantage is: you do not have to worry about anything, everything is controlled automatically - and also works. But the battery consumption is slightly more, since all apps wait in the background to be called.
With the app PMPlus, you can activate the Autostart Manager in the Phone Manager. To do this, start the app, go to Installation and as soon as the succesful message comes, close the app (can be uninstalled thereafter). Now, on screen two of the Phone Manager, the entry "App auto-launch" appears!
But NOTICE - through this upgrade will initially set ALL Autostarts to 0 ! You must manually enable the most important apps in App auto-launch - all apps that should receive push notifications - and, most importantly, SuperSU in the Classic Edition and Magisk Manager in the Magisk edition. Otherwise Root permissions do not work!
Advantage: You have control over which apps should not start at system start or in the background (if you need it rarely)
But you must always remember to activate a newly installed app there if necessary. Example: Amazon, E-Bay, PayPal - some of these apps are coupled and not only need the autostart to work , but also the so-called " app activation " (which appears in Autostart Manager when such apps are installed)
Disadvantage: If the apps are not configured correctly in the mask, you have more trouble than good. So, if you're not control freaks, then let's keep your fingers out of it.
But if you want to activate this function, it is recommended to do it at the end, if you have already installed all the apps you are using and not before!
- Facebook lite (original): I recommend to use this App instead of the BigBrother App Facebook - because it saves a lot of battery on Huawei P8!
- most of Google Apps from system are deleted, only the required Core-Apps not - so if you need more Google Apps - dont flash any GApps, just install it with Playstore (like Maps, Google Play Music.... )
- some nice Designs/Themes onboard (Themes will be copied to your internal storage/HWThemes - you can delete what you dont need)
- App-Clone is supported (in Huawei Launcher)
- VoLTE can be enabled in mobile network settings (if your Provider / SIM support it)
- Magisk-Edition: Magisk 15.3 with Magisk Manager 5.6.0 (please enable Magisk Manager as protected App in Phonemanager)
- Magisk Manager comes with pre-enabled settings for safetynet, dont change them. For example: AdAway works now without systemless host setting in Magisk Manager!
- Enabling systemless host in Magisk Manager Settings would break safetynet!
- Magisk v16 Update available - do it with this steps: https://forum.xda-developers.com/showpost.php?p=75656403&postcount=22
Do not update yet to Magisk v16.1 - it would cause big problems - I will provide a patch zip for the update
- You dont need Universal Safetynet Fix anymore - it break safetynet
- If you install Apps which requires safetynet, enable them first in Magisk Hide before you start them first time.
- Busybox 1.27.2 stable by YashdSaraf and SELinux Permissive Script installed as Magisk Module (required)
- In Superuser Section of Magisk Manager is one component pre-allowed for Root-Rights: com.android.inputdevices (its for communication between Magisk and KangV settings)
- If you receive Root-Request from Kernel Audiutor or another Huawei App if you have uninstalled Kernel Audiutor App - then allow this Root Request too
- The system-partition in Magisk Edition must be untouched after Rom Installation, or you loose cts and basicintegrity=true
- means: dont delete or change anything in system partition (with Root Explorer or system-app remover)
- Xposed Framework systemless by topjohnwu (SDK 23) can work with this Rom (not installed) - but it breaks safetynet!
- SuperSU-Edition: SuperSU 2.82 SR5 with modified launch_daemonsu.sh (for SELinux permissive and init.d support - note: you dont need to enable init.d with Kernel Audiutor in SuperSU-Edition)
- SuperSU-Root systemless with boot.img patching (Phone cancle first reboot after ROM Installation and boot up twice)
- Please enable SuperSU App in Phonemanager /Akkumanager as protected App!
- Known issues: In MagicArrow v1 was SuperSU-Root in system - this can make problems if you update directly to MagicArrow v3, because of the CR-Backup Script in v1. MagicArrow v1 must be 100% unrooted before installing v3
- Busybox 1.27.2 stable by YashdSaraf installed to su/xbin
- Xposed Framework v89 by rovo89 integrated in K-Settings /Xposed Settings: If you like to enable just use button "Install xposed" and confirm (same, if you want to uninstall Xposed Framework...)
- First reboot after Xposed Installing needs about 20 min
- PCB (Perfect Color Bar) module comes together with Xposed Framework (but its not enabled - enable it in Xposed Installer, if you like or uninstall it in settings/ apps...)
Download ROM:
P8-b399_MAv3-magisk.zip: https://www.androidfilehost.com/?fid=890129502657583539
MD5: 0394de70a5c3765914371ba4f5f0164b
FIX for the Network-Information-Query (for both Editions): https://forum.xda-developers.com/showpost.php?p=76416139&postcount=167
P8-b399_MAv3-supersu.zip: https://www.androidfilehost.com/?fid=818070582850493154
MD5: 27074686bfff020977ec09e68f80b0fe
You need this Version of TWRP: twrp-3.1.1-0-grace.img
- if you dont have it already... : https://eu.dl.twrp.me/grace/twrp-3.1.1-0-grace.img
Installation-Guide:
1) Make a TWRP Backup from your current system just for to be sure - use latest TWRP!
2) If you decide to flash clean or dirty, in both cases - Backup your stuff
3) IF YOUR CURRENT SYSTEM IS ROOTED - you must flash Unroot Script with TWRP
- For Magisk use Magisk Uninstaller: http://tiny.cc/latestuninstaller
- for SuperSU use UPDATE-unSU-signed.zip: https://forum.xda-developers.com/showpost.php?p=63615067
4) Soon you flashed Unroot Script, go back to main menu to WIPE /ADVANCED WIPE
- if you want to flash dirty, then wipe: Dalvik/ARTCache - Cache - Cust - System
- if you want to flash clean, then wipe: Dalvik/ARTCache - Cache - Cust - Data - System
5) After wipes flash MagicArrow-ROM and soon its finished, reboot your Phone without wipe Dalvik/Cache (Wipes must be done before flashing!)
6) Note - first Reboot can take up to 20 min, so stay tuned and trink some coffee, tea or beer
Disable Chinese Letters:
The Rom is European, but the K-Settings are from KangV. Thats why the Lunar component is installed in K-Settings (these are the only Chinese letters in this Rom).
To disable Lunar, go to K-Settings:
1) Lockscreen and desktop settings and disable: "Lunar Calendar" and at "Desktop weather lunar"
2) Notification settings - disable: "Show statusbar lunar"
Save Battery:
- NFC (with Google Pay) ist enabled by default - disable it and enable it only for the time you need it
- Location Settings (menu: scan settings) disable WLan and Bluetooth Search while Wlan and Bluetooth is disabled, Navi Apps are working also without this setting.
- You can change Location Service to WLan and mobile Network and enable GPS only if you need it
- Performance is enabled by default - change this in Akku-Manager (part of Phone Manager) to SMART
- Bluetooth enable it - if you use it and disable it - if you dont need it at the moment
- Close Apps in the background you dont use at the moment
Have much fun with this ROM​​​
Many thanks to KangV for his K-Settings Framework
If you like K-Settings - please support KangV: https://www.paypal.me/KangVIP
If you like MagicArrow, you can support this project here: https://www.paypal.me/Tecalote
Many thanks and credits:
@guitarededhero (Viper/Atmos) https://forum.xda-developers.com/nexus-6/themes-apps/viper4android-t2952137
@wanam and @rovo89 and @DVDandroid for the Xposed Framework Development
@HootanParsa (MiXplorer) and @YashdSaraf (BusyBox arm64)
@topjohnwu (systemless Xposed Framework and Magisk)
@Chainfire - SuperSU
@AD2076 for TWRP-Recovery twrp-3.1.1-0-grace.img for Huawei p8 marshmallow
@Blackball - BlackPyramid Theme and Custom Roms for P8 - P9 - P10 - P10 Plus - Mate 9
​

reserved for updates

reserved for additional Guides

Tecalote said:
Huawei P8 Custom ROM
*MagicArrow*
3.Version
based on Huawei EMUI European Firmware b399
Magisk-Edition and SuperSU-Edition
Teamwork by Tecalote and KangV
Release-Date: 15.02.2018
Status: stable
Tested and developed on: GRA-L09 c432
should work also on: GRA-UL10 und GRA-UL00
flashed over Firmware: b399 und b398 - clean und dirty
cust in this ROM: only for c432
(if somebody need, I can make cust-patches for other regions)
German-Thread:https://www.android-hilfe.de/forum/...ui-4-0-3-magicarrow-v3-bytecalote.866753.html
Known issues/not really a Bug:
A) AdAway is working as preinstalled apk for blocking ads (just enable it after first start) - but if you want to use TCPDUMP or Webserver, please install this apk over the existing one in the ROM as Update: https://androidfilehost.com/?fid=313042859668275788
B) If you flash clean and setup-assistant ask you for WLan Network Connection and you cancle it for the moment - it occurs sometimes on the Magisk Edition an error message like: "No SIM Card found - shoutdown or confirm..." - You just go to confirm and in the next second your SIM Network will be recogniced
C) If you install a new App or change something in settings you may receive from time to time a message: "Dropezone for K-Settings blocked... you can add K-Settings in Phonemanager to Dropezone Apps..." But it is not possible to add K-Settings into Dropezone in European Cust (because Phonemanager does not allow...) So, just ignore this message
Requirements:
- Huawei P8 GRA Phone without branding and with Unlocked Bootloader
- not flashable over Android 5 Lollipop
- for best results: Latest possible Android 6 Firmware for your device
- ore if you come from MagicArrow v2 or v1
- read Install-Instructions
- latest TWRP (see Download-Section)
Features/Infos:
-K-Settings by KangV for b399
-Viper4Android and DolbyAtmos with preinstalled Driver, working with Huawei Musicplayer (and with other Players)
- all the other Apps I have included are uninstallable with native settings /Apps (you dont need systemapp-remover!)
- PMPlus and Kernel Audiutor Mod (reborn) for Advanced Users (just uninstall with settings /Apps, if you dont know what to do with this apps)
- Kernel Audiutor can emulate init.d (without loose green safetynet)
- PMPlus can enable App-Auto-Launch in Phonemanager (but its not easy to configure!!)
Phone Manager and the app PMPlus:
Phone Manager does not include the Autostart Manager in European Firmware. The advantage is: you do not have to worry about anything, everything is controlled automatically - and also works. But the battery consumption is slightly more, since all apps wait in the background to be called.
With the app PMPlus, you can activate the Autostart Manager in the Phone Manager. To do this, start the app, go to Installation and as soon as the succesful message comes, close the app (can be uninstalled thereafter). Now, on screen two of the Phone Manager, the entry "App auto-launch" appears!
But NOTICE - through this upgrade will initially set ALL Autostarts to 0 ! You must manually enable the most important apps in App auto-launch - all apps that should receive push notifications - and, most importantly, SuperSU in the Classic Edition and Magisk Manager in the Magisk edition. Otherwise Root permissions do not work!
Advantage: You have control over which apps should not start at system start or in the background (if you need it rarely)
But you must always remember to activate a newly installed app there if necessary. Example: Amazon, E-Bay, PayPal - some of these apps are coupled and not only need the autostart to work , but also the so-called " app activation " (which appears in Autostart Manager when such apps are installed)
Disadvantage: If the apps are not configured correctly in the mask, you have more trouble than good. So, if you're not control freaks, then let's keep your fingers out of it.
But if you want to activate this function, it is recommended to do it at the end, if you have already installed all the apps you are using and not before!
- Facebook lite (original): I recommend to use this App instead of the BigBrother App Facebook - because it saves a lot of battery on Huawei P8!
- most of Google Apps from system are deleted, only the required Core-Apps not - so if you need more Google Apps - dont flash any GApps, just install it with Playstore (like Maps, Google Play Music.... )
- some nice Designs/Themes onboard (Themes will be copied to your internal storage/HWThemes - you can delete what you dont need)
- App-Clone is supported (in Huawei Launcher)
- VoLTE can be enabled in mobile network settings (if your Provider / SIM support it)
- Magisk-Edition: Magisk 15.3 with Magisk Manager 5.6.0 (please enable Magisk Manager as protected App in Phonemanager)
- Magisk Manager comes with pre-enabled settings for safetynet, dont change them. For example: AdAway works now without systemless host setting in Magisk Manager!
- Enabling systemless host in Magisk Manager Settings would break safetynet!
- You dont need Universal Safetynet Fix anymore - it break safetynet
- If you install Apps which requires safetynet, enable them first in Magisk Hide before you start them first time.
- Busybox 1.27.2 stable by YashdSaraf and SELinux Permissive Script installed as Magisk Module (required)
- In Superuser Section of Magisk Manager is one component pre-allowed for Root-Rights: com.android.inputdevices (its for communication between Magisk and KangV settings)
- If you receive Root-Request from Kernel Audiutor or another Huawei App if you have uninstalled Kernel Audiutor App - then allow this Root Request too
- The system-partition in Magisk Edition must be untouched after Rom Installation, or you loose cts and basicintegrity=true
- means: dont delete or change anything in system partition (with Root Explorer or system-app remover)
- Xposed Framework systemless by topjohnwu (SDK 23) can work with this Rom (not installed) - but it breaks safetynet!
- SuperSU-Edition: SuperSU 2.82 SR5 with modified launch_daemonsu.sh (for SELinux permissive and init.d support - note: you dont need to enable init.d with Kernel Audiutor in SuperSU-Edition)
- SuperSU-Root systemless with boot.img patching (Phone cancle first reboot after ROM Installation and boot up twice)
- Please enable SuperSU App in Phonemanager /Akkumanager as protected App!
- Known issues: In MagicArrow v1 was SuperSU-Root in system - this can make problems if you update directly to MagicArrow v3, because of the CR-Backup Script in v1. MagicArrow v1 must be 100% unrooted before installing v3
- Busybox 1.27.2 stable by YashdSaraf installed to su/xbin
- Xposed Framework v89 by rovo89 integrated in K-Settings /Xposed Settings: If you like to enable just use button "Install xposed" and confirm (same, if you want to uninstall Xposed Framework...)
- First reboot after Xposed Installing needs about 20 min
- PCB (Perfect Color Bar) module comes together with Xposed Framework (but its not enabled - enable it in Xposed Installer, if you like or uninstall it in settings/ apps...)
Download ROM:
P8-b399_MAv3-magisk.zip: https://www.androidfilehost.com/?fid=890129502657583539
MD5: 0394de70a5c3765914371ba4f5f0164b
P8-b399_MAv3-supersu.zip: https://www.androidfilehost.com/?fid=818070582850493154
MD5: 27074686bfff020977ec09e68f80b0fe
You need this Version of TWRP: twrp-3.1.1-0-grace.img
- if you dont have it already... : https://eu.dl.twrp.me/grace/twrp-3.1.1-0-grace.img
Installation-Guide:
1) Make a TWRP Backup from your current system just for to be sure - use latest TWRP!
2) If you decide to flash clean or dirty, in both cases - Backup your stuff
3) IF YOUR CURRENT SYSTEM IS ROOTED - you must flash Unroot Script with TWRP
- For Magisk use Magisk Uninstaller: http://tiny.cc/latestuninstaller
- for SuperSU use UPDATE-unSU-signed.zip: https://forum.xda-developers.com/showpost.php?p=63615067
4) Soon you flashed Unroot Script, go back to main menu to WIPE /ADVANCED WIPE
- if you want to flash dirty, then wipe: Dalvik/ARTCache - Cache - Cust - System
- if you want to flash clean, then wipe: Dalvik/ARTCache - Cache - Cust - Data - System
5) After wipes flash MagicArrow-ROM and soon its finished, reboot your Phone without wipe Dalvik/Cache (Wipes must be done before flashing!)
6) Note - first Reboot can take up to 20 min, so stay tuned and trink some coffee, tea or beer
Disable Chinese Letters:
The Rom is European, but the K-Settings are from KangV. Thats why the Lunar component is installed in K-Settings (these are the only Chinese letters in this Rom).
To disable Lunar, go to K-Settings:
1) Lockscreen and desktop settings and disable: "Lunar Calendar" and at "Desktop weather lunar"
2) Notification settings - disable: "Show statusbar lunar"
Save Battery:
- NFC (with Google Pay) ist enabled by default - disable it and enable it only for the time you need it
- Location Settings (menu: scan settings) disable WLan and Bluetooth Search while Wlan and Bluetooth is disabled, Navi Apps are working also without this setting.
- You can change Location Service to WLan and mobile Network and enable GPS only if you need it
- Performance is enabled by default - change this in Akku-Manager (part of Phone Manager) to SMART
- Bluetooth enable it - if you use it and disable it - if you dont need it at the moment
- Close Apps in the background you dont use at the moment
Have much fun with this ROM
Many thanks to KangV for his K-Settings Framework
If you like K-Settings - please support KangV:https://www.paypal.me/KangVIP
If you like MagicArrow, you can support this project here:https://www.paypal.me/Tecalote
Many thanks and credits:
@guitarededhero (Viper/Atmos) https://forum.xda-developers.com/nexus-6/themes-apps/viper4android-t2952137
@wanam and @rovo89 and @DVDandroid for the Xposed Framework Development
@HootanParsa (MiXplorer) and @YashdSaraf (BusyBox arm64)
@topjohnwu (systemless Xposed Framework and Magisk)
@Chainfire - SuperSU
@AD2076 for TWRP-Recovery twrp-3.1.1-0-grace.img for Huawei p8 marshmallow
@Blackball - BlackPyramid Theme and Custom Roms for P8 - P9 - P10 - P10 Plus - Mate 9
Click to expand...
Click to collapse
fantastic friend, newly installed, all good without any problem, dirty installation to not lose data, test and I will inform, thank you very much again

hey there
congratz to your new rom, well done!
quick question:
after flash my gallery, files and music app lost the abilty to showme my files..
and i allready figured out thats a problem withthe media-Provider-app
buuuut i cant fix it..
any ideas???
regards

Nice job work fine thanks

Rasenverbraucheramt said:
hey there
congratz to your new rom, well done!
quick question:
after flash my gallery, files and music app lost the abilty to showme my files..
and i allready figured out thats a problem with the media-Provider-app
buuuut i cant fix it..
any ideas???
regards
Click to expand...
Click to collapse
I like to know which Gallery and which music App did you flash and which files ? And which path did you use (which App into which directory?) Did you delete the original Huawei Musicplayer/Mediacenter and the original Huawei Gallery?

lespaul79 said:
fantastic friend, newly installed, all good without any problem, dirty installation to not lose data, test and I will inform, thank you very much again
Click to expand...
Click to collapse
Your welcome my friend

Tecalote said:
Your welcome my friend
Click to expand...
Click to collapse
Thank You, Tecalote!
I'll upgrade from MagicArrow v1 (!) one of the following weekends (I have to force myself to backup everything first ).
Quick question about the upgrading instruction you wrote:
- I want to do a clean install from v1 (b391): don't I have to reflash an official b399 first to update baseband/etc??? I hope not!

hello
my device p8 last update
GRA-UL10_C185B391 ?

aswertya said:
hello
my device p8 last update
GRA-UL10_C185B391 ?
Click to expand...
Click to collapse
The last Firmware is from December 2016 - b382 for c185. There's no newer Update available for c185
You must not update your Firmware, just do steps from OP

chros69 said:
Thank You, Tecalote!
I'll upgrade from MagicArrow v1 (!) one of the following weekends (I have to force myself to backup everything first ).
Quick question about the upgrading instruction you wrote:
- I want to do a clean install from v1 (b391): don't I have to reflash an official b399 first to update baseband/etc??? I hope not!
Click to expand...
Click to collapse
If you really want to do it complete clean, you should flash for L09c432 Full Firmware b399 with Factoryreset after.
I will write in #2 how to do with links and so on...

All perfect my friend

I have version 2 arrow magisk instaled,the correctway to update is uninstall magisk and after that flash with version 3 arrow magisk?

Cientista2018 said:
I have version 2 arrow magisk instaled,the correctway to update is uninstall magisk and after that flash with version 3 arrow magisk?
Click to expand...
Click to collapse
Yes just do Install Guide from Post #1 of this Thread (OP)

I've got GRA-UL00 with MagicArrow v2. Just updated it to v3 (dirty install), works fine.
I'm using version with SuperSU but thinking to switch over to Magisk. Do i need some additional steps than unroot, wipe and flash magisk version?

Thanks for the ROM. Is the missing 2G only option because it's not in the base ROM?
3G/HSDPA seem to display correctly now. I like having the option to force 2G only as there are a couple of areas where the 4G and 3G signal is very low.
Again, thanks for the ROM.

Morun said:
I've got GRA-UL00 with MagicArrow v2. Just updated it to v3 (dirty install), works fine.
I'm using version with SuperSU but thinking to switch over to Magisk. Do i need some additional steps than unroot, wipe and flash magisk version?
Click to expand...
Click to collapse
No additional steps, just as you said

beardedwonder said:
Thanks for the ROM. Is the missing 2G only option because it's not in the base ROM?
3G/HSDPA seem to display correctly now. I like having the option to force 2G only as there are a couple of areas where the 4G and 3G signal is very low.
Again, thanks for the ROM.
Click to expand...
Click to collapse
I have 2G only, 3G only, 2G/3G automatic and 4G/3G/2G automatic... (see screenshot) - but I have updated Firmware before installing the Rom.

Tecalote said:
I have 2G only, 3G only, 2G/3G automatic and 4G/3G/2G automatic... (see screenshot) - but I have updated Firmware before installing the Rom.
Click to expand...
Click to collapse
Which firmware are you on? I'm willing to do a full backup and install of that firmware then your ROM as I've had some dropped calls.

[MODULE] Safe Mode (Bootloop/Bootscreen/Blackscreen Solver For Apps)

It Is Now A Part Of The Main Module Of MultiFunctions & Its Thread https://forum.xda-developers.com/apps/magisk/module-multifunctions-bootloop-t3933386.
Click to expand...
Click to collapse
Introduction:
Simple Module To Boot The Android Into Safe Mode.
- In-Case Of Facing A Bootloop Issue Due To Installing/Configuring An App, Flash This Module
- This Module Disables All Installed Apps (User Apps) & Also The Root Access By Enabling Safe Mode & After Booting, Uninstall Any App Which Caused The Bootloop/Issue (From Settings --> Apps --> The App --> Storage --> Clear Cache --> Clear Data --> Uninstall) Then Reboot (Rebooting The Android Is Required To Get Back To The Normal Mode)
- Safe Mode Gives The Device The Ability To Not Open Any App Which Is Installed As A User App, And A "Safe Mode" Badge Will Appear In The Lower Left Corner Of The Screen
- After The Installation & Booting, It Puts The Android In Safe Mode & Disables Itself
- Enabling This Module = Doing Its Functionality & Disabling Itself (Next Reboot)
Current Version: 1.0.3.3
- For Magisk Users, Disable Magisk Core Only Mode From The Section Of Settings In Magisk Manager Which Is Required As An Essential Step To Activate The Functionality Of SafeMode
- For Activating The Functionality Of SafeMode, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> SafeMode --> Delete The File Of Disable From The Folder Of Active --> Reboot
- For Using The Module Thru ADB Shell/TWRP Terminal [The Module Must Be Pre-Installed Via Magisk Manager/TWRP Recovery/ADB Sideload], Write The Following Commands --> rm -f /data/DreamerMods/MultiFunctions/SafeMode/Active/disable (Click On Enter) --> reboot (Click On Enter)
Created: Sept.26.2018
Updated: May.09.2019
Download Link: Click Here
- For The Module Which Is Ended Its Name With v1300, It Supports Magisk v13.1(1310) To v13.6(1360)
- For The Module Which Is Ended Its Name With v1400, It Supports Magisk v14.0(1400) To v15.3(1531)
- For The Module Which Is Ended Its Name With v1500, It Supports Magisk v15.0(1500) To v17.3(17300)
- For The Module Which Is Ended Its Name With v17000, It Supports Magisk v17.0(17000) To v17.3(17300)
- For The Module Which Is Ended Its Name With v18000, It Supports Magisk v18.0(18000) To v18.1(18100)
- For The Module Which Is Ended Its Name With v19000, It Supports Magisk v19.0(19000) To The Latest Version
- For The Module Which Is Ended Its Name With Unity, It Supports Any-Rooting-Tool Such As SuperSU, Lineage-AddOnSU & Magisk
Installation:
- Flash It Thru TWRP Recovery
- Or Magisk Manager --> Modules --> Add (+) --> Choose The Downloaded File --> Reboot
- Or Flash It Thru ADB Sideload --> adb sideload Module.zip --> Reboot
- Or Using A Flash-Tool (Flasher) Such FlashFire, Flashify Or Rashr --> Flash ZIP File (Flash A Flashable ZIP File) --> Choose The Downloaded File --> Reboot
General Info:
- To Disable The Module For Magisk Users, Open Magisk Manager --> Modules --> The Module --> Tap On The Check Box/The True Icon --> Reboot
- To Enable The Module For Magisk Users, Open Magisk Manager --> Modules --> The Module --> Tap On The Uncheck Box --> Reboot
- To Uninstall The Module For Magisk Users, Open Magisk Manager --> Modules --> The Module --> Tap On The Bin Icon --> Reboot
- To Disable The Module For All Users [Non-Magisk Users & Magisk Users], Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> The Module --> Copy The File Of Disable To The Folder Of Active (Or Delete The File Of Disable From The Folder Of Inactive) --> Reboot
- To Enable The Module For All Users [Non-Magisk Users & Magisk Users], Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> The Module --> Delete The File Of Disable From The Folder Of Active (Or Copy The File Of Disable To The Folder Of Inactive) --> Reboot
- To Uninstall The Module For All Users [Non-Magisk Users & Magisk Users] (Unity), Reflash The Module
- In-Case Of Facing A Bootloop/Bootscreen/Blackscreen Issue Due To Adding App/Activity/Process To Magisk Hide, Download ClearHideList4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/module-hide-list-bootloop-bootscreen-t3849208 Then Flash It
- In-Case Of Facing A Bootloop/Bootscreen/Blackscreen Issue Due To Flashing A Module, Download CoreOnlyMode4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/module-core-mode-bootloop-solver-modules-t3817366 Then Flash It
Click On Thanks Button If The Module/Post Is Useful (Dreamer(3MF))
>>> Sharing A Good Thought Is Gold <<<
----------------------------------------------------------------------------------------------------------------
SELinux Mode Inverter - Clear Dalvik Cache - Core Only Mode - Other Modules
----------------------------------------------------------------------------------------------------------------

Reserved for News/Updates #1

Reserved for News/Updates #2

Cool!! Look like I gave you some idea, for a proper Safe Mode Module, for the whole Android system.
The other was a Safe Mode, kind , for only Magisk.
Cool to can boot Android in Safe Mode, just by flash a zip thru TWRP, as getting in Safe Mode with hard keys is very frustrating...
Anyway both goes to my ToolBox.
:good:

saoudien07 said:
Cool!! Look like I gave you some idea, for a proper Safe Mode Module, for the whole Android system.
The other was a Safe Mode, kind , for only Magisk.
Cool to can boot Android in Safe Mode, just by flash a zip thru TWRP, as getting in Safe Mode with hard keys is very frustrating...
Anyway both goes to my ToolBox.
:good:
Click to expand...
Click to collapse
P.S. CoreOnlyMode4Magisk Is For Uninstalling/Disabling Magisk Modules Which Caused The Booloop/Bootscreen Issue But SafeMode4Magisk Is For Uninstalling User Apps & Also Clearing Cache&Data Of User/System Apps Which Caused The Booloop/Bootscreen Issue

Dreamer(3MF) said:
P.S. CoreOnlyMode4Magisk Is For Uninstalling/Disabling Magisk Modules Which Caused The Booloop/Bootscreen Issue But SafeMode4Magisk Is For Uninstalling User Apps & Also Clearing Cache&Data Of User/System Apps Which Caused The Booloop/Bootscreen Issue
Click to expand...
Click to collapse
Yep I got well
One is for Magisk, BootLoop caused by guilty Magisk Modules, so possibility to remove them >>> CoreOnlyMode
And SafeMode, is for the Android OS itself, so App guilty BootLoop.
Hope it may help other, our litle chat

Hi, I have a problem I enabled core mode in the magisk manager menu to bypass safety, restarted it worked I logged into the app. But then i disabled the core only mode and rebooted my phone booted the first screen where it says Samsung but won't go into the boot loading screen. The LED Light is on but the screen is just black and doesn't change. I flashed this zip to re-enable the core only mode and my phone will boot but I can't disable core only without it getting stuck on a black screen. Any help would be appreciated

Apexpredator12 said:
Hi, I have a problem I enabled core mode in the magisk manager menu to bypass safety, restarted it worked I logged into the app. But then i disabled the core only mode and rebooted my phone booted the first screen where it says Samsung but won't go into the boot loading screen. The LED Light is on but the screen is just black and doesn't change. I flashed this zip to re-enable the core only mode and my phone will boot but I can't disable core only without it getting stuck on a black screen. Any help would be appreciated
Click to expand...
Click to collapse
This Thread Is For SafeMode4Magisk Not CoreOnlyMode4Magisk But Anyway Check This Post From The Thread Of CoreOnlyMode4Magisk.
Dreamer(3MF) said:
Introduction:
Simple Module To Open Magisk In Core Only Mode To Help For Removing Any Module Which Causes A Bootloop.
- In-Case Of Facing A Bootloop Issue Due To Flashing A Module, You Need To Put A Copy Of CoreOnlyMode4Magisk On SD-Card/Internal Memory Then Flash This Module Thru TWRP Recovery
- This Module Disables All Magisk Modules By Enabling Magisk Core Only Mode & After Booting, You Can Disable Magisk Core Only Mode From The Section Of Settings In Magisk Manager Then Removing/Disabling The Module(s) Which Caused The Bootloop/Issue From The Section Of Modules In Magisk Manager Then Reboot (Rebooting The Android Is Required To Load The Rest Of Modules)
Click to expand...
Click to collapse

Cool module thankyou.

Updated SafeMode4Magisk To v1.0.0A!
Changelog: Checking The Paths
- For The Module Which Is Ended Its Name With v1300, It Supports Magisk v13.1(1310) To v13.6(1360)
- For The Module Which Is Ended Its Name With v1400, It Supports Magisk v14.0(1400) To v15.3(1531)
- For The Module Which Is Ended Its Name With v1500, It Supports Magisk v15.0(1500) To The Latest Version Which Is Currently v17.2(17200)
- For The Module Which Is Ended Its Name With v17000, It Supports Magisk v17.0(17000) To The Latest Version Which Is Currently v17.2(17200)

Updated MultiFunctions4Magisk To 1.0.3.3!
Changelog: SafeMode Is A Sub-Module Of The Main Module Of MultiFunctions Which Supports Currently The Following Functions [Clearing DalvikCache-PlayStoreWithServices-MagiskHideList, Changing The SELinux Mode, Booting The Android Into Safe Mode & Opening Magisk In Core Only Mode]
- For The Module Which Is Ended Its Name With v1300, It Supports Magisk v13.1(1310) To v13.6(1360)
- For The Module Which Is Ended Its Name With v1400, It Supports Magisk v14.0(1400) To v15.3(1531)
- For The Module Which Is Ended Its Name With v1500, It Supports Magisk v15.0(1500) To v17.3(17300)
- For The Module Which Is Ended Its Name With v17000, It Supports Magisk v17.0(17000) To v17.3(17300)
- For The Module Which Is Ended Its Name With v18000, It Supports Magisk v18.0(18000) To v18.1(18100)
- For The Module Which Is Ended Its Name With v19000, It Supports Magisk v19.0(19000) To The Latest Version
- For The Module Which Is Ended Its Name With Unity, It Supports Any-Rooting-Tool Such As SuperSU, Lineage-AddOnSU & Magisk
Kindly Be Informed That
- For Magisk Users, Disable Magisk Core Only Mode From The Section Of Settings In Magisk Manager Which Is Required As An Essential Step To Activate The Functionality Of SafeMode
- For Activating The Functionality Of SafeMode, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> SafeMode --> Delete The File Of Disable From The Folder Of Active --> Reboot

[MODULE] Modules For SuperSU

Introduction:
Modules For SuperSU
- Download The Module Of MultiFunctionsPlus To Do The Next Functions [Clearing DalvikCache-PlayStoreWithServices-MagiskHideList, Changing The SELinux Mode, Booting The Android Into Safe Mode, Opening Magisk In Core Only Mode, Controlling The Virtual Memory (Swap), Changing The Swappiness Value, Keeping MagiskDaemon-MagiskHide Running, Changing DoubleTap2Wake(DT2W) Status, Fixing PlayStore Device Certification Status - Passing SafetyNet, Enabling The Low Ram Configurations, Disabling The Other Magisk Modules, Disabling The Magisk General Scripts & More] From This Thread https://forum.xda-developers.com/apps/magisk/module-social-media-cache-advanced-t3799155 (Unity Version)
Created: Nov.13.2018
Updated: Dec.23.2019
Download Link: Mentioned In The Above Threads (Download Unity Version)
** Unity Installer: It Supports Any-Rooting-Tool Such SuperSU, Lineage-AddOnSU & Magisk
- P.S. If You Flash The Same Version Of Module Twice, The Module Will Remove Itself But If The Version Of Second Time Is Higher Than The Version Of First Time, The Module Will Update/Upgrade Itself
Installation:
- Flash It Thru A Custom-Recovery Such TWRP Recovery --> Reboot
- Or Flash It Thru ADB Sideload --> adb sideload TheFileNameOfModule.zip --> Reboot (P.S. Renaming The File To Have A Short One Is Recommended Such mfm.zip Before Using ADB Sideload)
- Or Using A Flash-Tool (Flasher) Such EX Kernel Manager, FK Kernel Manager, FlashFire Or Flashify --> Flash ZIP File --> Reboot
>>>Dreamer(3MF)<<<
>>> Sharing A Good Thought Is Gold <<<
----------------------------------------------------------------------------------------------------------------
Other Modules
----------------------------------------------------------------------------------------------------------------

Reserved For News/Updates #1

Reserved For News/Updates #2

Thanks Dreamer!

Reserved For News/Updates #3