Database Develop

Systemless root (Android 6.0) - Method for easy future OTA updates

I am looking for an easy way to be able to receive OTA updates after rooting with the 'systemless' root method, the steps I mention below assume that the system partition remains untouched after rooting. I have searched and not found a clear answer on this.
Would I be correct in assuming that this procedure should work to receive an OTA update and keep stock recovery after rooting?
Start with completely stock Android 6.0
fastboot boot twrp-recovery.img (boot TWRP, NOT flash, to maintain stock recovery after rooting)
Flash systemless root with TWRP
OTA arrives (Android 6.0.1 for example)
fastboot flash boot boot.img (with stock 6.0 kernel, root lost)
Accept & install OTA update
Success?
So unless I am missing something, this method would leave the system in a stock, unrooted state after the OTA is installed, and could be repeated for future updates. Anybody have any experience with this yet?

Sounds like it will work, but why mess with the ota? More work and risk honestly.
Since you're already using fastboot just flash the newest boot and system.img. Then flash/boot twrp and flash su like you'd need to do anyway. Done. You don't lose anything flashing system.

yosmokinman said:
Sounds like it will work, but why mess with the ota? More work and risk honestly.
Since you're already using fastboot just flash the newest boot and system.img. Then flash/boot twrp and flash su like you'd need to do anyway. Done. You don't lose anything flashing system.
Click to expand...
Click to collapse
That is true, kind of just wondering/gathering information. It just seemed like with the new root method, OTA would be possible and less risky than before.
Sent from my MotoG3 using Tapatalk

@quakeaz there is one step missing on your guide. After boot.img you also have to flash stock recovery.img. From Lollipop, Google is also checking installed recovery, and for successful OTA, it has to be stock as well.
Otherwise, your guide should work, I've done same thing with my Nexus 5 and 7 for like last 3 months.

Srandista said:
@quakeaz there is one step missing on your guide. After boot.img you also have to flash stock recovery.img. From Lollipop, Google is also checking installed recovery, and for successful OTA, it has to be stock as well.
Otherwise, your guide should work, I've done same thing with my Nexus 5 and 7 for like last 3 months.
Click to expand...
Click to collapse
Thanks for your reply, but I intentionally left that step out, due to step 2 in my list. By only booting TWRP, instead of flashing, I assume stock recovery will remain after rooting.
Sent from my MotoG3 using Tapatalk

quakeaz said:
Thanks for your reply, but I intentionally left that step out, due to step 2 in my list. By only booting TWRP, instead of flashing, I assume stock recovery will remain after rooting.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Ah, sorry, I overlooked that.
Since I have flashed TWRP instead of stock recovery, I'm going by same process as you write, just reflash stock recovery. And can confirm, that the process is indeed working (no need to install system.img, as with previous system-based SuperSU).

Sounds good!
Sent from my MotoG3 using Tapatalk

quakeaz said:
I am looking for an easy way to be able to receive OTA updates after rooting with the 'systemless' root method, the steps I mention below assume that the system partition remains untouched after rooting. I have searched and not found a clear answer on this.
Would I be correct in assuming that this procedure should work to receive an OTA update and keep stock recovery after rooting?
Start with completely stock Android 6.0
fastboot boot twrp-recovery.img (boot TWRP, NOT flash, to maintain stock recovery after rooting)
Flash systemless root with TWRP
OTA arrives (Android 6.0.1 for example)
fastboot flash boot boot.img (with stock 6.0 kernel, root lost)
Accept & install OTA update
Success?
So unless I am missing something, this method would leave the system in a stock, unrooted state after the OTA is installed, and could be repeated for future updates. Anybody have any experience with this yet?
Click to expand...
Click to collapse
Instead of fastboot flashing boot.img, you can use "Settings --> Full Unroot" in SuperSU. During SuperSU systemless flash, your old boot image is backed up. Among other things, the full unroot option will restore the backup, assuming it hasn't been lost due to a factory reset and whatnot.
On many firmwares, this procedure also restores stock recovery. This requires that both the firmware supports recreating the recovery from the boot image plus a patch file (most do), and that TWRP did not remove said patch file (which some versions do).
That being said, if you're using fastboot anyway, flashing boot, recovery, system and vendor manually is always the safest thing before an OTA.

Thanks for the info. So I take it while using systemless root, installing ota without unrooting is a big nono? The January ota just downloaded and is asking me to install, should I do it manually?

