Huawei P9 [ROM][Android 7.0][EMUI 5.0.1][European Firmware b398]*MagicRainbow* v4 - Huawei P9 ROMs, Kernels, Recoveries, & Other Devel

Huawei P9 Custom Rom - for EVA-L09 - EVA-L19 - EVA-L29 ​
{
"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"
}
*MagicRainbow*​
Version 4
as usual in two Editions:
Magisk Edition and SuperSU Edition​
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-v4-by-tecalote.859343.html
I'm happy to present you my fourth version of MagicRainbow ROM for P9-EVA
Requirements:
P9 EVA-L09 - EVA-L19 - EVA-L29 - without mobile provider branding (like Vodafone)
unlocked Bootloader
minimum official Huawei background firmware b394
TWRP 3.1.1-1 by oldDroid - extended Version: https://www.androidfilehost.com/?fid=673791459329067086
Note: In Settings of TWRP on the last Tab disable "keep vendor mounted" but enable "Exclude OEM-Path from data wipe"
Phone must be encrypted because this ROM is based on EMUI (TWRP has encryption support) - if your data partition is decrypted, ROM cannot be installed properly because the script mount your data as encrypted. If you come from EMUI based ROM or official Firmware data is encrypted by default
Developer Options enabled, in these settings enabled OEM-Unlock and: A) ADB Debugging in charging mode - B) USB Debugging (in this order, or it will not stay enabled)
Changelog:
European Firmware b398 based for EVA-L09 - with patch.zips for L19-c432 – L19-c185 – L19-c636 – L29-c636 – L09-c636 – L09-c185 Note: EVA-L09 need no patch, but the other models/cust need this patch immediately after flashing the Rom without Reboot to system - but with reboot of TWRP (for fixing the mountpoints after ROM installing)
Magisk-Edition: Magisk v16 - preinstalled modules (required):SELinux Permissive-Script 1.2 - Busybox 1.28.1 by osmOsis - Huawei Property Fix 1.3 - KernelAudiutorReborn allows to emulate init.d
Safetynet-Workaround look in the description for Magisk
SuperSU-Edition: SuperSU 2.82 SR5 - init.d Support - modified launch_daemonsu.sh for SELinux Permissive - BusyBox 1.28.1 by osmOsis
"Advanced Settings" - made personally by KangV well known as "K-Settings" - ported in MRv4 from chinese Firmware b399 - optional flashable zip separate for SuperSU-Editon and for Magisk-Edition - please support this project in credits section. These settings allow you the maximum of customization. In SuperSU-Edition you can enable in Advanced-Settings /more settings/Xposed Framework last v89 by rovo89 (and of course, a lot of more...)
Note: If you enable Xposed Framework - after reboot (which takes bit longer than usual) you must reboot your phone once again (only one times) and Xposed will be and stay enabled (you can disable Xposed with same settings)
In Magisk-Edition this setting is not active (cause it breaks safetynet)
To disable chinese letters after flashing this mod in statusbar - open Advanced Settings /Notification settings and disable "Show statusbar Lunar"
Known BUG: Dont use "Hide navigation bar" - it works only on chinese Brands.
In Europe you should not use: "Disable Google Services"
Note: Do not change DPI in developer options (this can brick your device) if you use KangV Settings - change DPI only with KangV Advanced Settings!
Note: Do not flash KangV-Settings before first reboot to System. You can do it after first setup, but dont change the EMUI Launcher to alternative Launcher (example: Nova Launcher) before you have flashed KangV-Settings (if you decide to use KangV Mod)
With KangV Advanced Settings PMPlusApp will be installed (this App dont work on Stock Roms) With PMPlus you can enable in Phonemanager (on second page) the feature: Auto-Launch It is a powerful Autostart-Manager (which can help you also to save battery) that gives you full auto launch control over all Apps - but you must manually allow them to start automatically or not, on boot or in the background.
Note: If you enable this mod - you must enable important Apps into auto launch, example: Magisk Manager /SuperSU must be enabled in "Auto Launch" - and additional in Secondary launch management!, if not you cannot manage Root-Requests! WhatsApp, Viber, Telegram - all these apps you must enable in "Auto Launch" or they do not work properly. Some Apps like Amazon needs also an extra setting in "Auto Launch, called "App secondary launch" (this will only be displayed if you use apps that need it)
To enable this mod open PMPlus, use install button, soon it is succesful installed - close PMPlus and uninstall this App. After open Phone Manager and on second page you will find "Auto Launch"
Note: This mod is not uninstall able, once enabled!
Both Edition of MRv4-ROM have modified services.jar - the maximum of acces to external SD is enabled (TitaniumBackup dont neeed "DocumentProvider" but can use Filesystem storage - Ext. SD Card)
App-Twin: more apps than usual are enabled for cloning (WhatsApp, Telegram, Skype and a lot of more...)
Only the main Google (Core) Apps are installed in system, all others are installed so that they can be uninstalled via Settings /Apps. Same with added Apps - all of them uninstall able via Settings /Apps. If you need more Google Apps you can install them with Playstore (dont flash any GApps)
Added: Facebook Lite and Skype Lite (both can work in 2G/3G and 4G and saves a lot of battery
VIPER4AndroidFX and Dolby/Atmos with preinstalled Driver
Some beautiful Designs included: IOS11 - Sky Blue - Galaxya - XDA Exklusive - AegeanSea - Blue Pixel - Mate 10 (Mountains)
Security-Patch-Level: 01.02.2018
Installation-Guide:
1) Your official Huawei Background-Firmware must be updated to minimal b394 (which is available for all models/cust) - for updating use please my Post from MRv3 #3: https://forum.xda-developers.com/showpost.php?p=74913874&postcount=3
Note: Your Fingerprint HWEVA/xxx/xxx:user/release-keys (which you can see with apps like "My Device") on MagicRainbow v3 will show you ...b394 - but that does not mean your background official Firmware is b394 ! You see this information, because MagicRainbow v3 is based on b394 same as MagicRainbow v4 is based on b398.
But important is - which build was your last official Firmware. For example: If you had flashed MRv3 over MRv2 (which was based on b386) your background Firmware is b386 ! And this Firmware is too old and cannot be compatible with the Custom ROM MagicRainbow v4 which is based on b398. Custom ROM and Background Firmware should be similar the same build. Personally, I always update first to the last available firmware for my device before flashing my own Custom Rom
But if you have updated your Firmware to b394 - before you have installed MagicRainbow v3 - or if you come right now from Stock Firmware b394, b395, b397... then there is no need to update the firmware now and you can flash the MagicRainbow v4 directly - but with Unroot (if your Phone is rooted) AND with the neccesary wipes!
2) Before update your Firmware (or for clean flash) you must backup your apps and data (you can use Huawei Backup and/or TitaniumBackup - in every case make backup only from user-apps and not from system apps/components)
Backup also the important folders from your internal storage (WhatsApp folder, DCIM and so on...) - and copy them back to internal storage after updating the Firmware...
For Chat/Net-Call Apps like Viber, WhatsApp use inside Chat-Backup on GoogleDrive. If you reinstall these apps and registrate them new with your phone number, backup will be found automatically and you are able to restore chat-history.
3) For the next steps I now assume that your firmware is up to date Download now all Files you need - ROM.zip - patch.zip (if you need it for different cust/model than EVA-L09c432) - KangV-Settings.zip and copy it to your external SD.
4) Delete on your Phone your Fingerprint(s) and PIN(s)
5) If your device has Root - flash Unroot with TWRP - for Magisk: http://tiny.cc/latestuninstaller - for SuperSU flash UPDATE-unSU-signed.zip from this site: https://forum.xda-developers.com/showpost.php?p=63615067
6) Go back to main menu in TWRP and use WIPE /Advanced Wipe - for clean flash wipe: Dalvik/ART-Cache, Cache, data, system, vendor - for dirty flash exclude: data from wipe
7) Flash ROM - next step (8) is only important if you have another model/cust than EVA-L09c432
8) If you have another (like L19c432, L29c636.....) - you must REBOOT TWRP now (TWRP /Reboot /RECOVERY) - dont reboot to system! After TWRP is rebooted, go to install and flash the RIGHT patch.zip which match your model/cust. (EVA-L09c432 dont need this step.) In every case: no need to wipe Dalvik/Cache after the flashings
9) Reboot phone (first start needs about 10 minutes) - dont flash KangV Settings before first Reboot to system
10) Setup your Phone - disable "send systemdata to Google" (save battery)
11) Disable “automatic system updates” in developer options (save battery)
Safetynet-Workaround in Magisk-Edition:
1) If you made clean flash - during first setup at the point you enable your Google Account - disable "sending system-data"
2) After first setup safetynet check with Magisk Manager will show you - ctsProfile and basicIntegrity=false - so dont check now :laugh:
3) Enable Developer Options and in these settings enable A) ADB Debugging in charging mode - B) USB Debugging (in this order, or it will not stay enabled)
4) Reboot your Phone - after reboot, cts-profile and basicIntegrity=true
- Now we go to make Playstore certified:
5) Open Playstore and disable Play Protect
6) SET YOUR PHONE INTO FLIGHT-MODE!
7) Open native settings /apps and (right down) more: Show system processes - click on every following app and delete in storage-section: cache and data (some of them show you: manage space - in this case use "Delete all data"):
Google App
Google Play services for Instant Apps
Google Playstore
Google Play-Services
Google Services Framework
Huawei ID or Huawei Mobile Services (which is the same)
8) Reboot your Phone
9) If you get a message after Restart "Your backup-account is not set yet" - DONT enable it now!
10) DISABLE FLIGHT-MODE NOW - and wait until you have full network-access (open Browser for testing)
11) Now you can enable your backup-account (message is shown in statusbar)
12) Open Playstore - If you are facing a problem when you open Playstore (showing just a blank site) - open Settings /Apps /Playstore /storage - but this time wipe only Cache inside, after Reboot your Phone. Soon P9 is restartet, Playstore should work proberly and it should be certified
13) If you are using Apps (like banking apps and so on) which requires safetynet - enable them in Magisk Hide - BEFORE you start these apps first time - after reboot phone and then you can start these apps first time.
Note: If you did all these steps and ctsProfile /or basicIntegrity is false (red) - one User of this Rom (L19c432) found a trick which solved his issue: https://forum.xda-developers.com/showpost.php?p=75796309&postcount=595
14) If you use in Phonemanager "Auto-Lauch" (enabled with PMPlus - see description KangV Advanced settings) - you must enable Magisk-Manager in Auto-Launch and in Secondary launch management!
15) You can update to newest Magisk 16.1 using following method: https://forum.xda-developers.com/showpost.php?p=75845280&postcount=87
Download ROM:
ROM - MagicRainbow-4_magisk.zip: https://www.androidfilehost.com/?fid=746010030569959046
MD5: c0856ddabf79312376ec5f90e52087ab
KangV-Settings_magisk.zip: https://www.androidfilehost.com/?fid=746010030569959103
MD5: 47ec7117a403af004e43c42cecde2b36
ROM - MagicRainbow-4_supersu.zip: https://www.androidfilehost.com/?fid=746010030569959091
MD5: 0ba05c096f4caa09afbe373d2986801d
KangV-Settings_supersu.zip: https://www.androidfilehost.com/?fid=673956719939824958
MD5: 4e197148bd00f4bb14ae7253d3f00a91
Download Patches (EVA-L09c432 dont need this!)
MD5-checksum is also shown on Android Filehost during download, please check your downloaded files if they match with this checksum.
Note: A very required point is - If you have another model/cust than EVA-L09-C432 and you must flash Patch.zip do it with following steps:
1) After flashing Rom - go back to main menu of TWRP, go to Restart /but NOT system - Restart RECOVERY
2) Then flash patch.zip and after reboot Phone first time. If you don't restart Recovery between, patch will not installed properly and some apps may not work then.
Information: I have decided to make new patch.zips because there are problems with safetynet (in the Magisk Edition). Once these are done, I will post the new links here.
L19-c432-patch.zip: https://www.androidfilehost.com/?fid=890129502657588204
L19-c185-patch.zip: https://www.androidfilehost.com/?fid=746010030569959118
L19-c636-patch.zip: https://www.androidfilehost.com/?fid=890129502657588206
L29-c636-patch.zip: https://www.androidfilehost.com/?fid=673956719939824987
L09-c636-patch.zip: https://www.androidfilehost.com/?fid=890129502657588201
L09-c185-patch.zip: https://www.androidfilehost.com/?fid=818070582850497993
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
​
XDA:DevDB Information
MagicRainbow, ROM for the Huawei P9
Contributors
Tecalote
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 4.x
ROM Firmware Required: official Firmware b394 up to b398
Based On: EMUI (encrypted)
Version Information
Status: Stable
Current Stable Version: MagicRainbow v4.0
Stable Release Date: 2018-03-05
Created 2018-03-06
Last Updated 2018-03-14

Pictures and additions - tomorrow

