yashsingh1/xdaforums huggingface dataset:
[SuperSU] Ibuprophen:
I'm just making a guess at this...

I believe the reason why it isn't highlighted on the OP is because it was for testing purposes and, maybe, it either didn't work out for the majority of the members with Pixel or [MENTION=631273]Chainfire[/MENTION] may still be working on something that will work for the majority of the members with Pixel devices.

It's all about the "trial and error" process until Chainfire is confident enough to highlight as an actual working process for members with Pixel devices.

It like when Chainfire releases the Service Releases (SR) versions. Once he's confident enough that it works for the majority of members, he then releases the next stable version.

I hope this came out okay via text... :)

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

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

PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
[SuperSU] sharkie405:
That makes sense.

This time around I've bookmarked it for myself. Lesson learned.
[SuperSU] Ibuprophen:
I've found that when Chainfire releases something that i use or could use, i just post a, sort of, FYI to let him know that it worked or didn't work and some basic/simple info of the device.

I feel that even though Chainfire may not directly/indirectly respond to it, i do believe that he does take notice of it to support him with feedback by doing my part help him out with that valuable information developers do need.

This is just a little recommendation/suggestion for your reference.

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

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

PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
[SuperSU] sliding_billy:
Wouldn't that only hide suhide and not SuperSU?

I have nothing hidden in TB, but maybe it can help me troubleshoot.

---------- Post added at 01:43 PM ---------- Previous post was at 01:11 PM ----------

Genius. That was it. I still can't figure out how she was toggling it unintentionally, but I am able to unhide/hide at will now. It hides anything with a certain status in suhide which both of those apps have.
[SuperSU] qiurigao:
help me
[SuperSU] Ch3vr0n:
With what? We can't read your mind or have a crystal ball to know what's (not) happening.

Sent from my Nexus 7 with Tapatalk
[SuperSU] qiurigao:
[IMG="img"]https://dl.xda-developers.com/4/2/8/1/2/5/2/mmexport1505936364847.png?key=mkE8nB78BM20_KQzsozp-Q&ts=1506197764[/IMG]
[SuperSU] qiurigao:
My phone is the vivo brand, it is said that the company's Andrews system anti-root is very powerful, you can help me, thank you
[SuperSU] Bosko1976:
SuperSU v2.82 SR4 and Suhide-lite v1.08 perfectly work. :good:
[SuperSU] ICSFan:
2.39 seems to work.

No Trouble while several Reboots.

Thx a lot @ chainfire

regards
[SuperSU] perrito3:
+1
[SuperSU] mousawm:
Deleted
[SuperSU] scanno:
Omni5 problem fixed.
[SuperSU] anderson79:
Thanks chainfire
[SuperSU] XTitaniumX:
Thanks Great work :D
[SuperSU] pac213:
Seems that my S5 has a permanent root now. Thanks [MENTION=631273]Chainfire[/MENTION]
[SuperSU] purian23:
2.39 is running great as usual on the Verizon LG G3!
[SuperSU] anantk1965:
On a different note, when you uninstall SuperSu for unrooting the phone on Lollipop, it deletes "/system/bin/install-recovery.sh" file and while doing OTA update with Stock Recovery installed and after uninstalling SuperSu we get below error:

================================================== ==============================

Verifying current system..

failed to stat "/system/bin/install-recovery.sh" : no such file or directory

file "/system/bin/install-recovery.sh" doesn't have any expected sha1 sums; checking cache

failed to stat "/cache/saved.file": no such file or directory

failed to load cache file

script aborted: "/system/bin/install-recovery.sh" has unexpected contents.

"/system/bin/install-recovery.sh" has unexpected contents.

(status 7)

Installation aborted

================================================== ==============================

Even other users are facing this issue as mentioned in http://xdaforums.com/showthread.php?p=57247765#post57247765

It would be good if something can be done in SuperSu uninstall/cleanup process, so that after unrooting, we can install OTA updates(which are few MBs), instead of flashing complete factory images, which are of much bigger sizes.
[SuperSU] egingell:
Firstly, the slash is used to separate directories - not the dot. Secondly, that file goes here, /system/etc/install-recovery.sh, not here, /system/bin/install-recovery.sh. The cache file path is probably wrong, too.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] anantk1965:
Sorry. I have corrected the path in my post by replacing "." by "/". But I get this error for sure for OTA updates on Lollipop -->

