yashsingh1/xdaforums huggingface dataset:
[SuperSU] bdwilk:
Running great (as usual) on OPO bacon running official AICP 7.1.1
[SuperSU] morgoth6:
I give a try to SR3 on Nexus 6p with RR 7.1.1 r6 and as it seems to work I can see a loot of messages like pasted below in dmesg'u log:

--------

init: Starting service 'su_daemon'...

[ 163.591191] init: Untracked pid 10485 exited with status 1 [ 163.591558] init: Service 'su_daemon' (pid 10483) exited with status 0

[ 163.591591] init: Service 'su_daemon' (pid 10483) killing any children in process group

[ 168.598182] init: Starting service 'su_daemon'...

[ 168.646892] init: Service 'su_daemon' (pid 10487) exited with status 0 [ 168.646963] init: Service 'su_daemon' (pid 10487) killing any children in process group [ 168.647339] init: Untracked pid 10489 exited with status 1 [ 173.654564] init: Starting service 'su_daemon'...

[ 173.701565] init: Service 'su_daemon' (pid 10505) exited with status 0 [ 173.701633] init: Service 'su_daemon' (pid 10505) killing any children in process group

--------

I wonder is this normal? I remember similar reports in the past versions related to CM (RR ROM is CM based) , but was unable to find anything about possible reason and/or fix.
[SuperSU] xXx:
I'm using MM on OnePlus3 running OOS v3.2.8 + Boeffla kernel and 2.79 SR3 works without any issue now

Previously 2.79 SR1 + 2.79 SR2 did't provide root to any requesting app so I had to use 2.79 Stable so far.

thanks for the update and your effort to solve this. :good:
[SuperSU] yuri76:
after flashing this beta I can not flash a rom
[SuperSU] veez21:
You have to be more specific than that to help anyone
[SuperSU] Ch3vr0n:
Flashed about 25 minutes ago, no issues so far

Sent from my Nexus 6P with Tapatalk.
[SuperSU] TonikJDK:
All good on the Pixels.
[SuperSU] puhu:
Hello. Today I faced something about in my life once. Its called 'zygote64' asked for root permission. I denided it because I thought it can be malware. I googled it but no result for it. Pls help me what is that?

Im using Xiaomi Mi5

puHu
[SuperSU] bemagrp:
Zygote is the Init process on Android, it doesnt need root to do anything... it sounds like some malware is called like that.
[SuperSU] andreoide:
Samsung S5 sm-g901f kccat6 stock rom MM upgraded SU with TWRP, 279 SR3 working without any issue. Thank you Chainfire!

[emoji111]
[SuperSU] NLBeev:
You have a 64bit device,

On my Nexus 6 there is a zygote32.rc.

It's text file. Read it and see what it does.
[SuperSU] puhu:
I found only something about that and users said strongly its malware because real zygote never ask for permission it is impossible. Why zygote64 ask to me about permission? I did adb shell command: "ps | grep zygote" it showed 3 result about zygote. 2 zygote and 1 zygote64.

puHu
[SuperSU] Displax:
This problem is solved in SR3, thanks.
[SuperSU] KaMyKaSii:
Do you use the WhatsApp Extensions module? If so, the answer is there.

https://xdaforums.com/xposed/modules/mod-whatsapp-extensions-add-extra-t3452784/post70290016
[SuperSU] puhu:
No. İm not using whatsapp extentions. Just I updated supersu 2.79 sr3 after boot a few minute later zygote64 asked for root permission. I never install any apk or something unknown. What is the problem i dont know really but it makes me worry.

puHu
[SuperSU] skyhirules:
Still boot loop with SR3, as with the previous two, in stock Android 5.1.1 Xperia Z1 Compact.

Log pastebin link: http://pastebin.com/3k9Kd9NP
[SuperSU] naudmick:
Problem shealth S7 Android 7 nougat.

Knox problem
[SuperSU] NLBeev:
When you read the file zygote64.rc and it seems not changed you can compare it with another phone (same type; same rom).

When it's OK and still there is a permission question, you could try a malware scan app.

