yashsingh1/xdaforums huggingface dataset:
[SuperSU] bmg1001:
Actually, my 6P started to bootloop randomly again. I fixed it by removing su.img from data, but that obviously removes root. Reflashing makes it bootloop again. I'll see about getting some logs whenever I'm home, just thought I'd mention it if someone else has the same issue.
[SuperSU] MatiasLopezxD:
Every time the phone reboots it has a bootloop, just wait until it starts normally xd
[SuperSU] eduardozeassesme:
No problems here

edit: make a reboot and have bootloop

edit 2: re-flas supersu 2.79sr4 fix the problem mmm for now
[SuperSU] Maxr1998:
I also had the bootloop, but after four times it finally booted up. Just give it some time, then it'll work.
[SuperSU] bmg1001:
Eh, I went back to my pre-O backup for now. I'm just gonna sit this one out till May. On a reddit thread, someone mentioned the same thing about it taking a few loops. Thanks!
[SuperSU] Chainfire:
If the boot animation freezes for a second and it reboots, you are most likely hitting the same kernel panic I was during development. I'll add some info to the download post.
[SuperSU] CyberCodeDroid:
I have a question, if I want to version 7.1.2 of the Beta program, go to the first version of O, flash the FlashFire it over. Subsequently Supers over TWRP? Or can I somehow had to flash supers in FlashFire?
[SuperSU] Chainfire:
Disable EverRoot, and add the new SuperSU ZIP for ODP1 as a "Flash ZIP" action. That may work.
[SuperSU] CyberCodeDroid:
Work perfect Mr. Chainfire!
[SuperSU] schoerb:
My Nexus 5X was in a bootloop, too for about 15 minutes after I flashed SuperSU. But I was charging the phone at the same time.

So I turned off the 5X, finished charging and tried later. Then it boots correctly :) Thanks!
[SuperSU] kunal_07:
Anyone tried using substratum on O?
[SuperSU] skiely666:
Yes, no go..
[SuperSU] iamaniff:
How can I removed all file for unroot without flash system image?
[SuperSU] krasCGQ:
osm0sis' un-SU script will do it.
[SuperSU] iamaniff:
It can't.. coz I can't play Super Mario Run like before.
[SuperSU] krasCGQ:
Ah the SMR? This phenomenon starts to develop... :rolleyes:
[SuperSU] babyblue0718:
I searched a lot but could not find the definition of ODP1.

What is ODP1 and ODP2?

https://en.wikipedia.org/wiki/Ozone_depletion_potential

It seems not to fit your context.
[SuperSU] DEVILOPS 007:
Android O/8.0 developer preview 1 and 2
[SuperSU] viper2g1:
Is there a working root for 7.1.2 (March update - NPG47I)? I've tried the beta on the first page and it failed. Searched this thread and didn't see anything specifically pertaining to this.

Thanks!
[SuperSU] ridobe:
Yes, just did this a few hours ago.
[SuperSU] DEVILOPS 007:
I don't that is the devs thought because I've seen many people on it with root and no problem. It could be your device or setup?
[SuperSU] Pcsx2006:
SR3-SuperSU-v2.79-SYSTEMMODE.zip system mode causes Bootloop on OnePlus 3 Oxygen OS 4.1.0(Android 7.1.1)
[SuperSU] viper2g1:
I wonder why mine failed. I've rooted countless times before.
[SuperSU] DEVILOPS 007:
Try formatting in twrp before you try again.
[SuperSU] viper2g1:
That didn't do it but starting fresh from the factory image did. Not sure what the problem was but I'm rooted now.
[SuperSU] mobileman88:
Works well for me
[SuperSU] chevycam94:
Will that test SR4 for the 6P/5X work on 7.1.1 and 7.1.2 also? I would assume so.
[SuperSU] Alxoom33:
No, only for Android O beta

---------- Post added at 10:36 PM ---------- Previous post was at 10:34 PM ----------

Yes, 2.79 SR3 working well for these releases. The SR4 beta is only for select devices running Android O beta.
[SuperSU] tux95:
Works with Pixel C

