yashsingh1/xdaforums huggingface dataset:
[SuperSU] mat738:
I'm on stock Cyanogen OS with unlocked ​bootloader and root. I've rooted the phone with superSU, and now I'm running magisk. I'm not able to pass the safety net check and use magisk hide. Will this tool help me? Will I loose the root if I run the tool?
[SuperSU] Didgeridoohan:
What do you mean by "this tool"? Magisk cannot hide SuperSU. Better if you go to the Magisk forum instead.
[SuperSU] mobileman88:
Magisk and supersu should not be installed at the same time. Best you remove and install either of them. If you need to pass safety net in android n, you can only use Magisk
[SuperSU] mat738:
Sorry, I meant this tool
[SuperSU] jcmm11:
Yes you will lose root. The purpose of that is to completely remove root from the phone.
[SuperSU] Alxoom33:
What tool? SuperSU?
[SuperSU] GRSteelers:
Welp, on a sailfish with stock ROM, 2.79 SR3 installed from fastboot booting TWRP 3.0.2-0 RC1, and the installation completes but then I'm stuck in a bootloop.

The reboots happen almost immediately after the white background with the google icon shows, so I can't get any ADB logs for it.

It's happened twice now, first time required a factory image install, as reflashing the stock boot.img still led to quite a few issues.

Any help would be appreciated. I've used this method to root a few times on this device, mostly when FlashFire fails; the first instance today was from another FlashFire failure.
[SuperSU] Alxoom33:
Find SuperSU 2.79 SR 4 in this thread and flash it instead.
[SuperSU] Kisakuku:
May bootloader? Need to flash Verified Boot Signer v5 before rebooting out of TWRP.
[SuperSU] bobcatt:
Don't freak out, I just got the same. Good news is you can recover without factory reset. Bad news is you will loose root.

When on the device unlocked warning screen (black background), hold the power button for a good 10 seconds until the device powers off.

Power on the device in recovery mode by pressing power and volume down until you get to see the little android

Fastboot the device: fastboot boot xl\twrp-3.0.2-0-RC1-fastboot-marlin.img

Reflash the latest stock OTA update: https://developers.google.com/android/ota

Wipe Dalvik

Reboot... and wait

As it might help others, installing the the Stock Rom OTA May 2017 update and later flashing SR3-SuperSU-v2.79-SR3-20170114223742 is likely to cause a boot loop.
[SuperSU] GRSteelers:
I don't think it's the bootloader, as it's the stock on a recent phone that I've already successfully gone through this process with a few times.

Thus far I'm unable to find SR4, I'll have to dig a bit.

Yeah I did try that, but unfortunately I ended up with core processes constantly restarting, including the system ui; I had to cut my losses and wipe.

Still unable to root without a bootloop, but flashing the stock boot.img from the full factory image does resolve it.

It's possible that my core processes issue had something to do with the fact that I had just installed a new OTA, and installing the old one caused some trouble.

I'm hoping a new SuperSU release will take care of it, Chainfire is usually on top of these things.
[SuperSU] Kisakuku:
Or you could just flash the zip I linked.
[SuperSU] srqrob:
I'm having bootloop issues with an install of TWRP on the May Pixel XL update. Should I be OK with rooting with SR3 via a TWRP I'm accessing via a fastboot boot as opposed to from the installed phone recovery? It's not the most convenient but I can live without an installed TWRP as long as I can root.
[SuperSU] Ch3vr0n:
No you won't. The problem is the May bootloader, things have changed as you'll find in the last few pages. Simply flash the April bootloader for now

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] Kisakuku:
Either