Chainfire said:
Instead of fastboot flashing boot.img, you can use "Settings --> Full Unroot" in SuperSU. During SuperSU systemless flash, your old boot image is backed up. Among other things, the full unroot option will restore the backup, assuming it hasn't been lost due to a factory reset and whatnot.
On many firmwares, this procedure also restores stock recovery. This requires that both the firmware supports recreating the recovery from the boot image plus a patch file (most do), and that TWRP did not remove said patch file (which some versions do).
That being said, if you're using fastboot anyway, flashing boot, recovery, system and vendor manually is always the safest thing before an OTA.
Click to expand...
Click to collapse
Thank you for this thread and the procedure. I tried myself to avoid as much as possible to use a computer for super easy OTA update. But there is always one obligatory step: to root the phone.
Phone systemless rooted (2.66) - TWRP installed - OTA arrives.
In SuperSu app : Fully unroot
Install OTA - success
Fastboot boot (or install) TWRP
Flash superSu 2.66.zip
And that's it!
My question is the following: Does it exist a possibility to load on step 3. something that could flash superSu.zip from within the phone, no computer required?
Maybe FlashFire? I guess not, for it needs root and the point is to flash a rooting zip... You see the loop there...
Would it be theoreticaly possible at all?

Judim said:
Maybe FlashFire? I guess not, for it needs root and the point is to flash a rooting zip... You see the loop there...
Would it be theoreticaly possible at all?
Click to expand...
Click to collapse
Yes, this is one of the use-cases of FlashFire. I just haven't finished updating it to 6.0 yet.

Oh nice!
I didn't know it cause I never had the chance to try out FlashFire.
Thanks so much for everything you do for the Android community!
Cheers!

Srandista said:
Ah, sorry, I overlooked that.
Since I have flashed TWRP instead of stock recovery, I'm going by same process as you write, just reflash stock recovery. And can confirm, that the process is indeed working (no need to install system.img, as with previous system-based SuperSU).
Click to expand...
Click to collapse
mine fail here. i previously got systemless root 2.62, blu spark kernel and twrp. fastboot flash stock boot and recovery. reboot to update and it fail. any idea why?

ShanxRoux said:
mine fail here. i previously got systemless root 2.62, blu spark kernel and twrp. fastboot flash stock boot and recovery. reboot to update and it fail. any idea why?
Click to expand...
Click to collapse
Did you modify system?
Try flashing system, boot, and recovery.
Then try again.

Hi, I have a Oneplus One and today has been released an OTA, so I tried the method. I have COS13 JK (latest full rom) firmware, with systemless 2.84beta supersu and twrp.
The only apps that have root access are AdAway and Greenify (without mods to system apps). No Busybox installed.
I reverted via fastboot to original JK boot.img and recovery.img, and restored, via Adaway, the original hosts file, then I applied the OTA via stock Cyano Recovery, but update failed ("system partition has unexpected contents" error).
Why?
Thanks.

you have to unroot first from the app.Revert to original boot. and then flash
Sent from my ASUS_Z00LD using Tapatalk

caldent said:
you have to unroot first from the app.Revert to original boot. and then flash
Sent from my ASUS_Z00LD using Tapatalk
Click to expand...
Click to collapse
I tried: no way to install OTA, I had to wait for the full rom, and dirty flashed it via TWRP without a problem.
Then I rerooted.
Bye!

ok i seem to be getting the run around on where i need to be to ask my question(s)
i am very interested in systemless root....
that being said i am clueless and all info i am findingis just super confusing me.
if someone could humor a noob to systemless rooting that would be greatly appreciated!!
i recently bought 2 new phone for my household, both are the lg tribute hd (also called lg x style)
one click root and pc method of kingoroot etc dont work... i cant locate a twrp or a cwm for this model easily by searching so i am assuming there isnt one (maybe someone could located or help to build one?)- or maybe im not tech smart enough and i can use any?(i dont think so)
model is lg ls675,android 6.0.1, kernel version 3.10.49, build # MXB48T, software is ls676zv3
main reason at the moment for trying to get root is to remove bloatware and to be able to wifi tether without limitations buy the provider, on ther phone that i have obtained root on i used an app called WIFI Tether Router which works beautifully but requires root...
please help as this is how we use our computer with internet and its beneficial all the way around especially to get rid of bloatware and keep device running smoothly...
thanks again for any help. greatly appreciated.
if im not in the right thread please kindly direct me to the correct one. thanks

Can't seem to root 6.0.1

