yashsingh1/xdaforums huggingface dataset:
[SuperSU] a-dead-trousers:
How to remove OTA survival?

hi!

In the beginning I installed SuperSU the normal "system" way. As far as I know this will also install OTA survival (folder /supersu). After some time and problems (with Pokemon GO) I found out about "systemless" and it worked pretty well indeed. Now after I flashed to LineageOS I don't really need SuperSU anymore because nearly all features I was missing are now included (restart options for recovery and so on). Furthermore SafetyNet now seems to detect the modified boot-image and won't let me get a green response. So I unrooted SuperSu with the built-in options but still SafetyNet seems to find something which triggers its bad response. So I searched on and found the /supersu folder which I can't get rid of because after every reboot it gets created again. As far as I was able to stick together the information I found on the internet this folder is part of the OTA survival of SuperSU.

And here comes the tricky part: I'm not able to disable/remove this.

If I use SuperSU in systemless mode the OTA survival option is nowhere to be found and even the unroot does not seem to remove OTA survival. And SuperSU in system mode won't boot anymore on my device (bootloop).

So, does anyone know which files (in init.d?) I have to remove using the console to disable/remove OTA Survival once and for all?

regards ADT
[SuperSU] tag68:
If you are talking about /supersu in twrp, it is only existent while twrp is running to make it possible that twrp can root some phone using supersu. This will not be the problem.
[SuperSU] a-dead-trousers:
ok, thanks.

So I have to search on :crying:
[SuperSU] xell75:
SuperSU 2.79 SR3 is working just fine on my GT-I9505 with Optimized LineageOS 14.1 ?
[SuperSU] egingell:
Are you trying to delete survival mode files? Those files are in /system/bin/.su (or whatever it is exactly), but they should have been deleted when you flashed the custom ROM.

At any rate, I didn't think any custom ROM would/could pass the safety net check.

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] draiyan:
is supersu not compatible with lineage OS? I installed thru playstore and reboot for binary update but i got bootlooped...
[SuperSU] ulxerker:
Doesn't LineageOS need it's own SU (dl for arm64 version)?
[SuperSU] maximusmullivan:
Use the lineage files to get root http://www.androidpolice.com/2017/01/26/official-root-zip-package-lineageos-available-flashing/
[SuperSU] a-dead-trousers:
No. LineageOS is the succession of CyanogenMod hence the name. Instead of a built-in su they decided to have it as an addon which has some problems installing it. But you can also use SuperSU instead which in my opinion is way better.

Don't get me wrong: SuperSU works perfectly on my Phone with LinageOS BUT I'm not able to hide it from SafetyNet anymore. On CM I used RootSwitch which did the job. Now on Lineage (Android 7.1) I've read that SafetyNet is also checking for modified boot-images. So I asumed that is the problem and I tried to get rid of everythin SU-related. Because I found /supersu folder in TWRP filemanager I thought supersu OTA survival was still on the phone. My bad.

Currently I'm suspecting the ROM itself. According to the LineageOS Wiki they no longer hide the fact that the bootloader is unlocked and that would explain the red safetynet response.

regards ADT
[SuperSU] osm0sis:
Lineage doesn't root by default anymore (like CM did) so Play Store SuperSU can't just swap itself in like it used to; you need to flash the SuperSU installer zip from recovery. :good:

As for SafetyNet it depends on the device. Only some devices check for unlocked bootloaders, those have custom kernels with the necessary patch to evade it included. Untouched /system partition is only on devices that launched with dm-verity. Boot image verification also depends, for example it definitely detects something in the CM/Lineage code-base that doesn't get flagged on more directly AOSP-based, so, basically, a custom kernel is a must.

On my Nexus 5, using the Root Switch custom_ramdisk_patch.sh and .supersu config with SuperSU v2.79 and then franco.Kernel AK2 flashed over top works perfectly. My Automate flow for disabling root when a certain game opens is even still working well. ;)

