Database Info

[DISCONTINUED][KERNEL][G906S/K/L][4.4][5.0] Lolliwiz Kernel R10 [Sep 8]

This post can be updated anytime.
For korean support and for those who can translate Korean, visit my blog:
http://kykint.tistory.com/
Download TWRP Recovery v2.8.7.0 for G906SKL
/* Requirements */
* Galaxy S5 broadband LTE-A (SM-G906S, G906K, G906L)
* Samsung stock firmware or Dokdo-projct
- Kitkat: ANK1
- Lollipop: BOG2 for G906K, BOH1 for G906S/L
* Custom recovery (Philz, TWRP, etc)
/* Note before using */
* Backup important data before installing
* Upon installation, every warranty inclusing KNOX becomes void
* I, kykint, am not responsible for any inconvenience or problems that occur while using this kernel
* Only one hotplug driver should be on (mpdecision, intelli_plug, alucard_hotplug, lazyplug)
Lazyplug is currently not supported on kernel customizing applications. Wait until their developers update.
* Dokdo-Project version of lolliwiz is highly experimental. Don't complain about battery drain.
It also does not support uninstaller yet.
/* About new installer */
Since Release 9, the installer will automatically extract your device's ramdisk, merge it with lolliwiz kernel, and then install it.
Upon installation, if a backup folder (/system/lolliwiz-bak) is found, it will automatically restore it first and then continue installation.
It will backup original boot.img and sensors library to the backup folder (/system/lolliwiz-bak) while installing.
There might be some problems regarding this new installer, so please keep the following instructions in mind.
* When installing another variant's ROM, do not install lolliwiz right after flashing ROM.
Install the stock kernel of your variant, and then install lolliwiz.
* Those who have been using R8 or older version of lolliwiz must flash stock kernel first before installing R9 or later.
* Do not install stock kernel when lolliwiz is installed on your device.
Only install stock kernel when uninstaller fails to remove lolliwiz and restore to stock kernel.
/* Kernel features */
Built with custom compiled krait-optimized UBERTC 5.2.1
Various compile optimization flags
Various improvements backported from Linux mainline
CPU Governors: franco interactive & conservative, intelliactive, and a lot more
I/O Schedulers: CFQ, ROW, DEADLINE, SIO, FIOPS
Custom hotplug drivers: intelli_plug, alucard_hotplug, lazyplug
CPU Voltage control
Adreno_idler GPU governor addon
Simple_ondemand is not crashing anymore
Display gamma control
Dynamic FSync Control
SELinux set as permissive by default
FauxSound ported for wcd9330 (LP only)
Support for kernel mode NEON
Optimized Kernel Samepage Merging
Quickwakeup driver by Motorola
Random driver ported from latest Linux mainline
Adaptive LowMemoryKiller
Full support for F2FS
Power-efficient Workqueue
Unaligned access support for lib
Init.d script support
Various minor fixes and improvements
/* Changelogs */
Refer to the 3rd post
/* Kernel customization */
Recommended applications: Kernel Adiutor, TricksterMod
/* Downloads */
Lolliwiz & stock kernels
Previous versions of lolliwiz
LW-G906-Dokdo-R*.zip : for Dokdo-Project users
LW-G906-R*_F2FS.zip : for F2FS users
/* F2FS Conversion Manual */
Refer to the 2nd post.
/* Chatters */
Release 9 and 10 are mostly bug fix releases, so there isn't much difference.
Kitkat support has been put off to R11, and if a bug is found again and R11 happens to be released early, it will be put off to later release again.
Still, I'm considering EOL of kitkat version as it is becoming harder to support the old Linux version.
/* Contacts */
You can contact me through telegram @maplezeon, but I won't listen to complaints.
On weekdays I'm mostly at school, from 7am to 10pm, so there's no much time for chats.
/* Source */
http://pc.cd/U2YrtalK
/* Special thanks to */
세이님, 티라미슈님, hsk님, arter97님, JustArchi, Christopher83, faux123,
franciscofrancoeng.stk, flar2, imoseyon, friedrich420, Google, Samsung
and every single one of you guys, for using my kernel
XDA:DevDB Information
Lolliwiz Kernel for SM-G906, Kernel for the Samsung Galaxy S 5
Contributors
kykint
Source Code: http://pc.cd/U2YrtalK
Kernel Special Features:
Version Information
Status: Stable
Created 2015-04-28
Last Updated 2015-09-11

Changelogs
Release 10 - Sep 7
Reverted GCC 5+ compatibility improvement patches
=> Hopefully fixed some applications disappearing
Unaligned access enabled explicitly for lib
Release 9 - Sep 6
Brand new installer
=> Now support all three variants (S/K/L), boot.img and sensors library are backed up in /system/lolliwiz-bak
Add uninstaller
Fixed proximity sensor not working
=> Caused by Merge of G906K Kernel source, solved by installing sensors library from OG2 firmware
Applied patches regarding media driver
Updated lz4 source and enable unaligned access
NVIDIA's power savings patch
Westwood as default TCP congestion control method
Optimized intelli_plug
New hotplug driver: Lazyplug by arter97
=> Currently not supported on kernel setting applications, wait for updates
Some GCC 5+ compatibility improvements
Release 8 - Sep 1
Added experimental support for Dokdo-Project
(Compatible with all three variables and every version of Dokdo-Project)
KK support dropped at the moment
LP: Common: Merged G906K OG2 kernel source
LP: kt: Merged OG2 ramdisk
LP: skt,lgu: Merged OH2 ramdisk
LP: kt: fixed a typo in ramdisk
Linux 3.10.70
Full F2FS support + source updated to the latest
Power-efficient workqueue
Random driver backported from Linux 4.2+
Another new hotplug driver - Alucard hotplug
Custom built UBERTC with Krait optimizations
New build optimization flags
Fixed min cpu frequency changing on its own
Dynamic fsync disabled by default
built-in support for NTFS
Other miscellaneous fixes and updates
Release 7 - Jun 28
LP: Imported patches from upstream (1,000+ patches)
LP: Linux 3.10.59
KK: Imported patches from upstream (300+ patches)
KK: Linux 3.10.6
Compile optimization flags from arter97's kernel, big thanks to @arter97
Added adreno_idler addon for adreno-msm-tz GPU governor
Removed Simple GPU Algorithm
Switched to UBER Toolchain, GCC 5.1
Added motorola's quickwakeup driver
Added patches to reduce wakelock
Backported random driver from Linux 4.0.6
Optimized KSM
Added adaptive_lmk
Various small fixes & improvements
Release 6 - May 30
Added support for KitKat
Fixed wrong boot.img arguments
Fixed Sweep2Sleep not working on some variants
Removed SEANDROID warning on boot logo
Added advanced TCP congestion methods
Disabled crc check for better performance
Merged BOE1 changes
Ramdisk compressed with LZ4
Other small tweaks & fixes
Release 5 - Apr 20
Removed smartassV2 CPU Governor
Added mythx_plug CPU Governor
Added support for kernel NEON mode
Removed Franco's Sound Control
Ported FauxSound for work with wcd9330
Applied patches for gpu and video driver
Imported latest interactive & conservative governor from franco's shamu kernel
Added support for KSM on/off
Enabled tuning option for Cortex-A15
Some minor fixes from faux123

F2FS Conversion manual
/* F2FS Conversion Manual */
(for LP and Dokdo-Project only, no KK support)
(Not tested on Dokdo-Project)
I will not add any additional explanations about F2FS, since this is a very risky task and recommended only for experts,
and since not knowing about F2FS means that you're not one of them.
Cautions
1. Conversion process of /data partition and filesystem will wipe away every single data in your device,
so every data in internal sdcard should be backed up on your PC.
2. Flashing /cache partition image when the device has already been converted to F2FS will format /cache partition to EXT4,
so manual conversion process of /cache partition to F2FS must be done again.
3. The /cache partition image mentioned above is included in stock firmware package, so be careful when installing stock firmware
4. Inside stock firmware is included a stock kernel which only supports EXT4, so again, be careful when installing stock firmware
5. /data and /cache partition must be set to the same filesystem, both EXT4, or both F2FS
6. I personally recommend that every process be done using my TWRP recovery, which will be posted in a seperate thread later.
7. The F2FS version of kernel zip has a '_F2FS' tag at the end of its filename, while EXT4 has nothing.
Be careful, Dokdo-Project version supports both EXT4 and F2FS, so they're not seperated,
and when converting to F2FS on Dokdo-Project, you can skip kernel switching(reinstalling) process.
How to change filesystem on TWRP
Wipe > Advanced Wipe > (Select a partition) > Repair or Change File System > Change FIle System > (choose between EXT4 and F2FS) > Swipe to Change
* It takes a great amount of time when changing to EXT4, up to several minutes.
How to check current filesystem on TWRP
Wipe > Advanced Wipe > (Select a partition) > Repair or Change File System
and you'll see your current filesystem on the upper part of the screen.
Converting to F2FS
0. For stability, flash uninstaller first if you already have lolliwiz installed.
1. Install F2FS version of Lolliwiz. (_F2FS.zip)
2. Change the filesystem of /data and /cache partition to F2FS.
3. Reboot into recovery mode again.
Back to EXT4
0. For stability, flash uninstaller first if you already have lolliwiz installed.
1. Install EXT4 version of Lolliwiz.
2. Change the filesystem of /data and /cache partition to EXT4.
3. Reboot into recovery mode again.
Installing stock firmware on F2FS
1. Reboot into download mode and install stock firmware with odin as usual.
2. When the installation finishes, it'll automatically reboot into recovery mode and flash CSC package.
Wait until androboy disappears and the device reboots again.
3. Reboot into download mode again.
4. Install my TWRP.
5. Reboot into recovery right after installing.
6. Install F2FS version of lolliwiz.
7. Format /cache partition to F2FS
8. Run factory reset if needed. This is an option.
9. Reboot.
If the device won't boot even if you carefully followed all of the above instructions, repeat the process again.

Thanks

Thanks I was on the Korean forums yesterday trying to translate lol.

I noticed there's a test for b5. Giving it a try.
One issue I seem to have on b4 and 5 test is that no matter what kernel tuning app I use if I turn off mpdecision and intelliplug on, after a reboot mpdecision always comes back on.

Audioboxer said:
I noticed there's a test for b5. Giving it a try.
One issue I seem to have on b4 and 5 test is that no matter what kernel tuning app I use if I turn off mpdecision and intelliplug on, after a reboot mpdecision always comes back on.
Click to expand...
Click to collapse
Kernel settings are set to defaults on each reboot and the default setting on hotplug is mpdecision on, intelli_plug off. That's why every kernel app has the ability to restore previous settings after reboot. Try enableing them, kernel adiutor works fine for me

kykint said:
Kernel settings are set to defaults on each reboot and the default setting on hotplug is mpdecision on, intelli_plug off. That's why every kernel app has the ability to restore previous settings after reboot. Try enableing them, kernel adiutor works fine for me
Click to expand...
Click to collapse
Thanks, but I told it to save settings. It's weird as all the settings were saved, including intelliplug on, but mpdecision was turned on as well. I'll uninstall it and start again!
Do you have a donation link btw?
Edit: Here is what I mean
{
"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"
}
Edit2: Strange, I reflashed the kernel and it is now working!

Audioboxer said:
Thanks, but I told it to save settings. It's weird as all the settings were saved, including intelliplug on, but mpdecision was turned on as well. I'll uninstall it and start again!
Do you have a donation link btw?
Edit: Here is what I mean
Edit2: Strange, I reflashed the kernel and it is now working!
Click to expand...
Click to collapse
Nice to hear it's working well now.
I don't get donations, maybe you could donate to the REAL developers out there, they're always working hard for us XD