I'm having an issue rooting my Nexus 6. I rooted it easily enough a couple months ago with the NRT. I recently used the Flash stock + Unroot options to upgrade to 6.01. However, when I tried rooting it again I ran into problems. I plugged it up, selected the root option, it tested ADB connectivity, booted into TWRP and that's when I ran into an issue. It told me then that ADB device was not found. I rebooted my phone and though I can boot into it, I now get a "your phone is corrupt" message when I turn it on. I tried again and has the same issue.
I followed the instructions it gave me about checking my drivers and they're fine. Anyone have any idea what's going on and how I can get around it? Also help removing the "your phone is corrupt message"would be cool too, but it's not a priority since it seems harmless and I'm sure I could find it easily enough with a little Googling, the other problem I have not been able to find an answer to though.

Rentom said:
I'm having an issue rooting my Nexus 6. I rooted it easily enough a couple months ago with the NRT. I recently used the Flash stock + Unroot options to upgrade to 6.01. However, when I tried rooting it again I ran into problems. I plugged it up, selected the root option, it tested ADB connectivity, booted into TWRP and that's when I ran into an issue. It told me then that ADB device was not found. I rebooted my phone and though I can boot into it, I now get a "your phone is corrupt" message when I turn it on. I tried again and has the same issue.
I followed the instructions it gave me about checking my drivers and they're fine. Anyone have any idea what's going on and how I can get around it? Also help removing the "your phone is corrupt message"would be cool too, but it's not a priority since it seems harmless and I'm sure I could find it easily enough with a little Googling, the other problem I have not been able to find an answer to though.
Click to expand...
Click to collapse
flash any custom kernel to get rid of that message

simms22 said:
flash any custom kernel to get rid of that message
Click to expand...
Click to collapse
Don't really have any desire to use a custom kernel, but I'll keep it in mind. I just don't know why it popped up now when nothing happened, but when I actually rooted the device I never saw that message.

Rentom said:
Don't really have any desire to use a custom kernel, but I'll keep it in mind. I just don't know why it popped up now when nothing happened, but when I actually rooted the device I never saw that message.
Click to expand...
Click to collapse
because google put it there, it is new.

It was rooted with an older version of su. You probably said yes when twrp asked if you wanted to root it. Flash it back to stock, if you use nrt again select the no wipe option to save your data. And make sure your net is current. If you do it by hand skip the user partition.
When you root it male sure you use a newer su. 2.67 is the current version I believe.
Sent from my Nexus 6 using XDA Labs

TonikJDK said:
It was rooted with an older version of su. You probably said yes when twrp asked if you wanted to root it. Flash it back to stock, if you use nrt again select the no wipe option to save your data. And make sure your net is current. If you do it by hand skip the user partition.
When you root it male sure you use a newer su. 2.67 is the current version I believe.
Sent from my Nexus 6 using XDA Labs
Click to expand...
Click to collapse
Yeah I let twrp root it when it asked when I did it two months ago. Was that a bad thing? I thought I read that it was if you were rooting 6.0.1, but I was rooting 6.0 so I decided to see what would happen, and it went smoothly.

That is what is causing the corrupted message. It was an old version of su and it modified the system.
Sent from my Nexus 6 using XDA Labs

TonikJDK said:
That is what is causing the corrupted message. It was an old version of su and it modified the system.
Sent from my Nexus 6 using XDA Labs
Click to expand...
Click to collapse
I see. Makes sense. Alright, thanks. I already did flash it back to stock to update to 6.0.1, so I'm not sure why you told me to flash it back to stock and then install su 2.67.

I am also having this problem. Twrp will not let me flash a kernel or SuperSU. I went back to stock recovery and tried to root using cf auto root. But no luck. Phone runs fine, I upgraded to 6.01 with adb and did not flash user data. Any help would be greatly appreciated.

Mongo23ny said:
I am also having this problem. Twrp will not let me flash a kernel or SuperSU. I went back to stock recovery and tried to root using cf auto root. But no luck. Phone runs fine, I upgraded to 6.01 with adb and did not flash user data. Any help would be greatly appreciated.
Click to expand...
Click to collapse
flash twrp again, pick the kernel and SuperSU, then flash in twrp. if you can't pick them, make sure that twrp is mounted. and you DID NOT use adb to boot 6.0.1, you used fastboot, that is different than adb.

simms22 said:
flash twrp again, pick the kernel and SuperSU, then flash in twrp. if you can't pick them, make sure that twrp is mounted. and you DID NOT use adb to boot 6.0.1, you used fastboot, that is different than adb.
Click to expand...
Click to collapse
I can pick them both, when I swipe to flash it just goes back to the teamwin start up screen. Tried many, many times.