My idea: a factory reset.
[SuperSU] puhu:
[MENTION=631273]Chainfire[/MENTION]

What can i do? I scanned all my phone and just found "init.zygote32.rc" and "init.zygote64_32.rc" files. I checked them no problem in there I compare them with google sources they all same everything looking fine. But I cannot understand why "zygote64" asked for root permission? I didn't install any apk or another things. Just updated supersu 2.79 sr3 after boot zygote64 asked for root permission. Pls anybody help me? İm really worrying about it.

puHu
[SuperSU] Abhijeet Prasad:
Hi I am using redmi note 3g(mtk) running Resurrection Remix v5.7.4 MM I tried to install the supersu zip in systemless mode using twrp using terminal command as insalling normally was getting me system root but when I iam using terminal command to force systemless root fusing installation it says unable to unpack boot img and aborts... can help or suggestions???
[SuperSU] puhu:
I compared init.zygote32.rc and init.zygote64_32.rc files with google sources. Everything is same and looking fine no problem in there. I scanned avast and kaspersky too and no threats. İt scanned almost 15.000 files. I wanna make factory reset too but im using Android 7.0 nougat now and factory reset makes phone bricked and its really hard to get back. And İ just only one time saw zygote64 asking for root permission after update supersu and i denided it and not see again. Just one time.

puHu
[SuperSU] NLBeev:
OK, when you didn't install suspected apps; you may decide to ignore the permission issue and do a reboot every day to check if it happens again.
[SuperSU] glauberlima:
Moto X (2014) XT1097

Systemless mode as default flashing method reported working on Moto X (2014) XT1097 variant. :D

This is a very welcome improvement!

Thanks [MENTION=631273]Chainfire[/MENTION] !
[SuperSU] Licaon_Kter:
No joy on Xperia Z3 5.1.1, 2.79 working fine, yet SR1/2/3 bootloops.
[SuperSU] grep_i:
Yes but doesn't he has to delete it from the denied list first so the pop up will show whenever the zygote64 asks for root again or does he wants to scan the log files everyday for the denial of zygote64 ?
[SuperSU] Pkt_Lnt:
OT - ask in the Nexus 5 forum https://xdaforums.com/google-nexus-5
[SuperSU] NLBeev:
It's a personal thing, better is a factory reset.

He knows that already.

BTW the owner is the only one that knows about installed stuff and web surfing.
[SuperSU] Alxoom33:
SuperSu 279 SR3 working great on my Nexus 6 running Stock 7.1.1 Q, and on my Pixel C tablet also running latest 7.1.1.
[SuperSU] grep_i:
I don't see why it's better, but if you say so and he knows so than it's okay for him I guess and I wish him good luck with it.
[SuperSU] NLBeev:
OK, but it's not better because I say so[emoji1]

It's better because of the 'wipe everything from memory' and start fresh.

Unfortunately people can't reset their memory, but we can pretend a fresh start.[emoji85] [emoji86] [emoji87]
[SuperSU] white7561:
Are you Indonesian ?? :D
[SuperSU] doomscooter:
Yes, i am. How do you do ;)
[SuperSU] white7561:
i'm fine.. FYI i know your Indonesian because u have T*koped*a app installed :P
[SuperSU] Ja_som:
Guys, please use PM
[SuperSU] doomscooter:
Yes. Tia.
[SuperSU] jdegreef:
Great, 2.79 SR3 installs as systemless on Moto G4+ (Athene xt1642) stock 6.0.1 without the need of /data/.supersu.

BTW the translation of "Install SuperSu into /system" in French is misleading :

"Not (currently) available in system-less root mode"

is translated

"Non disponible sur les sytèmes avec un root limité"

It should rather be

"Non disponible (pour le moment) sur les sytèmes avec un root system-less"

"Indisponible" could be used instead of "Non disponible" to make the string shorter.

"(pour le moment)" could be removed to make the string shorter.
[SuperSU] PAPalinskie:
Systemless root seems to work on MT6580 5.0/6.0 phones. but, one question.

What partition will be patch when im flashing systemless root?
[SuperSU] mdn80:
SuperSU context

Hello.

I installed SuperSU v2.79 SR3 to device with Android 7.1.

