Database Develop

[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 [ROM][6.0][EMUI 4.0.3]MagicArrow - Custom ROM European Firmware b398 based

{
"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 *
Version Two
Magisk Edition and Classic Edition
Teamwork by Tecalote and KangV
Based on the European firmware b398 - only installable, if you are already on Marshmallow Firmware (Android 6)
Developed on GRA-L09 C432 - but it should run on all GRA-xxx models and regions due to my modification
Thread for German Users: https://www.android-hilfe.de/forum/root-custom-roms-modding-fuer-huawei-p8.2257/huawei-p8-rom-6-0-emui-4-0-3-magicarrow-v2-by-tecalote.819399.html
Well, you've been waiting long enough I am pleased to present you the new version of Arrow under the extended name "MagicArrow"
1) Difference between Magisk and Classic Edition:
The Magisk Edition was made to have a safteynet capable device that still offers much more features than Stock Firmware ... It has the same features like Classic Edition, with one difference: Outward It looks as if you had not unlocked the bootloader .... Apps like Pokemon Go, various banking apps - which does not work anymore on rooted devices should work in this Rom
However, you can not install Xposed Framework in the Magisk Edition without losing the green safetynet! There is the systemless Xposed Framework by topjohnwu, the developer of Magisk and it works, can be easily downloaded and installed in the Magisk Manager via modules (SDK 23) - but - there is currently no way to pass safetynet with a modified custom Rom together with Xposed Framework! For this reason, the installation pool in K-Settings for Xposed is removed from its function.
Attention: Update the preinstalled Magisk with newer Version 15.3 flashable zip made for this ROM: https://forum.xda-developers.com/showpost.php?p=75178940&postcount=871
Then look in the Thread for new posts about future Updates.
The Classic Editon is rooted with SuperSU and has same features, but you cannot bypass safteynet check. However, who does not run apps depending on this "questionable" service will have the same joy with this Rom. The advantage of the Classic Edition is: You can install from K-Settings Wanams Xposed Framework 87.1 and use a lot of Xposed modules ...
2) Requirements and information for this Rom:
If you want to have the best of this Rom, then it would be necessary to start completely clean - means from Custom Rom back to Stock Firmware b398 - With the exception of devices for which there is no more recent firmware than b370. An EMUI Custom Rom is as good as the before installed Firmware in the background. In principle, only system, cust and kernel will be flashed with the Rom zip. The original Firmware update a lot more, like modem etc. Therefore, the Custom Rom works best if you start from latest firmware for your device on which the Rom is based.
If you have already latest official Huawei Stock Firmware installed, it is less work...
I really dont recommend to flash dirty this Rom directly from Arrow v1 or if you stay on older Firmware. System and Apps will be wiped with the installation script. So you cannot keep your previous apps and data, you have to install them new.
You need the latest TWRP:https://dl.twrp.me/grace/twrp-3.1.1-0-grace.img Do not use older ones!
The bootloader must be unlocked. Pick up the Huawei unlock code, because it is always valid for the same device. If you do not have an unlock code from Huawei and have problems to get it from Huawei Website, recently you can call regional Huawei service hotline and get the code by mail during 24 hours.
3) Installation guide for the MagicArrow:
1) Backup your apps and data from your current Firmware or Rom - but only User-Apps and not System-Apps. You can use Huawei Backup as well as TitaniumBackup. (Dont restore any System-Apps from previous system in the new Rom - example: if you use Huawei Backup dont backup Phonemanager, but you can backup desktop layout, sms, calendar, User-Apps etc.) Dont backup and restore Chat-Apps like WhatsApp, Viber, WeChat, Facebook and so on - use their inbuilt Backup Function like Google Drive Backup (its different, some Apps are storing everything on their server like Telegram) You must install and register Chat-Apps new on your new Rom. If you dont do that, Push-Notifications cannot work.
2) Make a backup of important folders and files from your internal storage (DCIM, WhatsApp folder, Downloads....)
3) Download Firmware update.zip - depending on the device model - and unzipp it on your PC - you receive META-INF and UPDATE.APP
GRA-L09C432B398: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G985/g104/v88316/f1/full/update.zip
GRA-L09 with other Cust: http://hwmt.ru/hwmtsite/firmware-database/?firmware_model=GRA-L09&firmware_page=0
Other GRA models: http://hwmt.ru/hwmtsite/firmware-database/?firmware_model=GRA&firmware_page=0
4) Copy UPDATE.APP and META-INF into a folder on the root directory of your external SD which must have the name: dload
5) If you are on Stock Firmware, not rooted you can directly update your Firmware. But go to step 6
A) If you are on Stock Firmware, but rooted, with TWRP installed and Xposed Framework installed, uninstall first Xposed Framework, reboot to system, after unroot your device, restore original boot.img and flash the original Huawei Stock Recovery.
B) Arrow Editions: If you have Xposed Framework installed, uninstall Xposed Framework, reboot to system (15 min) - after go to step 6
If you are on Arrow v1 Classic Edition without Xposed Framework, flash Huawei Stock Recovery from K-Settings /more settings / flash recovery - flash official recovery. You can reboot directly from here to Stock Recovery.
If you are on Arrow v1 Magisk Edition without Xposed Framework, flash with TWRP Magisk Uninstaller: http://tiny.cc/latestuninstaller and after flash Huawei Stock Recovery b391 (by choosing img): https://www.androidfilehost.com/?fid=529152257862705190
- go to step 6
6) Press Vol+ and Power Button until phone reboot and hold this position until phone boot up to Stock-Recovery. Here you do first "Wipe Cache Partition" and second "Factoryreset" - go to step 7
7) If you start EMUI Update from here, just go to Restart and press Vol+ and Vol- (in the middle down and hold this position), wait until phone reboots and EMUI Software Installing begin (of course, update.app and meta-inf must be already in dload folder)
If you was back in system between you can start update with pressing down Vol+ and Vol- in the middle and at the same time pressing Power Button. Wait until phone reboot and you see Huawei Logo. Now you can release Power button, but you must keep holding all the time the pressing down postion with Vol+ and Vol- until EMUI Software Installing begin. After some time your firmware is updated and restart to system. Dont make an account yet, just make short setup.
8) Open settings /about phone and klick 7 times on build number for enabling developer options. Open developer options and in there enable USB Debugging. After go to settings / (advanced) settings and enable "unknown sources"
9) Connect your device with USB to your PC and let windows install the drivers or install HiSuite (which installs drivers if windows cannot recognice) You need the USB Connection. With Minimal ADB and Fastboot in administrative mode you can flash now the newest TWRP, which I have linked above.
10) Disconnect your device from USB Cable, soon TWRP is succesful flashed
11) With Vol+ and Power Button reboot your device to TWRP - this step is important if you want to keep TWRP
12) Allow system modification and go to ADVANCED WIPE - choose in the first step ONLY internal Storage (nothing else). Do not wipe internal Storage together with the other partitions in step 14! Soon internal storage is wiped, go back to main menu and restart the recovery. You should get the Root Permission request from TWRP "Allow system modification" once again, allow it and open settings to configure (24h clock, language, time zone, etc) If you dont get the Root Permission request from TWRP yet, you will get it after next boot to TWRP.
13) Now copy MagicArrow.zip to your external SD - Attention: If you want the boot sound to be played on the phone - before flashing the Rom, sound must be switched on!
14) Boot to TWRP and go to ADVANCED WIPE - Wipe following partitions:
Dalvik/Art Cache
Cache
Cust
data
system
15) Go back to main menu and flash MagicArrow. After flashing is done, reboot system without wipe of dalvik/cache. As you know, the first boot process can take up to 15 minutes (just like installing the Xposed Framwork)] After boot to system and first setup - you have to make some IMPORTANT STEPS (see next Point) before you restore /installing your apps and adjust your phone.
4) Important information for the Magisk -Edition:
During first setup you may receive a root-rights request, if so, confirm this. After first setup - please do not open the Magisk Manager . Before you do anything else,open settings / about phone and klick 7 times on build number to enable the developer options. Open developer options and in there enable USB debugging! Then go back to Settings - in the b398 there are the extended settings with the short name: Settings. In it, please enable " allow unknown sources "
At this point restart immediately your P8.
Now open the Magisk Manager, the app is looking for updates - to speed this up, drag from first white field (like refresh of a website in Chrome) with the finger pressed down - the manager is up to date. Makes a query of the Safteynet = green.
Then you go in the Magisk-Manager left to the Controll-Pannel to settings. Do not change anything, with one exception: enable systemless hosts! This step is very important. Then immediately the second reboot .
Next open AdAway and activate the hosts file (download files and activate the advertising block) - then the third reboot .
After open AdAway again and see if the hosts file is active, if it is, all well, if not, download the hosts files once again and restart P8. (Sometimes another reboot is necessary at the point) Only when AdAway is green (activated) - then the safetynet is passed by. You can now again check in the Magisk manager safetynet = green - if you do not these steps, you can break the safetynet. In addition, root and apps can be blocked!
As you know, Magisk uses his own superuser, integrated into Magisk Manager
For some reason if you have problems with safetynet with some apps, just download the following module in the Magisk Manager in the Control-Pannel under Download:
Universal Safetynet Fix
Otherwise, please do not download any modules, you do not know if they run and what they do.
Two modules are preinstalled - please leave this, otherwise this Rom does not function properly with K-Settings!
5) Important information for the Classic -Editon:
The Classic edition gets systemless Root during the installation by SuperSU 2.82 SR1 (SR1 has an integrated update for Huawei devices). After Rom is flashed and you restart phone, the first boot process will terminate, the device will restart once again - this is normal because of systemless rooting . Why systemless this time? Because of compatibility with SuperSU. The new versions of SuperSU are rooting always systemless. If there is the next Final version of SuperSU, you need only flash the zip in TWRP and there are no problems with the update.
To enable AdAway , just download the AdAway ad block (hosts file) and reboot the P8 - but after rebooting, please open AdAway again and see if it worked the first time - otherwise just download again and restart the device once more. The second time it fits. AdAway is controlled by the systemless root using an init.d script that mount the hosts file systemlessly and this script is usually only active after the second restart. If you ignore this step, you can block root privileges.
6) Features:
• VoLTE and IP-Calling enabled - disable it, if your mobile provider dont support it!
• Push notifications working - Enable WhatsApp, Telegram... as protected apps and enable Wlan and mobile data during "sleeping mode" as always on
• Most Gapps contained in system debloaded - please dont flash any GApps, just install it with Playstore (Core GApps and settings are present in the Rom)
• System is deodexed
• pre-rooted: Classic Edition by Chainfires SuperSU 2.82 SR1 - Magisk Edition by topjohnwuMagiskSU 13.3
• BusyBox 1.27.1 - Please dont change this BusyBox to any other (not Stericson, not JRummy...)
• Call Recorder - You can enable recording manually, if a call comes through with the memory icon in dialer - or constantly in dialer settings
• Some nice themes, BlackPyramid ...
• K-Settings - as usual with extended restart menu
• MiXplorer (very powerful Root-Explorer) and TitaniumBackup (can store backups without any problem through storage SD instead of document provider)
• Dolby / Atmos for Teamwork with Viper4Android - best experience with BlackPlayer (or similar) but not Huawei Music App
• Security patch level 1 July 2017 - all known Stagefright Security holes are closed
• Multiwindow mode - you can start this mode with long tap on square in navigation bar. Close the Mod in the middle with the turquoise symbol.
• Viper4Android (enable it via K-Settings) can be linked to its settings permanently in notification bar for quick access. - as usual.
• Xposed Framework of Wanam included in K-Settings, Installation start from there, reboots automatically. The Restart needs about 15 minutes.
• VIA Browser instead of Chrome
• AdAway - newest release
• And much more...
7) 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!
8) 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 hide these, 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"
9) Save Battery:
NFC (with Android Pay) ist enabled by default - disable it and enable it only for the time you need it
VoLTE is enabled by default - disable it, if your mobile provider dont support 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.
Performance is enabled by default - change this in Akku-Manager (part of Phone Manager) to SMART
With "auto app-launch" (if you have installed) you can disable Apps which you use just sometimes.
Bluetooth enable it - if you use it and disable it - if you dont need it at the moment
9) Download MagicArrow:
MagicArrow Classic Edition: https://www.androidfilehost.com/?fid=889764386195920974
MD5: 5ee32443300f10dcbced4808101aff42
MagicArrow Magisk Edition: https://www.androidfilehost.com/?fid=673368273298976764
MD5: 7afa8619778a81a11a60665f27b2289f​
Magisk-Update to 15.3 - use only this zip from this post please: https://forum.xda-developers.com/showpost.php?p=75178940&postcount=871
Please check the MD5 after the download! Because if the download / the zip is faulty - then you have problems after the flash!
And please keep to my instructions - then everything is as it should be
Have much fun with this ROM
Many thanks to KangV for his K-Settings Framework
If you like K-Settings - fell free to donate KangV: https://www.paypal.me/KangVIP
If you like MagicArrow, I am happy about some beer: https://www.paypal.me/Tecalote
Many thanks and credits to other great Developers:
@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
@dkionline - Custom Roms for P9
@Blackball - BlackPyramid Theme and Custom Roms for P8 - P9 - P10
​
Last Thread Update: 03.01.2018