Mongo23ny said:
I can pick them both, when I swipe to flash it just goes back to the teamwin start up screen. Tried many, many times.
Click to expand...
Click to collapse
OK, try flashing twrp again, maybe it just errored. flash twrp version 3.0

simms22 said:
OK, try flashing twrp again, maybe it just errored. flash twrp version 3.0
Click to expand...
Click to collapse
Tried flashing twrp a couple of times, went back to stock recovery and then twrp. No luck. Also, phone will not boot with custom recovery only with stock. Not sure if I tried 3.0.0.0

simms22 said:
OK, try flashing twrp again, maybe it just errored. flash twrp version 3.0
Click to expand...
Click to collapse
Do I keep system read only in twrp 3.0?

Mongo23ny said:
Do I keep system read only in twrp 3.0?
Click to expand...
Click to collapse
no, do not keep system read only, ever.

simms22 said:
no, do not keep system read only, ever.
Click to expand...
Click to collapse
Thanks for all your help, did a clean install, fastboot flashed 6.01. I had gotten that corrupt phone message when I rebooted again but I took some security update and that got rid of the message. I flashed twrp 3.0.0.0 and SuperSU 2.67 and got root back. No worries, thx again.

Mongo23ny said:
Do I keep system read only in twrp 3.0?
Click to expand...
Click to collapse
simms22 said:
no, do not keep system read only, ever.
Click to expand...
Click to collapse
If you are using the systemless root method then yes, you do want to keep system read only.

alryder said:
If you are using the systemless root method then yes, you do want to keep system read only.
Click to expand...
Click to collapse
I kept it in read only, installed SuperSU 2.67 in twrp.

Magisk 14 News

Wow no need for custom recovery...
http://www.androidpolice.com/2017/0...hout-root-installing-without-custom-recovery/

@ultramag69 Maybe he doesn't follow Magisk closely? I know I don't. Magisk is only on used my stepmom's OP3T H2OS (which I update but don't look at the change log since it's only there in case I need it in the future), the other 2 phones I support don't use Magisk they use LOS su add-on. Not everyone who uses root cares about all the bloated/"nifty" features that come out, some just want plain old root.

I only use for root too but every so often I open magisk manager as it updates both the manager app and magisk itself....
It's done that for ages... The only one I found that didn't was 13.1, that one needed TWRP.

I'm letting people know that with 14 they can keep stock recovery and take OTAs

ultramag69 said:
I only use for root too but every so often I open magisk manager as it updates both the manager app and magisk itself....
It's done that for ages... The only one I found that didn't was 13.1, that one needed TWRP.
Click to expand...
Click to collapse
Before you flame someone you should read the link. FOR THE FIRST TIME YOU CAN KEEP STOCK RECOVERY SO YOU CAN TAKE OTAS

lollyjay said:
Before you flame someone you should read the link. FOR THE FIRST TIME YOU CAN KEEP STOCK RECOVERY SO YOU CAN TAKE OTAS
Click to expand...
Click to collapse
I have had stock recovery on more than one without having to reflash recovery with custom one .
If you use fastboot to flash the recovery, Instead of replacing with TWRP, you can use the command "fastboot boot TWRP.img" (TWRP.img being the name of the TWRP image you have such as twrp-3.1.1-0-oneplus5.img) , this will just boot you into TWRP where you can flash SuperSU or Magisk as you please but will revert back to stock recovery once you boot again while retaining root.

ultramag69 said:
I have had stock recovery on more than one without having to reflash recovery with custom one .
If you use fastboot to flash the recovery, Instead of replacing with TWRP, you can use the command "fastboot boot TWRP.img" (TWRP.img being the name of the TWRP image you have such as twrp-3.1.1-0-oneplus5.img) , this will just boot you into TWRP where you can flash SuperSU or Magisk as you please but will revert back to stock recovery once you boot again while retaining root.
Click to expand...
Click to collapse
No need to do that now

Honestly, who roots a phone without flashing a custom recovery the very second after? Unless they are forced to use Flashfire without BL unlock, I guess.

lollyjay said:
No need to do that now
Click to expand...
Click to collapse
Yeah, but using magisk to root my Axon 7 with unlocked bootloader didn't work...
There's still problems with some phones...

