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.
Here are a few scripts I wrote for my device to boost up its performance. Few of them are written without being specific to any device or version of OS. For these general scripts (not specific to any device), download links are given at this first OP. For scripts which are specific to Redmi 3s, links are given at second post. These redmi 3s specific scripts install certain modified files such as service.jar and framework-res.apk.
All possible care has been taken to make general scripts work on all devices. Since I could check only on a few devices I could have access to, there could be a remote chance of not working on some devices. As devices vary on many accounts like OS version, customisation, configuration and file structure, for any eventuality, I recommend to take back up before proceeding with flashing of these zips.
Since the scripts are zipped in flashable zips, custom recovery (preferably TWRP) is must on your devices.
Here are general scripts with brief explanations.
1. Busybox installer zip: For various tweaks and init.d scripts to work properly, busybox is inevitable. This script installs Stericsons Busybox v1.24.2. If you have already busybox installed, no need of flashing this. Further flashing on the installed busybox may not harm.
Download Link: http://www.mediafire.com/file/s45tpufcy42h107/BusyBox-v1.24.2-Stericson.zip
2. Boot_patcher zip: This zip adds mount flags such as noatime, nodiratime, commit=60, nobarrier, noaudot_da_alloc, etc in fstab in boot.img and removes DM-verity. These flags have proved to increase IO on file systems. Many tweaks, I have noticed, put init.d script to remount partitions with these flags. But this zip does it directly at mount points at boot level obviating the need of init.d scripts.
Note: This zip is observed to break root enabled by Magisk. No need to worry. Just flash once again Magisk zip after flashing this zip. However, there is no problem of broken root if same is enabled by supersu.zip by chainfire.
Download Link:
http://www.mediafire.com/file/wshva78c456z1ub/boot_patcher.zip
3. Universal_journal_disabler zip: This zip makes journaling off on ext4 for system, data and cache partitions provided the partitions have been mounted on ext4 fs (if mounted on f2fs, it won’t touch those partitions). Journaling is a special control measure introduced from ext3 onwards. Journaling keeps track of changes made before writing on fs. This is useful in the scenarios of sudden power off or closure/crash due to any reasons for later restoration of changes made. This is not necessary on devices like mobile. But by default it is on. Since Journaling involves overhead on cpu, disabling the same is observed to improve performance considerably.
Note: Please flash this zip placing it on external memory, not on internal memory. Flashing from internal memory will not switch off journaling on data partition. So to ensure disabling journaling on data (which is essential for noticeable improvement), flash this zip placing it on external memory (external SD card) only.
Download Link:
http://www.mediafire.com/file/fmij6tnt8aebtyj/Universal_journal_disabler.zip
4. Permissive_selinux zip: In nougat custom roms, especially for Redmi 3s, selinux is enforcing. Enforcing selinux is seen to come in the way of many root apps though root enabled. One important issue I noticed that scripts at init.d folder were not running at boot due to enforcing selinux. Thus, I have made a small script to make selinux permissive on every boot by default. It takes care of file/folders created by supersu and magisk zip and accordingly puts the ‘setenforce 0’ in the appropriate folder.
Note: zip found not compatible with Magisk version 14
Download Link:
http://www.mediafire.com/file/qkimoscmfpu8x8a/permissive_selinux.zip
5. Ad_blocker zip: Nothing special about it. It just replaces hosts file in /etc folder for ad blocking. Important thing is about permissions assigned (rw_ r__ ___) for reducing impact of reading the big hosts file.
Download Link: http://www.mediafire.com/file/i50pr16umzp7h9q/ad_blocker.zip
6. Build_prop_patcher zip: This one has taken hell out of my time and patience. Not that it does any special thing, it simply inserts some build properties to build.prop file. But I wanted to make it such that it would search the intended build properties in build.prop file and changes the values thereof. If properties not found, inserts them at the end of file.
It is customisable zip. You can unzip and modify buildprop file according to your requirements. Special feature is it won’t add properties if present already with intended values. So, it is useful particularly to those who frequently flash roms with the result of losing added build.prop on every flash. Just flash this after flashing rom and have all your desired build.prop instantly.
Download Link: http://www.mediafire.com/file/c208fq98mixu9vx/build_prop_patcher.zip
7. Init.d script installer zip: I have collected some init.d scripts which I felt very essential and to implement on every device I have. Like build_prop_patcher zip mentioned above, herein also you can unzip the file and add your scripts to init.d folder therein, and make a permanent zip to flash every time you change your roms.
Note: For the scripts to work placed in init.d folder, you device should have been rooted and init.d enabled.
Download Link: http://www.mediafire.com/file/ot51sid37sfr0m8/initd_script_installer.zip
Credits:
@jcadduono for having heavily relied on his kernel flasher zip
@skynet28 for the method of journal disabling
Redmi 3s specifc
Here are Redmi 3s specific zips
1. Mm_rr_service_frmwrk_patch zip: This is meant for marshmallow resurrection remix rom as the modified service.jar and framework-res.apk used here for installation are from marshmallow resurrection remix rom. However, I think these modified files work on any marshmallow los based custom rom for redmi 3s.
In service.jar file, oom (out of memory) values for different categories of apps have been modified as below. As mentioned here, these oom values have resulted in turnaround of functioning of apps.
App category - old values - new values
Home ---------- 6 ---------- 0
Visible ---------- 1 ---------- 3
Previous ---------- 7 ---------- 5
Heavy ---------- 4 --------- 4
Service --------- 5 ---------- 6
Backup ---------- 3 ---------- 7
In all the custom roms, adaptive brightness is problematic, screen brightness is erratic on slight change in ambient light. So, I decompiled framework-res.apk, and changed autobrightness array values and found adaptive brightness afterwards comfortable.
Download Link:
http://www.mediafire.com/file/7y40j1x8dxp0bla/mm_rr_service_frmwrk_patch.zip
2. nougat_aex_frmwork_patch zips: Here also, I have modified services.jar and framework-res.apk files of nougat AEX roms. In services.jar, oom values have been modified as stated above, and in framework-res.apk also, autobrightness array values have been changed for smooth adaptation of screen brightness to ambient light. Since the services.jar and framework-res.apks used here are from AEX roms, zips are for AEX roms only. For each version of AEX rom (so far two versions, 4.5 and 4.6) for Redmi 3s, there is a separate zip which is to be flashed depending upon the version of AEX rom installed on your device.
For AEX v4.5
Download Link: http://www.mediafire.com/file/lxgd42fmfljxavv/nougat_aex45_svc_frmwork_patch.zip
For AEX v4.6
Download Link: http://www.mediafire.com/file/5bhawu1o226qdh3/nougat_aex46_svc_frmwork_patch.zip
3. nougat_rr_frmwork-res_patcher: This is for nougat resurrection remix roms. It also does the same thing of patching resources.arsc file in framework-res.apk for smooth adjustment of screen light to the ambient light.
Download Link: http://www.mediafire.com/file/luf4kslvttxss2d/nougat_rr_framework-res_patcher.zip
4. nougat_rr_svc_patch: This zip is for nougat resurrection remix roms. This installs patched services.jar with modified oom values as mentioned above (for the first zip in this post) for smooth functioning of apps.
Download Link: http://www.mediafire.com/file/61h9dz77zpxxuj9/nougat_rr_svc_patch.zip
5. adaptive_brightness_for_Oreo.zip: This is for overlaying the correct values of adaptive brightness in framework_res.apk for Oreo roms. Here, overlay feature of Oreo rom is being used instead of replacing modified framework_res.apk as done in the cases of zips for marshmallow and nougat roms above.
Download Link:http://www.mediafire.com/file/n77hsdvg9jx6pkp/adaptive_brightness_overlay.zip/file
6. persist_patch zip: This is for those who have corrupted persist files causing light, proximate and magnetic sensors not working.
Download Link:
http://www.mediafire.com/file/rrshneruhkdn8on/persist_patch.zip
Good work bro
Will it affect battery backup?
basiljose007 said:
Good work bro
Will it affect battery backup?
Click to expand...
Click to collapse
Definitely
shankar_vl said:
Definately
Click to expand...
Click to collapse
I mean positively or negatively? I prefer battery backup over higher performance, so asking
basiljose007 said:
I mean positively or negatively? I prefer battery backup over higher performance, so asking
Click to expand...
Click to collapse
both positively
Don't know if i will ever use these. But your hard work definitely deservers a vote of thanks.
Experience more battery life and a cooler phone on Samsung Galaxy note 3(All variants) with any kernel/custom kernel
Note: This tweak doesn't do what you like it does what you need
Disclaimer: I am not responsible for any damage or soft/hard brick that may happen to your device...please make sure you know what you are doing and follow the installation instructions below !
Installation 1 :
1) You must be rooted
2) Download the attached ZIP
3) Extract the script
4) Move file i.e(ondemand, Interactive, Conservative) depending on the one you downloaded to the following location;
/sbin/.core/img/.core/service.d and give it the following permissions (0755) or rwxr-xr-r using your root browser(explorer)
5) Reboot your phone, let Android boot to the launcher and let Magisk boot service do its crucial magic (takes about 60-65 seconds before the script is fully up and running behind the scenes)
6) Now logs can be found in the logs directory /storage/emulated/0/logs
7) Enjoy! :good:
For now:
Join telegram group here's the invite link https://t.me/tweakmypixel
Installation 2:
1) You must be rooted
2) Download the attached ZIP
3) Extract the script
4) Open and Grant the app root access and go the script manager of any kernel app of your choice(SmartPack kernel Manager,Franco Kernel manager FKM(paid),Ex kernel manager(Paid))
5) Then import the extracted script(.sh)
6) Run or Execute
7) You can check apply on boot if you want it to always run after boot.
8) Reboot your phone, let Android boot to the launcher and let Magisk boot service do its crucial magic (takes about 60-65 seconds before the script is fully up and running behind the scenes)
9) Now logs can be found in the logs directory /storage/emulated/0/logs
10) Enjoy! :good:
For now:
Join telegram group here's the invite link https://t.me/tweakmypixel
CPU GOVERNORS SUPPORTED
1) Ondemand:
Default governor in almost all stock kernels. One main goal of the ondemand governor is to switch to max frequency as soon as there is a CPU activity detected to ensure the responsiveness of the system.
2) Conservative:
A slower Ondemand which scales up slowly to save battery. The conservative governor is based on the ondemand governor. It functions like the Ondemand governor by dynamically adjusting frequencies based on processor utilization. However, the conservative governor increases and decreases CPU speed more gradually. Simply put, this governor increases the frequency step by step on CPU load and jumps to lowest frequency on CPU idle
3) Interactive:
Can be considered a faster ondemand. So more snappier, less battery. Interactive is designed for latency-sensitive, interactive workloads. Instead of sampling at every interval like ondemand, it determines how to scale up when CPU comes out of idle
Features
1) CPU Governors Optimized for better battery saving
2) Enabled dimmer blacklight to save battery
3) faster internet speed
4) Fstrim data,cache and system
5) Completely Stop and Disable performance daemon at boot
6) Killed GAPPS processes that drains battery
Code:
ChangeLog
12/3/2020
-Added Conservative
-Added Interactive
-Added Ondemand
22/3/2020
-Made noop default I/O scheduler based on users requests
FAQ
Q: Will these work without Root?
A: NO. you can use magisk or superSu to root your device
Q: Does this work for xyz kernel?
A: Works on xyz kernel just follow the installation Instructions
Q: What are the advantages of this?
A: Better battery life.
Q: How do i check if I have the scripts installed correctly?
A: Check the logs directory /storage/emulated/0/logs
XDA:DevDB Information
Kernel Tweaks, Tool/Utility for the Samsung Galaxy Note 3
Contributors
enweazudaniel
Source Code: https://www.androidfilehost.com/?w=files&flid=306333
Version Information
Status: Stable
Stable Release Date: 2020-03-13
Created 2020-03-12
Last Updated 2020-03-17
Reserved
I don't use a Samsung note 3 check ANY DEVICE
Reserved
Please guys test and post screenshots
Andriodfilehost link
https://www.androidfilehost.com/?w=files&flid=306333
@enweazudaniel. Please check your PM's. Thank you.
Fixed the source code link and duplication of the other 2 threads was due to server error and they have been closed now...enjoy guys :good:
Hi @enweazudaniel this looks like an amazing work but your instructions are not clear enough for me. In Installation 1 step # 4 you've said move file xxxx to path xxxx/services.d but services.d itself is a script, how do I copy one script into another. And if I open one script in txt editor copy all the txt, open the other script in txt editor and paste all the txt then won't that cause confilct with already present values resulting in stability issues?
In installation 2 I'm using smartpack kernel manager but I'm unable to find any import script options in it. Kindly help.
immi said:
Hi @enweazudaniel this looks like an amazing work but your instructions are not clear enough for me. In Installation 1 step # 4 you've said move file xxxx to path xxxx/services.d but services.d itself is a script, how do I copy one script into another. And if I open one script in txt editor copy all the txt, open the other script in txt editor and paste all the txt then won't that cause confilct with already present values resulting in stability issues?
In installation 2 I'm using smartpack kernel manager but I'm unable to find any import script options in it. Kindly help.
Click to expand...
Click to collapse
Maybe you're already using another mod that's why there a script there already and It might conflict if they are for similar purposes(like change a CPU parameter)...if you open in text editor and copy and paste as you said is not the advisable... So just use the script as standalone for best possible results for smart pack manager see the attachment
Hi. Will push works with gms tweaks in the script?
Demonzzz said:
Hi. Will push works with gms tweaks in the script?
Click to expand...
Click to collapse
Hello you can try and as well edit the script in case it doesn't work
Need extra SOT+ on any devices
Join group https://t.me/tweakmypixel