yashsingh1/xdaforums huggingface dataset:
[SuperSU] VivaErBetis:
Tested SuperSU Pro 2.79 SR1

Google Nexus 5X

With android-7.1.1_r1 NMF26F Nougat (all stock).

Systemless install using TWRP. It works perfectly!

Google Nexus 4

With android-5.1.1_r19 LMY48T Lollipop (all stock).

Normal install using TWRP. Doesn't boot (bootloop).

Previous version 2.79 works perfectly (even when re-installed again over 2.79 SR1).

A clue: I'm also using your fantastic liveboot app and it doesn't even start when using 2.79 SR1, so the problem should happen before it.

Can I give you any other info? Since it's a bootloop I think there are no logs available.

Thanks and best regards.
[SuperSU] Vapu:
For me, TWRP throws "patching sepolicy, failure, aborting" and the phone is not rooted afterwards.

Samsung I9505, CM13 latest nightly.

FYI, the supersu 2.78 did install completely and caused a bootloop for me.
[SuperSU] sharp87:
Titanium backup keeps showing " searching application data " after flashing latest supersu zip
[SuperSU] Elanza_48:
Try disabling the namespace saperation.
[SuperSU] sharp87:
Still issue persist
[SuperSU] corkiejp:
Had trouble trying to flash SR1 on my Kenzo as well. Official TWRP for the device needs to be update.

In the mean time you can use Strix's TWRP or ZCX TWRP to flash it!
[SuperSU] djsolidsnake86:
the latest twrp official work?
[SuperSU] corkiejp:
Official twrp-3.0.2-2 didn't work for me today? When I tried!

On opening the SuperSU app, got a prompt "no su binary installed" or something similar and no option to install from the app.

From reading the Radon Kernel thread, I knew there was problem with official TWRP for that as well.

Hence I tried Strix's TWRP and it worked for both su and kernel!
[SuperSU] 123SIT:
Zygote dies with 2.79 SR1, xposed .87 installed, socket permission denial resulting in boot loop on emotion 6.0.1
[SuperSU] DeadlyGhost08:
For those having bootloops I may have the solution. I was having bootloops too but then I saw that SuperSU 2.79 SR1 was getting flashed in System mode. The earlier versions(2.78, 2.78 SR4/SR5 ,2.79) were flashing just fine but idk what caused 2.79 SR1 to flash in System mode, although I dirty flashed Resurrection Remix 7.1 for Lux before flashing 2.79 SR1 for some reason. I went to Terminal(TWRP) and changed to Systemless mode using this :

echo "SYSTEMLESS=true" > /data/.supersu

and then I flashed 2.79 SR1 and rebooted into system just fine. Hope it works out for anyone else having bootloop.
[SuperSU] Chainfire:
Does it work if you remove suhide, though?

Whether or not SafetyNet works without those changes is pretty device dependent.

As for updates to suhide, my problem is lack of time, not lack of will.

(1) I don't know

(2) They're loosely related at best, but they do somewhat influence eachother. It's complicated.

Can you quote the SELinux permission denials? Logcat?

There is no difference in the relevant code between 2.79 and 2.79 SR1 that I can see. I suspect if you had re-flashed the original 2.79 it would also have gone into system mode.
[SuperSU] gothicVI:
1) I personally flash SuperSU first

2) xposed just requires some rooted device but in my experience it doesn't matter whether it's SuperSU or, e.g., cm su.

Gesendet von meinem Moto G 2014 LTE mit Tapatalk
[SuperSU] playboy0187:
Working on galaxy s7 edge ??

Gesendet von meinem SM-G935F mit Tapatalk
[SuperSU] carlitobahsoun:
flashed on n920c and everything ok no bootloop : (mm) rom not ux or ported n7
[SuperSU] DeadlyGhost08:
Maybe dirty flashing RR ROM did something, and yes re-flashing 2.79 went through system mode (after dirty flashing ROM) and then bootloop. Flashing SuperSU in system mode gives bootloop while in systemless mode gives no problem.

EDIT: Now I remember flashing Magisk and phh's Superuser just because I wanted to play Pokémon Go but it didn't work so I uninstall both of these and then flashed SuperSU which resulted into bootloop so I dirty flashed RR7.1 ROM and then flashed SuperSU which again gave me bootloop. I dirty flashed again to remove SuperSU and booted into system. When I heard about 2.79 SR1 and tried to flash it then I realised it was getting flashed through system mode and not systemless mode. Moral of comment : Flashing SuperSU through systemless mode solves bootloop issue.
[SuperSU] djb77:
Just leaving some feedback...

