yashsingh1/xdaforums huggingface dataset:
[SuperSU] mash4077fan:
If I root my phone using chainfire but I keep stock recovery does that mean I could unroot phone using supersu full unroot and then would I be able to take a ota update?
[SuperSU] Sr. Zé Alguém:
How would you flash SuperSU without a custom recovery? This is interesting... Thanks

(Unless you are already rooted and use FlashFire...)
[SuperSU] GopalKaul:
You can , even with root!! But don't remove any system apps, only disable. Use FlashFire, by CHAIN FIRE!!!

https://play.google.com/store/apps/details?id=eu.chainfire.flash

It even automatically roots your device after ota!

I hope I helped...

GK.
[SuperSU] mash4077fan:
I think when you flash the cf autoroot file it automatically puts supersu on there so you dont have to flash it. Please correct me if I am wrong but I think it does and if it does not then I would imagine you could just use flashify.
[SuperSU] Chainfire:
My app is FlashFire, Flashify is a completely different app.
[SuperSU] GopalKaul:
Sorry sir. Corrected my mistake... But great app! Love your all apps including CF.lumen, FlashFire and SuperSU and StickMount
[SuperSU] mm1rza:
how to unroot?
[SuperSU] Sr. Zé Alguém:
My friend Google anticipated you would ask this question and already got answers for you:

https://www.google.com/search?q=how+to+unroot?
[SuperSU] mm1rza:
Of course my friend . Mostly i read get bootloop. maybe someone here can help me without get bootloop. iam install using twrp
[SuperSU] Sr. Zé Alguém:
Describe with details what you are trying to do, what you have done and the errors you are getting. And tell your device and ROM. Maybe, then, someone will help you.
[SuperSU] sagnikroy360:
Please add root hide feature
[SuperSU] DEVILOPS 007:
There's already something called suhide I think but by hiding root is your problem to do with safety net because if so then you need something like magisk for passing it and hiding root completely. I'm not bothered about it so I use SuperSU.
[SuperSU] osm0sis:
suhide crashes on any ROM with after the November 2016 security patches, but if one's okay with toggling SuperSU root instead of hiding it there's the Root Switch method I posted a while back. Thread search should bring it up pretty readily.

My Automate flows have it working for Pokemon GO and Android Pay pretty seamlessly.
[SuperSU] DEVILOPS 007:
Okay awesome. I completely forgot about root switch lol. I didn't know about suhide as I haven't tried it since marshmallow. Thanks for clearing up.

---------- Post added at 01:30 PM ---------- Previous post was at 01:27 PM ----------

Could you explain to me how root switch works please? I didn't see it when searching the thread but have it downloaded. How does it pass safety net without being magisk?
[SuperSU] nguyentankiet:
Here
[SuperSU] DEVILOPS 007:
I meant I have the zip but I'm not sure how it works or if there's an app or what. I didn't make it clear:silly:
[SuperSU] nguyentankiet:
Open zip and install apk. More info view readme.txt on mega folder
[SuperSU] DEVILOPS 007:
Yeah but I'm looking at the safety net version. I'm thinking that I need to add that to the ramdisk the file inside.
[SuperSU] osm0sis:
You put .supersu and custom_ramdisk_patch.sh in /data then reflash SuperSU, then Root Switch can completely, reversibly hide SuperSU from SafetyNet checks when toggled off.

Edit: Looks like there's a newer version (1.3.3.16) buried in the Root Switch thread: https://www.asus.com/zentalk/tw/for...5MjEyfGM2OGVmYTlhfDE1MDEyNDcyNTZ8MHwxNzM1NDI= :good:
[SuperSU] DEVILOPS 007:
But how do I toggle it? I don't get if there's an app or what as I see nothing? Thanks.
[SuperSU] osm0sis:
There are two downloads, one is a zip containing the APK you need to install, the second contains the other 2 files I just gave the instructions for. You toggle it in the app, and you can use Automate and my Flow to set specific foreground apps to trigger an automatic toggling.
[SuperSU] DEVILOPS 007:
SuperSU says SU binary occupued...
[SuperSU] osm0sis:
Huh? Never had that problem here. Sounds like you may not have followed the install instructions correctly? Did you use the .supersu and custom_boot_image.sh? The zip had dot.supersu or something in it so you had to rename it per the included readme.
[SuperSU] xmanweb:
SR1-2.82 cause ext sdcard can't mount as sdcardfs on lineageos 14.1 hlte offical

