yashsingh1/xdaforums huggingface dataset:
[SuperSU] Wolfcity:
No, as said above it's 2.82 SR5.

[MENTION=631273]Chainfire[/MENTION] released a version of SuperSU 2.82 SR5 build on his own servers. At that time he was working together with the guys from CCMT but that build was definitely [MENTION=631273]Chainfire[/MENTION]s work.

If you search the thread you'll find that info somewhere.
[SuperSU] zputnyq:
Anyone ?
[SuperSU] palmbeach05:
Systemless busybox? As in magisk module?
[SuperSU] zputnyq:
Not sure about it. It's busybox by [MENTION=4544860]osm0sis[/MENTION]

It's placed on /sbin/supersu/xbin
[SuperSU] Didgeridoohan:
Have you verified that the script doesn't execute or if it's just the command? Add something else to the script, like a touch command to create a file in /cache so you know that the script has executed. If that works it's the command itself that's not working as expected.

If a command that I know works doesn't seem to execute in a boot script I've found that it's often caused by running the command at the wrong time. Usually fixed by running it later in the boot process.
[SuperSU] zputnyq:
Oh, I've ever tried by giving "sleep 60" then my device bootloop, I think the script executed.

Any suggestion for the correct timing ?
[SuperSU] Didgeridoohan:
That could be caused by you blocking boot with the sleep command. Are you running it in a subshell? Something like this:

#!/system/bin/sh
{
sleep 60
echo 50 > /proc/sys/vm/swappiness
} &

That will not block anything, but will still wait with running the command.

For finding the correct timing, start with 60, reduce to 30 at next boot, and so on until you've honed in on a sleep time that works but's not too long.
[SuperSU] zputnyq:
Yes, I wrote the same as yours.

Ok I'm gonna try to reduce the sleep time
[SuperSU] Didgeridoohan:
Where you using curly brackets? Because in your original post I saw you had regular parentheses and that won't work the same.
[SuperSU] zputnyq:
Sorry, it was my eyes.

I thought that was regular parentheses.

I've just tried & no effect that's because regular parentheses, but so far no problem with reduced timing.

I will try with curly brackets.

Thank you so much for your guide
[SuperSU] jcmm11:
Try this:

#!/system/bin/sh
{ until [ $(getprop sys.boot_completed) = 1 ]
do
sleep 1
done

echo 50>/proc/sys/vm/swappiness
}&
[SuperSU] zputnyq:
The format given by [MENTION=4667597]Didgeridoohan[/MENTION] works eventhough I experienced something confusing. With reduced timing under 60 doesn't give effect, with 60 causes bootloops, so thne I decide to lengthen it to 120, then it works.