I own a Samsung Galaxy S7 (MM 6.0.1).

SuperSU 2.79 Stable works perfect, however 2.79 SR1 fails at the point where it patches the policy

- Patching sepolicy
sukernel v2.79 (ndk:arm64-v8a) - Copyright (C) 2014-2016 - Chainfire

Loading from [/sutmp/ramdisk] ...

Saving to [/sutmp/sepolicy] ...

supolicy v2.79 (ndk:arm64-v8a) - Copyright (C) 2014-2016 - Chainfire

Patching policy [/sutmp/sepolicy] --> [/sutmp/sepolicy.patched] ...
(Android M policy compatibility mode)
Segmentation fault
--- Failure, aborting

I attached the full recovery.log to show what happened.

Hopefully this can be sorted for SR2, otherwise I'll have to stick with 2.79 Stable.
[SuperSU] buttie:
Yes, after removing suhide phone boots without problem and I'm fully rooted on SR1.

With suhide it hangs on this:

(...)
12-23 22:52:16.517 736 736 W app_process64: type=1400 audit(0.0:2082): avc:
denied { write } for name="socket_haploid64_root" dev="mmcblk0p67" ino=647171 sc
ontext=u:r:init:s0 tcontext=u:object_r:zygote_socket:s0 tclass=sock_file permiss
ive=0
12-23 22:52:16.517 737 737 W app_process32: type=1400 audit(0.0:2081): avc:
denied { write } for name="socket_haploid32_root" dev="mmcblk0p67" ino=647170 sc
ontext=u:r:init:s0 tcontext=u:object_r:zygote_socket:s0 tclass=sock_file permiss
ive=0
12-23 22:52:16.767 736 736 W app_process64: type=1400 audit(0.0:2084): avc:
denied { write } for name="socket_haploid64_root" dev="mmcblk0p67" ino=647171 sc
ontext=u:r:init:s0 tcontext=u:object_r:zygote_socket:s0 tclass=sock_file permiss
ive=0
12-23 22:52:16.767 737 737 W app_process32: type=1400 audit(0.0:2083): avc:
denied { write } for name="socket_haploid32_root" dev="mmcblk0p67" ino=647170 sc
ontext=u:r:init:s0 tcontext=u:object_r:zygote_socket:s0 tclass=sock_file permiss
ive=0
12-23 22:52:17.027 737 737 W app_process32: type=1400 audit(0.0:2085): avc:
denied { write } for name="socket_haploid32_root" dev="mmcblk0p67" ino=647170 sc
ontext=u:r:init:s0 tcontext=u:object_r:zygote_socket:s0 tclass=sock_file permiss
ive=0
12-23 22:52:17.027 736 736 W app_process64: type=1400 audit(0.0:2086): avc:
denied { write } for name="socket_haploid64_root" dev="mmcblk0p67" ino=647171 sc
ontext=u:r:init:s0 tcontext=u:object_r:zygote_socket:s0 tclass=sock_file permiss
ive=0
12-23 22:52:17.277 736 736 W app_process64: type=1400 audit(0.0:2087): avc:
denied { write } for name="socket_haploid64_root" dev="mmcblk0p67" ino=647171 sc
ontext=u:r:init:s0 tcontext=u:object_r:zygote_socket:s0 tclass=sock_file permiss
ive=0
12-23 22:52:17.277 737 737 W app_process32: type=1400 audit(0.0:2088): avc:
denied { write } for name="socket_haploid32_root" dev="mmcblk0p67" ino=647170 sc
ontext=u:r:init:s0 tcontext=u:object_r:zygote_socket:s0 tclass=sock_file permiss
ive=0
12-23 22:52:17.367 759 759 W pnpmgr : type=1400 audit(0.0:2089): avc: denie
d { write } for name="dirty_ratio" dev="proc" ino=18446 scontext=u:r:pnpmgr:s0 t
context=u:object_r:proc_dirty_ratio:s0 tclass=file permissive=0
(...)
[SuperSU] itsahmad:
just for info it works on the s7 edge running android 7 beta 5
[SuperSU] ulxerker:
Samsung is still on 7 beta? :eek: we're on 7.1.1 stable meanwhile ... Nexus/Pixel rulez.
[SuperSU] iSplassh:
Hello guys,