"echo u:r:init:s0>/proc/self/attr/current" not work and su process is stopped after this command.

"su --context u:r:init:s0 -c my_command" not work(any my_command not executed).

Please add some way to get u:r:init:s0 context if it necessary in next releases.

Thank you.
[SuperSU] devil-kin:
Works fine on my OP3 running MM. Will upgrade to N and test again.

Edit: also works fine on Nougat.
[SuperSU] ruchern:
Wait. You're back on Stock? Why not Lineage?
[SuperSU] andreoide:
I'll send PM
[SuperSU] brotbuexe:
Does SuperSU flashing in TWRP needs a mounted /data partition?

I have a S7 and Nougat is around the corner but TWRP currently does not support the Samsung data encryption.

I don't want to run da decrypted /data and maybe the wait for an updated cfautoroot is too long.
[SuperSU] tag68:
On Lenovo Moto Z Play 1635-02 6.0.1 using this firmware but afterwards OTA to Patchlevel Nov 2016 flashing SuperSU 2.79SR3 gave an error (extracting ramdisk?). Copied the directory /cache/recovery to /storage/emulated/0/Download using TWRP to get the logs, but I can't enter this directory. Always get permission denied. How do I get access to the logs?

Edit: Got it, must use copy logs. Seems to be problem to create dirs on /su, read only? Do I need to give write access to system? Ah, TWRP chinese 3.0.2-0 includes some SU, can that be a problem?

Edit2: Please ignore last part of log when restoring boot again and flashing topjohnwu r2 also not working fine ;)
[SuperSU] jcmm11:
Use a root explorer. Get to the folder via /data/media/0

Change owner on directory, recursively, probably to media-rw. Just check owner and permissions of a regular directory to verify what you want to set it to.
[SuperSU] rogers11:
Flashed it on Nexus 4 with LineageOS 14.1. Working fine.
[SuperSU] marlborakis:
Sorry I am out of topic. How to Root s7 edge with nougat?

Στάλθηκε από το SM-G935F μου χρησιμοποιώντας Tapatalk
[SuperSU] Badger50:
Probably go to the S7 forum for starters.

Sent from me :)
[SuperSU] ulxerker:
gia sou file, edo einai: https://xdaforums.com/s7-edge
[SuperSU] Ch3vr0n:
Say what? This is an English only forum.

Sent from my Nexus 6P with Tapatalk.
[SuperSU] ashyx:
Considering zygote is a system process, how is a factory reset going to solve anything except wipe user data?
[SuperSU] puhu:
Zygote64 asked me for root permission only one time and I didn't give it access. I denided it. And never asked again. I checked supersu app there is no log about zygote64. I didn't install any suspected apps or anything. Just I got problem about supersu before zygote64 ask me. Supersu icon gone and it didn't response for pop up window so I flashed "Unsu.zip" and flashed supersu 2.79 sr3 and booted. After boot succesfully in a few minute later zygote64 asked for root permission.

puHu
[SuperSU] Chainfire:
There is a case where an internal crash of zygote(64) will attempt to create log files as root. This is a left-over from Android development and really shouldn't be in production builds, but it often is. It is impossible to know if that is the cause, though.
[SuperSU] BartVCD:
[MENTION=631273]Chainfire[/MENTION]

can you say something about galaxy S7 / S7 Edge with nougat and root?
[SuperSU] puhu:
Sorry my English is not good. I Translated and cant understand anything well. Its normal? I mean zygote can ask for root permission some time? Pls help me ı really obsessed with it. [emoji17]

puHu
[SuperSU] Chainfire:
something about galaxy S7 / S7 Edge with nougat and root
[SuperSU] Chainfire:
Get the output of 'ps' and 'ps -Z' WHILE the popup is on-screen. That may give a clue. Otherwise, we can't know.
[SuperSU] puhu:
Aww as I said only 1 time zygote asked for root permission after I updated supersu 2.79 sr3 and i denided. I checked supersu logs and there is no log about zygote accessed or denided, nothing about zygote.

I did "ps|grep zygote" command in adb shell. İt give me 3 result. Can you look at please I can take photo and upload here.