Right settings for Push Notifications and install manual for Stock Firmware Update
Right Settings to make Push-Notification work for Chat-Apps like WhatsApp:
Settings with Phone Manager:
1) Once you have installed with PMPlus the Autostart-Manager called: App auto-launch as a part of Phone Manager- WhatsApp, Viber and all those apps must be activated!
2) Activate these applications also in Protected apps
3) In Notification center activate for these applications - Priority display, Status bar, Banners and Lock screen
4) If these apps are available in Dropzone management - activate them
5) In Phone Manager /open Akku-Manager (Remainning) and in this mask open the settings-symbol above - deactivate Power-intensive prompt and deactivate "Close excessively power-intensive apps" and some lines below:
Activate: Keep Wi-Fi on when sleeping ALWAYS - Keep mobile data on when sleeping
Settings with Permissions and Notifications:
1) Open settings /Apps and search for WhatsApp. In this mask you find Permissions- and Notifications-Settings , go inside of both and set the needed permissions for the app and also "Alllow Notifications" and Priority display
Settings in Developer options:
1) one point after "use legacy DHCP client" - set: Mobile data always active
Additional Settings:
1) Settings /More - Open Mobile network and set: Mobile data - and Enable always-on mobile data
2) Open Settings /Wi-Fi and go to menu in the right corner below "Advanced setting" - set: Keep Wi-Fi on during sleep ALWAYS
3) Open Settings /Notification panel & statusbar - activate: Notification panel "Allow notification panel to be opened from the lockscreen if not password protected
4) Open Settings /Screen lock & passwords - activate "Show detailed notification info" and activate optional "Notification turn on screen"
For most users of ARROW Push-Notification for Chat-Apps are working now as they should (whitout converting them to system-apps like in Gratitude before) -
And for most users battery life is much more better than in Gratitude or in Stock Firmware.
But for some users not!
- Notifications coming not constant or not at all - andBattery life is worse than before - How can that be?
Answer: The complete different initial situation and sometimes also the settings.
Initial Situations (examples):
User A updated Lollipop with Stock Firmware to Marshmallow a long time ago (example: from b200 to b317) - after he was going to Custom Rom "Gratitude" - and from this time he was never back to any Stock Firmware and flashed new versions of Custom Rom always dirty.....
User B was also last on b317, after on "Gratitude" and flashed every new version clean, with Fullwipe.....
User C was last on b321a, after on "Gratitude" and flashed every new version clean, with Fullwipe but Arrow dirty....
User D was on Gratitude 5 and then he go back to Stock Firmware b370 - from there with OTA to b382 and after he flashed TWRP and did a Fullwipe before installing ARROW - this user has the best starting position! And for this user ARROW should work as provided
Why?
Custom Rom can only modifiy on Huawei Devices following partitions: system - cust - vendor (and nothing else!) Modem Updates, Updates for Push-Notifications and other sync services or battery software updates are coming with official Firmware!
The best performance for ARROW is given, if your Marshmallow Firmware and Bootloader and Modem.... is also up-to-date.
There is no need to do following steps, if you have flashed ARROW and everything is fine for you.
I would recommend to go back to Stock Firmware as an step between - before flashing ARROW - for Users which come from Gratitude and for Users which have already ARROW installed and issues with Push-Notifications or too much battery drain!
(STOCK-RECOVERY AND UNROOT IS REQUIRED - AND YOU NEED ALWAYS FULL FIRMWARE FROM CUSTOM TO STOCK) - see install manual below!
The Full-Firmware you download (no OTA Files please) should be minimal b370 (which is available for all models). After this EMUI-Installing with reboot to system you can use in settings the Update-App to receive the next OTA Update and install this also. If the Update-App says after installing "no more Updates available" it is okay!
Normally you can use one Full-Firmware above b370, for GRA-L09 it is b382 - alternatively you can use b391 - but a higher version like b391 seems not work (cause Rom is based on b391)
Complete List of Huawei P8 Firmwares (for all models and cust v.): http://hwmt.ru/oth/HWFF/info/view.php?find_model=gra
GRA-L09:
GRA-L09 Full Firmware b370: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G753/g104/v54178/f1/full/update.zip
GRA-L09 Full Firmware b382: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G753/g104/v69133/f1/full/update.zip
Attention: Bootloader may closed after update with Firmwares above 390 (even if showing in fastboot mode as open - but cannot flashing TWRP "command not allowed" - needs unlock Bootloader again)
GRA-L09 Full Firmware b391: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G985/g104/v71319/f1/full/update.zip
Complete list for GRA-UL00: http://hwmt.ru/oth/HWFF/info/view.php?find_model=gra-ul00
Complete list for GRA-TL00: http://hwmt.ru/oth/HWFF/info/view.php?find_model=gra-tl00
Complete list for GRA-CL00: http://hwmt.ru/oth/HWFF/info/view.php?find_model=gra-cl00
Firmware for GRA-CL10: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G985/g104/v73798/f1/full/update.zip
Complete list for GRA-UL10: http://hwmt.ru/oth/HWFF/info/view.php?find_model=gra-ul10
Install manual:
To go back to Stock Firmware you have to do following steps:
1) Backup what you need to backup! Use Huawei Backup and also Titanium Backup. NOTE: But dont restore in the new ARROW then system-apps or data from system-apps from previous system! Restore only USER-APPS. For Chat-Apps like WhatsApp, Viber, Skype use the built-in Backup function - but keep or backup the folder from those apps on internal memory (because you need them on the same place if you reinstall those apps)
Battery must have minimal 80% doing those steps....
2-A) Users of Classic-Edition: Open K-Settings /more settings /flash recovery - Flash official Recovery (grant Root-Permission) - this flashes Stock Recovery in half a second.
2-B) Users of Magisk-Editon: Please go to TWRP and flash Magisk-Uninstaller.zip to unroot your Phone. Users of Gratitude Magisk Edition should also flash unsu.zip (both linked in OP) After reboot make a connection with USB to your PC. With Minimal ADB and Fastboot program (on PC) flash Stock-Recovery. If you dont know how to do, ask me in this Thread. Download: https://www.androidfilehost.com/?fid=529152257862705190
If you have Xposed Framework installed - uninstall it (Magisk Users in Magisk Manager/Modules - Classic Users in K-Settings /Xposed Settings /Install Xposed confirm - Reboot needs about 15min)
3) Download the Full Firmware for your model, unzipp it on your PC (mostly you get update.app and meta.inf)
4) Create a folder on internal memory or external SD and name it: dload
5) Copy only update.app and meta.inf (if meta.inf is present) in this folder. After DISCONNECT USB from Phone!
6) Reboot to Stock Recovery - with Restart menu (also possible with pressing Vol+ and Power-Button at the same time as long until Recovery is displayed)
7) Wipe Cache with Stock Recovery (it uses another engine than TWRP) and do after a Factory Reset. There is no need to restart the phone to system now. Go to:
8) Press Vol- and Vol+ (in the middle) and Power-Button at the same time, until phone reboots and EMUI-Software-Installing is displayed
9) Let the EMUI-Installing finishing - it reboots automatically to system and starts the EMUI-Optimizing - wait until Language-Selection is displayed. Make a short set up (You can skip the most) - but it is important to arrive the homescreen.
10) Go to Settings / About the phone and tap 7x (times) on Build-Number. It activates developer options.
11) Go to Developer options and activate USB DEBUGGING - after open Advanced settings /security and activate "Unknown Sources"
12) Connect Phone with USB to your PC (Accept the Fingerprint query with "always" on your Phone) Look, if Windows installed the right drivers so you have access to phone - if not install HiSuite http://consumer.huawei.com/minisite/HiSuite_en/index.html and make a connection with HiSuite. Allow installing HiSuite on Phone. If you have access now, close HiSuite (also in Background).
13) Copy ARROW-Rom to your Phone.
14) With Minimal ADB and Fastboot flash TWRP: https://www.androidfilehost.com/?fid=529152257862681510 - if you are unsure with the right commands, ask me in the Thread.
15) DISCONNECT USB Cable now from your Phone
16) Press Vol+ and Power-Button at the same Time until phone reboot (at the moment, Huawei Logo comes you can leave Power Button, but keep holding Vol+) Reboot to TWRP takes a while
17) Set up TWRP (allow modification, set language, screen timeout, time zone...)
18) There is no need to wipe internal SD (but if you like to do this, do it at first and restart after TWRP - then you must setup TWRP again)
18) Go to Wipe, Advanced Wipe and wipe: Dalvik&Cache, Cache, data and system
19) Install ARROW Rom
20) Restore User-Apps, but dont restore any System-Apps (or data from it) Chat-Apps install from Playstore, and use the built-in restore function.
ARROW should work now as ist should!

