yashsingh1/xdaforums huggingface dataset:
[SuperSU] Thisguy129:
I was referring to the Chinese company he sold it to not him I don't think I need to explain to you anyway first off do you speak English native. Because your the one that should have stopped and not said anything it's funny chainfire is my idol for this Android stuff I seen that name everywhere learning about it so I looked on YouTube for a video to see a face with the name finally someone that's young Clean cut and motivated​for rooting I jumped on the bandwagon I started 3 months ago and it seems there alot of problems going on Samsung is enforcing kernel hard. There's no Xposed for nougat it's also terrible battery life YouTube background is I think about over because even mm with no play services or store installed is changing my YouTube some how I have different ui I am sad that all the rooms for Moto g4 are damn near the same I can't tell any difference. I thought roms would be like a new system just cool features like wifi tethering no ads ever block Google lol I does get to be pain. There's also no features really that cool on nougat name one. Wait are you the new owner?I did root a Nexus 6 7.0 Android with stock kernel is that right idk it worked but I heard you should do costume also false a different ADB interface because my laptop wouldn't show it so I update drive and it's really a down grade worked bootloader unlocked in two seconds I know I should have researched but my brother gave me an hour to figure it out so i jumped on unlocked flash twrp supsu backup done. I am going to say please use your words carefully I've had a long night with these comments I was trying to be nice if that's not how it came off sorry I didn't realize or mean it I was tired.. you though want to start something that doesn't really concern you does it
[SuperSU] toknitup420:
I've looked through yours. And you're quite rude. This is a development site. Keep that BS on Facebook.
[SuperSU] dahawthorne:
I'm sorry that you think that. You've read over a thousand of my posts? I'm flattered and impressed by your enthusiasm. Given the number of thanks I have, I have to dispute your comment, though I can accept that I may on occasion have been impatient. Can you point me to some examples so that I can learn from them?

I don't use Facebook.
[SuperSU] toknitup420:
Deleted. Have a lovely day.
[SuperSU] dahawthorne:
I've given you a thanks, and not in any ironic or offensive way. I saw your "troll" comment, which you've removed, and for that, thank you. I loathe trolls, and was momentarily sad at being classed as one when I think that I have added significantly to these forums.

Peace, genuinely.
[SuperSU] ruchern:
He probably meant the play store version of beta. You know the one where you scroll all the way below and "Sign me up for beta tester" button.
[SuperSU] Sr. Zé Alguém:
[MENTION=7851590]Thisguy129[/MENTION]

I remember reading somewhere that Chainfire is working at CCMT for about 2 years already, therefore I wouldn't say it was completely sold nor that it happened today or recently... When Chainfire stops working on SuperSU and reviewing its code, then I would say that it happened. (The only exception would be if the conspiracy theories are true -- that "Chainfire" account have had been already sold and that this one is actually CCMT pretending to be the real genius).

About your posts, it is mostly the lack of punctuation what makes them hard to read and understand... If you are good with your home language, and if it isn't an oriental language, English punctuation may be similar. Writing clearly is a good thing to learn ;)
[SuperSU] corkiejp:
Chainfire has other apps, flashfire and stickmount which he has not sold, so I doubt he would transfer his XDA account!
[SuperSU] Sr. Zé Alguém:
Yes, I think these theories are of almost null probability.
[SuperSU] osm0sis:
Fud fud fud.
[SuperSU] TonikJDK:
Exactly
[SuperSU] yung40oz84:
I posted in regular thread, but here goes again.

am using the superSU UPDATE-SuperSU-v2.82-20170528234214 and when trying to use systemless mode with Adaway it will not apply the host file. Then when I reboot device and go into to Adaway it says they are applied.... So I am confused, but I never got that error with 2.79 SR3. Log attached.
[SuperSU] corkiejp:
Check the Adaway thread, one of the sources for hosts files is down, you may need to add an alternative source.
[SuperSU] gothicVI:
Manually check your host file. Maybe it worked.

Gesendet von meinem Moto G 2014 LTE mit Tapatalk
[SuperSU] yung40oz84:
Ya I did check it, but if I'm using systemless mode where do I check the host file?

---------- Post added at 11:45 PM ---------- Previous post was at 11:44 PM ----------

