yashsingh1/xdaforums huggingface dataset:
[SuperSU] osm0sis:
When you get the chance, can you test to see if if it boots repacked with no changes with my Android Image Kitchen? It will use the legacy LZ4 to recompress and re-sign with AVB using AOSP testkeys (will be switched to the proper AOSP verity keys in the next release). I'm curious whether things are backwards compatible where they might not be forward compatible.

Edit: Nevermind, I see it's just the kernel that's compressed with LZ4 in Pixel's ODP, not the ramdisk. You'll probably want to support the legacy format though, since that's what Linux uses and the reason it's still included in LZ4:

-l : compress using Legacy format (Linux kernel compression)
[SuperSU] wetxxx:
For my HTC 10 version SR2 works ok with no bug. I should install sr3?

"Live long and prosper"
[SuperSU] ulxerker:
Yes, if sr2 ran sr3 will, too.
[SuperSU] Ibuprophen:
Understood Big Guy! :thumbup:

1 last quick question... :D

I know that CyanogenMod is still being used but, does the Setting (within the SuperSU Settings) regarding the option to Respect CM Root Settings still only apply to CM? OR Does it also apply to the LineageOS Root Settings (even with LineageOS SU installed)?

***I had attached a supporting image reflecting that certain portion within the SuperSU Settings.***

Thank you very much! :cool:

______________

PLEASE NOTE: I welcome any member to help with further valuable information/clarification for any of my posts.
[SuperSU] Alxoom33:
Same issue with my Nexus 6 with SR2 pathfix.
[SuperSU] Ch3vr0n:
I'm not using an N6. I'm using a 6P. Different device. For the moment no slowing or locking *crosses fingers*
[SuperSU] corkiejp:
Was trying out suconfig, SR3 and suhide-lite on my Nexus 9!

Used latest flashfire to flash everything successfully, and passed safetynet!

Just note Busybox Pro and Adaway will need to be update for the new paths.

I used meefik busybox installer to get it on the right path.

Adaway no longer gives the option of systemless install.

With the above, I probably altered my system image, so wondering how it still passes safetynet,
[SuperSU] bggold:
Worked fine for me on a pixel xl. Flashed SuperSUconfig and SR3, Busybox (Stericson) and Adaway installed without any issues.
[SuperSU] jcmm11:
[MENTION=4868912]corkiejp[/MENTION]

Adaway installed, but not in systemless mode. You can manually set it to run systemless. See page 1087, in this thread. 3rd post from bottom (and first post on 1088).
[SuperSU] Black Shade:
I have a very interesting issue on my Note 4 running Resurrection Remix 5.8.4... every time I try to use a root hiding method, my partitions get messed up, they are detected as "unmounted" and I can't edit any system files - my file manager says it's unable to mount /system. It happened with Magisk Hide, and now it's happening with SuHide... Does anybody have an explanation for this?
[SuperSU] combat44:
Thanks, the problem is solved, the network is.
[SuperSU] NLBeev:
Nexus 6, 7.1.1 August N6F27I, decrypted.

Flashed SR3 over SR1. Everything kept working as with previous SR1.

When SuperSU is started, it asks for updating the binary. That's also the same.
[SuperSU] BatChen:
hey,guys!

what are the differences between UPDATE-SuperSU-v2.79-20161211114519 and SuperSU-v2.79-201612051815 ?

And which one build by chainfire , sorry for that, i do not want to use CCMT'
[SuperSU] osm0sis:
About 6 days. You can read the changelog for any further differences. Chainfire's are labeled with UPDATE-

The CCMT ones are safe to use as well, Chainfire's ensured they're building exactly the same as his are. I usually just go with whichever has the newest build date (moar fixes!), v2.82 is the latest stable by the way.
[SuperSU] BatChen:
what about beta ? how can i know whether it is built by chainfire ？
[SuperSU] osm0sis:
Chainfire is the only one building betas, and again, there is no difference in builds, they come from the same source repo and there are no extra changes, verified by Chainfire to try and squash the FUD.
[SuperSU] BatChen:
thanks for your reply
[SuperSU] Chainfire:
Everything served from the chainfire.eu domain is built by me personally on my computer, even if the name includes CCMT (that just means the code matches the CCMT Play store release).

