Related
There seems to be a lot of issues regarding the systemless root method. Here is some help/basic info.
Prerequisite:
1. Bootloader must be unlocked
2. Must have TWRP recovery installed
How to systemless root:
1. Download SuperSU v2.61 or SuperSU v2.62-3. Both work, I use the v2.62-3.
2. Flash either in TWRP recovery. Reboot to system. You now have systemless root.
Problems/Fixes:
1. Don't update SuperSU via the Play Store. I didn't have any luck updating this way (nothing but problems). If you want to update SuperSU/binaries, just download the current version SuperSU v2.71 and flash it in TWRP. As long as you previously flashed one of the SuperSU's listed in "How to systemless root", it will boot without issue.
2. One of your favorite root apps doesn't see that your rooted? Do THIS.
I update super su from the playstore without issues.
kadopt said:
I update super su from the playstore without issues.
Click to expand...
Click to collapse
Could you explain your process? I tried updating from the 2.61 and had issues.
gokart2 said:
Could you explain your process? I tried updating from the 2.61 and had issues.
Click to expand...
Click to collapse
Well, to get root (systemless) you flash super su 2.62-3 with twrp, then go to playstore and update super su app, open Super su and a pop up will indicate that your binaries need updating, press OK and wait until it's complete, then just reboot your device.
Good post. I see nothing but problems in here from people trying to flash some of the newer supersu zips and not booting due to it installing to /system.
I'd just like to add that you can start with whatever version supersu you want (as long as it is new enough to support systemless install - don't dig out 2.47 and expect it to work). You don't have to start with 2.62, but 2.62 is a good choice since it only installed systemless.
On unrooted, unmodified stock you just have to add a preference file to force supersu to install systemless. I find its easiest to do via adb in TWRP, but TWRP's built-in terminal would work too. It is one extra step before rooting, but if you're on unmodified stock then you probably just fastboot flashed TWRP so the PC and USB cable are already handy. Just enter:
Code:
echo "SYSTEMLESS=true" >> /data/.supersu
Once that's done you should be able to flash newer supersu zips. No need to start from 2.62. :good:
gokart2 said:
1. Don't update SuperSU via the Play Store. I didn't have any luck updating this way (nothing but problems). If you want to update SuperSU/binaries, just download the current version SuperSU v2.71 and flash it in TWRP. As long as you previously flashed one of the SuperSU's listed in "How to systemless root", it will boot without issue.
Click to expand...
Click to collapse
Where can one find this magical "How to systemless root" list of safe-to-flash systemless SuperSU?
And I assume only the BETA versions are systemless? I have tried flashing the latest STABLE v2.76 and it just stuck on boot.
The SuperSU v2.62-3 that you mentioned does work but just want to find the latest version to flash.
jason2678 said:
Good post. I see nothing but problems in here from people trying to flash some of the newer supersu zips and not booting due to it installing to /system.
I'd just like to add that you can start with whatever version supersu you want (as long as it is new enough to support systemless install - don't dig out 2.47 and expect it to work). You don't have to start with 2.62, but 2.62 is a good choice since it only installed systemless.
On unrooted, unmodified stock you just have to add a preference file to force supersu to install systemless. I find its easiest to do via adb in TWRP, but TWRP's built-in terminal would work too. It is one extra step before rooting, but if you're on unmodified stock then you probably just fastboot flashed TWRP so the PC and USB cable are already handy. Just enter:
Code:
echo "SYSTEMLESS=true" >> /data/.supersu
Once that's done you should be able to flash newer supersu zips. No need to start from 2.62. :good:
Click to expand...
Click to collapse
Adding the single line text file to /data worked for me to root stock 1575 18-4 with the latest Supersu 2.76 stable.
Making it very easy for everyone, here's my simple flash zip which force-installs any version of SuperSU (2.62 or newer) as systemless.
What the installer does:
1. Copies the "systemless" file to the /data partition.
The systemless file contains the following:
SYSTEMLESS=true
BINDSYSTEMXBIN=false
Click to expand...
Click to collapse
2. Renames the "systemless" file in /data to ".supersu" (as required in SuperSU's guide to overriding.)
3. Installs SuperSU as systemless, as the "systemless/.supersu" file forces it to.
The installer includes SuperSU 2.76. Read updater-script in the ZIP if Chainfire releases a new update and you want to update the zip with a newer version of SuperSU.
EDIT: Updated the installer to apply permission fixes to /su/bin for Android Pay compatibility after installation.
EDIT 2: Removed the /su/bin permission script since SuperSU 2.76 now applies it itself.
EDIT 3: Fixed the installer to look for the correct filename of SuperSU. Everything is perfect now.
Spasticdroid said:
Making it very easy for everyone, here's my simple flash zip which force-installs any version of SuperSU (2.62 or newer) as systemless.
What the installer does:
1. Copies the "systemless" file to the /data partition.
2. Renames the "systemless" file in /data to ".supersu" (as required in SuperSU's guide to overriding.)
3. Installs SuperSU as systemless, as the "systemless/.supersu" file forces it to.
The installer includes SuperSU 2.76. Read updater-script in the ZIP if Chainfire releases a new update and you want to update the zip with a newer version of SuperSU.
EDIT: Updated the installer to apply permission fixes to /su/bin for Android Pay compatibility after installation.
Click to expand...
Click to collapse
Thanks for the script. It should make it easier for someone to apply systemless root. FYI, supersu 2.76 defaults the /su/bin to 751 permission.
csrow said:
Thanks for the script. It should make it easier for someone to apply systemless root. FYI, supersu 2.76 defaults the /su/bin to 751 permission.
Click to expand...
Click to collapse
Yeah I'm hoping this will make it easier for those who are flashing SuperSU and ending up with an un-bootable phone due to the installer defaulting to system root in newer versions.
I've removed the permission script since I had no idea 2.76 now applies it. Thanks for the heads up!
Spasticdroid said:
Making it very easy for everyone, here's my simple flash zip which force-installs any version of SuperSU (2.62 or newer) as systemless.
What the installer does:
1. Copies the "systemless" file to the /data partition.
2. Renames the "systemless" file in /data to ".supersu" (as required in SuperSU's guide to overriding.)
3. Installs SuperSU as systemless, as the "systemless/.supersu" file forces it to.
The installer includes SuperSU 2.76. Read updater-script in the ZIP if Chainfire releases a new update and you want to update the zip with a newer version of SuperSU.
EDIT: Updated the installer to apply permission fixes to /su/bin for Android Pay compatibility after installation.
EDIT 2: Removed the /su/bin permission script since SuperSU 2.76 now applies it itself.
Click to expand...
Click to collapse
Flashed your script but SU wasn't installed. After that, I flashed SU 2.76 in TWRP and everything is as it should be. Android Pay also working.:good:
Edvin73 said:
Flashed your script but SU wasn't installed. After that, I flashed SU 2.76 in TWRP and everything is as it should be. Android Pay also working.:good:
Click to expand...
Click to collapse
Found the issue. The installer couldn't find the zip as I pointed it to a different file that wasn't there
("supersu-v2.76-20160630161323.zip" instead of "UPDATE-SuperSU-v2.76-20160630161323.zip". Thanks!
Spasticdroid said:
Found the issue. The installer couldn't find the zip as I pointed it to a different file that wasn't there
("supersu-v2.76-20160630161323.zip" instead of "UPDATE-SuperSU-v2.76-20160630161323.zip". Thanks!
Click to expand...
Click to collapse
Do you have changed this in the zip file? So if i download the zip it will Flash super user or do i have to Flash super su separate?
Sent from my XT1572 using XDA-Developers mobile app
Ijspegel said:
Do you have changed this in the zip file? So if i download the zip it will Flash super user or do i have to Flash super su separate?
Sent from my XT1572 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes, I have updated the zip to fix this and it will now find and flash it.
Spasticdroid said:
Yes, I have updated the zip to fix this and it will now find and flash it.
Click to expand...
Click to collapse
Thank you for your work on this one, it is very helpfull!?
Sent from my XT1572 using XDA-Developers mobile app
Spasticdroid said:
Making it very easy for everyone, here's my simple flash zip which force-installs any version of SuperSU (2.62 or newer) as systemless.
What the installer does:
1. Copies the "systemless" file to the /data partition.
2. Renames the "systemless" file in /data to ".supersu" (as required in SuperSU's guide to overriding.)
3. Installs SuperSU as systemless, as the "systemless/.supersu" file forces it to.
The installer includes SuperSU 2.76. Read updater-script in the ZIP if Chainfire releases a new update and you want to update the zip with a newer version of SuperSU.
EDIT: Updated the installer to apply permission fixes to /su/bin for Android Pay compatibility after installation.
EDIT 2: Removed the /su/bin permission script since SuperSU 2.76 now applies it itself.
EDIT 3: Fixed the installer to look for the correct filename of SuperSU. Everything is perfect now.
Click to expand...
Click to collapse
Thanks man, your script was the only thing that worked for me, but now wifi isn't working. what can I do?
Spasticdroid said:
Making it very easy for everyone, here's my simple flash zip which force-installs any version of SuperSU (2.62 or newer) as systemless.
What the installer does:
1. Copies the "systemless" file to the /data partition.
2. Renames the "systemless" file in /data to ".supersu" (as required in SuperSU's guide to overriding.)
3. Installs SuperSU as systemless, as the "systemless/.supersu" file forces it to.
The installer includes SuperSU 2.76. Read updater-script in the ZIP if Chainfire releases a new update and you want to update the zip with a newer version of SuperSU.
EDIT: Updated the installer to apply permission fixes to /su/bin for Android Pay compatibility after installation.
EDIT 2: Removed the /su/bin permission script since SuperSU 2.76 now applies it itself.
EDIT 3: Fixed the installer to look for the correct filename of SuperSU. Everything is perfect now.
Click to expand...
Click to collapse
OMG THANK YOU
I had accidentally installed the wrong SU and i thought I would have to wipe my entire device after hours of trying different methods. Yours was the only one that worked and my phone booted back on. Thank you so much.
Taking a risk of sounding stupid, will your SystemLess Root work for Android 7.0 Nougat?
Need help guys i flash super su v2.46 now on bootloop i have twrp install how do i get the newer supersu to flash to my phone . How and where would i downloqd it .
phillyguy /northeast said:
Need help guys i flash super su v2.46 now on bootloop i have twrp install how do i get the newer supersu to flash to my phone . How and where would i downloqd it .
Click to expand...
Click to collapse
Didn't we fix this in another thread?!?!
Hey guys
Is there any method working with the newest version of Pokemon GO to allow Oneplus One custom ROM users to play this game? The Internet is full of methods, I've already tried some but didn't work. Do you have any working idea for now?
Thanks in advance
Check your inbox.
But for all the other folks.
1. Install suhide http://forum.xda-developers.com/apps/supersu/suhide-t3450396 (via recovery)
2. Install root switch apk https://www.asus.com/zentalk/tw/for...wNDk1fGJmMjhjZGZifDE0NzY0MDUzNjB8MHwxNzM1NDI=
3. Start the root switch app and toggle the first switch off (this will "disable" your root).
4. Play the game
5. If your ready playing and you wanna use root again just toggle the switch back on in the root switch app.
Just search for magisk
Sent from my A0001 using XDA-Developers mobile app
massivekind said:
Check your inbox.
But for all the other folks.
1. Install suhide http://forum.xda-developers.com/apps/supersu/suhide-t3450396 (via recovery)
2. Install root switch apk https://www.asus.com/zentalk/tw/for...wNDk1fGJmMjhjZGZifDE0NzY0MDUzNjB8MHwxNzM1NDI=
3. Start the root switch app and toggle the first switch off (this will "disable" your root).
4. Play the game
5. If your ready playing and you wanna use root again just toggle the switch back on in the root switch app.
Click to expand...
Click to collapse
Do I need SuperSU installed? I like built in root in CM14.1
dasti555 said:
Do I need SuperSU installed? I like built in root in CM14.1
Click to expand...
Click to collapse
In the topic of suhide you can find the following
Requirements
- SuperSU v2.78 SR1 or newer (link)
- SuperSU installed in systemless mode
- Android 6.0 or newer
- TWRP (3.0.2 or newer, with access to /data - link!) or FlashFire (link)
So yes, you need supersu.
massivekind said:
In the topic of suhide you can find the following
Requirements
- SuperSU v2.78 SR1 or newer (link)
- SuperSU installed in systemless mode
- Android 6.0 or newer
- TWRP (3.0.2 or newer, with access to /data - link!) or FlashFire (link)
So yes, you need supersu.
Click to expand...
Click to collapse
- SuperSU installed in systemless mode
This mean normally flashed SuperSU.zip or I need to do something more?
Because I just flashed SuperSU SR4.zip and after that I wanted suhide0.55.zip and I can't "error 1 - check if you have atleast SR1 installed"
Can it be because of some kind of "november update"?
dasti555 said:
- SuperSU installed in systemless mode
This mean normally flashed SuperSU.zip or I need to do something more?
Because I just flashed SuperSU SR4.zip and after that I wanted suhide0.55.zip and I can't "error 1 - check if you have atleast SR1 installed"
Can it be because of some kind of "november update"?
Click to expand...
Click to collapse
You can just flash the zip
massivekind said:
You can just flash the zip
Click to expand...
Click to collapse
Too bad because I can't :/
Hi,i updated my Htc A9 device from Marshmallow stock rom to Nougat official rom.
My Device Info:
***UNLOCKED***
S-OFF
CID BS_US001
MID 2PQ912000
Os 2.18.617.10I decided to root my device but i have problem on that!!!
Step 1- installed twrp 3.1.1-0 by fastboot mode
Step 2-installed Magisk Manager and download magisk v 12.0 zip file from magisk manager.
Step 3-Reboot to twrp recovery and select (Swipe To Allow Modifictions),then i flashed Magisk v 12.zip file from install menu and after that reboot device.(recovery log)
Step 4-Run Magisk Manager and see this Status:
installed magisk ver 12.0 --->Iatest version magisk installed and Properly rooted--->8:MAGISKSU
(tpjohnwu)Pic 1.
Superuser show on Magisk manager menu(Pic 2) and apps send request for permission to #superuser(Pic 3).
On the surface everything is OK but i have problem,for example i installed Link2SD app to use that for uninstall system apps and freez apps but does not work properly & show error msg(Pic 4).
I would be honored if you tell me what is my problem,thanks...
Hi, did you install busybox? I'm not familiar with Magisk nor Link2SD, but I can imagine there's an option to "ignore systemless root" so you'll be able to make changes to the system partition.
Do other root apps have problems as well?
eavandijk83 said:
Hi, did you install busybox? I'm not familiar with Magisk nor Link2SD, but I can imagine there's an option to "ignore systemless root" so you'll be able to make changes to the system partition.
Do other root apps have problems as well?
Click to expand...
Click to collapse
I can't install busy box,when o clicked on install button,busy box closed!!!!
cowboy_ea said:
I can't install busy box,when o clicked on install button,busy box closed!!!!
Click to expand...
Click to collapse
I think you'll be better off if you install the latest LOS ROM (20170530) and flash SuperSU. I don't know about Magisk, but I've never experienced problems with SuperSU. Once rooted, install busybox from the playstore and install into "system/xbin/"
In SuperSU make sure you override LOS root settings since it's set to off by default. By the way, you can turn on LOS root settings manualy. That way you don't need Magisk or SuperSU at all. Settings can be unlocked by tapping the build number several times in settings-->Device status. A menu will be unlocked called Developers options. Within that menu you'll find the root settings.
Good luck
Oreo Root For The S7/S7E (Will work on Rev4-Rev10/A Bootloader) Adb Install
A big thanks goes out to @klabit87 he is 99 percent the reason we have root! Also @stang5litre and stang5litre test group.Prefered Root Method Oreo Only Using Odin Only For Rev-4 Too Rev10/A
Odin Install Root Method For S7 Flat Can Be Found Here
Odin Install Root Method For S7 Edge Can Be Found Here
Root Method Using Odin Only For Rev-11/B -- Please Read Limitations On The Thread
Rev11/B Root Method For S7 Flat Can Be Found Here
Rev11/B Root Method For S7 Edge Can Be Found Here
ADB Method Oreo Or Nougat For Rev-4 Too Rev10/A -- Must Use Adb Method For Nougat Root
2023_S7_Flat_Edge _ADB_Root_Plus_Safestrap_V1.7z
Directions:
This works for Oreo Rev4-Rev10/A Bootloader Roms or Nougat Rev4
As always there is a chance of bricking your phone
1. Download and extract 2022_S7_Edge_ADB_Root_Plus_Safestrap.7z
2. Reboot your phone to download mode
3. Inside the 2022_S7_Edge_ADB_Root_Plus_Safestrap.7z folder you will find an Odin_Firmware folder. Use Odin and flash the Eng Boot Image for your phone
4. Once phone is rebooted and connected to computer click on the cmd-here.exe and type Install_One_Click.cmd in the command window and hit enter
5. Once root is done and root bat closes your phone will reboot too stock recovery where you must wipe data
6. Once booted click on SuperSu app and update su binary if app ask then reboot
7. Don't flash any superuser zips in recovery that are not made by me or use any other SuperSu apk
Rebooting Too Safestrap Recovery
1. Reboot phone as you would too boot stock recovery Pwr + VolUp + Home. It takes up too 40 seconds too boot recovery. Ignore the mount system errors on info screen
2. Enter recovery.
3. Too leave just reboot system ignore no system installed message if you get it
4. There is screen lag issues on scrolling in recovery. There is aroma file manager that takes care of this issue while in recovery but selecting zips too install may present a problem for this you can use the kernel manager recovery flash option while phone is booted too system. Simply select zip too flash and phone will reboot too recovery and flash it and reboot back too system. Most other function in recovery should work the issue is just scrolling too select files.
5. Flashfire is installed as an alternative as well
Features:
1. SuperSu Root- Do not use any other SuperSu app. Its ok to update su binary if app ask.
2. Safetrap recovery-Still working out scrolling issue
3. Flashfire
4. Kernel tweaks CPU governor set too Conservative
5. Entropy/Swapiness set to High
6. Build Prop tweaks to combat lag
7. Bloat removed from rom
8. Knox removed from rom
Bugs:
Eng Boot Image causes lag
Safestrap Recovery has scrolling issues
Random Reboots will most likely happen
Safetynet will not pass
Battery life may not be optimal
SuperSu cannot be updated
Flashfire may need date changed too 2016 to function if it just keeps closing on you
Volte And Hotspot Fix
View attachment OREO_VOLTE_ICON_HOTSPOT_FIX.zip
Old Downloads
S7_Oreo_Nougat_Adb_Advanced_Root_V12.zip Recommended Root Zip
This zip gives you the option to install some cpu tweaks and will also. Install the entropy tweak that the SEFix app does. The tweak sets entropy to high by default I also include the SEFix app if you want to change the settings. I also set the swappiness settings to very high. If you want to change these settings you can download the speedup swap app from playstore. The above zip also removes knox and changes the fstab.qcom file to disable dm-verity on system files and remove all file encryption which makes it seem to work better and make it compatible with my no root roms that has to have this done to allow safestrap to work. Installing the above zip requires a data wipe unless you have already installed it or you are coming from my non rooted roms
S7_Oreo_Su_Binary_Only_ADB_Root.zip Alternative Root Zip
This root zip is only for oreo an only installs the su binary to the system/xbin folder giving you root privelages it has no tweaks and does not change the fstab.qcomn file to remove dm-verity and system file encryption. There is no SuperSU app installed either but you will have root privelages.
Credits:
- @Raymonf for modified odin
- @afaneh92 for safestrap
- @me2151 for help and finding alternative flash methods
- @tytydraco for some instructions
- @mweinbach for some instructions
- @Craz Basics for help
- @partcyborg for help and guides other devices root methods
- @elliwigy for being great help when I need it
- @stang5litre
- @jds3118
- @Krog18
If I missed you please pm me
Donations
If you would like to donate please send all donations to @klabit87 PayPal Link Here and give a thanks!
It's awesome to see yet ANOTHER post by you! You're doing great. Looking forward to future development
Nice, hopefully I will update to Oreo on e @stang5litre does a new rom for us. Once again thanks @klabit87 and you also
Sent from my SM-G935V using Tapatalk
I've selected "1 - Yes SafeStrap is Install" in :MENU5 phone reboted to SafeStrap how to exit? It is always rebooting to safestrap back.
Note: After I selected that menu console fast closed and I noticed some error.
abyss7 said:
I've selected "1 - Yes SafeStrap is Install" in :MENU5 phone reboted to SafeStrap how to exit? It is always rebooting to safestrap back.
Note: After I selected that menu console fast closed and I noticed some error.
Click to expand...
Click to collapse
Wow sorry about that I had script wrong. You cant really enter safestrap can you?
Edit:
redownload zip from OP its fixed. As far as you not being able to boot flash the BL enter_safetrap file then enter safestrap then mount system use file manage and delete e2fsck from system/bin folder then rename e2fsck.bin to e2fsck then reboot to download and Flash BL file in BL slot And the Eng boot loader in the AP slot
jrkruse said:
Wow sorry about that I had script wrong. You cant really enter safestrap can you?
Click to expand...
Click to collapse
On the contrary, I cannot exit from safestrap, it enters always after reboot. Sometimes screen contain small image of original loockscreen, it looks like split view.
Nice!! Is this the binary you wrote and how did you get the script to fire off??
abyss7 said:
On the contrary, I cannot exit from safestrap, it enters always after reboot. Sometimes screen contain small image of original loockscreen, it looks like split view.
Click to expand...
Click to collapse
follow my above directions
Craz Basics said:
Nice!! Is this the binary you wrote and how did you get the script to fire off??
Click to expand...
Click to collapse
@klabit87 found a way to hook in a script at boot so normal root works
jrkruse;77136767 [user=4168602 said:
@klabit87[/user] found a way to hook in a script at boot so normal root works
Click to expand...
Click to collapse
Normal root as in SuperSU?? And hats off to you @klabit87
abyss7 said:
On the contrary, I cannot exit from safestrap, it enters always after reboot. Sometimes screen contain small image of original loockscreen, it looks like split view.
Click to expand...
Click to collapse
jrkruse said:
Wow sorry about that I had script wrong. You cant really enter safestrap can you?
Edit:
redownload zip from OP its fixed. As far as you not being able to boot flash the BL enter_safetrap file then enter safestrap then mount system use file manage and delete e2fsck from system/bin folder then rename e2fsck.bin to e2fsck then reboot to download and Flash BL file in BL slot And the Eng boot loader in the AP slot
Click to expand...
Click to collapse
Follow these instructions
V2 zip is posted in OP that fixed the safestrap issue
Craz Basics said:
Normal root as in SuperSU?? And hats off to you @klabit87
Click to expand...
Click to collapse
Yes normal supersu
jrkruse said:
Yes normal supersu
Click to expand...
Click to collapse
I didn't think SuperSU supported Oreo?
@jrkruse, will it work with your CRF1 hybrid?
TheDevelopper said:
@jrkruse, will it work with your CRF1 hybrid?
Click to expand...
Click to collapse
Yes make sure you download V2 zip file from the OP
Craz Basics said:
I didn't think SuperSU supported Oreo?
Click to expand...
Click to collapse
It does 8.0 not 8.1
@jrkruse, there are two different Eng.boot for G935, which one should I choose? The 21.92MB or the 22.07MB?
Added a Volte Icon and Hotspot fix zip to OP
TheDevelopper said:
@jrkruse, there are two different Eng.boot for G935, which one should I choose? The 21.92MB or the 22.07MB?
Click to expand...
Click to collapse
Read what they say it tells you one is for OREO and one is for NOUGAT
hello xda,
This tutorial shows you that how to make your device fully functional with root.
but most of the peoples question is to pass SafetyNet, make their device status "Official" and also to work with Private Mode after root and with custom kernel. And here is the answer ,
BEFORE BEGIN, BACKUP YOUR DATA AND DOWNLOAD CORRECT FILES. I AM NOT RESPONSIBLE FOR ANY DAMAGE CAUSE TO YOUR DEVICE BY THIS PROCEDURE!!!
1. Download and flash stock oreo firmware via ODIN.
2. After boot, Turn on developer mode and turn on OEM Unlock.
3. turn off your device and get in to download mode.
4. Flash latest TWRP recovery via ODIN.
6. Get in to twrp recovery and format data and again boot into twrp.
7. first flash "no-verity-opt-encrypt-6.0", secondly flash "latest magisk", thirdly flash "TGP kernel v6.8.0".
8. After boot, update magisk app itself ( Latest v17.1 ).
9. download and install any root browser app ( root explorer recommanded) and give the root permission.
10. Navigate to /system/priv-app/PersonalPageService and delete the apk file and replace with modified apk
( Do not forget to set correct permission "rw-r-r" or chmod 644).
11. Navigate to /system/app/sysscope and delete the apk file and replace with modified apk
( Do not forget to set correct permission "rw-r-r" or chmod 644).
12. Reboot the device.
13. Now you can check SafetyNet, System Status and private mode.
NOTE :
DO NOT ATTEMPT TO INSTALL SYSTEM UPDATE. BECAUSE YOU MAY HAVE INSTALLED CUSTOM RECOVERY. SO THE UPDATE WILL PROBABLY FAIL.
YOU CAN OBTAIN UPDATE PACKAGE AT "/data/fota".
YOU CAN ALSO RIDE WITH BANKING APPS AND OTHER APPS WITH ROOT.
CAUTION :
●DO NOT FLASH CF SU.
●DO NOT ATTEMPT TO FLASH SYSTEM UPDATE.
●DO NOT INSTALL XPOSED FRAMEWORK. THIS WILL TRIGGER SAFETYNET.
KNOWN BUGS : NOTHING YET. TESTED ON GALAXY S7 (EXYNOS).
Files
( sysscope, PersonalPageService ) : https://drive.google.com/folderview?id=1ekOXMNMYGhaMke58y_xkVMFiAvP-Ncpm
no-verity-opt-encrypt-6.0 :
https://androidfilehost.com/?fid=817906626617949632
TGP Kernel v6.8.0 :
https://androidfilehost.com/?fid=1322778262903992351
Systemless magisk :
https://www.google.lk/amp/s/forum.x...-magisk-v7-universal-systemless-t3473445/amp/
second method:
Download (e.g. with SamFirm (v0.3.6)) and flash stock oreo firmware via Odin
After boot, Turn on developer mode and turn on OEM Unlock.
Turn off your device and get in to download mode.
Flash latest TWRP recovery via ODIN.
Get in to twrp recovery and format data and again boot into twrp.
First flash "no-verity-opt-encrypt-6.0", secondly flash "latest magisk"
After boot install latest magisk manager
In magisk manager install the module Xposed Framework (SDK 26) systemless
Install XposedInstaller_3.1.5-Magisk from https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
In XposedInstaller-App install Firefds Kit [Oreo]
Start Firefds Kit [Oreo] and enable in Security hack "Fake system status"
Now the system status is official and you can download the OTA-Update.
To get ctsProfile: true and basicIntegrity: true you have to deactivate Xposed in the XposedInstaller-App (disable Xposed Status) and disable the module in magisk manager
But the interessting question would be how to install OTA updates without loosing root.
Because, if you go in the xposed method, It will probably trigger SafetyNet. So you couldn't be able to ride with updates, banking apps and etc.
This is why I placed modified Sysscope in order to make official.
And yes, stock private mode checks for custom binary or custom kernel. So the best way to modify the apk to work with custom binary.
Unfortunately, you cannot be able to install system updates via recovery. But, you can extract the fota.zip and place those files manually at your own risk. But I recommend you not to do.
DO NOT INSTALL XPOSED. IT WILL TRIGGER SAFETYNET. EVEN THOU SYSTEMLESS METHOD WOULDN'T HELP.
What should I do to get root again after the OTA?
Reflash magisk to regain root access
Are there any news to this topic?