EDIT: ya I checked and it doesn't work in systemless mode, system mode ya it's fine.
[SuperSU] jcmm11:
In systemless mode do you have a file

/su/su.d/0000adaway.script

If yes what is the output, in a terminal emulator, of

mount | grep hosts

(root not required to run that command)
[SuperSU] yung40oz84:
I will check then,thanks bud!

---------- Post added at 03:17 AM ---------- Previous post was at 03:01 AM ----------

Ok I do have the script in /su/su.d/ and the output of the command is:

/dev/block/loop0 on /system/etc/hosts type ext4 (rw,seclabel,noatime,data=ordered)

marlin:/ $
[SuperSU] jcmm11:
Both as it should be. It should be working. What's the size of the hosts file? (Should be the same in both /system/etc and /su/etc)
[SuperSU] gothicVI:
You could also check the content of the host file. That's what I initially ment.

Gesendet von meinem Moto G 2014 LTE mit Tapatalk
[SuperSU] yung40oz84:
Yep, same size. Odd, I guess it's working but it's giving me the error that it's not working when I apply in AdAway. When I Reboot it shows applied.
[SuperSU] jcmm11:
Same size, but what is the size? ?
[SuperSU] Telperion:
Huawei devices and their issues with SuperSU

[MENTION=631273]Chainfire[/MENTION]

I have an update on the issues Huawei devices have with SuperSU. Huawei is starting to fix their broken kernels so some changes to SuperSU might not be needed anymore. (As a mental refresher, [MENTION=6870018]Tecalote[/MENTION] had posted in the 2.82 thread and you'd replied.)

Loop support -- Huawei has added loop support back in to its Nougat kernels, at least on some devices (FRD B38* branch). Official 2.82 (and 2.79, etc) flash successfully in systemless mode on these updated firmwares. I can't confirm that other Huawei devices (EVA, etc) have fixed the loop issues.

Library issues -- From recovery, official SuperSU (tested on 2.79 & 2.82) fails due to liblog.so being inaccessible (log attached). When the user mounts Vendor in recovery, then the zip flash succeeds. I've made the maintainers of the Huawei branches of TWRP aware of this so they can hopefully mount Vendor by default. Perhaps that's the best solution, perhaps the SuperSU installer should be modified, I'll defer that decision of course to you and them.

Going forward -- I don't want to speak for all other Huawei devices out there, but on the FRD the official SuperSU now works on the latest B38* firmwares. It's fair to say none of us want you to waste dev time on a fix for a one-time, transient issue.

That being said

, this probably isn't the last time a vendor like Huawei screws up their firmwares. We're lucky that Huawei fixed their issue, the next time we might get abandoned on a broken kernel. My opinion is that if you can still include a fix in the official SuperSU code to allow installation on devices with no loop support, it's probably a good idea.
[SuperSU] yung40oz84:
My bad, 71.67kb
[SuperSU] TonikJDK:
June security patches are out. I am updated.

Google Pixel XL

Flashall after removing the -w

Boot to TWRP.

Install SR3 and V3 signer. Did not install TWRP.

Updated to 2.82 via the playstore.

All is well, no problems at all. If you have questions please take them to another thread. I posted this here so SU users would know we are ok this month.
[SuperSU] jcmm11:
Ah ha - we have a winner!!!!

If you had been posting in the Adaway thread you would have had an answer before this. One of the three default Adaway hosts is currently down. It happens to be the largest of the 3, which is why your host file is too small by almost a MB.

Personally I stopped using the defaults a while ago and switched to just this one

http://sbc.io/hosts/hosts

That's a mirror for the Steven Black file and works very well for me. If you want to stay with the defaults try switching https://hosts-file.net/ad_servers.txt from https to just http. That should fix your problem.
[SuperSU] eqbirvin:
strange question but could i get a copy of the v3 zip signer?
[SuperSU] corkiejp:
June Factory Images - Successfully updated Nexus 9 and rooted .....

June Factory Images.

Successfully updated Nexus 9 and rooted with UPDATE-SuperSU-v2.82-20170528234214.zip.

I used flashfire app to flash image, supersu and Elementalx kernel!

Luckily I don't have to worry about signing the boot image on this device.
[SuperSU] yung40oz84:
So that mirror u gave me, I can just replace my hosts file in /system/etc/ with that file and be good?
[SuperSU] jcmm11:
In Adaway, 3 dot menu in upper right, hosts sources.

Either add the one I gave you (and uncheck the others) or modify the hosts-file.net entry (long press on an existing entry to edit/delete)
[SuperSU] yung40oz84:
Yep I just added it and unchecked others, thanks again for the help bud!
[SuperSU] mielletseed:
[MENTION=4487388]jcmm11[/MENTION], [MENTION=6044187]yung40oz84[/MENTION]: could you please use private messages for your conversation? This thread is about SuperSU. Thank you :)
[SuperSU] yung40oz84:
It started as superSU not applying hosts files with systemless mode in AdAway, went to hosts file. Convo over now though. Thanks. ?
[SuperSU] altwu:
look in this thread. http://xdaforums.com/android/software-hacking/signing-boot-images-android-verified-t3600606 the zip signer is now up to v8.
[SuperSU] eqbirvin:
I appreciate it! I am actually looking for v3 in particular for root testing. And I haven't been able to find it
[SuperSU] Ibuprophen:
You can grab what you need from the following Github link.

