yashsingh1/xdaforums huggingface dataset:
[SuperSU] Vinnom:
Well, I quoted other posts of mine just as little background and just to try to be more clarifying:

I have a huawei nova CAZ-TL10 (chinese device)

The quotes are from chinese firmware (CAZ-TL10C01B180 - ANDROID 6) which can't be decrypted (after format data via TWRP, device won't boot. It have to be formatted again via stock recovery) and we don't have any dev working in twrp so we can mount in TWRP the encrypted data.

So I changed to an european firmware (CANC432B100) which is decrypted and data is mounted successfully. Then I tried to flash same superSU which script finished successfully in the chinese firmware (but couldn't place files in the right places because unable to access data partition) on the european one. Now, the script doesn't finish successfully (as I already mentioned in one of the quotes).

Anyone can help me with this? The recovery log from chinese fw is attached in the post of the last quote I made. The recovery log of european fw is attached here. For now, I'll keep using phh's superuser as a root solution, but I would be glad to use superSU
[SuperSU] wwlotus:
Bug in HuaWei p3 in SBIN mode

My cellphone is Huawei p9 , as　I do 　echo "BINDSBIN=true">>/data/.supersu　 in abd shell , and want to supersu being SBIN mode , It is suceesfull , but the sad thing is the password and fingerprint gesture no more work , i can not acess my phone until i reset to factory!! ,please fix the bug

please test it in SBIN mode
[SuperSU] SpasilliumNexus:
I'm sure he'll get right on that, right after he goes through thousands of Android phones and somehow guesses which one you have.

By the way, nice logs. Oh, wait...
[SuperSU] gverma1:
I guess the command is: echo "BINDSBIN=true">/data/.supersu

Notice the single greater than sign ( > ). Two such signs ( >> ) as you have mentioned would be appending to an existing file or creating a new file. This may/may not solve your issue, but is worth a shot.
[SuperSU] NLBeev:
Think you are right. Probably the file .supersu contained BINDSYSTEMXBIN=true.

When su282sr3 is installed editing this and reboot could help.
[SuperSU] Midomad:
Deleted.
[SuperSU] officiallyme:
Hi,

may I ask if the current version will also work on my old i9100 (JB stock 4.1.2)?

If not, which version is the newest/best that'll work?
[SuperSU] Ch3vr0n:
There's only one way to know. Try it.

Sent from my Nexus 6P with Tapatalk
[SuperSU] ashyx:
I think CF dropped support for anything below KitKat.

In any case it will always install in system mode on JB.

Also you have no need at all for the updated versions, they are only fixes for newer devices and pretty much irrelevant for anything running JB and may even cause unnecessary issues.

You'll need to consult the changelog to ascertain the latest version for when support for JB was dropped.
[SuperSU] officiallyme:
Hmmm, there is no entry regarding JB being dropped. I couldn't find any information on which is the "final" SGS2 compatible SuperSU :(

I will try flashing Siyah kernel and the the latest SuperSU, but I am guessing it will fail. So if anyone knows something that can help me out? I figured that if I re-partition and freshly install the latest stock I might as well use the latest SuperSu ;)
[SuperSU] ktmom:
*I* wouldn't bother with anything newer than 2.79. I'm not positive that version will work with JB but it's the one I'd try.
[SuperSU] osm0sis:
They should all still include system-modifying SuperSU for older Android. I think it'll work.
[SuperSU] ashyx:
True but I'm sure Chainfire said when he released V2. 82 support was being dropped for anything below KitKat.

I may be having a moment and possibly be referring to something else. :silly:

EDIT : all I can find is reference to support for 2.1/2.2 being dropped by CCMT.
[SuperSU] wwlotus:
I try this echo "BINDSBIN=true">/data/.supersu , the same problem 。。。。。。。。。。。。。
[SuperSU] corkiejp:
Weird error today on Nexus 9 September Factory image.

Used flashfire to update and inbuilt everroot. Supersu was looking to grant itself root permission.

I thought, I had a bootloop, so rebooted the device myself, so may have interrupted the process.

Was able to flash stock boot and system. But TWRP is reporting a mounting error.

Haven't time now to debug, get logs or attempt rooting again. Going out for dinner.

Will edit this post again tonight, when I get logs and attempt rooting again.
[SuperSU] officiallyme:
So, quick update. I re-partitioned, installed a clean Samsung JB stock, flashed Siyah and then flashed the current SuperSU stable version.