or flash Verified Boot Signer v5 after SuperSU and before you reboot out of recovery.
[SuperSU] srqrob:
Thanks. Flashed the zip and perfect. Thanks to Chainfire also.
[SuperSU] AJ:
Is there a way to root developer preview 2 on the pixel ?
[SuperSU] Kisakuku:
You could try the Pixel ODP1 rooting method with some verified boot signer v5 flashing thrown in.
[SuperSU] jcmm11:
Yes, it is the bootloader. Did you successfully go through the process with the May bootloader installed, or with earlier versions? May bootloader changed things. Go see the other thread that was linked. Answers will be found there.
[SuperSU] chevycam94:
Looks like the O-DP1 root method is broken in O-DP2 (Nexus 6P). Poo. lol I'm waiting for an update so I can release my next custom ROM based on DP2.
[SuperSU] iamaniff:
It's work on Nexus 5X
[SuperSU] chevycam94:
I have yet to get it to work on the 6P. Tried both the original SR4, and the extra delay version. Just reboots forever, or hangs on the Google name. Still working on it....
[SuperSU] lesbianu:
Flashed ODP2, flashed TWRP 3.1.0-0, rooted using SR4 for ODP1 from Chainfire (the one without the extra delay), everything looks OK for the moment.

The only thing, now the Google Play Store it's "uncertified". The apps were staying on pending at the beginning, but now it's downloading and installing them. Will see if I encounter any problems...

[MENTION=631273]Chainfire[/MENTION] Thanks for your work!
[SuperSU] Maxr1998:
Have the same. Did you try the new VerifiedBootSigner? I will also try if it boots with only forceencrypt and dm-verity disabled. [MENTION=631273]Chainfire[/MENTION], could you provide a "SuperSu" zip for the future that only patches the above mentioned items, without actually installing su? That would make testing a lot easier, because using all the sukernel helpers (unpacking ramdisk, decompressing, extracting files, patching, everything in reverse) manually takes a lot of time..

EDIT: I actually got it to work by flashing the boot.img, SuperSU, and the VerifiedBootSigner-v5.zip, it boots up without issues and root also works.
[SuperSU] zipredictive:
Hi, what have you done? Just flashing the extr delay zip or followed the whole procedure?

thanks
[SuperSU] jalizi:
Hi

I have installed SuperSu 2.46 and twrp 3.0.2 recovery on the latest stock MM (c435b571) on my huawei mate7. when I try to update SuperSu to the latest version (2.79 SR3), I lost root state and SuperSu will hidden.

How to update SuperSu to the latest version?
[SuperSU] ashyx:
Unroot, Install the zip version.
[SuperSU] The Wrath of Kahn:
Did you have to use the VerifiedBootSigner-v5 while attempting this?
[SuperSU] lesbianu:
Just flashed the .zip, and waited for the phone to reboot few times... When finally started, SuperSu was installed and fully functional!
[SuperSU] zipredictive:
on what device and what rom? thanks
[SuperSU] lesbianu:
Nexus 5X, using the ODP2 (Android O BETA) released last night. I forgot to mention the details, sorry!
[SuperSU] Ch3vr0n:
The play store shows "uncertified" because either 1) the device is rooted and/or 2) the bootloader is unlocked. That voids safetynet which is checked in order to be certified.
[SuperSU] zipredictive:
I can confirm 5x with the last Android O (it rebooted twice)

Thanks lesbianu
[SuperSU] Alxoom33:
My boot animation stops and then reeboots. Pixel C. Using 2.79 SR 4
[SuperSU] Wolfcity:
I'm using 2.79 SR3 since it's appearance on my Moto G titan running Aosp Extended 7.1.2. After an update with cleaning system/cache/dalvik and reflashing superSU it's working some time, then it says binary outdated, update fails.

Any suggestions?
[SuperSU] Wolfcity:
Did a full unroot,reflashed 3.1.0-0 recovery, same problem. Now I did a complete clean flash and after some time SuperSU SR3 2.79 asks for binary update which fails.

