[ROOT]SuperSU 2.82

[ante0]

Gave it ago and got stuck in a boot loop. Flashing back system and boot to the original fixed it. So no joy on mate 9 pro.

Are you decrypted? If not, that's probably why.

 

[LastStandingDroid]

Gave it ago and got stuck in a boot loop. Flashing back system and boot to the original fixed it. So no joy on mate 9 pro.

What did u do? What u tried to flash

Sent from my CUBOT_MANITO using Tapatalk

---------- Post added at 03:04 PM ---------- Previous post was at 03:03 PM ----------

Are you decrypted? If not, that's probably why.

Should have to do with Decrypt it's something else. Bad patch maybe. Phh is working with encrypted devices

Sent from my CUBOT_MANITO using Tapatalk

 

[ante0]

What did u do? What u tried to flash

Sent from my CUBOT_MANITO using Tapatalk

---------- Post added at 03:04 PM ---------- Previous post was at 03:03 PM ----------


Should have to do with Decrypt it's something else. Bad patch maybe. Phh is working with encrypted devices

Sent from my CUBOT_MANITO using Tapatalk

SuperSU removes "encryption" (fileencryptioninline) from the fstab, so if your /data is encrypted it won't decrypt at boot and you get a bootloop.
One could just change the script to not remove encryption.

 

[virtyx]

supersu root doesnt work with many apps, i removed it and installed phh instead and it works as it should.
somethings broken ??

 

[ante0]

supersu root doesnt work with many apps, i removed it and installed phh instead and it works as it should.
somethings broken ??

Can you give me a list of apps you can't use with SuperSU?
Except tibu and gsam battery, both of those are working for me.
Also, do you have SuperRoot installed now or "regular" Phh? If so from where?

 

[virtyx]

Can you give me a list of apps you can't use with SuperSU?
Except tibu and gsam battery, both of those are working for me.
Also, do you have SuperRoot installed now or "regular" Phh? If so from where?

Superroot sorry,

These are from the top of my head
Titanium backup 7.4.0.3 - only works with supersu newer versions do not but works fine in superroot
Gsam - same as above works in previous versions
Root explorer - only works in a few
Disable services - doesn't work

They all work fine once I flash superroot and use phh apk for root management

Im on c636b172

 

[eddmecha]

Superroot sorry,

These are from the top of my head
Titanium backup 7.4.0.3 - only works with supersu newer versions do not but works fine in superroot
Gsam - same as above works in previous versions
Root explorer - only works in a few
Disable services - doesn't work

They all work fine once I flash superroot and use phh apk for root management

Im on c636b172

u r from which country?just wondering due to u r on the latest b172

 

[virtyx]

u r from which country?just wondering due to u r on the latest b172

Australia

b172 is here http://hwmt.ru/oth/HWFF/info/view.php?find_model=

 

[ante0]

Superroot sorry,

These are from the top of my head
Titanium backup 7.4.0.3 - only works with supersu newer versions do not but works fine in superroot
Gsam - same as above works in previous versions
Root explorer - only works in a few
Disable services - doesn't work

They all work fine once I flash superroot and use phh apk for root management

Im on c636b172

I dunno what's wrong then. All of those work for me using SuperSU. Except for TiBu when it comes to apps not in /system/app or priv-app.

 

[gm007]

He has b172 that it's not release yet for public,could be they changed things in this new firmware.
Or it's an incomplete firmware missing updated hw_data.
And i think they patched something for root vulnerability

 

[virtyx]

He has b172 that it's not release yet for public,could be they changed things in this new firmware.
Or it's an incomplete firmware missing updated hw_data.
And i think they patched something for root vulnerability

HW_data was flashed post installing twrp (as is needed from wiping data)

 

[ante0]

HW_data was flashed post installing twrp (as is needed from wiping data)

I checked boot images and compared 176 to 156, not that much changed. A few lines here and there. One that caught my eye was persist.sys.huawei.debug.on, not sure what it does.

The RomAur seems to have problems with SuperSU as well. I should update to 176 just to check what's wrong.

 

[virtyx]

I checked boot images and compared 176 to 156, not that much changed. A few lines here and there. One that caught my eye was persist.sys.huawei.debug.on, not sure what it does.

The RomAur seems to have problems with SuperSU as well. I should update to 176 just to check what's wrong.

strange, i wouldnt of thought much would change from 156/8 to 176

 

[ante0]

strange, i wouldnt of thought much would change from 156/8 to 176

Android security patches, but worth a shot anyway

 

[virtyx]

Android security patches, but worth a shot anyway

why would they affect supersu root and not superroot?
let me look closer at my config it doesnt make sense.

edit: Definitely a supersu issue... i had a script that broke root that i thought may have caused the issue, removed it and still happens.
i can only root properly using the superroot method

 

[ante0]

why would they affect supersu root and not superroot?
let me look closer at my config it doesnt make sense.

edit: Definitely a supersu issue... i had a script that broke root that i thought may have caused the issue, removed it and still happens.
i can only root properly using the superroot method

Will know soon. Setting up phone now after installing b176...
They did change one thing. Play store is installed as a system app now
It wasn't in b138, not sure about b156.

 

[ante0]

why would they affect supersu root and not superroot?
let me look closer at my config it doesnt make sense.

edit: Definitely a supersu issue... i had a script that broke root that i thought may have caused the issue, removed it and still happens.
i can only root properly using the superroot method

Question: When did you install SuperSU?
Right after 172?
And did you format before installing it?

I do notice that if you format data after installing SuperSU, the SuperSU.apk is lost as it's installed to /data.
TiBu will say you have root, which is true, but you don't have any SU manager so you can't approve/deny requests.
Meaning apps will just say no root blah blah.

Edit: TiBu sure is strange. I think it's built-in busybox is very outdated.
Wouldn't restore first. Tried everything. Then installed Stericson Busybox and it magically works again.

 

[virtyx]

Question: When did you install SuperSU?
Right after 172?
And did you format before installing it?

I do notice that if you format data after installing SuperSU, the SuperSU.apk is lost as it's installed to /data.
TiBu will say you have root, which is true, but you don't have any SU manager so you can't approve/deny requests.
Meaning apps will just say no root blah blah.

Edit: TiBu sure is strange. I think it's built-in busybox is very outdated.
Wouldn't restore first. Tried everything. Then installed Stericson Busybox and it magically works again.

yes tried with wipe before and then did it without a wipe - same thing - supersu app is present both times though

busybox may be an issue but i already have jrummy bb working

the grant su dialog comes up as usual, i grant it, go to freeze an app and it says it froze it successfully - however the app doesnt go 'blue' to show it froze.

it says i have root and is working in some apps, but in others it refuses to work properly.

---------- Post added at 03:16 PM ---------- Previous post was at 03:15 PM ----------

Will know soon. Setting up phone now after installing b176...
They did change one thing. Play store is installed as a system app now
It wasn't in b138, not sure about b156.

sorry im on MHA-L29C636B172

 

[nitrate]

Does anyone know if "suhide" by Chainfire is compatible with this release of SuperSU for the Mate 9?

Gesendet von meinem MHA-L29 mit Tapatalk 2

 

[ante0]

Does anyone know if "suhide" by Chainfire is compatible with this release of SuperSU for the Mate 9?

Gesendet von meinem MHA-L29 mit Tapatalk 2

If you're trying to get Pokemon Go/Android Pay to work it won't, SafetyNet will still not pass.

Enabling it can be tricky. As we can't mount su.img, and /su is rewritten after each boot it needs to be included in the boot.img, and the scripts in SuperSU need to be edited as well.
So you can't install it with the suhide installer script.