Credits:
All Credits go to @Atarii for his special EMUI-Recovery for P9 EVA (L09 / L19 /L29). Users had reported, it is working also on P9+ VIE (L09 / L29) - but it will not work on other devices. Following method is based on this modified EMUI-Recovery.
Thanks to @zgfg He inspired me to do this post.
This Guide show you how to go back from Custom ROM to original Huawei EMUI Firmware. You can use this method also for updating/downgrade your Firmware - but only on Android 7. Also users of Lineage OS or RROS can use this method to return to Stock Firmware.
It can not be used for downgrade to Android 6 /or upgrade to Android 7 (this can brick your device) and it will not debrand your device!
Requirements: Unlocked Bootloader, installed TWRP, inserted SD Card (ExFat filesystem format recommended) -
Enable Developer Options and inside enable first ADB Debugging in charging mode and then USB Debugging - OEM Unlock must also be enabled!
Do a backup as usual if you change your system to another (Backup your Apps /data and also data from internal storage!)
Follow the steps on the instructions!
Not required: Root
Required: I would recommend to UNROOT your device before flashing the Firmware-Update and you should delete your Fingerprint /PIN /Password
How it works:
1) First you need one of those zip files (depended to your device):
Download HWOTA.zip for P9 and P9+ EVA/VIE-L09: [url]https://www.androidfilehost.com/?fid=962187416754474573[/URL]
md5: 98e141ca6d6ccc262d22288490a5eeea
Download HWOTA.zip for P9 EVA-L19: [url]https://www.androidfilehost.com/?fid=962187416754474574[/URL]
md5: e90b5b4d14d9808bb0626dbd77bb452f
Download HWOTA.zip for P9 and P9+ EVA/VIE-L29: [url]https://www.androidfilehost.com/?fid=673956719939834215[/URL]
md5: 5fad3c1971c45ad7b9a72ab2e8cc9404
2) Unzipp the HWOTA.zip on your PC - HWOTA folder contains 2 Files:
L(xx)_Recovery.img
(dependend to your device for example: L09_Recovery.img)
HWOTAUpdateSCRIPT.zip​
3) Do not use internal Storage of your Phone! Create a folder in the main directory of your EXTERNAL SD with the name: HWOTA
4) Copy L(xx)_Recovery.img and HWOTAUpdateSCRIPT.zip into the HWOTA folder on your external SD.
5) Search for the correct FullOTA-MF Firmware for your Device /Cust and download the 3 firmware zip files. See Guide below...
6) Copy the 3 Firmware zip files into the HWOTA folder on your external SD:
update.zip
update_data_full_public.zip​(The third zip file has different names dependend to your device: update_full_EVA-L09_hw_eu.zip / update_full_EVA-L19_hw_eu.zip / update_full_EVA-L19_hw_meafnaf.zip / update_full_EVA-L29_hw_spcseas.zip...) - Rename only this third zip file to the general name:
update_full_hw.zip​
6) Your HWOTA folder on the external SD is now prepared!
7) Disconnect USB cable from your P9
8) Boot to TWRP and from HWOTA folder flash only: HWOTAUpdateSCRIPT.zip
9) The phone reboots to EMUI recovery and automatically installs the firmware. After 57% it takes a while, do not worry. As soon as the update has been performed 100%, the system will be restarted
10) Open settings /advanced settings/ Backup and restore and do a data Factoryreset with wipe of internal Storage
11) Once the factory reset is 100% in EMUI recovery, the phone restarts. At this moment, press the VOL + key until the EMUI Recovery boots again
12) Do Wipe Cache Partition and Reboot to System
13) Look into settings /about phone and enjoy - and if you want to stay on original firmware, now everything is done.
14) On some Firmwares the Bootloader will get closed - in case you want to open Bootloader again, enable Developer options and open them. First enable "Allow ADB Debugging in charge only mode" and then "USB Debugging" (in this order USB Debugging stays enabled) and very important: Enable "OEM Unlock". Enter your Unlock Code with ADB in Fastboot Mode. Let the phone doing the low-lewel-wipe and do not disconnect the Phone from USB, the wipe should be done with 100% (important)- if not: open settings /Advanced settings /Backup & reset /Factory data reset with enabled "erase internal storage"
15) To flash TWRP, enable Developer Options again / OEM Unlock is enabled (but greyed out) /enable ADB Debugging and USB Debugging and then flash TWRP in Fastboot Mode.
16) Enjoy
How to find the Firmware:
A) You can not use FullOTA-MF-PV or OTA-MF - you can use only FullOTA-MF firmware for this method.
The firmware for your device consists only of three zip files. But the differnt possibilities for downloading the firmware can show you four / sometimes five zip files if the Build is made for two or three models. For example for L09 /L19 and L29 or for L09 and L19.
You need in every case update.zip and update_data_full_public.zip and third zip must match your device - and you have to rename it:
Examples:
If you own L09-c432 you choose update_full_EVA-L09_hw_eu.zip - and rename this update_full_hw.zip
If you own L19-c432 you choose update_full_EVA-L19_hw_eu.zip - and rename this: update_full_hw.zip
If you own L19-c185 you choose update_full_EVA-L19_hw_meafnaf.zip - and rename this: update_full_hw.zip
If you own L19-c636 you choose update_full_EVA-L29_hw_spcseas.zip- and rename this: update_full_hw.zip
B) For searching your firmware you enter always model name and cust version from your device - for example:
EVA-L09C432 or EVA-L19C432 or EVA-L19C185 or EVA-L29C636 ....
Note: You can not install L19c636 Firmware if you own a L09c432 device ....
C) Which Firmware should I use?
For the users of MagicRainbow v4 I recommend to use the firmware that was installed before MRv4. Same for the users of MagicRainbow v3.
From there you can update if necessary.
Note: There can not be any impossible "version jumps". For example, it is not possible to update from b386 directly to b398. Firmwares depend on prerequisite versions. For example with EVA-L09c432 you can switch from b386 to b394 and then: b397 -> b398 -> b399. It is recommended to use approved versions, otherwise Playstore is not certified. For example, EVA-L09c432 currently has the rollout b399 - that means, the firmware is approved.
If you do not succeed in updating with this method, then you have done something wrong, or the download of the zip files is buggy, or the version did not fit. Nothing bad can happen if an update fails, but TWRP must be reinstalled. Then you can try it with a different version that fits your firmware. But you can not use firmware that does not match your model /cust - this can brick your device!
D) There are three ways to download the firmware and it is up to you, which you use of it
1. Firmware Finder - Android App on Playstore:[url]https://play.google.com/store/apps/details?id=com.teammt.gmanrainy.huaweifirmwarefinder&hl=us[/URL]
2. Direct Link: [url]http://pro-teammt.ru/firmware-database/?firmware_model=EVA-L09C432&firmware_page=0[/URL]
3. Firmware Finder for PC: [url]https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146[/URL]

Instructions for v4 have that new section Playstore Certified but Magisk Hide section (from v3 Instructions) are omitted - Magisk Hide is no more needed?
Maybe you can also copy/paste the Statusbar Lunar note for K-Settings (if Chinese letters still persist).
In case of installing from L09 c432 b394 -> MR v3, upon going back to stock b394 (by HWOTA), is it necessary to update in two steps b397 -> b398 or it can be flashed only one HWOTA for L09 c432 b398.

zgfg said:
Instructions for v4 have that new section Playstore Certified but Magisk Hide section (from v3 Instructions) are omitted - Magisk Hide is no more needed?
Maybe you can also copy/paste the Statusbar Lunar note for K-Settings (if Chinese letters still persist).
In case of installing from L09 c432 b394 -> MR v3, upon going back to stock b394 (by HWOTA), is it necessary to update in two steps b397 -> b398 or it can be flashed only one HWOTA for L09 c432 b398.
Click to expand...
Click to collapse
Magisk Hide for some required components is preset!
You just enable Apps which requires safetynet (Banking Apps and so on) in Magisk Hide and reboot phone before you start these Apps first time.
Direct update from b394 to b398 didn't work for me and I got problems to update after trying the short way.
L09 c432 b394 -> MR v3 - going back to stock b394 (by HWOTA), then b397 then -> b398!
Statusbar Lunar note for K-Settings is included in description of KangV Settings

Hi,
What is difference between v3 and v4?

mnv12345 said:
Hi,
What is difference between v3 and v4?
Click to expand...
Click to collapse
I didn't install yet but you can check post #1 ChangeLog.
E.g. based on b398 (for c432) with Feb Sec patch, latest Magisk components and so

zgfg said:
I didn't install yet but you can check post #1 ChangeLog.
E.g. based on b394 (for c432) with Feb Sec patch, latest Magisk components and so
Click to expand...
Click to collapse
Where did you read based on b394? - I have written there and it is based in b398.
February Sec Patch is also written there..

Tecalote said:
Where did you read based on b394? - I have written there and it is based in b398.
February Sec Patch is also written there..
Click to expand...
Click to collapse
Of course b398, lapsus

mnv12345 said:
Hi,
What is difference between v3 and v4?
Click to expand...
Click to collapse
It contains the Features of b395 - 3D Camera Plugin
and newest Security Patch Level from b398 (February) - it has some optimations for Battery Life - Magisk Edition has newest Magisk v16 - SuperSU Edition has newest Xposed Framework (to enable from KangV Advanced Settings, sone more Apps added (but uninstall able from settings /apps)
Read Post #1 please

I'll hope you upload all files to change to v4.
My stock Rom is c185B387

Tecalote said:
Huawei P9 Custom Rom​Safetynet-Workaround in Magisk-Edition:
1) If you made clean flash - during first setup at the point you enable your Google Account - disable "sending system-data"
2) After first setup safetynet check with Magisk Manager will show you - ctsProfile and basicIntegrity=false - so dont check now :laugh:
3) Enable Developer Options and in these settings enable A) ADB Debugging in charging mode - B) USB Debugging (in this order, or it will not stay enabled)
4) Reboot your Phone - after reboot, cts-profile and basicIntegrity=true
- Now we go to make Playstore certified:
5) SET YOUR PHONE INTO FLIGHT-MODE!
6) Open native settings /apps and (right down) more: Show system processes - click on every following app and delete in storage-section: cache and data (some of them show you: manage space - in this case also DELETE ALL DATA):
Google App
Google Play services for Instant Apps
Google Playstore
Google Play-Services
Google Services Framework
Huawei ID or Huawei Mobile Services (which is the same)
7) Reboot your Phone
- if you get a message "Your backup-account is not set yet" - DONT enable it now!
8) DISABLE FLIGHT-MODE NOW - and wait until you have full network-access (open Browser for testing)
9) Now you can enable your backup-account (message is shown in statusbar)
10) Open Playstore - it is certified
11) If you are using Apps (like banking apps and so on) which requires safetynet - enable them in Magisk Hide - BEFORE you start these apps first time - after reboot phone and then you can start these apps first time.
Click to expand...
Click to collapse
I made it and Play Store stoped working. It searching updates for years and nothing else happen.
And second case. After clean flash via TWRP I lost TWRP and had to reflash it again. Is it normal?

hapnik said:
I made it and Play Store stoped working. It searching updates for years and nothing else happen.
And second case. After clean flash via TWRP I lost TWRP and had to reflash it again. Is it normal?
Click to expand...
Click to collapse
Playstore must just create new cache. Just open settings /apps and wipe in storage only cache at this point.
Reboot phone and it should work again.
Normally you loose not TWRP with clean flash. I never heard this.
But if you wipe internal storage included in the wipes you loose normally settings of TWRP.
That's why I do a wipe if internal storage with an extra step and reboot Recovery between the next wipes.

jonathanhenry81 said:
I'll hope you upload all files to change to v4.
My stock Rom is c185B387
Click to expand...
Click to collapse
I can upload HWOTA.zips for newest Firmware c185b387 tonight (but late)

Tecalote said:
I can upload HWOTA.zips for newest Firmware c185b387 tonight (but late)
Click to expand...
Click to collapse
Just take time you need