[MENTION=631273]Chainfire[/MENTION]: I can confirm your SuperSU-v2.79-SR4 works on Pixel C with ODP1. Finally I can use my titanium backup. Nice work :good:
[SuperSU] DEVILOPS 007:
Sr4 works fine on 7.1.1
[SuperSU] nimnull:
Hello

I found out that supersu does have a daemon.

Can i get SU without it?

Can I manually push all necessary fie to system via twrp adb?

I just need adb root access

Thank you in advance
[SuperSU] mimo.aridi:
Hey guys i have a Sony Z2 D6503 bAsed on LineAge Os kernel 3.4 android 7.1.

I had su sr3 working but what i did is i pressed full unroot in superuser app.

Then when u try to flash su.zip (systemless mode) the process goes without errors. But when i reboot the phone doesn't boot. The boot partition gets corrupted. It used to work but after full unroot the boot.img gets corrupted and phone doesn't boot. I also tried latest systemmode but i get stuck on boot animation.
[SuperSU] Captain_Throwback:
TWRP has adb root by default. You don't need SuperSU for that.
[SuperSU] nimnull:
I know, but i need root in device also, but only for adb

So i need only "su"

Question is can I manually install it via twrp adb?
[SuperSU] Captain_Throwback:
No. You need to let the zip install it for you.

EDIT: If you really just want to push the su binary to your device, I'm sure you can, but it probably won't be fully functional (if at all). So try it and let us know.
[SuperSU] mimo.aridi:
Any help?
[SuperSU] Captain_Throwback:
Reflash ROM boot.img and try again.
[SuperSU] mimo.aridi:
Did that no luck.
[SuperSU] veez21:
Reflash your rom and flash unSu zip by [MENTION=4544860]osm0sis[/MENTION] (you can google that). Then flash supersu. Idk of it'll work but a it's a possible solution.
[SuperSU] Alxoom33:
On what device?
[SuperSU] CrashTestDroid:
2.30 is working great for me. CM12, temasek build
[SuperSU] jeryx:
2.30 beta also working very good on htc m8 gpe android 5.0 sky dragon rom! Thx a lot sir!
[SuperSU] daystrom:
Installed 2.30 using TWRP on a Nexus 7 (grouper). Working fine so far. Thanks!
[SuperSU] Krowbarr:
2.30 beta working great on Galaxy S5(G900P) running MOAR Rom 2.2/kt kernel/Philz recovery
[SuperSU] Pure Drive GT:
So is this how root is "going to be" on lollipop? Was waiting for everything to settle down before rooting the N9. Saw that you want to roll out to Playstore soon, can I assume that once that happens, everything will be more or less reliable?

Gesendet von meinem Nexus 9 mit Tapatalk
[SuperSU] Long Island NOOBIE:
[BETA][2014.11.25] SuperSU v2.30 functioning flawlessly on my older Samsung Galaxy devices. SGS3-i747 running KK-4.4.2 TW stock rom w/TWRP custom recovery and Tab2-10.1 P5113 running KK-4.4.4 Slim Kat custom rom w/TWRP custom recovery . As always, thank you sir!
[SuperSU] HorstiG:
No Problems on Galaxy S3 and S5, only on Winphone i have a little Problem, can´t install SuperSU :D
[SuperSU] fhem:
running 2.3 on N9 with R build no problems.
[SuperSU] aldyu:
New material icon looks good, it should now be the default overall, imo, other icons aren't needed anymore. :)
[SuperSU] rcobourn:
All good on Tmobile Note 4.
[SuperSU] Gips3yD4ng3r:
All goo nexus 5 sykopompos rom
[SuperSU] gianton:
Working great on OPO CM12 pre-alpha
[SuperSU] nyijedi:
Is getting OTAs in the future after rooting as simple as using the remove root option in supersu, or is this not enough in 5.0? Is more required, like wiping the phone?
[SuperSU] Haadkoe:
Thanks Chainfire, 2.30 seems to be working well here.
[SuperSU] ramjet73:
I think that depends on the device. Most OTA updates require the stock recovery and some won't install if the system partition has been modified at all.