my device is hlte, known as samsung galxy note 3.

i was using lineageos 14.1 offical 20170725. android 7.1.1.

when i flash SuperSU-v2.82-201705271822.zip everything works fine.

but when i flash SR1-SuperSU-v2.82-SR1-20170608224931.zip ,my hlte can't mount ext sdcard as sdcardfs, so it's can not see my sdcard in ES file explorer or root explorer.and every boot will show a notification says: 'new sdcard: for media and photos '

pls check it out .thank you.
[SuperSU] DEVILOPS 007:
It turned out it wouldn't let me change the name at first so it was really confusing me but I eventually got it to work and I pass safety net fine now. I actually created a little script to simplify the process as it installs the apk and places the two files. Thanks a lot!
[SuperSU] GopalKaul:
How do I pass safetynet? How to use this? I hate magisk and use SuperSU. How to use this??
[SuperSU] DEVILOPS 007:
Just flash the zip and open the root switch app. It will let you disable root to pass the safetynet but you can't have root and safety net passing unlike magisk.
[SuperSU] Alxoom33:
I have a Nexus 6 on Android 7.1.1 July patch with SU 2.82 SR1-no Magisk. I flashed your zip and disabled SU with root switch, Safetynet failed, reebooted and tried again with the same result. Tried Android Pay; failed-got the unlocked bootloader/rooted message. Is there anything else that you may recommend?

Also, what files do you remove if you want to uninstall root switch and any of the files installed with the zip?

Thank you.
[SuperSU] Wolfcity:
That's what superSU (without switch) says in my case everytime after a complete clean flash. The zip installs without error through twrp and after 20 minutes or so "binary occupied". The strange thing is I never used anything else than SuperSU, and [MENTION=631273]Chainfire[/MENTION] said it's a message that appears when some other root solution is present.

I tried several versions 2.79, 2.79 SR3, 2.82.

I'm on magisk now but I don't need that safety net passing stuff at all. The modules are nice but I was a SuperSU guy since I root phones and really would like to return to it.

Any ideas? I'm running aex 7.1.2 on a Moto g titan. As the flashing process runs without errors I don't think that a recovery log will show much.
[SuperSU] DEVILOPS 007:
Well what mods do you have installed? Some tweaks will trigger the safety net no matter what. To remove root switch go to /data and delete .SuperSU and custom ramdisk patch sh and uninstall the app and reflash SuperSU.
[SuperSU] Alxoom33:
Thanks,

Only have EX kernel v. 4.23 and some substratum dark and transparent apk's. Strictly cosmetic. I can't think of anything that would cause Android Pay to fail besides root and unlocked bootloader.
[SuperSU] DEVILOPS 007:
I don't know. You pressed the toggle to actually disable root didn't you and granted it root permission?
[SuperSU] Alxoom33:
Sure, but I did notice that I was back to the stock kernel. Is there an issue with the custom ramdisk?

Among SU, EX Kernel and Rootswitch zip files, what order should I flash?
[SuperSU] DEVILOPS 007:
I think the ramdisk has something to do with the kernel so it is very possible that being on stock kernel might possibly be affecting it's functionality. Can you try a custom kernel just to test?
[SuperSU] GopalKaul:
App hides SuperSU but fails safety net
[SuperSU] Ch3vr0n:
Suhide hasn't worked with safety net since November last year. Old news

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] Alxoom33:
what phone and Android version are you using rootswitch on?

---------- Post added at 03:26 PM ---------- Previous post was at 03:25 PM ----------

