yashsingh1/xdaforums huggingface dataset:
[SuperSU] Hal9k_:
Hi all.

I installed SuperSU v2.82 SR5 in Android 7.1.2 NHG47L and have this problem:

When I type su in the terminal, the system hangs up instead of showing a request for granting the root-rights.

If I disable the request for granting root-rights in the settings of SuperSU, the rights are granted.

In logсat is such a recurring error.

11-01 04:53:47.666: D/AndroidRuntime(6906): >>>>>> START com.android.internal.os.RuntimeInit uid 0 <<<<<<
11-01 04:53:47.672: D/AndroidRuntime(6906): CheckJNI is OFF
11-01 04:53:47.822: D/ICU(6906): No timezone override file found: /data/misc/zoneinfo/current/icu/icu_tzdata.dat
11-01 04:53:47.841: W/System(6906): ClassLoader referenced unknown path: /vendor/lib64
11-01 04:53:47.841: W/System(6906): ClassLoader referenced unknown path: /system/lib64
11-01 04:53:47.862: E/memtrack(6906): Couldn't load memtrack module (No such file or directory)
11-01 04:53:47.862: E/android.os.Debug(6906): failed to load memtrack module: -2
11-01 04:53:47.864: I/Radio-JNI(6906): register_android_hardware_Radio DONE
11-01 04:53:47.887: D/AndroidRuntime(6906): Calling main entry com.android.commands.am.Am
11-01 04:53:47.894: E/ActivityManager(1064): Activity Manager Crash
11-01 04:53:47.894: E/ActivityManager(1064): java.lang.NullPointerException: Attempt to invoke virtual method 'int java.lang.String.indexOf(java.lang.String)' on a null object reference
11-01 04:53:47.894: E/ActivityManager(1064):	at com.android.server.am.ActivityManagerService.checkBroadcastFromSystem(ActivityManagerService.java:18167)
11-01 04:53:47.894: E/ActivityManager(1064):	at com.android.server.am.ActivityManagerService.broadcastIntentLocked(ActivityManagerService.java:18785)
11-01 04:53:47.894: E/ActivityManager(1064):	at com.android.server.am.ActivityManagerService.broadcastIntent(ActivityManagerService.java:18876)
11-01 04:53:47.894: E/ActivityManager(1064):	at android.app.ActivityManagerNative.onTransact(ActivityManagerNative.java:502)
11-01 04:53:47.894: E/ActivityManager(1064):	at com.android.server.am.ActivityManagerService.onTransact(ActivityManagerService.java:2924)
11-01 04:53:47.894: E/ActivityManager(1064):	at android.os.Binder.execTransact(Binder.java:565)
11-01 04:53:47.899: I/art(6906): System.exit called, status: 1
11-01 04:53:47.899: I/AndroidRuntime(6906): VM exiting with result code 1.

Also I found an error in update-binary

To whom can I propose its correction?
[SuperSU] ktmom:
You could be pragmatic and use the contract info in the play store description.

"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
[SuperSU] osm0sis:
Supporting Pixel 2 is going to require AVB v2 signing. The signing utility, avbtool, is Python, so that's a bit trickier for on-device signing.
[SuperSU] DB126:
Where was it stated there would be no further development? I certainly agree the new custodians have missed numerous opportunities for community outreach (not a good start) but I am not ready to throw in the towel yet. New and legacy builds of SuperSU continue to meet my needs with zero issues. Magisk remains an option which can be executed at any time should SuperSU go rogue.
[SuperSU] wetxxx:
Hi guys. I have a problem with showmax aplication. This apk gave me a message that I have a rooted phone. I have root and S-OFF.

What is the best metod to hide my root?

"Live long and prosper"
[SuperSU] Didgeridoohan:
Two working options are:

SuperSU + suhide

