yashsingh1/xdaforums huggingface dataset:
[SuperSU] jcmm11:
If I had to guess I'd say that somehow /system is mounted rw and the hosts file is being updated directly rather than systemlessly.

What's the output of the following commands, as root, from a terminal emulator.

mount | grep /system

ls -l /system/etc/hosts
[SuperSU] snovvman:
"mount | grep /system" returns:

/dev/block/sda34 on /system_root type ext4 (ro,seclabel,noatime,data=ordered)

/dev/block/sda34 on /system type ext4 (ro,seclabel,noatime,data=ordered)

"ls -l /system/etc/hosts" returns:

-rw-r--r-- 1 root root 1783095 [date/time] /system/etc/hosts

I was wondering the same, but Safety Net is passing (for now), ever after time and reboots.

Thank you.
[SuperSU] jcmm11:
Should be a number between root root and [date/time]. Results aren't what I expected so far so this may be relevant.

Safety Net passing isn't surprising if suhide is installed and working correctly.
[SuperSU] mobileman88:
The secret sauce was wiping data for Play app for me. Thanks!
[SuperSU] snovvman:
I edited my post and it is also quoted here. What does that number mean?

I thought that for Safety Net to pass, the /system partition cannot be altered. I therefore wondered that if Adaway was writing to /system, why SN would pass.

Thanks again.
[SuperSU] Lunoru:
Thank you, I did manage to gain root access with Kingo root, thanks to your links, but the Superuser application of that is simply ridiculously, stupidly annoying. So I am currently trying to find a way to overwrite it with Supersu, problem is, that Supersu thinks that the SU binary is occupied and won't work with it. Trying to find a way around it currently
[SuperSU] Ch3vr0n:
[MENTION=7464691]Lunoru[/MENTION] Search XDA for SuperSUme. That's a flashable zip that will do just that.

Sent from my Nexus 6P with Tapatalk
[SuperSU] jcmm11:
I am stumped. That number is file size in bytes. So somehow hosts is being updated even though system is mounted read only. I also see no indication of a bind mount for hosts.

If you weren't running suhide (or Magisk) your supposition about SN would be correct. But they both prevent SN from noticing any /system alterations.

One more experiment. From the terminal emulator, as root, what happens if you run

echo "127.0.0.1 localhost" >/system/etc/hosts

(without trying to remount system as rw)

Also I assume that in Adaway's preferences 'Target host file' is still set to /system/etc/hosts

---------- Post added at 11:33 AM ---------- Previous post was at 11:31 AM ----------

Edit: should probably move this discussion to the Adaway thread. Somebody there may have more insight. (Well it was supposed to be an edit. I need coffee ? )
[SuperSU] snovvman:
"can't create /system/etc/hosts: Read-only file system".

Yes, the Adaway Target hosts file is set to /system/etc/hosts.

Adaway currently shows "Enabled" with a green check mark. I ran an app that is know to throw up ads, there is no ad.

Re moving, perhaps that is a good idea. Relatedly, before I made my initial post, I searched over at the Adaway thread. I didn't come up with anything.

Thank you.

Edit--I was running Magisk on 7.x and Adway in systemless. When I flashed 8, I used SuperSU, suhide. Magisk manager is still installed and, as far as I know, not doing anything.
[SuperSU] Lunoru:
Thank you, but it only fixes it if it's "King root" It does not work for "Kingo root" root. Yes I tried to root it using King root, no luck :(
[SuperSU] Dave_247:
My Xperia X gets stuck in an endless bootloop if I try flashing 2.8.2 SR3 with systemless SBIN mode using the aroma configurator, and changing nothing but the install method. I'm running the stock Sony firmware 34.3.A.0.194 with the Vodaphone AU carrier, which is Android 7.1.1. I have also used ta_poc to patch my bootloader and disable Sony RIC before installing SuperSU as otherwise it would fail to install.