Sure, but I thought this was something else?
[SuperSU] DEVILOPS 007:
Nexus 6p 7.1.2 pa 7.2.1 Franco kernel r54
[SuperSU] Alxoom33:
I uninstalled Root Switch, went into recovery and in /data I deleted the .SuperSU and custom ramdisk patch.sh and all files related to SuperSU. Reflashed SU 2.82 SR1 and custom kernel and now phone is still not rooted. Tried flashing SU 2.82 SR 1 again and still no luck. Please let me know what other files does your zip install and where are they? Something is blocking Superuser installation.

Thank you.
[SuperSU] DEVILOPS 007:
You shouldn't have deleted anything I didn't say to delete. Try just dirty flashing your so flash rom, gapps, kernel, SuperSU etc.
[SuperSU] ktmom:
If all you had was Ex, on top of PN you won't pass safetynet without Magisk's help. The stock kernel in PN has a patch so that unrooted, it passes safetynet. Ex does not.
[SuperSU] Alxoom33:
I don't have PN. I have stock Android 7.1.1 with EX. By the way, reflashed the rom, SU and EX and I'm good to go. Don't think your zip file works on current Android versions, however. What are you running?
[SuperSU] NLBeev:
Nexus 6, stock 7.1.1 lite, Franco's kernel r67 su282sr1, unlocked bootloader, some blacked out apps.

I've no Android pay, but I tried to pass SafetyNet, because the app Netflix is hidden in the Play Store.

Installed rootswitch 1.3.3.16.

Copied two files to /data:

.supersu and custom_ramdisk_patch.sh

Reflashed SU 282sr1 in recovery.

Reboot and disabled root with rootswitch.

Rootchecker tells me that SafetyNet is passed completely.

Settings - about doesn't show Franco's kernel anymore. The Google name is shown.

Reflashed FKernel r69 and in settings Franco's name is back; rootswitch keeps working. When root is disabled SafetyNet is passed, until a reboot.

Although SafetyNet is passed the Play Store does not show the Netflix app to me.
[SuperSU] GopalKaul:
Check your dpi(ppi) with stock
[SuperSU] NLBeev:
Done; fontsize and display size set to default.

Root disable and Playstore disabled. Playstore reinstalled with root still disabled.

No Netflix in the Playstore.

Installing Netflix with a Windows PC also not working.

Error: no suitable device.....

Seems to me it's a server side check of Google.

My N6 is on a blacklist...
[SuperSU] jcsww:
Netflix uses the Google Console to hide the Netflix app from devices that fail the SafetyNet check.
[SuperSU] shoey63:
But what about Safetynet detecting unlocked bootloader? RootSwitch doesn't hide it, so it fails :(

Edit: Found a solution using your kitchen?

Users who are interested can PM me.

Edit: Method is Here
[SuperSU] xell75:
Sounds like an good solution for pre-unlocked phones like the Galaxy S4 (GT-I9505)

---------- Post added at 02:30 PM ---------- Previous post was at 02:25 PM ----------

Doesn't normal install works? I mean downloaded from a site like apkmirror? I use the newest 5.3.0 and it works without a problem.
[SuperSU] ulxerker:
thanks for offering, PM sent!
[SuperSU] Alxoom33:
I have an unlocked bootloader and rooted Nexus 6 SU2.82 SR1 on the latest version of Android 7.1.1 stock with the EX kernel. I have no rootswitch or any other cloaking software like Magisk or SU Hide, and get Netflix without any problem whatsoever.

I don't pass SafetyNet and I can't use Android Pay. When I flashed the zip file posted above and turned on root switch I didn't pass Safety Net and could not use Android Pay.

Just FYI[emoji2]
[SuperSU] osm0sis:
I'm curious too, can you post it in my AIK thread for people?
[SuperSU] Ibuprophen:
I looked into the Netflix issue a bit and found some, very informative, information regarding it and I just wanted to share it with you.

Netflix was quoted in the following statement:

"With our latest 5.0 release, we now fully rely on the Widevine DRM provided by Google; therefore, many devices that are not Google-certified or have been altered will no longer work with our latest app and those users will no longer see the Netflix app in the Play Store."

