yashsingh1/xdaforums huggingface dataset:
[SuperSU] zer0se7en:
I was replying to those other guys. Sorry. I even thumbs up'd your comment. And thanks for the answer. I already figured it out myself after seing the replies of others earlier that hey rather reply with insults and scolding with soooo many words than to just type one word = TWRP 3.1.1.0.

If only they did replied accordingly... But they rather chose to boast about their knowledge and highness. Oh well. Stupid of me to think they would be kind enough.
[SuperSU] matt4321:
I've cleaned up the thread a bit, let's relax a little. In a thread with 1000s of replies it can be difficult to find answers, however please try to search (using Google or the in thread search) and look for recent answers. At the same time it isn't necessary to slate users for asking questions, you don't need to spoon feed but a point in the right direction never hurt anyone.

Let's all chill a bit and hope you're having a good day :D

Matt

Senior Moderator
[SuperSU] corkiejp:
Don't have a Pixel, but managed to install busybox to correct path using BusyBox meefik version on my Nexus 9!
[SuperSU] kiloe:
I cant find the md5sum for v2.82 sr3 on the download page. Has anybody else found it?
[SuperSU] bggold:
Just flashed with no wipe on my pixel xl O official release and before I flashed supersu 2.82 sr3 and suhide v1.08 I ran the phone for a good hour and no issues. Just flashed supersu and suhide with modded twrp and phone started to lag a few mins after reboot and becomes unresponsive and will eventually reboot.

I uninstalled suhide to test and it still is doing it. Chainfire I will PM the ps -A screen shots. Let me know if you need anything else. This is my test pixel so I will not restore my 7.1.2.

UPDATE: I think I figured out the issue. I had to remove all previously approved apps from SuperSU and grant them permission again. So far so good, installed suhide and pass SN.

Thanks
[SuperSU] DB126:
There are many sources; I tend to use APKMirror which is both trustworthy and well provisioned (including common hash values). SuperSU page here. Of course you don't have to download from APKMirror once you secure the MD5 but there are no strings attached other than the normal ad blitz for free download services (which I block in favor of an occasional donation).
[SuperSU] dyingearth:
Confirm. I manually flash recovery to twrp-3.1.1-0-angler.img and then applied SuperSU-v2.79-SR4-20170323220017-ODP1-5X-6P.zip. Busybox seems to be working as well.

The only thing that doesn't work is JRom's root check, but I don't think that's necessary anymore.
[SuperSU] badhabit_wb:
I noticed my Pixel was lagging after dirty flashing 8.0 too. I re-flashed and wiped and then flashed supersu rebooted, and flashed suhide. Then I loaded all my programs again. Works great. I was on 8.0.0 beta and it was working great before I dirty flashed 8.0.0 on top. Might want to wipe it and reflash 8.0.
[SuperSU] KaMyKaSii:
It would be good for you to test the most up-to-date SuperSU and report any errors
[SuperSU] Alxoom33:
You're welcome!

I didn't notice you thumbed up my response and thought your remarks we're directed at me. I really dislike those who try to show how smart they are by bullying someone who is asking a simple question, instead of trying to help.

It would be so much nicer if he provided some helpful information and a polite suggestion for searching for additional information, like the Mod, above.
[SuperSU] bggold:
My test pixel has been stable for the past 3 hours. No sign of lag or lockups. Clearing supersu seemed to do the trick. I have a feeling it did not like something from N. I never had to do that between upgrades on N. Hopefully someone else can confirm.

Did you try that before doing a wipe?

My phone would take days to set backup. That's why I have a test device and use flash fire religiously. I like to try to figure out the issue if possible before a wipe.

As a matter of fact I am doing a backup and will restore and try the process once more on the test then off to the races to upgrade my daily driver.
[SuperSU] badhabit_wb:
I didn't try clearing supersu. That may, or may not, have solved it.