failed to stat "/system/bin/install-recovery.sh" : no such file or directory
[SuperSU] Chainfire:
The install-recovery file is backed up and restored in the latest SuperSU versions, but it's not going to matter. I understand you want this, but you should understand that it's not currently possible. Yes, a solution is being worked on, but it's weeks out at least. All in all, it's a lot of whining for something that happens about 3 times a year and takes you 10 minutes.
[SuperSU] anantk1965:
Thanks Chainfire for prompt response. As you are aware of this issue, I am sure you will be able to find the way to fix it sometime in future. Not at all problem with this issue, as along as your wonderful SuperSu utility is working for rooting without any issues on Lollipop.

Thanks once again.
[SuperSU] edreams:
Once more Chainfire did it ! 2.39 works great on my Lollipop S5. Permanent root enabled. Thanks a lot !!!
[SuperSU] ShredderLM:
2.39 works great. Thank you! But I have a small problem: everytime I boot my S5 there is a message "Updating one app". This app is SuperSU. This procedure ("updating one app) takes a least 7 minutes. How can I solve this problem to reduce my boot time (7 minutes!)?
[SuperSU] _alexndr:
Excellent update :D

All issues in S5 running Lollipop, I've mentioned in posts #1076 and #1081 have gone :)

I my opinion it is RC, not BETA :good: and should appear in Play Store ASAP :good:
[SuperSU] white7561:
Try wipe cache and dalvik cache. Reboot. Then after homescreen reboot again to see is it still saying that
[SuperSU] HorstiG:
Same Problem here on S5 (G900F). with Stock KK 4.4 AllianceRom .

I have completely uninstalled SuperSU. And now running all beautifully and very fast with full root access. ;):D
[SuperSU] RheRa:
Yes.....I've this issue too, but just for few second not take as long time as you mate.
[SuperSU] HorstiG:
You're right, for me it was also only seconds.
[SuperSU] shadavis08:
What is this su hide? And where is it
[SuperSU] Ibuprophen:
http://xdaforums.com/showthread.php?t=3653855

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

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

PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
[SuperSU] gothicVI:
Which Andrews version are you running?

What have you tried until now?

What so you want exactly? (Preferably complete English sentences that actually contain information...)

Custom recovery?

Unlocked bootloader?

...

Gesendet von meinem Moto G 2014 LTE mit Tapatalk
[SuperSU] qiurigao:
I was 6.0 system, I did not unlock, but the use of the bootloader loopholes successfully brush and run the TWRP3.1.1, but still can not be successful after installing supersu root, su no operational authority, SElinux has also been closed
[SuperSU] CAL7:
2.82 SR4 on Sony Xperia Z3 Compact: Good
[SuperSU] SpamAndEggs:
I'm unable to set SBIN mode on my LG V20, whether it be using SUconfig or the TWRP terminal method. Anyone else with a V20 was able to use SBIN mode?
[SuperSU] gothicVI:
Please use distinct sentences. I'm unable to understand what you have done exactly.

I'm not [MENTION=631273]Chainfire[/MENTION] but he'll need to understand your issues in order to resolve them.

Please also state versions of SuperSU you tried to flash.

Gesendet von meinem Moto G 2014 LTE mit Tapatalk
[SuperSU] qiurigao:
ok
[SuperSU] osm0sis:
This is the SuperSU thread, not Magisk. Please go to the Magisk forum with your issue.
[SuperSU] ashyx:
Translation from another language. The poster isn't English.
[SuperSU] qiurigao:
I re-upload the log, read it better
[SuperSU] gothicVI:
Which is fine. I'm not a native speaker as well. Still, if it's not understandable it poses an issue.

Gesendet von meinem Moto G 2014 LTE mit Tapatalk

---------- Post added at 08:52 ---------- Previous post was at 08:46 ----------

Did you even read my reply?

I'm giving up...

Gesendet von meinem Moto G 2014 LTE mit Tapatalk
[SuperSU] osm0sis:
I can read your log just fine:

init: (Parsing /init.magisk.rc took 0.00s.)

Once again, you are clearly in the wrong thread. SuperSU and Magisk are NOT the same thing.