Here's just a handful of the additional information out there regarding the Recent Google Play Store Changes and Netflix:

Keep in mind that the information is much more than what the title states...

Netflix confirms it is blocking rooted/unlocked devices...

Netflix was just the start: Google Play Console lets developers exclude app availability for devices that don't pass SafetyNet

Everything new in the Google Play Console

[US] Netflix no longer compatible? - Reddit Discussion

In closing... Since this Google/Netflix issue is much more than the scope of SuperSU, I'll respect [MENTION=631273]Chainfire[/MENTION] for keeping the thread on point without any further, personal, comments regarding this issue.

Thank you for your time :) .

______________

PLEASE NOTE: I welcome any member to help with further valuable information/clarification for any of my posts.

×MY DEVELOPMENTS×

[APP][TOOL][4.2+]The SELinux Toggler

[ZIP][TOOL][AIO]BusyBox Stericson Binary Installer v1.26.2 {BB/TB Auto-Symlink}

×IN DEVELOPMENT×

[APP][TOOL][4.2+][OFFICIAL]The SELinux Switch

Will Supersede "The SELinux Toggler"

×IDEAS FOR DEVELOPMENT×

[APP][UNOFFICIAL][4.2+]XDA Forum {Classic}

[APP][UNOFFICIAL][4.2+]XDA Reader {Classic}
[SuperSU] NLBeev:
Yes normal install works.

Still using Netflix4.16.

I've about the same N6-configuration; no Magisk etc, only su282sr1 and FKernel.

I did not flash rootswitch. I've used the method of Osm0sis.

According to rootchecker SafetyNet is passed,
[SuperSU] viietkoz:
i have J500FN lineage 7.1.2 and can i root with superSU ?
[SuperSU] poganytamas:
Blackview BV800 Pro

Hello all,

I have a MediaTek Helio P20 (MT6757) based phone, Blackview BV8000 Pro with Android 7.0.. I installed SR1-SuperSU-v2.82-SR1-20170608224931.zip via TWRP. It says it needs to update the su binary, which is always unsuccessfull. Root checker confirms that I have root. Some root required functions work, some not. Examples what is working: Titanium Backup can delete system apps, Root explorer can delete files from /system. Examples what is not working: Adfree can not alter /system/etc/hosts. Titanium backup can not restore system apps (it hangs), Busybox can not install (neither to /system nor /su). Any ideas?
[SuperSU] bdvince:
I don't think the method for passing Safetynet is working for Samsung devices . I have a Samsung Galaxy S7 Edge G935F and did the following:

-Installed Rootswitch 1.3.3.16.

-Copied these two files to /data:

".supersu" and "custom_ramdisk_patch.sh"

-Reflashed SuperSU v2.82 SR1 in TWRP.

-Reboot and disabled root with Rootswitch.

After doing this Safetynet

does not

pass, even though root is disabled and confirmed by SuperSU. Worse, if "disable all su daemons" is checked root can only be regained with a reboot. Enabling in Rootswitch does not work.
[SuperSU] followmsi:
Just testing SR1-SuperSU-v2.82-SR1-20170608224931.zip on fresh Android O (DP4) installation for Pixel C.

All works fine - except for the /data partition.

The fstab will be changed correctly to "encryptable" but the Android O system still make some kind of changes on first boot.

TWRP is not able to access the /data partition after first boot into system.

Formatted /data via TWRP and tested again .. same behaviour - /data partition will be "pre-encrypted" or changed again on first boot.

Is this a known issue in Android O ?

How to prevent this "changes" to /data partition in Android O ?

Same experiences on other devices running ODP4 ?

EDIT:

Fixed .. it was the missing "SDcardFS" support inside TWRP kernel.
[SuperSU] jcmm11:
If you're running stock, with an unlocked bootloader and a stock kernel, you will fail Safetynet. You need a kernel with the bootloader patch to prevent the unlocked bootloader from being detected. Beyond that I'm not using Samsung so can't comment further.
[SuperSU] Not_aTotalN00b:
how did you get twrp on bv8000?
[SuperSU] Sr. Zé Alguém:
https://www.google.com/search?q=how+did+you+get+twrp+on+bv8000?
[SuperSU] NLBeev:
I've used rootswitch to disable superSu.