Someone who could help me out? Never had this problem with this rom and this version of SuperSU.
[SuperSU] martyfender:
Did you try the unSU Script zip? I wouldn't think you would need to with a clean flash, but maybe others will have suggestions?
[SuperSU] Wolfcity:
No I didn't because I thought a full clean install should solve it and there's​ nothing more the unsu.zip could do. At the moment I do a second clean flash with the first 4.2 aex ROM and until now SuperSU is working, knock on wood....if it stays like this the problem is between the last aex update and SuperSU 2.79 sr3.
[SuperSU] russian392:
SR4 working fine with Odp2 and franco kernel r52. ALL GOOD no playstore issues.

Nexus 6p 64gb
[SuperSU] thenameistoms:
What if even after the extra 15-second delay zip is flashed and the still the device is stuck in bootloop?
[SuperSU] Ja_som:
Then try to reflash, few days I've been using the normal zip (w/o delay), but my boot freezes, so I just flashed with delay and it looks OK now.
[SuperSU] Mar-cel:
Why does Supersu gets no updates?
[SuperSU] dahawthorne:
Because it works...?
[SuperSU] gubacsek:
help please

hi [MENTION=631273]Chainfire[/MENTION]!

I would like to ask for a little help!

I'm trying to get root working on a pixel with O DP2 for a while, and came pretty far, but here my knowledge stops...

As you most probably know, the fastboot bootable TWRP image does not actually start TWRP ( when booting with Android O dp2 bootloader ?). I see some errors while trying to decrypt the data partition, so most likely Google changed something again (bad magic of data partition....). First I tried to repair TWRP, but i can't compile a working version, that I can boot, so I gave up on this. Fortunately, although the recovery doesn't start, it gives at least ADB, so I can play around with a root shell :D

So I started to take your update-binary (of course the script) from the supersu zip file, and modified parts and now I am at a point where it runs through, doing all the patching, changing, unpacking, repacking of the boot image, as it should do in recovery. I manually sign the resulting boot image on my pc, and flash it with dd at the end. Everything looks fine, but when I boot, well, nothing extra happens :D The phone boots normally, and that's it. It seems that launch_daemonsu.sh is not executed (no /dev/.launch_daemonsu.log file exists). I checked, unpacked the boot image, init.rc, init.supersu.rc, everything is in place, it is just not executed.

There is one thing: because TWRP fails to decrypt the data partition, the files (su.img and Supersu.apk) are placed into /cache. Thanks to your brilliant code, it is already prepared for this scenario, so I didn't had to modify anything :D

I would like to ask for your opinion, what should i check. I can give you the boot image, log of creation of the boot image, anything that helps. Unfortunately I have no idea how to get any log during this part of the boot process... No access to kmsg, no log file created by launch_daemonsu.sh......

I would really appreciate your help on this problem!

Thanks in advace!
[SuperSU] corkiejp:
Stable Updated to 2.80!!??

Stable version 2.80 has been released today (24th May). Waiting on [MENTION=631273]Chainfire[/MENTION] to make it also available from his site, with a changelog posting. 2.79-SR3 is working fine at present on my devices. So no rush to update, if it only includes SR4 updates for O!
[SuperSU] Chainfire:
I'm not sure which devices support ODP2 on v2.80. At least Angler (Nexus 6P). Pixel support is coming in SR1, as well as a test run on the other Nexuses. They changed up quite a few things in the boot sequence again for the Pixel, and as you have already discovered, that is very difficult (or time consuming, rather) to debug. I'm getting close to solving the issue, though.

TWRP (RC1) is having difficulties both with the ext4 quote as well as with decryption. This will probably require a rebuild of TWRP. Of course, if you format /data ( make_ext4fs /dev/block/bootdevice/by-name/userdata ) this allows TWRP to function until the next time Android is booted.

There is a way to mount /data without decrypting, by using these commands:

mount -o rw,remount rootfs /
SLOT=$(getprop ro.boot.slot_suffix)
mkdir /system_root
mount -t ext4 -o ro /dev/block/bootdevice/by-name/system$SLOT /system_root
mount -o bind /system_root/system /system
/system/bin/tune2fs -Q ^usrquota,^grpquota,^prjquota /dev/block/bootdevice/by-name/userdata
umount /system
umount /system_root