Very interesting!
I'm reading the Asian forums since a week and I have found that this kernel is well used.
How can I flash back stock kernel if something happens? And where can I find stock kernels??
If they are unavailable, I'd like to make my own Odin tar.md5 files for flashing stock kernel.
Can I follow the script/batch procedure (found here on Xda) that produces the tar.md5 flashable files?
Tnx!!
Sent from my Samsung Galaxy S3 GT-i9300 using Tapatalk 4

Thanks

PIRATA! said:
Very interesting!
I'm reading the Asian forums since a week and I have found that this kernel is well used.
How can I flash back stock kernel if something happens? And where can I find stock kernels??
If they are unavailable, I'd like to make my own Odin tar.md5 files for flashing stock kernel.
Can I follow the script/batch procedure (found here on Xda) that produces the tar.md5 flashable files?
Tnx!!
Sent from my Samsung Galaxy S3 GT-i9300 using Tapatalk 4
Click to expand...
Click to collapse
No worries, I'll upload stock kernels for recovery/odin as soon as I get back home

kykint said:
No worries, I'll upload stock kernels for recovery/odin as soon as I get back home
Click to expand...
Click to collapse
Can you do it also for KitKat if you have then?
Tnx.
Sent from my Samsung Galaxy S3 GT-i9300 using Tapatalk 4

Sharing battery based profile still in testing
Hi everyone ,
i would like to share my battery based profile.
I used Trickstermod kernel app taken from bbs dot sonyue dot com
( The kernel app is under attachment)
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
1. Install the app.
2. Open the app, at top left a list will open, Choose the General
3. Change the following
I/O Control:
Read Ahead Buffer Size 1024
Schedular fiops
CPU Frequency Control
Frequency Lock ON
Min 300000 (choose the lowest scroll to the top first)
Max 1574400
CPU Governor Control
Governor Conservativex
------------------------------------------------------------------------------------------------------------------------------------------
4. Now Choose Specific
Mp-Decision OFF
Intelli-Plug ON
Dynamic FSYNC ON
GPU Governor Powersave
GPU Max Frequency 240
Intelli-Thermal Control ..........> Intelli-Thermal ON
MPU Voltages
( I undervolted from Snapdragon 805 thread in xda)
< 300MHz 700
< 345MHz 710
< 422MHz 720
< 499MHz 730
< 576MHz 740
< 652MHz 750
< 729MHz 760
< 806MHz 770
< 883MHz 780
< 960MHz 820
< 1036MHz 830
< 1113MHz 840
< 1190MHz 850
< 1267MHz 860
< 1344MHz 870
< 1420MHz 880
< 1497MHz 890
< 1574MHz 900
< 1651MHz 910
< 1728MHz 920
< 1804MHz 930
< 1881MHz 940
< 1958MHz 950
< 2035MHz 960
< 2112MHz 975
< 2188MHz 990
< 2265MHz 1005
< 2342MHz 1020
< 2419MHz 1035
< 2457MHz 1040
---------------------------------------------------------------------------------------------------------------------------------------------------------------------
Or You can download the profile in attachment and do the following:
1. Download the profile and extract it.
2. Go to your phone storage and look for a folder name tm_profiles
3. Paste it there.
4. Open the trickstermod app.
5. press at the top left and choose Tool.
6. You will find Global Profile. press restore and choose my profile Battery Test V2 pvs11 .
----------------------------------------------------------------------------------------------------------------------------------------------------------------
I hope you will test it guys and my aim is just battery light user no gaming.
Please feedback its just test if you more knowledge share as i already contacted the OP permission to open a profile thread.
@kykint
Undervolting source
http://forum.xda-developers.com/htc-one-m8/general/guide-snapdragon-801-clocking-voltage-t2807173

kardinal969 said:
Hi everyone ,
i would like to share my battery based profile.
I used Trickstermod kernel app taken from bbs dot sonyue dot com
( The kernel app is under attachment)
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
1. Install the app.
2. Open the app, at top left a list will open, Choose the General
3. Change the following
I/O Control:
Read Ahead Buffer Size 1024
Schedular fiops
CPU Frequency Control
Frequency Lock ON
Min 300000 (choose the lowest scroll to the top first)
Max 1574400
CPU Governor Control
Governor Conservativex
------------------------------------------------------------------------------------------------------------------------------------------
4. Now Choose Specific
Mp-Decision OFF
Intelli-Plug ON
Dynamic FSYNC ON
GPU Governor Powersave
GPU Max Frequency 240
Intelli-Thermal Control ..........> Intelli-Thermal ON
MPU Voltages
( I undervolted from Snapdragon 805 thread in xda)
< 300MHz 700
< 345MHz 710
< 422MHz 720
< 499MHz 730
< 576MHz 740
< 652MHz 750
< 729MHz 760
< 806MHz 770
< 883MHz 780
< 960MHz 820
< 1036MHz 830
< 1113MHz 840
< 1190MHz 850
< 1267MHz 860
< 1344MHz 870
< 1420MHz 880
< 1497MHz 890
< 1574MHz 900
< 1651MHz 910
< 1728MHz 920
< 1804MHz 930
< 1881MHz 940
< 1958MHz 950
< 2035MHz 960
< 2112MHz 975
< 2188MHz 990
< 2265MHz 1005
< 2342MHz 1020
< 2419MHz 1035
< 2457MHz 1040
---------------------------------------------------------------------------------------------------------------------------------------------------------------------
Or You can download the profile in attachment and do the following:
1. Download the profile and extract it.
2. Go to your phone storage and look for a folder name tm_profiles
3. Paste it there.
4. Open the trickstermod app.
5. press at the top left and choose Tool.
6. You will find Global Profile. press restore and choose my profile Battery Test V2 pvs11 .
----------------------------------------------------------------------------------------------------------------------------------------------------------------
I hope you will test it guys and my aim is just battery light user no gaming.
Please feedback its just test if you more knowledge share as i already contacted the OP permission to open a profile thread.
@kykint
Undervolting source
http://forum.xda-developers.com/htc-one-m8/general/guide-snapdragon-801-clocking-voltage-t2807173
Click to expand...
Click to collapse
Good!
I'm following the Asian forum where I've found this kernel and related config app, from which I've read that there's a modified version of the app....And for this please give me some infos.
I'm also searching for some interesting custom rom as I see there are some, like the KingWolf one or the Milan one.
Any help on using this kernel with some roms?
Tnx!
Sent from my Samsung Galaxy S3 GT-i9300 using Tapatalk 4

PIRATA! said:
Can you do it also for KitKat if you have then?
Tnx.
Sent from my Samsung Galaxy S3 GT-i9300 using Tapatalk 4
Click to expand...
Click to collapse
I uploaded lollipop stock kernels for both recovery and odin. I'll upload for kitkat as well when I get the latest kitkat firmware.