Netflix did not appear in the Playstore immediately. But after 24 hours with disabled root: the Netflix app is back in the playstore.

I've used a VPN !.

N6, Franco's kernel and superSu disabled with rootswitch. After 24 hours Netflix is back in the playstore.

I've used a VPN !
[SuperSU] Alxoom33:
I'll give it a try.

Thanks,
[SuperSU] SilverDragon24:
Not working with x86

I tried to flash on my Asus Zenfone 5 T00F Running LineageOS 14.1 with TWRP 3.0.2.

The T00F is an x86 device not x86_64

Here's what happens when I try to flash

This is in Systemless Mode. When I disable systemless mode it bootloops, which I should expect to happen from previous experiences with disabling systemless mode on other devices with 6.0+.
[SuperSU] Alxoom33:
N6 Android 7.1.1 July patch, rootswitch zip from prior page (or 2) SuperSU 2.82 SR 1 and Franco's kernel. Failed Safety Net and Android Pay. Not sure what you are doing differently?
[SuperSU] ktmom:
If SuperSu can't find your boot image, it can't patch it. I guess you could manually patch it.

More to the point, Lineage has built in root support.
[SuperSU] jcmm11:
Have you ever mounted system as rw? If so that's your problem.
[SuperSU] SilverDragon24:
Is there a guide on how to do that? i know its about the fstab file but my phone uses an unusual boot.img format.

P.S I wouldn't try this if the built in root supported liveboot.
[SuperSU] Alxoom33:
Sure, deleted Korean, Chinese, Indian and other keyboards from System/Apps and enabled Google Assistant. Also, added overlays to System/Vendor.

Must the System be unmodified to pass? [emoji13]
[SuperSU] jcmm11:
Not only unmodified but never even mounted as rw.

Google Assistant is, now, I believe, enabled by default. If not you can use a setprop command in a script in su.d

Keyboards you'll have to leave alone.

Vendor overlays I'm not sure about. What, exactly, does that involve?
[SuperSU] Alxoom33:
Yes, you're correct, Google assistant is enabled by default.

Overlays and Layers, involves providing root permission and activating selected overlays, which inserts an Overlays folder in the Vendor partition, with the selected apk files that theme the various desktop items, system UI, settings etc...

I can try with an unmodified ro system when I update to the August patch later this week.
[SuperSU] NLBeev:
Important is to copy .supersu and custom_boot_image.sh. to /data.

After that su282sr1 must be reflashed.

(the file dot.supersu in the downloaded zip needs to be renamed to .supersu)
[SuperSU] Alxoom33:
I believe that [MENTION=503996]develops007[/MENTION]'s RootSwitch_Flashable.zip in post #10684 automatically installs the files in /data.
[SuperSU] Didgeridoohan:
[MENTION=4487388]jcmm11[/MENTION] [MENTION=4100646]Alxoom33[/MENTION]

Mounting system rw or modifying the system partition has, in itself, got nothing to do with passing SafetyNet.
[SuperSU] osm0sis:
I think that depends on the device. On some it does look at the lifetime write count of the /system partition (which gets reset to 0 with a factory image flash). Chainfire mentioned it at one point and modified his mount scripts to avoid tripping it.
[SuperSU] Didgeridoohan:
Interesting... I had missed that one. Some research is required. :D
[SuperSU] Alxoom33:
Thanks,

When I update to August 7.1.1 patch I'll try root switch w/o modifying or rw of System partition. I'll let you know how it goes.
[SuperSU] elliwigy:
Are there any devs that would like to help us get full root on the G955U?

Before you laugh, I have system/xbin/su in place. We cannot launch su but we have found a way to run any binary commands as root user..

The issue we have currently is /system not usermountable in fstab or not mountable in /proc/mounts

