[BETA][2017.10.01] SuperSU v2.82 SR5

The Analog Kid · Jan 5, 2018

Alxoom33 said:
He has an XDA thread.

Alright. Finally used @osm0sis unSU.zip, reverted back to stock kernel (was on @flar2 ElementalX), cleared caches, rebooted back to TWRP, flashed ElementalX back again, flashed v2.82-SR5 once more and rebooted... just to find a tiny little mess. Although a couple apps normally requested root permission, "root checker" was telling me no root was present, as well as most other root apps. Weird. Rebooted to no avail and apps started to close in sequence. Decided to reflash SuperSu once again, rebooted and now things are working as expected, SuperSu included. As to what caused the initial no log, SuperSu crashing issue, my guess is that it was some clean up I did with SDMaid, probably getting rid inadvertently of some useful thing related to SuperSu. Not sure... Whatever, thanks for the suggestion.

Sent from my Moto G4 Plus using XDA Labs

mwilky · Jan 5, 2018

Seems like latest sepolicy blocks dex2oat accessing data/dalvik-cache/arm and data/dalvik-cache/arm64 folders. I've tried

/sbin/supolicy --live \
"allow dex2oat dalvikcache_data_file file { write read execute }" \
"allow dex2oat dalvikcache_data_file dir { write read execute }" \
"allow dex2oat dalvikcache_data_file dir create_dir_perms" \
"allow dex2oat dalvikcache_data_file file create_file_perms"

And a few others to no avail, anyone know if it is possible?

dswwong · Jan 6, 2018

Supers zip

khelaf · Jan 6, 2018

:good:

Eures · Jan 7, 2018

Hello, I have a question: is the SuperSU-v2.82-20170528234214-TEST-1.zip (for Xperia users) rolled out in the SR5-SuperSU-v2.82-SR5-20171001224502.zip? In other words, can it be said that the former is obsolete?...

SlimSnoopOS · Jan 8, 2018

Eures said:
Hello, I have a question: is the SuperSU-v2.82-20170528234214-TEST-1.zip (for Xperia users) rolled out in the SR5-SuperSU-v2.82-SR5-20171001224502.zip? In other words, can it be said that the former is obsolete?...

Depends but likely yes. Whenever Chainfire would release test zips for specific issues, if it fixed issues then he'd incorporate that into his next SR# zip. Try SuperSU beta SR5 just know that there's no further support if anything goes awry.

Sent from my Nexus 5X using Tapatalk

Marsh-mallow · Jan 8, 2018

Guide to Root Nokia2

I am asking that which app is compatible to root Nokia 2 smart phone?

GetOffMyLawn&!+¢#{$ · Jan 9, 2018

arter97 said:
f2fs with Android story is always complicated.

So why is SuperSU broken with many custom ROMs:
systemless SuperSU saves a raw ext4 image in /data/su.img and mounts it as a loopback device and to various locations upon boot.
The problem with f2fs, is that most kernels included in custom ROMs have issues with managing loopback devices.
This is not SuperSU issue, rather, kernel developers has to incorporate the necessary fix for f2fs.

This “fix” is rather dumb :
https://git.kernel.org/cgit/linux/k...y&id=0d5ed69805ee57d7b416c4a6b47c3b67284db105

The f2fs head, Kim Jaegeuk forgot to add those pointer to post-4.10 versions of f2fs backports.
(The stock OnePlus 3T’s kernel source code seems to already have this fix. This explains why OxygenOS didn’t have any issues with SuperSU.)
So you have 2 choices :
A. Cherry-pick that fix separately
B. Merge f2fs version all the way up to 4.10(latest f2fs-stable.git is updated to 4.10)

But there are more stories to be told, unfortunately.
Both 2 methods introduce a new problem : breaks all previous f2fs versions to read the data.
There is no on-disk-format change introduced by the new “fix”, but it turns out that older versions of f2fs has an issue which is exploited only when newer version of f2fs is used to write data.

You need this additional fix, if you have no intention to update f2fs to the latest 4.10 version :
https://git.kernel.org/cgit/linux/k...y&id=7a895023cc2c06c08a6cccb71e112255eb0837ee