Sorry, this might be a dumb question, but I'd rather ask it then brick my only smart-phone:
I'm currently on miscom's ROM (see here: http://forum.xda-developers.com/galaxy-s5/development/galaxy-s5-g906-custom-rom-t2848569)
Also using Philz recovery
How do I get to the Lolliwiz Kernel safely? Can I keep my apps, settings and so on?
Again, sorry. This is my first android phone (but certainly not the last one!) and I'm pretty clueless... But getting the miscom kernel on it was pretty easy with a bit of reading...

mcbrite said:
Sorry, this might be a dumb question, but I'd rather ask it then brick my only smart-phone:
I'm currently on miscom's ROM (see here: http://forum.xda-developers.com/galaxy-s5/development/galaxy-s5-g906-custom-rom-t2848569)
Also using Philz recovery
How do I get to the Lolliwiz Kernel safely? Can I keep my apps, settings and so on?
Again, sorry. This is my first android phone (but certainly not the last one!) and I'm pretty clueless... But getting the miscom kernel on it was pretty easy with a bit of reading...
Click to expand...
Click to collapse
Make a backup of whole apps with TitaniumBackup first, then backup system, data, boot in philz recovery(run custom backup) and flash stock lollipop through odin. miscom's rom is 4.4.2 as I know of, and my kernel supports 5.0.1 only at the moment.
If your phone bootloops after flashing lollipop, factory reset through philz and restore apps from TitaniumBackup, or flash back stock kitkat firmware and then restore system, data, boot in recovery.
Note that flashing stock firmware will blow away your recovery and you should manually install it again with odin. Also, factory reset through philz will preserve your internal sdcard but stock recovery WILL NOT.

kykint said:
Make a backup of whole apps with TitaniumBackup first, then backup system, data, boot in philz recovery(run custom backup) and flash stock lollipop through odin. miscom's rom is 4.4.2 as I know of, and my kernel supports 5.0.1 only at the moment.
If your phone bootloops after flashing lollipop, factory reset through philz and restore apps from TitaniumBackup, or flash back stock kitkat firmware and then restore system, data, boot in recovery.
Note that flashing stock firmware will blow away your recovery and you should manually install it again with odin. Also, factory reset through philz will preserve your internal sdcard but stock recovery WILL NOT.
Click to expand...
Click to collapse
Wait a minute!!! I though that factory reset in Philz recovery for G906 was not working and doing that would brick the phone!!!!!
I've read this in the info thread on the S5 G906 here on XDA!!!
Look under here in the Known issues:
prodigiez said:
.........
CWM
Unofficial PhilZ recovery is also available as below
Credit to hsk for unofficial CWM
updated : adb fix for cwm
Source: http://www.matcl.com/?m=bbs&bid=appDB&where=subject|tag&keyword=hsk&uid=231166
PhilZ Touch official thread http://forum.xda-developers.com/showthread.php?t=2201860
Download unofficial philz cwm here
This document is unofficial (Unofficial) ported version.
There may be bugs, so please use at your own risk.
Before flashing this, you must understand the contents of this post after you decide whether to apply please.
G906S/K/L = Tested working.
Flashing guide
Flash philz cwm with Odin as AP/PDA
Uncheck Auto Reboot and Start flashing.
Once completed , disconnect the USB cable and enter recovery manually by pressing the combination key.
Recovery time and date synchronization
PhilZ Settings - GUI Preferences - Time Setup - Change date and time - Qualcomm Time Daemon and (x) check - Yes Load Time Daemon
PhilZ Settings - GUI Preferences - Time Setup - Time Zone ( your preferred timezone )
Date / time will be synchronized with the system.
Reboot device.
Known issues:
KNOX Warranty 0x1
.
Wipe Data / Factory Reset from Clean to Install a New ROM feature is not working and might brick your device. Do not use this feature. If you brick your device , you may download the stock firmware from sammobile and flash it with ODIN.
CWM does not work with adb. CWM now works with ADB
CWM does not work with aromafm.
Credit to : XDA , PhilZ , hsk , bluecloud ,dougiebee and whoever involve. Tks
.......
Click to expand...
Click to collapse
Sent from my Samsung Galaxy S3 GT-i9300 using Tapatalk 4

Great.... Bricked it.... Gonna need you guys' help again....
Did it like instructed... After flashing stuck lollipop, stuck on the second boot logo ("olleh o" for me).
Since recovery went back to stock, tried a factory reset and cache delete from the stock recovery... no help....
UPDATE: HOLD THE HELP!!! Unbricked it! On Stock Lollipop now... Working on it... Will get back to you....

Huawei P9 [ROM][Android 7.0][EMUI 5.0.1][European Firmware b394]*MagicRainbow* v3

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Huawei P9 Custom Rom​
*MagicRainbow*
Version 3
Magisk Edition and SuperSU Edition​
Note: New Version available - MagicRainbow-v4: https://forum.xda-developers.com/p9/development/rom-huawei-p9-magicrainbow-v4-t3759292
XDA DevDB Information
[L09/L19/L29][C432/C185/C636][7.0][EMUI 5.0.1] MagicRainbow v3.0 – European B394 ROM for Huawei P9 EVA
Contributors:
Tecalote
German-Thread:https://www.android-hilfe.de/forum/root-custom-roms-modding-fuer-huawei-p9.2808/huawei-p9-rom-android-7-0-emui-5-0-1-magicrainbow-v3-by-tecalote.859343.html
I'm happy to present you my third version of MagicRainbow ROM for P9-EVA
Custom ROM based on European EMUI 5.0.1 Firmware b394
Release-Date: 12. December, 2017
You can flash over Firmware b386+ until b395
- not tested over higher Firmware Versions
Security-Patch-Level: 6. November, 2017 – Krack fixed
Developed on: EVA-L09, tested also on EVA-L19
Data-Files Patches: for EVA-L19c432 and EVA-L19, EVA-L29 cust 185 and cust 636
Data Files for Chinese Brandings – not yet, but possible - just ask
EVA-L09c432 don’t need data file patch – just flash Rom
Advanced-Settings made by KangV from Huawei Rom Team: for b394 - optional flashable
KangV Settings developed on EVA-AL10 – Hide Naviagation Bar don’t work on European Brandings
Current Status: stable
Requirements:
P9 EVA-L09 - EVA-L19 - EVA-L29 - without Provider-Branding
Unlocked Bootloader
Required Firmware: Android 7 b386+ (and higher)
Installed TWRP – I recommend you to use my extended Version of OldDroids TWRP 3.1.1-1
In settings of TWRP ) disable "Keep vendor partition mounted" - but keep the setting as it is: "Exclude OEM Path from data Wipe"
You can flash from Stock Firmware as well as from EMUI based Custom Roms (like MagicRainbow v2, @dkionline ROM and so on)
Installation-Guide:
For clean flashing delete your PINs and Fingerprint(s) in current system
If you have Xposed Framework installed – uninstall it, if you decide to flash dirty
Download the Files you need, copy it to your external SD and boot to TWRP
If you decide to make Nandroid Backup with TWRP or you like to wipe internal storage – do so, but after go back to main menu and "Reboot" RECOVERY – to restart TWRP before flashing steps
If your current system has Root – make Unroot now in TWRP
For SuperSU flash UPDATE-unSU-signed.zip (download from this site): https://forum.xda-developers.com/showpost.php?p=63615067
For Magisk flash Magisk-Uninstaller: http://tiny.cc/latestuninstaller
After you have flashed Unroot with TWRP go back to main menu and choose “Reboot” RECOVERY – to restart TWRP
Go to Advanced Wipe – for clean flashing choose: data, cache and dalvik/cache – all other partition will be wiped by the ROM Script
For dirty flashing – wipe only dalvik/cache and cache – but I recommend clean flashing to have best results
Go back to main menu and open “Mount” – uncheck everything except “Micro SD” – Partitions will be mounted by the ROM Script
Now navigate to “Install” and flash MagicRainbow v3
After flashing, don’t wipe Dalvik/Cache again! – If your Phone is EVA-L09c432 you can just reboot now (first start will be until 9 min, if you took SuperSU Edition you have one extra loop)
But if your Phone is EVA-L19 or EVA-L29 – you must doing following step before Reboot Phone:
Go back to main menu, “Reboot” RECOVERY to restart TWRP and then flash the data-files_patch.zip for your Phone (EVA-L09 don’t need this step)
Setup your phone
KangV Advanced Settings:
If you decide to use KangV-Settings, which bring you a lot of customization for your Phone - you can flash the right version for Magisk-Edtition ROM or SuperSU-Edition ROM after setup.
At this Point many thanks to KangV for his great Settings!
If you decide to use another Launcher like Nova – don’t change the Launcher before flashing KangV Advanced Settings (if you like to use this Mod)
The Reboot after flashing KangV Settings needs a bit longer than normal reboot
KangV Settings for Magisk-Edition installs additional KernelAudiutor App. If you open the App you can enable init.d (optional)
If you decide to install Xposed Framework with Magisk-Edition, install it from Modul section of Magisk Manager (SDK 24) – but it will break safetynet!
Safetynet cannot come back “green” once you have Xposed activated on Magisk-Editon, even if you uninstall it – reinstalling ROM brings green safetynet back
With KangV Settings for SuperSU-Edition you can enable in More settings: Xposed Framework. Phone make reboot (start needs bit longer than usual) and you will find on a blank site of homescree the Xposed Installer for download and manager modules. In KangV Settings you can also disable Xposed Framework. So you can switch between enabled and disabled.
Xposed Framework has a FIX to stay activated (this Bug was on several Huawei Phones). The Fix comes together with KangV Settings.
KangV Settings installs additional PMPlus App – you can use it optional, if you like to activate “Auto-Launch” in Phonemanager.
If yes, just open the App PMPlus, go to install and after close the App. Open Phonemanager and you find additional: “Auto-Launch”. But now you must activate Autostarts of Apps manually, otherwise they would not start at boot or in the background. If you decide to use this, it is required to enable Magisk Manager /SuperSU in Auto-Launch– without enabling it to autostart Root cannot work. You must also enable Apps, which should receive Push-Notifications!
If you don’t like do manage everything by yourself, don’t open PMPlus, just uninstall the App with Settings /Apps before using.
The ROM is European, but Advanced Settings are made by KangV. He comes from China, thats why the Lunar component is activated.
To disable chinese letters in statusbar, go to Advanced Settings /Notification settings and disable "Show statusbar lunar"
Important notice:
Don’t use in More settings: “Disable Google Services” – and don’t use “Hide Navigation Bar” in Navigation bar settings. This is working only for Chinese Region.
Changelog:
Magisk-Edition: Magisk 14.5 by topjohnwu
Note:
For Updating Magisk-Root to v15.3 after new ROM Installation you can use this special zip for MRv3 made by Tecalote:
https://www.androidfilehost.com/?fid=817906626617958352
Just flash with TWRP and reboot (without wipe dalvik/cache)
In the meantime Magisk v16 is out... - Just do the Update with this steps: https://forum.xda-developers.com/showpost.php?p=75655877&postcount=454
Preinstalled required Magisk modules: SELinux Permissive Script, BusyBox 1.27.2 by osmOsis (Android NDK), Huawei Property Fix
Safetynet-Workaround: Open Magisk-Manager, go to menu left above into “Magisk Hide” – enable Hide for: Huawei Filemanager (com.huawei.hidisk), Google Play Store, HiCare, Huawei-ID (Huawei Mobile Services) and on devices with NFC (L09) enable NFC-Service – after you can check safetynet
ADB Debugging and USB-Debugging is not required for safetynet, but I have it enabled for the possibility to communicate everytime with ADB to my phone
System deodexed und light debloaded
Almost Apps are uninstall able with native App-Manager in settings
Working AdAway out of the Box – don’t activate systemless hosts in Magisk Manager settings.
Dolby/Atmos and Viper4Android with driver preinstalled (in both editions)
Callrecorder
Extended Reboot-Menu available with KangV-Settings (reboot to recovery, eRecovery, bootloader...)
Some beautiful designs included
Battery Life better than in Stock Firmware
SuperSU-Edition: SuperSU 2.82 SR5 by chainfire with init.d Support and SELinux Permissive enabled, BusyBox 1.27.2 by osmOsis
FIX included for staying Xposed Framework enabled - if you enable it in KangV-Settings (SuperSU Ed)
A lot of more….
Download TWRP 3.1.1-1-extended Version: https://www.androidfilehost.com/?fid=673791459329067086
Note: Developer of this TWRP is OldDroid - I just added to show and enable more Partitions to Backup.
Download ROM und K-Settings:
ROM-P9-MagicRainbow_v3-Magisk: https://www.androidfilehost.com/?fid=817906626617952424
KangV-Settings_MRv3_MagiskEd: https://www.androidfilehost.com/?fid=745849072291695763
ROM-P9-MagicRainbow_v3-SuperSU: https://www.androidfilehost.com/?fid=745849072291694710
KangV-Settings_MRv3_SuperSuEd: https://www.androidfilehost.com/?fid=817906626617953680
Download data-files_patches (EVA-L09c432 doesn’t need!!):
Note: In the moment ROM is already flashed - dont reboot system now, if you have another model/cust than L09c432 - go back to main menu and go to Restart - BUT NOT SYSTEM, you must reboot RECOVERY to restart TWRP. Then go again to install and flash the (right) data-files_patch.zip for your device!
If you would flash it directly after ROM without restart TWRP it would not be succesful installed, because the Mountpoints after flashing ROM are busy. Thats why its neccesary to reboot TWRP after ROM Installation and then flash data-files_patch according to your model and cust!
L19c432-data-files_patch-v2-update: https://www.androidfilehost.com/?fid=673791459329069646
L19c185-data-files_patch: https://www.androidfilehost.com/?fid=673791459329068282
L19c636-data-files_patch: https://www.androidfilehost.com/?fid=962021903579499478
L29c636-data-files_patch: https://www.androidfilehost.com/?fid=962021903579499481
L09c636-data-files_patch: https://www.androidfilehost.com/?fid=817906626617953681
L09c185-data-files_patch: https://www.androidfilehost.com/?fid=673791459329068279
Please check MD5 on Android Filehost and after download!
For Updates look #2
For going back to Stock Firmware look #3
HAVE MUCH FUN WITH THIS ROM
Many thanks to KangV for Advanced-Settings
If you like Advanced Settings made by KangV - you can support him: https://www.paypal.me/KangVIP
If you like *Magic-Rainbow* ROM and want to support the project, feel free to donate https://www.paypal.me/Tecalote
Many thanks and credits:
@OldDroid - TWRP with DECRYPTION SUPPORT for P9
@guitardedhero(Viper/Atmos)
@HootanParsa (MiXplorer)
@Chainfire - SuperSU
@topjohnwu (systemless Xposed Framework and Magisk)
@dkionline - Custom Roms for P9
@Blackball - Custom Roms for P8 - P9 - P 10 - P10Plus - Mate 9
@osm0sis – BusyBox for Android NDK
@ SuperR. – Best Kitchen I have ever seen
​Last Thread Update: 08.01.2018

Different Tips
Previous-Magisk-Updates
Update Magisk v15.2 to v15.3 - Difference between Direct Install and flashing Update zip by Tecalote: https://forum.xda-developers.com/showpost.php?p=75178201&postcount=333
Update Rom installed MAGISK to version 15.3 with flashable zip by Tecalote:
https://www.androidfilehost.com/?fid=817906626617958352
Just flash with TWRP and reboot (without wipe dalvik/cache)
Update Rom installed MAGISK to version 15.2 with flashable zip by Tecalote:
https://forum.xda-developers.com/showpost.php?p=75059492&postcount=222
Click to show DIRECT INSTALL Update Method:
Update Magisk 15.1 - 15.2 - 15.3 with Direct Install
https://forum.xda-developers.com/showpost.php?p=74997195&postcount=162
More info about Direct Install - without Bootloop: https://forum.xda-developers.com/showpost.php?p=74968881&postcount=108
The actual Magisk-Update is v16 - Just use this method to Update:
https://forum.xda-developers.com/showpost.php?p=75655877&postcount=454
GUIDE TO ENABLE SUBSTRATUM IN THIS ROM: https://forum.xda-developers.com/showpost.php?p=74984531&postcount=132
and some more information: https://forum.xda-developers.com/showpost.php?p=74985319&postcount=135
Apps, you should not Backup and Restore with Huawei Backup: https://forum.xda-developers.com/showpost.php?p=74941931&postcount=80
Same with Messenger-Apps - dont restore WhatsApp and Co from Titanium or Huawei Backup (Push-Notifications will not working properly)
After restoring a TWRP Backup of this ROM, Bootanimation is lost, and theres only Android Logo to see on boot.... https://www.androidfilehost.com/?fid=745849072291697149
You can flash this zip if you are on MRv3 and you will have the Rom integrated Bootanimation back.

HWOTA zips for updating Stock or going back to Stock
Here is a very easy way going back from MagicRaibow-v3 to original Huawei Firmware with HWOTA.zip - but you have to do it with the right steps!
Note: To go back from MRv3 → to Stock b394, you can use the Download Files and this Guide. For other Firmwareupdates, you find a Guide here. It is described, how you can use this method simple by yourself: https://forum.xda-developers.com/showpost.php?p=75787156&postcount=3
Credits:
Many thanks to @Atarii for special Recovery - without this it would not possible!
Users can go back from this ROM to original Huawei Firmware with following steps - you dont need Unroot !
You have no risk to test this ROM and can easy go back to Stock. It should work from every Stock based Custom Rom.
It worked also from RROS -> Stock b394
https://forum.xda-developers.com/showpost.php?p=75155089&postcount=314
It can also be used to upgrade from Stock b386 -> Stock b394
Note:
1) If you had first Stock Firmware b395 - and had installed after MRv3 ROM and want later go back to Stock Firmware - you must use the b395 HWOTA.zip. You cannot directly update to b397 or b398! That would fail! Thats why you use first b395 HWOTA.zip, after b397 HWOTA.zip and at last b398 HWOTA.zip
2) If you had first Stock Firmware b386 - and had installed MRv2 and later directly flashed MRv3 (over MRv2 without updating the Firmware) - you must use the b394 HWOTA.zip. After you can update to b397 and in the next step to b398. You cannot update from b394 directly to b398 - that would fail!
The right steps of flashing HWOTA.zips are dependend on which official Firmware you had installed before using my Rom (or any other).
b386 -> b394 -> b397 -> b398 (b397 and b398 only for L09 and L19 c432 at the moment) or:
b395 -> b397 -> b398
If your bootloader get closed (this is for example the case if you update from b386 to b394) you must reopen the bootloader and then phone makes low-lewel-wipe factoryreset. It is important that this reset is 100% successful - if not, you must perform this kind of reset manually (before delete all your pins, fingerprints and Accounts like Google, WhatsApp, Skype etc:
settings -> advanced settings -> backup & reset -> Factory data reset -> Erase internal storage -> Reset phone (internal storage will be wiped!)
Guide:
0. Make Backup of your stuff and copy folders from internal Storage to a folder on external SD (WhatsApp folder, DCIM, Pictures, Downloads...) Be sure in Developer Options is 1) ADB Debugging in charging mode and 2) USB Debugging enabled and of course 3) OEM Unlock (should be enabled by default if you are using Custom Rom)
1. Download right HWOTA.zip for your Device and Cust - unzipp it on PC - you have now unzipped HWOTA folder
2. Copy unzipped HWOTA folder to the main directory of your EXTERNAL SD (dont place it in subfolders!)
3. HWOTA folder contains 3 Files:
A) Folder with number (it is the correct Number of Firmware-Version) Inside are 3 zipped Firmware-Files - dont touch it, dont unzipp it!
B) EVA_xxx_nocheckrecovery.img
C) hwota_update.zip
4. Boot to TWRP and navigate to the HWOTA folder and flash hwota_update.zip
5. Screen become black and in a view seconds Stock Recovery is flashed and Firmware is loaded
6. EMUI Software Installing installs now the originial Firmware, wait until it is 100% and device will reboot
7. Go to settings /advanced settings/ Backup and restore and do a Factoryreset with wipe of internal Storage
8. Soon Factoryreset is finished and device begin to reboot, press Vol+ on your Phone to boot into Stock Recovery instead of system
9. Make Wipe Cache Partition!
10. Now you have clean original Stock Huawei Firmware and if a OTA is avialable - you can do it without problems (but SIM must be inserted)
Note: During the Upgrade - the Firmware zips inside the unzipped HWOTA folder on external SD will be deleted by Stock Recovery (unzipped folder can be used just onetimes) - if you decide to use it again in another situation keep the downloaded zip....
Downloads for L09:
EVA-L09-c432 b394 HWOTA.zip: [url]https://www.androidfilehost.com/?fid=817906626617956737[/URL]
MD5: 895923ee5d8e4de7dedf9d96b84cd388
EVA-L09-c185 b394 HWOTA.zip: https://www.androidfilehost.com/?fid=745849072291700568
MD5: b249285cfa6a75d46bb937d9f6c342b0
EVA-L09-c636 b394 HWOTA.zip: https://www.androidfilehost.com/?fid=962157660013071602
MD5: e76c5edcb0401cd993fa1f46262beaa5
Downloads for L19:
EVA-L19-c432 b392 HWOTA.zip: [url]https://www.androidfilehost.com/?fid=962157660013070163[/URL]
MD5: 9813212ef8933df637402fab137fb9d3
EVA-L19-c185 b394 HWOTA.zip: https://www.androidfilehost.com/?fid=962157660013070477
MD5: 99883e7f2c351ed36755dd04c45be347
EVA-L19-c636 b394 HWOTA.zip: https://www.androidfilehost.com/?fid=962157660013070988
MD5:d2bd88a021fc280672d26e223a0a29cb
Downloads for L29:
EVA-L29-c636 b394 HWOTA.zip: https://www.androidfilehost.com/?fid=673791459329073605
MD5: 87b4ea112660ec70fee1dc407ccb957e
The latest Firmware for EVA-L09 - EVA-L19 - EVA-L29 Cust c636 is b395 - is available as FullOTA-MF-PV version - you can flash it directly with TWRP
1) You need three zips:
A) Update.zip
B) Update_data_full_public.zip
C) Update_full_EVA-Lxx_hw_spcseas.zip - it must match the EVA model you have - EVA-L09 or EVA-L19 or EVA-L29
2) You flash in this order:
A) Update.zip
- dont boot to system - flash
B) Update_data_full_public.zip
- dont boot to system - flash
C) Update_full_EVA-Lxx_hw_spcseas.zip
- dont boot to system - go back to main menu and use restart - but: RECOVERY
3) In Stock Recovery make A) Wipe Cache Partition and B) Factoryreset - after reboot P9
Note: internal storage get wiped with this method - so backup everything you need from internal storage, before updating your Firmware with this method!
Download:
Update.zip: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1864/g1755/v114776/f1/full/update.zip
Update_data_full_public.zip: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1864/g1755/v114776/f1/full/public/update_data_full_public.zip
From the next zips you need only one (the right one) for your device:
Update_full_EVA-L19_hw_spcseas.zip:http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1864/g1755/v114776/f1/full/EVA-L19_hw_spcseas/update_full_EVA-L19_hw_spcseas.zip
Update_full_EVA-L29_hw_spcseas.zip: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1864/g1755/v114776/f1/full/EVA-L29_hw_spcseas/update_full_EVA-L29_hw_spcseas.zip
Update_full_EVA-L09_hw_spcseas.zip: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1864/g1755/v114776/f1/full/EVA-L09_hw_spcseas/update_full_EVA-L09_hw_spcseas.zip
German Guide:
[url]https://www.android-hilfe.de/forum/root-custom-roms-modding-fuer-huawei-p9.2808/huawei-p9-rom-android-7-0-emui-5-0-1-magicrainbow-v3-by-tecalote.859343.html#post-10819769[/URL]