I am able to root and boot successfully in regular systemless mode however with no issues however.

Attached my kernel crash log after over 5 consecutive reboots.
[SuperSU] Ch3vr0n:
Contact the dev or do some more searching on XDA. Maybe the dev can update it for kingo root (i thought that was the same as kingroot). But in the end kingo root is better than NO root at all ;)
[SuperSU] snovvman:
Does this mean that I can modify the build.prop (e.g., for tethering) and suhide will still allow SN to pass? I ask because I always thought that although Magisk hides root, it does not prevent SN from detecting /system modification. Does the SuperSU/suhide combo provide for hiding /system mods? Thanks.
[SuperSU] Lunoru:
After doing a lot of reading and accidentally blacking out from the amount of ice cream I've ate. I've figured out how to install root with "King root" (hell painful) and then thanks to your suggestion, I was able to use Supersume (or how was it named) to turn that into Supersu. After a few fails, finally it's all working rather fine with no problems. So, I dearly thank you ^^
[SuperSU] DB126:
Maybe - KingORoot is borderline malware with questionable add-ons that are resist removal. Depends on your level of tolerance and skill at decrapifying system. Not a big deal if ultimate goal is a full wipe in preparation for a different ROM or stock reload.
[SuperSU] Ch3vr0n:
Glad I could help. Welcome to the SuperSU world!

Sent from my Nexus 6P with Tapatalk
[SuperSU] zhangbo5891001:
Is anyone successed to root android oreo on Pixel devices?

I flash SuperSuv2.82 SR3 with twrp3.1 on my pixel for android oreo, the phone stucked on the splash screen(a letter 'G')

Is anyone successed on pixel devices? any suggestion, i will be grateful

factory image: sailfish-opr6.170623.012-factory-8ada9373.zip
[SuperSU] liam_davenport:
Working fine here on Pixel XL guessing the steps are the same but I'm also using ElementalX kernel

All I did was boot the img, Flash ElementalX, Flash SuperSU, Reboot
[SuperSU] santhu05:
Hi

I am using samsung A710-FD

I followed the instructions in the thread and was able to root successfully using TWRP 3.0.2.1 and installed SU (SR3-SuperSU-v2.82-SR3-20170813133244).

But now the pattern lock is sluggish. It takes 2-3 seconds after the correct pattern is inserted.

Any trick to solve this..

Help ,much appreciated..Thanks
[SuperSU] zhangbo5891001:
Thanks, what is ElementalX kernel ? it seems to be a customed kernel

supersu 2.82 is working fine with andorid 7.1.2 on my Pixel.

I just want it to working on Oreo...
[SuperSU] gverma1:
Check out the steps in this post. This also has the steps to install SuHide to hide your root status from apps that wont work on a rooted device (like AndroidPay, Snapchat, PokemonGo, etc.). Btw, I have a Pixel XL. https://xdaforums.com/apps/supersu/suhide-lite-t3653855/post73550490#post73550490
[SuperSU] toknitup420:
I'm confused. Where are you trying to flash supersu. Supersu doesn't flash in bootloader unless you're using boot to root boot image. If you're using the zip then you need to boot twrp first.
[SuperSU] zhangbo5891001:
Thanks.

yes, my steps are almost same to that in the post except no flashing SuHide. but it just don't work....

Are your Pixel XL using the factory image sailfish-opr6.170623.012-factory-8ada9373.zip ?
[SuperSU] jcmm11:
Modify buildprop - probably. I'm not sure what the limits are. Have you tried setprop instead of physically modifying buildprop? I actually do try to minimize my system changes but it's still heavily modified since I replace system apps rather than just updating them. I also have A.R.I.S.E. installed, which modifies a lot of system. But I also use bind mounts for things like font changes and some config files.

A bind mount for buildprop probably won't work since I think buildprop is accessed too early in the boot process.