Without this fix, the kernel will panic upon reading any data.

So we took care of the method A.
However, there is still an issue with method B : deadlock.

As noted in https://review.lineageos.org/#/c/95316/ , there are deadlocks present on the latest version of f2fs(from 4.8, iirc).
It took about a month to bisect it, and I got the culprit commit :
https://git.kernel.org/cgit/linux/k...y&id=de62dad6f502c67fd01b5c0b1f7f242836ce90d0

I’m still yet to hear from the upstream developers, but I can confirm that reverting that commit fixes the deadlock.
Our internal AOSPA builds are running on 4.10 f2fs with that commit reverted.

TL;DR
It’s not @Chainfire 's fault.
You have to ask the kernel developer to fix the issue.
2 methods for the kernel developers

A. Incorporate only the necessary 2 fixes to fix loopback images :
https://git.kernel.org/cgit/linux/k...y&id=0d5ed69805ee57d7b416c4a6b47c3b67284db105
https://git.kernel.org/cgit/linux/k...y&id=7a895023cc2c06c08a6cccb71e112255eb0837ee

B. If you want to upstream f2fs to the latest 4.10, revert this to avoid deadlock :
https://git.kernel.org/cgit/linux/k...y&id=de62dad6f502c67fd01b5c0b1f7f242836ce90d0
(A little credit would be appreciated, as it took me a frustrating month to bisect this)

Thanks.

I just thought some of you might like to see this.
Edit: I almost forgot, I did give credit and linked the post.
Sent from my Moto E (4) Plus using XDA Labs

Razor10707 · Jan 13, 2018

Hey sorry this Will most likely sound nooby but I didn't used supersu alot till Now

No matter which version I choose either Way doesnt work if I used a version 2.80 or before it fails in the flashing procedure at patching sepolicy failure aborting

Or if I use v2.82 sr2 or sr5 they both flash but then ask for binary update which fails and even after relfashing in twrp still nothing fixes it

My device is a p9 liter (vns-l21c432)
Running Elite rom 7.3

TIA.

ktmom · Jan 13, 2018

@Razor10707, I take it you tried 2.80 then tried newer versions? How did you remove the previous flash before flashing the next version?

I'd first do a nandroid backup, then dirty flash your ROM again to get everything back to a known condition. Boot first to make sure everything is working then try SR5 and see if it flashes correctly.

"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers

Razor10707 · Jan 14, 2018

ktmom said:
@Razor10707, I take it you tried 2.80 then tried newer versions? How did you remove the previous flash before flashing the next version?

I'd first do a nandroid backup, then dirty flash your ROM again to get everything back to a known condition. Boot first to make sure everything is working then try SR5 and see if it flashes correctly.

"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers

Yes I tried older versions but as I said other Than 2.82 all fails at flashing in recovery only 2.82 gets trough that but it fails at binary update

deloj · Jan 14, 2018

After I dirty flashed Nougat and Odined TWRP, I still cant get root. I Odined SuperSu but after that I got this message: "Verification Failed, Unable to restart your device. The Integrity verification has failed. You need to reset your device to factory default settings. This will erase all your data."

I then dirty flashed Nougat and everything is ok. But I still dont have root. I used this SuperSu: SR5-SuperSU-v2.82-SR5-20171001224502.

What do you suggest to get root?

.

Badger50 · Jan 14, 2018

deloj said:
After I dirty flashed Nougat and Odined TWRP, I still cant get root. I Odined SuperSu but after that I got this message: "Verification Failed, Unable to restart your device. The Integrity verification has failed. You need to reset your device to factory default settings. This will erase all your data."

I then dirty flashed Nougat and everything is ok. But I still dont have root. I used this SuperSu: SR5-SuperSU-v2.82-SR5-20171001224502.

What do you suggest to get root?

.

Since SU is no longer being activity developed at this time, you might wanna try this.

https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

Razor10707 · Jan 14, 2018

ktmom said:
@Razor10707, I take it you tried 2.80 then tried newer versions? How did you remove the previous flash before flashing the next version?