You need to reread my previous post to you and follow its advice if you want help with your issue.
[SuperSU] pavan3999:
Anyone help me, when i installed supersu 2.82 sr4 in sbin mode its showing root undetected. I even tried v2.82 sr2 and sr3 still showing like this. I'm using redmi 3s miui9 7.9.22 latest global beta rom.
[SuperSU] ashyx:
You should post your recovery.log after installing. No logs, lack of required details means no assistance.
[SuperSU] pavan3999:
here the logs
[SuperSU] unkdirkpitt:
Hi there. I am unable to flash any of the SR2-4 versions onto my oneplus X in an oreo rom. I am able to flash the stable v2.82 fine, but would like to try out suhide.

Please see the attached log. It fails during the dtb stages(?)
[SuperSU] chevycam94:
I've been searching all over for this one answer, and I can't find it.

What is the first line of a current su.d script?

"#!su/bin/sush"? (minus quotes obviously).

The su.chainfire.eu site is completely down (was just up a couple hours ago), so I can't check there, which is where I found out first.
[SuperSU] ashyx:
Everything seems to go successfully until the end where there is a segmentation fault.

Maybe you should bring this to the attention of Chainfire?
[SuperSU] pavan3999:
[MENTION=631273]Chainfire[/MENTION] sir, i'm facing this from starting of miui9 update.
[SuperSU] jcmm11:
#!/system/bin/sh

Works just fine
[SuperSU] osm0sis:
It's called a shebang (or hashbang, which makes more sense, but much less commonly called so). It's a Linux shell script convention denoting what command interpreter should/will be used to execute a script.

It doesn't affect su.d execution itself because they're run via subshells, but since su.d is changing locations from /su/bin/sush to /sbin/sush (and was /system/xbin/sush before that), one is better off using the more generic /system/bin/sh so that scripts can also be run outside of su.d.

Sidenote: Magisk's equivalents are post-fs-data.d for early start (more like su.d) and service.d for later start.
[SuperSU] pavan3999:
[MENTION=631273]Chainfire[/MENTION] sir can you look over this?
[SuperSU] chevycam94:
Gotcha. I think I have what I need now. His site is back up. This is what I was referring to, btw.

#!/su/bin/sush
(
sleep 300
echo done
)&
[SuperSU] ashyx:
Does SuperSU now support Android 7 in system mode or is that still in the works?
[SuperSU] Ch3vr0n:
It always has, depending on the rom. But if you want to force systemless, go here https://xdaforums.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120
[SuperSU] Tecalote:
There's a special Thread for SuperSU in system mode:

https://xdaforums.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120/page56

Works with Android 7 on some devices and on others not ;)
[SuperSU] ashyx:
Thanks, I'm aware of the thread, but it's not what I'm looking for.

SuperSU supports system mode officially up to Marshmallow.

In discussions Chainfire mentioned SuperSU isn't compatible in System mode on anything greater than Android 6.

However has also said future versions may be.
[SuperSU] mauam:
And how about with SuperSU Config!?
[SuperSU] ashyx:
The thing is its just config options for supersu. It seems however the actual binaries are not compatible with Android 7 or indeed Android 7 isn't compatible with system installs.

What is confusing is that chainfire mentions that for SYSTEM installs on Android versions greater than MM, with Supersu config, that ROM support is required. What sort of ROM support? :confused:
[SuperSU] mielletseed:
Since systemless install needs to patch SE Linux permissions of the boot image, I suppose that a ROM needs the right SE Linux permissions ;)
[SuperSU] ashyx:
The selinux permissions are not a problem. Both systemless and system installs require a patched Sepolicy or permissive kernel on anything android 6 and above or 5.1.1 in the case of Samsung devices.

I can patch Sepolicy or just use a permissive kernel.

However neither works on Android 7.
[SuperSU] kien_vip:
I manage to implement some init.d tweaks in stock samsung MM without root (because get yellow triangle warning if rooted). So i edited init.qcom.post_boot.sh to execute init.d scripts but it not works. ... But after i root device with supersu, all scripts execute successful. What prevent scripts modify system. anyway to using init.d features without root??
[SuperSU] Ch3vr0n:
You're in the wrong forum for that question. You need to ask in your device forum. This topic is for SuperSU specific things. Whatever is preventing your scripts from modifying system is not an SuperSU issue but an issue with your script / rom
[SuperSU] osm0sis:
And it's SELinux preventing it without root, for the record. ;)