Magisk
[SuperSU] xell75:
Is there any way to pass safetynet with SuperSU and SU Hide with Pixel Launcher 2 installed? Cause everytime I change Kernel to enforcing, the Launcher FC continuesly. I'm on Galaxy S4 with Android 8.0 AOSP Custom Rom.
[SuperSU] DodoGTA:
Quoting myself:
[SuperSU] xell75:
Thank you mate, it worked!
[SuperSU] wetxxx:
Safety Net was passed but still showmax doesn't work :(

"Live long and prosper"
[SuperSU] xell75:
My S4 Rom Got an update (Developer Preview 8.1 SDK27) Is SuperSU still working there, anyone tested with an Android 8.1?
[SuperSU] Ibuprophen:
Though this thread does fit your question but, you may want to consider posting this question within the following thread for feedback/recommendations from other GS4 users.

https://xdaforums.com/showthread.php?t=2192886

Good Luck!

~~~~~~~~~~~~~~~

I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.

PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
[SuperSU] citytrader:
Hello to all, with my Galaxy A7 2017 (A720F) Nougat after I install Supersu I get a lag of 5sec after I pattern unlock, uninstalling root solves the problem, is there any way to troubleshoot this so I can upload logs, etc, to solve the issue?

Thanks!
[SuperSU] martyfender:
Off topic, but those are some nice images there.

I was a professional school photograher, here in the United States, for 26 years, but that kind of photography was alway my real passion.
[SuperSU] Paschfire:
A logcat would probably be helpful.
[SuperSU] citytrader:
Logcat in the attachment (I did a pattern unlock and after that I took the logs)
[SuperSU] niko26:
Haha... I feel you. Were you able to get OTAs working via Flashfire?
[SuperSU] Josh:
Download factory image and you can flash it from Flashfire.
[SuperSU] Mulham82:
Guys .. Can I flash this build on LG G3 D855 based on Lingeage 7.1 or not?!

Thanks.
[SuperSU] niko26:
While keeping root?

Last few times I've tried it, I had a bootloop. :(
[SuperSU] ffejy462:
Yes. I've flashed every ota for the last few months (including 8.1) with flashfire. Keeping root is kinda the point of flashfire... The few times that bootloader or radios updated I used fastboot although.

Nexus 6p
[SuperSU] niko26:
Can you tell me the exact steps please? That would be really much appreciated. I wasn't able to install the OTAs and it was a pain in the a**.
[SuperSU] osm0sis:
Check out my FlashFire "Recipe Book" here: http://xdaforums.com/showpost.php?p=67124458&postcount=3480

FYI, OTA zips via FlashFire will update the radio and bootloader properly, so nothing to worry about there, it's only with factory images of those that it might be safer to use fastboot.
[SuperSU] peterlee928:
hi all... to confirm, sr5 works for the nov android update?
[SuperSU] jcsww:
Yes!
[SuperSU] osm0sis:
From further testing by [MENTION=4470081]topjohnwu[/MENTION] it seems that AVB v2 signing might not be enforced currently on unlocked Pixel 2 bootloaders, so that's good news... for now at least, since we know Google also likes to change the rules, sometimes month-to-month, like they did on the Pixel with AVB v1. ;)

Regardless, here's some fun I whipped up for anybody semi-savvy wanting to play around with on-device AVB v2 signing.

It's straight up using Python (all credit there to QPython) to run avbtool with a simple little wrapper script I wrote. This is labeled "-arm" because of this Python dependency, which is only built for ARM, but it should/does work on ARM64, and possibly x86 and x86_64 with the libhoudini compatibility layer. I'm not sure if MIPS/64 has a similar compatibility layer, so MIPS devices may be out of luck for now.

Unpack to /data/local/avbtool-arm or anywhere that isn't under /sdcard so that you can set executable permissions to my avbtool script and be able to run it.

Syntax is pretty straightforward, but it's complicated slightly by avbtool wanting the size of the partition so that it can pad the entire partition and place a footer at the end denoting the signature. So:

./avbtool add_hash_footer --image boot-new.img --partition_size $(wc -c < boot-original.img) --partition_name boot

where boot-new.img is your unsigned, repacked image, and boot-original.img is an untouched signed dump from the target device.

There's an embedded default testkey in avbtool, but I've also thrown in the other rsa testkey .pem files which can be used with some of the avbtool command-line options.

Happy hacking! :cowboy::cool:
[SuperSU] Andi17:
Hello all,

Sorry for my Bad question, but i read in a thread that chainfire will stop developing of supersu. Is it true or not? I hope not.

Thanks in advanced
[SuperSU] ktmom:
https://plus.google.com/+Chainfire/posts/6Sp6t9LxtQZ

"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
[SuperSU] Ibuprophen:
Unfortunately Chainfire has Retired from the SuperSU side of the development as he had announced it on his following G+ post.

https://plus.google.com/+Chainfire/posts/6Sp6t9LxtQZ

~~~~~~~~~~~~~~~

I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.

PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
[SuperSU] defens23:
Hi. just installed the latest November update to my XL.

Powered phone down.

Fastboot boot to twrp.

Flashed SuperSu config for systemless sbin.

Then tried to flash SU 2.82 sr5.

Each time I try to flash it I get an error at the end saying "failed to mount '/system' (device or resource busy).

Couldn't get root

Any ideas?

Flashed SU 2.82 sr3 and got same message at the end but when I hit reboot it did it's thing and I have root again.
[SuperSU] AP2FTW:
I don't believe SuperSU config is necessary any more...at least I'm pretty sure I read that somewhere and it wasn't listed in the steps I followed to root my XL
[SuperSU] Alxoom33:
I am not sure the rooting procedure on the Pixel XL. I know on the Pixel 2 XL it is much more complex than just flashing​ the SU 282 SR 5.zip. In fact we don't even have a working TWRP yet. It is just in the Alpha stage. You should probably read some in your device threads.
[SuperSU] peterlee928:
awesome!

flashed it and got an error message that it couldnt mount... but phone is rooted... am i missing something?

also... does latest version of stericson busybox pro work with the latest supersu?

much thanks! :)
[SuperSU] jcsww:
I don't use BusyBox but I had no issues flashing. All went as best to be expected.
[SuperSU] jcmm11:
I switched from stericson to osm0sis' version, but checking the play store for stericson the latest "What's new" says "Added Busybox 1.27.2, also added support for systemless root within sbin (Oreo support)" so it should work.
[SuperSU] peterlee928:
got it. i suspect the issue is with how supersu was flashed. i started by doing a clean install of the nov update. then fastboot boot twrp, then flashed sr5. but got the error message that it didnt mount. any thoughts as to what the issue is here and/or potential solution? much thanks in advance :)

EDIT

so as a point of reference, i flashed sr1 pixelfix on my verizon google pixel xl and stericson busybox withthe october update with no issues (either supersu mounting or busybox).
[SuperSU] defens23:
Thanks. I use SuperSU config because it's needed for SUhide otherwise I can't use Netflix or Directvnow because they block you from using the services if they detect root.

---------- Post added at 05:14 PM ---------- Previous post was at 05:12 PM ----------

Same issue I had. Said mount was busy but root finally worked after a couple of tries.
[SuperSU] peterlee928:
i am rooted also despite the error message. but because im having busybox issues, im wondering if that is stemming from the supersu error message... :confused:
[SuperSU] AP2FTW:
But I am using suhide to use Android pay and I didn't flash suconfig
[SuperSU] corkiejp:
If your using OREO, SBIN mode of supersu is the default, prior version you need suconfig to set that mode.
[SuperSU] peterlee928:
so the only version of supersu that seems to mount properly for me is sr1 pixelfix.

see attached screenshots.