Worked like a charm. No problems at all so far. Was even able to install Netflix, which did not work before with older SuperSU.

So, if anybody is still using JB, then the current stable still works :)
[SuperSU] corkiejp:
Messed up my Nexus 9!

I Messed up my Nexus 9, with September Image!

As a follow up to my previous post here.

I tried to root my device again, first I tried with SBIN enabled.

The second attempt (without sbin) after flashing stock boot and system again, I have attached recovery log.

Still Supersu is requesting permission for root access itself before error of not responding.

There is a copy of suhide on device, I am wondering if it is causing conflicts. But my file managers are also crashing. So deleting that is difficult. Have to look for adb commands to do it.

Edit: - No su folder in adb ---> /data/adb/su/suhide

Looks like I may need to wipe device and start from scratch, can not remember when I used flashfire to backup the device.

If I am wiping it, I might look at a custom rom for it, as support is coming to end for the tablet for official roms.

Edit: - Flashed back to August Image, device still acting weird, have not tried supersu. Looks like I will have to wipe and start a fresh. (I am hoping, i haven't reached EOL for the device).

Edit 2: -

Just a follow up!

Wiped device and removed encryption and flashed LineageOS, used the recommend gapps and rooted with supersu!

What possibly went wrong. When rebooting the device (when I thought it boot-looped), I must have corrupted the data partition.

Edit 3: - Last Flashfire backup was 23/11/2016, way to old to be useful!
[SuperSU] metalcated:
[MENTION=631273]Chainfire[/MENTION] Nexus 6P, stock oreo, stock boot. I installed this beta SR3 and it was working great for days and then suddenly today WiFI stopped working. I removed SuperSU through the app's native uninstall method and restored the boot.img then WiFi started working again on the next boot. Not seeing anything else about this from anyone else, but I thought I would report it.

9-09 22:37:12.960 412 412 I android.hardware.wifi@1.0-service: Wifi HAL started
09-09 22:37:13.516 412 412 I WifiHAL : Initializing wifi
09-09 22:37:13.516 412 412 I WifiHAL : Creating socket
09-09 22:37:13.518 412 412 I WifiHAL : Initialized Wifi HAL Successfully; vendor cmd = 103
09-09 22:37:13.530 907 2513 I WifiVendorHal: Vendor Hal started successfully
09-09 22:37:13.530 907 2513 D WificondControl: Setting up driver for client mode
09-09 22:37:18.554 907 2513 E WifiMonitor: startMonitoring(wlan0) failed!
09-09 22:37:18.555 907 2513 E WifiStateMachine: Failed 6 times to start supplicant, unload driver
09-09 22:37:18.560 907 907 E WifiController: WifiControllerWifi turn on failed
09-09 22:37:18.562 907 2513 D WificondControl: tearing down interfaces in wificond
09-09 22:37:18.612 412 18435 E WifiHAL : wifi_event_loop: Read after POLL returned 4, error no = 0 (Success)
09-09 22:37:18.612 412 18435 D WifiHAL : Got a signal to exit!!!
09-09 22:37:18.612 412 18435 I WifiHAL : Exit wifi_event_loop
09-09 22:37:18.612 412 412 E WifiHAL : wifi_cleanup: Read after POLL returned 4, error no = 0 (Success)
09-09 22:37:18.612 412 412 E WifiHAL : Event processing terminated
09-09 22:37:18.613 412 412 I WifiHAL : Internal cleanup completed
09-09 22:37:18.816 412 412 I android.hardware.wifi@1.0-service: Wifi HAL stopped
09-09 22:37:18.818 907 2513 I WifiVendorHal: Vendor Hal stopped

Update #1

I ended up having to perform a full factory reset to gain root back with WiFi working. What ended up happening was when I restored system and data from a previous backup, TWRP for some reason kept telling me /system was read only only after I attempted to flash a custom kernel. After that I lost WiFi. (Franco Kernel which works fine in most cases with WiFi working). So I am not 100% sure what caused the issue in that process because the phone booted up fine and worked fine after that as long as I flashed the stock kernel and removed root.
[SuperSU] obe_budda:
Odd Issue.

So I have a rather odd issue. Updated to Oreo which is fine. Then followed whats in this guide https://discussions.citrix.com/topic/309643-remove-configured-group-from-the-published-application/. All went fine apps all seem to work great root worked better than ever even SUhide works great. Only odd thing I have now is I play a Marvel Contest of Champions on my phone the app launches then says "Your Device is out of storage space. Please clear some space and try again later." Which makes no sense I have 65 GB of free space. So I did some trial and error and found out that the error only happens after flashing SuperSU I tried it both with 2.82 SR3 and SR2. Just uninstalling SuperSU doesn't correct the issue either I have to boot to TWRP wipe system and rerun the update of Andriod to Oreo from ADB and the game will launch fine. But if I again try to flash SuperSU it pops the same error after reboot. The phone is Pixel XL running 8.0.0 Patch Level is 8/5/17 Build Number is OPR6.170623.012. The game is the only thing that doesn't seem to work it's very odd. I also tried letting the phone update 8.0.0/OPR3.170623.007 which is Patch level 9/5/17 I believe and it was still the same issue after flashing SuperSU. I would post logs but I am honestly not sure which logs to post for this kind of issue. I also tried reflashing SuperSU from FlashFire on the build OPR6.170623.012 still the same issue. Any help would be appreciated.
[SuperSU] jcmm11:
logcat would probably do, at least for starters.

Also instead of wiping system and reinstalling Android see what happens if you just restore the kernel to stock. You should have a backup image of the stock kernel at /data/stock_boot_<sha1 hash of boot image>.img.gz

The hash is of the image file after you extract it.

Or just take a backup before applying Supersu.

Take a backup of the boot partition before restoring stock then to get root back just restore the backup.

This works because most of what supersu needs to do in order to work takes place in the kernel patches it applies. The support files will still be on the data partition, they just won't do anything.
[SuperSU] obe_budda:
Okay, I'll give it a try think it's them though this was posted on their forum.

http://forums.playcontestofchampions.com/en/discussion/comment/126093/
[SuperSU] jcmm11:
It's still interesting that it only seems to trigger when you're rooted. Probably won't have a solution, but still interested in what logcat shows.

If active root is really the trigger you can simply have 2 different boot images backed up. One before Supersu and one that's patched by Supersu, restore the pre-patched one to play the game, restore the other to get root back.

Pain in the butt, but it's one way to get to play relatively easy.
[SuperSU] TR2N:
Hi guys, hello [MENTION=631273]Chainfire[/MENTION],

I have a problem with SuperSU Pro.

After I have accidentally hided SuperSU and suhide with the Volume Rocker combination I was finally able to manually unroot and reinstall everything. I was not able to use SuperSU anymore because the app was not shown in my Launcher anymore. So far so good. But now I can't SuperSU Pro to work. I can install it via Playstore but nothing happens, SuperSU is shown as free version. And even when it says it is installed the install button appears again. my system even says it is installed.. Is there something I can do to get Pro working again?

The Screenshots are in the order I have tried it to install.
[SuperSU] Chainfire:
(a) resize images so they aren't ginormous

(b) reboot
[SuperSU] ffejy462:
Nexus 6p stock 8.0. Latest supersu.

Lost root, but reboot restored.

Been trying to recreate to get logs since this happened, but unsuccessful. If it happens again, I'll update with logs. (yeah yeah i know, logs or it didn't happen)
[SuperSU] TR2N:
Sorry, I use Tapatalk to attach photos.