jonathanhenry81 said:
Just take time you need
Click to expand...
Click to collapse
I answered here: https://forum.xda-developers.com/showpost.php?p=75780638&postcount=557
You said your model is L19c185 and last official Firmware was b387.
In this case you must first update to b394 - after to b396 (you can't go directly to b396, it would fail)
The downloads and the Guide how to do you will find here:
https://forum.xda-developers.com/showpost.php?p=74913874&postcount=3
Be careful to download the right two zips.
I wish you success
Note: b396 is latest official Firmware for your device.
After it is installed (with factory reset and wipe of internal storage from settings) you can flash MRv4 (read Guide before)

Tecalote said:
I answered here: https://forum.xda-developers.com/showpost.php?p=75780638&postcount=557
You said your model is L19c185 and last official Firmware was b387.
In this case you must first update to b394 - after to b396 (you can't go directly to b396, it would fail)
The downloads and the Guide how to do you will find here:
https://forum.xda-developers.com/showpost.php?p=74913874&postcount=3
Be careful to download the right two zips.
I wish you success
Note: b396 is latest official Firmware for your device.
After it is installed (with factory reset and wipe of internal storage from settings) you can flash MRv4 (read Guide before)
Click to expand...
Click to collapse
I read the guide https://forum.xda-developers.com/showpost.php?p=74913874&postcount=3
and I'm not clear, I have MR V3 at this time. but before that update to stock B387 .. now to change MR v4 first I have to update and should I start with B387 or B394 ???
as the post says; first B387.

jonathanhenry81 said:
I read the guide https://forum.xda-developers.com/showpost.php?p=74913874&postcount=3
and I'm not clear, I have MR V3 at this time. but before that update to stock B387 .. now to change MR v4 first I have to update and should I start with B387 or B394 ???
as the post says; first B387.
Click to expand...
Click to collapse
I think b394 should be okay.
On L09 it is also working to update from b386 to b394

Hi a small question, once I have returned from MRv3 to stock. I am assuming that TWRP will need to be re-flashed! Is this correct?
DH

bubba_66 said:
Hi a small question, once I have returned from MRv3 to stock. I am assuming that TWRP will need to be re-flashed! Is this correct?
DH
Click to expand...
Click to collapse
Yes, that's correct - because the Update flash Stock Recovery (without no update possible)
After Update reflash of TWRP is necessary.
But sometimes Bootloader get closed and in this case unlock Bootloader is required..

Related

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

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

[ROOT][Android 7.0][EMUI 5.0]SuperSU 2.82 for EMUI 5

{
"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"
}
SuperSU 2.82 for EMUI 5
Note: SuperSU 2.82 working on EMUI 5 but may not on EMUI 5.0.1 or 5.1 ​
Here is updated SuperSU-2.82-SR5 for EMUI5.0.1
This will work (tested) on EVA (Huawei P9) - based on original SuperSU SR5 by @Chainfire
Download: https://www.androidfilehost.com/?fid=673956719939815322
MD5: b168a88bc815d3fac521ace97402a949
Older Versions here: (Thread will get general update soon)
SuperSU-2.82-EMUI5
Changelog: First 4 Versions based on original Chaifires SuperSU 2.82 code with mounting vendor and search for boot_a. These versions are without additional modification by phh superuser files/scripts
The second 3 Versions (a/b) - 09.06.2017 01:17- are mixed with phh superuser and original Chaifires SuperSU Code (same as 2.79 for EMUI): Download-Links below - for Firmwares before b38x and without loop support
Current Status: STABLE
NOTE: If your device has no Root - just flash it with the related TWRP for your device! - But if your device is rooted with previous Versions of SuperSU for EMUI, dont flash it over existing Root but make the steps written below "How do Root"
4 Versions based on original Chainfire SuperSU 2.82 code - 07.06.2017
Succesful tested on P9 b383, b386 and Mate 9, also working on Honor 6x BLN-B360 - but may work also on other devices from Firmwares b38x up and new Nougat Firmwares for Devices, which had Marshmallow until short time ago.
It will probably not work on other Firmwares before b38x (for these devices are the modified versions with mixed code from SuperSU and phh Superuser)
1) SuperSU-v2.82-EMUI5-SELEnforcing.zip
Just added init.d script, but let's SELinux as it is.
Download: https://www.androidfilehost.com/?fid=673368273298961353
MD5: 18529db8978a39212db335ad006760cf
2) SuperSU-v2.82-EMUI5-SELPermissive.zip
Added init.d script and set SELinux permanently to permissive (required for Viper4Android)
Download: https://www.androidfilehost.com/?fid=817550096634775861
MD5: 57a081ba3ba03691c4ffaf9ab141a44e
3) SuperSU-v2.82-EMUI5-KangV-Roms.zip
Added init.d script, SELinux Permissive, Script for K-Settings
Download: https://www.androidfilehost.com/?fid=817550096634775860
MD5: 5e68f7b1175f7b51d64802f7416a04f5
4) SuperSU-v2.82-without-additive.zip - try out, if none of the three above works (its without additional features, just Root)
Download: https://www.androidfilehost.com/?fid=961840155545571636
MD5: bfa6f458949f6deb056044b0337ef31a
3 Versions (a/b) mixed with original Chainfire SuperSU 2.82 code and pph superuser code - 09.06.2017
For devices which has no Loop Support yet, but working also on devices, which can succesful use Version 1, 2, 3 and 4.
Kirin 960 based Devices must use Version 6 a/b and 7
Following versions are not compatible with AOSPA based Roms.
5. Version comes in 2 editions (5a and 5b) - should work with devices which have fully working TWRPs - like P9
Version 5/a - Name: SuperSUv2.82-EMUI5-dm-verity-Enforcing.zip
DOWNLOAD UPDATED VERSION: https://www.androidfilehost.com/?fid=961840155545572192
MD5: 0da8bcbf0eb164c7512ae083012b45eb
About:
dm-verity and dm-crypt enabled
init.d Support
SELinux Enforcing
Version 5/b - Name: SuperSUv2.82-EMUI5-dm-verity-Permissive.zip
DOWNLOAD UPDATED VERSION: https://www.androidfilehost.com/?fid=817550096634776377
MD5: 14a0ac7fd3a725ee326e9944399a916e
About:
dm-verity and dm-crypt enabled
init.d Support
permanent SELinux Permissive
Version 5 (a/b) is working (tested) on:
Huawei P9
Huawei P9 Lite
Huawei Mate 8
Huawei Mate 9
Honor 8
Not working:
Huawei Honor 8 FRD-L09C432B380
Huawei P10 and P10 plus - must have noverity version
6. Version comes in 2 editions - for Kirin 960 based Devices like P10 and P10+ and should work with other devices which have NOT properly working TWRPs
Version 6/a - Name: SuperSUv2.82-EMUI5-noverity-Enforcing.zip
DOWNLOAD UPDATED VERSION: https://www.androidfilehost.com/?fid=889764386195906385
MD5: a37380d6f1659f78bbd341954ed804b2
About:
dm-verity DISABLED
init.d Support
SELinux Enforcing
Version 6/b - Name: SuperSUv2.82-EMUI5-noverity-Permissive.zip
DOWNLOAD UPDATED VERSION: https://www.androidfilehost.com/?fid=889764386195906386
MD5: 99f06e5fe34b93409d558fc119d15e59
About:
dm-verity DISABLED
init.d Support
permanent SELinux Permissive
Version 6 (a/b) is working (tested) on:
Huawei P10+
Huawei P10
Huawei Mate 9
Huawei P8 Lite 2017
Huawei Honor 8 FRD-L09C432B386
7. Version comes in 2 editions - special for KangV-ROMs on Kirin 960 based Devices.
Version 7/a - Name: SuperSUv2.82-EMUI5-dm-verity-KangV.zip
DOWNLOAD UPDATED VERSION: https://www.androidfilehost.com/?fid=745425885120739007
MD5: 8ca92c52a338fd82e923d0479769e23a
Version 7/b - Name: SuperSUv2.82-EMUI5-noverity-KangV.zip
Download for testing issues: https://www.androidfilehost.com/?fid=889764386195906387
MD5:0df87e5c4a5d41a0ed8b21085a33a6e8
About:
Version 7/a = dm-verity and dm-crypt enabled
Version 7/b = dm-verity disabled
init.d Support
script for K-Settings
script for busybox in /system/xbin
permanent SELinux Permissive
Version 7/a is working (tested) on:
KangV Roms
Huawei Mate 8
Huawei P9
Version 7/b is not tested yet!
PREVIOUS FINAL VERSION 2.81 - mixed code with chainfires and phh superusers - was working on most Huawei Devices:
https://www.androidfilehost.com/?w=files&flid=183923
How Do Root:​A) You need unlocked Bootloader and the TWRP related for your device installed!
TWRP for Huawei P9 Nougat you can find here - with Decryption Support by Recognized Developer OldDroid: https://forum.xda-developers.com/p9/development/twrp-t3565703
B) Look into your settings: Developer options must be enabled and inside: ADB Debugging and USB Debugging, as well as in settings/advanced settings/security "Allow unknown sources" PC should have the driver installed for connecting Phone in Fastboot Mode.
C) Make a TWRP Backup of - boot.img - data - system -vendor - before flashing SuperSUfor EMUI 5 - if one version dont work on your Huawei Device as it should, restore original boot.img with TWRP and try one of the other versions.
Note: If your Phone is not rooted -just flash SuperSU 2.81 EMUI 5 and reboot - Phone boots up two times and with the second boot you come back to your homescreen with Root.
If your Phone is rooted und you want update SuperSU - dont flash over existing Root, do following steps:
1) Copy SuperSU-2.82.zip to your external SD
2) Make a Complete Unroot from SuperSU App!
3) SuperSU ask: "Should SuperSU restore original boot.img" - check YES (2 times)
4) Phone reboots - dont wait but in the moment your screen is black press VOL+ Button and hold it the whole time until you are booted to TWRP.
5) In TWRP go to install and select SuperSU 2.82, swype to install
6) Search on Homescreen for SuperSU App and open it - look if you're done - if yes =good
NEXT STEPS ONLY IF ROOTING WAS NOT SUCCESFUL OR IF SUPERSU APK CANNOT UNROOT OR RESTORE BOOT.IMG:
Flash original (unmodified) boot.img with Fastboot - or restore boot.img from the Stock TWRP Backup (boot) of same Firmware
- if restored from TWRP Backup, dont restart system, go back and - flash SuperSU
- if flashed instead with Fastboot - disconnect USB from Device and with Power and VOL+ boot to TWRP and flash SuperSU
Note 2: If you are own the SuperSU PRO Version - you have just to update the SuperSU-Pro.apk directly from SuperSU "Upgrade to Pro Version". You will redirected to Playstore, install the Update!
If your Phone has a Custom Rom like Nougat KangV Rom - you can try to flash over existing Root - if it dont work (its different: for most will work, for some not) you can do:
Unroot with following steps:
0) KangV Roms for Nougat come with prerooted boot.img. SuperSU 2.82 should be able to patch and update it - just try.
If the update fails it would be good to find (or have) the original unmodified boot.img for the Firmware on which Rom is based and restore this.
1) Look into your settings: Developer options must be enabled and inside: ADB Debugging and USB Debugging, as well as in settings/advanced settings/security "Allow unknown sources" PC should have the driver installed for connecting Phone in Fastboot Mode.
2) Copy SuperSU 2.82 EMUI 5 to your external SD
3) Open old or not properly working SuperSU and make a "complete Unroot" - when SuperSU ask you 2 times "Do you want to restore original boot.img" check: YES
Maybe it is successful - perhaps not - if yes:
4) Phone reboots - but it cannot reboot to system!!
5) Instead booting to system you come into Huawei eRecovery - just make SHUTDOWN.
Now same steps, if the restore of original boot.img was not succesful - you must restore original (unmodifiied) boot.img from Firmware. If you have a TWRP-Backup from unrooted original boot.img restore it and go to 8) - if you have not a TWRP Backup for restore - go to step 6)
6) Connect Phone with USB to PC and with Vol- and Power start Phone into fastboot mode.
7) Flash unmodified boot.img with Minimal ADB and Fastboot. Disconnect phone from USB.
8) Press VOL+ with the finger of your left hand and press it all the time and with the finger of your right hand press Power Button.
9) Phone boot up and soon as Huawei Logo is shown on screen, release the Power Button but stay pressing VOL+ the whole time until you are in TWRP.
10) Flash SuperSU 2.82 EMUI 5
11) Phone boots up now two times and will finally boot to system.
12) search for SuperSU on Homescreen - its not on your usual place, its somwhere else on homescreen - open it and you should have now clean SuperSU 2.82
Do this steps just, if you had problems with flashing 2.82
Please report if you rooted your device successful / not succesful - and give information about your Device-model, Build number, TWRP-Version (fully or not properly working, ist it able to mount data with f2fs, make backup and restore?...)
Credits:
@Chainfire - SuperSU
@CCMT - SuperSU Release
@phhusson - phh's SuperUser/ OpenSource SELinux-capable SuperUser
@OldDroid - TWRP for P9 Android 7 with Decryption Support
@ante0 - Mate 9 Development
@Telperion - Honor 8 Development
Thank you ​
Thanks for the great job.
how do you root it if it's still not rooted? I lost root when I upgraded to nougat and never found out how to get it back
Thanks for job, but 2.81 version is really works? Because the 2.79 is not fully good: there was 1 problem: doesn't delete system programs with the Titanium Backup.
kazshizka said:
how do you root it if it's still not rooted? I lost root when I upgraded to nougat and never found out how to get it back
Click to expand...
Click to collapse
You just need the right TWRP and then flash SuperSU zip, reboot phone without wipe of Dalvik /Cache
Which phone model to you have?
Shyciii said:
Thanks for job, but 2.81 version is really works? Because the 2.79 is not fully good: there was 1 problem: doesn't delete system programs with the Titanium Backup.
Click to expand...
Click to collapse
You need also a good busybox 1.26.2 - I always use the one from YashdSaraf (xda)
Tecalote said:
You need also a good busybox 1.26.2 - I always use the one from YashdSaraf (xda)
Click to expand...
Click to collapse
SuperSU must works without busybox. My friend modified the SuperSU version 2.79, and it works fully.
Tecalote said:
You just need the right TWRP and then flash SuperSU zip, reboot phone without wipe of Dalvik /Cache
Which phone model to you have?
Click to expand...
Click to collapse
My phone is a P9, Model is EVA L-19. So i need to flash TWRP first? I just used a one click program the last time I rooted it so I'm too sure how to do stuff
kazshizka said:
My phone is a P9, Model is EVA L-19. So i need to flash TWRP first? I just used a one click program the last time I rooted it so I'm too sure how to do stuff
Click to expand...
Click to collapse
You need this TWRP: https://forum.xda-developers.com/p9/development/twrp-t3565703
And after flash with this TWRP this SuperSU and you are rooted
If you don't know how to flash TWRP, search related Thread
Tecalote said:
You need this TWRP: https://forum.xda-developers.com/p9/development/twrp-t3565703
And after flash with this TWRP this SuperSU and you are rooted
If you don't know how to flash TWRP, search related Thread
Click to expand...
Click to collapse
Many Thanks!!!!
Shyciii said:
SuperSU must works without busybox. My friend modified the SuperSU version 2.79, and it works fully.
Click to expand...
Click to collapse
This SuperSU works fully - but we talked about TitaniumBackup and this would may work better with Busybox.
Root without Busybox is like a tree without leaves.
I have not tested yet, if SuperSU works in case of TitaniumBackup without Busybox.
But you can test it by yourself.
And if your friend make it better let him do this Job - but don't discuss with me about Busybox
Shyciii said:
Thanks for job, but 2.81 version is really works? Because the 2.79 is not fully good: there was 1 problem: doesn't delete system programs with the Titanium Backup.
Click to expand...
Click to collapse
I have the same issues but these might be unrelated to the most recent SuperSU version. I cannot uninstall system apps and I can't "frost" system apps in Titanium Backup (I have pro version).
Also some other root apps don't work correctly like:
https://play.google.com/store/apps/details?id=de.andip71.screenoff&hl=de
https://play.google.com/store/apps/details?id=com.goodmooddroid.gesturecontrol&hl=de
clouds5 said:
I have the same issues but these might be unrelated to the most recent SuperSU version. I cannot uninstall system apps and I can't "frost" system apps in Titanium Backup (I have pro version).
Also some other root apps don't work correctly like:
https://play.google.com/store/apps/details?id=de.andip71.screenoff&hl=de
https://play.google.com/store/apps/details?id=com.goodmooddroid.gesturecontrol&hl=de
Click to expand...
Click to collapse
I make some tests in the evening on Stock Firmware with this SuperSU and will report you how to do
For PRO SuperSU is one more information in OP (OP updated)
cant freeze apps?
Terminal:
su
setenforce 0
done
xtcislove said:
cant freeze apps?
Terminal:
su
setenforce 0
done
Click to expand...
Click to collapse
Good idea to set temporarily SELinux from Enforcing to Permissive. :good:
I made also second version of SuperSU 2.81 for EMUI 5, which enables SELinux durable to permissive.
But I didn't post it here.
I don't know if people would like to have this.
Tecalote said:
Good idea to set temporarily SELinux from Enforcing to Permissive. :good:
I made also second version of SuperSU 2.81 for EMUI 5, which enables SELinux durable to permissive.
But I didn't post it here.
I don't know if people would like to have this.
Click to expand...
Click to collapse
Give it to me
xtcislove said:
Give it to me
Click to expand...
Click to collapse
Okay, in the later evening. I am at work now (Job)
Soon I come home
Give me too
Wysłane z mojego EVA-L09 przy użyciu Tapatalka
scaniathe said:
Give me too
Wysłane z mojego EVA-L09 przy użyciu Tapatalka
Click to expand...
Click to collapse
Yeah, I will update Thread with both versions and Users can choose

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)