busybox installs properly with sr1 pixelfix.
[SuperSU] galaxys:
TWRP Beta image and zip are out today for the Pixel XL 2!
[SuperSU] Alxoom33:
Unfortunately the Beta 1 and Beta 2 still having keyboard problems once installed.
[SuperSU] raymondbernard:
Tuck you and parsing trying to download twrp file funny:))
[SuperSU] Alxoom33:
Working great now. Key is to flash in TWRP both the TWRP.beta².zip and the Magisk 14.4.4.zip. All is working like Magisk ?
[SuperSU] Sheetzie03:
[MENTION=6617276]ktmom[/MENTION] so when he officially retires, will you all stop using SuperSU? If so, why?

Thanks
[SuperSU] Ch3vr0n:
He already has officially retired from SuperSU

Sent from my Nexus 6P with Tapatalk
[SuperSU] xell75:
I still stay with SuperSU so long it works. I'm on an Android Oreo 8.1-DP1 Custom Rom for my Galaxy S4 and SuperSU still works for me. I don't like Magisk, cause it never really worked for me and sometimes lose root all of sudden, that made me to reflash Magisk again. That's really a pain. So, so long SuperSU works without problems, I keep using it in combine with SUhide.
[SuperSU] ktmom:
I'm not sure why I got singled out for this question, but I'll answer ;)

I primarily use Magisk and have for quite some time. I occasionally re-root with SuperSu just to play.

The reason I started using Magisk was to become familiar with another option. I became a more consistent user because Magisk is an open source alternative and after the unannounced addition of the analytics debacle that became *much* more desirable. While the analytics were removed, the fact it was done and unannounced continues to make me uncomfortable. The extremely limited engagement here on xda over the last 2 years from any CCMT rep is another downside to me.

If SuperSu launched originally cloaked in this type of secrecy, I would have never used it. Thus, it makes sense that Magisk better suits my needs.

These are all my personal positions and I'm not advocating that anyone dump SuperSu because of my concerns. I'm sure it's possible to get to know the people behind ongoing development by spending more time on their forum. I just don't have any reason to put the effort in to it.

"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
[SuperSU] srqrob:
I read item after item on the quirks of Magisk. It's SuperSU for me until I find a reason to switch. "It just ain't broke."
[SuperSU] DB126:
Excellent post that likely mirrors the perception of many others (certainly mine). There is no 'right' answer but understanding the considerations of others can go a long way to shaping ones own views.
[SuperSU] IronTechmonkey:
Well said. At the risk of a bit of off topic, but something CCMT should know: Apart from the trust issues you and others have mentioned...

The moment (now several months or a year ago) when an official Play Store update caused problems and loss of data on a wide scale and was followed by an apology at the Play Store page that said "we" are sorry, may have been a watershed moment. It was not reassuring for that to have been the first statement I had ever seen CCMT make after their introduction.

At the time I had no choice but switch to LOS SU, but as you mentioned, I still explore SuperSU and Magisk in the interest of knowledge and am not advocating that people jump ship, just that they be informed.
[SuperSU] martyfender:
I, for one, agree with you. I tried the 2 previous offical releases of magisk on my 6.0.1 tablet and in both versions I lost root in less than 24hrs of using it.

I have used supersu through many, many beta versions and not once have I lost root with it. The cases where I had problems with it were when I had with it were solved by using osmosis's unsu and reflashing the supersu.zip in twrp.

In my particular case I had used the unofficial supersu system mode zip and decided to use the official systemless version.

however, I had no apparent problems with the system mode version, osmosis stated that I should be using the official, not the hack version of supersu.

Another, (not named developer) stated that osmosis has it all wrong, that true root is when it is in system mode and that systemless is a "hack" to get root on newer os's.

I will let the masses decide who is right. chainfire obviously had a very good reason to to do it the way he did it for android 6 and later.

Apparently sbin mode is the current mode for android 7, 8 and later?