After a second or two, the screen will stop flashing, and /data will be mounted. If Android boots again, you will need to redo those commands.

You mention the brilliance of using /cache when /data is not available: this is actually not true for the Pixel, it does not have a /cache partition, it is faked in ramdisk. All data written there is lost at reboot. This is also why the above is necessary: SuperSU can actually cope with /data still being partially encrypted on the Pixel, but it must be able to mount it.

As for installing SuperSU (or any other ZIP, really):

adb push something.zip /tmp/install.zip
adb shell
cd /tmp
rm -rf install
mkdir install
cd install
unzip ../install.zip META-INF/*
chmod 0755 META-INF/com/google/android/update-binary
META-INF/com/google/android/update-binary 3 1 /tmp/install.zip
exit

Of course, none of this really helps, because the currently available SuperSU ZIP will not work. But stay tuned, I'll have an update on this hopefully within a few days.
[SuperSU] Chainfire:
I expect to release this tomorrow. It is late.
[SuperSU] smartfaune:
v2.80 already on Aptoide...

??

Installation creates a 'mobclick_agent_cached_eu.chainfire.supersu' file in SD

What this file for ?
[SuperSU] shaggyskunk:
Advertising....probably because of aptoide

https://www.theatlantic.com/amp/article/36963/

Google is your friend ;)
[SuperSU] Ibuprophen:
The v2.80 Stable has been creating issues for me too...

I believe that it, might be, tied to the SuperSU Pro still remaining on v2.79.

Normally when a new stable version of SuperSU is released, there matching SuperSU Pro is awaiting on the Play Store with a matching version.

I can only assume this but, I'm actually forced to flash back to the stable v2.79.

Oy Vey! LOL!

"Live Long and Prosper..."

~Ambassador S'chn T'gai Spock

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise
[SuperSU] Shtiff1:
Will this ever move towards something like "magi**" being able to hide apps, and etc.... Working alongside Xposed (as it does now) and making devices show certified? It would be greatly appreciated. Thank you!
[SuperSU] shaggyskunk:
v2.80 SuperSU and SuperSU Pro are up on the Store now.
[SuperSU] Wolfcity:
Working after binary update but Adaway doesn't work anymore, it seems it cannot write to /system. First it told me to change the host file directory to data/data/hosts, then it wasn't able to create a symbolic shortcut to system/etc.

The error message was something about S-On/Off on HTC devices..

Motorola Titan, AEX 4.2 (7.1.2).

Someone an idea?

[MENTION=309187]edit[/MENTION]: It works in system mode.
[SuperSU] Ibuprophen:
Great!

Thanks a Bunch for letting me know!

"Live Long and Prosper..."

~Ambassador S'chn T'gai Spock

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise
[SuperSU] whereme:
Why does supersu v2.80 need so many new permissions?
[SuperSU] Ibuprophen:
I'm not sure why it asks for certain permissions that i never thought it would ask for.

Just a friendly reminder... You'll may want to post your questions, comments, concerns, etc... within the following SuperSU Stable v2.79 thread.

http://xdaforums.com/showthread.php?t=3452703

"Live Long and Prosper..."

~Ambassador S'chn T'gai Spock

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise
[SuperSU] fubo73:
Is it supersu Pro update necessary? I've got it from amazon appstore, and there is no update up to now.
[SuperSU] Chainfire:
Please see my post here:

https://xdaforums.com/showpost.php?p=72422394&postcount=1436

Also, the Pro update is not necessary. The version number increase is merely cosmetic. I used to leave it at 1.00, but people keep asking why the version number is different from non-Pro.
[SuperSU] osm0sis:
I see 2.80 pushes the change that breaks system file replacement via bind mounts. Shouldn't this be limited only to Pixel where it's (currently) necessary? Would explain AdAway's systemless issue as well.

... Or maybe it's just another​ symptom of the larger problem?

Regardless of who actually committed the breaking change, it does feel like they are pushing half-baked releases out the door on you as "stable" where you would have tested things more thoroughly. :(
[SuperSU] Chainfire:
I'm not even sure what you mean. Can you elaborate?

Nothing is intentionally breaking bind mounts. How is this necessary for Pixel?

I'm not sure that's true, as I'm having a hard time replicating the problem on the devices I usually test on.
[SuperSU] osm0sis:
I have a few su.d scripts that bind mount a whole system directory. One, for example, replaces whatever ROM sounds/boot animation are in /system/media with Nexus ones I keep in /su/media.

After 2.80 updated from the Play Store and did the binary update, I pressed the reboot button in the app and the bootanim and all the system media reverted to the ROM's, suggesting the bind mount didn't work or wasn't early enough in the boot. I flashed back to 2.79 (stable) and all resumed working.

I thought I recalled you saying you had to adjust when the su.d hook took place in the boot to accommodate ODP and/or the Pixels, sorry if I have misunderstood/misremembered.
[SuperSU] Chainfire:
You remember correctly, but that issue has been fixed / reverted for v2.80 final release. Nevertheless, I will look into what you're saying. Which device/firmware did you experience this on?
[SuperSU] gubacsek:
:eek:

I always wonder where do you get these informations from :D Like now with the quotas and tune2fs, previously the boot signing....

Awesome ! I really could mount /data, put the su.img, and Superuser.apk there, but unfortunately this didn't change anything...

It still seems like something is wrong in the boot image, because the launch daemon script doesn't get executed.

Anyway, thank you very much for these instructions again! It is always nice to learn new stuff :D

Unfortunately one answered question pops up at least 2 new ones :D Like:

- is it possible to decrypt the data partition? I saw in TWRP source, that vold is being used, but I have no idea (yet? ) what it is..

- why do things I copy to /system get lost after reboot? (i thought it has to do with the bind mount, but even if I copy through /system_root/system/..... things get lost...)

...

Google messed up android since I last played with my htc desire :D It was so easy... you could mount a partition and change it's contents. separate recovery, and cache partitions. Now ? You can't even change anything.... It is very disappointing.. I'm starting to give up and go back to 7.1.2... :( I only have 1 phone and I need my sound mods :D It would have been nice to be able to solve this on my own, but I need to learn a lot more.... You are an awesome person, and you will most probably solve the problems before me :D So I would like to thank you for the time and effort spent and spend on making root possible! And also for all the information that you provided! I find this wonderful to be able to ask and also get help from you personally!
[SuperSU] osm0sis:
Nexus 7 2013 running the latest LineageOS nightly.

The su.d script contains:

#!/system/bin/sh
# chmod -R 755 /su/su.d
#
# Systemless Media Replacement Mounts
# osm0sis @ xda-developers

mount -o bind /su/media /system/media;

From my Nexus Media Installer package.
[SuperSU] Chainfire:
What's the output of "getprop | grep daemonsu" ?

EDIT: Nevermind, I have found (but not solved) the issue
[SuperSU] Taomyn:
I've noticed the same with my stock Nexus 6P - AdAway was suddenly disabled and could no longer save host files. The only bind file I have was for it. Also my Simple Reboot app could no longer reboot to recovery. Reverted to SR4 and all back to normal.
[SuperSU] The Doctor04:
Just to share...Nexus 6, Pure Nexus Rom 7.1.2 and Franco r67 kernel. Updated to Super v2.8 and lost AdAway in same fashion others have noted. Flipped back to 2.79 and it works again. I was fortunate enough to not get a bootloop or anything funky. BusyBox, file explorer, other root required apps worked. adAway was the only one that broke. Thanks as always [MENTION=631273]Chainfire[/MENTION] we know it will get fixed ?
[SuperSU] shaggyskunk:
[MENTION=631273]Chainfire[/MENTION] is aware of the Adaway issue and has asked for people to stop reporting it for now.

https://xdaforums.com/showthread.php?p=72424502
[SuperSU] Ch3vr0n:
[MENTION=631273]Chainfire[/MENTION] after reading both stable and beta i'm glad i didn't update yet. Had only downloaded initial zip. Though i do have a suggestion. I recommend (if it's possible) to revert the stable version to 2.79 and have the re-pushed through the play store. At least that would prevent the buggy 2.80 from being pushed to more devices and bootlooping them. Causing worrying users to flock here :)
[SuperSU] Midomad:
New SuperSU 2.81 version is Up on the playstore !
[SuperSU] Caltinpla:
I have no problem at all after updating my SupperSU to the 2.80 stable version from the Play Store. My phone and AdAway app are working fine.

I have Nexus 6P running the latest PN rom with Franco kernel.
[SuperSU] gothicVI:
Same here. Updated from sr3 to 2.80 via play store, running lineage13 on thea.

Gesendet von meinem Moto G 2014 LTE mit Tapatalk
[SuperSU] Lord_Flaya:
2.81 from play store not successful in updating binary. After rebooting SuperSU claims root not found. Reverting to 2.79 solved the issue. Nexus 5x in pn 7.1.2 Franco kernel
[SuperSU] peterlee928:
DELETE
[SuperSU] andre0005:
Same issue.
[SuperSU] ashyx:
People who flash stuff willy nilly and allow auto updates only have themselves to blame. They almost always have the opportunity to backup before proceeding and therefore any easy way to revert and fix.

In the very rare circumstances were that's not possible then caution is the name of game and maybe popping on the old giggstacles and having a quick peruse before pressing the go button maybe a good idea.

If the few who can't be bothered end up here bleeting about their devices not booting then why should a retrospective fix be applied just to accommodate them? :rolleyes:
[SuperSU] Electronic Punk:
Yes, those idiots that actually install apps from the Play Store are to blame.
[SuperSU] Ch3vr0n:
I have auto-update enabled by default. I disable it when i read stuff like this ;) That said, i usually always read the last few pages when a new version is out. Just to make sure there's no issues before i flash things. Since there were, i held of and disabled auto updates. Still rocking SR3 here
[SuperSU] veez21:
Most users will assume that it's safe (like above noob level but below the guys who knows stuff) to update cause it's stable and is available on play store, and is from a well known developer (well, not ccmt).

Those who bleet about their device not booting are users so, why not accommodate them, since supersu is on a scale that almost all noobs will use it as their first go to root solution.
[SuperSU] guitar1238751:
Can confirm that "SuperSU-v2.79-SR4-20170323220017-ODP1-5X-6P" works fine on my Nexus 6P running ODP2. Used twrp 3.1.1-0. I was also able to unroot , sign into snapchat, and then reroot without any issues. Boot times are also still blazing fast on ODP2.
[SuperSU] manpildo:
Maybe because the release is borked and should be pulled anyway? What's the point in leaving up something that is broken? So that those few people who make backups before every update can feel arrogantly good about themselves?
[SuperSU] buzzboy:
+1 had to reflash SR3, and disable auto-update in PlayStore. (Pixel XL PureNexus 7.1.2)
[SuperSU] Chainfire:
I wish we could have pulled it and put v2.79 back, but due to recent changes to the Play store, the old version cannot be put back (because it was released too long ago, bloody Google and their constant changes to the developer console).

Believe it or not, v2.80 was actually a staged rollout with no issues reported on the first batch.

I am trying to get to the bottom of the issues, but it will take some time, and actually v2.81 is making it more difficult than had we just stuck with v2.80.

Oh well, sometimes this stuff happens.
[SuperSU] wizardwiz:
Same here.

Not 2.8 nor 2.81 work on my 7.1.2 nexus 6p

Had to revert pack to SR3 to get it to work properly