I haven't actually used Magisk so my comments on that may well be off.
[SuperSU] snovvman:
I have not. I have never come across setprop. A few minutes of research suggests that it is an overlay/override of build.prop entries and can be run as a script on boot. I will do some more research and give that a try. If setprop works to enable tethering without build.prop modification, it is a more elegant solution. I'll need to ensure that any setprop script runs after SuperSu runs on boot.
[SuperSU] jcmm11:
You would just put the script into su.d

Format is simple

setprop net.tethering.noprovisioning true

note the lack of an equals sign. Setprop will not override a setting that's already coded into buildprop. To test if it will work you can issue the command in a terminal emulator (as root) followed by a getprop to see if it took.
[SuperSU] gverma1:
I am using the marlin build, because Pixel XL! But that should not matter as method for sailfish (regular Pixel) and marlin (Pixel XL) is the same.
[SuperSU] snovvman:
Thank you. Before I read your post, I did some reading/testing and ended up putting it into Automate (graphical Tasker-ish app) to run on launch (with a short delay after seeing the "boot complete" broadcast). It is working like a charm. Great solution. Thank you very much for illuminating the existence of setprop.
[SuperSU] polykoma:
Hi

I unlocked BL on X performance. Upgraded to F8132_39.2.A.0.442_R2C_Thailand Generic_1304-6595

Then fastboot TWRP.

Boot into TWRP.

Install SU v79 -> works fine

Install v82 R3 -> reboot

Show yellow exclamation mark on start ->

Then RED Exclamation mark. Your Device is corrupted. Press Power. Then Dead.
[SuperSU] avijwr:
plzz solve this

https://xdaforums.com/general/help/problem-supersu-cm13-t3664668
[SuperSU] bonny_k-9:
Hi, on my n6p smartphone is 82SR3, which is installed on android 8.

Terminal commands do not work correctly.

in terminal:

angler: / $ su

Angler: / # script -q -c 'getevent -q / dev / input / event0' / dev / null | while read code1 code2 code3; Do echo "$ code1 $ code2 $ code3"; done

Usage: getevent [-t] [-n] [-s switchmask] [-S] [-v [mask]] [-d] [-p] [-i] [-l] [-q] [-c] Count] [-r] [device]

-t: show time stamps

-n: do not print newlines

-s: print switch states for this bits

-S: print all states

-v: verbosity mask (errs = 1, dev = 2, name = 4, info = 8, vers = 16, pos. events = 32, props = 64)

-d: show HID descriptor, if available

-p: show possible events (errs, dev, name, pos. Events)

-i: show all device info and possible events

-l: label event types and names in plain text

-q: quiet (clear verbosity mask)

-c: print given number of events then exit

-r: print rate events are received

angler: / #

I was told the following:

"It looks like your su version has problems with executing commands, which can be obtained only if the argument /dev /null is the argument to getevent, not script." So, put the getevent -q /dev/input/event0 construct into a file, specify the file argument to -c. What's going on?"

On my tablet on android 7 and supersu 82 (stable) code is executed normally. Then I decided to install 82 stable version on n6p 8 android. The terminal can not receive the root at all. SU simply does not open the grant window. In the supersu manager, there is no terminal in the application list, and the terminal is displayed in red in the logs.

It does not even show all the "ps" processes. There are only two processes, sush and ps. Definitely, something with su is not so.

Why is the new version not working properly with commands for the terminal? Thx.
[SuperSU] jcmm11:
Where is busybox installed and what version? script is a busybox command (at least in Nougat it doesn't exist in /system/bin). On my Nexus 5X, with SuperSU 2.82 SR3 in sbin mode terminal commands work fine (albeit not running Oreo yet), so this isn't inherently a SuperSU problem - there's something else going on.
[SuperSU] Alxoom33:
Read the OP. BusyBox 1.26.2 installed in/sbin/supersu/xbin[emoji3]
[SuperSU] bonny_k-9:
And the fact that the terminal can not get all the processes with the ps command does not bother you, right?

I put the busybox from here,

https://xdaforums.com/android/software-hacking/tool-busybox-flashable-archs-t3348543?nocache=1 1.27.1

since Programs can not install it on android 8

The script command is just working. su incorrectly takes arguments, apparently.
[SuperSU] jcmm11:
My ps, when run as root, works fine. Like I said something else is going on. That busybox should work ok. It probably installed to /vendor/bin since it hasn't yet been updated for the new SuperSU paths and Oreo dropped /system/xbin (I prefer osm0sis' version myself)