Men like always the best work!! I already intalled the Arrow ROM... At the moment working excellent... Congratulations :highfive:

Hucast_DL said:
Men like always the best work!! I already intalled the Arrow ROM... At the moment working excellent... Congratulations :highfive:
Click to expand...
Click to collapse
Thank you

Hello @Tecalote, at first i wanna thank you for your work! I want to as you, in description you have "Open PMPlus, select "install it" - message "succesful installed" , but not such app is preinstalled in my Rom, clean flashed classic version, any tips?

00471 said:
Hello @Tecalote, at first i wanna thank you for your work! I want to as you, in description you have "Open PMPlus, select "install it" - message "succesful installed" , but not such app is preinstalled in my Rom, clean flashed classic version, any tips?
Click to expand...
Click to collapse
Hi This is interesting - I am at home in two hours and loading up the apk for you.
I flashed both versions of the Rom about 20 times for testing several things and had always the App preinstalled...
I think it is cause of TWRP.
After making a Nandroid Backup before flashing the Rom it has problems to unmount and remount partitions.
If data was not mounted correctly, the App would not be preinstalled - cause it should go to /data/app
That's why I recommend, after making a Backup to Restart TWRP (reboot Recovery) before flashing the Rom...

Tecalote said:
Hi This is interesting - I am at home in two hours and loading up the apk for you.
I flashed both versions of the Rom about 20 times for testing several things and had always the App preinstalled...
I think it is cause of TWRP.
After making a Nandroid Backup before flashing the Rom it has problems to unmount and remount partitions.
If data was not mounted correctly, the App would not be preinstalled - cause it should go to /data/app
That's why I recommend, after making a Backup to Restart TWRP (reboot Recovery) before flashing the Rom...
Click to expand...
Click to collapse
i will try dirty reflash it with mounted data and let you know :good:
EDIT. reflashing fixed it and app appeared, thanks for halp @Tecalote

To say sir, a perfect job, thank you for all your effort and give you the opportunity to have this great ROM. My congratulations and best wishes to you.
Sent from my GRACE using XDA Labs

lespaul79 said:
To say sir, a perfect job, thank you for all your effort and give you the opportunity to have this great ROM. My congratulations and best wishes to you.
Sent from my GRACE using XDA Labs
Click to expand...
Click to collapse
Thanks a lot

Hello, first of all, thank you for this amazing rom. I've installed it about 6 hours ago and its work perfect at the moment. The only thing that I cannot explain is why show me the block screen weather widget in Chinese, can u help me?

enzoade1994 said:
Hello, first of all, thank you for this amazing rom. I've installed it about 6 hours ago and its work perfect at the moment. The only thing that I cannot explain is why show me the block screen weather widget in Chinese, can u help me?
Click to expand...
Click to collapse
Hi
Written in OP
"In ARROW are not included Chinese letters, with the exception of "Lunar" - which comes with K-Settings. Gratitude users know how to get rid of them. For all others:
1) Go to K-Settings, in there to:
2) Notification Settings / Show "statusbar lunar" - deselect.
3) Go to Lockscreen and desktop settings "Lunar calender + desktop wheather lunar" - deselect."

Great work, flashed it on my UL00 3 hours ago after wiping cache and dalvik cache only, everything seems to work alright, I can confirm that this ROM works flawlessly on UL00.

Ammar_ said:
Great work, flashed it on my UL00 3 hours ago after wiping cache and dalvik cache only, everything seems to work alright, I can confirm that this ROM works flawlessly on UL00.
Click to expand...
Click to collapse
Hi Thank you for your feedback!
You have installed the ROM on the Middle Eastern variant UL00C185...
I am glad to hear that it not only works on GRA-L09
This is what I promised, but I wasn't 100% sure - cause I have only L09...
I am interested which build number is displayed in "About the phone"?
Thanks!

Everything is looking good so far. Thank you for your time and effort!
How do I activate automatic call recording? Is there a possibility of adding more regions to this rom? I have region specific software that fails. My digital satellite provider's software checks my region before it can work. I'm in South Africa.