Though, it's for something different, It has the "VerifiedBootSigner-v3.zip" within a list of downloads to select from.

https://github.com/Walkman100/PixelRoot/releases

I hope it's what you're looking for... :)

***Please Note: As always, I welcome any member to help with further valuable information/clarification for any of my posts.

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise...
[SuperSU] eqbirvin:
Amazing!!! Thank you!! :)
[SuperSU] Ibuprophen:
Not a problem at all.

It took me about a minute to Google it.

All i did was look at the file name that Chainfire labeled it and changed the v8 to v3 and Googled the whole file name and the Github link was the 3rd result.

Anyway... Enjoy!

***Please Note: As always, I welcome any member to help with further valuable information/clarification for any of my posts.

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise...
[SuperSU] Tecalote:
Thanks for your input - this gave me the idea this night:

https://xdaforums.com/showpost.php?p=72564045&postcount=1768

Updated SuperSU for EMUI 5 (complete Unroot from previous modified SuperSU is required): https://xdaforums.com/p9/development/root-supersu-2-81-emui-5-t3612258
[SuperSU] peterlee928:
hi all

apologies in advance

for this noob q

im currently rooted

via sr3

is there any benefit

to updating to 2.82?

my view is

if it aint broke...

but figured id ask

the brilliant minds here first

much thx in advance :)
[SuperSU] dahawthorne:
Until they get here, one vote for "if it ain't broke"... :)

I switched to Magisk a couple of months ago and am still on v12 although there is a v13. I tried v13 but (a) had problems and (b) v12 does all I want it to do.

Until you start to hit problems, leave well alone.
[SuperSU] mondohow:
Are you having issues with the version you're on now? No? Then stick with that version.

Xperia user? Stick with your current version or at least make a backup then use the version direct from Chainfire: https://download.chainfire.eu/supersu

Do you have a compulsive need to be on the latest version of everything? Then at least make a backup and use the version direct from Chainfire: https://download.chainfire.eu/supersu

Aside from getting rid of the notification indicating an update is available then stick with the current version that works. However, since you posted in the Beta thread then maybe you like trying new things, in which case read up on how to grab logs and make a backup of your current setup then use the version direct from Chainfire: https://download.chainfire.eu/supersu. If you have problems then post logs and detailed steps to reproduce so they can try to fix it for others.
[SuperSU] Chainfire:
Have you tried with the new v1.3.3.7 posted yesterday in RootSwitch's thread ?

Also, it seems you are trying this now on a Nexus 5. But what firmware etc are you running? For what app do you need RootSwitch?

Needs more info to reproduce/fix.
[SuperSU] gothicVI:
Where did you find that? The official thread list v12 as latest?

Sorry for OT!

Gesendet von meinem Moto G 2014 LTE mit Tapatalk
[SuperSU] dahawthorne:
[MENTION=5895297]gothicVI[/MENTION]

Well, I typed Magisk v13 into Google.

But typing exactly the same into the XDA search top right will also get you there.