I couldn't wait and I installed from the DE forum. Dirty Flash on L19C432. Except the bug on K-Settings with left alignment, this is a blazing fast Rom. Thank you very much!

I want to use MagicRainbow with supersu and KanV settings I should download this one right ?
KangV-Settings_MRv3_SuperSuEd: https://www.androidfilehost.com/?fid=817906626617953680
I have stock b394 with twrp 3.1.1 and supersu.
Could I make these steps.
- twrp flash unsu
- reboot to twrp
- advanced wipe data, cache and dalvik/cache
- Mount – uncheck everything except “Micro SD”
- Install and flash MagicRainbow v3
reboot

netaccs said:
I want to use MagicRainbow with supersu and KanV settings I should download this one right ?
KangV-Settings_MRv3_SuperSuEd: https://www.androidfilehost.com/?fid=817906626617953680
I have stock b394 with twrp 3.1.1 and supersu.
Could I make these steps.
- twrp flash unsu
- reboot to twrp
- advanced wipe data, cache and dalvik/cache
- Mount – uncheck everything except “Micro SD”
- Install and flash MagicRainbow v3
reboot
Click to expand...
Click to collapse
Yes, right
You need this KangV zip in addition for the SuperSU Edition Rom.
The steps are right.
Flash first ROM and wait until it reboot to the system (don't panic - first boot will be canceled by systemless Rooting with SuperSU, after it boots up again and needs maybe 9 minutes to start into EMUI Setup)
After setup you can boot again to TWRP and flash KangV Settings zip.
If you decide to change Huawei Launcher to Nova (or whatever) do it after flashing KangV Settings.
Wish you success and much fun with MagicRainbow

I am new to the huawei scene. I have worked on a lot of samsung projects but this is a completely new world. I have been using your v2 for a week and now cant wait to use v3. Keep up the good work mate.

Came from NewWorld 7, finally on Nougat this rom is fantastic, everything works so far, thank you very much Tecalote.

What's the difference between Magisk and SuperSU? Any major differences that would help? And also, when you have super su that means you can have Xposed? Thank you in advance and for the good rom

Tecalote said:
Yes, right
You need this KangV zip in addition for the SuperSU Edition Rom.
The steps are right.
Flash first ROM and wait until it reboot to the system (don't panic - first boot will be canceled by systemless Rooting with SuperSU, after it boots up again and needs maybe 9 minutes to start into EMUI Setup)
After setup you can boot again to TWRP and flash KangV Settings zip.
If you decide to change Huawei Launcher to Nova (or whatever) do it after flashing KangV Settings.
Wish you success and much fun with MagicRainbow
Click to expand...
Click to collapse
Am i understand correctly ?
First installing the ROM -> P9-MagicRainbow_v3-SuperSU.zip
after complete and reboots, have to flash via twrp -> KangV-Settings_MRv3_SuperSuEd

netaccs said:
Am i understand correctly ?
First installing the ROM -> P9-MagicRainbow_v3-SuperSU.zip
after complete and reboots, have to flash via twrp -> KangV-Settings_MRv3_SuperSuEd
Click to expand...
Click to collapse
Yes, that's right

RandomQuezoPH said:
What's the difference between Magisk and SuperSU? Any major differences that would help? And also, when you have super su that means you can have Xposed? Thank you in advance and for the good rom
Click to expand...
Click to collapse
If you like to use Xposed Framework - take SuperSU Edition and flash after first setup KangV Settings.
It includes a patch for Xposed Framework.
You can enable/disable in KangV Advanced Settings /More Settings /Xposed Framework the Framework.
After enabling it you must reboot and find then Xposed Installer on a blank site of Homescreen. (for download and activate Modules)
Magisk Edition is for green safetynet, without Xposed.
Xposed cannot have green safetynet

On almost Huawei Phones Xposed Framework after reboot is deactivated by itself - it's a Bug on EMUI.
But not in this SuperSU Edition Rom with KangV Settings.
Xposed Framework will stay enabled until you decide to disable it

Can I somehow add used mobile data to notification screen, like it was on NewWorld 7?

frozenfry said:
Can I somehow add used mobile data to notification screen, like it was on NewWorld 7?
Click to expand...
Click to collapse
Nope, not in the European Firmware Rom.
NewWorld was on Android 6 with Chinese Cust.
It was working in European Regions - but no more in Android 7.
Nougat has more restricted rules and laws.
BTW: It was a part of the Phonemanager like the Permission Manager, which was available on Android 5 in Europe, and in Android 6 which Chinese Rom on European Phones.
It's interesting :
Phonemanager apk is the same on EVA-AL10 - there it has all those features.
But not on our branding.
I found no hack until now - but I am working on it
But otherwise Google Services are not running properly on Chinese Branding
That's difficult...

Magisk Manager Update available (for Magisk Edition)
If you restart Phone or open Magisk Manager may you receive an Update notification in statusbar and the phone vibrates - Magisk show you an Update for the Manager (Version 5.5.0.80). You can open native settings /apps / Magisk Manager /permissions and allow Magisk the permission for storage or you will get the question, if you open Magisk Manager (allow it). After let Magisk Manager download and install the new version.
Changelog see screenshots. After the update I had in advanced options "force encryption" enabled. if you get the same setting automatically, keep this as is

frozenfry said:
Can I somehow add used mobile data to notification screen, like it was on NewWorld 7?
Click to expand...
Click to collapse
If anyone is interested, this app is the solution.

frozenfry said:
If anyone is interested, this app is the solution.
Click to expand...
Click to collapse
But you can also setup in Phonemanager "mobile data" and open the settings symbol and make there your settings (even possible notification in Statusbar)
After reboot your phone and after a while you receive notifications..
It's not the same than in NewWorld, but similar

my wifi turn off sometimes after the screen goes off. I have the same issue on bluewei with base B394.
L19 model.

NervReaper said:
my wifi turn off sometimes after the screen goes off. I have the same issue on bluewei with base B394.
L19 model.
Click to expand...
Click to collapse
Have you flashed the L19 patch for your cust immediately after flashing Rom before first Reboot?
Have you checked different settings?
1) In native settings /WLAN / WLAN+ should be enabled.
2) In settings /Akku right above the settings symbol / WLAN in Standby Mode = always on
(same setting for mobile data =always on)