ramjet73
[SuperSU] livelie:
XModGames

Nexus 5, Android 5.0, SuperSU Beta 2.30

XModGames still does not work!

Please help!
[SuperSU] Srandista:
Contact developer of app. Incompatibility with Lollipop is not problem of SuperSU.
[SuperSU] ajack2001my:
SuperSU v2.30 works as expected on stock Nexus 4 Lollipop with Franco kernel r214
[SuperSU] USBhost:
All good here

Nexus 9

FIRE-ICE Kernel
[SuperSU] flakinarist:
Still no working WifiKill :(

SuperSU says it granted root access, but WifiKill doesn't think so...

Do you need any further information / logs? Or should the developer be contacted?
[SuperSU] nimnull:
Okay, fine

What if I want to execute one command: pm disable <package>

Can I put it somewhere in "/system" via twrp adb, so it will be execute after the boot?

I just need to remove one package and disable few.
[SuperSU] Captain_Throwback:
Can you put what somewhere in /system? The su binary? I already said you can. Just extract it from the zip, mount /system in TWRP and copy it into /system/xbin. Did you try it, like I suggested? Stop asking and start trying...
[SuperSU] Ibuprophen:
I agree with you.

For this... I don't agree (respectfully of course!).

The SuperSU zip file, by design, will only property install one way by flashing it as is.

For the binaries to be installed outside of using the app/zip file, a separate file would have to be created with the SuperSU binaries and Chainfire would be the only individual who could accomplish this to correctly work and being on vacation on top of having so many other things on his plate, i doubt he'll be even remotely interested in doing this.

Also, he would also have to consider that, if the separate binary package was created, then he would have to create updates to it as the binaries get updated adding more to his plate.

The member with the issue will have to be helped out to learn to use what he's got so, hopefully, he'll know what to do with the next SuperSU binary update.

I'm stating this both out of respect to you and for the member to understand why he's got to learn to use what he's got.

I still think you're a great individual Captain_Throwback for helping that member out!

Peace my Friend!

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

***PLZ THANK ME WITH A THUMBS UP***

---------- Post added at 11:57 AM ---------- Previous post was at 11:42 AM ----------

I would have to recommend not to do that.

The binaries are not only just placed in its directory, other modifications and such are made to accommodate the Binary installation. The SuperSU application and the system needs to know what, where, and how to use the binaries because just being there just isn't enough for their being used at all as well as being used appropriately when they're being called on for use.

Your dilemma is a challenging one and i have a feeling that you're doing your best to communicate the information here, I've got a feeling, though I'm sure that it's completely unintentional, that the whole picture isn't being seen by the others here (though, i may be wrong for everyone here).

I'm actually trying to think of something myself but, am trying to get the whole picture to see what your seeing.

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

***PLZ THANK ME WITH A THUMBS UP***
[SuperSU] :
Wipe google play data. And re download the game after uNroot
[SuperSU] DEVILOPS 007:
Nexus 6p
[SuperSU] DEVILOPS 007:
See
[SuperSU] iamaniff:
Not work
[SuperSU] skiely666:
Just download the apk from apk mirror, I'm rooted on O with Mario run working no problems. After i rooted it doesn't show up on the play store..
[SuperSU] veez21:
I think you misunderstood him, he meant that the other guy can push/copy the binaries by himself but it probably wouldn't be functional and won't be a good idea. That's why he said that. He didn't mean what you what you thought, i think. :rolleyes:
[SuperSU] :
Have you returned to stock? Or you still have root. To play super Mario u need to return to stock and then wipe data of play store that's how I got it to work

---------- Post added at 01:08 PM ---------- Previous post was at 01:07 PM ----------

It works until after tutorial is done and when it has downloaded data. Some time after that you will get a error which will loop you back to main screen
[SuperSU] iamaniff:
How to return to 100% stock without flash stock system.img? I just unroot. Then still can't play. What file I need to delete manually in system?
[SuperSU] :
Well if you don't flash system.img you won't return to stock if u done modifications would you?

I was rooted on my p8 lite and even if I had cts match and no root I couldn't play.

Updated with ota with twrp and manually wiped play store data it was visible in play store and I can play more than just tutorial
[SuperSU] iamaniff:
I don't want flash stock image bcoz I have put pixel launcher on system. Nvm.. btw thanks
[SuperSU] :
Isn't there port for non root pixel launcher?
[SuperSU] iamaniff:
I'm running Android O
[SuperSU] skylover007:
thanks for sharing.........................

thanks for sharing....
[SuperSU] CyberCodeDroid:
FlashFire repeatedly falls, if I wanted to try flash any FW package when choosing a file. Does anybody have the same experience?
[SuperSU] LazerL0rd:
Fingerprint has disappeared :\ Safe mode doesn't fix it. It's there after a reset but after flashing SuperSU it disappeares....

Could it be to do with the new build.prop line - ro.bionic.Id.warning=1
[SuperSU] Ibuprophen:
Your question is a valid but, extremely open...

This all depends on what your device is, the firmware installed and want to install, what your bootloader is or is it locked, etc... etc...

To get the best help/support, even for actions as simple as what your asking, all depends on exactly what you have and exactly what your doing.

I am in no way refusing to offer you assistance (as, I'm sure, my other counterparts feel the same way) but, please help us help you.

Thank You for Your Understanding and Patience!

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

***PLZ THANK ME WITH A THUMBS UP***
[SuperSU] jcole90:
Hi guys sorry if this has been answered previous but i have spent 3 hours reading, rooting, unrooting restoring defaults etc to no avail!

I rooted my two tablets yesterday for the sole purpose of using HIROMACRO the app works great and does all i need it to, now it was working great on both tablets, one is a galaxy tab3 (working) the other is a Galaxy Tab A SM-T585 10.1

Now the macro app was working great doing what it should etc, then i went to use it earlier this evening and suddenly it just will not recognise the Action keys,

So i used the setting that displays the record button on screen, clicked this tried a test "run" but its saving nothing its as if it is suddenly not recognising the input,

As this is anew tablet i had no issues wiping it back to factory settings etc incase i had clicked something, tried unrooting re roorting installing different SU versions etc etc but nothing is working

Any ideas of a fix as it is driving me mad!

Appologies if this is wrong section google search brought me here, and if it is can u please advise where to look

Thanks!

EDIT:

I have tried numerous other macro recorders that recognise touch input and none of them are working as opposed to just this one app? its as if there is something blocking the touch input being recognised? any suggestions?
[SuperSU] w0rdie:
When pushing files to /system using ADB root via TWRP -- the files are missing when I boot into Android, but are present if I reboot into TWRP.

Am I missing something obvious?

***********************

Should note that the above is the case PRIOR to install the ODP1 SU -- once its been installed the /system files that I see in TWRP are reflected in Android, however the desire is a modified system without SU installed.
[SuperSU] Captain_Throwback:
Forget to change permissions/owner on the files?
[SuperSU] w0rdie:
adb push blahblah.apk /system/priv-app

# chmod 777 blahblah.apk

# cd /system/priv-app

# ls -l

blahblah.apk shows rxrxrx

Boot into Android and its no where to be found. Install SR4, boot into Android and there it is.
[SuperSU] Captain_Throwback:
I didn't see you change owner anywhere...(I did say "permissions/owner" didn't I?)
[SuperSU] w0rdie:
Like I said to start with -- assumed I was missing something obvious, I've never had to chown a file when doing this before. (Haven't used the command at all).