rodlane said:
Everything is looking good so far. Thank you for your time and effort!
How do I activate automatic call recording? Is there a possibility of adding more regions to this rom? I have region specific software that fails. My digital satellite provider's software checks my region before it can work. I'm in South Africa.
Click to expand...
Click to collapse
Hi there Automatic Call Recording can be enabled that way:
Open the Dialer App - below left is a star, below right is the symbol for the settings menu. Open it and there you can enable automatic call recording.
For the other issue: Can you give me a link to an African Marshmallow Huawei Stock Firmware? So I can look at it and perhaps include the Region.
Which Region did you set up right now?

Thanks very much man!
Flashed it last night, after it took me half an eternity to backup all my files (had something messed up so I had to look a bit deeper). Flashing and all was fine, including xposed via magisk.
Been using it the day now, but at 2 Things im not sure if it is caused by the Rom or by the latest whatapp update:
-in widgets i can select WhatsApp - but there is no more this huge 4*2 widget with message-preview, does anybody else have this? (only WhatsApp Chat and WhatsApp camera available there)
-even though i have given WhatsApp all permissions, my Screen won't wake up when i receive a message. It was quite usefull while the phone lay at my table i could see in one glance whether or not it was important and decide to pick it up
....okay i have tried a bit and found out my Screen also won't wake up after receiving sms or email.. where could i look after that? every app has "Show on lockscreen" enabled
There was another thing, which i could't read fast enough, but it was something with kvip Settings and some overlay permissions and a path where to find them or so?
it popped up a couple of times at the beginning (those little messages in the lower middle of the Screen, just like "wifi connected") next time i will try to make a screenshot of that.
edit:
@Tecalote congrats for 500 Posts and 300 likes! :good:

@Tecalote your ROM IS ****ing awesome, congratulations!!!
Enviado desde mi HUAWEI GRA-L09 mediante Tapatalk

@ChavezD For the Wakeup Screen you must open Phonemanager and in there the Notification Manager. Every App like WhatsApp and Gmail, Email... is in the list - open WhatsApp or Email in the list and set up "Showing on Homescreen" and everything.
The other things I must look. Small popup messages should be shown, like "RAM 1.7 GB available, Wifi connected".. I must look later, at the moment I am not at home
Edit:
For enabling the Wakeup on Homescreen - you must go to Settings /Screenlock and Password - and there set up : Notification turn on screen!

Tecalote said:
@ChavezD For the Wakeup Screen you must open Phonemanager and in there the Notification Manager. Every App like WhatsApp and Gmail, Email... is in the list - open WhatsApp or Email in the list and set up "Showing on Homescreen" and everything.
The other things I must look. Small popup messages should be shown, like "RAM 1.7 GB available, Wifi connected".. I must look later, at the moment I am not at home
Click to expand...
Click to collapse
@Tecalote yeah those Settings are all activated, really don't know what went wrong for me again or what i broke..
EDIT: OH god damn it, thank you so much! I hope i didn't actually disable it half sleeping this morning/"night"
Take your time, it wasn't annoying or anything, just wondered what it was. But it's exactly as you described, but not just 4 words but 4 rows or so in the same time period.
Maybe im also gonna reflash and not install every stupid app i've installed once. Is there any Chance to stop Google from automatically downloading all (>100) recently installed apps after reflashing a Rom? [I always Flash clean, so.. no dirty Flash for me^^]
Edit2: I think in those Messages i was talking about it wasn't Overlay - it was Dropzone. But still no clue what i should do there, everthing is allowed that wants to be

ChavezD said:
@Tecalote yeah those Settings are all activated, really don't know what went wrong for me again or what i broke..
EDIT: OH god damn it, thank you so much! I hope i didn't actually disable it half sleeping this morning/"night"
Take your time, it wasn't annoying or anything, just wondered what it was. But it's exactly as you described, but not just 4 words but 4 rows or so in the same time period.
Maybe im also gonna reflash and not install every stupid app i've installed once. Is there any Chance to stop Google from automatically downloading all (>100) recently installed apps after reflashing a Rom? [I always Flash clean, so.. no dirty Flash for me^^]
Click to expand...
Click to collapse
Hi again You can stop Google from downloading the previous installed Apps at the first start. After Google Login you will be asked if you want to restore - just deny.
Don't know yet what you exactly mean with 4 rows in the same time.
Do you mean perhaps Toast Messages? There's for example an Xposed Modul called "Perfect Color Bar" - in this you can enable "Toast" with mixed compatibility. After you get instead of the the small black info messages colored ones with the symbol of the App message. There are also other "bars" on the Repo for customization that messages.
Do you remember which official firmware did you have before using Custom Roms like Gratitude? b317, b321a, or b370? I know, there were some modem updates coming with the official firmwares (which cannot be done with Roms on Huawei Phones)
Maybe you should update to officially Firmware as an step between before reflashing the Rom. For this you would need the Stock Recovery, which can flashed from K-Settings, more Settings. On xda you can find the b391 here:
https://forum.xda-developers.com/huawei-p8/how-to/firmware-huawei-p8-b391-gra-l09c432-gra-t3534020
It would refresh the Rest of your Phone (which cannot be reached by ROM) - and after the ROM can work as it should...
Just an idea

[Tool][Aroma] Magisk Manager Recovery Tool V2.5

Warning: It's not a Magisk module!
Description
This is a Magisk module management tool that can be used in Recovery mode.
It's based on Aroma Installer.
You can manage almost everything in Magisk with this tool.
You can manage installed modules, enable/disable core only mode, and even manage Root rights.
What can it do
1. Enable/Disable modules
2. Enable/Disable modules mount
3. Remove modules at next reboot (support undo)
4. Remove modules directly
5. Enable/Disable Magisk core only mode
6. Enable/Disable Magisk Hide
7. Enable/Disable Zygisk
8. Enable/Disable DenyList
9. View module descriptions, versions, authors, etc.
10. View module content (directory structure)
11. Shrinking magisk.img (useable for Magisk v18.1 and earlier)
12. Clear MagiskSU logs
13. Manage Superuser rights
Feature
1.Friendly interface & easy to use.
2.Supported older recovery or even CWM.
Download
Github releases
or Download the latest version v2.5 via XDA
How to use
1. Reboot to recovery mode
2. Flash it
3. Enjoy!
Note
1. Only supported arm & arm64 architecture.
2. Will get stuck at Recovery for some device. This is a bug in Aroma Installer binary file and I can not fix it(about: see this issue).
3. If your device is using Qualcomm soc and model is greater than {660, 7xx, 835}, then this tool does not support it.
Github
https://github.com/Pzqqt/Magisk_Manager_Recovery_Tool
Thanks
DualBootUtilities (framework)
Magisk Manager for Recovery Mode (mm) (code of mount magisk.img)
ElementalX Kernel (Aroma Installer theme)
p7zip (7za)
tree (tree)
micropython (micropython binary)
usqlite (μSQLite library module for micropython)
If you have other questions, you can ask me in this post.