puHu
[SuperSU] BartVCD:
I mean it is not possible to get root with SR3 2.79, after flashing with TWRP 3.0.2.4 its not possible to boot into the system.
[SuperSU] puhu:
View attachment 4007886View attachment 4007887

[MENTION=631273]Chainfire[/MENTION]

I got these.

puHu
[SuperSU] Chainfire:
Unless the popup is on the screen at the same time, this does not help.
[SuperSU] puhu:
[MENTION=631273]Chainfire[/MENTION]

And this.

View attachment 4007966

puHu
[SuperSU] Chainfire:
I have not tested it yet...
[SuperSU] Wolfcity:
What [MENTION=631273]Chainfire[/MENTION] ment was to log when the pop up is on screen. As zygote only asked one time for permissions you can only wait if it happens again. A friend of mine had the same thing, one time zygote asking for root permissions.

Maybe it's just the left-over of development, the ROM my friend is using is not that new.

As I didn't know if some malware was involved and tried to "hijack" a system process I did a complete clean install on my friends phone. It's up to you to leave everything as it is as you denied root permissions or wipe everything.
[SuperSU] puhu:
I wanna wipe everything but Im using Xiaomi Mi5 Android 7.0 and manually wipe system was bricked phones. And really hard get back. I really dont know what can i do.

Zygote asked for root permission 3 days ago and gone. Just one time. İm really obsessed it.

puHu
[SuperSU] mielletseed:
Could you please stop that zygote thing? Please! I googled quickly and you are not the only one. It happened just one and you did not grant the permission... chainfire explained to you that this could be a developer code while zygote process was crashing

so please, stop here :)
[SuperSU] NLBeev:
There has been a suggestion in the thread that is wasn't a system process but a virus. Because 'zygote system' is a init process and asking for root access isn't normal.

In case of doubt.....etc
[SuperSU] puhu:
I Swear I really wanna stop it but no I cant. ? zygote thing in my head and Im really worrying about that because im using financial apps, private things etc..

puHu

---------- Post added at 06:30 PM ---------- Previous post was at 06:29 PM ----------

What is your advice? What can I do?

puHu
[SuperSU] BartVCD:
Maybe Erdogan is watching you :D
[SuperSU] smitharro:
Yeah, he already locked up many teachers... [emoji15] But this is not a political forum about high testosteron scumbags like Erdogan, Putin and Trump. We're talking about Android here...

Send from my XT1642, with LineageOS OMS, using Tapatalk
[SuperSU] nathanchance:
No offense but if you are concerned about your privacy and security, you probably shouldn't be rooted...

I think this discussion has been run into the ground; Chainfire gave you an answer that was sound and reasonable, you can choose to accept or reject it but it's time to move the thread along.
[SuperSU] NLBeev:
When you read the thread carefully you could stop worrying. Because you're not the only one with this zygote thing.

But the virus response makes it difficult for you.

When you have standard apps and you're are a decent user and your phone functions 'normal' you can live with it, until you flash another ROM.

Q: what can I do?

A: make backups.

Many users with custom Roms need to wipe and reset from time to time, because of issues after flashing a new ROM.

Apps can be restored by Google.

Your data must be restored by yourself.

Make a copy of your data to a pc or the cloud.

There are apps that will make automatically backups.

Hopefully you can stop worrying.
[SuperSU] puhu:
Thanks to you. Ill try to clean all my phone.

puHu
[SuperSU] jdegreef:
That's a good one, couldn't resist even if it's OT :D

---------- Post added at 18:48 ---------- Previous post was at 18:36 ----------

Despite answers that would have satisfied me and your knowledge of what you've installed on your phone I have the feeling you worry too much.

But if that will reassure you clean your phone.

I'm just wondering what you'll do if zygote crashes again and ask for root to save its log ?

I this case don't deny root, keep that window open and do what Chainfire told you in a previous post.
[SuperSU] ulxerker:
ATOMROFL xD
[SuperSU] puhu:
I really hate that zygote thing really [emoji23] But I really obsessed it. İm thinking that ill clean all my phone and zygote will ask again OMG. [emoji33] So actually Im scarying about clean too because I wanna wipe everything. But it made bricked alot of Xiaomi Mi5 on Android 7.0 and Im using writed imei too Maybe ill lost imei too so that's why I obsessed zygote too much.