Anyway, let's not devolve the conversation in here to be all about SafetyNet again. There are other threads in this subforum more appropriate. :)
[SuperSU] draiyan:
Thank you all for the information ?
[SuperSU] Sachin ET:
Can i flash this on Ressuruction Remix........... ?
[SuperSU] kskillz2000:
Yes
[SuperSU] Sachin ET:
what does it mean by binary update............ ?
[SuperSU] Ch3vr0n:
it means the binaries that actually grant the su rights need updating, exactly what it sais
[SuperSU] kskillz2000:
It's telling you su needs to update the binaries to function properly. There should be a zip at the beginning of op that shouldn't require you doing that. Or you could see if it takes the update. Sometimes it works perfectly while other times not so much, this the need to flash the zip.
[SuperSU] Ibuprophen:
SuperSU requires Superuser scripts to be installed in order for the app to do what it's designed to do. Kinda like the BusyBox app requiring BusyBox Binaries to be installed in order for the BusyBox app to do what it's meant to do.

Now the Stable version of SuperSU has 2 ways in which it can be installed.

1) SuperSU as an app, via the Play Store, that installs the app conventionally but, requires that the Binaries be installed (as indicated by a popup when you first open the app after installing it from the Play Store). This binary installation is performed by the app itself and requires a reboot to complete it. And, once rebooted, the Binary installation is confirmed by reopening the app and no there's no popup indicating the binaries needing to be installed (as it does when the app is first opened as it did before the reboot).

2) SuperSU as a flashable zip (via recovery), after using Chainfire's link to download the zip file manually. When SuperSU is flashed, via the recovery, the flash file installs the app and binaries together. Once it's done flashing, and the device is rebooted, then the Binary installation is also confirmed by opening the app and no there's no popup indicating the binaries needing to be installed (as it does when the app is first opened).

With that stated regarding the Stable version of SuperSU... When it comes to the Service Releases (as labeled by the letters "SR".), there's only 1 caveat to this. That is that the SuperSU SR releases are only available as a flashable zip. This means that #2, above, is the only way to install it. And, as stated above, Flashing the SR version installs both the app and binaries together and also confirmed after reboot and opening the app with no popup indicating the binaries needing to be installed (as it does when the app is first opened).

Please note... Unless you really need to (by way of SuperSU specific issues and SR releases to address those issues), i recommend installing the Stable version. The SR versions are not considered stable versions and are builds with certain fixes that, when stable enough, Chainfire releases them as Stable versions.

The new Stable versions are announced both via an XDA specific thread and in the Play Store as an update.

I hope i had explained this okay. I've explained this when asked from a PM and other threads to those who are not as technically inclined as others.

Peace and Love!

Peace and Love!
[SuperSU] skyhirules:
[MENTION=6298645]erfanoabdi[/MENTION]

Jesus Christ man! Is it that difficult to attach that log as a txt file instead of making this huge post?
[SuperSU] danieldmm:
Let me guess, you running on F2FS partitions and device is OnePlus 3 or 3T ?
[SuperSU] Ararquen:
Hi, I'm have Xiaomy mi4c with TeamSuperluminal CM13.1 20161231 build now. I had older CM build installed which worked fine with systemless SuperSu v2.78 SR1, but updated CM recently. Tried to reinstall systemless SuperSu, but got bootloop. Trying to install SuperSu v2.79 SR3 in systemless mode now, but getting bootloops as well. Any suggestions?
[SuperSU] nathanchance:
Is it that difficult to kindly guide instead of snapping? It looks fine on desktop for me because he used code tags.

[MENTION=6298645]erfanoabdi[/MENTION] it is generally good practice when giving logs to use a site like Hastebin or Pastebin :)
[SuperSU] handers1234:
I put the zip in ext sd card and then flash it with twrp but the supersu installed as system-less root how to make it system root and not system-less root?
[SuperSU] ¿GotJazz?:
Using SSU v2.79 SR3 on a new Amazon HD8 (6th Gen).