The only thing I can suggest at the moment, and I have no idea if it will help or not, is to do a wipe and clean install. Beyond that I suspect that logs would be helpful.
[SuperSU] osm0sis:
Are all those spaces supposed to be there? Shouldn't it be /dev/input/event0 and /dev/null? Might explain getevent throwing an error.

Edit: also $code1 not $ code1
[SuperSU] bonny_k-9:
This code works perfectly on my tablet with firmware 7, SuperSU 82 stable and busybox. It's true there busybox Was installed from an application from Google Play. Now these applications can not install it on Oreo.

And with the code, everything is fine, there simply when copying here the forum.
[SuperSU] corkiejp:
Only Stericson Pro app has not been update to install to correct path.

There is alternatives meefik, [MENTION=4544860]osm0sis[/MENTION] [Thread] and JRummy's all are able to install busybox to the correct path!
[SuperSU] Alxoom33:
I can confirm. Have used meefik, JRummy (for Android 7.1.1 not 8.0) and [MENTION=1143630]osmosis[/MENTION] installer's to install Busybox with SuperSU 2.82 SR3. Stericson has not yet been updated.
[SuperSU] bonny_k-9:
https://play.google.com/store/apps/details?id=com.jrummy.busybox.installer&hl=en - Crashes when load!

https://play.google.com/store/apps/details?id=ru.meefik.busybox&hl=en&rdid=ru.meefik.busybox :

### BEGIN INSTALL

Remounting /system to rw ... done

Copying busybox to /system/xbin ... fail

Setting permissions ... fail

Removing old applets ... done

Installing new applets ... fail

Remounting /system to ro ... done

### END

Android O
[SuperSU] corkiejp:
Try the recommend path suggested by ChainFire!

You need to edit the install path in settings of the Meefik app.
[SuperSU] bonny_k-9:
Indeed, the script has earned. Thank you.

The ps command still displays two process.

Installed using https://play.google.com/store/apps/details?id=ru.meefik.busybox&hl=en&rdid=ru.meefik.busybox сhanged the way
[SuperSU] jcmm11:
What happens if you run

busybox ps
[SuperSU] bonny_k-9:
You tell me what happened to the built-in ps command? It works for some reason, no su.
[SuperSU] minio.cz:
Sideloaded SuperSU 2.82 SR3 on honor 9 (firmware STF-L09C432B120). So far It works great without any problems.
[SuperSU] dunjamon:
Is anyone having issues with the beta and Oreo? On my Nexus 6P it causes random reboots. I've installed the stable release and it looks to be OK for now. I was under the impression the stable release would not work with Oreo.
[SuperSU] Alxoom33:
Works flawesly on my Pixel C.[emoji3]
[SuperSU] badhabit_wb:
No problems at all on my Pixel after I wiped and reinstalled.
[SuperSU] jcsww:
Running perfectly fine on my Nexus 6 and Nexus 6P. Both run stock though. The 6 is still on Marshmallow butt the 6P is on the Oreo preview
[SuperSU] dunjamon:
Strange. I flashed the beta and had reboots all day yesterday. Switched to stable this morning and it's been working OK all day. Might stick with it for now.
[SuperSU] jcsww:
Perhaps the reboots were caused by another app? I don't run busybox and most other things. Basically stock with suhide.
[SuperSU] dunjamon:
Same as me. I flashed full stock, nothing more. I thought it might have been a custom kernel, so flashed stock again, but it still did the same thing. It's been OK on the stable release so far, so will see how it goes for a couple of days.
[SuperSU] Alxoom33:
Sounds like you might have a bad dl. Try dl your Oreo Factory image and reflash. What we're you running before 8.0?
[SuperSU] dunjamon:
I had stock N with Franco. I've reflashed again this evening so will see how it goes.
[SuperSU] Alxoom33:
Good luck!
[SuperSU] avijwr:
run ur device in safe mode... by resrarting phone with volumedown button... keep pressing it only... and then find is this prblm due to apps or hardware ..
[SuperSU] mobileman88:
Check the hash of the download. It was corrupted before for me and caused such issues
[SuperSU] Vinnom:
I have a Huawei Nova device, Emui 4.1 (Android 6.0.1). I tried a lot of superSU before, none could even finish the script, always ended before patching the boot image. For the time being, as a root solution, I was using phh's superuser, but I'd rather use superSU.