But Thank you so much for the alternative format, I'm gonna keep it & try it. I really appreciate it :)
[SuperSU] Didgeridoohan:
The format given by [MENTION=4487388]jcmm11[/MENTION] is far better, and probably more consistent.
[SuperSU] goldmobile:
Please pro version 2.82 sr5
[SuperSU] GopalKaul:
No warez here and project dead.
[SuperSU] guest4711:
You could try the following: Download SuperSU Flashable and install via TWRP. Enable pro features. After this, update the application by Google Play Store or Aurora.
[SuperSU] goldmobile:
How enabled pro version? And after update google play after not have free?
[SuperSU] guest4711:
I don't use it anymore because all my devices support magisk now. But as far as I remember there is an option in settings - advanced (or like that) to enable pro features. And you should enable it before updating.
[SuperSU] dahawthorne:
If I remember correctly (I haven't used SuperSU for a couple of years) Chainfire was generous enough to provide an "enable Pro features" in Settings for people too cheap to buy it. Since he no longer supports SuperSU, I doubt that he would object to people using this feature now.
[MENTION=8010004]guest4711[/MENTION] - sorry, I missed reading that you'd just suggested the same thing. Duh...
[SuperSU] palmbeach05:
Agree with above, download sr5 from link on post 1, then go into app settings, sroll to the bottom, enable pro features. App will have to restart
[SuperSU] casouzaj:
You could make a backup of your phone's TA partition, use that backup to build a new kernel which would contain its DRM keys, unlock the bootloader, fastboot TWRP to the FOTAKernel partition and the built kernel to the boot one. Then, through TWRP, Install Magisk, in order to get root access. Your phone would behave exactly as if its bootloader was locked. I did it my late Z3 Compact phone, but it ran Marshmallow, then.
[SuperSU] razes:
Thank you casouzai for your suggestion. Surprisingly, I was able to restore root simply by installing the Supersu.apk (v.2.79). I don't want to move to Marshmallow because I'll lack the stamina mode on my Xperia and that firmware more energy consuming. Also, it seems Magisk doesn't support the Lollipop (works on 6+).

BTW what is the FOTAKernel partition?

Xperia Z3 compact

Lollipop 5.1.1

---------- Post added at 09:52 PM ---------- Previous post was at 09:52 PM ----------

Thank you casouzai for your suggestion. Surprisingly, I was able to restore root simply by installing the Supersu.apk (v.2.79). I don't want to move to Marshmallow because I'll lack the stamina mode on my Xperia and that firmware more energy consuming. Also, it seems Magisk doesn't support the Lollipop (works on 6+).

BTW what is the FOTAKernel partition?

Xperia Z3 compact

Lollipop 5.1.1
[SuperSU] ashyx:
Magisk 4.2+
[SuperSU] Wolfcity:
Correct.

-Android 4.2+: MagiskSU and Magisk Modules Only

- Android 4.4+: All features available

- Android 6.0+: MagiskHide guaranteed support

- Android 7.0+: MagiskHide full protection

- Android 9.0+: Magisk Manager full hide capability

source:

https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445/post68966662
[SuperSU] casouzaj:
The FOTAKernel partition is where the stock recovery residea, in order to process OTA (acronym die Over-The-Air) upgrades, but, since the Marshmallow release, back in 2016, Sony hasn't released any new firmwares for the Z3 series, neither will ever do so. So,, why not give that partition a far more useful cuatom recovery?
[SuperSU] pramodinchur@gmail.com:
I haz root
[SuperSU] palmbeach05:
I have magisk induced root
[SuperSU] Lughnasadh:
You also posted your gmail account. Probably not a good idea if it's real.
[SuperSU] DEVILOPS 007:
I haz root too?
[SuperSU] Knightrider_kit:
Lost root

Using SuperSU 2.82. Added to path with export PATH=/system/xbin/misc:$PATH checked path with echo to make sure it was added then closed terminal. Lost all root and SuperSU says su binary occupied. Tried rebooting, terminal reports only bin and xbin in path now but su still occupied. Requesting help before I try something drastic. Appreciate any help.
[SuperSU] dahawthorne:
I guess you know after extensive research that SuperSU is now almost 3 years old and not maintained.

Use the SuperSU removal script and install Magisk, which is regularly maintained and pretty much bulletproof these days.
[SuperSU] palmbeach05:
And then i learned of magisk and boom! I solved all my issues. All hail topjohnwu!
[SuperSU] Knightrider_kit:
I would like to use Magisk but as far as I know I cannot. Let me explain, I have an obscure device that has been locked down in many ways. I cannot adb to it, cannot seem to get a non stock recovery working on it, cannot access the boot loader ( all I get is a black screen). The only reason I can root is because of a flaw in the way that the manufacturer did ota's that let me hijack their mechanism. I am also stuck with the stock ROM which is jelly bean. But if you have ideas on other ways to root and or mod this device within the stated constraints I would love to hear them. Update, I was able to get SuperSu to uninstall and was able to reroot the way I had before.
[SuperSU] Strephon Alkhalikoi:
You didn't explain that in your post that [MENTION=6161558]dahawthorne[/MENTION] quoted. It would have helped significantly, because then no one would be recommending Magisk to you. Magisk doesn't support Jellybean.
[SuperSU] palmbeach05:
Jellybean 4.1 is not supported. However, jellybean 4.2 and up is supported.
[SuperSU] Knightrider_kit:
I have jb4.2 but the problem is to install magisk you either have to have a custom recovery or access to fast boot through adb both of which I don't have. This is why I've been trying to port my own recovery. I know that its possible to write to the ROM from recovery but only apparently from preloaded commands to the recovery. I've been trying to educate myself on how this is done but have not found much on it.
[SuperSU] Strephon Alkhalikoi:
When did that change? Last I read about it, Magisk only supported as far back as KitKat. Not that it matters for me, as I don't have devices that old running on a daily basis.
[SuperSU] palmbeach05:
https://github.com/topjohnwu/Magisk
[SuperSU] Strephon Alkhalikoi:
Apparently things changed, but honestly I don't care so much that I have to go to his github to read it. As I said before, I don't have devices that old running on a daily basis.
[SuperSU] palmbeach05:
Its ok. I still have my old atrix 4g and droid x, both got left behind on stable kitkat releases, i had to go find that info out after i dropped off the radar for a few yrs and came back to see how smooth and easy to use magisk was.
[SuperSU] Sjain11:
Can the supersu Uninstaller zip be flashed via stock recovery? Since i dont have twrp installed.
[SuperSU] Strephon Alkhalikoi:
No. But you also don't have to flash TWRP to recovery either. Use fastboot to boot a copy of TWRP on your PC, and then you can run the uninstaller.
[SuperSU] Sjain11:
I appreciate your help. Could you please tell the steps or guide me to some link? I have used fastboot before but I don't know the exact steps and commands.
[SuperSU] dahawthorne:
[MENTION=7079349]Sjain11[/MENTION]

I'd be interested too.

It may be that Strephon means to temporarily boot TWRP on your device, which will give you TWRP functionality without flashing TWRP permanently.

To do this, when you're in bootloader and connected to your PC, you can use the command window to type

fastboot boot twrp.img

(Obviously use your TWRP image name. The image needs to be in the same directory as fastboot).

Once in TWRP, do what you need, reboot, and you'll still have stock recovery.
[SuperSU] guest4711:
Think you mean

adb fastboot boot pathname-of-twrp.image

, e.g.

adb fastboot boot d:\\android\\twrp3.0.1.img
[SuperSU] dahawthorne:
Seriously? Do you think that after 8 years' Android experience I don't know how to use Fastboot? I specifically stated "when you're in bootloader and connected to your PC". Your ADB command would not work in Bootloader.

We all want to show off our extensive knowledge, but please make it sensible and relevant.
[SuperSU] DB126:
lol - all hail the butthurt Android God.
[SuperSU] dahawthorne:
Not butthurt, but thank you for the rest... :)
[SuperSU] Strephon Alkhalikoi:
Yeah, my mind wasn't working correctly when I wrote my reply. You managed to understand what I was driving at however. :)
[SuperSU] guest4711:
Thanks for pointing me into the right direktion. I did not get it - on my sammy devices a download mode which is not compatible with fastboot.