He can try my init.d injector from my Odds and Ends thread, but it might run into the same issue.
[SuperSU] elliwigy:
system root works fine with SamPWND.. as far support i am not sure lol.. maybe dm verity disabled?
[SuperSU] Chainfire:
v2.82-SR5 released; release notes here: https://plus.google.com/+Chainfire/posts/BanQpQ1QPEg
[SuperSU] ashyx:
SamPWND?
[SuperSU] osm0sis:
suhide-lite v1.09 app updated correctly, but just as with SR4, SR5 SuperSU app did not update correctly. I had to extract it from the zip and install the apk manually. This seems to only occur on Oreo.
[SuperSU] bggold:
Mine updated to v1.09 with out any issues. Side note sr5 updated too.

---------- Post added at 12:22 AM ---------- Previous post was at 12:18 AM ----------

Flashed sr5 after TWRP and all is good.

Thanks Chainfire
[SuperSU] chazall1:
Great Job. All function great here Oreo TWRP and your new SR5.

Thank You
[SuperSU] Slim2none4u:
I can confirm. Works on system root with SamPWND.
[SuperSU] sharkie405:
Yes! So glad to have SuperSu back! Working perfectly on my Pixel XL on Oreo with Twrp 3.1.1!

No disrespect to Magisk, but I hated having to use it. Being able to use SuperSu again is like eating my favorite comfort food after not having had it for years.
[SuperSU] Ibuprophen:
[MENTION=631273]Chainfire[/MENTION], Confirmed working without an issue on my KLTEVZW & D2VZW.

Thank you very much!

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

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

PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
[SuperSU] Alxoom33:
For me, a soft reeboot fixed the update of SR5.
[SuperSU] sgtslaughter64:
I am trying to update to SR5, but I keep getting error messages that the zip file is corrupt. Any ideas?
[SuperSU] jcmm11:
Bad download? I show an md5 of f20d6d46b454cb74470977cb445eb8e4 if you want to check.
[SuperSU] ALIGATOR26:
Thank you. [emoji6]

Trimis de pe al meu SM-G930F folosind Tapatalk
[SuperSU] TheBurgh:
Can anyone verify if we have a working ADB with this version? I apologize if wrong thread.
[SuperSU] DEVILOPS 007:
If you're referring to the ADB by osmosis then yes it works.
[SuperSU] osm0sis:
Damn I forgot we discussed that last time too; delayed processing. Weird that it worked immediately for suhide though.
[SuperSU] Ch3vr0n:
Flash SR5 and SuHude 1.09 in 1 go with flashfire, extra no (soft) reboot required. After standard reboot due to flashing SU, app immediately said SR5 on my 6P
[SuperSU] clothednblack:
Tried to use flashfire with twrp 3.1 but upon reboot I still had root but no twrp. Figured I'd test it out to see if it was possible lol. Will just have to wait until after work.
[SuperSU] Ch3vr0n:
It is possible, your flash a recovery through the 'flash firmware' option not flash zip

Sent from my Nexus 6P with Tapatalk
[SuperSU] clothednblack:
Tried it, asks for what slot but nothing after hitting the [emoji736].
[SuperSU] KaMyKaSii:
Try flashing TWRP first and then SuperSU v2.82-SR5 instead of using Everroot

https://plus.google.com/+Chainfire/posts/BanQpQ1QPEg
[SuperSU] clothednblack:
I disabled everroot in flashfire then flashed twrp, lost root as expected but twrp only shows the splash screen so I will just fix it when I get home from work as now I can't flash anything due to not being rooted anymore. Was trying to avoid the pc route haha
[SuperSU] AP2FTW:
I apologize for this most likely noob question...how do you create number 2? I have no idea how to make a script please help..
[SuperSU] osm0sis:
I've just posted a command to do all the setup at once to the AdAway thread. You should direct any further questions over there.

https://xdaforums.com/showthread.php?t=2190753
[SuperSU] clothednblack:
All fixed.

Flash-all - w

Fastboot twrp

Installed twrp

Used twrp to flash su and suhide

Root is back and twrp stuck.