Changelog
V1.0 Alpha:
Initial Release
V1.0 Alpha5:
1.Now can recognize update & remove flag. Not allowed to operate modules with these flags to ensure stability.
2.Show "version" & "author", instead of "description".
V1.0 Alpha7:
1.Add switch to enable/disable auto_mount.
2.Draw a new "delete" icon.
V1.0 Alpha9:
1.More friendly user tips.
V1.1 Alpha:
1.If the zip binary is already have in /system/xbin or /system/bin, use it first.
2.Add a "Shrinking magisk.img" option
V1.1 Alpha2:
1.Fix "Error 1" if have not installed any Magisk modules.
V1.1 Alpha3:
1.Arch check: no longer check ro.build.version.sdk.
2.If module removed/with update flag/with remove flag, immediate prompt.
3.Fix wrong printing method in shrink-magiskimg.sh
V1.2 Alpha:
1.Give up zip, use 7za
V1.3 Alpha:
1.Improve magisk.img mount method
2.Draw a fake Magisk logo
3.Show module ID on title
4.Add an option to show module description
5.Version text italic
6.Code clean
V1.4 Alpha:
1.Show different icons depending on the module status
2.Adjust the method of getting module description
3.Add an option to enable/disable Magisk core only mode
4.Remove all unnecessary "-ex" parameters
5.Code clean
V1.5 Alpha:
1.No longer use textbox to return execution results (all use Alert dialog)
2.Dynamic enable/disable module(auto_mount) options
3.Adjust UI & some text (make it look more like the Magisk Manager app)
4.Code clean
V1.6 Alpha:
1.Support operate /data/adb/modules directory (compatible with magisk.img). And make some adjustments to the UI
2.7za: set compression method to 0 (reduce startup time by at least 30%)
3.Show more execution details when flashing
4.Shrinking magisk.img: only show results, no details
5.Code clean
V1.7 Alpha:
1.Force use DroidSansFallback font
2.Use an easier way to create symbolic link
3.Faster way to get magisk.img size
4.Mount /system as readonly
5.Support reading build.prop from system-as-root devices
6.Show installed Magisk version code in the welcome interface
7.Show magisk.img information (size & free) in the welcome interface
8.Remove useless partition information in the welcome interface
9.Show module's size on subtitle
10.Add an option to show module's recursive directory listing
11.Add an option to remove module at next reboot (and can undo this operation)
12.Code clean
V1.8 Alpha:
1.Show magisk.img used size instead of free size
2.Use an easier way to show installed Magisk version
3.License: change to GPL-3.0
4.Handle compatibility with Magisk v19.0
5.Code clean
Hotfix: Fix cannot handle modules with exception path
V1.9 Alpha:
1.Handle modules with exception path (module ID/directory name endswith \r)
2.Improve the mount_image & symlink_modules method again
3.With the help of Aroma Installer's built-in file_getprop function, reduce startup time by at least 50%
4.Add -h flag to du command
5.Improve generate icon prop method, shorten the interface conversion time
6.Hide unavailable options directly
7.Get the module's enabled/disabled status accurately
8.Add an option to clear the MagiskSU logs
9.Add an option to remove all saved apps MagiskSU permissions
10.Add an option to reject all saved apps MagiskSU permissions
11.Add an option to allow all saved apps MagiskSU permissions
12.Add build script
13.Code clean
V2.0 Alpha:
1.List installed modules: sort by module id(case insensitive) or sort by module name
2.Add a debug option to enable geek mode, it will disable a lot of unnecessary "operational success" dialog in this tool
3.Add an option to uninstall Magisk(include latest Magisk-uninstaller package)
4.Add an option to manage Root rights
5.Remove some residual options from v1.9
6.Some UI & text adjustments
7.Code clean
V2.1 Alpha:
1.Automatic creation modules dir when MAGISK_VER_CODE > 18000
2.Automatic creation /data/adb/magisk.img when MAGISK_VER_CODE <= 18000(drop check /data/magisk.img)
3.Shrink magisk.img: Fix sometimes "awk: not found"
4.Give some sorting tasks to sqlite3
5.Rebuild tree binary with Android ndk
6.Include a prebuilt sqlite3 binary(built with Android ndk)
7.List installed modules: force sort by module name
8.Some UI & text adjustments, and remove "Geek mode" debug option
9.Update Magisk uninstaller to 20190501
10.Drop unused resources
11.Show more execution details
12.Code clean
V2.2:
1.Install Magisk internal busybox before use(make sure all common commands are available)
2.No need mount /system now
3.Force use prebuilt sqlite3 binary
4.Unblock the restriction of force remove modules
5.Root manager: show the uid of item in list
6.Update sqlite3 binary to 3290000
7.Rebuild 7za with Frankenstein NDK(reduce binary size by 40%)
8.Real-time calculation of modules number and total size
9.Add an option to enable/disable MagiskHide
10.Update Magisk uninstaller to 20191011
11.Added "About" interface... and some easter eggs
V2.3:
1.Fix "Clear MagiskSU logs" not working on Magisk v20.2+
2.Add module backup/restore options(Experimental)
3.Update Magisk uninstaller to 20200110
4.Update sqlite3 binary to 3300100
V2.4
1. Move the binary files to the bin directory
2. Use Aroma's "include" method to simplify overly long and complex code
3. Fix an issue where sometimes the name of backed up module was incorrectly displayed
4. Unmount all unnecessary partitions when preparing
5. Add MagiskHide warning for v20.4+
6. Disable core only mode switch in Magisk v21.0+
7. Disable MagiskHide switch if Magisk version number >= 23010
8. Add an option to enable/disable Zygisk
9. Add an option to enable/disable Deny List
10. Move Magisk Core Only Mode, MagiskHide, Zygisk and Deny List to the new "Magisk Settings" menu
11. Handling the case where no some key in the Magisk database
12. Remove the uninstall Magsik option
V2.5
1. Compatible with Magisk 24305+
2. Rewrite some script with Python (use micropython as the interpreter)
3. aroma-config: Use magisk busybox's sh instead of /sbin/sh
4. Module size is not displayed for now (until I find a way to reimplement it)

Works great thanks

Updated

Pzqqt said:
Warning: It's not a Magisk module!
Description
This is a Magisk module management tool that can be used in Recovery mode.
It's based on Aroma Installer.
This tool will allows you to perform certain operations, such as enabling, disabling, and removing, on the installed Magisk modules.
Feature
1.Friendly interface & easy to use.
2.Supported older recovery or even CWM.
Download
Google Drive
or Download the latest version v1.2 Alpha via XDA
How to use
1.Reboot to recovery mode
2.Flash it
3.Enjoy!
Note
1.Only supported arm & arm64 architecture. Not supported x86 & x64 architecture.
Github
https://github.com/Pzqqt/Magisk_Manager_Recovery_Tool
Thanks
I borrowed some of the code and resources for the following projects.
If I infringe on the interests of anyone. Please tell me. I will deal with it in time.
DualBootUtilities(framework)
Magisk Manager for Recovery Mode (mm)(code of mount magisk.img)
ElementalX Kernel(Aroma Installer theme)
p7zip(7za binary)
If you have other questions, you can ask me in this post.
Click to expand...
Click to collapse
I can't thank you enough for this app. It saved me from a troublesome module. (I'm looking at you, xposed)
It's easy to use, and has nice UI.
Again, thank you very much!

gamalkevin said:
I can't thank you enough for this app. It saved me from a troublesome module. (I'm looking at you, xposed)
It's easy to use, and has nice UI.
Again, thank you very much!
Click to expand...
Click to collapse
Welcome

Now you can see the status of each module more intuitively, just like this

Well known, magisk.img was removed in Magisk v18.2 build.
The modules will be installed in the /data/adb/modules directory.
It is beneficial to do so. Of course we will follow it.
Magisk Manager Recovery Tool has been updated to v1.6-Alpha. Now it supports operating /data/adb/modules directory to manage modules.

What is the difference between CH magisk recovery and magisk recovery zip

sachin karinki said:
What is the difference between CH magisk recovery and magisk recovery zip
Click to expand...
Click to collapse
I'm gonna take a guess that CH means chinese

Thanx for this tool:good: Is it possible to get a non-transparent theme? On my Z1c the aroma installer is transparent, which makes it hard to read anything.. Thanx again

Ænimal said:
Thanx for this tool:good: Is it possible to get a non-transparent theme? On my Z1c the aroma installer is transparent, which makes it hard to read anything.. Thanx again
Click to expand...
Click to collapse
Transparent theme? Maybe it's a bug in your recovery or Aroma Installer. no problem on my device. Sorry I cannot fix it. Youneed to find a solution yourself.

Thank you for your great work!
God bless you ?️?️?️

Ænimal said:
Thanx for this tool:good: Is it possible to get a non-transparent theme? On my Z1c the aroma installer is transparent, which makes it hard to read anything.. Thanx again
Click to expand...
Click to collapse
What version of twrp are you using ? The latest ? Flash the latest and test it
The official site of twrp is: http://twrp.me

joluke said:
What version of twrp are you using ? The latest ? Flash the latest and test it
The official site of twrp is: http://twrp.me
Click to expand...
Click to collapse
Thanx, I know, but there are no official updates for my device. I'm using 3.2.3-0 and everything else is working fine. I'll just wait for an update of the other magisk manager for compatibility with Magisk 18.2..

Absolutely easier than the vi text editor based one, keep it up!

Hey...
Why not go one step further...
Add in flashing magisk from your tool (external zip)
And
Add in removing magisk from your boot.img (ala the uninstall button in the Manager app)

rignfool said:
Hey...
Why not go one step further...
Add in flashing magisk from your tool (external zip)
And
Add in removing magisk from your boot.img (ala the uninstall button in the Manager app)
Click to expand...
Click to collapse
This will increase the zip file size and is reinventing the wheel.

v2.0-Alpha release!
This is probably the most powerful release d to date.
Magisk Manager Recovery Tool is no longer a simple Magisk modules management tool. It has to be a real "Magisk Manager for Recovery Mode".:fingers-crossed:
Now what can it do?
1.Enable/Disable modules
2.Enable/Disable modules mount
3.Remove modules at next reboot(support undo)
4.Remove modules directly(useable for Magisk v18.1 and earlier)
5.Enable/Disable Magisk core only mode
6.View module descriptions, versions, authors, etc.
7.View module content(directory structure)
8.Shrinking magisk.img(useable for Magisk v18.1 and earlier)
9.Clear MagiskSU logs
10.Manage Superuser rights
11.Uninstall Magisk
Enjoy it!

Hello. Could you tell me if it works on Android pie with rom samsung? Thx

Development [ROM][CUSTOM] <<>> Polar Star Pure Edition <<>>