Resource online for more info on changing ownership?
[SuperSU] jcmm11:
Just Google "chown Linux". It's simple enough. For apk files

chown root:root name.of.apk

Also permissions for apk files are 644 (they're not executables)

I also stick them in individual folders in priv-app. Folder permissions are 755, also root:root
[SuperSU] asadnow2k:
just need to flash with stock firmware mate to revive in good state than it can be done using a service any firmware any patch any thing
[SuperSU] w0rdie:
Thanks -- By default with ls -la I'm getting this output, so if root is owner, I should be fine right?

-rw-r--r-- 1 root root 2370870 2017-03-18 16:46 debug.apk
[SuperSU] jcmm11:
Yes, that looks good
[SuperSU] proza:
Is this the systemless SuperSU?

Does it support Lollipop? or I need to use the 2.6.x
[SuperSU] RandomPooka:
At worst, mimic the owner:group of an existing system apk. But, root:root should work.

-- update on my idiot self --

They're mostly root:root anyway. Just thinking that there might be groups like on linux system for various functions, and you could prevent an app from running as root while still being a system app
[SuperSU] jcmm11:
Well each app does have its own id. You have to remember that first of all apk's are not executable files. If you drop into /data/app you'd see that instead of root root it becomes system system. If you look at the odex files found in the oat subdirectories you'll see that the groups become unique for each app. The system apps equivalent are .dex files found in dalvik-cache. And those files are not world readable.

So Android does have a permission system, it just works differently from normal 'nix. I don't completely understand how it all works and ties together myself, but I do know it's there.

So you're idiot self isn't quite as idiotic as you thought ?
[SuperSU] krisyarno:
I pulled the Pixel Launcher and audio from the O-Preview of the Pixel XL, used Luthepa1's Black Edition Boot Animation, and created a flashable zip of this. You can use FED-Patcher to make this mod work without root. Here's my post about it

https://xdaforums.com/nexus-6p/themes-apps/zip-o-preview-pixel-launcher-pixel-mod-t3579092

I'm on the O-Preview without root and the Pixel Launcher works fine with this
[SuperSU] ulxerker:
yes, use this version. it will automatically install as systemless.
[SuperSU] iamaniff:
I means can u swipe left?
[SuperSU] krisyarno:
Yes you can, this will install it as a system app
[SuperSU] Captain_Throwback:
You might need to also chcon, if they got copied with the wrong file contexts. ls -lZ will tell you the context.
[SuperSU] gothicVI:
I guess you mean chown.

Gesendet von meinem Moto G 2014 LTE mit Tapatalk
[SuperSU] Captain_Throwback:
No, I don't.
[SuperSU] abeloman:
Trying to root moto g5 plus, it fails to decompress ramdisk... Any way to resolve this?

Enviado desde mi Moto G (5) Plus mediante Tapatalk
[SuperSU] -Deco-:
Update your kernel so that it is compatible with systemless root.
[SuperSU] abeloman:
Any way to make it work? I've tried many SuperSU zips and none working, even the system mode but they cause bootloop

Enviado desde mi Moto G (5) Plus mediante Tapatalk
[SuperSU] -Deco-:
Its not SuperSU, its your kernel. It is not compatible with the latest SuperSU edits so it will not work. Find an updated custom kernel for your phone.
[SuperSU] Ibuprophen:
It kinda seems as though something is already present within one of the directories where SuperSU accesses top install/modify causing a conflict with something that is loading while the system is going through the boot-up cycle.

Making my brain go into its own force close and reboot cycle itself LOL!

Have you tried a version of SuperSU that a few releases older?

Maybe somewhere between v2.76 - v2.78?

Just throwing out an idea...

Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
[SuperSU] abeloman:
I read that, something about compression used on kernel, but sadly my device have a few days on the market, to be specific moto g5+, which doesn't have too much development right now... So, I'm attached to stock ROM and kernel

I've tried lot versions of SuperSU, 2.52 until 2.79 systemless and system mode, none working

Enviado desde mi Moto G (5) Plus mediante Tapatalk
[SuperSU] -Deco-:
I've actually had the mentioned issue before in the past, specifically involving the use of the Hacker kernel with the GS6.

Ah, then there isn't much you can do I'm afraid.
[SuperSU] gothicVI:
You're right. Sorry, my bad.

Gesendet von meinem Moto G 2014 LTE mit Tapatalk
[SuperSU] dracinn:
Trying to root my Nexus 6P on O DP1 and it aborts in failure used 2.79 SR3.
[SuperSU] bdwilk:
https://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/post71561057
[SuperSU] ulxerker:
thats known, use 2.79 SR4 instead.
[SuperSU] Zdrpkamil:
CM is prerooted!?
[SuperSU] Ch3vr0n:
CM is, was, and always has been. LineageOS isn't.
[SuperSU] abeloman:
Seems I was able to remove dm verity and force encryption from my kernel... So, what's next? Flash my kernel and delete user data? I hope that would be enough for get SuperSU working...
[SuperSU] Idebutterpiep:
Does SuperSU v2.79 SR3 work on Samsung S7 Edge SM-G935F and Android 7 G935FXXU1DQCG?
[SuperSU] voroxda:
Yepp :good:
[SuperSU] no.human.being:
Moved ...
[SuperSU] Ch3vr0n:
You're in the wrong thread. Developer discussion => https://xdaforums.com/apps/supersu/devs-supersu-developer-discussion-t3291434
[SuperSU] Idebutterpiep:
Just flash twrp-3.0.2-5-hero2lte.img with Odin and then SR3-SuperSU-v2.79-SR3-20170114223742.zip with Twrp?
[SuperSU] buffer overflow:
Maybe I'm outdated... Can't flash img with Odin, or must convert img in tar ? :confused:
[SuperSU] Ch3vr0n:
if Last time i checked your 5X doesn't need or use Odin. Just flash it via fastboot
[SuperSU] jcmm11:
Except the person he's replying to (Idebutterpiep) has a Galaxy S7 Edge (at least according to his profile)
[SuperSU] ashyx:
[MENTION=631273]Chainfire[/MENTION]

Does SuperSU have issues with finding partitions defined as block devices in the recovery fstab?

I have successfully compiled TWRP for the new Galaxy Tab S3 however SuperSU complains it cannot find the boot image so it fails to patch.

The device is running Nougat, there is nothing special about the boot.img it uses the standard android magic and gzip.

I can patch the boot.img manually and obtain systemless root, so it seems SuperSU is able to create and mount su.img in /data.

As you can see from the recovery log below, the boot image patcher by jcadduono can find and unpack the boot image no problem.

However further on SuperSU fails to locate it.

Any idea what the issue is here, could it be related to the boot partition size? It's massive at 76mb, however the boot.img itself is only 16mb.

https://drive.google.com/file/d/0BwPAGUQCA8FDN2pGWV9HSmdYNDQ/view

I'd appreciate it if you wouldn't mind taking a quick peek.

Thanks.
[SuperSU] Chainfire:
You absolutely do not need to run both SuperSU and noverity/noforceencrypt patch. SuperSU has done this automatically I think since even before that patch was created :/

If SuperSU cannot find the boot image/partition, this log doesn't help. Let's start with the output of:

ls -laR /dev/block

from a (root) shell. Additionally, all the fstab files ( /*fstab* , /res/*fstab* , anything else you can find ) may be helpful. SuperSU doesn't really look at fstab that much, because certainly in the past it has not been reliable. It rather tries to find things on its own if possible.
[SuperSU] kelvs12:
does this work for the lg aristo ?
[SuperSU] Idebutterpiep:
I don't know what this messages mean??????????
[SuperSU] ashyx:
Actually the no-verity-opt-encrypt patch does need to run.

On some recent devices Samsung is no longer using the forceencrypt flag in the fstab.

Encryption seems to be forced by vold.

Attempting to disable forced encryption fails on these devices.

The no-verity-opt-encrypt patch above has been modified by myself as I have found a way to disable encryption being forced by vold.

It has successfully worked on these devices whereas your patch and the original no-verity-opt-encrypt doesn't work.

I can show examples of fstabs where neither patch works if you wish.

As for the other info you require I will have to come back with that as I don't own the device and will need my tester to supply it for me.