yashsingh1/xdaforums huggingface dataset:
[SuperSU] Chainfire:
Not completely, but mostly. Probably to a point where it would be such a hassle that the root community would shrink significantly. There are relatively few iPhone/iPad models and they run a very uniform OS. This is not the case for Android. A string of exploits that gets you proper root on one device is unlikely to work on another. Somewhat generic exploits do turn up now and then (towelroot and dirtycow are the two most recent ones) but they are few, far between, and becoming increasingly rare.

With the refinement of SELinux and introduction and better use of technologies like TrustZone/TIMA/TEE/etc in theory they could virtually eliminate it. We could only survive on finding and exploiting bugs, with most parts of the system protected with multiple layers of security.

A lot of US carrier devices have no proper root already. And these are insanely popular devices. Less popular devices hardly stand a chance.

There really are multiple camps in this. Some think the openness of desktops was a mistake to begin with. As a developer I disagree, but as a user I am slowly edging into that direction (not quite getting close though). The aim (on paper) is improved security, the problem for us is reduced usability. But the latter gets better as the OS gets further developed. See how many things we used to do with root that we are now able to do without!

I agree completely.

Though of course it should be noted that it is rather silly that my banking app refuses even read-only access on my benignly rooted phone, while I can send money to the entire world on my Windows machine which is significantly more likely to be infected by a malicious rootkit.
[SuperSU] Ch3vr0n:
Thanks for the fast response, my device didn't get the update notification yet. I was just asking ahead, I'll await SR1 then before I do any June flashing.

Keep up the good work and I do hope you find a way for that auto-dowload thing for SuperSU and flashfire.

Verstuurd vanaf mijn Nexus 6P met Tapatalk
[SuperSU] gubacsek:
I say it should be at least a choice to have root on our own devices, which we bought on our money. There should be a big red switch, with some text that we take full responsibility if we turn this on, and then it should grant root access.

Now that I read your post saying "google could easily f*ck us, and make it impossible to have root", I am happy they don't do it :D Although they are not making it easy for us to keep using root, right ? ;)

I can't wait to have root on android O! I read your post on g+, and i'm really curious what are those changes by google, and how you solve them! I admire your work! :)

And if you need testers, please let me know, I would like to help in any way possible!
[SuperSU] zelendel:
I see this argument a lot. Yes you payed for the device and own it but that only covers the hardware. The software is leased not owned. So unless you plan on making a whole OS from the drivers up then you have really no say in the software.

Root really is a security hole that is a risk many are slowly moving away from using. It will be interesting to see as things get only more secure like chains as already stated. It's only a matter of time.
[SuperSU] _that:
Root is only a security hole if you see it from the perspective of Google. Not having root and not having control over my data is a security hole from my perspective as a device owner.
[SuperSU] zelendel:
You own hardware. Not software. That is only leased.

People really have big egos if they think they are better equipped to deal with security matters then people that do it for a living.

Root in itself is a security Hole from all security stand points. It is too easily manipulated. Won't matter as chains has already said. Things are getting harder and soon root will not really be an option except to those select few that are willing to lose things like the play, store and Google pay (not sure why someone would use mobile payments but hey a sucker born every minute)
[SuperSU] TioCareca:
When i pay for a piece of hardware, drives are included, so we should be given drivers with our phones and the opportunity to use our own OS when we decide to use root, and as Android is open source that make our life's easier...
[SuperSU] gubacsek:
Yes, you are right, and I don't want to start a debate here, let's keep Chainfire's thread clean, and focused on development.

I'm an IT architect, and love computers since I touched the first one, and loved to program in basic, and I loved to play around with settings (in the OS, not in the GUI), and I still want to be in control. I still install my sound mods, I still have my chrooted gentoo running on the phone sometimes, I still use my own busybox, openssh server, rsync binary, and I want to be able to back up my apps, and also to restore them after flashing my phone. I use this thing as a PC, or laptop, not just a phone.