{
"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"
}
Polar Star Pure Edition ​​This ROM is unified for Edge S Pro / Edge 20 Pro.
Custom ROM based on Global Stock firmware
Android 13 RETAIL_T1RA33.55-15-10-1
Android 12 RETAIL_S1RA32.41-20-16-11
Android 11 RETAIL_RRA31.Q3-19-86-6
This custom ROM uses stock kernel without modification.
>>> Preliminary requirements <<<
Only unlocked bootloader
>>> What's done <<<​- Root permissions via Magisk v.26.1 (26100) Stable (Android 12 - Magisk v.25.2 (25200) Stable) ;
- Removed the restriction on writing to the system, which in Android 11 is in Read Only (r/o) mode by default, which eliminates the possibility of modifying it. In this firmware it is possible to mount the system in Read Write (r/w) mode. Encryption is preserved in this case.
- System passes SafetyNet test, device is certified;
- NFC and GPay with unlocked bootloader and Root worked!
- Cleaned and lightened the system;
- Built in additional system color accents (only Android 11);
- Updated Moto and some Google applications; Android Auto is integrated into the system;
- Removed the pill (bar) at the bottom of the desktop under the dock + made a small distance from the bottom edge of the display to the dock icons and under the keyboard. Especially good on NovaLauncher. In the Android 13 version of the firmware, this feature is implemented systematically.
- YouTube removed, because I use YouTube Vanced;
- Installed apps AdAway ad blocker, Audio Recorder, File Manager, Gallery;
- Ringtones, notifications, alarms sounds have been replaced;
- Mod Logo and Bootanimation;
- The button for calling Google Assistant is reassigned to the: Android 12 - camera shutter and use it to activate the lockscreen; Android 13 - camera launch;
- Beginning with the PStar_PE_A12-41-20-16-5-01 build, I slightly increased the volume of the ear speaker.
How can I turn down the speaker volume?
Use RootExplorer or similar app to delete the mixer_paths.xml file from /vendor/etc. Rename the mixer_paths.bak file to mixer_paths.xml. Restart the device.​
Click to expand...
Click to collapse
- No Warez!
What was done in the latest update (Dec, 05, 2022) :
- Updated ROM base to stock firmware version S1RA32.41-20-16-9;
- New logo & bootanimation;
- Updated Magisk to v25.2;
- Updated applications to the latest versions at the time of ROM build;
- Updated Moto Display;
- Updated Moto Widget;
- Updated Moto Audio Recorder;
- Updated Asus File Manager;
- Completely removed Google Assistant and reassigned its button to the camera shutter;
- Removed Google location history and telemetry apps;
- Removed Turbo and Wellbeing apps;
- Slightly increased the volume of the hearing speaker.
>>> Installation Instructions <<<​1. Extract the system partition images from the archive (see the Download tab) and copy them to any convenient location on your PC.
2. Reboot the device into bootloader mode and:
- If you are installing the ROM for the first time or if you want to install the firmware with all data from the previous firmware removed, then use the _flash_custom.bat executable file;
- If you want to install the ROM as an update to its previous build, then use the _update_custom.bat executable file. Then all your data and applications will be saved and the system will be updated.
3. Phone will reboot into fastbootd mode and flash installation will start automatically. When the installation is completed the phone will automatically boot into the system.
4. When the boot is complete perform the initial settings.
Spoiler: Magisk v.23001(21)
Don't update Magisk and Magisk Manager! Build Magisk (d7e7df3b) (23010) (may be and laters builts) breaks Magisk Hide and SafetyNet.
5. Do not update Magisk Manager, but install this version Magisk Manager 23001(21) in the attached files.
Then you will be asked to configure the working environment. We agree. The phone will automatically reboot after the setup is complete.
6. In the Magisk Manager Settings, disallow "Check Updates". In "Update Channel" select "Custom channel" and in the opened window indicate the link:
Code:
https://raw.githubusercontent.com/topjohnwu/magisk-files/fde0bddfc5683cc8524e323e95f6c8432fbd11da/canary.json
If you are still updating, you can rollback to a working version of Magisk using the following instructions.
-= Rollback Magisk to version 23001 (21) =-
a) Uninstall Magisk with Magisk Manager - click "Uninstall Magisk" button, select "Complete Uninstall".
b) The phone will automatically reboot at the end of the uninstall process.
c) During the rebooting process, press and hold the "volume down" button until the phone enters the fastboot mode. Connect the phone to PC with a USB cable.
d) Extract the boot_magisk.img image from the archive to the folder with the drivers adb:
Android 12 S1RA32.41-20-16_boot_magisk
Android 11 RRA31.Q3-19-86-6_boot_magisk
e) Install boot_magisk.img with the command:
Code:
fastboot flash boot boot_magisk.img
f) Boot into the system and follow steps 5-6 of the basic Instructions for installing the firmware.
>>> Notes <<<
With the update Stock base to RRAS31.Q3-19-86 the problems described below are corrected.​There is a hang-up when entering the connection settings of the NFC and Bluetooth settings. Don't worry about this. You just need to wait a little while.
There is no hang-up when you enable/disable NFC and Bluetooth via the icon from the Notification bar. This happens due to uninstalling any system applications.
>>> Download <<<
Please, don't put the ROM, or links to it, on other sites without the author's permission!
Android 13 PStar_PE_A13-55-15-10-1-02
Android 12 PStar_PE_A12-41-20-16-11-02
Android 11 PStar_Pure_Edition-19-86-6-01​

If you have requests, I can make the same ROM for Moto Edge 20 Pro.
Now the ROM is the same for both modifications.

ROM update S_Pro_Pure_Edition. Added ROM 20_Pro_Pure_Edition.

Updated the ROM for both devices.
What's done:
- replaced the CommandCenter_2 widget with a slightly larger one;
- updated Moto and some Google applications;
- remapped the Google Assistant button to the camera shutter button;
- removed the pill (bar) at the bottom of the desktop under the dock + made a small distance from the bottom edge of the display to the dock icons and under the keyboard. Especially good on NovaLauncher.

Thanks for the ROM.
I was wondering if widevine was L3 or L1 on this.

Updated the ROM to the base RRA31.Q3-19-50.
Since 11.10.21 the firmware is unified for both versions of the phone.

Hello, @ilia3367 do you happen to have any links where I can download your custom rom aside from mega.nz. Would really appreciate if you do, thanks.

rendmazues said:
Hello, @ilia3367 do you happen to have any links where I can download your custom rom aside from mega.nz. Would really appreciate if you do, thanks.
Click to expand...
Click to collapse
Nvm my request, I just have additional question. Does this rom supports OTA? When I searched online, they said that OTA will be downloaded thru playstore so I think it is possible to be supported if that is the case.

do you happen to have any links where I can download your custom rom aside from mega.nz.
Click to expand...
Click to collapse
No. I don't have any free space on my other file stores.

rendmazues said:
Does this rom supports OTA?
Click to expand...
Click to collapse
No. This ROM only supports its own updates, which will be released as Stock firmware updates become available.

Hello
Can you add "Task lock" function in recent apps screen?
I want to keep apps I often use in task list, even if I push "all clear".

Attention users of Custom ROM or users of Root Magisk on Stock firmware!
Starting with version Magisk (d7e7df3b) (23010) the structure of this utility has changed - now Zygisk is used, but Magisk Hide was removed from the utility, SafetyNet test fails.
Read more in the Magisk thread.
For whom these features are important, but accidentally updated Magisk, I offer instructions in the first post of this thread.

ilia3367 said:
Attention users of Custom ROM or users of Root Magisk on Stock firmware!
Starting with version Magisk (d7e7df3b) (23010) the structure of this utility has changed - now Zygisk is used, but Magisk Hide was removed from the utility, SafetyNet test fails.
Read more in the Magisk thread.
For whom these features are important, but accidentally updated Magisk, I offer instructions in the first post of this thread.
Click to expand...
Click to collapse
Thanks for the tut on how to downgrade, I accidentally updated mine. I'll do the downgrading later.

ilia3367 said:
If you have requests, I can make the same ROM for Moto Edge 20 Pro.
Click to expand...
Click to collapse
Yeah Sir, We need a custom rom for edge 20 pro and also how to root this mobile.

hello I just did the steps to be root, I succeeded. install root explore and link2sd to be able to remove apps they give me per, isos, but when I want to uninstall I can't.
root explore does not let me change to r / w and uninstallation fails and link2sd removes but reboot and this is the app.

tarshar01 said:
Yeah Sir, We need a custom rom for edge 20 pro and also how to root this mobile.
Click to expand...
Click to collapse
Now the ROM is the same for both modifications.

Naza1879 said:
root explore does not let me change to r / w and uninstallation fails
Click to expand...
Click to collapse
Are you getting Root on the Stock firmware or on this Custom ROM?
Did Root Explorer ask Magisk for permission the first time it started up?