Today, I tried superSU (SR3-SuperSU-v2.82-SR3-20170813133244.zip) and everything went fine, the script finished fine.

The device booted, but no su. I try to start superSU app, it gives me the message that supersu is not detected.

What logs should I provide? And how (at boot, opening an root app...)?
[SuperSU] Ibuprophen:
It looks like there's few open ended places that I feel that really should be clarified.

According to my understanding of what you stated...

After some unsuccessful attempts when trying to flash the SuperSU, you had, in a way, given up at some point in time and then you were successful in flashing the Superuser by Phh.

Okay... As a, personal preference of yours, you then gave SuperSU another try and it successfully flashed.

Then after you had successfully flashed SuperSU, you had rebooted your device and, after it was booted up, you could not locate the SuperSU icon inside your app drawer.

Assuming that I'm correct (thus far)... It may be just me but, i am seeing some gaps in this (possibility inadvertent) and I am hoping that you could do a bit of clarifying.

How did you go about with the installation (Was it TWRP, CWM, FlashFire, etc...)?

You had mentioned installing the Superuser from Phh but, you didn't mention removing it prior to the successful installation of SuperSU. Did you remove the Superuser from Phh first?

When it comes to obtaining logs reflecting this issue, personally, i feel that it all depends on the answers above.

The way you had attempted/successfully installed any of them depends on how it was delivered.

For example, if this all happened in TWRP, then there's a place to copy the logs reflecting the attempts. This goes for CWM, FlashFire, etc... since the different ways reflects the different ways/locations where the logs are located.

If there's another member who may be much better versed with SuperSU that can Correct, elaborate, add, remove, etc... or just plain state that "Ibuprophen doesn't know what he's doing so this is what you need to do..." LOL!

Thank you! :)

~~~~~~~~~~~~~~~

I Am The Egg Man,

They Are The Egg Men.

I Am The Walrus!

Coo Coo Cachoo!

I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.

PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
[SuperSU] Vinnom:
Hi! You're right, I need to describe better.

I've been testing superSU in my Huawei nova since I got it and none of the releases was able finish installing, except for the latest release.

I used osmose's unsu script and flashed my original boot image so I could get rid of phh's superuser.

After I successfully flashed latest superSU and booted, I did found the superSU app, but it claims that no root was found. In fact, I tried to open Titanium Backup (which verifies su existence every time we start it) and the superSU dialog pops up, I gave it su permission, but the app can't pass beyond it, because it can't su binary, I think.

About the recovery.log, if it needed, I can do all the steps again. I just need to know what other logs are needed and the right moment to get them. [emoji1]

Enviado de meu HUAWEI CAN usando Tapatalk
[SuperSU] Ibuprophen:
My apologies but I've got another clarification i need to help me better understand...

Your second explanation is much better but, is there anywhere (1 or more) within all of the steps taken that you had started from scratch?