Feels good!
[SuperSU] KaMyKaSii:
I saw that you have solved the problem, but you have to know that the purpose of FlashFire to allow several actions and choose the order of each is precisely to automate processes that would take several steps in recovery. So remember that next time, there was no need to restart between the flash of TWRP and SuperSU. Probably the TWRP stopped at the logo was caused by you doing a dirty flash instead of restoring the stock boot.img first
[SuperSU] clothednblack:
Is there a way to use flashfire for the Oct security ota that keeps popping up or do I need to start with the fastboot of boot IMG again? Kinda missing my N6 at this point lol
[SuperSU] badhabit_wb:
Just download the ota. put it on the phone and then direct flashfire to the ota. That's by far the best way to install it in my experience. It worked great with my Pixel.
[SuperSU] clothednblack:
I was thinking about that, but do I want everroot to flash too or would that cause an issue. Also, do I still toggle "mount" on?

Flashfire pops up with asking to install the ota, just didn't know if I need to change any settings or let it do its thing as is.
[SuperSU] badhabit_wb:
I just clicked on the + icon, flash zip or ota and then didn't change anything else and flashed it. I didn't get around to doing it until Sunday but that worked flawlessly. Just give it time to reboot. It took a few minutes so be patient.
[SuperSU] clothednblack:
Flashfire failed, I will try later after work.

Lost twrp and took me back to an earlier su version. I will stop using flashfire and stick with using a pc
[SuperSU] rubentkato77:
will this work on moto g 2nd generation xt1064, android 6.0, unlocked bootloader, twrp 2.8.0.1 ? can I flash it via twrp?

Sorry for my noob question, I just got this phone and want to install custom roms.: Nougat.

Regards.
[SuperSU] Chainfire:
Announcing my retirement from developing SuperSU
[SuperSU] gianton:
That's a sad day...

Thanks a lot for all the hard work you put into Android development for so many years. Hope you'll be around and see your work again.
[SuperSU] Megaflop666:
Thank you for all your work over the years!
[SuperSU] badhabit_wb:
Thanks for all you've done. We will surely miss your work!
[SuperSU] osm0sis:
Congratulations. Much deserved. :)
[SuperSU] GuardianUSMC:
Won't double post this.
[SuperSU] laupuy:
Hi Chainfire, thank you for everything and good continuation in your new life ;)
[SuperSU] DingoDingo:
Thanks for everything, wish you all best in future, it has to be a great relief for you, new energy for new projects.
[SuperSU] Ch3vr0n:
A well deserved retirement but that does bring the hope that ccmt won't bring supersu to a total crappy (spyware infested) app, preventing stable use with flashfire etc.

[MENTION=631273]Chainfire[/MENTION] this does audio bring up multiple questions

- how will this affect your development for flashfire?

- How will this affect the creation and release of SR's?

- who's going to respond to questions, posts etc in the stable and sr thread...

Sent from my Nexus 6P with Tapatalk
[SuperSU] rubentkato77:
Sad notice, thanx for all your hard work.

Best regards.
[SuperSU] xV1CT0Rx:
Thanx for all the time and effort you put in this and in general in the whole root section, you brought so many people so many great apps and I'm sure you will continue this wherever you will be working now and in the future!

I followed you since the times with my Galaxy S2 and now I wish you good luck with your new projects and working places and hope to hear from time to time from some of your new (and furthermore continued old) projects, ideas and apps.

Greetings and a good time :)
[SuperSU] corkiejp:
To ChainFire: -
[SuperSU] Locura18:
Congratulations. Thanks for all your hard work
[SuperSU] Wolfcity:
[MENTION=631273]Chainfire[/MENTION]: I can't thank you enough for what you have done for the whole android world. It's a sad day losing such a talented and gifted man.

But at least I've got a good message (even if it may just one for me):

After having problems with SuperSU since 2.79 (the binary occupied thing) and switching to magisk for that time I used an update of my rom to give SuperSU 2.82 SR4 a shot and everything is working well.

So I'm back where I belong, been a su guy since it's release.

So I wish you all the best, it's time to move.
[SuperSU] surubutna:
What about Magisk?
[SuperSU] Alxoom33:
Thank you for all that you have done, that has benefited all of us

"Super Super Users". I hope that you enjoy your retirement and your future endevours.
[SuperSU] shaggyskunk:
[MENTION=631273]Chainfire[/MENTION]

Thank You for your Tremendous & Tireless Dedication to the Android Community!

Your Outstanding Contributions (Massive Understatement) have made SO MUCH of what we enjoy possible!

I know that we all hope that you will stop by from time to time!

Enjoy your Thoroughly Deserved Retirement!

shaggyskunk ?
[SuperSU] mark manning:
Sorry to drop in but had to clean up some of that ridiculousness smh.....

Thread Cleaned