SuperSU works, but must be put into [GRANT] mode to function. For some reason, the newer HD8 does not prompt properly - nothing shows up, and it seems like the su attempt locks up the app.

The older 5th Gen HD8 would prompt without any problems. Not sure if this is SuperSU related, or HD8-6G releated.

I have attached a logcat where I attempted an 'su' inside a Terminal Emulator while SuperSU was configured to be in [Prompt] mode.
[SuperSU] jdegreef:
You can use this version.
[SuperSU] Sachin ET:
can i install SuperSU on LinageOS............. ?

once when i tried in an unOfficial build it led me to bootloop
[SuperSU] bdwilk:
Shouldn't be a problem if you flash the zip. I use it on RR, AICP, and AOKP and they're LOS based and never had an issue.
[SuperSU] Sachin ET:
which zip plz get me the link
[SuperSU] bdwilk:
You're really close......

https://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/post55256620
[SuperSU] Sachin ET:
thankyou
[SuperSU] erfanoabdi:
No it's Moto z with data on f2fs

Is there any solution for OnePlus 3?

I don't think it's related to f2fs cause only Google app break's superSU

Sorry for long post
[SuperSU] tag68:
For Moto Z play (/data has f2fs also) systemless root does work neither with SuperSU nor with Magisk, but phh superuser works fine. SuperSU currently works in system mode only.

Maybe this helps a bit. Sorry for of topic, please analyze and discuss further in Moto forum.
[SuperSU] dhirajahuja432:
It's not working on Asus Zenfone 5 using resurrection remix rom nougat plz help
[SuperSU] erfanoabdi:
Why you guys thinks my reported bug related to f2fs ?

I built TWRP with modified f2fs kernel for Moto z

And systemless su flashed successfully and I have root access, full root access !!

But when I'm searching something in Google app

SuperSU or libsuperuser craches with that log in my previous (long) post

I can use root access flawlessly without touching Google app

I don't what to use magisk to get root access or any other ways I just tried to report bug that maybe gonna fix in next new superSU version
[SuperSU] andreoide:
Is it so difficult to use normal language ?
[SuperSU] tag68:
Because it makes sense. Currently

Which kernel are you using when accessing su? Does it integrate the fix for f2fs, or did you only use a changed twrp?

I'm not sure how that error behaves when accessing.
[SuperSU] erfanoabdi:
Thanks for helping

My TWRP kernel based on stock Motorola kernel source with patched f2fs driver by arter97

And my system kernel is still stock one

Guess I should install my modded kernel in boot partition too?

So Let me try it
[SuperSU] Cuculuz:
Go with kingroot, SU is broken
[SuperSU] RandomPooka:
Worst advice ever ^^
[SuperSU] buffer overflow:
Are you serious ? ?
[SuperSU] handers1234:
Ummm can i just flash that version or should i reflash my rom first?
[SuperSU] erfanoabdi:
[MENTION=6192363]tag68[/MENTION] thanks dude

Looks fine, That's fixed by flashing modded kernel
[SuperSU] jdegreef:
You can completely unroot from Supersu app and then flash that version.

If that doesn't work I'm afraid you'll have to reflash your rom.
[SuperSU] ZeeJcG:
Will this not bootloop my device after flashing the zip and updating the binaries through the app because on the 2.79 , it is booting after flashing, but however when i open thr app it require me to update the binary script and then reboot, but after succesfully updating the binary and rebooted, the phone got into bootloop.
[SuperSU] krasCGQ:
Ouch. One of the worst suggestions ever I read.