https://xdaforums.com/apps/magisk/unofficial-magisk-v10-beta-built-t3521901
[SuperSU] osm0sis:
Latest official Lineage nightly (0530). I'm using it to disable root and pass SafetyNet to use RBC Wallet, though Android Pay and Pokémon GO work as an easy test as well. ;)

The main thing to pass SafetyNet is that custom_ramdisk_patch.sh removes /su from the path, then links things with .supersu XBIN_BIND so when /su is unmounted and moved it looks like root is gone.

I'll try to get 1.3.3.7 now and see if it makes any difference, though regardless of that it used to work with 1.3.3.2 and now it doesn't without disabling mount namespace separation so it must be a regression, no?

Edit: Same deal on 1.3.3.7. Trying to toggle fails. If you're trying to mirror my setup, in Root Switch none of the options are checked.
[SuperSU] Chainfire:
There is no Android Pay where I'm from. Don't they ban rooted Pokemon Go users these days?

As I stated elsewhere, I have similar code here somewhere (for a long time). Not sure if it's going to be released though, with Google cracking down once more on those who try to root it.

Not necessarily. Mount namespace separation was only partially working on 6.0+ devices. That was corrected in v2.82. In other words, a bug was fixed. Now the question is, was the bug improperly fixed, or did RootSwitch never take mount namespace separation into account in the first place? In one case the fix is up to me, in the other the fix is up to the RootSwitch author (and is probably a one-liner). I'll now more when I've had the chance to investigate.
[SuperSU] osm0sis:
I've never been banned, so I guess not? They still just ban people doing malicious stuff like GPS spoofing as far as I can tell. SafetyNet Helper Sample always worked well for me to test the status.

Please do release the new suhide update, Magisk has certainly enjoyed its version unencumbered for some time now.

Thanks for looking into it! It's pretty easy to reproduce here. Just add that custom_ramdisk_patch.sh and .supersu with XBIN_BIND, reflash SuperSU, install Root Switch and attempt to toggle. The spinner will stay up longer than usual and the toggle won't change to disabled, it "bounces back" to enabled because Root Switch failed.

SuperSU full content logging only shows that it tries to run its /data/data/... app dir disable.sh and enable.sh scripts.
[SuperSU] Ibuprophen:
I never thought that the Open GApps App would have been banned but, Google apparently thought that it violated their terms.

Though, I'm sure that there's more details to it, so i can't state, for a fact, whether or not there's something that may or may not have violated something but, i would hate for the SuperSU to get banned over something minor.

I've got a feeling that Chainfire had battled with the Giant before LOL!

***Please Note: As always, I welcome any member to help with further valuable information/clarification for any of my posts.

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise...
[SuperSU] Chainfire:
I try not to piss them off. Like doing things you know they're explicitly against :)
[SuperSU] Chainfire:
Yeah, the su call made by RootSwitch is just wrong. This is what it is doing:

su -c /data/user/0/com.corner23.android.rootswitch/files/disable.sh

And this is what it should be doing:

su --mount-master -c /data/user/0/com.corner23.android.rootswitch/files/disable.sh

As I said, the fix is a one-liner. I suggest someone ping him and notify him of the problem and solution.

Again, this has always been a bug a RootSwitch. If you mess with system-wide mounts, you need to use the --mount-master switch. This is pretty well documented.
[SuperSU] DEVILOPS 007:
The hell is rootswitch??
[SuperSU] Chainfire:
[MENTION=3694505]Telperion[/MENTION] [MENTION=6870018]Tecalote[/MENTION] [MENTION=2247733]ante0[/MENTION]

Please note that v2.82-SR1 release is imminent. For there to be any chance for this to be included, I need answers to https://xdaforums.com/showpost.php?p=72568022&postcount=1773 ASAP.
[SuperSU] jekyll530:
I already replied there and notified him to take a look.

Thank you.
[SuperSU] Tecalote:
I will answer tonight, cause I am on job now
[SuperSU] osm0sis:
suhide isn't part of the SuperSU app however, so they wouldn't have any grounds to remove it.

Open GApps downloaded GApps packages, a clear violation of their "no built-in downloading of apps from other places than the Play Store" policy, and Magisk also serves some APKs and other modifications through its module repo in addition to blatantly circumventing SafetyNet and showing it does so within the app, violating their security exploit and no outside apps policies.