I'd first do a nandroid backup, then dirty flash your ROM again to get everything back to a known condition. Boot first to make sure everything is working then try SR5 and see if it flashes correctly.

"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers

Thanks for your help i kinda fixed it now i have root only thing doesn't work is Ksettings but I'm gonna deal with that later

ktmom · Jan 14, 2018

deloj said:
After I dirty flashed Nougat and Odined TWRP, I still cant get root. I Odined SuperSu but after that I got this message: "Verification Failed, Unable to restart your device. The Integrity verification has failed. You need to reset your device to factory default settings. This will erase all your data."

I then dirty flashed Nougat and everything is ok. But I still dont have root. I used this SuperSu: SR5-SuperSU-v2.82-SR5-20171001224502.

What do you suggest to get root?

.

What jumps out at me is that you used odin to flash SuperSu. I stay away from Samsung devices but even for Samsung I don't think using odin is right. SuperSU gets flashed in twrp.

"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers

saspo59 · Jan 14, 2018

Hi ,i am on 1+3t Nos 8.1 ,was running magisk till now i wish to try su ,i unindtalled magisk and installed SR5-SuperSU-v2.82-SR5-20171001224502.zip
I am rooted cose all apps that need root work and ver root app says all ok but i don't see any kind of su app in app drow do i need to install another app tu see something
Thanks

Sent from my ONEPLUS A3010 using Tapatalk

ktmom · Jan 14, 2018

saspo59 said:
Hi ,i am on 1+3t Nos 8.1 ,was running magisk till now i wish to try su ,i unindtalled magisk and installed SR5-SuperSU-v2.82-SR5-20171001224502.zip
I am rooted cose all apps that need root work and ver root app says all ok but i don't see any kind of su app in app drow do i need to install another app tu see something
Thanks

Sent from my ONEPLUS A3010 using Tapatalk

How did you uninstall Magisk? It's often a good idea to dirty flash your ROM after removing systemless root.

Have you checked in your settings for root management? Some ROMs don't show the app in the app drawer but rather put it in settings.

In the SuperSu zip file, in the common folder is a copy of the apk. You could try installing that.

"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers

saspo59 · Jan 14, 2018

ktmom said:
How did you uninstall Magisk? It's often a good idea to dirty flash your ROM after removing systemless root.

Have you checked in your settings for root management? Some ROMs don't show the app in the app drawer but rather put it in settings.

In the SuperSu zip file, in the common folder is a copy of the apk. You could try installing that.

"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers

Thanks for repaying now all ok with su app ,one more question why titanium backup app says there is no root and it dosnt open

Sent from my ONEPLUS A3010 using Tapatalk

ktmom · Jan 14, 2018

saspo59 said:
Thanks for repaying now all ok with su app ,one more question why titanium backup app says there is no root and it dosnt open

Sent from my ONEPLUS A3010 using Tapatalk

Double check that TiBu was granted root access. If it's listed as denied, then it won't prompt again, TiBu just reports no root access.

An app can get listed as denied if it requests root and the request times out. While you were having trouble with the SuperSu app, if you opened TiBu, then that's when the request timed out.

"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers

saspo59 · Jan 14, 2018

ktmom said:
Double check that TiBu was granted root access. If it's listed as denied, then it won't prompt again, TiBu just reports no root access.

An app can get listed as denied if it requests root and the request times out. While you were having trouble with the SuperSu app, if you opened TiBu, then that's when the request timed out.

"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers

Thanks,its not listed and wasn't denide just directly says it not detect root did i have to instal it as system app there is an option for that in setting

Sent from my ONEPLUS A3010 using Tapatalk

[BETA][2017.10.01] SuperSU v2.82 SR5

Senior Member

Recognized Developer

Senior Member

New member

Senior Member

Senior Member

Member

GetOffMyLawn&!+¢#{$

Guest

Attachments

Senior Member

Retired Forum Moderator

Senior Member

Senior Member

Senior Moderator / Moderator Committee

Senior Member

Retired Forum Moderator

Senior Member

Retired Forum Moderator

Senior Member

Retired Forum Moderator

Senior Member

Similar threads

Top Liked Posts