Why not with it's built-in SU?
[SuperSU] jdegreef:
If after flashing the latest zip the app ask to update it means something has failed during flashing IMO.
[SuperSU] handers1234:
I tried many times but the system-mode always give me bootloop gotta stick to system-less mode.Thanks anyway+1
[SuperSU] ZeeJcG:
This always happened to me even from CM 13.1 and I always boot successfully after the app ask to update the binaries. My phone is Zenfone 6
[SuperSU] ruchern:
Why are you even here?
[SuperSU] Cuculuz:
Wanted help, got none, SU still broken, gave logs tried all the betas here and "stable" version 2.79 from Gplay. Non work

Only version that is working is 2.78, had no problems updating it until the last update hit the market.

---------- Post added at 02:02 AM ---------- Previous post was at 01:55 AM ----------

Apology for being salty, but if 2 of my devices are running different ROMs on 2 diffrent phones what else can I say? :/ its not working anymore
[SuperSU] ruchern:
What's the error message?
[SuperSU] andy hall:
Which devices which ROMs? Are you running f2fs anywhere?
[SuperSU] VincentJoshuaET:
What I want to do is to flash LOS 14.1, ElementalX, SuperSU, Open GApps, some mods (boot animation, emoji, aptX, WiFi mod, camera, etc.).

AFAIK, only flashing LOS and GApps will still make your device pass SafetyNet and CTS (if not, using a custom kernel or Magisk is a solution). If I flash those mods to the system and remove some files, I can still pass SN/CTS, right? Do I still need to flash Magisk if I'm already flashing SuperSU in systemless mode for passing it?
[SuperSU] xomikronx:
Hey Guys,

I'm running Pixel XL on NMF26U (Jan Patch) and was using SuperSU 2.79 SR3. Out of no where, I am no longer able to get root. I tried uninstalling the SuperSU app and reapplying root zip via TWRP. No luck. Anyone else having issues? I'm not sure how to get root again.

Forgot to mention, after uninstalling the APK manually, even reflashing the SuperSU zip in recovery, I do not see the SU binary after reboot

[UPDATE] Incase anyone else runs into this, I had to use a root-to-boot version which installed the SU binary, then upgraded the binary via Google Play.

I think the original issue is that you need the stock boot.img before flashing SuperSU zip.
[SuperSU] TonikJDK:
Might be similar to what I have seen using Franco's kernel. I have to root before I ever boot that kernel. So maybe flash all taking out the -w then before you boot it fastboot boot TWRP and install SU.

I think the kernel is getting copied or modified or something on first boot.
[SuperSU] AnkitGourav:
Any update is going to come or not...
[SuperSU] ZRK_NanDRD:
Such rudeness:p it will come out when it does
[SuperSU] smitharro:
Ooops... A question that should not be asked! Please no ETA questions on XDA!

Send from my XT1642, with LineageOS OMS, using Tapatalk
[SuperSU] fmc000:
Nice first post!
[SuperSU] Midomad:
Not...
[SuperSU] vandyman:
This is the Super user beta thread.

Sent from my Nexus 5X
[SuperSU] RandomPooka:
Update scheduled for February 30th.
[SuperSU] NotATreoFan:
That soon? I don't know if I've got room on my calendar to pencil that in!

Perhaps I'll send Chainfire a message asking him to release on April 31st.
[SuperSU] veez21:
crap, that's my birthday!!
[SuperSU] Hgneto:
Apologies for the noob question but with Systemless SuperSU is it possible to have root on my S7 Edge Exynos version without tripping/triggering KNOX?

(The tread for the systemless SuperSU is closed, so not sure if he will keep developing/improving that or if he had given up..)
[SuperSU] h_maharaj:
I don't think so since SuperSU zip needs to be flashed via a custom recovery, the installation of which trips knox.