puHu
[SuperSU] Raven_999:
C'mon dude, you've been asked once to cut this "zygote" talk.

Two pages about your probably not to worry about issue. Even OP told u it must be a code leftover. Let's keep this thread clean and to the point. If you have such important apps and data, why do u even unlock bootloader and root. No offence man, but i think we've had enough. Back all up, do the wipes and start clean
[SuperSU] 200:
2.79 SR3 working flawlessly on OP3 4.0.2 F2FS. :)
[SuperSU] Chainfire:
Or running Android.
[SuperSU] Chainfire:
SuperSU vs Samsung Galaxy S7 Official Nougat (DPLT)

I'm not entirely sure what is going on here yet. I've had the stock firmware randomly stop booting even without modifying the boot image (rooting). Others have also reported that just flashing TWRP may trigger a bootloop (which is weird). I have some ideas what the cause may be, but it will be some time before I can properly investigate them.

The only way I seem to reliably get both TWRP and SuperSU working right now is:

- Flash TWRP (3.0.2-5) to recovery

- Immediately boot into TWRP

- If you were encrypted, format /data (ext4) and reboot into TWRP again

- Flash SuperSU v2.79-SR3 in TWRP

- Reboot into Android

The first boot will take a while if you performed that format, but for me it ultimately completes. Note that your device will be running unencrypted at this point!

Of course, if you format /data, you will lose all your data (including contents of internal storage!). Before I flashed the new version, I used FlashFire v0.54-PRE to create a backup of /data and internal storage to the removable sdcard, and restore that backup after flashing DPLT, rooting, and reinstalling FlashFire. This worked fine for me, and all my settings - including fingerprints and system settings - transferred fine. I came from the first Nougat beta, but I've seen others reporting success doing the same thing coming from Marshmallow. As always, your mileage may vary.

Unfortunately, due to this boot-loop issue with DPLT and encrypted data, it is also impossible to use FlashFire to upgrade the firmware itself to DPLT while keeping root if you started with an encrypted device.

I am not sure if the same difficulties exist with other official builds than DPLT, nor if the same problems occur with any of the custom ROMs based on DPLT. The S7 is my daily driver so I don't like to experiment with it too much :)
[SuperSU] kasi5471:
For me 2.79 SR3 Work with TWRP 3.0.2-4 on the S7 G930F Nougat - Beta ZPKK without Problems...next days i will Test it on my Official DPLT Rom

Thx Chainfire, for the best Root ever
[SuperSU] calaiou:
Hello and sorry my english , i instaled oficial nougat DPLT of sammobil in my s7flat, i flash su79 stable and i have no caméra, do you now if su79.sr3 work well? sorry and much respect for all
[SuperSU] starbucks2010:
I'm on sr3 but I cannot make my File Manager get root access to System files. In su UI is listed as granted but I cannot do anything on System files. Do you have any idea how can I Solve this issue. I'm on S7 edge with latest Nougat DPLT deodex.

Thank you for any idea.
[SuperSU] jdegreef:
Or even have a turned on phone in your pocket.

---------- Post added at 13:48 ---------- Previous post was at 13:39 ----------

Did you try with another file manager ? I use Total Commander with root enabled without problem.
[SuperSU] starbucks2010:
But it was working fine yesterday when I was on MM. I even tried a different kernel but no joy. With es file exp it seems to work.
[SuperSU] jcmm11:
It's due to the way the mount command in toybox is working at the moment. Some (most?) file explorers have adapted. I use x-plore and it works. To see what I'm talking about start a terminal emulator and, as root, try the following commands (you can replace rw with ro depending on current state). Only the last will work.