I know the majority of people doesn't care about things like this, they are using it as a phone, making phone calls, playing some games.... This is why I say, it should be optional, and people like me could still be in control, but app makers could make sure their app doesn't run on a rooted device. I am okay with this. I'm not using netflix, pokemon , or any banking software on my phone. I give these up, so I can use it for anything else...

I'm also not sure about getting the hardware only for my money... It is google's phone, with google's (open source) software. It is an android phone, running android. Most probably you are right, but somehwere deep down, it is not quite right.

I am also using root less and less... I don't have so much time to play around with stuff, and sometimes I only use it for installing ARISE, and restoring my backups.

But the fact that I'm in control of my own device, makes me feel right, and sleep relaxed :D It is an itch, the world is not right until I know I am in full control. :P
[SuperSU] Danilo Pantelić:
Android O Dev Preview 3 is rolling out with final APIs

http://www.androidpolice.com/2017/06/08/android-o-dev-preview-3-rolling-final-apis/

Download - https://developer.android.com/preview/download.html#flashable-images

Release Notes - https://developer.android.com/preview/release-notes.html

Blog - https://android-developers.googleblog.com/2017/06/android-o-apis-are-final-get-your-apps.html

Android 8.0 confirmed - http://www.androidpolice.com/2017/06/08/android-o-confirmed-8-0-latest-developer-preview/
[SuperSU] zelendel:
Yes with a lease. Yet no one reads it. You know the part that states how it can and can't be used.

Also on a side note only aosp is open source and even that is not completely open. It is licensed under the apache which means any code changes to aosp is their code changes and they own that code so they don't have to share it.

Google could easily not push anything to aosp at all and no one could make them do so under the apache license.

---------- Post added at 12:53 PM ---------- Previous post was at 12:51 PM ----------

It's not open source though. Take the pixel as example. Many of the base systems are closed sourced and what is pushed to aosp is not even close to what comes on stock Google devices like the pixel and nexus line.
[SuperSU] Sh0X31:
Hope the Pixel get rooted soon on Android O
[SuperSU] :
Guys this thread is for Supersu, not to link firmwares or request root. Lets keep it on track please we don't want to have to come in and do a mass spring cleaning

Regards

Sawdoctor
[SuperSU] Chainfire:
v2.82-SR1 available for download:

https://download.chainfire.eu/1114/SuperSU/SR1-SuperSU-v2.82-SR1-20170608224931.zip

Changelogs:

https://xdaforums.com/showpost.php?p=64916199&postcount=3

Release notes:

https://plus.google.com/+Chainfire/posts/XikxTkhHpiG

Flashing on the Pixel (XL) with ODP1/2/3:

Using the attached root-sailfish/marlin-pixel(xl)-v2.82.zip

For full instructions read the included

README.txt

file. Long story short:

- fastboot boot boot-to-root.img

- wait 5 minutes

Manual TWRP instructions

The above should be enough, but if you like to play around:

TWRP still has some issues with ODP on the Pixel, so this is a bit tricky.

To start please make sure you are running the stock boot image for your ODP firmware. Then fastboot boot TWRP RC1 ( twrp-3.0.2-0-RC1-fastboot-marlin/sailfish.img ).

If TWRP comes up and is usable at this point, flash the ZIP as normal. In the more likely case that you end up with a flickering screen, follow the rest of these instructions.

ADB will probably not detect the device. Just keep it plugged in and wait 5-10 minutes, and it might show up.

Then, copy the downloaded SuperSU ZIP file to /tmp/supersu.zip on the device:

adb push /path/to/supersu.zip /tmp/supersu.zip

Now go into adb shell and copy/paste the following commands to unlock /data:

mkdir /system_root
mount -o ro /dev/block/bootdevice/by-name/system`getprop ro.boot.slot_suffix` /system_root
mount -o bind /system_root/system /system
/system/bin/e2fsck -E journal_only /dev/block/bootdevice/by-name/userdata
/system/bin/tune2fs -Q ^usrquota,^grpquota,^prjquota /dev/block/bootdevice/by-name/userdata
sleep 10