SuperSU app only works if the device is already rooted, and doesn't download or serve any files, nor in itself mess with SafetyNet. Should be totally safe for you to release the new suhide the way you did before, as an addon zip in the suhide thread. :)

Ahah, so your fix to the old mount namespace bug just exposed that Root Switch wasn't doing it correctly. Thank you for looking into it! [MENTION=1813976]shakalaca[/MENTION]

I've just updated my "AutoRoot Switch" Automate flow to reflect this as well and it works perfectly: https://llamalab.com/automate/community/flows/7559 :good:

P.S. changing the foreground app trigger to com.google.android.gms works for Android Pay. ;)
[SuperSU] Chainfire:
I am convinced that if they really wanted to, they could find some grounds to remove it. Furthermore, they reserve the right to remove any app without policy violations anyway... Hence my policy to not piss them off any more than necessary :)

See my comment above. In addition, their recent policy change of not allowing downloads of binaries and whatnot has caused me to scrap the new auto-updater for SuperSU (which was almost done, hrrrhhh), and quite a few planned features for FlashFire. Oh well...

Good!
[SuperSU] Ch3vr0n:
[MENTION=631273]Chainfire[/MENTION] your nexus 6P hasn't had the june update by any chance has it. Is it needed to flash boot verifying zip?
[SuperSU] Sr. Zé Alguém:
[MENTION=631273]Chainfire[/MENTION]

Why are you afraid of hurting Google's self-esteem? Many good apps are not or don't care to be in Play Store... Furthermore, what could prevent you from releasing a different version of the app only in the forums? One approved by Google in Store and another more complete here... Better than lose the work already done in new features ;)
[SuperSU] Ch3vr0n:
[MENTION=631273]Chainfire[/MENTION] That's actually an idea. If you for example release it through XDA Labs (the one found on the forums, not the one in the play store) you could keep the auto-updater functionality. Though this may mean you'd need to maintain 2 codebases. One for SuperSU throug play store, one for SuperSU (& flashfire) released through XDA Labs (with the app repo)
[SuperSU] Chainfire:
Who says none of that is happening? It's just not happening today.

I'm aware of all the options, and I've been taking them all under consideration for quite some time. There are pros and cons to all of them. Not to mention that CCMT needs to sign off on any path forward as well.

That being said, Google has always turned a blind eye to what's going on here. If you think Google cannot get rid of rooting almost completely with fairly little effort, you're naive and sorely mistaken. The same goes with SafetyNet - it is trivial to detect the current bypasses, and they are intentionally not doing so. Think about that before you want to scream off the rooftops that we've beaten them.
[SuperSU] Ch3vr0n:
I'm not saying anything like that, anyway. My question was in post 10302, that's I'll I'd like to know

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] Sr. Zé Alguém:
Can Google eliminate root completely? More likely it would become a problem like iPhones are for Apple, in the sense that since the first version they are jailbreakable.

Really, why mobile OS makers don't want to give owners administrative rights like any desktop OS have for free and no hassle? The obvious: This is what Google should do (and promote), even more because Android is open source.

The culture of making everything easy for brainless users not need to have a brain is what is ruining the world. No options, only one path to only one direction...
[SuperSU] spainter:
Lot of data mining for advertising profit. Just follow the money.

Sorry for OT
[SuperSU] ktmom:
I don't agree that google, device manufacturers, app developers, ect are not entitled to block the running of at least certain apps if root is installed. e.g. A banking app could easily be at risk running on a rooted device. The bank should have the right to refuse access to their systems on these devices if they choose. The same for android pay, or even Netflix.

I'm in favor of rooting my device. I accept it means I may not have access to some apps as a result. Maybe an argument for multi-rom. But it wouldn't surprise me if google goes after the hide functions to help ensure app developers have some confidence in the platforms their app is ruining on. SafetyNet is important feature in this world. </rant>
[SuperSU] Chainfire:
My reply was more to people in general, as lately a lot of related questions have come up.

As to your specific question, I don't know, I have not tested. And I'm testing with the as of yet unreleased v2.82-SR1 anyway, which includes signing automatically. I hope to release it before the end of the week.