ultramag69 said:
Yeah, but using magisk to root my Axon 7 with unlocked bootloader didn't work...
There's still problems with some phones...
Click to expand...
Click to collapse
No problems at all with my OP5

Magisk 14.0 breaks XPosed so had to go back to Magisk 13.3

Now where can we obtain a copy of the stock boot.img?

almostthere said:
Now where can we obtain a copy of the stock boot.img?
Click to expand...
Click to collapse
What you're supposed to do is make a backup of your boot partition any time you update your rom. So if you didn't do that then you can dirty flash your current Rom and that would give you the stock boot.img and again, go into recovery and make a backup of your boot partition. then if you want to flash a custom kernel you can.

Help the noobs
Would any of you more experienced guys please post a step-by-step of how to do it?
From what Eric214 wrote I still don't understand where (or how) to get a copy of the stock_boot.img.
If you get the copy of the stock boot image, is it possible to do it without unlocking the bootloader?
I already installed everything before reading how to root - stupid me, and don't want to reinstall everything.

s_ofer said:
Would any of you more experienced guys please post a step-by-step of how to do it?
From what Eric214 wrote I still don't understand where (or how) to get a copy of the stock_boot.img.
If you get the copy of the stock boot image, is it possible to do it without unlocking the bootloader?
I already installed everything before reading how to root - stupid me, and don't want to reinstall everything.
Click to expand...
Click to collapse
I have the stock 4.5.10 boot.img for download here:
https://drive.google.com/file/d/0B3gcDbDvV4Mkbm5EMEZ4dnpSbk0/view?usp=drivesdk
Sent from my OnePlus5 using XDA Labs

Thanks.
Do any of you think it is possible to FLASH anything without unlocking the bootloader?
There is a thread somewhere for OP3T that shows somehow that is possible to load TWRP on the phone without unlocking the bootloader or wiping data.

I only use for root too but every so often I open magisk manager as it updates also both the manager app and magisk itself. But using magisk to root my Axon 7 with unlocked bootloader.

[ODIN] J700T Nougat 7.1.1

https://www.androidfilehost.com/?fid=889964283620761169
Grabbed straight from SamMobile. Flash using Odin.

Not for j700t1 though, correct?

AngryManMLS said:
Grabbed straight from SamMobile. Flash using Odin.
Click to expand...
Click to collapse
But how do you root after flashing this Nougat in J700T?

deloj said:
But how do you root after flashing this Nougat in J700T?
Click to expand...
Click to collapse
There's all sorts of knowledge in the thread
https://forum.xda-developers.com/galaxy-j7/j700t-development

Anything you see for the J700T is compatible with the J700T1. The phones are exactly the same minus 4 apps inside the system.
ctindell1981 said:
Not for j700t1 though, correct?
Click to expand...
Click to collapse

Is this Nougat stock rom for the samsung J700T? And how do I root it?

I have a J700T with twrp and root. Is there a nougat ROM that I can download and flash via twrp?
I would rather not go back to stock, flash nougat, and then re-root.

nimbus22 said:
I have a J700T with twrp and root. Is there a nougat ROM that I can download and flash via twrp?
I would rather not go back to stock, flash nougat, and then re-root.
Click to expand...
Click to collapse
There is no such rom for this model in nougat yet

nimbus22 said:
I have a J700T with twrp and root. Is there a nougat ROM that I can download and flash via twrp?
I would rather not go back to stock, flash nougat, and then re-root.
Click to expand...
Click to collapse
I'm writing this up in case anyone else needs help.
1) Couldn't get the 7.1.1 download to work from sammobile. Ended up downloading the firmware from another source and flashing through Odin. Took a couple of minutes to reboot after the flash.
2) Wanted to get TWRP and Root back on the phone and followed these instructions.
https://forum.xda-developers.com/galaxy-j7/j700t-development/recovery-galaxy-j7-sm-j700t-t1-t3560342
Now have twrp and root. Everything seems to be working fine.

nimbus22 said:
I'm writing this up in case anyone else needs help.
1) Couldn't get the 7.1.1 download to work from sammobile. Ended up downloading the firmware from another source and flashing through Odin. Took a couple of minutes to reboot after the flash.
2) Wanted to get TWRP and Root back on the phone and followed these instructions.
https://forum.xda-developers.com/galaxy-j7/j700t-development/recovery-galaxy-j7-sm-j700t-t1-t3560342
Now have twrp and root. Everything seems to be working fine.
Click to expand...
Click to collapse
followed the steps on the thread. can't make it work. always getting stuck at tmobile logo
here are the steps i used.
1. flash firmware through odin
2. flash twrp through odin
3. flash supersu through twrp
4. flash dm-verify.zip through twrp
5. stuck on tmobile logo.
any ideas?