🗃️S4 Unified Collection & Guides📚

Welcome to S4 Unified Collection!
​STOCK ROM FIRMWARES
[Check my Guides for Installation]
Note: If you can't find the Firmware for your device from the link below, then it's not my fault. Android File Host informed me, they delete files with less population on downloads. I don't have these files anymore.
You can find the latest Stock ROM Firmware for your S4 variant below:
GT-I9295 (jactivelte): I9295XXSDQD6 / Build Date: 2017-04-20 / OS: Lollipop 5.0.1
GT-I9500 (ja3gxx): I9500XXUHQD1 / Build Date: 2017-04-25 / OS: Lollipop 5.0.1
GT-I9505 (jfltexx): I9505XXUHQK1 / Build Date: 2017-11-09 / OS: Lollipop 5.0.1
GT-I9505G (jgedlte): I9505GUEUDPF1 / Build Date: 2016-05-13 / OS: Lollipop 5.1.1
GT-I9506 (ks01lte): I9506XXUDRB1 / Build Date: 2018-02-15 / OS: Lollipop 5.0.1
GT-I9515 (jfvelte): I9515XXS1BQD2 / Build Date: 2017-04-17 / OS: Lollipop 5.0.1
GT-I9515L (jfvelte): I9515LUBU1BQF1 / Build Date: 2017-06-08 / OS: Lollipop 5.0.1
SCH-I545 (jfltevzw): VERIZON USERS: since your bootloader is locked, you must be on the VRUAMDK
SCH-I545L (jfltelra): I545LWWSGQA1 / Build Date: 2017-01-05 / OS: Lollipop 5.0.1
SCH-R970 (jflteusc): R970TYSGPL1 / Build Date: 2016-12-02 / OS: Lollipop 5.0.1
SCH-R970C (jfltecri): R970CVRUFND1 / Build Date: 2014-04-11 / OS: KitKat 4.4.2
SCH-R970X (jfltecsp): R970XWWSGQA1 / Build Date: 2017-01-05 / OS: Lollipop 5.0.1
SGH-I337 (jflteatt): AT&T USERS: since your bootloader is locked, you must be on the UCUAMDB or UCUAMDL
SGH-I337M (jftlecan): I337MVLSGQB1 / Build Date: 2017-02-09 / OS: Lollipop 5.0.1
SGH-M919 (jfltemo): M919UVSFQA1 / Build Date: 2017-01-04 / OS: KitKat 4.4.4
SM-S975L (TracFone-StraightTalk): S975LUDUANB1 / Build Date: 2014-02-04 / OS: Jelly Bean 4.3
SPH-L720 (jfltespr): L720VPSGPL1 / Build Date: 2016-12-20 / OS: Lollipop 5.0.1
MODEMS & BOOTLOADERS
[Check my Guides for Installation]
Note: If you can't find the Modem/Bootloader for your device from the link below, then it's not my fault. Android File Host informed me, they delete files with less population on downloads. I don't have these files anymore.
You can find the latest Bootloader & Modem for your S4 variant below:
GT-I9295 (jactivelte): I9295XXSDQD6 COMBINED BOOTLOADER & MODEM / BOOTLOADER - MODEM
GT-I9500 (ja3gxx): I9500DXUHPB1 MODEM
GT-I9505 (jfltexx): I9505XXUHQK1 COMBINED BOOTLOADER & MODEM / BOOTLOADER - MODEM
GT-I9505G (jgedlte): I9505GUEUDPF1 MODEM
GT-I9506 (ks01lte): I9506XXUDRB1_I9506XXUDRA1 COMBINED BOOTLOADER & MODEM / BOOTLOADER - MODEM
GT-I9515 (jfvelte): I9515XXU1BQD2 COMBINED BOOTLOADER & MODEM / BOOTLOADER - MODEM
GT-I9515L (jfvelte): I9515LUBU1BQF1 COMBINED BOOTLOADER & MODEM / BOOTLOADER - MODEM
SCH-I545 (jfltevzw): VERIZON USERS: since your bootloader is locked, you must be on the VRUAMDK
SCH-I545L (jfltelra): I545LWWSGQA1 COMBINED BOOTLOADER & MODEM / BOOTLOADER - MODEM
SCH-R970 (jflteusc): R970TYSGPL1 COMBINED BOOTLOADER & MODEM / BOOTLAODER - MODEM
SCH-R970C (jfltecri): R970CVRUFND1 COMBINED BOOTLAODER & MODEM / BOOTLOADER - MODEM
SCH-R970X (jfltecsp): R970XWWSGQA1 COMBINED BOOTLOADER & MODEM / BOOTLOADER - MODEM
SGH-I337 (jflteatt): AT&T USERS: since your bootloader is locked, you must be on the UCUAMDB or UCUAMDL
SGH-I337M (jftlecan): I337MVLSGQB1 COMBINED BOOTLOADER & MODEM / BOOTLOADER - MODEM
SGH-M919 (jfltemo): M919UVSFQA1 COMBINED BOOTLOADER & MODEM / BOOTLOADER - MODEM
SM-S975L (TracFone-StraightTalk): S975LUDUANB1 COMBINED BOOTLOADER & MODEM / BOOTLOADER - MODEM
SPH-L720 (jfltespr): L720VPSGPL1 COMBINED BOOTLOADER & MODEM / BOOTLOADER - MODEM
RECOMMENDED ROMS
Recommend ROMs for the variants below, are:
Official LineageOS / LineageOS microG, Official crDroid, Official DivestOS or any of JDCTeam ROMs with tags [LIVE] [STABLE] [DAILY]
GT-I9505 (jfltexx)
GT-I9505G (jgedlte)
GT-I9507 (jtfddxx)
GT-I9508 (jfltezm)
GT-I9515 (jfvelte)
GT-I9515L (jfvelte)
SCH-I545 (jfltevzw) VERIZON USERS: since your bootloader is locked, you must be on the VRUAMDK
SCH-I545L (jfltelra)
SCH-R970 - jflteusc
SCH-R970C (jfltecri)
SCH-R970X (jfltecsp)
SGH-I337 (jflteatt) AT&T USERS: since your bootloader is locked, you must be on the UCUAMDB or UCUAMDL
SGH-I337M (jftlecan)
SGH-M919 (jfltemo)
SM-S975L (TracFone-StraightTalk)
SPH-L720 (jfltespr)
Recommened ROMs for the variants below are:
GT-I9295 (jactivelte): Official LineageOS / LineageOS microG
GT-I9500 (ja3gxx): -
GT-I9506 (ks01lte): Unofficial LineageOS 20.0 or Unofficial crDroid
TWRP RECOVERIES
[Check my Guides for Installation]
The list below contains the variants which can use the latest Official Unified TWRP Recovery or Unofficial TWRP Recovery or OrangeFox Recovery:
GT-I9505 (jfltexx)
GT-I9505G (jgedlte)
GT-I9507 (jtfddxx)
GT-I9508 (jfltezm)
SCH-I545 (jfltevzw)
SCH-I545L (jfltelra)
SCH-R970 - jflteusc
SCH-R970C (jfltecri)DCTeam
SCH-R970X (jfltecsp)
SGH-I337M (jftlecan)
SGH-M919 (jfltemo)
SM-S975L (TracFone-StraightTalk)
SPH-L720 (jfltespr)
The list below contains the variants which need a specific TWRP Recovery version:
GT-I9295 (jactivelte): Official TWRP Recovery
GT-I9500 (ja3gxx): Official TWRP Recovery
GT-I9506 (ks01lte): Official TWRP Recovery / TWRP- 3.6.0_9-0 or OrangeFox Recovery Project
GT-I9515 (jfvelte): Official TWRP Recovery
GT-I9515L (jfvelte): Official TWRP Recovery
SGH-I337 (jflteatt): TWRP Recovery Locki Patched by mattgyver
GAPPS & microG
GApps
Note: You should always use the smallest package of GApps, be sure you have selected Platform: ARM and the proper Android version of the ROM you are going to flash. If the ROM you want to flash include GApps, no need to download and flash any GApps at all.
Most of the GApps have also a config. file which can be used to to configure your installation the way you like. You can skip any Package that you don't want to be part of your installation. For more infos about that, read the instructions of the GApps you chose or search in Google.
MindTheGapps
BiTGApps
NikGApps (Only Core version)
Open GApps / Open GApps Unofficial A12L
LiteGapps
microG
If you don't want to use Google Play Services and general move away from Google, microG and its variants is an open source alternative which replace these services.
NanoDroid
MinMicroG
BiTGApps microG
microG
MAGISK ROOT
You can check my Guides for installation.
Magisk (APK)
Magisk.zip (Flashable Zip)
Uninstall.zip (Flashable Zip)
Magisk Canary (APK)
Magisk Delta
FoxMagiskModuleManager (This app replace the official magisk module repository since no longer available)
Momo (You can use this app too check if any modifications related Magisk are detected or not)
Universal SafetyNet Fix by kdrag0n [Video Guide]
Shamiko (Hide Root from apps) [Guide]
Note: If your apps detect root, follow this Guide (or this) to pass SafetyNet and have certified Play Store. [YouTube Video Guide]. For Microsoft Intune and other microsoft apps, check this guide.
PIT FILES
Note: If you messed the partitions of your device, you can fix it by simply flashing the PIT FILE for your variant via Odin in the PIT TAB.
The list below contains PIT FILES for some variants:
GT-I9500 (ja3gxx) PIT FILE
GT-I9505 (jftlexx) PIT FILE
SAMSUNG USB DRIVER
Note: If you have a problem while you connect the device to your PC and PC can't recognize it, you may miss the Samsung USB DRIVER. To fix follow these steps:
1. Download SAMSUNG USB DRIVER.
2. Unzip it and install it to your PC.
3. Connect your device and done! Now should be ok.
ODIN
You can download ODIN HERE. Recommened version is Odin 3.12.3
ULTIMATE COLLECTIONS & GUIDES (APPS)
Check the Privacy & Security section in my Guides.
If for some reason you can't find/install an app on Google Play Store due country restrictions or anything, you can sideload the app from APKMirror.
Android Ultimate Collection & Guides
Windows Ultimate Collection & Guides
ReVanced & ReVanced Extended - Guides & Useful Links
UNIVERSAL ANDROID DEBLOATER
Universal Android Debloater
S4 UNIFIED COLLECTION MIRROR
S4 Unified Collection AFH Mirror
DISCORD SERVER
Please verify yourself at #welcome channel. Read #FAQ channel.
Discord Server
JDCTEAM UNIVERSE
Here you can find the work of JDCTeam over the years for our S4 device!
Scroll Down to check the Guides
​
Welcome to S4 Unfied Guides!
!DISCLAIMER!
Most people I know (including myself) who used my Guides and steps, did that with success many times. If you don't follow exactly the steps or you do a mistake during the process, I do not take any responsibility for any unexpected results or damage that may happen. However I am here to help if something goes wrong, just ask in the thread.​
INSTALL BOOTLOADER & MODEM
You can flash Bootloader & Modem with two methods:
Combined: [Recommended]
1. Download Odin and the COMBINED BOOTLOADER _MODEM.tar for your variant to your PC. [You can find everything in my Collection]
2. Reboot your device to Download Mode by pressing Power Button + Vol.down + Home Button and run Odin from your PC as administrator.
3. Put the COMBINED BOOTLOADER_MODEM.tar to AP section, untick Auto-Reboot, flash!
4. When It's done, reboot your device by pressing Power Button for couple of seconds.
Seperate:
1. Download Odin, the BOOTLOADER.tar and MODEM .tar for your variant to your PC. [You can find everything in my Collection]
2. Reboot your device to Download Mode by pressing Power Button + Vol.down + Home Button and run Odin from your PC as administrator
3. Put the BOOTLOADER to BL section and MODEM to CP section, untick Auto-Reboot and flash!
4. When It's done, reboot your device by pressing Power Button for couple of seconds.
Notes:
Check what version of Modem and Bootloader you have with apps like Device Info HW.
If Modem & Bootloader didn't changed to the version you wanted, do the same steps again with the method you have selected.
If for some reason Odin failed to flash, make sure your run Odin as adminstrator, try to change USB Port in your PC and don't move the cable during flash. Also if you have Odin and the files on an External hard drive, move Odin and all the files you want to flash, into one folder to your Main Drive for example C: drive.
For Stock Rom to have your WiFi working you need to have the same version of Modem/BL as your Firmware. For example if you have QK1 Stock ROM then you need to have QK1 Modem/Bootloader. On Custom ROMs doesn't matter. You can have any Modem/BL of your variant you want but recommend is always the latest.
INSTALL TWRP RECOVERY
ODIN Method (No TWRP Recovery currently installed)
1. Download Odin and the .tar file of the TWRP to your PC. [You can find everything in my Collection]
2. Reboot to Download Mode by pressing Power Button + Vol.Down + Home Button.
3. Run Odin as adminstrator > connect your device to PC > put the .tar file of TWRP in AP section > untick Auto-Reboot in options and flash.
4. Done! Restart to TWRP Recovery. (power button+vol.up+home button)
Recovery Method (TWRP Recovery already installed)
1. Download .img of TWRP Recovery. [You can find everything in my Collection]
2. Reboot to Recovery by holding Power Button + Volume Up (+).
3. Press Install Image.
4. Locate the recovery.img you recently downloaded.
5. Select it and choose the option Recovery and Flash.
6. Go back and Reboot to Recovery.
7. Done! Your new recovery should be installed.
CLEAN INSTALL CUSTOM ROM
Note: If you have issues after flash check possible solutions here:
Check integrity of all downloads (compare checksums), do the downloads again.
Make sure you Wiped everything and Formated Data (format data not just wipe) except external SDCard and USB OTG.
Flash only the ROM (without GApps and Magisk) and check if the problem persists. If yes, flash another ROM.
Try other GApps package.
If nothing helps, go back to stock and start from scratch.
Note: You can also Flash Custom ROM using ADB sideload Method.
1. Backup all your data to PC or to external SDCard. [All your data into Internal Storage will be lost on step 7 while Formating Data or Wiping Internal Storage]
2. Install the latest Bootloader & Modem for your S4 variant. [Read the Install Bootloader & Modem Guide above]
3. Download: [You can find everything in my Collection]
TWRP Recovery.
Custom ROM of your choice.
GApps (be sure you have selected Platform: ARM and the proper Android version of the ROM you are going to flash) if the ROM you are going to flash does not include. [Optional]
Magisk Root. [Optional]
4. Move all these files in one folder to your PC or to External SDCard if you have one.
5. Install TWRP Recovery. [Read the Install Custom Recovery Guide above]
6. Turn off your device and Reboot to Recovery Power Button + Volume Up (+)
7. Installation:
Steps without external SDCard:
Select Wipe > Advanced Wipe
Select Dalvik / ART Cache, System, Data, Internal Storage, Cache and then Swipe to Wipe. [All your data into Internal Storage will be lost]
Go back and select Wipe > Format Data > type yes [All your data into Internal Storage will be lost]
Connect your device to PC while you are on TWRP and transfer into Internal Storage, the ROM, GApps etc. and the files you want to flash.
Flash ROM > GApps [Optional]
Reboot Enjoy!
[Optional] If you want to root, reboot once again to TWRP Recovery and flash Magisk (you need to download it again if you previously had it in Internal Storage) then reboot to system and enjoy!
Steps with external SDCard:
go to Advanced > File Manager > External_SD and delete all folders in ur ext sd card (For example you should delete: Android, .android_secure, LOST.DIR, DCIM, etc) except your personal files/folders and the folder with your custom ROM/Gapps/Magisk/DFE you want to flash.
Each app on your phone with the WRITE_EXTERNAL_STORAGE permission may create files or folders in ur sdcard. Most of these folders have once been created by one of these apps and many of them may be deleted with a few exceptions (e.g. Android, .data, .android_secure, these contain important system or app data like a game's downloaded content):
.android_secure: apps installed and then moved to sdcard
Android: app data/cache
data: app data
.estrongs: ES file manager
LOST.DIR: sort of trash folder (collects recovered files after phone crashes)
DCIM: phone gallery's photos and previews
OTA-update: Over The Air update service
ppy_cross: an unknown third-party app's data.
So I recommend to delete them so you can put your phone/sdcard in a clean state and is guaranteed to be able to re-create these folders.
Select Advanced Wipe
Select Dalvik / ART Cache, System, Data, Internal Storage, Cache and then Swipe to Wipe. [All your data into Internal Storage will be lost]
Go back and select Wipe > Format Data > type yes [All your data into Internal Storage will be lost]
Flash ROM > GApps [Optional]
Reboot Enjoy!
[Optional] If you want to root, reboot once again to TWRP Recovery and flash Magisk then reboot to system and enjoy!
DIRTY INSTALL YOUR CUSTOM ROM
Note: Before you start flashing, keep in mind the ROM you dirty flashing MUST be the same with the one you have already installed.
1. Make a full nandroid backup, just in case something goes wrong. You can use TWRP to do that. (TWRP > Backup > Select everything) [Optional]
2. Remove all Magisk modules. [Optional]
3. Reboot to TWRP and Wipe Dalvik / ART Cache, System and Cache.
4. Flash the ROM > GApps [Optional] > Magisk [Optional]
5. Reboot and Enjoy!
I've skipped some explanations, because if you are going to dirty flash, you already know for example how to boot to TWRP.
CLEAN INSTALL OFFICIAL STOCK ROM
Note: For Stock Rom to have your WiFi working you need to have the same version of Modem/BL as your Firmware. For example if you have QK1 Stock ROM then you need to have QK1 Modem/Bootloader. On Custom ROMs doesn't matter. You can have any Modem/BL of your variant you want but recommend is always the latest.
1. Download the latest stock ROM (Firmware), Modem & Bootloader for your variant, TWRP Recovery (.tar file) and ODIN to your PC. [You can find everything in my Collection]
2. Install TWRP Recovery [Read the Install Custom Recovery Guide above]
3. Reboot to TWRP Recovery and Select Wipe > Advanced Wipe
4. Select Dalvik / ART Cache, System, Data, Cache, External SDCard (if you have) and then Swipe to Wipe.
5. Go back and select Wipe > Format Data > type yes [All your data into Internal Storage will be lost]
6. Reboot to Download Mode Power by pressing Power Button + Vol.Down + Home Button
7. Run Odin as adminstrator from your PC > connect your device > put the Stock Rom (Firmware) file to AP section and flash it!
8. Let the ROM boot.
9. Install the same version of Bootloader & Modem as your Firmware. [Read the Install Bootloader & Modem Guide above]
10. Enjoy!
BACKUP & RESTORE ROM (NANDROID BACKUP)
Check this Youtube Video to see the process in action.
Backup:
1. Reboot to Recovery (Power Button + Volume Up (+))
2. Choose Backup and Select Boot > System > Data (excl. storage)
3. Select Storage and choose SDcard if you have one otherwise let it on Internal Storage.
4. Swipe to Backup.
5. Done!
Restore:
1. Reboot to Recovery. (Power Button + Volume Up (+))
2. Select Wipe > Advanced Wipe.
3. Select Dalvik / ART Cache, System, Data, Cache and then Swipe to Wipe.
4. Press Home Button to go back and Select Restore.
5. Select the backup file with the ROM and make sure Boot, System and Data (excl. storage) are selected.
6. Select Swipe to Restore and when completed Reboot to System.
7. Done!
MAGISK ROOT
The easiest way to root your device is via Magisk, it should work in all ROMs, Stock and Customs.
Install Magisk:
1. Install latest TWRP Recovery. [Read the Install Custom Recovery Guide above]​2. Download the Magisk [You can find it in my Collection]​3. Reboot to TWRP Recovery by pressing Power Button + Volume Up (+) and flash it.​4. Reboot and check whether the Magisk app is installed. If it isn’t installed automatically, manually install the APK. [You can find it in my Collection]​Note#1: From Official TWRP Recovery 3.5.1 and onward (and other recoveries based on that), Magisk.apk can be flashed as apk without the need of rename it to .zip. So you can simply flash the Magisk.apk in TWRP.​Manually Creation of Flashable Zip:​Download the latest Magisk APK and rename the Magisk.apk → Magisk..zip.​​Note#2: If your bank apps detect root, follow this Guide.​
Uninstall Magisk:
Flash the Uninstall.zip in TWRP Recovery and reboot. [You can find it my Collection]
If Magisk App isn’t uninstalled automatically, manually uninstall the app.
Manually creation of Flashable Uninstall Zip:
Download the latest Magisk APK and rename the Magisk.apk → uninstall.zip
Uninstall Magisk directly through the Magisk app. Simply press the Uninstall button.
Note: If your apps detect root, follow this Guide (or this) to pass SafetyNet and have certified Play Store. [YouTube Video Guide]
MIXER_PATHS (INCREASE VOLUME VALUES)
Check HERE and HERE.
HOW TO TAKE LOGS
How to take logs on Android
SCREEN RETENTION FIX
Screen Retention FIx: If you have an issue with screen retention apply this configuration to your device ROM.
BATTERY TIPS
Samsung Galaxy S4 Battery Model: B600BE
Battery Replacment (Video)
Advanced Guide
Simple Battery & Charging Tips
Improve your SOT
Battery Calibration
Method 1
Steps:
1. Discharge your phone fully until it turns itself off.
2. Turn it on again and let it turn itself off.
3. Plug your phone into a charger and, without turning it on, let it charge until the on-screen or LED indicator says 100 percent.
4. Turn your phone on. It's likely that the battery indicator won't say 100 percent, so plug the charger back in (leave your phone on) and continue charging until it says 100 percent on-screen as well.
5. Unplug your phone and restart it. If it doesn't say 100 percent, plug the charger back in until it says 100 percent on screen.
6. Repeat this cycle until it says 100 percent (or as close as you think it's going to get) when you start it up without it being plugged in.
Method 2
Notes: It won't dramatically extend battery life, but it will give your old battery at least 30 minutes additional run time.
Steps:
1. Get "GSam or Ampere" from the Google Play Store.
2. Launch the app and fully charge your phone. (Important: Only proceed with the calibration when the word "Full" appears in GSam or Ampere.)
3. While your phone is still connected to the cable reboot your phone to recovery mode, open file manager and navigate to "/data/system" and delete "batterystats.bin," "batterystats-checkin.bin," and "batterystats-daily.xml."
4. Reboot your phone (while it is still plugged in) and charge it until it reads "full" on GSam or Ampere.
5. Unplug the cable and use your phone normally until it shuts down (0 percent )
6. Charge your phone to 100% while it is turned off.
7. Boot into os and plug in your phone and charge it until it says "full" on the GSam or Ampere.
8. Unplug and have fun!
Battery Capacity Health
Notes:
1) Before checking the battery health, charge the device to 100%.
2) Check charge counter values and consider first 4 digits from left as your battery capacity in mAh. And check charge counter. (Charge counter/level)*100 is the battery capacity.
To find battery capacity in Windows:
Enable Developer options in your device.
Enable USB Debugging in your device.
Conect your device to PC and give permissions.
Open Minimal ADB (run cmd.exe) or Platform tools.
Type "adb shell dumpsys battery" command in Minimal ADB or Platform tools.
To find battery capacity in Android (Terminal) - Root needed:
Download an android terminal app like Termux,
Open terminal and type: cat/sys/class/power_supply/battery/charge_full
Overheating
Following reasons will lead to device heating issue:
During the initial setup after purchase or when restoring data.
Downloading large files.
Using apps that require more power or using apps for extended periods such as:
Playing high-quality games for long time.
Recording videos for extended periods.
Streaming videos while using the maximum brightness setting.
Using the Screen Mirroring / Smart View feature (connecting mobile to a TV).
While multitasking or when running many apps in the background i.e:
Using Multi window.
Updating or installing apps while recording videos.
Downloading large files during a video call.
Recording videos while using a navigation app.
Large amount of data for syncing with the cloud, email, or other accounts.
Exposing device under sunlight when temperature is high around you.
Extensive usage of mobile hotspot and tethering feature.
Using device in areas with weak signals or no reception or in roaming network.
Charging the battery with a damaged / unapproved USB cable.
Device's multipurpose jack is damaged or exposed to foreign materials, such as liquid, dust, metal powder, and pencil lead.
Solution:
Turn off Wi-fi, GPS , bluetooth and other connectivity options when not in use by dragging the notification panel.
Decrease screen brightness.
Close background running applications.
Too many applications installed in device may result in device heating since their corresponding process will keep on running in background. It is advised to uninstall un-necessary apps if not using them.
Avoid using apps like GPS, data dependent apps or graphic intensive games for longer duration since they require more energy to function, causing device to heat.
It is advised not to use device while charging as it may cause the device to over heat.
General:
DO:
Use manual brightness or dim the screen.
Turn off notifications for apps you don't use. Better still, delete/disable the apps entirely if you don't need them.
Enable battery or power saving mode when you want to extend your battery life.
Use the power adapter that came with your phone. Other chargers can charge slowly/faster but they can also damage your phone or battery.
Turn off bluetooth, location tracking, and Wi-Fi (unless you are actively using it)
Turn off print services from bluetooth connection preferences.
Avoid extremes of heat and cold. If your phone gets very hot or cold it can strain the battery and shorten it's lifespan.
DON'T:
Have Bluetooth or Wi-Fi turned on constantly.
Leave apps running in the background. Instead restrict background usage off apps that you don't need running.
Push email means your device is always listening for new email which drains alot of battery.
Drain your phone battery all the way to 0% or charging it all the way to 100%. Keep it between 20% - 90% for longer battery lifespan.
The more advanced the graphics and animations are (games, videos, photos, animations), the harder the processor and graphics chip in your smartphone have to work. More activity means more battery use.
PRIVACY & SECURITY
Some useful links:
All about Privacy & Security at Privacy Guides.
Electronic Frontier Foundation.
PrivacyTests: Open-source tests of web browsers privacy.
Check if your email address or your phone number is in a data breach at Have I been Pwned & at Firefox Monitor.
Test your browser to see how well you are protected from tracking and fingerprinting at Cover Your Tracks by EFF and at Bromite fingerprint mitigations tests.
WebRTC IP Leak Test. WebRTC is a new communication protocol that relies on JavaScript that can leak your actual IP address from behind your VPN. You can find more infos how to disable it at Privacy Guides in browsers section.
Ad Block Tester is a free service on the Internet to evaluate content blocking solutions. It is not designed to be a benchmark, but it reveals the level of blocking against a set of hosts that are very popular.
Check on AM I FLoCed? by EFF if your your Chrome browser has been turned into a guinea pig for Federated Learning of Cohorts or FLoC, Google’s latest targeted advertising experiment.
How to block ads on Android.
εxodus: εxodus analyzes Android applications in order to list the embedded trackers and ads.
Spyware Watchdog Article Catalog: A catalog which determinate under tests and tracking if an app is spyware and what data it collects.
CryptPad: CryptPad is built to enable collaboration. It synchronizes changes to documents in real time. Because all data is encrypted, the service and its administrators have no way of seeing the content being edited and stored.
PrivateBin: PrivateBin is a minimalist, open-source online pastebin where the server has zero knowledge of pasted data. Data is encrypted/decrypted in the browser using 256-bit AES. It is the improved version of ZeroBin.
ShutUP10++ , Privacy.Sexy: Disable major tracking features of Windows.
General:
Always prefer Open Source or well popular Programs, Apps, ROMs, Kernels & Stuff.
Open Source doesn't mean it's 100% safe but it's unlikely to have something suspicious, since you and other users can check the code in GitHub or in any other code hosting platform the "stuff" is hosted. You can also find and use FOSS apps at Droid-ify.
Prefer ROMs & Kernels with SELinux Enforcing. You can find informations here.
Always download and install Apps, Programs, ROMs & Stuff from official sources and do not use redirection links from different sites. Google is your friend to find the official source of the stuff you want.
Always check the permissions an app requires, before download and install it to your device. If an app ask for permissions which has nothing to do with the app functionality then it's should be reconsider or ask the developer why these permissions needed.
You can also check if the app includes trackers and ads with εxodus.
If you want to avoid Google and Play Store (De-Google), you can choose a ROM without GApps preinstalled like LineageOS and use Droid-ify client which is an installable catalogue of FOSS (Free and Open Source Software) applications for the Android platform. The client makes it easy to browse, install, and keep track of updates on your device. Note that not all apps from Play Store will be available in Droid-ify or F-Droid. Only Open Source projects. You can find alternatives though.
Alternative you can use LineageOS for microG or any ROM which support signature spoofing and can support microG and use Aurora Store.
For Windows use the default Windows Defender & Malwarebytes to scan your files whenever you want (Prefered before open or install them). Also use the addon/extension uBlock Origin in your Browser. These should be enough for normal users. You can also use the tool ShutUp10++ or Privacy.Sexy to disable major tracking features of Windows.
For Android Do not use any antivirus - antimalware since it's useless, just check what apps and from where you installing.
Always verify the source of addons/extensions in your browser. Avoid installing random and unpopular addons/extensions. Keep it minimal and clean, so browser can be fast and safe, no need bunch of extensions.
If you are using VPN, always check the terms and rules of the provider. Avoid random VPN Services.
Recommended VPN Services.
Using a VPN will not keep your browsing habits anonymous, nor will it add additional security to non-secure (HTTP) traffic.
Recommended is to encrypt your data/files always before uploading them to cloud with tools like Cryptomator.
Always use unique and strong passwords for each of your accounts.
Use awarded open source Password Managers like KeePass or KeePassXC for Desktop and KeePassDX for Android to manage your passwords and have them with you safe, encrypted and secure. Must be noted you can use the same database file between these programs.
Always enable 2 Step Authentication wherever is available for your accounts.
You can use apps like Aegis Authenticator.
Do not open or click on links attached in unknown emails or SMS you may get. Always check the address of the email or the number of SMS and verify it's legit from the official source.
Create and use "burned" email for accounts/sites you have concerns but you definitely want to try them. Do not use your personal or business email. You can also create and use email aliases of your email with SimpleLogin which is open source and awesome service.
DISCORD SERVER
Please verify yourself at #welcome channel. Read #FAQ channel.
Discord Server
Changelog
Note: Changes in Collection & Guides happens in real time. The date I post these Changelogs is just a sum up since I can't post all the changes the time that happening to avoid spamming the thread. So you can always consider the Collection & Guides Up-to-Date. However, I may announce some big changes in posts before I include them in the Changelogs.​
LATEST
Update: 18/01/2023
Changelog
ARCHIVED
Update: 29/10/2022
Changelog
Update: 01/07/2022
Changelog
Update: 07/05/2022
Changelog
Update: 01/04/2022
Changelog
Update: 28/02/2022
Changelog
Update: 04/02/2022
Changelog
Update: 23/12/2021
Changelog
Update: 01/10/2021
Changelog
Update: 31/08/2021
Changelog
Update: 01/05/2021
Changelog
Update: 19/04/2021
Changelog
Update: 27/02/2021
Changelog
Update: 28/01/2021
Initial Release
Hi guys,
I can't manage to install the Bootloader & Modem via Odin on my phone.
Does the phone need to be already rooted in order to install the B&M?
Attached is also the capture I took when rebooting the phone in Download mode.
I selected "reboot to bootloader" in order to install the B&M, because otherwise Odin won't detect that the phone is connected to the PC. Probably I'm doing something wrong.
Any help will be very much appreciated.
Thanks in advance.
{
"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"
}
R_A_N_D_Y said:
Does the phone need to be already rooted in order to install the B&M?
Click to expand...
Click to collapse
I'n not 100% sure, but I think no
R_A_N_D_Y said:
Attached is also the capture I took when rebooting the phone in Download mode.
Click to expand...
Click to collapse
The picture shows your device in recovery
R_A_N_D_Y said:
I selected "reboot to bootloader"
Click to expand...
Click to collapse
How did you do that? I'm not aware of such a reboot option.
You should boot into download mode (see above for how to). It should look like attached picture 1
In Odin, before you start flashing, you should see a success message "<ID ... Added!! If not, you should check if you have all required driver installed for your device.
pocketrule said:
I'n not 100% sure, but I think no
The picture shows your device in recovery
How did you do that? I'm not aware of such a reboot option.
You should boot into download mode (see above for how to). It should look like attached picture 1
In Odin, before you start flashing, you should see a success message "<ID ... Added!! If not, you should check if you have all required driver installed for your device.
View attachment 5212215View attachment 5212217
Click to expand...
Click to collapse
Thank you very much !
R_A_N_D_Y said:
Hi guys,
I can't manage to install the Bootloader & Modem via Odin on my phone.
Does the phone need to be already rooted in order to install the B&M?
Attached is also the capture I took when rebooting the phone in Download mode.
I selected "reboot to bootloader" in order to install the B&M, because otherwise Odin won't detect that the phone is connected to the PC. Probably I'm doing something wrong.
Any help will be very much appreciated.
Thanks in advance.
Click to expand...
Click to collapse
No need root.
Download and install the Samsung USB Drivers in your PC. (You can find it in my collection)
Download the Combined Bootloader & Modem for your variant from my collection.
Turn off your device.
Reboot your device to Download Mode by pressing Power Button + Vol.down + Home Button and run Odin from your PC as administrator.
Put the COMBINED BOOTLOADER_MODEM.tar to AP section, untick Auto-Reboot in options and flash!
When It's done, reboot your device by pressing Power Button for couple of seconds.
New Update:
Changelog:
Added Changelog Tracking at #3 post
Added Privacy & Security section in Guides.
Added a Note to check Privacy & Security Guide at Useful Apps section in Collection.
Added Flashable Zips for Install & Uninstall Magisk in Collection.
Updated the Magisk Guide and added Flashable Zip method.
Reordered the sections in Guides.
Hi Retrial, first of all this is a really useful post thank you so much!
I just bought a brand new S4 GT-I9505 and I used the latest TWRP in your post wich is twrp-3.5.1_9-0-jflte.img.tar for flashing lineage-17.1-20210116-UNOFFICIAL-jflte.zip and I have some question if you are so kind to aswer me:
I want to update the firmware so I downloaded the last one for Italy from Updato.com which is I9505XXUHPK2 (Genuary 2017) and I would like to know if is a good idea to flash it with Odin and if I have to fresh re-installing Lineage. Then I would like to know if after updating the firmware I can update only XXUHQC1_BOOTLOADER and XXUHQC1_COMBINED which are the international versions and obviously the most recent versions.
Do you think is possible? Thanks in advance. Kind Regards
hermes127 said:
Hi Retrial, first of all this is a really useful post thank you so much!
I just bought a brand new S4 GT-I9505 and I used the latest TWRP in your post wich is twrp-3.5.1_9-0-jflte.img.tar for flashing lineage-17.1-20210116-UNOFFICIAL-jflte.zip and I have some question if you are so kind to aswer me:
I want to update the firmware so I downloaded the last one for Italy from Updato.com which is I9505XXUHPK2 (Genuary 2017) and I would like to know if is a good idea to flash it with Odin and if I have to fresh re-installing Lineage. Then I would like to know if after updating the firmware I can update only XXUHQC1_BOOTLOADER and XXUHQC1_COMBINED which are the international versions and obviously the most recent versions.
Do you think is possible? Thanks in advance. Kind Regards
Click to expand...
Click to collapse
Hello,
If you flash firmware u need to reflash lineageos from start along with twrp. U can only do it via Odin.
Btw use the latest for your variant from my collection. Doesn't matter the country.
Flashing firmware=flashing stock rom. Why u want to do that if u are already in los?
You can flash bootloader and modem seperate yes (but I recommend to use my combined .tar which include both of them), without the need to flash everything again. Just go to Odin and flash the combined .tar I have made to AP. Once again, all the latest versions are included in my collection, doesn't matter the country so just use them.
All the infos and steps you need are in my collection and guides. Let me know if you have more questions.
Retrial said:
Flashing firmware=flashing stock rom. Why u want to do that if u are already in los?
Click to expand...
Click to collapse
Hi thanks for your fast response! I want to flash an updated firmware because my S4 GT-I9505 is new and probably from an old stock so the firmware is for sure the old one (2013-2014) ,right now in lineage os in setting/info I can't see the current version of baseband. I don't care if I have to re-install Lineage and the recovery, I had to do it before installing Lineage, I know I forgot it... but I wanted just to know if is possible to do now without breaking something. Now you say that it doesn't make sense and that is better to just flash your combined Modem and Bottloader package, is it correct? What's your advice: installing your last complete firmware or just the combined Bootloader and Modem package? I red somewhere in this forum that it's better to update the firmware before installing lineage so I wanted to do the installation again in the right way. Sorry if it's an annoying question I'm not an expert and I want just to be sure. Thank you so much for your support.
hermes127 said:
Hi thanks for your fast response! I want to flash an updated firmware because my S4 GT-I9505 is new and probably from an old stock so the firmware is for sure the old one (2013-2014) ,right now in lineage os in setting/info I can't see the current version of baseband. I don't care if I have to re-install Lineage and the recovery, I had to do it before installing Lineage, I know I forgot it... but I wanted just to know if is possible to do now without breaking something. Now you say that it doesn't make sense and that is better to just flash your combined Modem and Bottloader package, is it correct? What's your advice: installing your last complete firmware or just the combined Bootloader and Modem package? I red somewhere in this forum that it's better to update the firmware before installing lineage so I wanted to do the installation again in the right way. Sorry if it's an annoying question I'm not an expert and I want just to be sure. Thank you so much for your support.
Click to expand...
Click to collapse
Just follow what Retrial said; flashing his combo-file will accomplish what you want. Starting from scratch like you wanna do isn't any better.
I flashed bootloaders and modems so often, I can't even remember. Flashing stock firmware? Maybe once!
hermes127 said:
Hi thanks for your fast response! I want to flash an updated firmware because my S4 GT-I9505 is new and probably from an old stock so the firmware is for sure the old one (2013-2014) ,right now in lineage os in setting/info I can't see the current version of baseband. I don't care if I have to re-install Lineage and the recovery, I had to do it before installing Lineage, I know I forgot it... but I wanted just to know if is possible to do now without breaking something. Now you say that it doesn't make sense and that is better to just flash your combined Modem and Bottloader package, is it correct? What's your advice: installing your last complete firmware or just the combined Bootloader and Modem package? I red somewhere in this forum that it's better to update the firmware before installing lineage so I wanted to do the installation again in the right way. Sorry if it's an annoying question I'm not an expert and I want just to be sure. Thank you so much for your support.
Click to expand...
Click to collapse
Firmware=Stock Samsung ROM. Firmware does not include Modem & Bootloader. So even if u flash Firmware u have to also flash Bootloader & Modem.
Now you say that u are on lineageos, I don't know what version you are but you can flash via Odin the combined .tar file which include Bootloader & Modem and then clean install via TWRP the latest LineageOS along with latest GApps if you use.
If you want to start from scratch-fresh then follow my Guides: "Clean Install Official Stock ROM" and then the guide "Clean Install Custom ROM".
With few words: go to TWRP wipe everything, the connect ur device to PC and flash via Odin the latest Firmware (stock ROM). Let it boot and then flash via Odin the latest Bootloader & Modem. Then flash TWRP and clean install the latest LineageOS with GApps (optional).
Everything you need is on my collection and all steps in my guides. Since u have i9505 variant you need the latest Firmware/Modem & Bootloader which is I9505XXUHQK1.
Let me know how it goes or if you have any other questions.
Retrial said:
Flashing firmware=flashing stock rom. Why u want to do that if u are already in los?
Click to expand...
Click to collapse
Retrial said:
Firmware=Stock Samsung ROM. Firmware does not include Modem & Bootloader. So even if u flash Firmware u have to also flash Bootloader & Modem.
Now you say that u are on lineageos, I don't know what version you are but you can flash via Odin the combined .tar file which include Bootloader & Modem and then clean install via TWRP the latest LineageOS along with latest GApps if you use.
If you want to start from scratch-fresh then follow my Guides: "Clean Install Official Stock ROM" and then the guide "Clean Install Custom ROM".
With few words: go to TWRP wipe everything, the connect ur device to PC and flash via Odin the latest Firmware (stock ROM). Let it boot and then flash via Odin the latest Bootloader & Modem. Then flash TWRP and clean install the latest LineageOS with GApps (optional).
Everything you need is on my collection and all steps in my guides. Since u have i9505 variant you need the latest Firmware/Modem & Bootloader which is I9505XXUHQK1.
Let me know how it goes or if you have any other questions.
Click to expand...
Click to collapse
Wow your instructions are absolutely detailed and useful, thank you so much Retrial for your support.! I'll opt for the "start from scratch-fresh" install by following your guides. If I can take advantage of your competence I would like to ask you just one last advice: I switched to Lineage OS for privacy reasons (I don't like google so I don't need GApps) and I also use it for sharing internet to my MacBook Pro with USB tethering (not wifi tethering which is not safe for privacy) so do you think that the Optimized Lineage OS (Android 10) version from JDCTeam is the right version for me? May I use the Android 11 version? Probably I'm asking you to much things and I can understand if you can't answer me, you have been really kind and I really appreciated your help. Anyway I'll post here my experience with "start from scratch-fresh instal" .
Anything for the AT&T S4 Active (+) variant?
hermes127 said:
Wow your instructions are absolutely detailed and useful, thank you so much Retrial for your support.! I'll opt for the "start from scratch-fresh" install by following your guides. If I can take advantage of your competence I would like to ask you just one last advice: I switched to Lineage OS for privacy reasons (I don't like google so I don't need GApps) and I also use it for sharing internet to my MacBook Pro with USB tethering (not wifi tethering which is not safe for privacy) so do you think that the Optimized Lineage OS (Android 10) version from JDCTeam is the right version for me? May I use the Android 11 version? Probably I'm asking you to much things and I can understand if you can't answer me, you have been really kind and I really appreciated your help. Anyway I'll post here my experience with "start from scratch-fresh instal" .
Click to expand...
Click to collapse
Don't worry mate, ask whatever you want. I will help if I can.
Optimized LineageOS 10 is great but it's EOL (end of life). Optimized LineageOS 11 is also great and it's currently under development.
But since you are looking for privacy & security it's better to use Official LOS with guarantee monthly security patches cause lately optimized los stays a bit behind on updates. (Dev is busy) Soon official 11 will also be released.
blackhawk said:
Anything for the AT&T S4 Active (+) variant?
Click to expand...
Click to collapse
I think ur variant has locked bootloader so I don't know if anything exist.
Retrial said:
I think ur variant has locked bootloader so I don't know if anything exist.
Click to expand...
Click to collapse
Thank you. If you become aware of any work arounds please let me know.
It's a phone that is expendable now
blackhawk said:
Thank you. If you become aware of any work arounds please let me know.
It's a phone that is expendable now
Click to expand...
Click to collapse
I know there is a workound for S4 AT&T on specific firmware with locki patched TWRP but I don't think it's exist anything for ur S4 active at&t. I will let u know if I find anything.
Retrial said:
Don't worry mate, ask whatever you want. I will help if I can.
Optimized LineageOS 10 is great but it's EOL (end of life). Optimized LineageOS 11 is also great and it's currently under development.
But since you are looking for privacy & security it's better to use Official LOS with guarantee monthly security patches cause lately optimized los stays a bit behind on updates. (Dev is busy) Soon official 11 will also be released.
Click to expand...
Click to collapse
Ok thank you, I'll follow your advice.

