yashsingh1/xdaforums huggingface dataset:
[SuperSU] IronTechmonkey:
In re this https://xdaforums.com/showpost.php?p=72745688&postcount=10526

Clean flashing CM12.1 with Open Gapps Pico and SR1-SuperSU-v2.82-SR1-20170608224931.zip On Moto E 2nd Gen 3G (Otus) and using TiBu as the primary app that could induce the issue: I had no problem after installing TiBu from Playstore, until attempting to restore apps via TiBU (user apps only, AFAIK no system components) when TiBU FCed during the process and various apps and services including Google services and native CM settings started to FC regularly.

One on hand I'm tempted attribute this to TiBU restoring app data (which I've gotten away with for a few years) however the first time I noticed the issue was not during a restore but after updating SuperSU via Playstore, having made no other changes. In any event I suppose more tests, only restoring aps without data TiBU or installing from Playstore (x85 apps = ugh) might be in order.

FWIW the attached log should span several of the FCs that occurred.
[SuperSU] martyfender:
Have you tried flashing the latest supesu.zip from the op? If I'm not wrong, it is newer and has some fixes over the playstore version. Others, let us all know if I am wrong.
[SuperSU] simpa63:
Root Umi plus E

Salve, ho un umi plus E. Ho fatto il root con supersu, come da voi indicato, riuscito. Ma quando faccio il reset di fabbrica il root si disinstalla. Come risolvere il problema? Grazie
[SuperSU] ZRK_NanDRD:
Use english
[SuperSU] Chainfire:
This log only contains a single crash, and I see no reason to believe the cause for that is anything else than TiBu. However, just because it isn't visible doesn't mean it isn't true :)

It appears to be native code crash in TiBu; an invalid or double free.
[SuperSU] IronTechmonkey:
As to TiBu, IDK what double free is (and cant find any other references to it) but it is the paid version, with app and key installed from Playstore post-flash. That being said, one oddity in this test as opposed to others was that TiBU offered to restore previous device ID, which I've never seen when flashing across different Android versions. I had been running LOS 14.1 w/LOS SU, then flashed LOS14.1 w/SuperSU for a quick test, then flashed LOS CM12.1 w/SuperSu in which these issues occurred and were (minimally) logged.

Having seen the device ID quirk in TiBu I knew this was headed for another test so I did not put much time into logging, sharing the one short log I did get. To your point, everything about this test does seem related to TiBu itself or something I did wrong with it but, then I just cant wrap my mind around how it relates to the initial instance of the problem. Next test will have TiBU installed without restoring previous device ID and maybe with all apps installed from Plays store of apks instead of restored via TiBu to start fresh there. Thanks for the look.

---------- Post added at 05:28 AM ---------- Previous post was at 05:26 AM ----------

Not wrong, but perhaps not reading the details of my post, the second line of which indicates SR1-SuperSU-v2.82-SR1-20170608224931.zip;). That being said, always, good advise to use newest version, which was in fact the purpose of this test. :)
[SuperSU] ktmom:
Double free is a type of error where a program frees the same memory twice. This can lead to undefined crashes. The problem program doesn't have to be the one that crashed. If a program is assigned memory "double freed" by a different program, the first can get caught in the confused memory state.