It looks like you had went from one to another, to another, etc... and, if that was the case, then I'm not at all surprised with your current outcome but, this is why I am asking for these further clarifications to prevent any assumptions.

Also as an FYI... I had asked for some of the experts in the SuperSU Stable thread if they could pop in this thread to see if they could help with additional assistance for you.

Thank you! :)

~~~~~~~~~~~~~~~

I Am The Egg Man,

They Are The Egg Men.

I Am The Walrus!

Coo Coo Cachoo!

I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.

PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
[SuperSU] Vinnom:
I already had to flash my phone anew (flash system.img, boot.img in fastboot).

When I did this, I tried superSU, but in the occasion, the script failed and didn't finish.

Now, everytime I want to try other su solution, I flash via twrp the osmose's unSU.zip and flash original boot.img which in my understanding should leave me a clear environment without root.

One more thing I forgot to add before and maybe cause some troubles in the installation too (even can be the culprit), is that my data is encrypted by default. If I try to wipe data, so I get an unencrypted data partition, my phone doesn't boot anymore. I say this because the twrp for my device can't mount data partition, the dev who build it, couldn't decrypt it data in twrp :/

Enviado de meu HUAWEI CAN usando Tapatalk
[SuperSU] corkiejp:
[MENTION=4828250]Ibuprophen[/MENTION]

Just because the script finished, it still looks like your device was not rooted!

You had a working root with Phh's superuser, maybe hopefully you can return to that?

It is the recommend method in this thread for your device.

By having a quick look around your device forums, it seems that other people have had problems trying to root the device. Maybe try asking there if anyone has rooted successfully with supersu.

It seems that supersu is not compatible with your device. Maybe share the TWRP log after you used it to flash supersu (google how to capture the log, after flash go back into advance options and choose "copy Log" or something like that.)

Edit: - Just noticed you have no access to data partition which will make getting logs complicated (maybe by adb you could do it)
[SuperSU] Vinnom:
I returned to phh's superuser (in fact, I tried magisk - i wanted to test if it works amd works) and I have root now.

About my device forums, I participate frequently. For now, it seems that superSU didn't work for no one, only phh's. Magisk is working too, but I just found out today.

About the recovery log, maybe via adb, maybe putting it to micro sd. Later, I'll try again.

Thanks, folks :)

Enviado de meu HUAWEI CAN usando Tapatalk
[SuperSU] Ibuprophen:
Thank you [MENTION=4868912]corkiejp[/MENTION] for chiming in but, you had accidentally did a "call-out" to me when this was an issue that [MENTION=4699730]Vinnom[/MENTION] was requiring assistance with.

LMAO! :)

I apologize if I had caused any confusions with this.

~~~~~~~~~~~~~~~

I Am The Egg Man,

They Are The Egg Men.

I Am The Walrus!

Coo Coo Cachoo!

I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.

PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
[SuperSU] xflowy:
hey guys! somehow the workaround via unroot in supersu settings (then restart, then login again) does not work for me to get snapchat to login. any ideas, what i could do? I'm on dirty unicorns 11.7 on a nexus 6p.

thanks much!
[SuperSU] rickysidhu_:
Dirty flash your ROM
[SuperSU] srqrob:
Am I correct that v2.82 SR3 at present includes the code fixes that were in the Pixel Fix release as well as the check for a VBS and if existing, it signs the bootloader as a final step? I can't imagine that Google would roll out a signed boot only to abandon it as they have apparently done now. I'd wager it'll be back.
[SuperSU] Vinnom:
The recovery log is attached.

From what I can tell from reading it, the problem is that my data partition isn't mounted and because of that, the script can't work properly.

As my boot image got patched (or at least the script ended this part of the process) there is a way to make this work after booting my device (for example, copy the su folder where it should be)?
[SuperSU] core720:
[MENTION=631273]Chainfire[/MENTION]

Moto Z2 Play dont work...

LOG...