I rebooted several times, but I have no luck. I can't solve this issue.

SuperSU Pro is also not shown in suhide.
[SuperSU] Chainfire:
SuperSU v2.82-SR4 released: https://plus.google.com/+Chainfire/posts/BtFBSucPg29
[SuperSU] Chainfire:
Systemless SuperSU requires Android 6.0 or newer (5.1 on Samsung), because a lot of commands and scripts etc are not compatible, precisely as you have discovered.

It would require incorporating busybox to make the installation more reliable, which I refuse to do due to busybox's license. You're having quite some luck with the scripts and binary precisely because LineageOS offers a lot more standard commands than Android did itself at that time. Unfortunately for you, probably not everything went well, and even if it did, the APK has hardcoded API level checks for code paths that would otherwise be to costly to check, and we know aren't supported anyway.

When systemless SuperSU was made even then I limited it to 6.0+ and then 4.4 wasn't even that old, but now 4.4 is nigh 4 years old, and it would require quite a bit of effort to get it compatible.

Very strange!

You can try this from root shell:

pm unhide eu.chainfire.supersu.pro
pm uninstall eu.chainfire.supersu.pro

Then reinstall from Play Store.
[SuperSU] TR2N:
Hi Chainfire,

the first command did it. What was the reason, do you have an idea? Maybe the hiding with suhide?
[SuperSU] DodoGTA:
By looking at the LICENSE file of your SuperSU ZIP, I can see that you used components that are licensed with GPLv2 (Busybox is also GPLv2-licensed, so why don't you add it?)
[SuperSU] Chainfire:
Since very recently external (de)compressor binaries are included that are GPL licensed, but these are from generally nice people, where the busybox authors are notorious for pursuing people who use busybox but are not using the GPL for their own product.

(That Android itself uses toolbox and toybox, even though they're relatively ****ty in comparison, is not an accident)

Yes, in the end I caved and I do use it with FlashFire, but that is in my opinion much less risky.

Besides, aside from the handful of issues with bringing systemless to older Android versions that I have no intention to fix anyway, busybox really isn't needed. So why bother? And that's not even touching on that the ZIP includes binaries for several architectures and adding busybox would probably double the size, making it less usable in space-limited root injection tools such as rooting boot images like CF-Auto-Root.

It's just not going to happen.
[SuperSU] Chainfire:
Possibly. The issue you see hasn't occured for me, I'll put it on my list to re-test.
[SuperSU] DodoGTA:
Just what I thought :cool:

Slight offtopic: Does suhide-lite require the kernel to have setns support for the mount namespace?
[SuperSU] Chainfire:
Yes it does.
[SuperSU] DodoGTA:
OK, so that explains the cause for the problem that [MENTION=6290984]SSH316[/MENTION] is having:
[SuperSU] SSH316:
Too bad for my device :( , i think it's time to get new one
[SuperSU] VivaErBetis:
Does SuperSu 2.82 SR4 still show SR3 in Settings?
[SuperSU] mauam:
It shows SR4 here.
[SuperSU] VanGolfer:
Flashed SR4 (twice) but still showing SR3 :confused:
[SuperSU] osm0sis:
Odd sidenote, somehow Google Glass' (at least older) firmwares used busybox. Not sure how they got around that.
[SuperSU] SpamAndEggs:
Confirmed 2.82 SR4 is working on AT&T LG V20 stock. I came from 2.79 and was hesitant to update, but it went through without any issues.

For some reason I wanted to see if Root Switch worked - it disabled root, but I couldn't enable it until I rebooted the phone. I uninstalled that app after getting root again.
[SuperSU] Alxoom33:
Mine shows SR4. You may have a bad download. Try again.
[SuperSU] osm0sis:
Weirdly mine did that too. Stock Oreo, Nexus 5X. I had originally flashed SR4 from FlashFire (restore stock boot.img, EverRoot off, preserve recovery), and it still showed SR3, so then I just extracted the SR4 APK, sideloaded it, and reflashed the zip from TWRP (after my stock boot.img) just to be on the safe side.

Maybe there's something different with the way Oreo handles APK updates the way the SuperSU zip/scripts try to install them.
[SuperSU] radz_:
Not really a bug, but I think "Re-authentication" is broken for Samsung 6.0.1?

Whenever I re-install, or update an app. Its no longer asking for root? It will just Grant the root instantly if it was already granted previously.
[SuperSU] VivaErBetis:
My problem also happens in a Nexus 5x with Oreo. My devices with Nougat upgrades from SR3 to SR4 without problems.

To make it ever weirdier... The apk version of /data/app/eu.chainfire.supersu-1/base.apk is SR4 but system show that the apk installed is version SR3...
[SuperSU] vandyman:
I also have a N5X. That shows sr3 after installing sr4.
[SuperSU] Displax:
Same (maybe) issue here.
[MENTION=631273]Chainfire[/MENTION]

Here is log from install:

View attachment 4276819

I found this error:

dd: writing '/dev/block/mmcblk0p34': No space left on device
[SuperSU] vandyman:
Reboot solved the problem.

Now showing sr4.

Thanks...
[SuperSU] obe_budda:
I see SR4 is out maybe that will fix it.
[SuperSU] osm0sis:
Yup, this pretty much confirms my theory that Oreo package manager is handling them differently.
[SuperSU] Ibuprophen:
Just for the record [MENTION=631273]Chainfire[/MENTION]...

I had no issues with flashing and using the SR4 on my Unlocked (and of course Rooted) Verizon GS3 & GS5 (d2vzw & kltevzw) devices.

Thank you very much!

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

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] Manhkeu@gmail.com:
SuperSU v2.82 SR4 does not support swap ram.
[SuperSU] Ibuprophen:
Are you asking this as a question or stating this as a fact?

I see that it's your very first post and wanted to know if it's either of the two or just a way to build up a post count.

Thank you.

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

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

PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
[SuperSU] GuardianUSMC:
Good question.

Either really new, or spam because using your email as your username has to be intentional bait for bots right? or really bad misstep.
[SuperSU] Ibuprophen:
My, personal, opinion regarding this...

Though, you may be right in regards to some circumstances but, I believe that the majority of members who use personal information for their member name like emails, phone numbers, etc... do so for 2 reasons.

1) The member actually doesn't realize/understand why it's not a good idea.

2) The member does realize this and is actually using someone else's personal information like an ex girlfriend, someone they don't like, a random person, etc...