Can someone please take a look at my catlog file. My device is acting strage the last days. It gets laggy and sometimes it doesn't even respond at all, and randomly reboots 2-3 times a day. Im on stock ROM (NBD91P Build), rooted with SuperSU v2.79 and Franco Kernel.

TIA

Edit: i figured out what the Spam Error (E/PowerHALL) is, but i cant understand the other Errors

12-23 18:16:23.611 E/ActivityManager(29803): Sending non-protected broadcast eu.chainfire.supersu.NativeAccess from system uid 0 pkg null
12-23 18:16:23.611 E/ActivityManager(29803): java.lang.Throwable
12-23 18:16:23.611 E/ActivityManager(29803): at com.android.server.am.ActivityManagerService.broadcastIntentLocked(ActivityManagerService.java:17726)
12-23 18:16:23.611 E/ActivityManager(29803): at com.android.server.am.ActivityManagerService.broadcastIntent(ActivityManagerService.java:18287)
12-23 18:16:23.611 E/ActivityManager(29803): at android.app.ActivityManagerNative.onTransact(ActivityManagerNative.java:499)
12-23 18:16:23.611 E/ActivityManager(29803): at com.android.server.am.ActivityManagerService.onTransact(ActivityManagerService.java:2755)
12-23 18:16:23.611 E/ActivityManager(29803): at android.os.Binder.execTransact(Binder.java:565)

https://www.dropbox.com/s/dam6piicdh7ounu/2016-12-23-18-16-08.txt?dl=0
[SuperSU] Chainfire:
Both of you please upload your boot images. (For example, backup just 'boot' with TWRP and upload the backup)
[SuperSU] KaZo58:
i lost my root (2.79 SR1) after a crash/shutdown. wiped system, flashed rom and supersu 2.79, still no root. this happened first time for me. what do i have to do?
[SuperSU] djb77:
Here you go, TGPKernel v3.42 for G930F (Galaxy S7)

If you want to check the source code at all, here is my git: https://github.com/djb77/tgpkernel-s7

Hope this helps.

Merry Christmas and many thanks for all your hard work :)
[SuperSU] buffer overflow:
[MENTION=4058477]iSplassh[/MENTION] You use last version Franco kernel (30) ?
[SuperSU] iSplassh:
Yes im on last version of Frank r58
[SuperSU] buffer overflow:
Is fk-r30, not r58... ? Try other kernel like ElementalXIs very good and I have not any problem.Be carefully if you interested to install.Read OP.Is not SuperSU problem here.
[SuperSU] iSplassh:
For the nexus 6 its fk-r58
[SuperSU] buffer overflow:
Sorry, i don't see the segnature... Recomandation remain the same.
[SuperSU] CrazyCypher:
Hy guys, I purchased SuperSU but I can't seem to find OTA survival mode setting to enable?
[SuperSU] jcmm11:
Franco works just fine (as does elementalx. Franco and flar both know what they're doing). Kernel is not the issue.
[SuperSU] buffer overflow:
Maybe, but defenly not SuperSU.I used Franco Kernel for a short time...I know is good, but for max battery life is poll out some animation and scrolling.
[SuperSU] CyberpodS2:
I'll post this as a statement and a question. I didn't know if you wanted success reports but if so, all was transparent updating from 2.79 to 2.79 sr1. Nexus 6 running Pure Nexus 7.1.1 with ElementalX 4.14 in permissive.
[SuperSU] Ch3vr0n:
That's because it's no longer there. I think it got removed around the the time devices started using image 'blocks' for checksum and not file based.

Sent from my Nexus 6P with Tapatalk.
[SuperSU] iSplassh:
I saw this line here, and thought maybe i ask someone here for any help or tips. Im not saying its SuperSU's fault. I dint find anything usefull in google.

E/ActivityManager(29803): Sending non-protected broadcast eu.chainfire.supersu.NativeAccess from system uid 0 pkg null
[SuperSU] glauberlima:
SuperSU v2.79 SR1 - segmentation fault is back

Thanks for the update [MENTION=631273]Chainfire[/MENTION] although I had no chance to test it.

Just to let you know, the segmentation fault bug is back.

Device: Moto X (2014) XT1097

Follows the recovery.log extracted from my attempt: http://pastebin.com/WpB5jwcF
[SuperSU] Logan:
[MENTION=631273]Chainfire[/MENTION] Good afternoon boss xD

I was surfing my i9300 early using cm14.1.

After running With latest SuperSU version for 13hours ,i got this zygote calling SuperSU, as i read in google: "Zygote is a daemon whose goal is to launch Apps. The startup of the process is triggered by Init.rc after Service Manager and others but it is actually started by app_process".

My question is this related to supersu or cm/installed app because i can't find any answer about running zygote in root mode.

(Sorry for being careless without providing log...)

Thanks for your time :)
[SuperSU] djb77:
Here is also a solution my friend [MENTION=5899304]Tkkg1994[/MENTION] was able to put together, all he did was alter the update-binary a little and it did work.

