[ROOT][Android 7.0][EMUI 5.0]SuperSU 2.82 for EMUI 5

[Tecalote]

Sorry for troubles with SuperSU 2.82 - but Chainfire and CCMT has changed in 2.82 a lot of code.

It is better to Unroot from SuperSU App and restore boot.img before flashing 2.82.
And prerooted boot.imgs are difficult to handle.
Better to find Stock boot.img, flash it with fastboot and after flashing Root with TWRP.
KangV Roms are working with Stock boot.img and Version 3

 

[NeGriTa79]

SuperSU2.82-EMUI5-SelEnforcing.zip Works perfectly on p10 lite. Thanks

 

[Tecalote]

For Users of mate8 al10 kangv b587 I can check for you the original (unmodified) boot.img for this Firmware - and I can write a guide how to do - then you can root with v3 - just tell me who wants

 

[Tecalote]

OP is updated now.
Also the Guide for Unroot KangV Roms.

 

[cline2]

For Users of mate8 al10 kangv b587 I can check for you the original (unmodified) boot.img for this Firmware - and I can write a guide how to do - then you can root with v3 - just tell me who wants

I can test it for u.

 

[jasonseye]

For Users of mate8 al10 kangv b587 I can check for you the original (unmodified) boot.img for this Firmware - and I can write a guide how to do - then you can root with v3 - just tell me who wants

Dont have the original boot.img for al10 b587, just googled it and couldnt find in other sources, so sad.

 

[aburezk]

Working on P10 Lite, Thank you

 

[Tecalote]

Dont have the original boot.img for al10 b587, just googled it and couldnt find in other sources, so sad.

You cannot find it on the web - but that's why I said I can find, because I have connections

 

[fpippo1999]

@Tecalote you would install 1/a or 1/b on Huawei P9?
edit: what is the different in a daily usage?

 

[andres347]

Did you also try Unroot from SuperSU and after flashing the 2.82?

Yeah, unroofed 2.81 from within the app, reflashed my boot.img backup and everything was ok again. Then tried to flash versions 1a and 1b of SuperSU 2.82 but both left me without fingerprint features.

Used the same method on those two versions btw (uninstall from the app, reflash boot.img, wipe dalvik/cache, apply new flash file)

 

[Tecalote]

@Tecalote you would install 1/a or 1/b on Huawei P9?
edit: what is the different in a daily usage?

I prefer 1/b because only with SELunux Permissive I have more rights and can install Viper4Android: https://mega.nz/#!XIARUCoJ!5DNI_PDTjibR9hKzyGI8HKbzFBL5Idpoc2jtAUa0uDk
This version is modified by me with preinstalled driver.
I think, with Root its better to have more possibilities than with SELinux Enforcing...
But for daily use maybe not important

 

[Tecalote]

Yeah, unroofed 2.81 from within the app, reflashed my boot.img backup and everything was ok again. Then tried to flash versions 1a and 1b of SuperSU 2.82 but both left me without fingerprint features.

Used the same method on those two versions btw (uninstall from the app, reflash boot.img, wipe dalvik/cache, apply new flash file)

I try to make a different version with some changes. I send it to you soon is ready.
If you were between on phh superuser you should even unroot before using SuperSU (boot.img reflash is not enough) by flashing unsu.zip https://forum.xda-developers.com/showpost.php?p=63615067
And I would not reflash Stock boot.img after successful Unroot from SuperSU App and not wipe Dalvik and Cache in one processing. If you made Unroot with reboot to system , you can after wipe Dalvik and Cache with reboot to system. And then the next steps...
So wait for my changed version to try.
And with 2.81 was everything okay?

 

[Tecalote]

SuperSU 2.82 for EMUI will be updated soon!

User who have it already and have no problem with it can stay on it, all the others please wait - Thanks

 

[jasonseye]

You cannot find it on the web - but that's why I said I can find, because I have connections

Man, you are the PRO! Thanks!

 

[ante0]

2.82 works for Mate 9 as well with a little modification to the update-binary
tested with SuperSU2.82EMUI5noverityEnforcing.zip and SuperSU2.82-EMUI5-SelEnforcing.zip

for PARTITION in kern-a KERN-A android_boot ANDROID_BOOT kernel KERNEL boot BOOT lnx LNX; do

to

for PARTITION in boot_a BOOT_A kern-a KERN-A android_boot ANDROID_BOOT kernel KERNEL boot BOOT lnx LNX; do

 

[Tecalote]

2.82 works for Mate 9 as well with a little modification to the update-binary
tested with SuperSU2.82EMUI5noverityEnforcing.zip and SuperSU2.82-EMUI5-SelEnforcing.zip

You are the man That's fine, perfect Thank you!
So we should bring out a special version for Mate 9....
I would say if you like to make it I would post it in OP with your name and mention.

 

[ante0]

You are the man That's fine, perfect Thank you!
So we should bring out a special version for Mate 9....
I would say if you like to make it I would post it in OP with your name and mention.

You could probably just add it to your zips. It will just look for one more entry so shouldn't conflict with other phones.
I did however link a download in another thread over at the Mate 9 section and mentioned you so it's no biggie xD

 

[Tecalote]

You could probably just add it to your zips. It will just look for one more entry so shouldn't conflict with other phones.
I did however link a download in another thread over at the Mate 9 section and mentioned you so it's no biggie xD

I will add it into my zips - many thanks! :good:
I read all the lines of the update binary during night time (cause on day I'm in my job) but I didn't check this

I will update soon as possible.

 

[brokman]

What does SELinux Enforcing and permanent SELinux Permissive mean?
I, as a person far from programming, are interested in what to choose?

 

[Tecalote]

What does SELinux Enforcing and permanent SELinux Permissive mean?
I, as a person far from programming, are interested in what to choose?

See #131 - it's long not all what could be explained, but to have some idea

You can read here the first two articles:
https://wiki.gentoo.org/wiki/SELinux/Tutorials/Permissive_versus_enforcing