Figured id ask for help here as lots of RCs and RDs are in here and we have su in xbin but cant change its perms due to it being on /system which atm is only RO

is there a way to install SuperSU as a root apk so it can detect the SU binary??
[SuperSU] _that:
However, after installing official updates, sometimes the lifetime write count is no longer 0. That's why TWRP needs to ask the user if it should modify /system - the lifetime write counter is not a reliable indication that the system partition is "unmodified". The only reliable way would be to recalculate the dm-verity checksums and compare them with the actual contents of the partition.
[SuperSU] billa:
Interesting... as a thought, would it be possible to load the xbin contents into a ramdisk and symlink it to system?

With the presumption that the ramdisk could be somehow mounted as r/w.

Well just a stab in the dark...
[SuperSU] elliwigy:
we actually now have a stable full root shell.. however syatem cannot be mounted.. we think samsung might have implemented a "never allow" rule which would suck..

trying to mount system returns an "operation not permitted" now
[SuperSU] NLBeev:
Because you didn't pass safetynet on your Nexus 6.

I've compared the files in the flashable rootswitch.zip and the files on my Nexus 6 after a 'normal' apk install of rootswitch.

Found two different files:

- rootswitch.xml 411b; size on my N6 209b,

- setprops 223Kb; size on my N6 126Kb

The XML file sets some rootswitch options. On my N6 none options are checked/used.

Setprops is different. A compiled file or packed. Can't say anything about the content.
[SuperSU] Chainfire:
You might have uid 0 but do you have init SELinux context ?

How exactly did you gain uid 0 ?
[SuperSU] elliwigy:
yes, we actually started on permissive boot.img and can change our context to anything.. we have tried multiple contexts including u:r:init:s0, u:object_r:init_exec:s0 etc etc.. we also have a modified sepolicy to basically allow all permissions for init context

we used echo command twice to set context like so:

echo u:r:init:s0 > /proc/self/attr/current

echo u:r:init:s0 > /proc/self/attr/exec

prior to that loaded policy:

load_policy /data/local/tmp/newsepolicy

we confirmed it was loaded into /sys/fs/selinux/policy

To gain root well of course we used the SU binary lol it is located in /system/xbin/su

This is on the G955U with ENG system.img as it has the su binary already
[SuperSU] Chainfire:
So... sounds to me like you have root already? What is still lacking?

Can you automatically run a script at boot somehow?
[SuperSU] elliwigy:
well for some reason it does not allow to mount /system and the SU binary only allows to switch user in adb (supersu cant detect it)

---------- Post added at 07:25 PM ---------- Previous post was at 07:21 PM ----------

to be honest we really need an experienced person to take a look for us lol.. i will send you how we get root via shell through pm as it wasnt my find and they dont want me sharing info until we get full root

---------- Post added at 07:50 PM ---------- Previous post was at 07:25 PM ----------

i sent u a pm if u get the chance with detailed information.

we are looking into if theres a neverallow for users to remount, hopefully this isnt the case as we'd be in for a fight to get it to work :( and with our skillset and us learning as we go it will take even longer..

if we do get it however we would be worlds first! and itd open up more development for us

i also have the entire 4 file eng firmware but the boot.img we need to use with ro.secure 0 wont flash..

it throws binary error:

This is ENG binary! Please use USER binary!

it displays this as well when we dd it so we cant boot until flashing permissive boot.img in recovery

---------- Post added at 08:00 PM ---------- Previous post was at 07:50 PM ----------

to add, it very much so could be the ro.secure=1 but since we cant mount we cant change the value lol so you see our dilemma

samsung really stepped up their game.. they secured the full eng boot.img with binary checks, the combo/permissive firmware is limited/restricted compared to even the N7 or S7 devices and yes eng system has su the boot.img is secured preventing us from easily mounting lol like a root shell isnt helpful when you cant mount lmao
[SuperSU] osm0sis:
It won't flash the eng image but will it boot it with like `fastboot boot boot.img`?

What about bind mounting things into system, or a fake overlay approach like Magisk?