A12s Exynos 850 Development Kernel and TWRP for a127f u2 (Exynos 850)

I have built a custom kernel for the a127f Exynos 850
I've also included a link to more custom recoveries in post#2
physwizz a12s kernel version 4
Based on a127f
NOT for baseband u3 or higher
For OneUI 3.1
( also works for GSIs)
Samsung securities disabled
More CPU governors
Conservative, On-demand, Userspace, powersave, performance, energy_step, shedutil
Optimised for performance
Overclocked for performance
Underclocked for battery
CPU: 130MHz - 2210MHz
lz4 compression added to zram
Ready for spectrum installation
Installation
Method 1
Install from TWRP
Method 2
Install adb tools on pc
Connect to PC
Copy zip file to adb folder on pc
Open terminal on pc
Navigate to adb folder
Type
adb sideload name.zip
For Zram
Go to HKtweaks- virtual memory
Turn off zram
increase swappiness to 200
choose lz4
increase size to 4096
turn on Zram
Kernel
physwizz - Repositories
physwizz has 172 repositories available. Follow their code on GitHub.
github.com
@physwizz

Root and TWRP
NOT for baseband u3 or higher
Download zip file.
Extract recovery.img from tar file
Method 1.
If you have already installed recovery and decrypted.
1. Boot to recovery.
2. Install recovery.img
3. Choose recovery partition
4. Reboot to recovery
Method 2.
From the start
1. Download firmware
2. Extract ap file.
3. Patch with special magisk
4. Flash with Odin
5. Download tar and extract recovery.img
6. Install TWRP app
7. Install TWRP
8. Choose file to flash.(don't select device)
9. Select recovery.img.
10. Reboot to recovery.
10. Wipe, format data, type YES.
11. Advanced, terminal.
Type multidisabler (twice).
Reboot to recovery
12. Backup boot, data, super and dtbo
@physwizz
Links
A127f on XDA
More custom recoveries
M127f on telegram

I know that one brave person has downloaded this kernel.
Any feedback?

physwizz said:
I know that one brave person has downloaded this kernel.
Any feedback?
Click to expand...
Click to collapse
Well, you are right, I did download it but I'm scared to try, I think once I unlock the bootloader,
1. I'll not be able to re-lock it
2. I only have a raspberry Pi 3B+ and hence can't use Odin to restore of something goes wrong
3. I can't run the banking apps anymore due to Knox trip status
4. And if Knox trips, going to stock fully is going to be impossible, and Knox features will be unusable
And to top these all off, it's the new phone of my parents, they had a moto they previously lost, if their apps don't work after I do something, I'll be screwed over... :/

Hausemaster said:
Well, you are right, I did download it but I'm scared to try, I think once I unlock the bootloader,
1. I'll not be able to re-lock it
2. I only have a raspberry Pi 3B+ and hence can't use Odin to restore of something goes wrong
3. I can't run the banking apps anymore due to Knox trip status
4. And if Knox trips, going to stock fully is going to be impossible, and Knox features will be unusable
And to top these all off, it's the new phone of my parents, they had a moto they previously lost, if their apps don't work after I do something, I'll be screwed over... :/
Click to expand...
Click to collapse
lol
I understand

physwizz said:
I know that one brave person has downloaded this kernel.
Any feedback?
Click to expand...
Click to collapse
I have the Galaxy M127F / DS and I have problems installing a custom recovery, I have tried many but cannot finish successfully. I have root and it was as far as I could go, I miss my A20, by the way the binary is 2.
When I install any of the recovery that you uploaded, it sends me the statement "Recovery: No footer detected. (0)
Recovery: Error verifying vbmeta image: invalid vbmeta header (6) "
I don't know why this is, I hope you can help me, please.

Jeremia121 said:
I have the Galaxy M127F / DS and I have problems installing a custom recovery, I have tried many but cannot finish successfully. I have root and it was as far as I could go, I miss my A20, by the way the binary is 2.
When I install any of the recovery that you uploaded, it sends me the statement "Recovery: No footer detected. (0)
Recovery: Error verifying vbmeta image: invalid vbmeta header (6) "
I don't know why this is, I hope you can help me, please.
Click to expand...
Click to collapse
Did you root with the patched ap file
(Patched by special magisk I posted)

physwizz said:
Did you root with the patched ap file
(Patched by special magisk I posted)
Click to expand...
Click to collapse
I rooted the AP file from Magisk patched for A21s, I have only successfully managed to root.

Jeremia121 said:
I rooted the AP file from Magisk patched for A21s, I have only successfully managed to root.
Click to expand...
Click to collapse
Is your baseband U2 or u3?

A12/M12 versions
A12/M12 versions All of these are considered by Samsung to be A12 models Normally the A127f would be called A12S but Oppo already has an a12s MT6865 Helio p35 models 2.3GHz, 1.8GHz SM-A125U SM-A125U1 SM-A125F SM-A125W SM-A125M SM-A125G A12...
forum.xda-developers.com

V5

Thanks

physwizz said:
I have built a custom kernel for the a127f Exynos 850 which should work on the m127f.
I've also included a link to more custom recoveries in post#2
physwizz a12s kernel version 4
Based on a127f
NOT for baseband u3 or higher
For OneUI 3.1
( also works for GSIs)
Samsung securities disabled
More CPU governors
Conservative, On-demand, Userspace, powersave, performance, energy_step, shedutil
Optimised for performance
Overclocked for performance
Underclocked for battery
CPU: 130MHz - 2210MHz
lz4 compression added to zram
Ready for spectrum installation
Installation
Method 1
Install from TWRP
Method 2
Install adb tools on pc
Connect to PC
Copy zip file to adb folder on pc
Open terminal on pc
Navigate to adb folder
Type
adb sideload name.zip
For Zram
Go to HKtweaks- virtual memory
Turn off zram
increase swappiness to 200
choose lz4
increase size to 4096
turn on Zram
Kernel
physwizz - Repositories
physwizz has 172 repositories available. Follow their code on GitHub.
github.com
@physwizz
Click to expand...
Click to collapse
Can i use this to unlock the network sim lock?

judynar22 said:
Can i use this to unlock the network sim lock?
Click to expand...
Click to collapse
no

Development Pixel Experience For Samsung galaxy a12

What is this?
Pixel Experience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation)
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
Based on Android 12.0 (11 is available but 12 has no difference in terms of issues and is faster an the better ui and everything else of course)
Disclaimer:- This will void warranty.
You will need to unlock bootloader.
*All your data will be lost*
Read all the steps correctly
BUGS:- bluetooth ear/headphones do not work workaround- ( go into phh treble settings misc features and enable force-disable a2dp offload (thanks to @Lil_Boudy for figuring it out!)
If bluetooth crashes your system disable media recommendations under Sound & Vibration > Media > Show media recommendations
mtp not working (mtp does work in twrp and in some custom kernels the one linked here does not fix mtp as it is not changing too many things compared to other custom kernels which brick some phones)
sim 1 incoming and outgoing does not work (you can revieve calls and call but you wonth hear anything nor will your mic go trying to fix) (workaround is to put your sim into slot 2) (i have heard that other people dont have this issue so i guess try your luck)
DO NOT let the phone die of battery you will not be able to boot you can get back by holding volume down and power (workaround- in magisk install acca https://github.com/Magisk-Modules-Repo/acc and install this apk after installing https://github.com/MatteCarra/AccA then set profile to default (this will shut down the phone at 5% hence removing the risk of your phone not booting after hitting 0%
You tell me
Links
Source (Kernel Source)
https://github.com/topjohnwu/Magisk/files/7819803/app-debug.zip (magisk)
Rom download.
1.Need TWRP 3.4.0 or higher!
2. Unpack the "xz" archive and put the .img file onto the sd card or internal (if you dont have a sd card do step 3 then transfer the img file to your phone)
3. In TWRP head to factory reset format type yes and hit enter
4. Flash the img file (as system obviously)
5 install magisk (the one linked above only) (optional but you should as a lot of modules are listed here are very important (ie the acc module and the fast charging module)
5.5.Reboot and enjoy!
Zainullah Boot fix (if you cant boot)
install oneui boot into oneui change date to 3 months from now
check for updates
boot into download mode
flash twrp 3.6.0 and vbmeta
boot into twrp
do format data
flash multidisabler
flash rom
flash kernel as boot
do factory reset
reboot
if it boots you into fastboot shutdown flash twrp only and try another factory reset and reboot (In twrp)
Install Gcam go by greatness from here
https://www.celsoazevedo.com/files/android/google-camera/dev-greatness/f/dl9/
also enable extra cameras in phh treble settings - samsung settings for ultrawide
Increase performance without any battery impact or (by feravolt and gloeysik)
Step 1
- Uninstall ANY OTHER KERNEL MANAGER app including smartpack/Ktweaks to avoid conflict, since this app uses AI and machine learning to dynamically boost performance when needed
- Install FDE AI Magisk Module to make it a system app, thus it will work better and removes all kernel locks from OEMs (I'm looking at you, Samsung) https://github.com/feravolt/FDE.AI-docs/releases/download/12.4.1m/FDE.AI-as-system-app.MAGISK.zip
- Update FDE AI to the latest version by downloading the latest APK here, since the fde ai magisk module will only install fde ai 12.4.1, not the latest version: https://github.com/feravolt/FDE.AI-docs/releases
- Move to the bottom of the screen and select AI Chat, then type /advancedai (no space, no uppercase letters). This will going to make the AI more effective, without you having to do anything.
- Go to the settings tab and use the AUTO settings for FDE AI.
Optimized and adjusted Google Play services. Contribute to gloeyisk/universal-gms-doze development by creating an account on GitHub.
github.com
install cloudflaredns4magisk (install both ipv4 and ipv6 versions) (this will switch you to cloudflares faster and more secur dns
Cloudflare dns magisk download​
install adaway (optional if you want ads or not) , allow superuser for it download this https://energized.pro/bluGo/formats/filter in adaway click he button in the middle click add click file and add the file then go back to the main menu and click the reload button now https://adaway.org/
(you get better battery and performance in adaway)
also enable extra cameras in phh treble settings - samsung settings for ultrawide
install universal safteynet fix zygsik (magisk)to get safteynet working
enable denylist for apps you want to hide root from (dont enable it for google play services as it is not needed)
ALL credit goes to phusson , ponces and rest of the devs
Blog
Pixel Experience
Donate
jhenrique09
phhusson
AndyYan
eremitein
ponces

.

.

Reserved

You set it for as a question xD. Also for what model is this made?
Thanks for your work.

LAST_krypton said:
You set it for as a question xD. Also for what model is this made?
Thanks for your work.
Click to expand...
Click to collapse
it works on all models

Zainullahk1234 said:
What is this?
Pixel Experience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation)
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
Based on Android 12.0 (11 is available but 12 has no difference in terms of issues and is faster an the better ui and everything else of course)
Disclaimer:- This will void warranty.
You will need to unlock bootloader.
*All your data will be lost*
Read all the steps correctly
BUGS:- bluetooth ear/headphones do not work workaround- ( go into phh treble settings misc features and enable force-disable a2dp offload (thanks to @Lil_Boudy for figuring it out!)
If bluetooth crashes your system disable media recommendations under Sound & Vibration > Media > Show media recommendations
mtp not working (mtp does work in twrp and in some custom kernels the one linked here does not fix mtp as it is not changing too many things compared to other custom kernels which brick some phones)
sim 1 incoming and outgoing does not work (you can revieve calls and call but you wonth hear anything nor will your mic go trying to fix) (workaround is to put your sim into slot 2) (i have heard that other people dont have this issue so i guess try your luck)
DO NOT let the phone die of battery you will not be able to boot you can get back by holding volume down and power (workaround- in magisk install acca https://github.com/Magisk-Modules-Repo/acc and install this apk after installing https://github.com/MatteCarra/AccA then set profile to default (this will shut down the phone at 5% hence removing the risk of your phone not booting after hitting 0%
You tell me
Links
Source (Kernel Source)
https://github.com/topjohnwu/Magisk/files/7819803/app-debug.zip (magisk)
Rom download.
1.Need TWRP 3.4.0 or higher!
2. Unpack the "xz" archive and put the .img file onto the sd card or internal (if you dont have a sd card do step 3 then transfer the img file to your phone)
3. In TWRP head to factory reset format type yes and hit enter
4. Flash the img file (as system obviously)
5 install magisk (the one linked above only) (optional but you should as a lot of modules are listed here are very important (ie the acc module and the fast charging module)
5.5.Reboot and enjoy!
Zainullah Boot fix (if you cant boot)
install oneui boot into oneui change date to 3 months from now
check for updates
boot into download mode
flash twrp 3.6.0 and vbmeta
boot into twrp
do format data
flash multidisabler
flash rom
flash kernel as boot
do factory reset
reboot
if it boots you into fastboot shutdown flash twrp only and try another factory reset and reboot (In twrp)
Install Gcam go by greatness from here
https://www.celsoazevedo.com/files/android/google-camera/dev-greatness/f/dl9/
also enable extra cameras in phh treble settings - samsung settings for ultrawide
Increase performance without any battery impact or (by feravolt and gloeysik)
Step 1
- Uninstall ANY OTHER KERNEL MANAGER app including smartpack/Ktweaks to avoid conflict, since this app uses AI and machine learning to dynamically boost performance when needed
- Install FDE AI Magisk Module to make it a system app, thus it will work better and removes all kernel locks from OEMs (I'm looking at you, Samsung) https://github.com/feravolt/FDE.AI-docs/releases/download/12.4.1m/FDE.AI-as-system-app.MAGISK.zip
- Update FDE AI to the latest version by downloading the latest APK here, since the fde ai magisk module will only install fde ai 12.4.1, not the latest version: https://github.com/feravolt/FDE.AI-docs/releases
- Move to the bottom of the screen and select AI Chat, then type /advancedai (no space, no uppercase letters). This will going to make the AI more effective, without you having to do anything.
- Go to the settings tab and use the AUTO settings for FDE AI.
Optimized and adjusted Google Play services. Contribute to gloeyisk/universal-gms-doze development by creating an account on GitHub.
github.com
install cloudflaredns4magisk (install both ipv4 and ipv6 versions) (this will switch you to cloudflares faster and more secur dns
Cloudflare dns magisk download​
install adaway (optional if you want ads or not) , allow superuser for it download this https://energized.pro/bluGo/formats/filter in adaway click he button in the middle click add click file and add the file then go back to the main menu and click the reload button now https://adaway.org/
(you get better battery and performance in adaway)
also enable extra cameras in phh treble settings - samsung settings for ultrawide
install universal safteynet fix zygsik (magisk)to get safteynet working
enable denylist for apps you want to hide root from (dont enable it for google play services as it is not needed)
ALL credit goes to phusson , ponces and rest of the devs
Blog
Pixel Experience
Donate
jhenrique09
phhusson
AndyYan
eremitein
ponces
Click to expand...
Click to collapse
Whre is the ROM?

leonardo07746 said:
Whre is the ROM?
Click to expand...
Click to collapse
GitHub - zainullahk/universal-pixelexperience-samsung: this is pixel experience by ponces think of this as a mirror but tailored to samsung devices
this is pixel experience by ponces think of this as a mirror but tailored to samsung devices - GitHub - zainullahk/universal-pixelexperience-samsung: this is pixel experience by ponces think of th...
github.com

Zainullahk1234 said:
it works on all models
Click to expand...
Click to collapse
HI.. Filthy iOS user here with minimal experience loading custo roms - I have the newer A13 that appears to be the A12 in a newer housing.. Will this work?
This Samsung bloat is is ridiculous

Sean2e said:
HI.. Filthy iOS user here with minimal experience loading custo roms - I have the newer A13 that appears to be the A12 in a newer housing.. Will this work?
This Samsung bloat is is ridiculous
Click to expand...
Click to collapse
u have an a13 and it says its an a12 doesnt make sense

dav1234444 said:
u have an a13 and it says its an a12 doesnt make sense
Click to expand...
Click to collapse
I meant in terms of hardware, My A13 uses the same exynos 850 & Mali gpu as the A12.
Compare Samsung Galaxy A12 (India) vs. Samsung Galaxy A13 - GSMArena.com
m.gsmarena.com

can someone send a screenshot of this rom?

sigpurnomo said:
can someone send a screenshot of this rom?
Click to expand...
Click to collapse
{
"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"
}

Hidden User said:
Click to expand...
Click to collapse
hi I unlock boot loder my samsung a12 and flash twrp officall but i can not login to recovery for install this rom. now This page is displayed for me

imirsay said:
hi I unlock boot loder my samsung a12 and flash twrp officall but i can not login to recovery for install this rom. now This page is displayed for me
Click to expand...
Click to collapse
You should also flash vmbeta

Sheepmister said:
You should also flash vmbeta
Click to expand...
Click to collapse
ok thanks.
[AOSP-11] [OFFICIAL] Samsung SM-A125F TWRP
DISCLAIMER: I WAS NEVER, HAVE NEVER BEEN, AND WILL NEVER BE RESPONSIBLE OF ANY DAMAGES AGAINST YOUR DEVICES BY YOUR OWN MIS-OPERATIONS Install instructions: 1. Download an arbitrary SM-A125F firmware zip package on SamMobile.com, whose Android...
forum.xda-developers.com

imirsay said:
hi I unlock boot loder my samsung a12 and flash twrp officall but i can not login to recovery for install this rom. now This page is displayed for me
Click to expand...
Click to collapse
I installed TWRP by rooting then installing TWRP Official on the Play Store

Zainullahk1234 said:
Zainullahk1234 said:
install universal safteynet fix zygsik (magisk)to get safteynet working
enable denylist for apps you want to hide root from (dont enable it for google play services as it is not needed)
ALL credit goes to phusson , ponces and rest of the devsi
Click to expand...
Click to collapse
Click to expand...
Click to collapse
status bar and swip to unlock screan doesn't work and it gets fixed after a few seconds

Zainullahk1234 said:
What is this?
Pixel Experience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation)
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
Based on Android 12.0 (11 is available but 12 has no difference in terms of issues and is faster an the better ui and everything else of course)
Disclaimer:- This will void warranty.
You will need to unlock bootloader.
*All your data will be lost*
Read all the steps correctly
BUGS:- bluetooth ear/headphones do not work workaround- ( go into phh treble settings misc features and enable force-disable a2dp offload (thanks to @Lil_Boudy for figuring it out!)
If bluetooth crashes your system disable media recommendations under Sound & Vibration > Media > Show media recommendations
mtp not working (mtp does work in twrp and in some custom kernels the one linked here does not fix mtp as it is not changing too many things compared to other custom kernels which brick some phones)
sim 1 incoming and outgoing does not work (you can revieve calls and call but you wonth hear anything nor will your mic go trying to fix) (workaround is to put your sim into slot 2) (i have heard that other people dont have this issue so i guess try your luck)
DO NOT let the phone die of battery you will not be able to boot you can get back by holding volume down and power (workaround- in magisk install acca https://github.com/Magisk-Modules-Repo/acc and install this apk after installing https://github.com/MatteCarra/AccA then set profile to default (this will shut down the phone at 5% hence removing the risk of your phone not booting after hitting 0%
You tell me
Links
Source (Kernel Source)
https://github.com/topjohnwu/Magisk/files/7819803/app-debug.zip (magisk)
Rom download.
1.Need TWRP 3.4.0 or higher!
2. Unpack the "xz" archive and put the .img file onto the sd card or internal (if you dont have a sd card do step 3 then transfer the img file to your phone)
3. In TWRP head to factory reset format type yes and hit enter
4. Flash the img file (as system obviously)
5 install magisk (the one linked above only) (optional but you should as a lot of modules are listed here are very important (ie the acc module and the fast charging module)
5.5.Reboot and enjoy!
Zainullah Boot fix (if you cant boot)
install oneui boot into oneui change date to 3 months from now
check for updates
boot into download mode
flash twrp 3.6.0 and vbmeta
boot into twrp
do format data
flash multidisabler
flash rom
flash kernel as boot
do factory reset
reboot
if it boots you into fastboot shutdown flash twrp only and try another factory reset and reboot (In twrp)
Install Gcam go by greatness from here
https://www.celsoazevedo.com/files/android/google-camera/dev-greatness/f/dl9/
also enable extra cameras in phh treble settings - samsung settings for ultrawide
Increase performance without any battery impact or (by feravolt and gloeysik)
Step 1
- Uninstall ANY OTHER KERNEL MANAGER app including smartpack/Ktweaks to avoid conflict, since this app uses AI and machine learning to dynamically boost performance when needed
- Install FDE AI Magisk Module to make it a system app, thus it will work better and removes all kernel locks from OEMs (I'm looking at you, Samsung) https://github.com/feravolt/FDE.AI-docs/releases/download/12.4.1m/FDE.AI-as-system-app.MAGISK.zip
- Update FDE AI to the latest version by downloading the latest APK here, since the fde ai magisk module will only install fde ai 12.4.1, not the latest version: https://github.com/feravolt/FDE.AI-docs/releases
- Move to the bottom of the screen and select AI Chat, then type /advancedai (no space, no uppercase letters). This will going to make the AI more effective, without you having to do anything.
- Go to the settings tab and use the AUTO settings for FDE AI.
Optimized and adjusted Google Play services. Contribute to gloeyisk/universal-gms-doze development by creating an account on GitHub.
github.com
install cloudflaredns4magisk (install both ipv4 and ipv6 versions) (this will switch you to cloudflares faster and more secur dns
Cloudflare dns magisk download​
install adaway (optional if you want ads or not) , allow superuser for it download this https://energized.pro/bluGo/formats/filter in adaway click he button in the middle click add click file and add the file then go back to the main menu and click the reload button now https://adaway.org/
(you get better battery and performance in adaway)
also enable extra cameras in phh treble settings - samsung settings for ultrawide
install universal safteynet fix zygsik (magisk)to get safteynet working
enable denylist for apps you want to hide root from (dont enable it for google play services as it is not needed)
ALL credit goes to phusson , ponces and rest of the devs
Blog
Pixel Experience
Donate
jhenrique09
phhusson
AndyYan
eremitein
ponces
Click to expand...
Click to collapse
When I unlock the screen with my fingerprint. The touch screen does not work for a few moments.

Zainullahk1234 said:
DO NOT let the phone die of battery you will not be able to boot you can get back by holding volume down and power (workaround- in magisk install acca https://github.com/Magisk-Modules-Repo/acc and install this apk after installing https://github.com/MatteCarra/AccA then set profile to default (this will shut down the phone at 5% hence removing the risk of your phone not booting after hitting 0%
Click to expand...
Click to collapse
If the phone is turned off, will the data be deleted?
Can you explain more for beginners like me?
I turned on the phone screen in this video. See the delay in execution.

[A/B][A-ONLY][SCRIPT][READ-ONLY][EROFS][ANDROID 10+] Universal Disable Force Encryption for RO and RW "NEO STABLE"

Disable Force Encryption NEO​Do you all know what DFE is? no?
Anyway. Basically, your device has an encrypted data section "/data" by default. Let's look at the advantages of google's solution that we will lose after disabling encryption:
- Confidence in data retention. Even if your device has TWRP/OFOX or other custom Recvoery, before accessing your data, you will need to enter the password from the lockscreen, otherwise it will be impossible to read the data.
What disadvantages follow from this?
- As an enthusiast who wants to flash different ROMs, you may have noticed that every time that you flash a new ROM, you have to format the "/data" section. Which can be a pain.
Why is it necessary to do this?
- The fact that every ROM is assembled/compiled on a different database and may have different approaches (encryption keys) for data encryption. In order for this to work you need to format the data partition so that when the new ROM boots it can encrypt the system with its own unique encryption keys, so that the integrity of the data partition is maintained and it is accessible to the user.
So what does the DFE do?
- Removes the keys that are used to encrypt the data section from the fstab file
Read more about fstab here source.android.com
What are the advantages of using DFE?
- You don't need to FORMAT the data in the following cases:
*If you change the android database (From 11 to 12 and vice versa)
*If you change vendor database, miui/aosp/OOS/LOS and so on
*** !!!! You will still need to make wipe data for the ROM to work correctly
-There are also disadvantages:
*Since the data is not encrypted in any way, then access to them is free. Anyone who gets access to your device will be able to access ALL the data
*You need to carefully monitor the sequence of actions when installing or changing the ROM, so that the DFE is active, otherwise you may lose data because the data will try to be encrypted again, you will get a bootloop, and all data will be lost
What is DFE-NEO?
*Many people know DFE from this thread XDA, it has stopped working for A/B devices with dynamic partitions, there is also a problem that in some ROMs the system has the RO(Read-Only) status of the system partition. Starting with A13 Google will promote EROFS(Enhanced Read-Only File System) which will not be possible to manipulate without first converting to EXT4, in order to change the status to RW(Read-Write). Because of this, it is not possible to modify fstab directly in 100% of cases. This is where DFE-NEO comes in.
*The NEO method works by utilizing Magiskinit and Overlay.d GitHub
How does it work without Magisk?
*In fact, in no way. If my script does not detect magisk in the boot_a/Boot_b section, magisk will be installed, after which the main bianrys files will be deleted, so there will be no root access but magiskinit itself will continue to work. In this regard, the system boot time will be longer by 40-50 seconds ( from the brand logo )
And so what can this script do:
-Hides Encryption - Forces the system to think that the data is encrypted.
-Reflash recovery after OTA - only for devices with recovery in boot_a/_b
-Flash current recovery - only for devices with recovery in boot_a/_b
-Flash DFE
-Flash magisk
Spoiler: Arguments.txt
{
"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"
}
If you want to change the parameters , then you need to change the file argumetns.txt inside the archive , or put the modified arguments.txt to the archive, or to rebuild the archive with the changed argumetns.txt
Code:
# legacy or neo
DFE method=neo
# both | in-current | un-current
Flash SLOT=both
# none|system|bootloader|recovery
Reboot after installing=none
# You can add your own language, to do this, just drop
a file into the language folder by analogy with the topic
that is already there
# indo|russian|english
Language=english
Code:
# ================================================== #
Force reading arguments.txt=false
# ================================================== #
Flash DFE= true
Disable AVB= true
Disable QUOTA= true
Hide not encrypted= true
# ================================================== #
Flash Magisk= false
# ================================================== #
Reflash Recovery for OTA= false
Reflash current Recovery for Recovery= false
# ================================================== #
Wipe DATA= false
Remove PIN= false
# ================================================== #
Skip warning= false
Modes of operation of these parameters
These parameters have two modes:
• true (yes, true),
• false(no, not true)
Exceptions for specific parameters
• DFE method(DFE method)= neo(new method)
Another argument for DFE method
legacy(old method)
• Flash slot= both (patching boot_a and boot_b sections, also applies to magisk firmware, twrp)
More arguments for Flash slot
• in-current (patching of the boot_x section, where x is the current slot, also applies to magisk firmware, twrp)
• un-current (patching the boot_x partition, where x is the opposite slot)
• Reboot after installing(Reboot after installation)= none (no, that is, there will be no reboot)
More arguments for Reboot after installing
• system(restart into the system, simple reboot)
• bootloader (reboot to fastboot mode)
• recovery (reboot into recovery mode)
• Language(installer language)=english(English)
More arguments for Language
• indo(Indonesian)
• russian (Russian language)
So we have sorted out the modes of operation of all parameters. Now, what does each of them mean.
The values of these parameters
Here the functions of the parameters are described in true mode, for exceptions depending on the mode of operation of the parameter
• DFE method - DFE patching method
• Flash slot - patching the boot partition
• Reboot after installing - reboot after installation
• DISABLE DINAMIC REFRESHRATE - disable dynamic screen formatting, ONLY FOR MIUI
• Language - the language of the installer
• Force reading arguments.txt - dfe-neo will immediately address the arguments in arguments.txt without the possibility of creating a temporary arguments.txt
• Flash DFE - DFE firmware
• Hide not encrypted - The ROM will think that encryption is enabled
• Skip warning - at the end, a guide will be shown on the correct use of dfe after firmware
• Reflash recovery for ota - reinstalling recovery after ota updates, according to the Flash slot parameter mode=
• Reflash current Recovery for Recovery - flash the current recovery, according to the Flash slot parameter mode=
• Wipe DATA - deleting the contents of the /data section without formatting the internal memory (where the Android, Downloads, Music, etc. folders are located) If you sew DFE for the first time, then we still do format data
• Remove PIN - remove password
• Disable AVB - system integrity check is disabled (or whatever you call it, you can set false if you flash magisk)
• Disable QUOTA - (to be honest, I didn't understand what it was, but you can leave it true)
• Flash Magisk - Installing Magisk, according to the Flash slot parameter mode=
And you can also set up your own temporary arguments.txt during installation:
In DFE-NEO, in addition to using arguments.txt in .zip archive, you can still set up your temporary one.
Launch the dfe-neo archive and select Configure Arguments now ( volume + >> volume - )
And we are offered to configure the parameters.
Volume + indicates change
Volume - indicates select
What should I choose DFE method= neo or legacy?
• Neo method - patches the boot partition, we leave neo if the system partitions are read-only, also suitable if the system partitions are editable
• Legacy method - patches fstab.qcom in the /vendor/etc/ section, this method cannot be used if the system partitions are read-only.
Also be careful and read what the script writes at the end of the installation
If you data is encrypted, then after flashing DFE you need to format data
If DFE was installed with Magisk you can upgrade or downgrade the Magisk version later without flashing DFE again
If you uninstall Magisk via uninstall or Magisk app Then the DFE will stop its work! In this case, you will need to flash the DFE again
If DFE was WITHOUT Magisk, it WILL work, but you can also install Magisk later. And also follow the warning 1 and 2
If you install TWRP or another custom recovery, then DFE by analogy with Magisk, will stop working
If you update/Install a new ROM, then DFE will need to be flashed again, by analogy with Magisk
You can install DFE as a magisk module. BUT THIS IS NOT A MODULE, BUT JUST AN INTERFACE FOR INSTALLATION
Demo vido: https://t.me/mfpupdate/22
And also you can flash as a regular zip archive via TWRP, while you do not have to reboot TWRP.
The work consists of the same mechanism as Magisk. If your recovery is located in boot, then after updating / flashing twrp, just like magisk, dfe will be overwritten
After updating/changing ROM you need to reflash dfe again
You can flash dfe without rebooting twrp
No needed for system to be RW for DFE to work
Support erofs
Support flashing from magisk app ( like module magisk )
Later from the computer I will supplement the post. I will add screenshots, etc.
Download link - SourceForge
TG group : @PocoF3DFE
Donate only TG link https://t.me/mfpupdate/47

Great job Alexey. Very useful mod

LeeGarChat said:
Hello everyone, I am writing a script to disable encryption on A/B devices. if you help me with testing on other devices, I will be glad, at the moment it works fine for Poco f3 ( Alioth/Aliothin ). I'm sure it will work just as well on other devices.
And so what can this script:
Hide no encrypted - Forces the system to think that the data is encrypted.
Reflash recovery after OTA - only for devices with recovery into boot_a/_b
Flash current recovery - only for devices with recovery into boot_a/_b
Flash DFE
Flash magisk
The work consists of the same mechanism as Magisk. If u recovery if your recovery is located in boot, then after updating / flashing twrp, just like magisk, dfe will turn off
After update/change ROM u need reflash dfe
You can flashing dfe without reboot twrp
No needed RW system
Support erofs
Support flashing from magisk app ( like module magisk )
Later from the computer I will supplement the post. I will add screenshots, etc.
TG group : @PocoF3DFE
Click to expand...
Click to collapse
Great job bro its perfectly work on my Redmi Note 11 Spes, thanks buddy

sorry for my noob question:does it solove the read-only attribute for erofs partion，my phone is civi （code mona）

wsdyleon said:
sorry for my noob question:does it solove the read-only attribute for erofs partion，my phone is civi （code mona）
Click to expand...
Click to collapse
Yes, if I understand u. Anyway it's working on RW system and RO system. But anyway waiting 0.8.0 beta, because in > 0.7.0 patching only boot partitions, I think need patching recovery partition for device with recovery

LeeGarChat said:
Yes, if I understand u. Anyway it's working on RW system and RO system. But anyway waiting 0.8.0 beta, because in > 0.7.0 patching only boot partitions, I think need patching recovery partition for device with recovery
Click to expand...
Click to collapse
thank u for your answer，but i donnt konw how to flash it.i flash"dfe+magisk+reflash"on my phone in twrp，but bootloop for me

LeeGarChat said:
Yes, if I understand u. Anyway it's working on RW system and RO system. But anyway waiting 0.8.0 beta, because in > 0.7.0 patching only boot partitions, I think need patching recovery partition for device with recovery
Click to expand...
Click to collapse
my english still sucks,after flashing the zip ，the ro system would still ro，just dfe。am i right?

LeeGarChat said:
Download link - SourceForge
Click to expand...
Click to collapse
Great and Congrats!
Can you explain about each zip file made?
Is there a situation for each file?
What does each file do exactly?
Which file should I choose?
----------------------------------------
UPD.
Okay OP. Good work but have consequencies........
Here what I made:
installed magisk;
installed DFE-NEO-0.7.0-BETA+HNE.zip via magisk - modules;
Rebooted device.
Problem: Red message in the screen (look attached SS).
Solved with:
USB Debugging enable;​Permission adb Okay;​cmd command:​
Code:
D:\Program Android\platform-tools>adb shell
Mydevice:/ $ pm list packages
package:com.google.android.networkstack.tethering
package:com.android.fmradio
package:com.android.temperature
[...]
package:com.android.theme.icon_pack.filled.settings
package:com.android.watermark
package:com.android.dreams.basic
[...]
Mydevice:/ $ pm uninstall --user 0 com.android.watermark
Success
127|Mydevice:/ $ exit
D:\Program Android\platform-tools>adb reboot
D:\Program Android\platform-tools>
Reboot device and Red message good bye.
My device fir reference: MTK arm64 -- armv8-a - A11 - TWRP AB - ro.virtual_ab.enabled=true

lopestom said:
Great and Congrats!
Can you explain about each zip file made?
Is there a situation for each file?
What does each file do exactly?
Which file should I choose?
----------------------------------------
UPD.
Okay OP. Good work but have consequencies........
Here what I made:
installed magisk;
installed DFE-NEO-0.7.0-BETA+HNE.zip via magisk - modules;
Rebooted device.
Problem: Red message in the screen (look attached SS).
Solved with:
USB Debugging enable;​Permission adb Okay;​cmd command:​
Code:
D:\Program Android\platform-tools>adb shell
Mydevice:/ $ pm list packages
package:com.google.android.networkstack.tethering
package:com.android.fmradio
package:com.android.temperature
[...]
package:com.android.theme.icon_pack.filled.settings
package:com.android.watermark
package:com.android.dreams.basic
[...]
Mydevice:/ $ pm uninstall --user 0 com.android.watermark
Success
127|Mydevice:/ $ exit
D:\Program Android\platform-tools>adb reboot
D:\Program Android\platform-tools>
Reboot device and Red message good bye.
My device fir reference: MTK arm64 -- armv8-a - A11 - TWRP AB - ro.virtual_ab.enabled=true
Click to expand...
Click to collapse
Thanks for feedback. I'll try fix it. After installing DFE noe, is your device no longer encrypted?

LeeGarChat said:
Thanks for feedback. I'll try fix it. After installing DFE noe, is your device no longer encrypted?
Click to expand...
Click to collapse
I can make backup of Data now with TWRP.
But..........
I need to do more testing regarding the ROM.
I fixed a reset - FORMAT DATA with TWRP to see/test if everything would work fine after that.
Knowing that there would be a possibility it might not work, re-install your zip file and reboot to test again.
So there's a big problem: - WiFi connection doesn't work
- going to settings - Security - Encryption&credentials =====>>> Black Screen .......... stop ............ go back setting automatically
- others??
Do not worry about me. I have experience in getting the device running normally. The device is also not for my daily use.
So I will need time for more testing or you should write for users not to do a factory reset.

lopestom said:
I can make backup of Data now with TWRP.
But..........
I need to do more testing regarding the ROM.
I fixed a reset - FORMAT DATA with TWRP to see/test if everything would work fine after that.
Knowing that there would be a possibility it might not work, re-install your zip file and reboot to test again.
So there's a big problem: - WiFi connection doesn't work
- going to settings - Security - Encryption&credentials =====>>> Black Screen .......... stop ............ go back setting automatically
- others??
Do not worry about me. I have experience in getting the device running normally. The device is also not for my daily use.
So I will need time for more testing or you should write for users not to do a factory reset.
Click to expand...
Click to collapse
Send me download link on you ROM. I'll check structure

LeeGarChat said:
Send me download link on you ROM. I'll check structure
Click to expand...
Click to collapse
UMIDIGI Power 5 4GB_N_V1.0_20220315 - SPFT release
UMIDIGI_POWER5_4GB_N_V1-0_20220315.rar

Great.

lopestom said:
I can make backup of Data now with TWRP.
But..........
I need to do more testing regarding the ROM.
I fixed a reset - FORMAT DATA with TWRP to see/test if everything would work fine after that.
Knowing that there would be a possibility it might not work, re-install your zip file and reboot to test again.
So there's a big problem: - WiFi connection doesn't work
- going to settings - Security - Encryption&credentials =====>>> Black Screen .......... stop ............ go back setting automatically
- others??
Do not worry about me. I have experience in getting the device running normally. The device is also not for my daily use.
So I will need time for more testing or you should write for users not to do a factory reset.
Click to expand...
Click to collapse
Test 0.9.0 version please

LeeGarChat said:
Test 0.9.0 version please
Click to expand...
Click to collapse
Thanks man. I appreciate what you're doing.
I already tried with this and newer version DFE-NEO-0.10.1-BETA.zip having the same situation as before.
Unfortunately there is something that blocks the wifi working after installing DFE-NEO-x.xx.x-BETA.zip. Regarding this, I tested restoring the NVRAM, NVCFG and NVDATA files and the wifi started to work, however the part that DFE-NEO does is lost.
Is there something that DFE-NEO does with NvRam, NvCfg and NvData partitions?? Is it something that is a prerequisite for the ROM to work encrypted and consequently to work or not work the wifi?
I couldn't try all possibilities to investigate and test as I have been sick for a few days.

lopestom said:
Thanks man. I appreciate what you're doing.
I already tried with this and newer version DFE-NEO-0.10.1-BETA.zip having the same situation as before.
Unfortunately there is something that blocks the wifi working after installing DFE-NEO-x.xx.x-BETA.zip. Regarding this, I tested restoring the NVRAM, NVCFG and NVDATA files and the wifi started to work, however the part that DFE-NEO does is lost.
Is there something that DFE-NEO does with NvRam, NvCfg and NvData partitions?? Is it something that is a prerequisite for the ROM to work encrypted and consequently to work or not work the wifi?
I couldn't try all possibilities to investigate and test as I have been sick for a few days.
Click to expand...
Click to collapse
Some ROMs may not work correctly with DFE, due to the fact that the ROMs are designed to work with an encrypted data partition, or there are any protections. also, on some ROMs, the data split must be formatted according to the associated with certain keys -C and -O -g. DFE-NEO does not modify any partitions except boot, just like magisk. DFE-NEO works thanks to magisk-init, which allows you to run custom scripts during ROM startup. the script that is executed during system startup, makes a copy of fstab, deletes the encryption keys and mounts it in place of the original fstab, there is no full-fledged verification of the system. all work is based on magisk logic

Awesome job LeeGarChat, much appreciated by all users I have quoted your post link in other threads too so all can see the magic .
My device is Shamshung Galeksi M21 2021 (SM-M215G) But when I flashed from TWRP it showed some red error : 577 something like that, then when I flashed from Majisk it showed error code 3 : DFE-NEO only for virtual_ab devices
Treble Check shows my device is treble compliant having AB partition and TWRP displays following partitions: System, Vendor, Product, Odm, Cache, Data, EFS, Metadata, Sec EFS, Micro SD Card, USB OTG.
In my Shaomi Readmi Note 10 (mohito) TWRP displays Slot A & Slot B under Advanced Tab and ROMs get directly flashed to Inactive Slot B, also everytime I try flash new custom ROM I have to first flash MyUi Factory ROM and also System partition doesnt show in TWRP Mount section.
My question is what is the difference between Shamshung Galeksi M21 Android 11 out-of-box & Shaomi Readmi Note 10 Mohito ? why TWRP shows System partition mount in Shamshung and not in shaomi though both are A/B devices?
Pls help.

LeeGarChat said:
Some ROMs may not work correctly with DFE, due to the fact that the ROMs are designed to work with an encrypted data partition, or there are any protections. also, on some ROMs, the data split must be formatted according to the associated with certain keys -C and -O -g. DFE-NEO does not modify any partitions except boot, just like magisk. DFE-NEO works thanks to magisk-init, which allows you to run custom scripts during ROM startup. the script that is executed during system startup, makes a copy of fstab, deletes the encryption keys and mounts it in place of the original fstab, there is no full-fledged verification of the system. all work is based on magisk logic
Click to expand...
Click to collapse
Great News!
@2mkl and me solved the Wi-Fi issue......... But I not write here about.
Thanks again

lopestom said:
Great News!
@2mkl and me solved the Wi-Fi issue......... But I not write here about.
Thanks again
Click to expand...
Click to collapse
can you tell us in PM how you fixed the problems you wrote about earlier

History of updates and news
June 16
Update DFE-NEO 0.10.0 beta
- Added Feature, choose wether you want to flash DFE legacy / neo ( for legacy need RW system and not working with erofs)
july 14
Update dfe-neo beta 0.11.0
- Add magisk 25.1
- Add volume key selector
- Add remove lockscreen-pin select for key selector
july 20
Update dfe-neo beta 0.12.0
- Add new arguments:
- Wipe data
- Reboot after
july 22
DFE-NEO-0.12.4-BETA update
- Add additional settings (optional) like wipe data, reboot after
- Add disable dynamic refrash rate display ( only miui and works with dfe-neo method )
july 23
DFE-NEO-0.13.0-BETA update
- Add new arguments into arguments.txt, now u can change it without volume key
- Add new options "remove avb" " remove quota" ( default removed )
- The code has been slightly rewritten
- Update somthing patches for safety net fix based on later version 2.3.1 https://github.com/kdrag0n/safetynet-fix/releases/tag/v2.3.1
july 24
DFE-NEO-0.13.3-BETA update
- Minor fix
- Cleaning ui print
- Added calculation of script running time
july 25
I show by my example how to install a ROM in conjunction with DFE-NEO, as well as additional zips
Download DFE-NEO LINK ( Alway later version )
Thread XDA LINK
Please subscribe to the updates and news channel LINK
Thanks
july 28
DFE-NEO-0.14.0-BETA update
- Add language select ( it is currently configured only in the file arguments.txt )
Languages:
• Russian
• English
• Indo
• you can add your own language
- Fix ro.dfe.neo.state
- Add force reading arguments.txt
july 30
DFE-NEO-0.14.1-BETA update
- Reworked my_print function to work correctly in other languages. previously, it worked fine only with English
- Updated the Russian language. fixed typos
july 30
DFE-NEO-0.15.0-BETA update
- Add support A-Only devices
Languages v003:
- There was a bug with a large number of characters ****