hello, everyone! I want to know this ROM's back main camera whether support longer than 1/4s exposure by Gcam?
Now I'm using Chinese Rom. It has a serious touch screen issue, and doesn't support longer than 1/4s exposure by Gcam.

Sir, Can you make a video on how to install this on moto edge 20 pro, On YouTube and share link

Updated the ROM to the base RRA31.Q3-19-50-1 - - - PStar_Pure_Edition-19-50-1-02

[Guide][REDMI 7A][Linux][LineageOS] Full guide from stock to Custom LineageOs 18.1

Please find here my notes on the full configuration of a Redmi 7a.
I feel that these informations are generally very scattered, someone like me who didn't follow these topics for a few years may have a hard time getting back into the loop. I hope this guide will help others to quickly get a grip.
Note that I use Linux, so the Unlock part might be interesting for that. Windows users can still follow this guide but may need the official tool for the bootloader unlock and different drivers and tools to interact with the phone.
My configuration is rather intended to use a maximum of open source and securitized applications but with a door slightly open to applications requiring the Google framework.
WARNING : ALWAYS BACKUP, THIS GUIDE IS NOT INTENDED FOR UPDATES, BUT FOR A FULL FORMATTING SETUP.
XIAOMI REDMI 7A (PINE SDM439) : from locked Stock MIUI to Custom LineageOs 18.1 with microG and Gcam​
Unlock the Bootloader and install a Custom Recovery (for linux)​- [Android + Linux] Unlock your Xiaomi Device Bootloader : https://github.com/tkapias/XiaoMiToolV2
- [Linux] Dowload the SDK Platform Tools (ADB, Fastboot ...) : https://developer.android.com/studio/releases/platform-tools
- [PC] Download you current Stock Recovery ROM (Careful with the region): https://mirom.ezbox.idv.tw/en/phone/
- [PC] Patch your boot.img after extracting it from the Stock ROM : https://github.com/YaAlex3/patcher-oss
- [PC] Extract vbmeta.img from the Stock ROM
- [PC] Download PBRP zip and img, the best Custom Recovery : https://github.com/PitchBlackRecoveryProject/android_device_xiaomi_pine-pbrp/releases/
- [Android + Linux] Copy boot.img, recovery.img and vbmeta.img to your phone
- [Fastboot] Reboot in Fastboot and flash :
fastboot flash boot boot.img​fastboot flash recovery recovery.img​fastboot flash vbmeta vbmeta.img​fastboot boot recovery.img​- [Custom recovery] Boot in recovery and Flash the zip of PBRP
Unofficial LineageOs 18​(Performance, Open sources, noGapps)
- [Linux] Download the last zip release of the Unofficial LineageOs 18.1 (Android 11 64bit) : https://github.com/TTTT55/Lineage-OTA/releases
- [Custom recovery] Wipe: system, data, cache, vendor
- [Custom recovery] Format: data
- [Custom recovery] Flash ROM Zip
- Reboot
Root, Kernel, Drivers...​- [Custom recovery + Android] Root by installing the latest Magisk :
- Try the custom recovery method first : https://topjohnwu.github.io/Magisk/install.html#custom-recovery​- Download the Magisk APK : https://github.com/topjohnwu/Magisk/releases​- Rename the .apk file extension to .zip​- In Custom recovery, flash the zip​- Reboot and check whether the Magisk app is installed. If it isn’t installed automatically, manually install the APK.​- In Magisk check that yours is > v24.0 with [Zygisk], it replace the Riru module to install Gapps later.​- [Custom recovery] Flash the latest Cherry Kernel in Recovery (then wipe Dalvik) : https://t.me/s/CherryKernel_SDM439
- [Magisk] Install Adreno Team Graphics Drivers with Magisk([M] 4.2+) : https://drive.google.com/drive/folders/1sizBYMR40G8cF8c0SatGLqpOrbML0tPb?usp=sharing
- [Custom recovery] Flash the Cache Cleaner addon from the Team Graphics Addon Directory.
- [Magisk] Install the magisk module "Color accuracy preset for Redmi 7A" : https://t.me/AkiraLostSushi/30
- [Magisk] Install the magisk module "MagiskHide Props Config" : https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf/releases
[WARNING] [Magisk] The sepolicy.rule file of modules may be stored in the cache partition. DO NOT MANUALLY WIPE THE CACHE PARTITION from this point, or rebuild the rules after :
su​source /data/adb/magisk/util_functions.sh​copy_sepolicy_rules​reboot​
F-Droid in root​- Install the official F-droid apk : https://f-droid.org/F-Droid.apk
- In F-droid install the F-Droid Privileged Extension
- [Custom recovery] Flash the zip org.fdroid.fdroid.privileged.ota...zip in /data/data/org.fdroid.fdroid/ota/
Custom Webview​(UpToDate, AdFilter, more privacy)
- [Android] Download the last Bromite SystemWebView : https://www.bromite.org/system_web_view
- [Custom recovery] Use the file manager to copy the Bromite SystemWebview apk to /system/product/app/webview and rename it as webview.apk
- [Custom recovery] make sure the permissions of webview.apk are 0644 (should be by default)
- reboot phone
- [Android] install the Bromite webview.apk file as you would for any other app
- Once the installation is complete it will be possible to update the SystemWebView without root.
- If your have installed the Root privilege app for F-Droid :
- Add the Bromite repository to F-droid :​- Address: https://fdroid.bromite.org/fdroid/repo​- Fingerprint of the signing key: E1EE5CD076D7B0DC84CB2B45FB78B86DF2EB39A3B6C56BA3DC292A5E0C3B9504​- You can update from F-droid.​
Install NL Sound & Viper4Android with Magisk​(change all the audio framework ant effects engine)
- Install Package Manager and Termux from F-droid
- Disable or uninstall AudioFx in Package Manager
- [Magisk] Install the module “Audio Modification Library” : https://zackptg5.com/android.php#aml
- [Magisk] Install the module “NL Sound” : https://github.com/Briclyaz/NLSound_module_QCom (Zip it or from Telegram)
- [Magisk] Install the module "ViPER4Android FX" : https://zackptg5.com/android.php#viper
- Reboot
- Open Viper4Android, follow the prompt to install the driver, or install them from : https://zackptg5.com/android.php#viper
- Reboot
- In Termux, install root packages :
pkg install root-repo && pkg upgrade​- In Termux :
su​source /data/adb/magisk/util_functions.sh​copy_sepolicy_rules​reboot​- After the reboot open Viper4Android and switch on the Legacy option.
- Reboot
- Check the driver status in the second icon on the top in V4A
- Activate "Master limiter", "Gain control", "Speaker optimization"
- Disable battery optimization for the app in android
Install microG with Magisk​(Minimal Google framework to use Gcam and some apps from Aurora store)
- [Magisk] Install modules "Zygisk - LSPosed" : https://github.com/LSPosed/LSPosed/releases
- [LSPosed] Install the module "FakeGapps"
- [LSPosed] In FakeGapps, check that the recommanded app for subsystem is checked
- [Android] Add a file /data/adb/no_droid_guard with any content (it disables the installation of Droid Guard)
- [Magisk] From Magisk Modules, install "microG Installer Revived" : https://github.com/nift4/microg_installer_revived/releases
- [LSPosed] From F-droid, install "Aurora Store"
Tweak the network settings for a better roaming and latency​- [APK] Install KTweak : https://github.com/tytydraco/KTweak-Android-App/releases/tag/build-2dd09c9_1639707532
- [KTweak] Give it root acces, restart on boot and use its "throughput" profile.
- [DNS] Activate AdGuard DNS : Go to Settings → Network & internet ( or Wi-Fi & Internet), Select "Private DNS provider hostname" option and enter the following address: dns-unfiltered.adguard.com
- [Props] In Termux:
su
settings delete system tether_entitlement_check_state; settings delete global tether_dun_required
props
- "Select an option below." → "Add/edit custom props" 5 ↵
- Select "New custom prop" with n ↵
- net.tethering.noprovisioning ↵ → true ↵ → y ↵
- "Do you want to reboot now?" n ↵
- Select "New custom prop" with n ↵
- tether_entitlement_check_state ↵
- "Are you sure you want to proceed?" y ↵ → 0 ↵ → y ↵
- "Do you want to reboot now?" n ↵
- Select "New custom prop" with n ↵
- tether_dun_required ↵ → 0 ↵ → y ↵
- "Do you want to reboot now?" → y ↵
Custom Gcam​(Keep the stock camera app for fast results, Gcam is for quality HDR+)
- You need to install microG first
- Prefer 7.2/7.3/7.4 versions.
- Prefer Nikita or urnyx05 releases :
- https://www.celsoazevedo.com/files/android/google-camera/dev-Nikita/​- https://www.celsoazevedo.com/files/android/google-camera/dev-urnyx05/​- My favorite : GCam_7.3.018_Urnyx05-v2.5 https://www.celsoazevedo.com/files/android/google-camera/f/changelog1500/
- I uploaded my configs XML : https://www.celsoazevedo.com/files/android/google-camera/f/configs-urnyx-02/
List of favorite additional apps​
F-Droid​- FFUpdater (Install and update Browsers)
- Firefox Nightly (My addons collection: 17173754/tkacomplete, see Mozilla blog)​- DAVx5 (Sync CalDav and CardDav)
- Element (Matrix messaging)
- FairEmail (Email)
- Identiconizer! (Contacts pictures)
- KeepassDX (Passwords - sync with Syncthing)
- Lemuroid (Game emulation)
- Librera Reader (PDF, Books, Comics...)
- LibreSpeed (Open source speedtest)
- Markor (just for quicknotes, sync with Syncthing)
- Material Files (File explorer)
- MinCal Widget (Calendar widget)
- mpv-android (Player)
- NewPipe (Youtube player)
- OsmAnd+ (Maps)
- Package Manager
- QR & Barcode Scanner
- SimplyTranslate Mobile (Google translate with privacy)
- Syncthing (to sync files)
- Task.org (Task in CalDav)
- Telegram (Messaging)
- Termux (A better terminal)
- Wireguard (VPN client/server)
- XBrowserSync (Sync bookmarks)
Aurora Store​- Device Info HW
- Spotify (Music)