Play store and supersu.com downloads are built by CCMT.
[SuperSU] sb1893:
Frequent lock-ups, strange boot to bootloader behavior

I'm having some strange device instability ever since moving to SuperSu 2.82 SR2, SBIN mode. I have installed SuperSU 2.82-SR3, SBIN mode on. I am also running suhide 1.07. I am on a Google Pixel XL running August Security Update. Stock, unlocked bootloader, rooted (obviously). I did also install August Security Update recently - so entirely possible the instability is due to that change as well.

I'm noticing the phone locking up a few times each day (seems to be with increasing frequency since going to SuperSu 2.82-SR3 - three times since I installed it last night. But it was also exhibiting this behavior on -SR2 as well). When the phone locks up, the only method to escape seems to be pressing Power, Volume Up+VolumeDown at the same time. This eventually results in ramdump and then reboots the phone. The phone does boot successfully so this isn't a bootloop per se. I've also noticed then when the phone is powered down, attempting to boot directly into bootloader also does not work as expected...about 90% of the time it will eventually result in the ramdump. If I hit the Power, Volume Down buttons while the ramdump screen is displayed, the device does then boot into the bootloader screen.

I'd like to remain on the SuperSU Beta and suhide, but the instability is a challenge. Happy to provide any logs or debug information that might be needed to help diagnose. If I need to revert to more stable SuperSu, I believe I can just follow the instructions to remove suhide and then Full Unroot to remove SuperSu...will this also revert to current standard from SBIN mode, or do I need to issue some commands from Terminal in TWRP to reverse the SBIN enablement?

Many thanks for all you do!

S
[SuperSU] Chainfire:
Can you run without suhide (but keeping SBIN) for a few days and see if that gets rid of the lockups?
[SuperSU] sb1893:
Thanks for the rapid response! I can absolutely run without suhide. I'll remove immediately. If memory serves, I just need to remove the suhide directory via TWRP and then uninstall the app from within Android.

Thanks and I'll report back my findings.
[SuperSU] Ch3vr0n:
[MENTION=631273]Chainfire[/MENTION] i haven't had any lockups with SR3 AND SUhide 1.07 after flashing SR3 over SR2 and i hope it stays that way
[SuperSU] ulxerker:
I had the same issue with SR3 as soon as I installed suhide 1.07 after the first boot on my OnePlus5 stock OOS: total lockup in the app drawer.

Then I reflashed SR3 and it worked, but the phone felt kinda slow and laggy. So I uninstalled suhide including removing it's folder /data/adb/su/suhide, rebooted and everything is back to normal.
[SuperSU] Chainfire:
I wish I could reproduce the lockups. They're probably easy to fix, but if I can't catch them, I can't fix them.

The handful of times I had a lockup, it recovered after a minute or two.
[SuperSU] Chainfire:
I've not ran into any problematic images, but the attached version should detect if legacy format was used in the original image and uses the -l switch to recompress.

If you do run into one of these images, gives it a shot. The patch will also be in SR4 whenever that is released.
[SuperSU] sb1893:
I'm now running SuperSu 2.82-SR3 without suhide. No lockups so far (after about an hour). In the event, I do experience another lockup - is there anything I can do to "capture" the event for you? Any log files I can grab, etc.....

Happy to help diagnose if I am able.

S
[SuperSU] zenyatta80:
I've had the exact same issue. 4 lockups in the last 2 days. I'm running 7.1.2 but with July security patch, so I guess that eliminates Aug patch being a problem. Any thing else I can share to help diagnose?
[SuperSU] bggold:
Chainfire

I just experienced a lockup on my daily driver and decided to turn on my test pixel.

It also just locked up and had it plugged in doing an ADB logcat.

I will PM you the file. Hope this helps with the lockup issue. Please let me know if you dont get it.
[SuperSU] Chainfire:
I can see the system dying in the logs but not really any clue why. Did it just freeze while doing nothing? Were you actively using it? What is your suhide config like?