Eta. I recall reading that rooting the S7|S7 Edge without tripping knox is possible by flashing an engineering kernel. Unfortunately, I don't know anything else about the process beyond that.
[SuperSU] ashyx:
The thread is closed because it's for information purposes only. To keep the thread clean it's not open for general posting. There is a specific thread for that.
[SuperSU] ruchern:
It's a sarcastic reply to the person who asked for updates.
[SuperSU] Ja_som:
Noooo, really?
[SuperSU] ruchern:
You're assuming that there are people actually did not realise that.
[SuperSU] drewski_1:
you need to upgrade your sarcasm-dar ?
[SuperSU] DarkLanternX:
Did anyone managed to run suhide successfully on RR 5.8.0 or any android 7.1 based custom ROM?
[SuperSU] Ja_som:
This is SuperSU thread, not suhide...
[SuperSU] wetxxx:
Hi Guys I successful install latest beta on htc 10 s-on. When I try edit system files su inform me that I don't have permission to save files and error with mounting ? I know this problem with htc m8 but in new supersu this was past. May I ask for Your help. Thx

Send by HTC 10
[SuperSU] Surge1223:
Out of curiosity are you using an official twrp? (I know that it's not related directly to your issue, but I've seen some people getting cute with twrp source and messing up the linker patch and other thinks messing with default lib paths)
[SuperSU] erfanoabdi:
No I built TWRP from official source only with modded kernel(f2fs) myself

Thanks for reply but it's fixed now ;)
[SuperSU] Surge1223:
......so unofficial? Hah. Anyways glad you got it sorted.
[SuperSU] grep_i:
Is it possible to enable su rights manually on an application that for some reason does not ask for it itself ?

Or would that be pointless because that app won't even do root enabled stuff even if it's granted to it manually ?

In the app in question the root option is check marked already but there's no prompt for su usage, can anyone help or throw a suggestion ?
[SuperSU] egingell:
You can manually add it to /data/data/eu.chainfire.supersu/shared_prefs/eu.chainfire.supersu_preferences.xml (edit at your own risk).

The app is probably not asking for root. If the app doesn't do any root operations, it's pointless to grant it root access.

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] grep_i:
Okay so I was doing it right all along.

Tried that once but did not succeed I guess I messed up the UID of the app or made a typo, I will try it again and be more careful.

Thanks for the reply.

PS the apps root functionality did work before I have no clue as why it stopped working but the only thing I can see is that it is not listed in SuperSU anymore.

Probably this won't fix the problem but I have to try I must have tried everything.

---------- Post added at 10:00 AM ---------- Previous post was at 09:32 AM ----------

Okay the app is now back in the granted list of SuperSU but as scared for is happened, the app is not making the request anymore for some reason beyond my scope.

Thanks for the help anyway, I have to dig deeper to resolve this issue there goes my weekend.
[SuperSU] jdegreef:
[MENTION=6952047]grep_i[/MENTION]

Did the app version change recently ? It might be a bug of the app...
[SuperSU] DarkLanternX:
There wasn't an active suhide thread, I couldn't find one Sorry

---------- Post added at 03:45 PM ---------- Previous post was at 03:40 PM ----------