But I do not have any thoughts about anybodys knowledge... and it was no offence. If you got it this way I'm so sorry. It was not intended.
[SuperSU] dahawthorne:
[MENTION=8010004]guest4711[/MENTION]

No problem. It's very easy to misunderstand comments, especially without all the background information.

Thanks for explaining. Sorry for biting your head off... :)
[SuperSU] Ali.909:
:fingers-crossed:
[SuperSU] palmbeach05:
Awesome an empty post lmao
[SuperSU] ze7zez:
The post has been divided and is on page #1229. ;)
[SuperSU] palmbeach05:
Which is a 404, and kinda not possible yet, as we are 3, now 4 posts into page 1228, out of 10 or so posts.
[SuperSU] williamshockley:
Hey chainfire I have this lastest 2020 firmware for my samsung j7 prime?
[SuperSU] williamshockley:
Hey chainfire I have this lastest 2020 firmware for my samsung j7 prime: https://www.sammobile.com/samsung/g...e/SM-G610F/INS/download/G610FXXS1CTD1/348733/

I tried installing CWM and TWRP(https://xdaforums.com/t/recovery-root-twrp-3-1-1-1-galaxy-j7-prime-sm-g610f-2016.3617377/)

They work fine but then I can't install Super SU(maybe). because I get into bootloop even after installing no no-verity-no-encrypt

Anyone tell me how to get root for latest android firmware for my samsung mobile? (SM-610F)

@Chainfire also I'm a fan of you since 2012. I want to be you :)
[SuperSU] daywalk3r666:
for root flash magisk..SuperSu is sold and eol
[SuperSU] williamshockley:
ok any tutorials on how to use magisk for samsung firmware?
[SuperSU] daywalk3r666:
its the same as supersu..flash it via twrp
[SuperSU] Wolfcity:
Here's all you have to know. Github is also the place to download Magisk:

Installation

The Magic Mask for Android

topjohnwu.github.io

Great guide and troubleshooting:

{{color text="Magisk and MagiskHide Installation and Troubleshooting gu:Magisk and MagiskHide Installation and Troubleshooting guide

www.didgeridoohan.com

XDA thread:

https://xdaforums.com/t/magisk-general-support-discussion.3432382//unread
[SuperSU] andrew2432:
I <3 cf as well lol what I wouldn't give to see him and tjw work in tandem. Nice to see this thread light up again, nostalgia at its finest. Reboot???? Sorry lol
[SuperSU] williamshockley:
thankyou everyone for the help. I rooted by Sam**** with the help of magisk and fooked all the bloatware. Feels light on my ass. Thanks you again
[SuperSU] Wolfcity:
@gadiku3

Why are you quoting some posts from 2014 without any comment?
[SuperSU] Frex77340:
Klyde KD-1280 tesla Headunit

Small technical question, when you go to Recovery mode what I can do with the two welded wires, how to validate the menu choices when you do not have a high and low volume key and Power, I do not understand how to do ?

For info My steering wheel orders do not work, I tried with a mouse it works, I can choose the lines pass into green the choice, but after how to validate?
[SuperSU] mrrocketdog:
not sure if youre asking in the right place , but a search brought up this :

https://xdaforums.com/t/tesla-style-headunits.3512709/

or maybe just search for "headunits"?
[SuperSU] Frex77340:
Thank you indeed, I realized too late that I was not in the right place, thank you for the link
[SuperSU] Cyndaquissshhh:
The memories 🥲

Come back please, Chainfire!
[SuperSU] shoiby:
Any body can help me with this :(
[SuperSU] DLUX24:
IMO, those "battery saving apps" are just as bad for your battery.

But go into SuperSU settings and deny privileges to that app then reopen the app and grant permission
[SuperSU] shoiby:
Thanx for reply but there is no such thing in the settings here are some screen shots
[SuperSU] DLUX24:
Click on the app in the list when it opens up
[SuperSU] berniesteven:
Or, as last resort go into app manager and clear data for supersu. All your apps will then ask for permission again.

SM-G870A Peace
[SuperSU] ffejy462:
Go to apps tab, not settings, tap on app, tap deny (or your choice), then follow previous instructions.

LG G2 xdabbeb's vs982.5
[SuperSU] shoiby:
But the app du battery saver pro is not in the app list . Is there any way to put it there ?
[SuperSU] Pkt_Lnt:
Root is only used for:

https://play.google.com/store/apps/details?id=com.dianxinos.dxbs.paid&hl=en

Enable that setting and it will prompt for root.
[SuperSU] shoiby:
I did that but it didn't prompt for root it only showes this dialog
[SuperSU] shoiby:
In kitkat with superuser it gave permissions to the DU Battery saver and the option worked but i prefer supersu unfortunately it doesnt do the trick [MENTION=631273]Chainfire[/MENTION] please is there any way to fix this?
[SuperSU] Pkt_Lnt:
You need to contact the DU battery dev then.
[SuperSU] shoiby:
I did but i think its something with the supersu app because root permissions was given by another app called superuser app
[SuperSU] berniesteven:
Did you try wiping supersu data in app manager?

SM-G870A Peace
[SuperSU] egingell:
DUBS is asking or checking for root improperly.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] shoiby:
Yeah i know but my device is rooted & i checked with root checker also i have a lot of apps which granted root permissions by supersu

---------- Post added at 11:56 PM ---------- Previous post was at 11:54 PM ----------

I will try to delete data and report back

---------- Post added 29th December 2014 at 12:02 AM ---------- Previous post was 28th December 2014 at 11:56 PM ----------

Well i didnt find any data to delete only cash i delete it nothing changed
[SuperSU] berniesteven:
Then I would uninstall, wipe dalvik and cache and reinstall. Nothing to lose.

SM-G870A Peace
[SuperSU] shoiby:
You mean the DU BS or supersu?
[SuperSU] berniesteven:
Supersu

SM-G870A Peace
[SuperSU] Pkt_Lnt:
Other apps request root correctly and get it. DUBS is NOT requesting root correctly, does not matter if it worked with superuser, it is not using correct calls for root. The DUBS dev needs to fix it, not Chainfire. You are wasting time in this forum with this ongoing posting.
[SuperSU] egingell:
"Lots of apps" working means they should all be working? That's not how it works. That's a logical fallacy.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] 0.0:
We should all get back on topic. So far, the bugs in v2.42 beta are:

1. Bootloops (I had it once on my Moto X Pure)

2. Flashing deletes the YouTube app (should be a simple fix in the .sh file)

Any other bugs?

sent from my Moto X Pure Edition
[SuperSU] devsk:
I think boot loops on Moto phones with Lollipop is *THE* problem to solve as of now. Without a fix for the boot loops, SuperSU is not at all usable on Moto G 2014. It can take like 7 boot loops and 11-15 minutes to boot, if I am lucky, otherwise, it just shows blank screen.
[SuperSU] jemis1983:
Thank you chainfire for your great work!!!!!

i bought your apk's to encourage you!!!!

I have a question can you update the integrate supersu on mobile Odin pro to the last stable compatible with the leaked Lollipop on note 3 N9005.

I try to inject the root with flashing the rom but without success because the version of supersu its V1.90 or Sam thing else.

Do you think the new beta will be able to get the root without trip knox????

Thanks advance! !!
[SuperSU] Darkangels6sic6:
I have the same issue, but only when it comes to using back to kill function on wanam xposed for TouchWiz roms. With v2.9.9 all works fine. With any version I have tested after that up to the 3.2.7 I get your same issue.
[SuperSU] egingell:
This has been answered time and time again. In fact, someone answered the guy whose post you quoted in the next post.

Edit: "angered" is probably right, too, but "answered" is what I meant.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] Darkangels6sic6:
I scrolled through pages, posts, and searches. Only saw one or two people with similar issue and no answer so I just let it be.

Wasn't a huge issue and been otherwise occupied

Was just making conversation at this point. Time to go search again I guess. Thanks for the heads up.
[SuperSU] kmcphee:
I haven't had any problems with this version. I have Sprint Galaxy S5. I always flash Supersu. Never had a problem. Guess I have been lucky
[SuperSU] berniesteven:
Working fine on att s5 active running dk rom.

SM-G870A Peace
[SuperSU] Darkangels6sic6:
I'm not sure which version did it for me. I think it's 2.4, but ever since then I cannot update su.

That goes for this 2.4.2 as well. The 2.4 worked fine for me on lollipop however.

On my sprint note 2 on stock and stock rom kit Kat however it's a big no no. Something seems to have gone south for many in the last couple versions.

And as far as the wanam xposed thing goes I tried all the fixes, claiming it's a su issue. Turning off display and back on, tapping until it registers, checking Disable selinux "just caused reboot", enabling trust system user did not help until after I tried the update and even then only sort if.

But with slightly older su and wanam my phone is working 100% so for me at least we will reach full stability again eventually and patience in the meantime
[SuperSU] Pkt_Lnt:
This will give you a clue.

http://xdaforums.com/showpost.php?p=57181283&postcount=1021
[SuperSU] Darkangels6sic6:
Nothing new really
[SuperSU] Pkt_Lnt:
This will explain, from the Stable SU thread.

http://xdaforums.com/showpost.php?p=57499561&postcount=7826
[SuperSU] Chainfire:
I'd be happy to fix it but I have no clues, no assistance, and no device. I have a 2013 Moto G but as far as I know there's no Lollipop firmware showing this issue for it.
[SuperSU] devsk:
I would help out if you can please create a special build with debugs in it. The debugs should go to the internal storage (which should be easily discoverable and mountable in early boot), so that they are persisted and they should be elaborate enough to catch the issue when the reset happens. We can then go into recovery after the first boot loop and look at the logs from the shell.
[SuperSU] Darkangels6sic6:
I'll have to go read it in a bit. I still planned on reading a few more pages from the other link you gave. I only read about 3 or 5. Just in those couple I meant nothing new. Thank you.
[SuperSU] Frank Westlake:
If you have this particular device see if this will work on it:

http://xdaforums.com/showthread.php?p=56291448

In the root of the ZIP the file 'su-update-binary', a script, should be updated to reflect the 'update-binary' script for the version you are installing, but it still might be useful without that modification.

With TWRP , choose the SuperSU zip to install, then before installing it back up and choose the debug.zip as a second package to install. After installing both an archive of debug files will be saved to the directory you had the debug.zip stored in. '/sdcard/Download' is usually fine.

Frank
[SuperSU] devsk:
Looks like its information gathering from a booted system. Does it gather specific debug information (particularly, SuperSU related information in this case) from a particular failed boot?

Collecting logcat/recovery log etc. after the fact is not useful. We have to gather information at a specific time. The boot loop is like this:

adb reboot

white "unlocked bootloader screen" <============== We need to collect information here and store it in /sdcard.

phone resets

white "unlocked bootloader screen"

phone resets

white "unlocked bootloader screen"

...

Debugs will need to go into the SU binary and the daemon for us to see them. So, this will need an update from Chainfire.
[SuperSU] Frank Westlake:
It collects the state immediately after the installation while still in Recovery. It would be better to do as you suggest but that is more difficult and may not be ready right now, if ever. Right now you can use 'debug.zip' and examine the files to see if there is anything that might indicate why the installation is causing boot failure. The 'su' installation script does not check for mount errors, or other errors, and does not verify file writes, and these are things that the debug.zip might be able to show you.

Frank
[SuperSU] devsk:
IMO, the installation is not a problem. The root actually works perfect when it fully boots. It fails 6 out of 7 times (sometimes even more) and it is likely a script failure which is catastrophic (e.g. init dies) or SU binary causing some sort of kernel panic, which could be a race condition (which the SU daemon wins some of the times). IDK. The only way to know is to put debugs in the SU interactions in the early boot and persist them to disk.

Chainfire: if the logging routine (that gets called by SU and SU daemon) can stash the logcat and dmesg in /sdcard, that would help narrow it down even faster.
[SuperSU] Devilix:
I'm in this situation, i dont know why but i can't press allow or deny on supersu popup screen, when i use long press back button for terminate the apps...

there is anyone can help me?
[SuperSU] Pkt_Lnt:
Check the link in this post.

http://xdaforums.com/showpost.php?p=57842121&postcount=1255
[SuperSU] Devilix:
Checked, and? i still not able to press nothing on that popup, only for Android System i get this issue.

I have removed the tic for disable tapjacking protection, but still not work...

Any ideas?