I've been trying to replicate the crash by launching and killing lots of apps in a loop but no luck so far.

If you can catch it in crashed state but adb still works, the output of (in a root shell) 'ps' or 'ps -A' (O+) would be welcome.

Any pattern helps.
[SuperSU] bggold:
All I did was power it up, hook it up to the usb and start the adb logcat. It was just sitting there and I would check once in a while to see if it was locked up or not.

I will later to see if I can catch it. Kind of like watching a pot of water try to boil.

As for SUhid I have android pay, bank of america, google play services and google play store. Also I noticed google account manager and google backup transport were selected and I do not remember doing those.

Since the test one locked up my daily driver locked up again. I have changed all of the above back to root allowed. I will see if it happens again.

Thanks
[SuperSU] bggold:
Well after my daily driver locked up twice in the past hour, I sat down with my test and was finally able to get it to lockup. I was able to get you the ps. It seems to be the worst right after the device is restarted.

It seems that adb is still alive, not sure for how long. I was even able to do a adb restart.

So my daily driver only had SUHide enabled, but no apps configured. So it is not having apps configured to hid root.

I will PM you the latest catlog and ps info.

It would be great to get to the bottom of this, I am going to wear out the pwr and vol down button soon.
[SuperSU] Sr. Zé Alguém:
Shift-Del
[SuperSU] sb1893:
I've now been running with suhide uninstalled and SuperSu 2.82 SR3 in SBIN mode for 22 hours. No lockups yet. I'll continue to monitor and report any significant events or changes. Let me know if you want me to try anything else.
[SuperSU] techeligible3322:
SuperSU failed

I tried SuperSU with my MOTO X play, but i get failed error :confused:
[SuperSU] Alxoom33:
I have not had any lockups since flasing the LegZ SR3 version yesterday on my Pixel C running Android 8.0 ODP4 and Nexus 6 running Android 7.1.1 August patch.
[SuperSU] yung40oz84:
I had one lockup after initial install. And it was on rebooting. About 30 seconds after reboot I opened chrome, started some tasks, and it froze. I wasn't near anything so couldn't grab anything, I'll try to reproduce later tonight. Besides that one, no others. Angler, DU. Flash.
[SuperSU] Chainfire:
suhide-v1.08 is now available from the suhide thread https://xdaforums.com/apps/supersu/suhide-lite-t3653855

That should fix the crashing, if not, continue reporting it over there in that thread. I'm sure it's a suhide issue, not a SuperSU issue.
[SuperSU] freddienuxx:
ok I have pixel XL i updated aug/custom rom. I flashed rom flash TWRP rebooted back to system then rebooted back to TWRP deleted that fs.marlin I think it is. then I flash the latest beta supersu 2.82 then reboot back to system. now when I reboot it automatically goes back TWRP. any help would be appreciated
[SuperSU] shaggyskunk:
No you don't NEED to have an external sd card to Flash TWRP img.tar with Odin 3.12.3 - And you don't NEED an external sd card to Flash SuperSU v2.82 - But you will probably find that having an external sd card is a valuable asset and they are not very expensive these days ☺️

BUT if you Flash the Stock Firmware with Odin 3.12.3 - You will have to Format Data which means that you will lose your pictures - music etc - AND importantly you will also lose any zips for Roms etc

From Down the Rabbit Hole by:

My SM-G930W8 ??
[SuperSU] sb1893:
Great news and impressive turnaround as usual! I am traveling for work so I'll likely wait until end of week to try the new suhide. I continue to be lock-up free since uninstalling suhide1.07. I may try the new suhide1.08 tomorrow AM - schedule permitting. (Can't afford to risk having phone crash while I am navigating this evening or for the alarm clock to fail due to locked phone in the AM). Either way - thanks - and I'll report back on any lockups I may experience on the new suhide when I get it installed. Much appreciated!
[SuperSU] badhabit_wb:
New suhide seems to be working fine on my pixel.
[SuperSU] sb1893:
Further update - I've been running for 40 hours now on SuperSu 2.82-SR3 / SBIN mode with suhide 1.07 uninstalled. No lockups at all, phone has been rock-solid. I've got a full day at this office I am visiting, so I am going to install suhide 1.08 and see what it looks like for the day and if I remain lock-up free. Will report findings in the suhide thread.
[SuperSU] Black Shade:
[MENTION=631273]Chainfire[/MENTION] when I use SuHide and Magisk Hide (EDIT: both give me the issue, I'm not using them at the same time), disk info shows my partitions are all "unmounted" except for the internal storage, which is obviously impossible since the device is working. Also, when trying to edit system files using any file manager, it says it's impossible to mount /system partition. I don't really know what's going on here. I have a Note 4 trltexx running Resurrection Remix 5.8.4
[SuperSU] rjl3775:
lg fortune 6.01 mm

been trying to root my fortune android 6.01 can anyone help me?

p.s. = i am new so if i posted in the wrong place or did something wrong i am sorry.
[SuperSU] osm0sis:
What?
[SuperSU] Black Shade:
I mean, both of them give me the same issue, I'm not saying that I use them at the same time. I removed Magisk two days ago to install SuperSU instead.
[SuperSU] sb1893:
Just wanted to be sure I did this correctly and that it is working as intended. I made the changes above and rebooted. When I download/apply new hosts via Adaway. I notice that the hosts file in both /system/etc and /sbin/supersu/etc are being updated at the same time - indicating file was created by Adaway with the same date/time stamp. Just wanted to be sure this is the intended behavior - I never checked how Adaway updated these hosts files prior to SBIN mode - so not sure if this is how it should function or not - with both hosts files being updated.
[SuperSU] jcmm11:
Yes, that is functioning correctly. It's actually only 1 file being updated (the one in /sbin). The mount bind command causes that file to be mounted over the top of the one in /system/etc allowing the same file to be referenced from 2 locations and hiding the underlying file in /system/etc.

If you were now to go and issue an unmount command on /system/etc/hosts that link would be broken and the underlying /system/etc/hosts file would be revealed showing its size at approx 56 bytes. I actually have a Tasker task set up that I can invoke via a launcher shortcut that will toggle that file enabling me to de-activate ad blocking when necessary.
[SuperSU] jcmm11:
You're talking about trying to reboot from TWRP, right? This happens to me sometimes as well, but not always and I can't seem to find a pattern. In any case I have 2 workarounds that seem to work.

Reboot to power off than just start the phone as normal.

Reboot to bootloader, restart bootloader, start phone. (Restart bootloader may not be needed but it's quick enough that I always use it)
[SuperSU] sb1893:
Perfect thanks for the explanation. Makes sense. Much appreciated.
[SuperSU] osm0sis:
[MENTION=631273]Chainfire[/MENTION] does su.d occur at the same time during boot with bindsbin SuperSU as it does with su.img SuperSU?
[SuperSU] adome5:
does support nexus 6p odp4 of android o
[SuperSU] KHEMS91:
I'm on ViperOS 3.0 android 7.1.2, after flashlight 2.80 SR3, i can't shoot video.

An information appears on screen says "Can't record video"

When i full unroot my device, everything is fine.

It also happened with other roms like LineageOS, RR, AEX.
[SuperSU] KHEMS91:
Moto X Play
[SuperSU] espaciosalter20:
How to properly install this on huawei p10 with emui 5.1 to have security options enabled (fingerprint and pin-lock)?
[SuperSU] funiewski:
Flash in twrp for P10 as usually, you don't need to do anything special
[SuperSU] Tecalote:
Have you tested it?
[SuperSU] funiewski:
Yes, latest beta with b164 firmware
[SuperSU] Tecalote:
That's good to know! Thank you
[SuperSU] espaciosalter20:
i know, but when i boot it, nothing about security works (PIN or Fingerprint)... have to go back to a special version of superSU for EMUI from this thread in order to make my pin usable again...

Here is a vtr-l09c432b162

EDIT: well, i'm going to try it again with no security configured and see what's happen... i'll be back with report...

EDIT2: nope... after boot, it breaks all functionality of phone... i'm gonna make a video to show you whats going on...

EDIT3: Here is the videohttps://www.youtube.com/watch?v=2ugBOLuus20
[SuperSU] gothicVI:
Better provide logs...

Gesendet von meinem Moto G 2014 LTE mit Tapatalk
[SuperSU] Chainfire:
That thread is scarce on the details what was actually fixed, unfortunately.

Which of the many versions do you need to use? And are you running the old firmwares or the new firmwares he mentions that needs less fixes?

Have you tried SBIN mode in SuperSU ? That at least should bypass the loop mounting issue.
[SuperSU] DeaDruiD:
SR1

SR3 causes infinite boot issue with BINDSYSTEMXBIN=true, KEEPVERITY=true, KEEPFORCEENCRYPT=true and FRP=true on gts210velte. SR1 worked without problems. Can SR1 be downloaded somehwere? I would also like to try SR2 to find exactly which update broke it.

UPDATE: Nevermind, must have made some mistake. SR3 works for me after second try.
[SuperSU] Locura18:
Y

Try here.

https://download.chainfire.eu/1114/SuperSU/SR1-SuperSU-v2.82-SR1-20170608224931.zip

I've been having a lot of issues to. Going back to that version. I'll provide some more logs in a few days once I get back home. I thought initially that suhide was the one to blame but I uninstalled it and same issues keep happening.
[SuperSU] NLBeev:
Google search......... SR1-supersu
[SuperSU] badhabit_wb:
Sr3 working great on my pixel. Loaded it with the experimental TWRP kept stock bootloader etc
[SuperSU] espaciosalter20:
I'm trying to install sr3 on Huawei p10 (vtr-l09) on b132 fw (almost the last one).

Maybe, tried to install suhide as well breaks something... How to take a functional logcat to provide some light on this matter?
[SuperSU] linolino:
Xperia Z3c - didn't pay attention :crying: updated via PlayStore to V2.82

--> boot loop

struggled to get to Recovery, just reached CWM...tried (selected)

SR3-SuperSU-v2.79-SR3-20170114223742.zip

not sure if it installed correctly - don't like CWM.

Still boot loop!

Then managed to get TWRP started and installed

SR3-SuperSU-v2.82-SR3-20170813133244.zip

booted into android - with the like 1st time update/optimization of all Apps (long time for 347).

not yet sure if all is stable but it's alive again :silly:

Just missing App Icon for #SuperSU.

Was it removed with the ZIP?

Stable on 1st boot with:

SR3-SuperSU-v2.82-SR3-20170813133244.zip

cheers

Heiko
[SuperSU] srqrob:
Google store Pixel XL, Stock, August NJH47F, SuperSU 2.82 SR1 Pixel Fix with zero issues. Been following this thread for some time but I'm unclear if I should be updating to SR3 now. Advice?
[SuperSU] gverma1:
Yes. Upgrading to 2.82SR3 is highly recommended. Pair it with Suhide and you got an unbeatable combo. Just read the suhide-lite 1.08 thread op before flashing supersu. It has instructions for SBIN mode.
[SuperSU] osm0sis:
Hmm BINDSBIN SuperSU and Titanium Backup don't seem to get along (it doesn't detect root). Anybody else seeing that? I've also got suhide installed, but TiBu should have access. Any workarounds/ideas?
[SuperSU] bggold:
No problem here. Check that supersu doesn't have it denied and that suhide does not have it set to hide from root. Just my 2 cents worth.
[SuperSU] badhabit_wb:
I had some problems but they were caused by programs that were using root. I uninstalled all the rooted programs, except Titanium, re-rooted and now it works fine. I re-installed the call recorder and a couple of other programs and it's all working fine now.
[SuperSU] osm0sis:
Hmm FBE on top of it perhaps in my case? Fresh device setup on stock 7.1.2 ROM for N5X, so no root apps that aren't cleanly installed.

No other root apps are having any issue so I'm assuming it's an issue on TiBu's side.
[SuperSU] badhabit_wb:
maybe. i'm on 8.0.o too if I failed to mention that.
[SuperSU] ipdev:
[MENTION=4544860]osm0sis[/MENTION]

Just installed TiBu pro and TiBu from playstore on a 6.0 device. Asked for root right away, granted it, then used the freeze option, rebooted and checked, sure enough Carrier Services is disabled.

- Rom unofficial l13 port.

- Un-rooted with UPDATE-unSU - needed a little manual cleaning afterwards.

( User error - don't want to talk about it. :rolleyes: )

- SuperSU beta in SBIN

- suhide-lite (Some what configured)

I have a 5x for testing, it has lineage official from a few weeks ago. Needed to test something and I haven't got around to reflashing o beta yet. Currently flashing N2G48C to give a try.

I am a little new to suhide, can you point me to a good setup ? (aka what sould be hidden from root, more importantly what should not be blocked from root? Apps I get but some of the google / system apps confuse me.) I assume it's somewhere in the original suhide​ thread but, I haven't found it yet or missed it. (I'm only on page 50, long way to go yet. )

- N5X is done.

Same results on my n5x. No problems with TiBu. Not sure if it makes a difference but, I installed the TiBu pro app before TiBu app.

- N2G48C

- SuperSU beta in SBIN

- suhide-lite (Not at all configured - base settings)
[SuperSU] osm0sis:
Figured it out. :rolleyes:

Had "use external busybox" enabled in TiBu settings, and of course don't have a busybox installed yet in BINDSBIN mode. :o

Silly of TiBu not to fall back to their internal one when an external isn't found, but yeah..

As for suhide setup, defaults are fine, all I had to add was my bank's tap & pay app since it looks for root without SafetyNet.
[SuperSU] A.D.I.O.S:
no more bootloop on my xperia z2 tablet with 2.82 sr3. thanks chainfire :)
[SuperSU] Midomad:
I have this little bug from time to time since forever [emoji23]

Tapjacking protection is disabled in SuperSu settings.

Don't know what's the cause... [MENTION=631273]Chainfire[/MENTION] [MENTION=4544860]osm0sis[/MENTION]View attachment 4248269
[SuperSU] kevtrysmoddin:
Root working fine on Oreo on the 5x great work chainfire
[SuperSU] urim225:
How did you root ? TWRP working fine with Oreo ?
[SuperSU] kevtrysmoddin:
I just flashed sure 2.82sr3 and rebooted and yes twrp working fine so far
[SuperSU] joelcool69:
Working great on 6P with android O final ;)
[SuperSU] Alxoom33:
Working great on my Pixel C Dragon! OPR6.170823.010 Oreo!
[SuperSU] peterlee928:
hi yall ive seen conflicting posts as to whether suhide is needed or not for sr3. is there a final verdict on this? much thanks in advance.

phone stats:

verizon pixel xl

stock with august update

rooted via twrp/supersu pixelfix version
[SuperSU] Ch3vr0n:
Suhide isn't needed for SR3, it never has been. It's the other way around SR3 is needed for suhide! And SR3 has to be used in sbin mode

Sent from my Nexus 6P with Tapatalk
[SuperSU] TheUndertaker21:
anyone managed to get busybox to install for pixel ?

can't use viper4android due to busybox not being installed
[SuperSU] zer0se7en:
Damn. A simple question of "which version of TWRP" took some people up in heat. (Wasn't asking which version of SuperSU) Wow. The question was that invalid, huh? Ok. Thank you. You guys are soo amazing.
[SuperSU] Alxoom33:
Cool your jets, I was replying to the other guy. He doesn't know the answer to your question.

First, 2.82 SR 3 working on Nexus and Pixel devices for Oreo.

TWRP 3.1.1 [MENTION=5480152]followmsi[/MENTION] version works for Oreo for the Pixel C. Don't know about the Nexus 6p.

This is the wrong place to ask about TWRP. You should check in your device forums.