I've been using TiBu forever ?. I'm careful not to restore system settings, nor apps data on an OS version update. I've had no trouble. That said, I've not tried on 2.82.
[SuperSU] IronTechmonkey:
That seems to line up with the incongruity of TiBu offering to restore previous ID and restoring settings specific to a CM12.1 installation that had not been on the device for a few months while it ran LOS 14.1. My flashing progression is usually tidier than that (eg I've never gone back and forth like this except for clean ROM tests without restoring apps in TiBU), so I've gotten away with restoring app data (but never restore system data) in TiBu...until now. Looking more like TiBU and flash process issue than a SuperSU issue (except for the first incident that brought me here), and thanks to you and Chainfire my next test process is clear.
[SuperSU] chazall1:
I have had no issues restoring apt data and apps in TiBu.
[SuperSU] IronTechmonkey:
Not sure what Android version you are running or the recent ROM and TiBu history of the device but I would assume it's not CM12.1 with the same history as in my report. Same device with LOS14.1 did not have the same issues, and it may be that the TiBu history of managing the device ID (described in my posts) is an underlying cause. That being said, I'm now looking toward TiBu as cause rather than SuperSU so I dont want to get too far odd topic here.
[SuperSU] ndfan77:
Somehow I've lost MTP file transfer after rooting.

Android File Transfer pops up, shows the sdcard contents, and then immediately throws an error saying "Can't access device storage, if your device's screen is locked...". (Of course my phone isn't locked.)

These are the steps applied in order to root (on a factory fresh OTA with NKG47L):

fastboot boot twrp-3.0.2-0-RC1-fastboot-marlin.img

from TWRP RC1: flash twrp-pixel-installer-marlin-3.1.0-0RC2.zip

reboot system

reboot recovery

from TWRP RC2: flash SuperSU-v2.82-SR1-20170615211546-PixelFix.zip

reboot bootloader

fastboot boot boot-to-root.img

reboot recovery

from TWRP RC2: flash ElementalX-P-1.12.zip

I've installed quite a few of my normal apps before I found MTP wouldn't work. So, now I don't know what to do.

As test steps, can I...?

reapply boot-to-root.img with a custom kernel installed and be OK?

Or, is it easy to revert to the stock kernel?

Something else???

Any help would be appreciated!
[SuperSU] The Analog Kid:
He says he have an UMI plus E, had root by installing SuperSu as indicated, though, when performing factory reset, root disappears. Then asks how to solve the issue and finally thanked. That's it
[SuperSU] ktmom:
If the above is an accurate translation, then that is expected behavior. A factory reset will unroot your device by restoring system, boot and data. Afterwards, you must root again.
[SuperSU] ashyx:
Unless that particular device is different to other Android devices, a factory reset does nothing but format the data partition. It neither restores the boot or system partition to factory state.
[SuperSU] mielletseed:
It's the expected behavior but you are wrong! A factory reset only cleans the internal memory (/data, /cache, /sd-card) but doesn't "restore" /boot or /system (how should the function do that? there is no backup of the partitions available). When you have classical root (system mode) a factory reset wouldn't remove root but systemless root only modifies the boot partition (which stays changed after factory reset) and stores all necessary data for root in the /data partition which was wiped due to the factory reset ...
[SuperSU] yung40oz84:
no matter what I do I cannot change anything on /system? I am running Pixel XL, PN, EX kernel 1.12, and the latest pixelfix supersu sr version. I have tried mounting /system with adb shell on mint with both ways as suggested earlier in the thread (one way flipped) and neither worked. Tried in terminal on phone, no dice. I will grab a log here and share then, just wanted to report.
[SuperSU] misslebulletttttt:
the current twrp could not boot up from a plain pixel xl with OPP3 ??

anyone upgrade the pixel XL to o-preview3 and and install TWRP ??

mine stock pixel XL with OPP3 can't boot into any version of available twrp using fastboot boot twrp.img,

it keeps bootlooping in TWRP screen, no root before,device is unlock,

do I need to revert it back to android N for installing twrp then use twrp to flash OPP3 OTA ?
[SuperSU] shaggyskunk:
Maybe try posting your issue on the TWRP Thread for your device - What you are posting about has nothing to do with SuperSU ;)
[SuperSU] rotational:
FWIW, my Nexus 6P is working properly with the latest 2.82 SR1 on the July 7.1.2 (N2G48B) update after having the previously reported failures with 2.80 and 2.81.

Thank you for all of your hard work CF.
[SuperSU] Jon8RFC:
If anyone is curious, I updated my Google Store Pixel XL from the June OTA to the July OTA (NJH47B) and flashed SuperSU successfully. My root apps and recovery all function properly.

The PixelFix version ( SuperSU-v2.82-SR1-20170615211546-PixelFix.zip ) of SuperSU is still good to go:

https://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/post72686197#post72686197
[SuperSU] peterlee928:
same here except i have the verizon pixel xl. no custom roms or kernels - all stock.
[SuperSU] GopalKaul:
For [MENTION=631273]Chainfire[/MENTION],

I am on nexus 5 on LOS based custom ROM. No problem with SuperSU2.80,2.81,2.82!!!
[SuperSU] Camlin3:
Sir, [MENTION=631273]Chainfire[/MENTION]

i am trying to get root access in Anbox (Ubuntu)

Arch:-x86_64

Android Version:-7.1

Any suggestion. There is no method to flash recovery zip.
[SuperSU] GopalKaul:
Device?
[SuperSU] amitroutray:
Need to change my SELinux mode to permissive but when I open the SElinuxModeChanger apk it is not getting the Su access :(

Triggered from rn4
[SuperSU] Ch3vr0n:
Most likely that thing's su path are hardcoded and don't support Systemless SU. The dev needs to fix that. This is not a SuperSU issuer
[SuperSU] GopalKaul:
Better use the flashable zip for it..
[SuperSU] amitroutray:
Any link?? Flashed the below link but not working :(

The SELinux Toggler.ver.4.3.7.build.60.zip

Triggered from rn4
[SuperSU] Paschfire:
Have you checked the Grant/Denied status within SuperSU Manager?
[SuperSU] amitroutray:
I am always preferring Grant only.

Triggered from rn4
[SuperSU] Tanis64:
My Main-Device is a Samsung Galaxy SIV (I9505) still running a rooted 4.4.2 (I9505XXUGNK4_DBT) using xposed.

Comming from SuperSU 2.79 I update over Play-Store to 2.82 and later to 2.82 SR1 over PhilZ Recovery.

Everything seems ok so far, but

When the phone runs more then approx. 10-12 h after a restart somethng strange is happen

- massive Battery draining

- number of Processes running is rising from approx. 350-375 Processes (which is normal for my installations) to 550, up to 570, looks like there is a rabbit (forkbomb) jumping around.

- RAM goes down to 150 MB Free RAM or lower, so some Apps cannot start correctly anymore

- Phone massively slows down

- Phone doesn't go to Deepsleep and keeps warm.

Here only a reboot will bringback the phone in normal behavior for the next 10 to 12 hours, and then the strange behaviuor starts again.

Flashing back to SuperSu 2.79 SR3 brings the phone back to usual behaviour as it should be.

I'll stay now on SuperSu 2.79 SR3
[SuperSU] andrew2432:
7.0 based? What's your lag/system speed??
[SuperSU] GopalKaul:
2.3GHz? What's the speed? And LOS is 7.1.1 based.
[SuperSU] andrew2432:
That's the processor? I just meant how's the speed and reaction of the ROM!!
[SuperSU] ZRK_NanDRD:
There's the problem I guess
[SuperSU] jemmini:
[del]
[SuperSU] GopalKaul:
Awesome!! Zero lag... And pixel like. And it is not LOS, it is just LOD based
[SuperSU] andrew2432:
Out of thanks...maybe I won't forget if I quote you!!!
[SuperSU] GopalKaul:
Sure. You use the N5? Me too!! I use Dark ROM, try it!! It won't disappoint
[SuperSU] jemmini:
Go to privat! Enough to spam your offtopic.
[SuperSU] wetxxx:
It's any reason to install SuperSu 2.82 SR1?

I have HTC 10 device and SU 2.82.

"Live long and prosper"

HTC 10 Android 7.0 Stock Rom 2.41.401.4
[SuperSU] sagnikroy360:
Your app is great!
[SuperSU] GopalKaul:
[MENTION=631273]Chainfire[/MENTION], any lead on the Nokia 6?
[SuperSU] Crazy Chuckster:
I installed the v2.82 SR1 today on my Nexus 5x after the latest July nougat update. My device is rooted but there is no SU icon in my installed apps. How am I able to uninstall SU for future updates?
[SuperSU] jcmm11:
Extract the apk from the zip (it's in the common folder) and install it. For future updates just flash a new zip.
[SuperSU] Crazy Chuckster:
TYVM! Good to go now!
[SuperSU] wetxxx:
Very fast. When install su 2.82 sr1 from twrp my htc10 was a speed demon. I don't know what's happening before ;)

"Live long and prosper"
[SuperSU] darkragnarok100:
Hi,

Yesterday I flashed SR1-SuperSU-v2.82-SR1-20170608224931.zip using TWRP on my Nexus 5 purenexus_hammerhead-7.1.2-20170613-UNOFFICIAL.zip from this thread https://xdaforums.com/google-nexus-5/development/rom-pure-nexus-substratum-t3477787.

Everything looks right but after rebooting I do not see SuperSU in my phone and i don't know if my phone was roorted or not so i download Root Checker on Playstore to check and it said "Sorry! Root access is not properly installed on this device".

I do not know what i did wrong so if anyone can help me out, it will be highly appreciated.

Thanks in advance and cheers!
[SuperSU] jcmm11:
Do you know if you have root? (Does an app that needs root work?) If yes then you're rooted but just missing the SuperSU app (which would qualify as "not properly installed"). Extract the apk from the zip (it's in the common folder) and install it.
[SuperSU] darkragnarok100:
Just extracted and install SuperSU apk as you advised.

Installation process is OK but when i start SuperSU app, it said Root undetected and at the end of the pop-up box there is a option HOW TO ROOT and it lead to supersu.com/faq/howtoroot

:(:(:(
[SuperSU] peterlee928:
what phone are you flashing on? if pixel/pixel xl - have you flashed the pixelfix version?
[SuperSU] darkragnarok100:
I using LGE Nexus 5 (not 5x)
[SuperSU] ktmom:
What does the log tell you when you flash the supersu zip?
[SuperSU] darkragnarok100:
It said sucessfull but there is 1 failure just like in the picture so i'm not sure if it is the cause.
[SuperSU] Harrison Le:
Did your rom have rooted before flash SuperSU 2.82SR1?

If yes, I think you should unroot before flash Su 2.82SR1 may just this Su need the clean flash.

I have one time dirty flash this Su 2.82_SR1 and got issue then I have clean flash Rom + SuperSU 2.82SR1 it's okay, everything is perfect!
[SuperSU] darkragnarok100:
This rom comes un-rooted and I did a clean flash (from 5.x.x to 7.1.2) so everything is fresh.

Thanks anyway for your suggestion :)
[SuperSU] ktmom:
Start with updating your TWRP to the latest version. Yes, it matters.
[SuperSU] darkragnarok100:
Can you teach me how to do? I have no idea :D
[SuperSU] ktmom:
give a man a fish and you feed him for a day.... search
[SuperSU] darkragnarok100:
Updated TWRP and then flashed Superuser V2.82 SR1 and ........ IT WORK LIKE A CHARM.

Thanks a lot buddy :good::good::good:
[SuperSU] Pkt_Lnt:
Try this to get it to appear in drawer

Then change the icon to one of the older choices, not Material.
[SuperSU] canodroid15:
[MENTION=4403217]Pkt_Lnt[/MENTION] don't know why I didn't think of that,what a DOOF!! However the only option that doesn't show up in settings is the app icon switcher, still not in app drawer, supersuPRO installed also, idk its weird? Thanks man, at least I can access the settings now.
[SuperSU] jesssiii:
Could it be part of your rom settings now? Look for SuperSU under the settings.

VZW LG G2
[SuperSU] merlin21:
Please could someone describe how to downgrade to v2.35 when already using 2.37?

I tried flashing upgrade-supersu-v2.35.zip via recovery but that was a stupid idea.
[SuperSU] scoobyjenkins:
Try wipe system, flash rom, gapps, SuperSU and any other zips you might use.

*edit* Though if you're on stock I'm not sure... Maybe try the option in app settings to clean up to switch to another Superuser, then flash the version you want?

Tapatalked that shiznit.
[SuperSU] merlin21:
I'm on Pardus 7.7

Thx for fast answer, any suggestions without fullwipe?
[SuperSU] scoobyjenkins:
So can you safely wipe system and reflash rom? You won't lose data. Check my edit in my previous post, that may be better!

Tapatalked that shiznit.
[SuperSU] merlin21:
clean up. in supersu app didn't work- i only can flash 2.37 again. 2.35 want work.
[SuperSU] scoobyjenkins:
May have to wipe then. Can you wipe system and reflash your rom without issue? I'm only familiar with AOSP when it comes to that!

Tapatalked that shiznit.
[SuperSU] 23rdScientist:
Flawless on my SickWitIt S4
[SuperSU] itechengine:
I am using sgs5, tried to root with cf auto root. But SuperSu throwing error (plays tore updated)
[SuperSU] albert_htc:
Is it the same SuperSU I flash to my Nexus 7 2013 as I did to my Nexus 5 ?

If not, please can you provide a link..

Thanks
[SuperSU] Chainfire:
Just posted the v2.38 BETA on the first page

Should work a lot better on the SGS5 Lollipop firmware. Interesting story, but too tired to type it up now. Let me know how it works.
[SuperSU] aguarello:
Please try to update Mobile Odin to be able to flash lollipop ?!

Thanks for all your work!

Sent from my SM-G900F
[SuperSU] ramjet73:
Did you read the post you just quoted?

[MENTION=631273]Chainfire[/MENTION] said he's too tired to type an explanation for a problem with your current phone he just solved at about midnight in his country and you hit him with a request to update an app that isn't even supported in this thread.

You probably didn't mean it the way it came across, at least to me, but please try to be a little more considerate of the developers in the future since they are the reason XDA exists.

ramjet73
[SuperSU] aguarello:
Okay, I'm sorry I didn't mean it that way.

I beg your pardon

Sent from my SM-G900F
[SuperSU] ramjet73:
Not mine, [MENTION=631273]Chainfire[/MENTION]'s, but thanks for the apology and please think carefully in the future about when and how you request things from our developers since they work very hard to provide the tools we all enjoy using with our phones. :good:

ramjet73
[SuperSU] Frank Westlake:
2.38 OK through TWRP on:

- Note_ SGJ-I717 4.0.3

- Note3 SM-N900V 4.3 single user Permissive

- Note3 SM-N900T 4.3 single user Enforcing

Frank
[SuperSU] HorstiG:
OK on STOCK Lollipop S5 (G900F)
[SuperSU] martinoff:
OK on bacon SlimLP
[SuperSU] iAnkeet:
I installed the v2.82 on my moto g4 plus with invictaOS [rom] . My phone is properly rooted but there no superSU icon in app drawer ...

Any solution??
[SuperSU] wetxxx:
Read previous post

"Live long and prosper"
[SuperSU] ktmom:
It's answered in post #10591, just a page back.
[SuperSU] Shtiff1:
Where do you see post #s?
[SuperSU] :
Go To Page No 1060 And Find Post By jcmm11 Regarding No SuperSU App Installed After Flashing SuperSU.Zip
[SuperSU] Shtiff1:
Really I just wanted to know how you saw, or can see page numbers? Lol, using XDA Labs.
[SuperSU] ktmom:
Don't think you can in XDA labs. Just downloaded it to see. Bummer ?
[SuperSU] Shtiff1:
Ya using labs now, don't see it, no worries, just curious. Thanks
[SuperSU] peterlee928:
if you want to see page numbers in xda labs app, click the page number towards the center top of the page. you can then hop to any page in the thread.
[SuperSU] Shtiff1:
Pages I can see, post counts, can't.
[SuperSU] peterlee928:
correct. your last post said you wanted to see page numbers.
[SuperSU] Shtiff1:
Sorry, meant post counts.
[SuperSU] Waiting4MyAndroid:
I want to root my LG G4 H811 again. I unlocked the bootloader and installed latest TWRP. Stock Android 6.0. Is there a specific SuperSu version that I should flash? Will the latest release work? Please advise. Thanks.
[SuperSU] Alxoom33:
Yes, the latest release will work. In fact since you on 6.0 you can use the last stable release. The SR's are more important for rooting the latest Android 7 and 8 releases for the Pixel and Nexis devices.
[SuperSU] m0han:
did as you wrote. no go. phone gets rooted, but no icon. aicp of 16-july for m8.

didn't quite get what you meant by 'For future updates just flash a new zip'.
[SuperSU] ktmom:
Have you gone to settings and looked for supersu there? Some ROMs don't display the icon in the app drawer.
[SuperSU] m0han:
yeah, i did that before posting. thanks.
[SuperSU] ktmom:
I think this can happen if there is a glitch in underlying activities permissions for the app. Have you tried installing the apk from the play store?
[SuperSU] m0han:
no. maybe i will; after i flash an update to the rom.
[SuperSU] osm0sis:
I seem to recall Chainfire posting a command to use when the app disappears from the drawer. Search for that and it'll probably fix your issue.
[SuperSU] m0han:
App icon in Apps drawer

did you have this post in mind? https://xdaforums.com/showpost.php?p=57301245&postcount=1041. but, that procedure gets me to supersu settings. still, no icon.

so, i searched further and came to this post: https://xdaforums.com/showpost.php?p=70215420&postcount=8501. this gave me the idea to uninstall supersu and re-install it. now, i have the icon in app drawer. thanks a lot everyone.

edit: maybe this is what you meant after all: https://xdaforums.com/showpost.php?p=72429526&postcount=9821. :D
[SuperSU] osm0sis:
That's the one! Glad you got it working. :)
[SuperSU] Harrison Le:
AICP is not show SuperSU icon but you can go settings->Personalization to open/check/edit it.
[SuperSU] buffer overflow:
Are you sure about AICP ? ?
[SuperSU] Harrison Le:
Sure, click on SuperSU it will open as you click on SuperSU icon:)
[SuperSU] buffer overflow:
That's what i wanted to show. ?
[SuperSU] ahgahg:
does the beta affect the signal or anything like that

I just installed this beta 2.82 on htc 10 after puttinh twrp on it
[SuperSU] ktmom:
Can't imagine how it would. The ROM might affect reception. The baseband definitely could. Have you upgraded recently?
[SuperSU] ahgahg:
something to do with data encryption and losing, would result is losig signal
[SuperSU] 9062376203:
MI 5 is not starting after root

PLease help me after intallimg supersu2.82 my MI5 is not starting.

mod edit: email adress removed - please use the PM system
[SuperSU] Flippy498:
Moderation note: Please refrain from replying to a post (or even worse: spamming/trolling) if someone posts private information (email adress, IMEI, real world adress, etc.) and use the report button instead. The mod team will take care of the situation, then. Thanks! ;)
[SuperSU] Midomad:
Sometimes i have this,

I can't grant root permissions!

I have to try multiple times in order to gain it again.

Could anyone confirm?View attachment 4220888
[SuperSU] GopalKaul:
Go to SuperSU app and disable Tapjacking protection
[SuperSU] Midomad:
I never thought this could be the reason...

Appreciated.
[SuperSU] GopalKaul:
You're welcome! Wow ! A recognised Dev appreciated me!! Unbelievable!! My dream came true!!!
[SuperSU] Midomad:
Lol [emoji23]
[SuperSU] GopalKaul:
No. Seriously. It doesn't mean much for you, but for me it is much.
[SuperSU] DEVILOPS 007:
I'd love to know what settings you changed in that app lol:D
[SuperSU] Paschfire:
Scroll back one page in this thread and read what the solution was.
[SuperSU] DEVILOPS 007:
I meant for the backgroundpermissionsetter app.
[SuperSU] Midomad:
https://xdaforums.com/android/apps-games/app-runinbackgroundsetter-v1-0-t3637705
[SuperSU] beerbaronstatic:
Just flashed DP4 on my Pixel XL, using root-marlin-pixelxl-v2.82-SR1-PixelFix.zip boot-to-root method and things appear to be working same as DP3 for anyone interested
[SuperSU] iamaniff:
Work on Nexus 5X DP4 without any issue, so far
[SuperSU] rybshik:
deleted
[SuperSU] bahmonkeys:
I am running adaptable storage so SuperSU won't install right. Is there a way to manually SuperSU?
[SuperSU] Chainfire:
Are you sure this is due to adoptable storage? Are you actually installing *on* adoptable storage? What exactly happens?

I've installed SuperSU with adoptable storage without issue before.
[SuperSU] Chainfire:
Anyone having issues with ODP4 on 6P ?
[SuperSU] bahmonkeys:
I have installed on adoptable storage before and has always worked

Calling user ramdisk patch script

Failure aborting

That is far as I get. Thanks for your reply chainfire. You have been doing awesome work for years. Any ideas why it is failing?
[SuperSU] Chainfire:
Try removing /data/custom_ramdisk_patch.sh before flashing SuperSU. Magisk remnant?
[SuperSU] bahmonkeys:
Yes chainfire you are exactly right. Ya flashed no issues straight afterwards. How did you know? I suppose you are the master of root