Please add your thoughts on this for any better info, opinions and better insight on this.
[SuperSU] Ch3vr0n:
sbin mode is only default on 8, but can be manually done on 7
[SuperSU] KaMyKaSii:
I'm not an expert but I believe basically that the SuperSU installer used to do was add their binaries to system partition and the SuperSU app was the "bridge" between the apps (which you allow) and the binaries that will give superuser elevation. The end of the "SuperSU system mode" era started with selinux making things difficult, so the boot.img ramdisk should also be modified to workaround it. But since we are going to have to modify ramdisk, why not make it load the binaries in another location (/data) than /system? This will make it easier for users to apply otas and also make it difficult for apps to detect the rooted device, since /system has global read permission and /data don't, because it is a private partition

SBIN mode is the default installation on Oreo, but can also be used in Marshmallow and Nougat as long as the user sends the terminal command
[SuperSU] g465559090:
@Chainfire supersu 2.82 SR5 cannot work properly on mate10 devices

Please excuse my poor English

After HUAWEI mate10 brushes into supersu2.82 SR5,

Open supersu prompt without obtaining root permission

But use

ADB shell

$su

Stuck in here, does not appear #

If you uninstall supersu, then execute it

ADB shell

$su

#

There will be root

I'm sorry, I don't have permission to publish pictures

bbs.xxroot.com/data/download/1.jpg

bbs.xxroot.com/data/download/2.jpg

bbs.xxroot.com/data/download/3.jpg

Sorry, I can only send pictures to other forums, the above is the web site!
[SuperSU] ktmom:
What ROM are you on? Is it pre-rooted or rooted before with a different root?

"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
[SuperSU] g465559090:
I do not ROM, I was directly on the official system of the root brush into the brush, after installing the supersu program,

using the ADB shell Su computer implementation, does not appear #

If you uninstall supersu, then execute ADB shell Su, there is root
[SuperSU] peterlee928:
apologies for beating the dead horse... but has anyone had issues with sr5 failing to mount properly? if so, any solutions? i have searched but havent found any answers. much thanks in advance for any help or guidance :)
[SuperSU] srqrob:
I have been using SR5 on my Pixel XL since it's release. I use root for basic functions like TiBU and TWRP and Root Explorer. I have had no issues through the current 8.0 November updates. Google store device.
[SuperSU] peterlee928:
i reflashed the factory image.

fastboot boot twrp img.

installed twrp 3.1.1-1.

rebooted to system.

reboot to recovery.

flashed sr5.

reboot to system.

then flashed busybox to /system/xbin.

everything working all good now.
[SuperSU] Ch3vr0n:
then you modified /system and will have to flash either the factory image AGAIN before an OTA or the system.img. There's a reason SuperSU is systemless if the rom supports it.
[SuperSU] DB126:
Modifying the system partition is fine if applying OTA/incremental updates is not important.
[SuperSU] peterlee928:
yep i flash factory image every month. so its par for the course for me.

[MENTION=5488402]Davey126[/MENTION] great to see you back on xda!! couldnt stay away huh? :)
[SuperSU] DB126:
A rugged patch with unexpected (favorable!) outcome. Treading lightly; staying close to home. Gotta think some very generous commentary had something to do with that. Enough OT; get back to work. :)
[SuperSU] peterlee928:
yessir :) glad to hear the good news!
[SuperSU] raymondbernard:
Hey I can't seem to flash on my smj320 Samsung have .img file for magisk manager app to try to root this phone but it won't flash the img file can you please help or get [MENTION=4899305]ashyx[/MENTION] to help please
[SuperSU] shaggyskunk:
Unless I missed something - You realize that this is a SuperSU thread and Not Magisk...?

Sent from my SM-G955W ??
[SuperSU] raymondbernard:
Yes I did I have su super user but I can't pm the maker of magisk and twrp thread so I came here
[SuperSU] shaggyskunk:
Well you should be posting your Magisk issues here:

https://xdaforums.com/showthread.php?p=68034103
[SuperSU] Ibuprophen:
I just wanted to share the following information in case anyone was wondering "Where in the world is Chainfire"? :)

If you look at Chainfire's profile, you'll notice the following statement:

"I have retired from developing SuperSU, and am currently taking a break from devving in general"

So I'm just assuming that he may be monitoring but, not actively engaging within the Forum.

I'm just hoping that he'll be back after the holidays but, I hope that [MENTION=631273]Chainfire[/MENTION] and his loved ones have a VERY HAPPY HOLIDAYS. He deserves it!!!

I also hope that everyone, and of course your loved ones, here has a HAPPY HOLIDAY Season!!!

~~~~~~~~~~~~~~~

I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.

PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
[SuperSU] osm0sis:
Any SuperSU rooted Pixel (i.e. last year's) users in here with a Windows PC who can give me a hand testing the upcoming Android Image Kitchen v3.0?

No answer in my thread so I imagine there aren't any Pixel users lurking there at the moment, but I know there's got to be a couple in here.. ;)
[SuperSU] joe1349:
SuperSU v2.82 SR5

sm-a720f (7.0) thank for works :o:o
[SuperSU] shag_on_e:
I have up my 6p to get the Pixel 2xl but I'll certainly be using AIK for this if possible. Gotta root and remove this stupid forced encryption if that is even still possible. I kinda miss the old days flashing whatever I wanted without mega security.
[SuperSU] osm0sis:
[MENTION=6842057]nathanchance[/MENTION] and I have got AIK-mobile on the Pixel 2 for sure working after 4 hours of debugging the crazy loop mount commands behavior which doesn't occur on any other devices I've seen.. it was truly crazy and many many thanks to him for bearing with me.

I haven't gotten any replies from any OG Pixel owners though, so I still need someone to help test there. Any takers?
[SuperSU] peterlee928:
fyi so in case anyone was wondering, i flashed the factory image without "-w".

then:

fastboot boot twrp img

install twrp 3.2.0.0

reboot to system

reboot to recovery

install supersu (latest beta)

reboot to system

delete busybox pro

(all busybox references are to the stericson version)

reinstall busybox pro (default set to /sbin/supersu/xbin)

let that run to completion

change the install destination to /system/xbin

reinstall busybox pro

click on the settings option

everything working ok thus far
[SuperSU] jcmm11:
Just curious. You have 2 copies of busybox installed, one to /sbin/supersu/xbin and one to /system/xbin ? If so why? If not then I misunderstood your first reinstall line.
[SuperSU] peterlee928:
so technically, what i did was install the jrummy busybox first. that worked and automatically installed to /system/xbin.

but just my preference is to use stericson. so i deleted jrummy. then installed stericson busybox pro. that installs automatically to /sbin/supersu/xbin. so then i change the path to /system/xbin and reinstall again. then i go to settings and check the box that says "busybox will on every boot be removed from /sbin..."

im sure theres a more efficient way to do it... but this roundabout method worked for me.
[SuperSU] RichardEb:
When will you release a stable that supports Android 8?
[SuperSU] osm0sis:
When CCMT stops dropping the ****ing ball. :(
[SuperSU] sharkie405:
Is there a website where we can check on CCMT progress on SuperSU, if there is any?
[SuperSU] IronTechmonkey:
Ha. "...we apologize <for your lost data...>"

Sorry for the OT but been meaning to mention for a while that it is so nice to have access to your toys. Thanks for the digital playground.

[EDIT] Woops, more OT than I realized, as I thought this was in your thread. With apologies to Chainfire who's digital playground many of us grew up in.
[SuperSU] DB126:
You'd be better off going with Magisk. I am partial to SuperSU but the project has pretty much ground to a halt under CCMT's (cough) leadership.
[SuperSU] osm0sis:
I've got Magisk on a couple of my devices, but I'll probably keep using SuperSU on my daily driver until it stops working, even if there is no further development by CCMT.