I'm not an XDA Administrator or Moderator and can only try to "discourage without preaching" this.

But, this doesn't need to be here and is way off topic so I'm going to end my conversation regarding this.

My apologies to everyone!!!

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

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

PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
[SuperSU] GuardianUSMC:
Ok, agreed - apologies for replying to your post.
[SuperSU] Ch3vr0n:
[MENTION=631273]Chainfire[/MENTION] I was previously running SBIN mode on my nexus 6P (7.1.2) through the echo command. Now that the device has been updated to oreo via ota is the file that was written still needed? If so where is it located and what do i delete? Do i need to reflash SuperSU afterwards to be safe?
[SuperSU] corkiejp:
You could edit out the line in /data/.supersu
[SuperSU] Ch3vr0n:
might as well delete the file then? Cause it's the only line in there. I needed to "force" sbin mode as i was on 7.1.2 and suhide requires sbin mode (which is non-default in 7.x as you know)
[SuperSU] corkiejp:
Didn't know if you used other commands in there, you might have been running decrypted and deleting the file may have forced encryption on your device.

If it is the only line, deleting the file is grand. No need to reflash supersu.
[SuperSU] Ch3vr0n:
Nah I'm running encrypted :) just all stock plus root. No custom tweaks, kernel Xposed or anything like that. I like stock all the way, just need root :) deleting it is