One thing I did fail to mention too is that the ramdisk is XXU1BPLB (released this month). Maybe something new in the ramdisk could be causing the issue.

Sorry, should have mentioned this info when i gave you the boot image.
[SuperSU] Chainfire:
SuperSU is sending a broadcast as root, which the rest of the system thinks is odd. Even though it logs as "E" for Error, it's really only a "W"arning logged, it doesn't affect functionality whatsoever. I'm going to look into getting rid of the message for SR2, though.

Please post your boot.img.

The bug isn't back, it's a whole new bug :)

So... are you also going to state *what* he actually changed?
[SuperSU] glauberlima:
Here you are: View attachment 3978982

Thank you and Merry Christmas!
[SuperSU] Tkkg1994:
So since V2.79 sepolicy patch still worked fine on latest sepolicy from BPLB ramdisk I decided myself to do following: Check if android nougat is installed, if not use the old method of sepolicy patch. Check my code:

Replaced:

if ($PERMISSIVE); then
# once for default SuperSU rules, once to make everything fake-permissive, both are needed
LD_LIBRARY_PATH=$SYSTEMLIB /su/bin/supolicy --file /sutmp/sepolicy /sutmp/sepolicy.tmp --sdk=$API
LD_LIBRARY_PATH=$SYSTEMLIB /su/bin/supolicy --file /sutmp/sepolicy.tmp /sutmp/sepolicy.patched "permissive *"
else
LD_LIBRARY_PATH=$SYSTEMLIB /su/bin/supolicy --file /sutmp/sepolicy /sutmp/sepolicy.patched --sdk=$API
fi

With:

if [ "$API" -ge "24" ]; then
if ($PERMISSIVE); then
# once for default SuperSU rules, once to make everything fake-permissive, both are needed
LD_LIBRARY_PATH=$SYSTEMLIB /su/bin/supolicy --file /sutmp/sepolicy /sutmp/sepolicy.tmp --sdk=$API
LD_LIBRARY_PATH=$SYSTEMLIB /su/bin/supolicy --file /sutmp/sepolicy.tmp /sutmp/sepolicy.patched "permissive *"
else
LD_LIBRARY_PATH=$SYSTEMLIB /su/bin/supolicy --file /sutmp/sepolicy /sutmp/sepolicy.patched --sdk=$API
fi
else
if ($PERMISSIVE); then
LD_LIBRARY_PATH=$SYSTEMLIB /su/bin/supolicy --file /sutmp/sepolicy /sutmp/sepolicy.patched "permissive *"
else
LD_LIBRARY_PATH=$SYSTEMLIB /su/bin/supolicy --file /sutmp/sepolicy /sutmp/sepolicy.patched
fi
fi

This worked out as expected and supersu is fully functional. Hope this could help you
[SuperSU] Chainfire:
Well, obviously that works. SR1 was mainly about SELinux changes, which you reverted with your patch :)

EDIT: On re-reading that sounds harsh. This *does* actually help me track the problem, thanks.
[SuperSU] :
Usually this can happen (specially on Huawei) devices since we haven't symlinked vendor folder to system. And it can't patch properly but in your case it's not.
[SuperSU] Obi-XDA:
I've flashed 2.79 sr1 in a huawei ascend p7, previously rooted with 2.79 official, and previous versiones, 2.78 srX without problems, and stays in bootlogo, and flashing 2.79 again starts normally

sorry for my english
[SuperSU] grep_i:
Sorry it's really stating that /data failed to mount.

Why posting the log in plain text when the error stand in the first line.

Next time upload log file itself or link to something like pastebin for the reading pleasure of people who use XDA on mobile phones with smaller screens than 32" desktop screens.