Development [21.06.23] Full ROM System-RW for S908E/B I Magisk ROM Module for all S22 I Dr.Ketan ROM

S908B & S908E system-rw Dr.Ketan ROM
Supported device : S918B & S908E/N for Full ROM, All rootable variants for Magisk Module
We do support usually 2-3 years since device launched, but yet no guarantee, We may drop support for any device / any variant/s anytime without any prior notice.
ROM Features
ROM Features varies with version of ROM. For more details, read changelog post. Link available in post #3 for changelog of all versions.
Must read changelog for a version you are going to install, it will have latest information about features, changes, known bug list/fix and Installation guide of respective version.
There are two types of ROM available since OneUI 5.0
1.Full system-rw ROM : Full ROM includes super.img with system-rw capabilities + stock enforcing kernel + ROM Control & Modification
Supported device : S908B & S908E
2.Magisk ROM Module and here explained in details how it is different from full ROM
Supported device : All S22 variants
Credit and Thanks :
@Chainfire - Respected elite developer for supersu and his unbelievable contribution to XDA/Android community. @wanam - Respected elite developer for his awesome contribution and references to his works.
@topjohnwu for Magisk
@xperiacle the amazing developer for reference to his work and tools. @amarullz for aroma installer. @gharrington for 3minit battery and QuickLaunch.
ROM Control source and all credit and thanks goes to @daxgirl and @Wuby986 for their open source project for RomControl.
@AbrahamGC for some ideas samsungvn htcmania & 4PDA for tips and some stock apks.
AbrahamGC and Anan1211 for Secure folder and s-health A12 ianmacd for TWRP @afaneh92 for TWRP, system/vendor rw scripts and modules. @Arteush for bluetooth fix (losing BT pair on reboot) on Android Q, aka_vkl for Dolby digital, kdrag0n for SafetyNet fix @Winb33 for custom font pack. HuskyDG for Bootloop Protector magisk module. MrWeahere for CRB Kitchen
​​​
​​XDA devDB Information​S908 I Dr.Ketan ROM , ROM for the Samsung Galaxy S22 Ultra
Contributors
Dr.Ketan
ROM OS Version: Android 12
ROM Kernel: Stock (pre-rooted). Source code (samsung) here
ROM Firmware Required: Stock Samsung specified version
Version Information
Status: Stable
Created 2022-03-12
Installation, Important Infos & Download
Installation : State of the art Installation procedure.
Detailed installation guide separately available in download area along with ROM files for Full ROM and for magisk module read changelog post.
WARNING
Before you root your device you must be aware that
This will void warranty.
As of now you will lose Samsung Pay and Samsung Pass forever if you root once, even unrooting won't help.
There are many features stop working when you unlock bootloader other than S pay/Pass like Samsung Health, Secure Folder, Galaxy Watch pairing issue, Issue connecting old gear watch (S3 or earlier), Google Pay etc but ROM is patched for all these mentioned features. Still you may trouble using some bank apps and these may fixed by adding these apps to Magisk Hide
There may be some knox features there which you may not able to use but I can't list those as I never used. Just Google It
Patched featurs are working today when writing this, No idea if it may stop working next moment/tomorrow or later
Also to note, once you root, you can't go back to "pre-rooted" state completely. It is one way!
OTA won't work once you root device.
ROOT with caution.
You can unroot & Relock bootloader after flashing stock firmware, but still your warranty flag remain 0x1 and most of countries it still voids warranty. Also after unrooting & relocking bootloader, some knox features never work again.
ROM Tool permission : Files & media - To save and read files, Calendar - Tool needs some time monitoring to avoid using RT immediately after reboot. Special access for accessibility service - Since Android 12 it requires for QS panel custom Toggl e.g. Reboot to recovery
Download : https://drketanrom.com/
ChangeLog for Magisk Module ROM
OneUI 4.0
Spoiler: ChangeLog OneUI 4.1
ChangeLog OneUI 4.1
- S01 - 12.03.2022
- S02 - 14.03.2022
- S03 - 19.03.2022 & S03.1 - 30.03.2022
- S04 - 06.04.2022
- S05 - 27.04.2022
- S06 - 27.05.2022
- S07 - 05.06.2022
- S08 - 18.06.2022
- S09 - 08.07.2022
- S10 - 05.08.2022
- S11 - 15.10.2022
OneUI 5.0
- T01 - 26.10.2022
- T02 - 19.11.2022
- T03 - 14.12.2022
- T04 - 15.01.2023
OneUI 5.1
- T05 - 17.02.2023
- T06 - 11.03.2023
- T07 - 14.04.2023
- T08 - 15.05.2023
- T09 - 20.06.2023
ChangeLog for Full System-RW ROM
OneUI 5.0
- T01 - 07.11.2022
- T02 - 20.11.2022
- T03 - 14.12.2022
- T04 - 17.01.2023
OneUI 5.1
- T05 - 17.02.2023
- T06 - 11.03.2023
- T07 - 11.04.2023
- T08 - 12.05.2023
- T09 - 21.06.2023
How to Root (currently non rooted device) with or without TWRP
Spoiler: Root existing non rooted device
Root with or Without TWRP
1.Root without TWRP :
Unlock Bootloader
You needs to download stock firmware (You can get stock firmware with Frija) and extract AP*.tar.md5 file and patch with magisk. Flash patched file with AP tab of Odin PS : In case root files without TWRP available in download area for your variant, you can use that for AP slot instead of Patching AP
put device in download mode and connect to PC and flash above files
Reboot to recovery and select to format data
Reboot to system → You will see Magisk stub in drawer → Update it. (In case stub not there, Donload magisk app from Download area and intall manually) → Open Magisk - It will ask to complete additionl setup, Let it do. → Reboot device. You are now ready to Intall Dr.Ketan ROM module. Move to next step.
2.Root with TWRP
Unlock Bootloader
Download TWRP, Patched vbmeta and Kernel and system-rw script zip from TWRP thread (Link below)
Select TWRP tar file with AP slot and Patched vbmeta for USERDATA slot of Odin PS : In case root files with TWRP available in download area for your variant, you can use that for AP slot. It contains both TWRP+patched vbmeta
Put device in download mode and connect to PC and flash above files
When Flashing completes, disconnect device and starightway reboot to TWRP
Run multidisabler from TWRP → Advanced → Terminal → and type : multidisabler (it may take few minutes, keep patience)
Wipe Data (Full wipe, that you needs to type YES to continue)
Reboot TWRP and now connect to PC and copy Custom kernel and flash from TWRP as zip
get Latest magisk apk and flash from TWRP
If you want to make system-rw, Get afaneh92_lp_rw_tool_v*.zip from TWRP thread and flash
Reboot device to system Update Magisk from stub if availble OR Install Magisk apk
Now ready to install Dr.Ketan Module, Follow XDA ROM Changelog post to install ROM Module
Thanks & Credit to Afaneh92 for TWRP & Kernel, below are link for OP Exynos and SnapDragon
PS : For detailed instructions about Magisk installation (root) read here. In case still you have question, move to Question forum of S22 section and ask for help. This thread is development thread and any questions related to how to root will be ignored.
How to Update Firmware and Keep root/twrp intact without losing data
PS : We highly recommend to make data backup before trying this as something went wrong and you may lose data.
Spoiler: Update Firmwre with Keeping Root/TWRP/data intact
Read below methods depending on you have root with or without TWRP
1.Rooted S908B/E/N/0 without TWRP
Unlock bootloader
You needs to download stock firmware you want to update (You can get stock firmware with Frija) and extract AP*.tar.md5 file and patch with magisk. Select Patched AP file for AP slot and BL*.tar.md5,CP_tar.md5,Home_CSC*tar.md5 for BL,CP and CSC slot accordingly. (PS : In case root files without TWRP available in download area for your variant, you can use that for AP slot instead of Patching AP, Importnt : Use Home_CSC*tar.md5 if you want to keep data. Selecting CSC*.tar.md5 will Wipe data autometiclly.)
Reboot device → You are now ready to Intall Dr.Ketan ROM module. Move to next step.
2.Rooted S908B/E/N/0 with TWRP
Download latest firmware as per pre-requisite
Disable Auto Reboot option in Odin
Select appropriate slot in Odin for BL,AP,CP and CSC (Using HOME_CSC will keep data, while using CSC* will format data) from stock firmware
Select TWRP file for USEDATA slot . File must include patched vbmeta file. If TWRP doesn't have patched vbmeta included, you have to make one yourself. To make TWRP+Patched vbmeta : Download both the files from TWRP thread and extract it to get recovery.img and vbmet.img. On your PC, select these two .img files and Rt click → select 7zip → Add to archieve → select archieve format "tar" → Select OK and this will create a tar file that have TWRP+Patched vbmeta. Use newly created tar file for Userdat slot of Odin. PS : Incase download area have Rootfiles with TWRP for your device then it contains everything TWRP+patched vbmeta + Kernel, extract zip to get all required files
When Flashing completes, disconnect device and starightway reboot to TWRP. Importnt : At this stage you should be quick to reboot to TWRP, If you flais and device tries to boot to system, you may have to wipe data.
Run multidisabler from TWRP → Advanced → Terminal → and type : multidisabler (it may take few minutes, keep patience)
Wipe Data (If you are already using Afaneh92's TWRP and used multidisabler + Format data, you can select to Factory Reset too (This will preserve media file) OR you can skip wipe option at all in case you want dirty Install.)
Reboot to TWRP In case you have wiped data.
Copy Kernel & Magisk apk/zip to device (Alternatively use USB storage)
Install kernel (Flash Kernel zip from TWRP)
Flash Magisk
If you want to make system-rw, Get afaneh92_lp_rw_tool_v*.zip from TWRP thread and flash
If you don't have magisk app in drawer (in case of clean install), Install manually.
Open Magisk app and complete setup if it asked for
PS : If you are on any other TWRP or Stock recovery, you must FORMAT DATA (That requires to type 'Yes' to confrm wipe)
Now ready to install Dr.Ketan Module, Follow XDA ROM Changelog post to install ROM Module
Thanks & Credit to Afaneh92 for TWRP & Kernel, below are link for OP Exynos and SnapDragon
PS : For detailed instructions about Magisk installation (root) read here. In case still you have question, move to Question forum of S22 section and ask for help. This thread is development thread and any questions related to how to root will be ignored.
Help & Support
We do support only ROM related queries here over XDA thread only, we do not have/encourage any private support over telegram or other media to support ROM related queries.
We do not answer any ROM related question over private chat.
If your queries doesn't have enough information, it will be ignored.
We recommend everyone to read OP,Changelog and Installation guide before you install ROM. If answer to your queries already there in OP, Changelog post or in Installation guide, it will be ignored
Any queries not reated to XDA ROM (e.g. TweaksPro) then you must seek help from developer over mail/privately. Here we discuss only XDA ROM related issue.
For reporting issue/bugs you must provide enough info as said below under "How to report bug/issue"
How to report bugs/Issue?
To report issue, you needs to provide following informations, else it will be ignored. Also if your query is already mentioned on OP/ChangeLogg post, it will be ignored.
1.ROM build number.
2.Dirty/Clean Install. - If you have dirty installed, Then first clean install and report if issue persists.
3.Bug/Issue appears right after installing or later?
4.How to reproduce error.
5.Is there any same reports there on thread on your searching?
6.Is there any mention about same bug on OP or changeLog post?
7.Logs - Attach logs here/Upload to other places where it can be downloaded without registration and doesn't have ad (we recommend dropbox/Gdrive) and post link.
Click to expand...
Click to collapse
Finally! After all the teasers and trailers ... We are getting into serious business !
THANK YOU
All the best and cheers Dr. !
ChangeLog S01
Based on S908EXXU1AVBF Android12 March 2022 security patch OneUI 4.1
ROM Tool on essential fix auto setup zygisk including SafetyNet fix (no needs to change any option manually)
Important Instructions for setting up ROM (NEW)
Prerequisite :
Must have installed firmware S908EXXU1AVBF S22 Ultra
Rooted device with Magisk (Zygisk) Intallled (Follow steps belo in case you have non rooted device)
How to Root device
Unlock bootloader
Download Root_files*.zip (available in download area) - Extract and Flash Root_Files_*.tar.md5 with Odin for AP tab
Reboot to recovery and select to format data (Factory reset option on stock recovery)
Reboot device → You will see Magisk stub in drawer → Update it. (In case stuf not there, Donload magisk app from Donload area and intall manually) → Open Magisk - It will ask to complete additionl setup, Let it do. → Reboot device. You are now ready to Intall Dr.Ketan ROM module. Move to next step.
How to Install Dr.Ketn ROM Module
Download DrKetan_ROM_S*_module.zip and copy to device, We recommend to check MD5 to rule out faulty download
Uninstall any other magisk module you have installed
Open Magisk app → Click on Module → Select Install from storage → Select Module file you have copied to device → Complete Intallation and reboot device
Setting up device first time after Module installation
Open ROM Tool, Apply essential fix and Reboot,
After reboot you can check SafetyNet and should be passed. You can use this app from playstore or This from Github to check SafetyNet
Now you can further setup ROM a per your liking. Also MagikHide is Configure Denylist now and available under Magisk Settings.
Since A12 Stable Magisk not working and new Magisk doesn't have buil-in Module repo, You can get standalone module manager from here For more details and queries about new magisk ref this
PS : Plz don't install any other mods for SafetyNet, All queries related to Magisk/SafetyNet will be ignored if already explained above
TweaksPro version requires 4.1.0 or up
ROM Features (XDA Version)
- Ad Free QS Panel Toggle
- Reboot to recovery QS Panel Toggle
- Native call recorder (Manual) While you are on call - click 3 dot - Record (Should work without CSC restriction)
- Auto Call recorder without CSC restriction (ROM Tool - Mods & Fix)
- High Volume warning disabled
- Pre fixed Titanium freezing while restoring apps
- Probable fix for Titanium Backup schedule
- Internet browser Secret mode
- S Health patch for using with rooted device.
- ROM Tool with following Options
AdFree mode Enable/Disable
Single click install/uninstall custom fonts (on the fly)
YouTube Vanced Installer (No xposed requires)
NonRoot - Requires MicroG to login
Root - Truely alternate to Youtube, Can login to youtube without MicroG (disable Play store update)
You have to click on NonRoot/Root depending on your choice, then you needs to click "Install" tab and latest version of Youtube vanced will get installed.
StatusBar Icons
Show/Hide stock battery
Show/Hide 3minit battery
show/hide stock clock
show/hide 3minit clock
ROM Control - See below
Mods & Fix
Auto Call Record
Titanium backup FC fix
Google Pay Fix
Added camera fix (Certain users reported camera failed issue. This is reported on stock too, here is someworkaroung meanwhile samsung fix it)
SafetyNet Fix
Samsung Health & Private share fix
Update & Fix
- ROM Control (systemUI preferences)
Battery Bar with thickness and color option
Virtual key on statusbar (Lt/Cinter/Rt)
Network meter with Toggle (Lt/Rt/Quick Panel/None) with color option
PS : There may be few more options in ROM control but won't work if those are not mentioned here.
Known Bug/Tips/Fix
3 minit users can use 3minit battery paid version for free. Check this (Thanks to gharrington )
Tips on TWRP and App Backup/Restore Read Here
Download : DrKetanROM.com
PS : This is a fully customized ROM and for end users only, ROM or any part of ROM not allowed to redistribute,modify or to use as base to prepare new ROM.
STATUS : Online
Haleluja, its here!! Great amazing work! OMG I'm so excited! Let's go!!
Thanks alot !!! Finally I can unpack my S22 Ultra ^^ and use it as real Phone
Proud to be the first worldwide to have a Custom ROM, FULL ROOT, Adblock etc on a S22 Ultra Exynos
Community LOVE for you!! ♥♥♥♥♥
EDIT: HERE IS THE GUIDE TO USE FOR EXYNOS (still testing)
Ok, so basically find and download the firmware (S908BXXU1AVC6 for EU - or ask me for the File..) to the phone eather with the Phone itself or trought USB-Cable, install magisk.apk from here, unpack the zip file from Firmware and patch the ap file via magisk, get the files to the pc and use odin to flash the patched Firmware.
of course unlock bootloader before and go to download mode.
Here is how to do that:
Guide to root Galaxy S22 Ultra (B/E/N/0), unlock bootloader and flash official firmware (noob friendly)
Your warranty is now void. If you root your device, Your KNOX status will be tripped. You can still pass the safety net after you root if you follow the instructions. Sorry for USA models, you can't root unless you can unlock your bootloader You...
forum.xda-developers.com
or
https://www.droidwin.com/how-to-unlock-bootloader-on-samsung-galaxy-s22-s22-plus-s22-ultra/
Then follow the other steps from Dr. Ketan
S01 Dr.Ketan Magisk ROM is Online now
Must read changelog above for Installation guide and other Info
Thank you for Support & Trust on this ROM.
no rom, only module
Yaiks. Hopefully it will be available for B variant
iampatricktan said:
Yaiks. Hopefully it will be available for B variant
Click to expand...
Click to collapse
You can try on exynos (only module, no root files). If it doesn't work then maximum you needs is to factory reset.
In that case I may consider to make separate rom
dr.ketan said:
You can try on exynos (only module, no root files). If it doesn't work then maximum you needs is to factory reset.
In that case I may consider to make separate rom
Click to expand...
Click to collapse
I think its much better to make separate only for Exnos variant? So that files for SD will not be included, correct me if I'm wrong about that. Also been using your ROM since my Note 9.
dr.ketan said:
S01 Dr.Ketan Magisk ROM is Online now
Must read changelog above for Installation guide and other Info
Thank you for Support & Trust on this ROM.
.
Click to expand...
Click to collapse
Huge thx my bro
ok, so great news, it works at least for exynos as well!
Safetynet also works!
Problems so far:
Can't change my keyboard - UI restarts
com.android.phone closes down
and it says system is unstable - please do a factory restore - on boot up.
But all in all it seems to work, with root etc.
Thx Dr My bro. Hopefully we can have the Exynos version seperatly if possible and not too much of your time consuming.
beautyangel said:
Thx Dr My bro. Hopefully we can have the Exynos version seperatly if possible and not too much of your time consuming.
Click to expand...
Click to collapse
||||| said:
ok, so great news, it works at least for exynos as well!
Safetynet also works!
Problems so far:
Can't change my keyboard - UI restarts
com.android.phone closes down
and it says system is unstable - please do a factory restore - on boot up.
But all in all it seems to work, with root etc.
Click to expand...
Click to collapse
Will do it later today
Any of you free just inbox me
For S908B EXYNOS Users
I have added Bootlogo error text removal file in Download area. Instructions packed inside.
PS : DON'T USE ON SNAPDRAGON device
.
A thousand thank yous @dr.ketan and to @||||| for your Exynos work
Just need delivery of my S22 from Sammy now
dr.ketan said:
For S908B EXYNOS Users
I have added Bootlogo error text removal file in Download area. Instructions packed inside.
PS : DON'T USE ON SNAPDRAGON device
Huge Huge thx Dr my Bro and @||||| for all Awesome job.
Click to expand...
Click to collapse

Categories

Resources