Thanks, your concise guide helped me a lot, makes it really easy. Should be pinned somewhere at the top

Thank you Tupolef. I have found your instruction set very helpful and modified my 7A thanks to you.

Hi, thank you for this guide. I am a newbie at modding, and I don't have any idea how to have a Linux environment. Is there any chance I can send you my boot.img and ask you to patch it for me?

I can send you files I used but you need only python and the script from the link listed in the instructions. where to upload them?

Hi,
I hope this is helpful, I have updated the post regarding 3 points:
Magisk no longer offers the modules directly from the Magisk app, you have to download them yourself. So I put the links where they are needed.
Magisk since version 24.0 offers Zygisk, a feature that replaces the Riru module. LSPosed now offers a Zygisk version, no more need for Riru. I changed the links.
I added a section about network improvement, through DNS and Kernel settings with KTweak and Props. I really saw a difference.
There is still a problem, the fact that there is no update for the release that I had chosen at the beginning for the moment: https://github.com/TTTT55/Lineage-OTA
I may try to update to another release with the same bases to see but for the moment I stay on this version.

lyleflyle said:
Hi, thank you for this guide. I am a newbie at modding, and I don't have any idea how to have a Linux environment. Is there any chance I can send you my boot.img and ask you to patch it for me?
Click to expand...
Click to collapse
You can patch boot.img on Windows too.
Install python3 and 7-zip :
- https://www.python.org/ftp/python/3.10.4/python-3.10.4-amd64.exe
- https://www.7-zip.org/a/7z2107-x64.exe
Download a copy of Patcher-Oss :
- https://github.com/YaAlex3/patcher-oss/archive/refs/heads/main.zip
Extract main.zip in a folder and put your boot.img in the same folder, where main.py is.
Open a command prompt or powershell under windows and go to this folder with the "cd" command. Then run the script main.py with the command :
Code:
python3 main.py boot.img

Tupolef said:
You can patch boot.img on Windows too.
Install python3 and 7-zip :
- https://www.python.org/ftp/python/3.10.4/python-3.10.4-amd64.exe
- https://www.7-zip.org/a/7z2107-x64.exe
Download a copy of Patcher-Oss :
- https://github.com/YaAlex3/patcher-oss/archive/refs/heads/main.zip
Extract main.zip in a folder and put your boot.img in the same folder, where main.py is.
Open a command prompt or powershell under windows and go to this folder with the "cd" command. Then run the script main.py with the command :
Code:
python3 main.py boot.img
Click to expand...
Click to collapse
Got it. Thank you for the quick response.

BTW, what launcher do you use guys? I just last week tried Kvaesitso and I find it perfect. If you haven't yet - try it.

MariusSays63 said:
BTW, what launcher do you use guys? I just last week tried Kvaesitso and I find it perfect. If you haven't yet - try it.
Click to expand...
Click to collapse
Currently using pixel launcher. I’ll have to try Kvaesitso

Hi,
I have been using stock lineage OS for the past 2 days and it performs amazing. I have installed magisk and flashed the cherry kernel along with the adreno drivers. However, it seems like I have been experiencing lags and stutters in overall navigation since. Is this normal? Should I wait for a brief period before it performs optimal again?

FWIW: I haven't installed cherry kernel neither adreno drivers and I'm happy with stock lineage performance as it is.

MariusSays63 said:
FWIW: I haven't installed cherry kernel neither adreno drivers and I'm happy with stock lineage performance as it is.
Click to expand...
Click to collapse
I was quite curious on how it will perform with Cherry Kernel. I, too, was fully happy with stock lineage. Do you have any idea if the kernel will be back to stock if I re-flash the lineage ROM?

>>Do you have any idea if the kernel will be back to stock if I re-flash the lineage ROM?
I'm pretty sure you will reinstall the kernel and drivers in this case. Play with it

Personally, I've been on this configuration for 5 months and I have no lags.
I use this device to receive important notifications from many apps and as a backup hotspot. Sometimes some web browsing or audio stream with NewPipe or Spotify, but no games. I only have 2 widgets for calendar and tasks, and I always close the apps I don't use.
The only downside is that the Gcam apps are all very buggy or slow with this device, I ended up switching back to the LineageOs app. Apparently LineageOs 19 switches to Camera2, I will try to install it on the 18.1.
{
"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"
}

Tupolef said:
Personally, I've been on this configuration for 5 months and I have no lags.
I use this device to receive important notifications from many apps and as a backup hotspot. Sometimes some web browsing or audio stream with NewPipe or Spotify, but no games. I only have 2 widgets for calendar and tasks, and I always close the apps I don't use.
The only downside is that the Gcam apps are all very buggy or slow with this device, I ended up switching back to the LineageOs app. Apparently LineageOs 19 switches to Camera2, I will try to install it on the 18.1.
View attachment 5600453 View attachment 5600455
Click to expand...
Click to collapse
FWIW I tried few Gcams and stuck with MGC 8.1.101.345618084 but sluggish saving pictures but all functions seem to work. Also Kvaesitso works great with it as I have mentioned. This is my personal phone, I don't even have data just pay as you go as I have work phone but wanted something cheap but with good specs for its cost so I can tinker with and 7A was a great choice back then and still is.

First of all, thanks a lot for this guide!
One information + 2 questions:
1) Info: unlocking the bootloader is no longer possible on linux, even with recent patches to the XiaoMiToolV2. See the thread under that tool. I was able to do it on Windows however using the official Xiaomi tool.
2) Question 1: after I have flashed PBRP I cannot boot into it from fastboot. "fastboot boot ./recovery.img" sends the image and says "booting OKAY" but nothing happens, the phone remains in fastboot. I have to deconnect from the PC and go to PBRP manually by long pressing vol up + power. Has anyone come across this? I have tried several times, even going fully back to stock, installing PBRP anew etc., it is repeatable. Also, with my old Redmi 4A there is no such problem, I can boot into my custom recovery from fastboot. Does it have any repercussions?
3) Question 2: I'm trying to install crDroidAndroid-12.1-20220617-Mi439-v8.6.zip. I wipe and flash with PBRP, no errors. But it soft-bricks the device, only fastboot comes up afterward and I have to flash stock again... Does anyone here have experience with crDroidAndroid-12.1-20220617-Mi439-v8.6.zip? Thanks!

Just an update with respect to what I wrote here yesterday: today, following _almost_ this same process, I was able to start the phone with a custom ROM today. Only 2 differences:
-This time I formatted data in PBRP (not just wipe); not sure this matters however, since output always says "formatting data"?!
-This time I flashed crDroidAndroid-11.0-20220318-pine-v7.16.zip. I can really recommend this ROM by the way!

bunchofdutch said:
Just an update with respect to what I wrote here yesterday: today, following _almost_ this same process, I was able to start the phone with a custom ROM today. Only 2 differences:
-This time I formatted data in PBRP (not just wipe); not sure this matters however, since output always says "formatting data"?!
-This time I flashed crDroidAndroid-11.0-20220318-pine-v7.16.zip. I can really recommend this ROM by the way!
Click to expand...
Click to collapse
Thanks for the information about XiaoMiToolV2.
For that and the boot, I'll update in a little while, I plan to reinstall the device with the new LineageOs within the month.
I will update this post and answer you more extensively.

---