Related
HOW TO FIX PRIVATE MODE
NOTE: These instructions are for STOCK ROM using chainfire's system less cf-autoroot on the SPRINT GALAXY NOTE5 (SM-N920P). This might help for other Samsung devices but this is written for the mentioned model only. I TAKE NO RESPONSIBILITY FOR DAMAGE TO YOUR SOFTWARE, DEVICE, CAT, DOG, DRAGON, HOME, COUNTRY, PLANET OR SOLAR SYSTEM. USE AT YOUR OWN RISK.
1.) Install Xposed Framework (follow this thread: http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960 - use sdk22 arm64)
2.) Download module "Wanam Xposed for Android 5.x.x" - VERSION 1.3.0 OR NEWER
3.) Run Wanam Xposed and activate option Security hacks>Disable secure storage
4.) Using a file explorer that can access root with r/w permission, Delete the following folders:
Code:
- /data/data/com.samsung.android.personalpage.service
- /data/privatemode
- /data/system/secure_storage/com.samsung.android.personalpage.service
And delete the file:
Code:
/data/system/users/privatemode_edk_1000
5.) ACTIVATE THE WANAM XPOSED MODULE in Xposed
6.) Reboot
Private Mode should now work
How to Install Xposed framework WITH Top most Xposed Modules !
Please Read the Information Care fully !
Requirements for the Xposed Framework installation !
Device : Moto X Play XT1562 Indian (Duel Sim Mobile)
> Device Should be root enabled.
Note : Please do not aggressive and fast during installation, read all marked things carefully.
Top things to know: Your warranty will be completely lost during root method
Tips : Install Xposed framework with TWRP recovery (twrp-lux-3.0.2-r3.img)
TWRP can install temporary and permanently
fastbood.zip have some tested thing like.
> run (script) flash_permanent_recovery.bat for permanent install twrp recovery into moto x play.
> run (script) flash_temporary_recovery.bat for temporary bases ( this script will keep your original stock recovery)
Download: Download complete things on below google link.
>mail me on [email protected][/B][/COLOR]
[SIZE="5"]Video: I have not any video tutorial right now.[/SIZE]
> So Please find root method on google or YouTube.
>[COLOR="Teal"][B]or recommended link, mail me on [email protected][/B][/COLOR]
Modules List ( With Description )
1. Downloads2SD !
Info:
1. Your downloads with your desire location
2. Download modules into Xposed framework App.
2. GravityBox [MM] !
Info:
1. Enable some hidden tweaks Like:
2. Power Tweaks (Advance reboot menu, soft reboot, reboot confirmation, screen record).
3. Download modules into Xposed framework App.
4. Lock screen setting background style.
5. Replace your 4G symbol with LTE.
6. Heads Up Notification.
7. Ads More Tile into status bar (Quick Setting).
8. Battery Indication Setting.
9. Progress bar on your screen.
10. Data Traffic Monitor.
11. ( .etc ).
3. Greenify !
Info:
1. Save Your Battery with doze mode
2. Enable your working mode boost ( xposed framework required )
3. Some effective package required (donation package)
4. Deep Hibernation (Alpha)
5. Greenifiying systems apps
6. Download modules into Xposed framework App & Google Play Store
4. MinMinGuard !
Info:
1. Stop Adversiment as your want with particular apps.
2. Download modules into Xposed framework App.
5. One Tap Facebook Module !
Info:
1. Download Facebook Video with one tap (Very Effective & Help full).
2. This module work with your exiting Facebook App.
3. Download modules into Xposed framework App.
6. One Tap Youtube Module !
Info:
1. Download YouTube Video with one tap ( Very Effective & Help Full).
2. This Module works with your exiting YouTube App.
3. Download modules into Xposed framework App.
7. Xposed One Tap Video !
Info:
1. Important and have some useful setting for downloads.
2. Easily Available with Google Play Store.
3. Download modules into Xposed framework App.
8. YouTube AdAway !
Info:
1. Its stops all type advertisement during.
2. Modules works with Existing YouTube App.
3. Download modules into Xposed framework App.
9. YouTube Background Playback !
Info:
1. This will allow to play YouTube Video in background.
2. Modules works with Existing YouTube App.
3. Download modules into Xposed framework App.
When you're ready to post actual links, message me and I'll reopen this, but until then, thread closed.
I would first like to say that I cannot guarantee if this works on ALL devices. I was able to get this to work on the Galaxy S6 and posted it on the Galaxy S6 forums, however I am looking for people with other devices to see if it works for them as well (because why not share the bypass love to everyone ) If it works, please post a screenshot to confirm so I can post it on the thread here. Thanks.
(Please note that I am not responsible if your phone bricks etc. Please use at your own risk! Myself and others who have also tested this bypass have had no reported issues of this bypass causing some sort of brick etc., but I cannot guarantee anything.)
*This is a copy and paste of a thread I made on another forums and I felt like sharing it here. If there is any mistakes in the post, please tell me so I can fix it. Thanks.*__________________________________
Since October 2016, Google has (yet again) changed their way on how SafetyNet works and how they can now easily figure out if your phone is rooted or not. This caused many issues for rooted Android users who wanted to play games such as PKMNGO and use apps such as Snapchat. However, there is still ways to bypass SafetyNet.
Tested Devices:
- Samsung Galaxy S6
- Samsung Galaxy S5
*Looking for people with other devices to try and see if it works for themselves so I can add the device to the list.*
__________________________________
Requirements:
- Basic Understanding on how to use Custom Recovery, flashing zip files etc.
- Running on Android 6.0 (Looking for anyone with Android 7 to see if this works for them as well.)
- Phone has a custom recovery (I suggest TWRP) and on a Custom ROM. (Stock roms "should" work too.)
- Rom should have November 1st Security update or older updates. (Have not tested with roms with November 5th Security update and higher.)
- Magisk V10.2 & Magisk Manager 3.0
- SafetyNet Checker
- Phh Super User APK. PlayStore or 2.0 Beta
- Root File Explorer. I suggest Root Browser
- Kernel Adiutor
- Root Checker
(I have had issues trying Xposed on Magisk V9, however it may work on V10.2)
Tutorial
**WARNING: BIG IMAGES** (Had no time to resize them, but will soon.)
Before we begin, I suggest that you make a Nandroid backup through your preferred Custom Recovery. I suggest you use TWRP however CWM "should" work, but I have not tried myself.
Step 1:
Clean Install
The first step 'is' optional, however it is recommended that you do a clean install. I will be using Alexis Rom 8.0 Beta 2 for my Galaxy S6, but any rom should work. (Other than certain GraceUX ports, but am able to get it to work with other ported rom like CoreUi (a MIUI port) for the Galaxy S6). You should also flash a kernel now as well. I use to personally use Arter97 as SuperSU is not installed in this kernel, however Arter97 is slowly starting to become unstable as it hasn't been updated and there is better kernels out there. For this tutorial, I will be using Twisted Kernel.
Step 2:
Removing SuperSU
This step is 'also' optional, but ONLY if your rom/kernel does not automatically install SuperSU for you. In my case, it is automatically installed.
What you will need to do is to go to the SuperSU app, go to settings.
{
"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"
}
Scroll down until you see "Full unroot" and click it.
A popup will come up and click "Continue", then followed by another popup and click "NO".
Once you click no, your phone will freeze and then reboot. You should then install Root Checker to verify if your phone is unrooted.
(If for some reason, you are unable to use the SuperSU app but you know SuperSU is installed, I'd suggest you download UPDATE-unSU-signed.zip and flash it as it will manually remove SuperSU.)
Step 3:
Installing required APKs.
You will now need to install MagiskManager 3.0, SafetyNet Helper Sample, PHH Super User APK, Root Browser and Kernel Adiutor.
Step 4:
Flashing MagiskV10.2
You will need to reboot into your custom recovery and flash "Magisk-v10.2.zip", followed by rebooting. If you receive ERROR: 1 in TWRP when it is trying to mount SU, I suggest reflashing a kernel (and re-remove SuperSU), uninstalling Magisk with MagiskUninstaller (in Magisk thread) and reinstall Magisk V10.2, or reinstalling your rom.
Once you have flashed the file, reboot into System and open Magisk Manager to verify you have installed Magisk. A little pop up will open to allow Magisk to have root. Make sure to click allow and set it so it has root for "Forever".
If it states that root isn't properly installed, manually flash PHH Super User V266-2.
Step 5:
Enabling Magisk Hide
In Magisk Manager, go to the side menu and go to "Settings." You will see an unchecked box that says "Enable Magisk Hide." Select it and reboot. Re-open Magisk Manager and verify that it is now check marked. If the App crashes when you select "Enable Magisk Hide", reboot your phone and retry.
Step 6:
Set Permissions
In Root Browser, go to the directory "/sys/fs/selinux" and find the file "enforce" and the file "policy". On the file "enforce", change the permissions of the file from "644" to "640", and for the file "enforce", change the permissions of the file from "444" to "440". If Phh Super User pops up and asks for root access, click "Allow."
Once you are done, open up SafetyNet Helper Sample and it 'should' pass. If you are getting "Response Validation Failed" and the background is blue, uninstall Magisk by flashing Magisk Uninstaller, flash UPDATE-unSU-signed.zip, then reflash Magisk V10.2. Then, go back to Step 5 and enable Magisk Hide.
Step 7:
Use Kernel Adiutor to automatically set permissions in init.d
This last step is 'optional', however it automates the permission setting as every time you reboot your system, the file permissions will reset. Open up Kernel Adiutor, go to the sidebar and scroll down until you see 'Init.d'. Click it and make sure "Emulate Init.d" is enabled.
Then click the plus button, set the name to "Permissions" and then add the following script:
"chmod 640 /sys/fs/selinux/enforce" and "chmod 440 /sys/fs/selinux/policy" and save the files.
Also allow root access to Kernel Adiutor!
Step 8:
Reboot
Reboot your device, let Kernel Adiutor do its countdown (you will see in the notifications drop down) and once it says "Applying settings completed!", open up Safetynet and you should be passing!
Credits:
topjohnwu - Main developer of Magisk and Magisk Supported Phh Super User
This XDA thread - Helped me figure out how to do this bypass in the first place.
CoreUi Telegram Chat - Helped me test this bypass to see if it worked on different S6 models. Join here!
If I forgot to credit anyone, please tell me.
__________________________________
If there is any mistakes I made, spelling, phrasing etc., please tell me so I can fix it. Thanks.
Finally I can play again since they added the SafetyNet check! It's been way too long.
Worked perfectly on my Galaxy S5! I'm using the Resurrection Remix KLTE 6.0 for my Galaxy S5 so it came with it's own root. I just searched Root in settings, disabled it, flashed the unroot zip and then I was unrooted. Except for that everything worked the way you described! I forgot to reboot after Magisk Hide so I unrooted and reflashed Magisk but I'm not sure that was needed to be honest. Is SafetyNet Checker really needed? Magisk Manager also has a SafteyNet checker.
When I get more time I will do a backup and flash the 7.1.1 rom too and test if it works.
Complete package with everything needed in the guide for the lazy:
https://mega.nz/#!R18XRZQB!pgGx2LgNV8aqfwhsutmUnC4jay-FTGVR3-a9r3TJaEA
Martan404 said:
Finally I can play again since they added the SafetyNet check! It's been way too long.
Worked perfectly on my Galaxy S5! I'm using the Resurrection Remix KLTE 6.0 for my Galaxy S5 so it came with it's own root. I just searched Root in settings, disabled it, flashed the unroot zip and then I was unrooted. Except for that everything worked the way you described! I forgot to reboot after Magisk Hide so I unrooted and reflashed Magisk but I'm not sure that was needed to be honest. Is SafetyNet Checker really needed? Magisk Manager also has a SafteyNet checker.
When I get more time I will do a backup and flash the 7.1.1 rom too and test if it works.
Click to expand...
Click to collapse
There 'is' a Safetynet checker in Magisk Manager, however it will always say 'CTS Profile error', while SafetyNet Checker will say if its either a CTS error, Response Validation error, Play Store error etc. Maybe it's just a bug in Magisk Manager but if it gets fixed; I'll remove SafetyNet Checker from the tutorial.
xJovs said:
There 'is' a Safetynet checker in Magisk Manager, however it will always say 'CTS Profile error', while SafetyNet Checker will say if its either a CTS error, Response Validation error, Play Store error etc. Maybe it's just a bug in Magisk Manager but if it gets fixed; I'll remove SafetyNet Checker from the tutorial.
Click to expand...
Click to collapse
Can confirm that this works on 7.1.1 roms too! As I mentioned in my other post I use the Resurrection Remix rom.
By the way, you could mention that instead of using root browser to change permissions you could skip that step all together and just add the modification to Kernel Auditor. And instead of rebooting to test it you can just click the "Permissions" addition to execute the script right away just to make sure it works and then do a reboot to confirm.
Thank you so much. it worked
help plse plse give steps by step for 7.1.1(RR)
---------- Post added at 02:58 AM ---------- Previous post was at 02:54 AM ----------
i tried but cts profile mismatch becomes false
Sent from my MotoG3 using Tapatalk
Running a Mi Max here and have to say: Not working!
If i fully unroot the phone (magisk uninstaller / unSU script) then safety net helper gives me a red screen (CTS profile mismatch) but after installing Magisk 10.2 i only get a blueish screen in safetynethelper saying "response validation: fail"
naveenfre said:
help plse plse give steps by step for 7.1.1(RR)
---------- Post added at 02:58 AM ---------- Previous post was at 02:54 AM ----------
i tried but cts profile mismatch becomes false
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
1. Open the Settings app, and go About phone tab and spam click on Version to enable Developer Tools.
2. Do a search in the settings for "Root" and disable Root access.
3. Reboot to Recovery mode and flash this unroot https://forum.xda-developers.com/showpost.php?p=63615067
4. Reboot phone and follow xJovs' guide from step 3
Note: I also used the flashable zip file from the guide to get root and did not install the APK. https://forum.xda-developers.com/apps/magisk/magisk-phh-s-superuser-android-pay-t3435921
g_BonE said:
Running a Mi Max here and have to say: Not working!
If i fully unroot the phone (magisk uninstaller / unSU script) then safety net helper gives me a red screen (CTS profile mismatch) but after installing Magisk 10.2 i only get a blueish screen in safetynethelper saying "response validation: fail"
Click to expand...
Click to collapse
It might be because of the Kernel but I'm just speculating. Try flashing a new one to see if it helps!
g_BonE said:
Running a Mi Max here and have to say: Not working!
If i fully unroot the phone (magisk uninstaller / unSU script) then safety net helper gives me a red screen (CTS profile mismatch) but after installing Magisk 10.2 i only get a blueish screen in safetynethelper saying "response validation: fail"
Click to expand...
Click to collapse
It will always return blue right after installing Magisk. You need to follow through with the whole tutorial to work. If you have, then it's probably your rom. It happened with me on GraceUX roms.
Latest version of PoGo doesn't appear in magisk hide menu
It works
Thanks! Editing the permission of SElinux files works for me
Nexus 5X
GooglePixelROM v7.0.1
Android 7.1.2
NPG05D
Using Magisk 11.1
Now I can pass SafetyNet and use AndroidPay on a custom ROM
Galaxy Note 3 (N9005) MagmaNX with Magisk v11.1 + MagiskSU
CTS profile match: false
Basic Integrity: false
xJovs said:
I would first like to say that I cannot guarantee if this works on ALL devices. I was able to get this to work on the Galaxy S6 and posted it on the Galaxy S6 forums, however I am looking for people with other devices to see if it works for them as well (because why not share the bypass love to everyone ) If it works, please post a screenshot to confirm so I can post it on the thread here. Thanks.
(Please note that I am not responsible if your phone bricks etc. Please use at your own risk! Myself and others who have also tested this bypass have had no reported issues of this bypass causing some sort of brick etc., but I cannot guarantee anything.)
*This is a copy and paste of a thread I made on another forums and I felt like sharing it here. If there is any mistakes in the post, please tell me so I can fix it. Thanks.*__________________________________
Since October 2016, Google has (yet again) changed their way on how SafetyNet works and how they can now easily figure out if your phone is rooted or not. This caused many issues for rooted Android users who wanted to play games such as PKMNGO and use apps such as Snapchat. However, there is still ways to bypass SafetyNet.
Tested Devices:
- Samsung Galaxy S6
- Samsung Galaxy S5
*Looking for people with other devices to try and see if it works for themselves so I can add the device to the list.*
__________________________________
Requirements:
- Basic Understanding on how to use Custom Recovery, flashing zip files etc.
- Running on Android 6.0 (Looking for anyone with Android 7 to see if this works for them as well.)
- Phone has a custom recovery (I suggest TWRP) and on a Custom ROM. (Stock roms "should" work too.)
- Rom should have November 1st Security update or older updates. (Have not tested with roms with November 5th Security update and higher.)
- Magisk V10.2 & Magisk Manager 3.0
- SafetyNet Checker
- Phh Super User APK. PlayStore or 2.0 Beta
- Root File Explorer. I suggest Root Browser
- Kernel Adiutor
- Root Checker
(I have had issues trying Xposed on Magisk V9, however it may work on V10.2)
Tutorial
**WARNING: BIG IMAGES** (Had no time to resize them, but will soon.)
Before we begin, I suggest that you make a Nandroid backup through your preferred Custom Recovery. I suggest you use TWRP however CWM "should" work, but I have not tried myself.
Step 1:
Clean Install
The first step 'is' optional, however it is recommended that you do a clean install. I will be using Alexis Rom 8.0 Beta 2 for my Galaxy S6, but any rom should work. (Other than certain GraceUX ports, but am able to get it to work with other ported rom like CoreUi (a MIUI port) for the Galaxy S6). You should also flash a kernel now as well. I use to personally use Arter97 as SuperSU is not installed in this kernel, however Arter97 is slowly starting to become unstable as it hasn't been updated and there is better kernels out there. For this tutorial, I will be using Twisted Kernel.
Step 2:
Removing SuperSU
This step is 'also' optional, but ONLY if your rom/kernel does not automatically install SuperSU for you. In my case, it is automatically installed.
What you will need to do is to go to the SuperSU app, go to settings.
Scroll down until you see "Full unroot" and click it.
A popup will come up and click "Continue", then followed by another popup and click "NO".
Once you click no, your phone will freeze and then reboot. You should then install Root Checker to verify if your phone is unrooted.
(If for some reason, you are unable to use the SuperSU app but you know SuperSU is installed, I'd suggest you download UPDATE-unSU-signed.zip and flash it as it will manually remove SuperSU.)
Step 3:
Installing required APKs.
You will now need to install MagiskManager 3.0, SafetyNet Helper Sample, PHH Super User APK, Root Browser and Kernel Adiutor.
Step 4:
Flashing MagiskV10.2
You will need to reboot into your custom recovery and flash "Magisk-v10.2.zip", followed by rebooting. If you receive ERROR: 1 in TWRP when it is trying to mount SU, I suggest reflashing a kernel (and re-remove SuperSU), uninstalling Magisk with MagiskUninstaller (in Magisk thread) and reinstall Magisk V10.2, or reinstalling your rom.
Once you have flashed the file, reboot into System and open Magisk Manager to verify you have installed Magisk. A little pop up will open to allow Magisk to have root. Make sure to click allow and set it so it has root for "Forever".
If it states that root isn't properly installed, manually flash PHH Super User V266-2.
Step 5:
Enabling Magisk Hide
In Magisk Manager, go to the side menu and go to "Settings." You will see an unchecked box that says "Enable Magisk Hide." Select it and reboot. Re-open Magisk Manager and verify that it is now check marked. If the App crashes when you select "Enable Magisk Hide", reboot your phone and retry.
Step 6:
Set Permissions
In Root Browser, go to the directory "/sys/fs/selinux" and find the file "enforce" and the file "policy". On the file "enforce", change the permissions of the file from "644" to "640", and for the file "enforce", change the permissions of the file from "444" to "440". If Phh Super User pops up and asks for root access, click "Allow."
Once you are done, open up SafetyNet Helper Sample and it 'should' pass. If you are getting "Response Validation Failed" and the background is blue, uninstall Magisk by flashing Magisk Uninstaller, flash UPDATE-unSU-signed.zip, then reflash Magisk V10.2. Then, go back to Step 5 and enable Magisk Hide.
Step 7:
Use Kernel Adiutor to automatically set permissions in init.d
This last step is 'optional', however it automates the permission setting as every time you reboot your system, the file permissions will reset. Open up Kernel Adiutor, go to the sidebar and scroll down until you see 'Init.d'. Click it and make sure "Emulate Init.d" is enabled.
Then click the plus button, set the name to "Permissions" and then add the following script:
"chmod 640 /sys/fs/selinux/enforce" and "chmod 440 /sys/fs/selinux/policy" and save the files.
Also allow root access to Kernel Adiutor!
Step 8:
Reboot
Reboot your device, let Kernel Adiutor do its countdown (you will see in the notifications drop down) and once it says "Applying settings completed!", open up Safetynet and you should be passing!
Credits:
topjohnwu - Main developer of Magisk and Magisk Supported Phh Super User
This XDA thread - Helped me figure out how to do this bypass in the first place.
CoreUi Telegram Chat - Helped me test this bypass to see if it worked on different S6 models. Join here!
If I forgot to credit anyone, please tell me.
__________________________________
If there is any mistakes I made, spelling, phrasing etc., please tell me so I can fix it. Thanks.
Click to expand...
Click to collapse
i have HTC Desire 820 d820u running 6.0.1 mm stock.
is this will be ok to try?????
yo_honey said:
i have HTC Desire 820 d820u running 6.0.1 mm stock.
is this will be ok to try?????
Click to expand...
Click to collapse
Could but I have no idea.
I have tried latest magisk
xJovs said:
Could but I have no idea.
Click to expand...
Click to collapse
Here is full guide https://forum.xda-developers.com/desire-820/general/guide-bypass-safetynet-magisk-t3592508
Doesn't this work for Lollipop or is it just that you haven't tested?
xJovs said:
I would first like to say that I cannot guarantee if this works on ALL devices. I was able to get this to work on the Galaxy S6 and posted it on the Galaxy S6 forums, however I am looking for people with other devices to see if it works for them as well (because why not share the bypass love to everyone ) If it works, please post a screenshot to confirm so I can post it on the thread here. Thanks.
(Please note that I am not responsible if your phone bricks etc. Please use at your own risk! Myself and others who have also tested this bypass have had no reported issues of this bypass causing some sort of brick etc., but I cannot guarantee anything.)
*This is a copy and paste of a thread I made on another forums and I felt like sharing it here. If there is any mistakes in the post, please tell me so I can fix it. Thanks.*__________________________________
Since October 2016, Google has (yet again) changed their way on how SafetyNet works and how they can now easily figure out if your phone is rooted or not. This caused many issues for rooted Android users who wanted to play games such as PKMNGO and use apps such as Snapchat. However, there is still ways to bypass SafetyNet.
Tested Devices:
- Samsung Galaxy S6
- Samsung Galaxy S5
*Looking for people with other devices to try and see if it works for themselves so I can add the device to the list.*
__________________________________
Requirements:
- Basic Understanding on how to use Custom Recovery, flashing zip files etc.
- Running on Android 6.0 (Looking for anyone with Android 7 to see if this works for them as well.)
- Phone has a custom recovery (I suggest TWRP) and on a Custom ROM. (Stock roms "should" work too.)
- Rom should have November 1st Security update or older updates. (Have not tested with roms with November 5th Security update and higher.)
- Magisk V10.2 & Magisk Manager 3.0
- SafetyNet Checker
- Phh Super User APK. PlayStore or 2.0 Beta
- Root File Explorer. I suggest Root Browser
- Kernel Adiutor
- Root Checker
(I have had issues trying Xposed on Magisk V9, however it may work on V10.2)
Tutorial
**WARNING: BIG IMAGES** (Had no time to resize them, but will soon.)
Before we begin, I suggest that you make a Nandroid backup through your preferred Custom Recovery. I suggest you use TWRP however CWM "should" work, but I have not tried myself.
Step 1:
Clean Install
The first step 'is' optional, however it is recommended that you do a clean install. I will be using Alexis Rom 8.0 Beta 2 for my Galaxy S6, but any rom should work. (Other than certain GraceUX ports, but am able to get it to work with other ported rom like CoreUi (a MIUI port) for the Galaxy S6). You should also flash a kernel now as well. I use to personally use Arter97 as SuperSU is not installed in this kernel, however Arter97 is slowly starting to become unstable as it hasn't been updated and there is better kernels out there. For this tutorial, I will be using Twisted Kernel.
Step 2:
Removing SuperSU
This step is 'also' optional, but ONLY if your rom/kernel does not automatically install SuperSU for you. In my case, it is automatically installed.
What you will need to do is to go to the SuperSU app, go to settings.
Scroll down until you see "Full unroot" and click it.
A popup will come up and click "Continue", then followed by another popup and click "NO".
Once you click no, your phone will freeze and then reboot. You should then install Root Checker to verify if your phone is unrooted.
(If for some reason, you are unable to use the SuperSU app but you know SuperSU is installed, I'd suggest you download UPDATE-unSU-signed.zip and flash it as it will manually remove SuperSU.)
Step 3:
Installing required APKs.
You will now need to install MagiskManager 3.0, SafetyNet Helper Sample, PHH Super User APK, Root Browser and Kernel Adiutor.
Step 4:
Flashing MagiskV10.2
You will need to reboot into your custom recovery and flash "Magisk-v10.2.zip", followed by rebooting. If you receive ERROR: 1 in TWRP when it is trying to mount SU, I suggest reflashing a kernel (and re-remove SuperSU), uninstalling Magisk with MagiskUninstaller (in Magisk thread) and reinstall Magisk V10.2, or reinstalling your rom.
Once you have flashed the file, reboot into System and open Magisk Manager to verify you have installed Magisk. A little pop up will open to allow Magisk to have root. Make sure to click allow and set it so it has root for "Forever".
If it states that root isn't properly installed, manually flash PHH Super User V266-2.
Step 5:
Enabling Magisk Hide
In Magisk Manager, go to the side menu and go to "Settings." You will see an unchecked box that says "Enable Magisk Hide." Select it and reboot. Re-open Magisk Manager and verify that it is now check marked. If the App crashes when you select "Enable Magisk Hide", reboot your phone and retry.
Step 6:
Set Permissions
In Root Browser, go to the directory "/sys/fs/selinux" and find the file "enforce" and the file "policy". On the file "enforce", change the permissions of the file from "644" to "640", and for the file "enforce", change the permissions of the file from "444" to "440". If Phh Super User pops up and asks for root access, click "Allow."
Once you are done, open up SafetyNet Helper Sample and it 'should' pass. If you are getting "Response Validation Failed" and the background is blue, uninstall Magisk by flashing Magisk Uninstaller, flash UPDATE-unSU-signed.zip, then reflash Magisk V10.2. Then, go back to Step 5 and enable Magisk Hide.
Step 7:
Use Kernel Adiutor to automatically set permissions in init.d
This last step is 'optional', however it automates the permission setting as every time you reboot your system, the file permissions will reset. Open up Kernel Adiutor, go to the sidebar and scroll down until you see 'Init.d'. Click it and make sure "Emulate Init.d" is enabled.
Then click the plus button, set the name to "Permissions" and then add the following script:
"chmod 640 /sys/fs/selinux/enforce" and "chmod 440 /sys/fs/selinux/policy" and save the files.
Also allow root access to Kernel Adiutor!
Step 8:
Reboot
Reboot your device, let Kernel Adiutor do its countdown (you will see in the notifications drop down) and once it says "Applying settings completed!", open up Safetynet and you should be passing!
Credits:
topjohnwu - Main developer of Magisk and Magisk Supported Phh Super User
This XDA thread - Helped me figure out how to do this bypass in the first place.
CoreUi Telegram Chat - Helped me test this bypass to see if it worked on different S6 models. Join here!
If I forgot to credit anyone, please tell me.
__________________________________
If there is any mistakes I made, spelling, phrasing etc., please tell me so I can fix it. Thanks.
Click to expand...
Click to collapse
Step 6:
Set Permissions
In Root Browser, go to the directory "/sys/fs/selinux" and find the file "enforce" and the file "policy". On the file "enforce", change the permissions of the file from "644" to "640", and for the file "enforce", change the permissions of the file from "444" to "440". If Phh Super User pops up and asks for root access, click "Allow." Which file gets which perms bud you mention the same file twice.
savvy1968 said:
Step 6:
Set Permissions
In Root Browser, go to the directory "/sys/fs/selinux" and find the file "enforce" and the file "policy". On the file "enforce", change the permissions of the file from "644" to "640", and for the file "enforce", change the permissions of the file from "444" to "440". If Phh Super User pops up and asks for root access, click "Allow." Which file gets which perms bud you mention the same file twice.
Click to expand...
Click to collapse
Yeah I had to change it on my other thread in the GS6 forums. However I'm stopping maintenance of these threads as MagiskHide deals with all that permission stuff automatically now.
Seems to not working on leeco le max 2
Welcome to the official thread for Intex Cloud Tread.
You can discuss anything related to the phone here. (All links are Google Drive and XDA)
Make: INTEX
Model: Cloud Tread
Stock ROM: Android 5.1
Kernel: 3.10.72 (Remember this while looking for ROMs to port)
SOC: MT6591 (The same as MT6592, so you can easily port ROMs)
RECOVERY
Type: TWRP
Version: 3.2.1 EXPERIMENTAL
Kernel: 3.10.72
Supports: MT6591/MT6592
Download (Note: Old backups doesn't' work with this one.)
*Might have a couple of bugs (CPU Temperature doesn't work, ADB Backup doesn't work), but works for backups and restores and flashing and mounting and ADB Sideloads. This is an experimental build. Use with caution.
Type: TWRP
Version: 3.1.0
Kernel: 3.10.72
Supports: MT6591/MT6592
Download New Fixed Version Download (Note: Old backups doesn't' work with this one.)
OLD Version (This was a half-assed port from Excite Prime that Identifies device as Excite Prime and has a lot of other bugs)
Download OLD Version
Instructions:
1. Download and install SP Flash Tools
2. Start it and go to Download tab.
3. Now, in the scatter loading file box open the SCATTER Text you downloaded. (Link below)
4. Make sure the drop down box is selected at Download Only.
5. Untick all boxes except recovery and double click on the location part of the recovery row.
*DON'T PLUG YOUR PHONE IN NOW*
6. Select the recovery you downloaded from here and click the Download button.
7. Now turn the phone off or remove its battery and plug it in.
The necessary drivers should install and wait for a few seconds until a green tick or circle comes on the screen.
There, one custom recovery for INTEX Cloud Tread has been flashed.
SCATTER FILE - Download (You will need it to use with SP Flash Tool)
If you want the STOCK RECOVERY download it from here.
ROOT
Type: SuperSU
Download
Instructions:
1. Copy the file to your SD Card.
2. Press Volume Up+Power to boot into recovery when the phone is off.
3. There go to Install > Select Storage > MicroSD > SuperSU.zip.
4. Un-check Reboot Automatically. (This may clear the dalvik-cache which is recommended but not necessary and might take some time to boot up the first time.)
5. Then Swipe to flash and reboot.
Congratulations! You are now rooted without the annoying KingUser.
XPOSED
Installer: v89 sdk 22
Download
Uninstaller: Download
Instructions:
Flash XPOSED using the same method used to flash SuperSU above.
After flashing Clear Dalvik-cache (Option is on the same screen) and boot into android and install below APK to manage XPOSED
XPOSED APK v3.1.5
Uninstallation Instructions are also the same.
STOCK ROM - Download
Flash with SP Flash Tools.
After flashing stock ROM from the above link, untick all the boxes and tick only the boot image section.
Now download and select this boot image and flash.
This is because the boot image included in the above linked ROM has screen flickering issues.
Intex Cloud Tread Battery and Performance Optimization
First download and flash this "IntexDebloat.zip" file.
It will remove the bloatware that came with the phone. (User uninstallable apps are not included)
Intex Keypad (Which when automatically updates to Mox Keypad is a privacy nightmare) is also removed. Use Gboard or the stock AOSP keyboard in the phone.
Now make sure you are rooted and have xposed installed.
Install these below apps from playstore or apkmirror or from anywhere
1. Greenify
2. Kernel Adiutor
3. L Speed
4. Busybox
5. Powernap 0.7a (optional) (and don't download the newer versions or update from play store)
After installing all of the above follow these tutorials in order.
#BusyBox - Preparing the phone
Open busybox, grant SuperUser permissions and install it. Now you can uninstall the app if you don't need it.
#Kernel Adiutor - Custom Governor Tunings
Disabling MTK Performance Service
This is one of those situations where a good idea is implemented in a not so good way. Performance service can provide you good performance at a very dear cost of battery life and it can also override or worse play along and consume more power with the below tweaks. So you should disable it before attempting these.
Open Kernel Adiutor, grant su permissions and in the sidebar goto build prop tab
There search for ro.mtk_perfservice_support
Change its value from 1 to 0.
Now we are going to tune the Governor.
Believe me when I say this I've been tuning this phone for over two years now with 100s of different configurations and these are the two best configurations for a balance between power consumption and performance.
Option one: Hotplug with rush function and fast sampling rate (My favorite)
Open Kernel Adiutor > CPU tab.
Make sure the governor is set to Hotplug.
Now change the following Governor tunables;
Code:
cpu_down_avg_times=20
cpu_down_differential=1
cpu_input_boost_enable=0
cpu_rush_boost_enable=1
cpu_rush_threshold=98
down_differential=5
sampling_rate=30000
up_threshold=99
This should give you good performance while maintaining good battery life
Option 2: Hotplug with no rush and high sampling rate (This is also good for battery life but a bit low on performance)
Code:
cpu_down_avg_times=20
cpu_down_threshold=20
cpu_input_boost_enable=0
cpu_rush_boost_enable=0
cpu_up_threshold=90
down_differential=5
sampling_rate=73000
up_threshold=97
No matter what you choose your battery life is hugely dependent on what you choose to do with your device. I usually get 5h of *continuous* SOT on auto brightness with these settings on WiFi and browsing. YMMV.
Some people might suggest setting
ignore_nice_load=1 for more battey life as well. But this phone kinda categorizes everything as nice processes and will only run on 1-2 cores @728MHz if you enable that without MTK Performance Service. It did got me more than 7h SOT but it was basically unusable.
Make sure you enable apply on boot on each page you change to make it apply on each boot!
Now go to I/O Scheduler tab.
There change scheduler to noop for internal storage and sd card if you have one.
Also goto settings and change the apply on boot delay to instant.
#LSpeed, Paget96's masterpiece!
Open L Speed, finish the tutorial without enabling anything and do as follows
Sidebar > Main section
Disable Debugging: Enabled
Window Animation Scale: 0.5x
Transition Animation Scale: 0.5x
(Don't change animator duration scale as it will mess up every animations in the device)
CPU Tuner
Don't enable anything in here, we already tuned our governor with our own values in Kernel Adiutor.
Battery
Battery Improvement: Enabled
I/O Tweaks
SD Tweak: Enabled (If you have a SD Card)
I/O Boost: Enabled
Partition Remount: Enabled
Disable I/O stats: Enabled
Don't enable scheduler tuner as we choose noop in kernel adiutor which can't be tuned!
RAM Manager
You will be tempted to change a lot of things here but don't. It will only make it worse. Just change the below settings
Virtual Memory Tweaks: Battery
Cache Reclaiming: 50%
OOM Killer: Enabled
OOM Dump Tasks: Disabled
Also you can do a fstrim as well if you would like to. No probs.
Now go to settings and chage the apply on boot delay to instant.
#Greenify
Install greenify, enable the module in xposed installer and restart. After boot, make sure you wait till L Speed and Kernel Adiutor apply their settings.
Now open greenify, goto its settings, xposed based features and enable the below
Wakeup timer coalescing
Telephony Wakeup
Greenifying System apps
Now go back, select add apps and on the top right corner, select the three dot button and choose Show All.
Now add every app in the phone to greenify. (Don't worry greenify only hibernates app that consumes battery, those who don't consume battery in the background will be shown as background free.)
Don't add the following apps:
Bluetooth
MTK NLP Service
Phone
Phone (System)
Google play Services
Google Play Services (Persistent)
Voicecommand
Download manager
Calendar storage
Play store
Google account manager
com.mediatek.voiceextension
Google backup transport
Google calendar sync
Google contacts sync
Kernel Adiutor
L Speed
Prevent Pocket Dials
Click to expand...
Click to collapse
^These will start again and will consume more battery if you hibernate them.
#Power Nap (Optional)
Only install v0.7a (link above).
It's the basic stuff. Install, enable in xposed installer, open, enable the first option, add L Speed and Kernel Adiutor to it's whitelist. And reboot.
And that's it! Make sure you add any new app you install to greenify. Some say you don't need to hibernate everything, only the rogue apps. But Greenify itself can decide whether it should hibernate an app or not. So that's fine.
This took me a long time to write and more importantly this took me two years of experimentations to find. (Especially the governor tunings). Hope you guys enjoy it.
In addition to this I also recommend using Nova Launcher as the stock launcher is basically adware and follow the usual "don't install every crap-booster-cleaner-app you see" advice to maintain your device.
Device not revealed.
When I start MTK Droid tool, it says,"The device isn't revealed. Connect or reconnect a cable." I waited for like half an hour still the issue persists.
MTK Droid doesn't work that easily with phones newer than KitKat because of an incompatible adb. The solution is to manually replace the adb while MTK Droid Tools is running to make it work.
You can use this script I made that will automate the process and saves you the hassle.
https://forum.xda-developers.com/android/general/fix-impossible-to-start-adb-error-t3582571
Remember: Keep the phone connected with USB Debugging enabled before using the above script.
If it fails, try again it will work. :good:
Ritesh Sachan said:
When I start MTK Droid tool, it says,"The device isn't revealed. Connect or reconnect a cable." I waited for like half an hour still the issue persists.
Click to expand...
Click to collapse
Bump! :highfive:
Yes it did work, but on running mtk droid tools the icon on the bottom left corner shows yellow colour. So to fix that I clicked on the ROOT option next to the ADB Terminal option. I granted the access through my phone. Few seconds later the icon turns green for few milliseconds and it quickly turns into red colour saying "CONNECTION LOST." Even though my device was connected with USB Debugging ON. HELP ME.
You cant use MTKDroid to root the phone. Try with TWRP and SuperSu.zip
Now even after rooting MTKDroid will report that the phone is not rooted.
That's another security feature of Android. The adbd interface will work on non root mode even after rooting. You have to install adbd insecure apk (paid on google play, but available for free here on its XDA thread) by chainfire to change it to root mode.
Link to adbd - https://forum.xda-developers.com/showthread.php?t=1687590
Adithya FRK said:
Welcome to the official thread for Intex Cloud Tread.
You can discuss anything related to the phone here. (All links are Google Drive and XDA)
Make: INTEX
Model: Cloud Tread
Stock ROM: Android 5.1
Kernel: 3.10.72 (Remember this while looking for ROMs to port)
SOC: MT6591 (The same as MT6592, so you can easily port ROMs)
RECOVERY
Type: TWRP
Version: 3.1.0
Kernel: 3.10.72
Supports: MT6591/MT6592
Download
Instructions:
1. Download and install SP Flash Tools
2. Start it and go to Download tab.
3. Now, in the scatter loading file box open the SCATTER Text you downloaded. (Link below)
4. Make sure the drop down box is selected at Download Only.
5. Untick all boxes except recovery and double click on the location part of the recovery row.
*DON'T PLUG YOUR PHONE IN NOW*
6. Select the recovery you downloaded from here and click the Download button.
7. Now turn the phone off or remove its battery and plug it in.
The necessary drivers should install and wait for a few seconds until a green tick or circle comes on the screen.
There, one custom recovery for INTEX Cloud Tread has been flashed.
SCATTER FILE - Download (You will need it to use with SP Flash Tool)
If you want the STOCK RECOVERY download it from here.
ROOT
Type: SuperSU
Download
Instructions:
1. Copy the file to your SD Card.
2. Press Volume Up+Power to boot into recovery when the phone is off.
3. There go to Install > Select Storage > MicroSD > SuperSU.zip.
4. Un-check Reboot Automatically. (This may clear the dalvik-cache which is recommended but not necessary and might take some time to boot up the first time.)
5. Then Swipe to flash and reboot.
Congratulations! You are now rooted without the annoying KingUser.
XPOSED
Installer: v87 sdk 22
Download
Uninstaller: Download
Instructions:
Flash XPOSED using the same method used to flash SuperSU above.
After flashing Clear Dalvik-cache (Option is on the same screen) and boot into android and install below APK to manage XPOSED
XPOSED APK v3.1.1
Uninstallation Instructions are also the same.
Recommended and tested Mods:
Ultimate Performance MOD by sohamsen (Tweaks - Flashable with TWRP)
BootManager (XPOSED Module)
GravityBox [LP] (XPOSED Module) (Requires dalvik-cache to be cleared after changing settings to avoid SystemUI crash)
Zeus Contextual Expanded Status Header (XPOSED Module)(Requires dalvik-cache to be cleared after changing settings to avoid SystemUI crash.
Android O (Oreo) Boot Animation by -CALIBAN666-
I made a flashable ZIP here. In case you want the stock animation back, flash this.
If you did encounter a SystemUI crash after enabling some XPOSED module you can boot into twrp and Deleting the folder 'conf' from /data/dev.robv.android.xposed.installer to disable the XPOSED modules without uninstalling it altogether.
Thanks: rovo89 for XPOSED for Lollipop.
If this guide has been helpful for you, please hit thanks.
Click to expand...
Click to collapse
Awesome work Adithya ..have been looking for custom recovery for quiet long....and your twrp worked like a charm..Thankyou....just need to point u out that supersu link is not working....keep-up the good work,will be looking forward for new custom roms for intex cloud tread from u.
jackquest said:
Awesome work Adithya ..have been looking for custom recovery for quiet long....and your twrp worked like a charm..Thankyou....just need to point u out that supersu link is not working....keep-up the good work,will be looking forward for new custom roms for intex cloud tread from u.
Click to expand...
Click to collapse
Thanks for pointing that out. I will fix it as soon as possible. Also updated some extra info about the tweaks.
i have used this boot animation (Android O (Oreo) Boot Animation by -CALIBAN666- ) ....its working perfect...thanks ... if possible upload stock rom to flash with sp flash tools(in case if phone brick) . i have tried mtk tools to backup and your zip" [FIX] 'It is impossible to start ADB' or 'Phone not revealed' error in MTKDROID Tools" ... no success ...cannot get root in mtk tools though my phone is rooted.
That is a safety measure. Install adbd insecure to enable root interface.
jackquest said:
i have used this boot animation (Android O (Oreo) Boot Animation by -CALIBAN666- ) ....its working perfect...thanks ... if possible upload stock rom to flash with sp flash tools(in case if phone brick) . i have tried mtk tools to backup and your zip" [FIX] 'It is impossible to start ADB' or 'Phone not revealed' error in MTKDROID Tools" ... no success ...cannot get root in mtk tools though my phone is rooted.
Click to expand...
Click to collapse
Stock ROM link added.
Adithya FRK said:
That is a safety measure. Install adbd insecure to enable root interface.
Click to expand...
Click to collapse
after install [2014.11.10][ROOT] adbd Insecure v2.00 i got root access on mtk tools though weird its not showing my imei numbers its button is gray...block map create scatter is gray
when i hit backup its trying to store preloader and other files on phone then error no space on phone ...only 1 file on comuputer backup its system...any way i got that repair mobile stock rom before its posted ,was not sure if its tested and safe to flash if needed
Before doing anything, please do a readback using SP Flash Tools. The scatter file is in the #1 post.
EDIT: MTKDroid never worked for me too, apart from making the scatter file.
Adithya FRK said:
Before doing anything, please do a readback using SP Flash Tools. The scatter file is in the #1 post.
EDIT: MTKDroid never worked for me too, apart from making the scatter file.
Click to expand...
Click to collapse
Thanks for the advice ,got my readback using sp tools.
Just a suggestion, TWRP is extremely good with backups. If you just want the stock ROM, goto TWRP>Backup>Tick all except data and cache. The backup size should be around 1.6 GB.
Note: SuperSU and Boot animation are in the system partition so that will also be in the backup.
Adithya can u edit EBR files ..in our phone EBR 1 is too small ....i know the method ..though not a geek to do it.
hope this link will help u even getting new roms to intex cloud tread ....... http://www.droidgyan.com/development/
jackquest said:
Adithya can u edit EBR files ..in our phone EBR 1 is too small ....i know the method ..though not a geek to do it.
Click to expand...
Click to collapse
To be fair, I am not really a geek myself. I did this because I was so desperate to get a recovery.
The EBR records doesn't seem to be too small (I got 171 apps installed) and still says I can have more.
You should try SD Maid Pro it really is a great app to clean the remains if you are rooted, you might get more space that way.
Still, it's good to learn something new and might be useful in the future if you could share how to modify the partition size.
EDIT: I can't really work on my phone now. It's kind of my day to day phone.
just go to the link http://www.droidgyan.com/development/ everything /lots of information for MTK chipset.
Updated.
Warnings about powersave governor added. (Post #2)
Next post will be about saving battery without radically affecting performance using SetCPU.
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 RomSafetynet-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..