mount -w -o remount /system
mount -o remount,rw /system
mount -o rw,remount /system
[SuperSU] brotbuexe:
Did you try to reencrpyt after the flashfire restore inside 7.0 yet? I tried it once before and it seems to have not done it. Still have encrypt device as an option in settings.
[SuperSU] starbucks2010:
Actually, none of them is working.
[SuperSU] DasXardas:
Hi please I tried to flash latest SuperSU via CF-Autoroot (CF-Auto-Root-chagalllte-chagallltexx-smt805.tar.md5) on my T805 (Galaxy Tab S 10.5 chagallte) but after flash I stuck on "recovery not seandroid enforcing" message. Can you help me or update the package? I have this official stock samsung rom: T805XXU1CPL1_T805OXX1CPK1_T805XXU1CPH5_HOME.tar thank you.
[SuperSU] osm0sis:
Might also need -t auto
[SuperSU] jcmm11:
Hmm, I haven't needed that. At least not so far. In any case I wish toybox would just fix it.
[SuperSU] grep_i:
Why don't you use BusyBox GNU(more functionality and compatibility) instead of toybox BSD?
[SuperSU] Aroly7:
[MENTION=631273]Chainfire[/MENTION]

Hi I have Huawei honor 7 with android 6.0 after flashing zip with twrp I have ended in bootloop.

Now had to jde backup. So I ONLY want to say plk-l01c432b370 have problem to boot but v2.62 works.

Aroly7
[SuperSU] jcmm11:
I have BusyBox installed. Toybox is the default on Android and is what's found in /system/bin. If I could change the PATH order I would, but I haven't found a way to do that that sticks. BusyBox mount works just fine.
[SuperSU] chhapil:
Bootloop on miui nougat builds. Although 2.79 boots fine, but there is lot of stuttering.
[SuperSU] Strephon Alkhalikoi:
A little more detail please. Are you saying that your device gets stuck trying to enter recovery to root?
[SuperSU] jdegreef:
Why don't you just flash the supersu zip from TWRP skipping the use of CF-Autoroot ?
[SuperSU] DasXardas:
It gets stuck after flash. I flash the CF-autoroot, odin shows that the flash was successfull and after reboot It shows the message.
[SuperSU] mielletseed:
might be the wrong way you are going - cf-autoroot is for users that don't want to use a custom recovery and therefore comes bundled with a stock recovery. Maybe that stock recovery is to old and not supported by your updated bootloader anymore. But that's not really relevant since your post is off topic in this thread because this thread is for SuperSU beta versions and there are no cf-autoroot beta versions ...
[SuperSU] DasXardas:
Because If I try to flash TWRP, so I get the same error. I tried to flash CF and TWRP without restart, disconnect battery, and boot into recovery but I got the same error
[SuperSU] Elanza_48:
Sir,

I had a question, i,e. The systemless method creates an extra su partition of 100 mb so my question is in order to do so space of which partition is deduced ?
[SuperSU] gothicVI:
/data as far as I know.

Gesendet von meinem Moto G 2014 LTE mit Tapatalk
[SuperSU] ulxerker:
correct.
[SuperSU] jdegreef:
So your problem is flashing TWRP ? Ask the question in your device TWRP thread or in CF thread. It's not related to Supersu, especially the beta version.
[SuperSU] DasXardas:
My problem is, that If I try flash TWRP or CF, so I get the same error. I put the ask into both threads to TWRP and CF.
[SuperSU] mielletseed:
maybe you should flash stock recovery after flashing cf auto root

then you are rooted and have accepted recovery again

but maybe you better ask in your device's forum...
[SuperSU] Licaon_Kter:
[MENTION=631273]Chainfire[/MENTION] Anything we can do/provide to track the bootloop on Xperia 5.1.1 ?
[SuperSU] jwchips:
SR3 works fine for me on my Mi5 running 7.1.12 global. FlashFire however is a different story....
[SuperSU] chhapil:
Not sure what could be an issue. I'm on global beta 7.1.19.

Non rooted works just fine but after flashing supersu it starts stuttering
[SuperSU] thorium666:
Hi,

i've tried this binary on a S7 Nougat (Encrypted/SD Card is mountd as internal sorage) using adb and it ended in a >20min loop, so no success.
[SuperSU] ulxerker:
why adb? try to flash it in twrp, supersu is supposed to work on a S7.