Thanks in advance please.
[SuperSU] decayed.cell:
I ended up doing a Format data and then reinstalling - worked like a charm
[SuperSU] grep_i:
Of course it worked, it fixed the problem with your mount point :good:
[SuperSU] ksnewland:
is link in OP dead? download.chainfire.eu isn't working
[SuperSU] Ja_som:
It's OK
[SuperSU] HorstiG:
You are the Best :good::good::good:
[SuperSU] m0han:
did you try running any root-required apps - just to be sure?

http://xdaforums.com/showpost.php?p=70215420&postcount=8501

---------- Post added at 09:33 AM ---------- Previous post was at 09:32 AM ----------

i use alka twrp and things seem fine. except that my status is almost like this; onlythe location of supersu (base.apk) is different.

---------- Post added at 09:33 AM ---------- Previous post was at 09:33 AM ----------

i remember reading somewhere (xposed thread, i think) that it's best to flash xposed the last - with a wipe of cache & dalvik cache

before & after

flashing xposed.

---------- Post added at 09:40 AM ---------- Previous post was at 09:33 AM ----------

yeah, but i faced this issue (no icon in app drawer or settings) only after dirty-flashing the 20161225 nightly for kenzo. the 20161224 nightly dirty-flashed fine.

---------- Post added at 09:57 AM ---------- Previous post was at 09:40 AM ----------

i face almost the same situation; i did not do any apk-uninstalling/installing or binary-updating, though. i notice that my supersu is located in /data/app/eu.chainfire.supersu-1. should i just leave it as is where is?

---------- Post added at 10:02 AM ---------- Previous post was at 09:57 AM ----------

i used to do this - delete supersu folder in twrp and execute the code - after a clean flash of every rom. but, i forgot to do this once and i saw i still had systemless root. from then on, i just flash the latest supersu by chainfire and things have been fine.
[SuperSU] panczyszynjan1:
Su
[SuperSU] gothicVI:
That's what I do and also wrote. In my experience it's best to go as follows:

0 back up!

1 ROM

2 gapps if it's a new install

3 SuperSU

4 xposed framework

5 custom scripts if wanted

6 wipe cache and art cache

7 reboot

Gesendet von meinem Moto G 2014 LTE mit Tapatalk
[SuperSU] andrew2432:
Xposed won't install without root!! You may be able to unroot after the install of systemless, but I can't find that post anymore

Don't forget you MAY need to enable root and remove the native toot within your app!!

Beta works on my lgg2
[SuperSU] corkiejp:
SR1 Failed to flash properly again, without first ......

Device: - Redmi Note 3 Pro running xiaomi.eu 6.12.22.

A new version of the Radon kernel was release today, that required flashing on a stock kernel.

I flashed the stock boot image and again tried to root using SR1, something wrong with the zip as it is not installing the binaries properly. Need to first flash stable 2.79 and then flash SR1 over it for it to work.

Do not know what logs you would need? If i'm flashing again, for rom update on Friday, maybe I can save some logs and share them here.
[SuperSU] gothicVI:
[MENTION=4868912]corkiejp[/MENTION] TWRP logs might be a good start

Gesendet von meinem Moto G 2014 LTE mit Tapatalk
[SuperSU] corkiejp:
[MENTION=5895297]gothicVI[/MENTION] Thanks, must remember to copy the log from TWRP on Friday!
[SuperSU] Elektron60:
Plesse do NOT post long logs here!
[SuperSU] IronTechmonkey:
It is not that persons fault that the hide tag, which they actually attempted to use, does not work in the XDA Labs app. Also, perhaps constructive suggestions such as sharing only pertinent parts of the log or using a hosting site would help.
[SuperSU] grep_i:
Not true to install Xposed you don't need root the only time when you need root in Xposed installer is to use the reboot function and for some modules but not for Xposed installer itself.
[SuperSU] andrew2432:
So only to use reboot within xposed installer and SOME apps in the repository? I thought, maybe for system?, That to install xposed your phone needed to be rooted. Awesome news if not, just check the xposed module to see if root is required if I can get xposed installed?
[SuperSU] grep_i:
It looks like it had issues with mounting

/data

So it is not mounted during flash probably this causes all the errors and the segmentation fault.
[SuperSU] drewski_1:
Root is needed for Xposed in general, I thought.
[SuperSU] mielletseed:
so maybe you thought wrong. in my opinion you only need a custom recovery to install the framework but the most people with custom recovery have their devices rooted ;)