Sent from my Nexus 7 with Tapatalk
[SuperSU] eXI911:
I tried to use it on my Galaxy K Zoom SM-C115. After installing it with TWRP i only get boot loop. Via ADB access to recovery is possible. Wipe cache, factory reset has no effect. Any other solutions or do i have to flash stock firmware?
[SuperSU] sliding_billy:
Having a strange problem on a Pixel (not an XL though I have both devices and the XL does not have the issue)), and nobody has responded with any suggestions on the PIxel forums. Using SuperSU and suhide, and the icons for both disappear randomly (after a few days of being present) and reappear just as randomly. Both apps still show as installed in settings>applications while the icons are missing though Titanium Backup claims that suhide has a backup present despite the app being uninstalled. Root continues to work (on all rooted apps except suhide since I can't launch it or see it's status in SuperSU) while the icon is missing, though I notice that on reboot Flashfire does not grant root access during boot like it does when the icon is present. I have tried reinstalling the latest version of Oreo without doing a -w in the flashall.bat and have done it as s complete reinstall including the -w. The complete reinstall brings back the icons and the disappears in a couple of days. This issue was present in SR3 and continues to be so in SR4. Once again , same config in my XL as my wife's Pixel and the XL has never lost the icons. Any thoughts would be greatly appreciated. Both SuperSU and suhide were installed on both devices with the development version of TWRP that uses the fastboot boot .img.
[SuperSU] jcmm11:
The description you give sounds exactly like what happens when you trigger hide mode in suhide. Is it possible that hide mode was somehow accidentally triggered (volume up/down 3 times within 3 second)? If that is the case then the same action will toggle it in the other direction and make them visible again.
[SuperSU] badhabit_wb:
It may be titanium backup. I had two apps that I alternately froze in tb. They started disappearing and reappearing just like what you're describing. I uninstalled and reinstalled both apps. I did the same with tb, same results. I finally wiped and reinstalled oreo because that was faster than figuring out what was causing the problem and I didn't reinstall tb. All is well now and I'm not having random problems. I know it's a pain but that may be the only way to fix it.

h
[SuperSU] sharkie405:
[MENTION=631273]Chainfire[/MENTION] I've just spent an hour trying to re-find this post. Just a humble suggestion, but it'd be really helpful if you linked this post in the first post. :)

It's the only one that works for me (Pixel XL - Android 8.0 - marlin-opr1.170623.026-factory-1ed9b4b2).