Once it's been on the screen saying t mobile for at least 10 mins, pull battery, boot to stock recovery, mount system, factory reset, reboot. There. Now u will hear t mobile jingle and it will reach set up wiz

nikkosaurus said:
followed the steps on the thread. can't make it work. always getting stuck at tmobile logo
here are the steps i used.
1. flash firmware through odin
2. flash twrp through odin
3. flash supersu through twrp
4. flash dm-verify.zip through twrp
5. stuck on tmobile logo.
any ideas?
Click to expand...
Click to collapse
I flashed supersu after the dm verity had no problems

benny3 said:
I flashed supersu after the dm verity had no problems
Click to expand...
Click to collapse
Which TWRP version is people using?

https://forum.xda-developers.com/ga...ecovery-galaxy-j7-sm-j700t-t1-t3560342/page30
Same as mm

Does anyone know if Xposed works on it yet? Wanting to update but don't want to lose Xposed

uklele1234 said:
Does anyone know if Xposed works on it yet? Wanting to update but don't want to lose Xposed
Click to expand...
Click to collapse
Yes, it does
.

uklele1234 said:
Does anyone know if Xposed works on it yet? Wanting to update but don't want to lose Xposed
Click to expand...
Click to collapse
I would recommend using the magisk modified Xposed installer from the magisk stable threads, and install Xposed via magisk. The other xposed doesn't work as well, it says some modules are installed and running, but actually not doing anything. Just a heads up
hightech316 said:
Yes, it does
.
Click to expand...
Click to collapse

fullofhell said:
I would recommend using the magisk modified Xposed installer from the magisk stable threads, and install Xposed via magisk. The other xposed doesn't work as well, it says some modules are installed and running, but actually not doing anything. Just a heads up
Click to expand...
Click to collapse
How strange for me the official xposed works better than the Magisk version, the Magisk version makes my phone restart when I try to rotate the screen.

carlosbalbuena_ said:
How strange for me the official xposed works better than the Magisk version, the Magisk version makes my phone restart when I try to rotate the screen.
Click to expand...
Click to collapse
That is bizarre. I tried official first and nothing would activate

fullofhell said:
That is bizarre. I tried official first and nothing would activate
Click to expand...
Click to collapse
I have all these modules active and it works perfectly

How do I update supersu binaries?

Just successfully installed Supersu 2.81 (2.81 because the guide I used said it's the most stable version) when my phone rebooted the playstore promted me to update Supersu so. being the clueless noob that I am I updated it. Now it keeps failing when it's trying to update binaries. I can still use supersu and still have root access though. It's just annoying seeing that message to update binaries.

I have the same problem, I've even tried flashing the SuperSU .zip manually using TWRP! It reboots my phone before it finishes the flashing process. Does anyone know how to update it?

fajner said:
I have the same problem, I've even tried flashing the SuperSU .zip manually using TWRP! It reboots my phone before it finishes the flashing process. Does anyone know how to update it?
Click to expand...
Click to collapse
I already fixed mine.

blitzball said:
I already fixed mine.
Click to expand...
Click to collapse
How did you fix it?

fajner said:
How did you fix it?
Click to expand...
Click to collapse
Open Supersu, navigate to the settings, scroll down and do a full unroot. Your phone will reboot so make sure you activate twrp before your phone boots fully otherwise you'll have to reinstall twrp again via adb cause your phone will overwrite twrp after it boots.
Download Supersu 2.82 here (the one I have is the no additive version just root) and just flash it with twrp. Done. Easy.
https://forum.xda-developers.com/p9/development/root-supersu-2-81-emui-5-t3612258

blitzball said:
Open Supersu, navigate to the settings, scroll down and do a full unroot. Your phone will reboot so make sure you activate twrp before your phone boots fully otherwise you'll have to reinstall twrp again via adb cause your phone will overwrite twrp after it boots.
Download Supersu 2.82 here (the one I have is the no additive version just root) and just flash it with twrp. Done. Easy.
https://forum.xda-developers.com/p9/development/root-supersu-2-81-emui-5-t3612258
Click to expand...
Click to collapse
Sorry for late reply, I've tried uninstalling supersu/unrooting but neither did work or help. I finally ended up rebranding my phone to AL10 and installing the Chinese Oreo rom which works great.