It takes a while to set back up but I have a checklist and I just do it after work while I'm watching tv with my wife...
[SuperSU] holla420:
Well there is a viper4arise which is basically the same. Works on Oreo. Just follow this thread... https://xdaforums.com/showpost.php?p=73323347&postcount=49
[SuperSU] bggold:
I think there is a post in chainfires supersuconfig forum he has the path to use to install BusyBox. I used it and installed BusyBox successfully on my pixel in both N and O.

Here it is. /sbin/supersu/xbin
[SuperSU] _alexndr:
There is another random issue. I didn't write about it before because I wasn't sure that this is root-related. Now I'm 100% sure, but correct me if I'm wrong (maybe I'm just lucky?). Quote from my thread:

It occurs also after about 1 per 10 reboots (see attachment).

I was very desperated to check if it is root-related - just did "Full unroot" in SuperSU and performed >40 reboots (at this moment) - everything is perfect, no such issue!

I'm going to do 100 reboots in sum to rule out that I was lucky - will write about the results :cowboy:

BTW

My Multi CSC ROM based on Android L is unmodified - all permissions / symlinks / SELinux contexts are exactly mapped from original pure BNL2 stock (odin version). I do not use any kitchen - I'm doing everything manually
[SuperSU] xdamami:
Just write supersu zip I have everyday after reboot this issue.
[SuperSU] _alexndr:
I'm not sure what you mean by that. So do you confirm that

such issue exists and is root-related

? Please try to unroot the phone if you can (using "Full unroot" option in SuperSU). I'm not forcing you, just suggest...
[SuperSU] scanno:
[MENTION=631273]Chainfire[/MENTION]

This is what i get when i do a : adb shell " daemonsu --restart"

F/libc ( 4088): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x0 in tid 4088 (daemonsu)

I/DEBUG ( 123): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***

I/DEBUG ( 123): Build fingerprint: 'Android/omni_manta/manta:5.0.1/LRX22C/menno12080135:userdebug/test-keys'

I/DEBUG ( 123): Revision: '8'

I/DEBUG ( 123): ABI: 'arm'

I/DEBUG ( 123): pid: 4088, tid: 4088, name: daemonsu >>> daemonsu <<<

I/DEBUG ( 123): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0

W/NativeCrashListener( 407): Couldn't find ProcessRecord for pid 4088

I/DEBUG ( 123): r0 00000000 r1 00000000 r2 00000010 r3 00000000

E/DEBUG ( 123): AM write failure (32 / Broken pipe)

I/DEBUG ( 123): r4 be851970 r5 00000000 r6 00000000 r7 b6ff0122

I/DEBUG ( 123): r8 00000002 r9 be851a38 sl 00000000 fp b6ff703c

I/DEBUG ( 123): ip b6fbf7fc sp be8518e0 lr b6f9ed55 pc b6f7c2c8 cpsr 400f0030

I/DEBUG ( 123):

I/DEBUG ( 123): backtrace:

I/DEBUG ( 123): #00 pc 000132c8 /system/lib/libc.so (strlen+83)

I/DEBUG ( 123): #01 pc 00035d51 /system/lib/libc.so (sscanf+52)

I/DEBUG ( 123): #02 pc 000028df /system/xbin/daemonsu

I/DEBUG ( 123): #03 pc 00011ee5 /system/lib/libc.so (__libc_init+44)

I/DEBUG ( 123): #04 pc 00003374 /system/xbin/daemonsu

I/DEBUG ( 123):

EDIT: perhaps i know the reason.... could this be CCACHE related (2 seperate source trees, 1 for manta and 1 for opo - because of CAF) guess i should have cleaned CCACHE ...
[SuperSU] Frank Westlake:
With Android Terminal Emulator (now Terminal Emulator for Android) you can make a desktop shortcut for that command to simplify fixes until the problem is resolved.

Frank
[SuperSU] Chainfire:
Broken pipe issues are expected by su and usually dealt with... have a link to your exact build ?
[SuperSU] scanno:
https://www.androidfilehost.com/?fid=95832962473399539
[SuperSU] Chainfire:
Yeah I have seen this one as well occassionally. I'm pretty confident this issue is either directly related to or caused by the same problem as the SuperSU issue.
[SuperSU] itechengine:
Works perfectly fine with my SGS 5 with Android L. Installed SuperSU v2.38 with Twrp 2.8.1.0 The one issue i found is with Titanium Backup, it doesn't able to recognize root privileges
[SuperSU] tinko975:
In xtrestolite rom, works good. No root errors on reboot .
[SuperSU] edreams:
I'm very happy since yesterday with this new SuperSU v2.38. I can get root access permanently on my official GALAXY S5 Polish Lollipop ROM and TWRP 2.8.2.0

Thanks so much Chainfire !!!
[SuperSU] Lammy696:
Keep getting "error:device not found" after trying the adb shell daemonsu --restart

Can't for the life of me get it to root
[SuperSU] Alex_rac:
Xperia Z2 Root permissions fix

[MENTION=631273]Chainfire[/MENTION]

Hi mate

everytime that we Xperia Z2 owner try to update the superuser we get problem

so ive compared my system dump before and after the problem and i ve found that the file causing the issue is the " install-recovery.sh "

i ve attached the file to solve the problem ( using that everything work fine )
[SuperSU] Chainfire:
v2.39 beta out now! BETA-SuperSU-v2.39.zip

Should work better on SGS5 5.0. Please let me know. I've had an auto reboot/launch su/check root/log loop running all night and I haven't had a single case of lost root. Unfortunately this doesn't prove anything. So let me know if you guys still have trouble.

An issue with truly permissive Lollipop ROMs (like Omni5) has also been fixed.
[SuperSU] Chainfire:
You should put the antiric call in install-recovery-2 as noted in the script. And note that this will break on Lollipop.
[SuperSU] beton87:
Confirmed fix on OmniRom 5.0.1 on Find 7a.
[SuperSU] Frank Westlake:
Yes, it might not be clear in the script but 'install-recovery-2.sh' is for us to create and use.

Frank
[SuperSU] hrh_fourtyseven:
thank you chainfire

finally 2.39 worked!

2.38 didnt work for me at all but 2.39 working like a charm.I tried 5 reboot,shutdown, power on... and working...
[SuperSU] goran_oh:
2.39 work like charm.
[SuperSU] MrKiasu:
I had the same laggy performance. A brief look at top suggested it's actually a memory usage problem - all the CPU is going to kswapd and memory consumption is very high.

I had to clear out the contents of /data/adb/su to fix it. It was not sufficient to delete records in the supersu app or to clear the supersu app data.
[SuperSU] bggold:
Good to know.

Thanks

---------- Post added at 05:42 AM ---------- Previous post was at 05:40 AM ----------

Good to know

Thanks
[SuperSU] pellajl:
I have a Galaxy Tab S (SM-T700) with the stock MM firmware but rooted using this SuperSU method.

Recently, an app I had was updated and all of a sudden it decided to throw up an error saying it will not run on a rooted device. That's fine....

I decided t try the suhide-lite v1.08 app to try an hide root from this app. The same app runs on my rooted Galaxy S5 with Magisk root installed.

I installed suhide-lite v1.08 and had an issue with suhide which I overcame by performing a manual install of the apk file. I proceeded to hide the offending app and then opened the app. The app still detected root and would not run.

I decided to try a little experiment on an app that I know had been granted root access. (ES File Explorer Pro). I opened the SuperSU app and removed ES File Explorer Pro's root permission. I then opened ES File Explorer Pro , disabled root access under settings and rebooted the tablet.

Once the reboot was completed, I opened up ES File Explorer Pro and switched the Root Explorer option on. After a couple of seconds, the Grant/Deny dialog box popped up and I chose to "Deny" access.

To my surprise, I was still had root access able to browse all folders and to also open text files for editing. Having denied root access to ES File Explorer Pro's, I would not have expected to be able to access root.

Is this a bug with the SuperSU app or have I messed things up by installing suhide?
[SuperSU] dyingearth:
Just flashed to factory (while not wiping) and try again. And it works again.
[SuperSU] DB126:
Can't directly answer your question but will comment ES File Explorer does not play nice on many devices and often exhibits questionable behaviors. The digressions started after the developer sold out to a company with a less than stellar track record. Exercise caution using this product to demonstrate root capabilities. Obviously not relevant to your immediate concern as denying access should have blocked root access. Then again, it's ES File Explorer ... (ugh).
[SuperSU] pellajl:
Thanks for the heads up on ES File Explorer.

I'll retest with Root Explorer and see what happens.
[SuperSU] KaMyKaSii:
I recommend the FX file manager, it's the best I've found and I've been using it for over a year

https://xdaforums.com/showthread.php?t=1253399
[SuperSU] mssam:
Yeah, fx, MiXplorer and solid file explorer are tops these days. ES is probably good for the Fire TV, that's about it...
[SuperSU] chazall1:
MiXplorer by far is the best FE that I have used.

Give it a try
[SuperSU] user2k10:
Deleted
[SuperSU] Sh0X31:
Hi,

What I do:

Flash Bootloader & Radio via fastboot

Flash Android Oreo (fastboot update image.zip)

After successful flashing I boot directly into bootloader

Flash SuperSU (sr3) & reboot

result
[SuperSU] KaMyKaSii:
First, you should have booted Android at least once to make sure that the installation occurred well, it is not possible to say that the culprit is the SuperSU just because it was involved. Second, did you actually install SuperSU through the bootloader (fastboot?)? Did not you install it by TWRP?
[SuperSU] Sh0X31:
Bootloader and radio are flashed with ADB.

When I boot it up, my device is encrypted :(
[SuperSU] Maurice84:
Device: Google Pixel XL, Oreo 8.0.0, SuperSU v2.82 SR3

Kernel: Stock

Problem: HiroMacro not working in Oreo

Steps: Install HiroMacro, Go to Settings > Macro ActionKey > Add a button on the screen. Go back and press Start, nothing happens (it should display a gray rectangle on the left side).

I've enabled logging in SuperSU and It shows the following problem after a lot of chmod 666 lines:

chmod: /android/dev/uinput: No such file or directory

chmod: /dev/input/uinput: No such file or directory

chmod: /dev/misc/uinput: No such file or directory
[SuperSU] skyhirules:
That's Satan's log... I think your phone is possessed... :silly: :p
[SuperSU] badhabit_wb:
Is that Lucifer you're talking too?
[SuperSU] KaMyKaSii:
Using a file manager with superuser access, can you find any of the files that the SuperSU log says do not exist? If so, the error may be in SuperSU. If not (most likely), HiroMacro is not yet compatible with Android Oreo. You should report this error to the developer of this app
[SuperSU] bemagrp:
Using solid explorer, very stable , and i think is the way to go.
[SuperSU] DB126:
Excellent choice. FX and a handful of others are great alternatives as well.
[SuperSU] DEVILOPS 007:
Mixplorer for me:)
[SuperSU] chazall1:
+1
[SuperSU] buffer overflow:
Root browser but with old UI, not new.
[SuperSU] Ahil Khan 7:
Dose UnSu script zip work ...Can it fix bootloops?!
[SuperSU] iXaidyiu:
If the bootloop is triggered after flashing SuperSU, yes it can fix it.
[SuperSU] Alxoom33:
SuperSU v.2.82 SR 3 working great on both of my NEXUS 6 running latest Android N 7.1.1 stock and Pixel C running Android O 8.0 OPR6.

I have Stericson's Busybox Pro 1.27.1 and tried unsucessfully to install in both devices to:

/sbin/supersu, /sbin/supersu/bin and the reccomended path: /sbin/supersu/xbin.

For both devices BusyBox reported the instullation was unsucessful each time. In checking these paths with Root Explorer I found various BusyBox components installed in each of the paths on my Nexus 6 (7.1.1) today, but nothing shows as being installed in the Pixel C (8.0).

I have read the linked information in the OP and posts in this and related threads on the recommended path of /sbin/supersu/xbin to install BusyBox, but I have been unsuccessful, each time.

I checked in the DevCheckPro app and it shows under BusyBox: not found. Any suggestions?
[SuperSU] corkiejp:
[MENTION=4100646]Alxoom33[/MENTION] Try meefik busybox!
[SuperSU] Alxoom33:
I saw your prior post. What is meefik busybox?

Thank you.
[SuperSU] jcmm11:
Osm0sis just updated his installer to use the correct path
[SuperSU] corkiejp:
It just an alternative busybox installer (open source), linked above. Can't remember where/when I was recommended it.

But you can choose customs paths for install with it.

I use it when Busybox Pro has not been updated to support latest supersu paths. Although your suppose to be able to choose custom paths with that as well (just doesn't stick).

Edit: - Also has the same problem when the path was /su/xbin
[SuperSU] Lunoru:
Hello hello, I am curious, is it possible to install SuperSU via flashing on Fastboot? My phone is a little ****ty and it will not simply accept any custom recovery applications, so I am left with a Fastboot option, which only flashes Img files.

Is there a way to flash SuperSU and gain root access with it via Fastboot?
[SuperSU] corkiejp:
You didn't mention your device, but you could check if CF-Auto-root is available for your device. Also don't know when that method was last updated. So you may be on an older version of supersu.

If you are then possibly use Flashfire to update to latest!
[SuperSU] Alxoom33:
I was able to install busybox with Meefik busybox and JRummey's Busybox installer. I like JRummy's tools, so I bought the Pro version and am using it on both of my devices. Working great! Thanks you for your advice.

---------- Post added at 04:30 PM ---------- Previous post was at 04:29 PM ----------

Is it available on the Play Store or elsewhere​? I always try to support developers that I know and like.

Edit: The JRummy installer keeps fc on the Oreo Pixel C. Successfully downloaded and installed with [MENTION=1143630]osmosis[/MENTION] Busybox installer. Meefik busybox installer also works nicely.
[SuperSU] jcmm11:
https://xdaforums.com/showthread.php?t=2239421
[SuperSU] Ch3vr0n:
Even if yours won't accept one, is there a twrp available for it at all? Because if there is you could place the SuperSu file on internal storage and 'fastboot boot' into the twrp recovery. You don't actually have to install twrp to be able to use it.

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] corkiejp:
[MENTION=1754043]Ch3vr0n[/MENTION]

[MENTION=7464691]Lunoru[/MENTION]

He has an obscure foreign phone Flycat optimum 5501 .

Which he will find no help with the CFAR Method Linked before, just basing this on his other posts.
[SuperSU] Alxoom33:
Thanks, sucessfully installed BusyBox on my Pixel C running Android Oreo 8.0 OPR6 with [MENTION=1143630]osmosis[/MENTION] BusyBox installer.
[SuperSU] DB126:
In addition to other solutions you can try to boot a TWRP image via fastboot command: fastboot boot <twrp.img>

This solution is best used when TWRP (or other custom recovery) can not be flashed to the recovery partition for whatever reason.
[SuperSU] Ch3vr0n:
That's what i already said in post 11041.

[MENTION=7464691]Lunoru[/MENTION] i had a quick search on google and it may be able to root your phone with SuperSu through alternate means. I hope you speak russian or know how to use google translate website perhaps. Grab a look here

http://rulsmart.com/flycat-optimum-5501-3318/

Here's another one that may be of help. I don't understand any russian but i did recognise root and "CWM Recovery (aka ClockWorkmod Recovery)

http://rulsmart.com/flycat-optimum-5501-3318/recovery/

It lists a number of rooting applications such as KingoRoot and framaroot. If they're succesful, into rooting your device, there are scripts / tools that can replace those notorious rooting tools with SuperSU.
[SuperSU] DB126:
Sorry...didn't see your initial response until after an XDA Labs refresh.
[SuperSU] bggold:
Finally got to continue my testing and I now can't get rid of the lag and all of the crash_dumps I see in TOP after dirty flashing O.

Steps after dirty flash to root.

1. booted with twrp mod for pixel

2. flashed the latest supersu 2.8.2 sr3

I have tried the following to resolve lag issue.

1. deleted all authenticated apps from supersu - This worked the last time and is not working this time.

2. dirty flashed O and delete the SU folder. Then flashed supersu again.

I can dirty flash O and the phone returns back to normal.

Since this is my test pixel xl, I am not in a need to reload from scratch. I will wait until Chainfire returns and has time to look into it, unless someone has any ideas.

Thanks
[SuperSU] Lunoru:
Flycat Optimum 5501
[SuperSU] badhabit_wb:
I had a problems with lag. I fixed it by unrooting, flashing the factory image, rerooting and flashing suhide. I then reinstalled each app individually. I did that last monday, I think, and have had no problems since and the phone still is fast. I wasn't able to get things working right until I flashed the factory image.

I flashed SuperSu and SuHide with TWRP but didn't install Twrp

Hope this helps
[SuperSU] Ch3vr0n:
[MENTION=7464691]Lunoru[/MENTION] https://xdaforums.com/showpost.php?p=73553947&postcount=11045
[SuperSU] bggold:
Thanks that is what someone else said they had to do. I am not in a hurry since this is not my daily driver, so I think I will wait to see if Chainfire can figure it out before I do a complete rebuild. Since I can reproduce it maybe there will be something useful for him from the logs or to test a fix.

Thanks again
[SuperSU] badhabit_wb:
Makes sense. Good luck!
[SuperSU] bggold:
After looking at TOP a little closer I noticed that TeslaUnread was at the top most of the time. Just for fun I uninstalled it and the lag went away. I reinstalled and no lag. Not sure the reason for this since TelsaUnread was installed before I re-rooted after upgrading to O. Oh well probably not a supersu issue, going to just get a stable test for a few days then upgrade the daily driver and call it a day. Worst case I can flash back to my last N backup.

Thanks
[SuperSU] badhabit_wb:
I'm using the stock launcher and since google has the bubbles now I don't use Telsa unread and Nova. Not sure how the bubbles work with another launcher.
[SuperSU] Ibuprophen:
Thankfully I've never experienced any issues with the Next Launcher. It may not be perfect but, it has worked for me. :)

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

I Am The Egg Man,

They Are The Egg Men.

I Am The Walrus!

Coo Coo Cachoo!

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

PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
[SuperSU] Ch3vr0n:
What does any of that (Tesla, Nova or next launcher) have to do with this topic? This is about SuperSU SR3, not a launcher discussion topic or problems relates to them!
[SuperSU] badhabit_wb:
My apologies
[SuperSU] bggold:
The only reason it was brought up in the first place is that originally the issue seemed to start after rooting O. So it was an update that it does not look like it is.

I did not intend the post to become a discussion on launchers.
[SuperSU] Ibuprophen:
Maybe it was inadvertent but, when someone had mentioned issues with SuperSU and their Launcher, a few of us members were just providing some information regarding the other Launchers we used as not having any issues.

Sometimes when a member states an issue, like the SuperSU and a Launcher, another member will typically ask how it does with whatever Launcher.

Those of us had stated this, regarding our Launchers, I'm sure was all in good faith though, we could have clarified this a bit better.

I apologize if members thought i was going off topic since it was not my intention.

Okay.... Let's PLAY BALL!!! :D

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

I Am The Egg Man,

They Are The Egg Men.

I Am The Walrus!

Coo Coo Cachoo!

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

PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
[SuperSU] snovvman:
I have OPR6 installed on Pixel, along with EX Kernel, 282SR3, and suhide 108. All appears ok--I have root, pass safety net, Playstore (for now) shows certified after clearing data. Adaway is also installed. The systemless mode is grayed out, box unchecked. I've read the previous posts re manually creating the mount on this post and this post, that was AFTER I lauched Adaway and it was able to enable the adblock/host files. What is this? Adaway is working without me having to manually create the mount. Safety Net still passes, etc.