There wasn't an active suhide thread or I couldn't find one sorry
[SuperSU] adrman:
https://xdaforums.com/apps/supersu/suhide-t3450396/page571
[SuperSU] egingell:
It's one of the sticky threads on this forum.

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] grep_i:
Yes it changed yesterday but I have this problem for a month already the app in question is aptoide.
[SuperSU] wetxxx:
It`s possible to change bootup screen without red Warnings about legal etc? After install Supersu 2.79 SR3 this screen was appears.

thx
[SuperSU] Chainfire:
PSA: SuperSU stuck on "creating image"

Apparently the Note5 seems to get stuck on "Creating image" during SuperSU install. This appears to be an issue with the kernel used by TWRP, which is very slow to feed the random number generator. If you leave the device for a few days the install will succeed :)

Of course in a future version of SuperSU this will be fixed, but should you run into the issue in the mean time, run the following command in adb shell in TWRP before flashing SuperSU:

mount -o bind /dev/urandom /dev/random
[SuperSU] Explorare:
SuperSU 2.79-SR3 works like a charm on Moto X Force (XT1581). But 2.97 failed to root XT1581 and stuck on Moto logo. See Failed to root XT1581 and stuck on Moto logo… | Motorola Droid Turbo 2.
[SuperSU] ulxerker:
There's no version 2.97 :p

Anyway, as 2.79-SR3 is working fine you're good and there's no need to complain. 2.79-SR3 is newer than 2.79 and contains a lot of bug fixes.
[SuperSU] Explorare:
Sry, I mean 2.79.
[SuperSU] ulxerker:
Obviously, but pay attention to the rest of my earlier post.
[SuperSU] Vlad Paul:
Hi, [MENTION=631273]Chainfire[/MENTION]

mi4c users have problem when flashing SuperSU from TWRP, losing IMEIs after flash. A lot of complains on xiaomi.eu forum. Check here, please https://xiaomi.eu/community/threads/7-2-9.38201/page-26#post-351891

Please fix this issue. Thank you, Sir!
[SuperSU] Ibuprophen:
So, for example, you're stating that when individuals flash a ROM, like LOS14.1 and the SuperSU, they are having modem issues like being able to connect to the cell tower and the WiFi but, no data/Internet is working?

Also, how did they come to the conclusion that the culprit is the SuperSU?

And did they try a the stable or even an older release of SuperSU?

I'm really not trying to give you a hard time but, making that type of statement, though understood, really needs something to support how the conclusion of the SuperSU was made.

Peace and Love!

Peace and Love!

~Ringo Starr~

Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
[SuperSU] Vlad Paul:
Sorry. This happening on new released Nougat MIUI rom, after flashing latest SuperSU from new twrp 3030. Losing IMEI's, no signal, no IMEI's.
[SuperSU] Vlad Paul:
View attachment 4038964
[SuperSU] Ibuprophen:
Looks like they may need to reinstall their ROM again...

If they want, have them try the Stable SuperSU v2.78 from here:

https://download.chainfire.eu/1001/S…perSU-v2.78-20

We'll keep our fingers crossed!

Peace and Love!

Peace and Love!

~Ringo Starr~

Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
[SuperSU] nathanchance:
Actually sounds like it could be something up with sepolicy and maybe RIL. I recall a few other devices having similar issues after upgrading to Nougat.

To anyone with these issues, logs (logcat and dmesg) tend to be helpful ;)
[SuperSU] str8str:
I thought the latest stable was 2.79?
[SuperSU] str8str:
Are you on an s3? I recognize that number
[SuperSU] Ibuprophen:
It is but, I've seen others who had a similar experience was successful with the 2.78 build.

I can't guarantee that it will work but, based on the similar issues, it may...

Peace and Love!

Peace and Love!

~Ringo Starr~

Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...

---------- Post added at 04:49 PM ---------- Previous post was at 04:43 PM ----------

Yes, my primary device is a d2vzw Verizon Galaxy S3 that's Unlocked and rooted beautifully.

I do have 2 other devices. My S4 & the great Motorola Electrify LMAO!

Peace and Love!

Peace and Love!

~Ringo Starr~

Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
[SuperSU] hackxda:
HUAWEI Honor7 Android 6.0 (EMUI 4.0.2 B386) cannot use this version "SuperSU v2.79 SR3 ". TWRP shows "Failure, aborting" at "Extracting ramdisk" during "Boot image patcher".

And, two errors shows during booting, which are "Func NO: 10 (boot image)" and "Error NO: 2 (load failed!)"

So, Honor7 cannot enter system.
[SuperSU] jdegreef:
This is a bit off-topic, but to not cross post, is there a place where we can find old versions of Chainfire apps ? I'm not lucky, the latest versions of Flashfire, Sickmount, are not working for me on different phones where old versions where ok.

I bought them but I don't have backup of all of them.

And I don't trust Apk4fun and the likes.
[SuperSU] ted24j:
http://www.apkmirror.com/apk/chainfire/ personally I trust apkmirror..