This should stop the TWRP screen from flickering.

Now to actually install the ZIP:

mkdir /tmp/zip
unzip /tmp/supersu.zip META-INF/* -d /tmp/zip
sh /tmp/zip/META-INF/com/google/android/update-binary 3 1 /tmp/supersu.zip 2>/dev/null | grep ui_print

Finally you can use adb reboot to reboot the device. After a minute or two your Android should be up and running, rooted.

If all else fails you may try to 'fastboot erase userdata' (this wipes all data) before starting TWRP.
[SuperSU] Danilo Pantelić:
Nevermind...
[SuperSU] NLBeev:
As long as manufacturers ads proprietary stuff to open source software in a way it can't be removed/changed as normal apps, there must something like root. In the EU we have rules to avoid unfair competition and abuse of power.

For whom? Users that root their devices will lose warranty and support and security. That's the price. But they can customize their device. Rip music, movies and block ads etc.

In general it's not black-white. It's complicated. Manufacturers has to balance a lot between international rules, patents, economics and marketing.
[SuperSU] zelendel:
Yes it wouldn't be as bad if every accepted the things that come with root. Like giving up banking apps and thing that should only really be used a secure device. Yet they don't. They are always trying to bypass the system. Which causes issues for everyone.

See that is the thing. Everyone keeps saying android is open source. Yes aosp is. What Google, Samsung, HTC, Sony ect release is not.
[SuperSU] Chainfire:
Release notes for v2.82-SR1 posted: https://plus.google.com/+Chainfire/posts/XikxTkhHpiG
[SuperSU] msprenger:
Please excuse this noopy question...may i use it on galaxy s5...thank you very much
[SuperSU] aburezk:
Tested v2.82-SR1 on Huawei P10 Lite Working

WAS-LX1A

Android 7.0
[SuperSU] yjcbn:
Just flash v2.82-SR1 as normal on my Nexus 6P using Android O Dev Preview 3 and it works! Thanks developer.
[SuperSU] -DarkKnight-:
I can't seem to boot into TWRP on my Pixel. Everytime I fastboot boot twrp RC1. I get a black screen. Not even flickering.

adb shows my devices as offline
[SuperSU] Benny100:
Is Working Samsung S7 Edge S8 Port Rom....

THX! :)
[SuperSU] zipredictive:
Flashed on 5x dp3 perfect!
[SuperSU] NLBeev:
Nexus 6, Nougat 7.1.1 June, boot.img 3.10.40-g80b1ca674b0, unencrypted.

Twrp-recovery 3.1.1.0. Flashed su 2.82-SR1. Reboot as before, no issues.
[SuperSU] nitramus:
I think you might have the wrong thread. This is supersu not twrp thread.
[SuperSU] quincho54:
Flashed SuperSU v2.82 SR1 with twrp 3.0.2.0 on Note 4 SM-N910h ,Costume Rom Nemesis Refined Light 3.6.9, no issues.
[SuperSU] skyhirules:
Thank God, no boot loop on Xperia Z1 Compact, stock Android 5.1.1. Works fine so far.
[SuperSU] StrizzMatik:
For some reason the DP3 root method didn't work on my Pixel XL :/ followed Chainfire's instructions to the letter with no issues, reboot and still no root.
[SuperSU] Chainfire:
I've added fastboot bootable images that install v2.82-SR1 to Pixel (XL) to the release post: https://xdaforums.com/showpost.php?p=72604085&postcount=10323

Easier than mucking about with a non-working TWRP.
[SuperSU] Ibuprophen:
It installed and operates without any issues on my d2vzw.

I can just imagine that SINKING feeling Chainfire must feel as he officially releases the next version of SuperSU.... LMAO!

***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] X04D:
Installed using fastboot method (fastboot boot boot-to-root.img) and the process went perfectly.
[SuperSU] okidokiss:
Flashed with twrp, loosed access to external card

Enviado do meu GT-I9505 através de Tapatalk
[SuperSU] yung40oz84:
Kind of off topic, but once we get to the spot where TWRP stops flickering can this method potentially be used to flash other zips in TWRP? And boot-to-root worked fine so far on DP3, took about 2 minutes if that to fully boot, did have systemUI FC upon boot, but went away.
[SuperSU] holla420:
Thank you very much for this. Been waiting a good bit for root on OPD2-3 for Pixel XL. Followed the .Txt worked perfectly
[SuperSU] martyfender:
Just out of curiosity, could you describe this method using fastboot instead of twrp?

Thanks
[SuperSU] Chainfire:
There could be exceptions, but I think virtually any ZIP should be flashable that way. You may need to manually pre-mount /system and /system_root as well, but it should generally work.

Also, ODP3 seems to randomly FC for me at boot, regardless of rooted or not :/
[SuperSU] andreoide:
Yes you can flash it on your S5.

I flashed on Samsung S5 Plus SM-G901F kccat6.

Working without any issue.

Thnx ChainFire :good: :good:
[SuperSU] okidokiss:
Back to 2.82 solved the issue
[SuperSU] Dnorris55:
Same here on my Samsung T800.

With sr1, seems like a link is missing. In ES File Explorer, couldn't see external sd card under Local, but could see it via /mnt/media_rw. Couldn't see it in File Manager app, could see it in Files app. Could see it in Settings-Storage.
[SuperSU] Ch3vr0n:
[MENTION=631273]Chainfire[/MENTION] SR1 bootloops N6P. Stuck on google logo after flashing june updates. Below all the info

procedure done:

Update june OTA restore boot & recovery

flash SR1, NOT restoring backups (in order to root based on updated images)

SR1 determines signed boot and proceeds to signing

procedure appears succesfull but reboots to BOOTLOADER and not system

Manually attempted reboot system > failure

Net result: system boot failure stuck on google logo. Rebooting to recovery also stuck at google logo

Next proceeded to system: adb/fastboot not recognised. had to update SDK to API 26 (though rootchecker seems to indicate api 25, yes im still on N so may be unrelated). Then fastboot boot to twrp works

Flashed 2.82 stable over the top. TWRP Reported "error installing zip file Cache/recovery/block.map

system boots up with 2.82 rooted, all root requiring apps seem to be fully functional

That's all the info i can give. I'd be happy to pull the FF backup of original boot image if ya tell me how.

Flashfire lastlog, full syslog & twrp log attached
[SuperSU] ALIGATOR26:
SR1 work Great on Samsung Galaxy S7 with stock rom rooted phone. Tnx.

Trimis de pe al meu SM-G930F folosind Tapatalk
[SuperSU] yung40oz84:
I flash rom, TWRP reboot.

Then flash kernel, TWRP, boot signer and reboot recovery

Flash superSU and boot signer, and system boots but when reboot back to recovery it fails, no recovery.... Am I missing something, is the newest boot signer only compatible with the SR1 2.82 supersu?

This procedure has always worked for me

UPDATE: I just did the same process with 2.82 stable and it worked fine
[SuperSU] krazekid7:
Can anyone help me? The boot-to-root keeps installing as systemless root. I would like it to install as system root so that I can delete and install system apps. Any help?
[SuperSU] Ch3vr0n:
systemless root has absolutely ZERO to do with the ability or inability to install and delete system apps. Systemless root simply means you are ROOTED without touching the SYSTEM partition, that doesn't mean you can't install or delete apps into the the system partition. Just mount it r/w and you're all set.
[SuperSU] krazekid7:
it wont let me mount with busybox installed
[SuperSU] Ch3vr0n:
"it" won't let you mount, what exactly is "it"? Which busybox, there's lots of them
[SuperSU] yung40oz84:
Wait so if I flash a kernel, TWRP, and then boot signer, reboot recovery, will superSU recognize that as a signed boot image since I flashed the boot signer and I don't need to flash boot signer again, I posted a few posts back and this may be the issue? Or if I flash kernel and TWRP and reboot recovery without flashing boot signer, then flash superSU it will sign, is that sufficient.
[SuperSU] Golf c:
Excellent question?

Edit: I'm leaning towards yes. Could be totally wrong. Chainfire talks about a stock boot image being signed but doesn't talk about a VBS.zip signature being acceptable for SuperSU to recognize.
[SuperSU] krazekid7:
Sorry, adb won't let be mount the system using all the methods I've tried.
[SuperSU] yung40oz84:
I had a post here about my progress, same process works on previous version of superSU, here is https://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/post72611681
[SuperSU] nicolap8:
No, very bad. Reread the release note on g+.

Yes, you are wrong :o

For SuperSU a signature is like others.
[SuperSU] Golf c:
Out of thanks for the day. Yep, I read that. Things are changing rapidly. Keep up the good work. I hope it gets easier and we get updated TWRP.
[SuperSU] Sh0X31:
I flash the image without -w (wipe) on my Pixel and I don't boot up (because of the encryption). I reboot direct in the bootloader and use to boot-toroot.img but my phone always reboot after the Google Splashscreen

talk about odp3. How I flash O Dp3:

fastboot flash radio radio-x.img

fastboot flash bootloader bootloader-x.img

fastboot reboot-bootloader

fastboot update image-sailfish-o-dp3.zip

after successfully flashing the Image of Android O DP3, I press Vol Down and use reboot to boot into bootloader. Here I use the boot-to-root from Chainfire:

fastboot boot boot-to-root.img
[SuperSU] bemagrp:
Pixel xl, stock, twrp, super su 2.82, elementalx .

Question, can i just flash sr1 in twrp and if yes, do i have to flash vszip8 after it?

Thanks
[SuperSU] martyfender:
Is it possible for me to create a boot to root image for a device which does not have twrp built for it? It is an intel x86 cherry trail device with android 6.0.1. I have unlocked it in fastboot. Would android image kitchen be used to create the image? If there is a link to another forum to help, that would be great.

Thanks
[SuperSU] Golf c:
Huh? Sounds like you have a semantics problem? I'm saying if the boot image is signed by the VBS zip, SuperSu 2.82 RC1 should recognize this and sign the boot image.

---------- Post added at 12:24 AM ---------- Previous post was at 12:07 AM ----------

Elemental x signs the boot image, so were thinking that you won't have to flash VBS.zip cause elemental x signed it already and Supersu 2.82 RC1 should sign it again? Please let us know if that's correct.
[SuperSU] peterlee928:
read thru the recent posts

sorry if im dense

and missing the obvi

but if i am currently running

twrp 3.1.0

stock rom june update

vzn pixel xl

can i just boot to recovery

install 2.82

then good to go?

or do i need to flash the vbs

after installing 2.82?

from my interpretation

i dont need to flash vbs

since im flashing supersu

over stock signed boot img...

and assume no data loss

or reset of system settings

from installing 2.82?

much thx in advance

for answering noob q's :)
[SuperSU] krazekid7:
Can anyone help me mount system. I'm on a pixel XL DP3.Adb gives me an error even with busybox installed.
[SuperSU] yung40oz84:
Ok, so I still need to know something.

I flashed custom kernel, TWRP, then VBS

Reboot recovery

Flash superSU, VBS

Reboot system

When I got to reboot into recovery it goes to ram dump, no recovery.

If I used this process with superSU 2.82 stable it works.

So my question is if I am using the VBS after the custom kernel, then I don't need to flash the VBS after flashing superSU correct? That's the only way I haven't tried.....
[SuperSU] osm0sis:
New Root Switch is now out fixing the mount namespace separation / --mount-master issue. Here are the direct links since the Asus forum is all tricky with overlays and such. ;)

RootSwitch-1.3.3.12.zip:

https://www.asus.com/zentalk/tw/for...5MDU4fDdlNzgwMzVifDE0OTcxOTY5OTh8MHwxNzM1NDI=

RootSwitch.zip (.supersu and custom_ramdisk_patch.sh, needed for passing SafetyNet checks):

https://mega.nz/#F!NwUAxKjA!lodsOX94Wd4I5HfBFR3jJg

Pro tip: Enable "Request desktop site" in Chrome and Mega won't try to force its app on you. :)
[SuperSU] jekyll530:
I've installed it for 2 days. But according to my test, when "Mount namespace separation" is enabled, hiding root with RootSwitch results in not able to restore root. I don't know the root cause though.
[SuperSU] osm0sis:
Working fine for me. I don't have any options checked, just used the enable/disable function.
[SuperSU] jekyll530:
I've installed it for 2 days. But according to my test, when "Mount namespace separation" is enabled, hiding root with RootSwitch results in not able to restore root. I don't know where the root cause is though. I'm using OnePlus 3 with OxygenOS 4.1.5 which was just released few days ago.

---------- Post added at 07:07 AM ---------- Previous post was at 07:01 AM ----------

Sorry, I thought my first reply wasn't published......

I only have "Show switch in notification" checked in RootSwitch. I tried many times, once "Mount namespace separation" is checked, hiding root results in loss of root.
[SuperSU] Golf c:
Here is what I just did that works.

Flash custom kernel

Flash Twrp

Flash Vbs.zip

Flash SuperSU 2.82 RC1

Reboot system

Profit
[SuperSU] peterlee928:
[MENTION=6302926]Golf c[/MENTION]

dumb ?

can i just go into twrp

flash rc1

and call it a day?

i just use stock

no custom roms

no kernels

already have twrp installed

and used vbs v3
[SuperSU] Golf c:
Yes.

If you're all set up with Twrp and SuperSU 2.82, then just flash SuperSU 2.82 RC1.
[SuperSU] peterlee928:
coolio

so im running supersu 2.79

assume that makes no diff?
[SuperSU] Golf c:
If your boot image is signed, it should make no difference.
[SuperSU] peterlee928:
worked

much thx :)

---------- Post added at 09:37 AM ---------- Previous post was at 09:11 AM ----------

also experiencing same prob

started with

twrp 3.1.0 installed

vbs v3

and supersu 2.79 sr3

booted into twrp

flashed 2.82 sr1

reboot

everything working fine

except when boot into recovery

goes to ramdump
[SuperSU] SnapShot86:
Huawei Honor 5C Rooted Emui 5 Nem-L51 C10B355 Android 7
[SuperSU] Golf c:
Same thing here. No recovery. Ram dump. Then boots back into system.
[SuperSU] ianmacd:
2.82 SR1 working as expected on my S8+.
[SuperSU] saransh arya:
New to the post can I flash it on my moto g Merlin turbo edition pure stock 6.0.1 with twrp or do I have to enter the command in terminal in recovery?
[SuperSU] shoey63:
Works good? or is there a problem ?
[SuperSU] peterlee928:
issue is when i try to boot into recovery

the phone goes to ramdump
[SuperSU] bemagrp:
On June stock, twrp rc1, supersu 2.82, elementalx 1.12.

Do I have to just flash supersu 2.82 sr1, then elementalx, right?

Thank you in advance for help.
[SuperSU] X04D:
Used the boot-to-root method on Pixel running ODP3. Was working fine, then I rebooted and SystemUI continuously crashes. On restart, notification came up saying "Factory Reset", then bootloops. Have to flash boot.img to slot a and b to get the phone working again, but can't keep root.
[SuperSU] messiahfreedom:
After using boot to root on ODP3, I can't set system to RW no matter what I do. Anyone else have trouble with this?
[SuperSU] Golf c:
That is correct, but we can't get back in recovery. Everything runs fine but booting to Twrp goes into a ram dump and reboots to system. I would stick with your current setup.