the latest version of the installer can directly install to /system and therefore root is necessary too.
[SuperSU] grep_i:
Root is not needed to flash the Xposed framework in systemmode I tested this with v76 to v87.

With systemless you need systemless root as a dependency.

For the Xposed installer you do not need root but most people were already rooted to flash the framework.
[SuperSU] ldeveraux:
Again, no. The Amazon Fire doesn't have a recovery, but can use flashfire. Therefore root is required.
[SuperSU] mielletseed:
so what? are we discussing in general or a particular device? it's not that xposed would need root but you will need root to install it on devices without custom recovery. to me this is a difference. it was told "xposed requires root" and that's not true. "some devices require root to get xposed installed" is true..
[SuperSU] gothicVI:
I'm sorry. I posted via the website and just now realised that the hide tags don't work in Tapatalk as well. I'll do it differently in the future. Anyway as you can see I already cut the log...

Do you think simply mounting data manually in TWRP does the trick?

Gesendet von meinem Moto G 2014 LTE mit Tapatalk
[SuperSU] grep_i:
No I do not think that will help, there is an issue on your device that prevent /data to mount.

You have to find out what it is, fix it and maybe than you can mount /data and flash supersu correctly ?
[SuperSU] IronTechmonkey:
Nothing to apologize for. :)
[SuperSU] _alexndr:
[MENTION=631273]Chainfire[/MENTION]

v2.79 SR1 finally works well @ Nougat beta @ G935F :good:

However, v2.79 SR1 fails @ Note4 (the newest N910FXXU1DPL2 stock ROM).

[...]
- Patching sepolicy
--- Failure, aborting
[...]

More detailed (reproduced) error message:

supolicy v2.79 (ndk:armeabi-v7a) - Copyright (C) 2014-2016 - Chainfire

Patching policy [/sutmp/sepolicy] --> [/sutmp/sepolicy.patched] ...
(Android M policy compatibility mode)
Segmentation fault

v2.79 (official, stable) works well

EDIT: Original sepolicy file from original N910FXXU1DPL2 stock kernel has been attached
[SuperSU] andreoide:
Strange....

After update the December fw for samsung sm-g901f kccat6, I could not root with the new SR1.

Had to flash 2.78 SR5, than in Google play store the new SU 2.79, and than the Su 2.79 SR 1

Never had troubles before and now though I have root finally I wonder how this can be?
[SuperSU] Ch3vr0n:
Nobody will know unless you can provide some kind of logs where you try or tried to flash SR1

Sent from my Nexus 6P with Tapatalk.
[SuperSU] kylemd:
Yes! :D F2FS working fine here now. Xiaomi Mi5 on 2.79 SR1.

You're a legend [MENTION=631273]Chainfire[/MENTION] !
[SuperSU] etoy:
did you install it in systemless mode?

what rom? thanks
[SuperSU] kylemd:
Sorry meant to say all that...CM14.1 final nightly. Installed in systemless mode.
[SuperSU] _alexndr:
Just reproduced this issue manually from TWRP's terminal and edited my previous post (as above)
[SuperSU] etoy:
same device (mi5) same cm14 build (12.25), same filesystem (f2fs on data and cache)

systemless mode fails

-Finding boot image
- - - Boot image: /dev/block/sde36
- Extracting ramdisk
- - - Failure, aborting

system mode installs but after rebooting device stays on bootanimation forever

----

edit: tried all SuperSU versions, including latest 2.79 and 2.79SR1
[SuperSU] kylemd:
That's what mine was doing up until now. Did you do a clean install?

What I did:

Backed up /data and copied to PC

Formatted /data and /cache as F2FS

Restored /data backup

Ran fix contexts + flashed osm0sis' fix permissions script (to fix the discrepancy between file systems)

Flashed 2.79 SR1
[SuperSU] andreoide:
I is rooted now the way I did described above so no logs available.

But maybe someone with same phone having stock rooted, has/had same problem?
[SuperSU] ive.heyah:
When at last will it work well with Huawei's EMUI?

It's something with overlay, for instance another utility "CoolTool" also didn't want to display its flowing window with it's default settings, however it has option "Overlay Mode" and after choosing "SECURE_SYSTEM_OVERLAY" now works well.
[SuperSU] grep_i:
To help you find out what went wrong in your device we need your log.

You probably do not know where to find it looking at your answer.

It is logged on your device in the folder

/cache/recovery

Study it your self or upload it here and let us take a look for you.