yashsingh1/xdaforums huggingface dataset:
[SuperSU] CatThief:
I'm partial to SuperSU, too, but installation aborted at "patching sepolicy" on my Pixel after updating to Oreo 8.1. It worked on my Pixel C, but on my Pixel I installed Magisk instead and had no problems at all. Looks like that's what I'll be using from now on.
[SuperSU] ktmom:
From the contact info for SuperSu on google play store;

Contact us:

Website : http://supersu.com/

Forum: http://forum.supersu.com/

Facebook: www.facebook.com/SuperSUofficial

Good luck with that.

"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
[SuperSU] RichardEb:
Does the latest stable(!) Magisk supports Android 8?
[SuperSU] DodoGTA:
Yes

---------- Post added at 08:42 PM ---------- Previous post was at 08:40 PM ----------

Magisk doesn't work below Android 5.0
[SuperSU] DB126:
All valid considerations. I have no plans to move a stable/working device off the root solution currently in place provided it satisfies my interests. When that changes I will assess the landscape and select the best solution(s) that address those needs which may or may not carry over to other devices in my portfolio. It doesn't get any more complicated than that.
[SuperSU] RichardEb:
I'd like to install Android 8 and I'm tired of waiting,
[SuperSU] martyfender:
I have considered trying Magisk again, but in the previous versions I tried on my Nextbook Ares 8A x86, Android 6.0.1 tablet, I lost root in less than a day, with it. That is unexceptable. I have never lost root with SuperSu, despite using many beta versions of it.

I follow the Magisk beta threads and look at the unofficial builds thread of it frequently, but am fearful of trying it again.

However, I do like the fact it is in active development, so the lastest unofficial versions may be much improved:

https://github.com/kantjer/MagiskFiles
[SuperSU] jcmm11:
Just use SuperSU-SR5, it may not be labeled as stable but it's acting stable.
[SuperSU] RichardEb:
Maybe this Version is stable. But what will happen if there is a new bug or even a zero day security issue?

Maybe it will take weeks maybe years until die SuperSu developer will release a Bugfix. There are also no compatibility checks for new Android releases.

No i'd like to stay off supersu for now.
[SuperSU] DodoGTA:
You should try the latest Magisk unofficial snapshot (I don't see any root loss with it, I think)

But, please provide as much information as possible if you experience that issue again
[SuperSU] dechronic:
People have already been using it for a few months. Even if there is an issue with SuperSU or you wish to switch it can be easily removed and likewise for Magisk. If you're worried about it that much you can just make a complete backup of your phone before you try it. Which is good practice for any time you are going to use something that will modify a device's working configuration.

I just wiped my cache, boot, system and vendor partitions last night to install Android 8.1.0. Then I installed SR5 and my kennel of choice and I haven't had any problems on my Nexus 5X.
[SuperSU] DB126:
Same exposures/risks exist for other alternatives. Arguments can be built and torn down over who does what better, when and why. Security dramas are just that. Yes, there are real threats in the wild that must be monitored (no worries; screaming media headlines will keep us informed) and occasionally warrant a response. In the end personal behaviors are biggest determiners of what happens to your electronic gizmos and the information entered into them. If worried don't root.
[SuperSU] elotan:
Hi all

I just upgraded my Nexus 6P to Pixel 2 XL. I have unlocked bootloader (and critical partitions), and got the 8.1.0 official update. Can I use the latest Super-SU to root my device the same way I did with the Nexus 6P?
[SuperSU] Sh0X31:
If SuperSU works I don't know but you can try magisk

https://xdaforums.com/pixel-xl/how-to/guide-pixel-xl-android-8-1oreo-unlock-t3715279
[SuperSU] peterlee928:
got sr5 working on my verizon pixel xl (much thanks to [MENTION=5365841]AP2FTW[/MENTION] for the game changing tip). see my steps below. steps assume that you have the latest platform tools and google drivers, and that all files are in the proper folders.

1) back up everything

2) plug phone into laptop

3) adb reboot bootloader

4) flash factory image 8.1

5) phone automatically reboots

6) do NOT set fingerprint, password, or pin during setup process

7) turn on developer options

8) allow usb debugging

9) put twrp 3.2 zip onto phone

10) adb reboot bootloader

11) fastboot boot twrp img

12) install twrp zip

13) reboot system

14) extract supersu sr5 zip file on your computer... find the superuser apk file and put that on your phone

15) put the sr5 zip file on your phone also

16) adb reboot recovery

17) install supersu zip

18) reboot system

19) supersu app should not show up in your app tray... now run the superuser apk file

20) supersu should now be installed on your phone

EDIT

when flashing the factory image, i did a clean install... no removal of -w from flash-all.bat file, etc.
[SuperSU] AP2FTW:
I just used a file explorer on my phone to go into the zip and click on the supersu apk :good:

I also flash suhide in twrp to pass safety net as per homeboys instructions in his thread

Edit I'd also like to make clear that I did initially flash the supersu zip in twrp...but when I didn't see the app in my drawer I figured let me try to find the APK in the zip and install it
[SuperSU] sharkie405:
SuperSu (any version) does not work on the Pixel 2 XL (any build) unfortunately. Oh how I wish that it did!
[SuperSU] Alxoom33:
No, unfortunately the only current root method for the Pixel 2 XL is patching the boot.img with Magisk.
[SuperSU] paradox923:
I tried this step by step several times. In TWRP 3.2 when flashing SuperSu i get fail on patch sepolicy. On reboot I install apk but shows not rooted. Scratching my head here. Pixel Sailfish (google) 8.1 final version.
[SuperSU] peterlee928:
somethings going wrong when flashing sr5. i didnt get fail on patch sepolicy. to be fair i definitely tried this process multiple times before it stuck (likely user error on my end).

feel free to pm me.

EDIT

one suggestion is to do a clean flash of the factory image. i failed to note that in my instructions, which i will amend now. hopefully that does the trick.
[SuperSU] TonikJDK:
Flash the boot image to both slots and start over. SU5 is picky if either are modified.
[SuperSU] elotan:
Thank you very much for your help.
[SuperSU] ashyx:
Oh if only, XDA's noob post count would drop considerably.

It seems for many an extra minute or two to make a pre-mod backup is far too much to ask and would rather spend hours afterwards trying to fix things when all doesn't go to plan. :rolleyes:
[SuperSU] PaulPizz:
I'm running the og pixel. Let me know if I can help
[SuperSU] DodoGTA:
[MENTION=4544860]osm0sis[/MENTION] Do you prefer SuperSU or Magisk?
[SuperSU] osm0sis:
I like the stability and predictability of SuperSU. Magisk is excellent and getting better by the day, but its super-active development right now also means a lot of regressions. So I do have Magisk on a couple of my devices, but my daily driver will likely remain with SuperSU until SuperSU doesn't work on it anymore.
[SuperSU] tombraga:
i cannot find the download link for the new version...not on the 1. page!
[SuperSU] ktmom:
I don't know why you couldn't find it. It's in post #1

"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
[SuperSU] osm0sis:
[MENTION=4999212]PaulPizz[/MENTION], check your PMs please. :)
[SuperSU] badhabit_wb:
I have an original pixel and can't get root. I had no problem on 8.0. I used new platform tools and twrp 3.2.0. Couldn't get by password so I flashed factory image. Failed at supolicy. Flashed it again same thing. Any ideas? Both times it said slot b. tia
[SuperSU] PaulPizz:
I've rooted 8.1 successfully. Try using slot a.
[SuperSU] badhabit_wb:
How do I move it to slot a? Normally when I flash it just decides which slot on it's on. It looks like it loads to slot b and is backing up to slot a.

Thanks
[SuperSU] gubacsek:
I have the same. I could root the first dev preview with supersu, but now I am trying the final realease and it fails at supolicy.
[SuperSU] badhabit_wb:
Yeah and I keep hearing to change slots but nobody seems to know how
[SuperSU] bsmitty83:
I'm running a pixel XL right now , 8.1 stock with my own kernel , superSU adb sideloaded via twrp 3.2 , since I don't want to de-encrypt. Works fine , just like Android 8.0 .

If you need testing on Marlin , just hit me up old friend......
[SuperSU] Golf c:
A, B, C, D changing slots isn't the problem. I can do whatever I want in any slot I want.

fastboot - -set-active=a (or b)
[SuperSU] badhabit_wb:
I'm going to try to switch from b to a and see if that makes a difference. I doubt it since it stops at supolicy patch.

---------- Post added at 08:39 PM ---------- Previous post was at 07:51 PM ----------

Still fails at patch supolicy and I'm on slot a now.
[SuperSU] badhabit_wb:
Any ideas?
[SuperSU] Mzprx:
SU does not install

Same here. Pixel (1st gen) Last night I sideloaded the latest Android update 8.1. TWRP couldn't decript, so I turned security off to make it work. So far so good, however SuperSU is failing to install. As noted above fails when patching sepolicy.

I've done this after every update for 8.0 (except that TWRP decription was working) without a problem, but this time it didn't work. I should have installed Flashfire, but who knows if it would work after relatively major update as 8.1.

I'm doing systemless root (no permanent TWRP install). Trying to install latest SU SR5. Tried also older (stable) SU versions without success.
[SuperSU] daddylonglegs:
I have to also chime in about the original Pixel on 8.1. I have followed five different guides and absolutely nothing works. I cannot get SuperSU no matter what I do.

I have been rooting since the HTC Thunderbolt so I know it's not a mistake on my end. But I don't understand how some people say it works for them, and so many others say it does not.
[SuperSU] peterlee928:
i have read that pixel x supersu is having problems. but magisk is confirmed by multiple sources to work. for whatever its worth...
[SuperSU] daddylonglegs:
For some reason I can't get Magisk working either.

I get systemUI crashes whenever I try to install it. I think it's because in Android 7.0 I used this Magisk module called EvilTheme patcher. It might be residing somewhere on my phone and when I install Magisk it re-enables it. I have no clue where to begin looking to see if that is the case though.
[SuperSU] Mzprx:
Same here. I think we will have to wait for new SU version.

The TWRP password problem can be avoided by setting the security to "none" temporarily, but SU installation still fails. New TWRP should come around too.
[SuperSU] badhabit_wb:
It will be interesting to see how long it takes for supersu to be updated, or if it's in a time frame that's relevant. I couldn't get magisk to work but I'm betting it's sorted out first now that chainfire is not around...
[SuperSU] Mzprx:
Well, chainfire said that CCMT are good fellows and I hope they will take action soon... Maybe he can get a short break from the retirement to help :)
[SuperSU] badhabit_wb:
I hope he's enjoying his retirement. I think if CCMT would start posting on xda and keeping the beta's on the thread it would help to ease everyones mind. Change makes people nervous. If they get off to a good start it would help them and us. I'm hoping they do a great job. I've always liked supersu because I could keep everything else like it came. I mostly use root for tasks that require root but I don't have a lot of apps that do.
[SuperSU] shaggyskunk:
Exactly - CCMT appears (poor choice of word as they haven't) to be noticeably absent from XDA and if someone is prone to cynicism.... ?

Sent from my SM-G955W ??
[SuperSU] TonikJDK:
Unfortunately they are also absent from their own message boards.

That said, they paid Chainfire money, they must have a plan of some sorts....they didn't buy it to abandon it.
[SuperSU] shaggyskunk:
Who knows - "foot in the door" investment? Tax Right off?....

Sent from my SM-G955W ??
[SuperSU] ktmom:
I'm starting to believe, (my own personal opinion) that CCMT's plans are not inline with what people here (xda) want. Nor that this population is their target audience. I think they are heading off in their own directing and trading against the reputation built by Chainfire for supersu. The same way you don't see development threads here on xda for other root apps, I suspect they are fine with running their own thing from their own platforms (FB, website).

The discussion here may be a useful vent for the disappointed, but I highly doubt they're even aware of it.

"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
[SuperSU] badhabit_wb:
I agree. We'd be a good beta test source for them if they would let us though.
[SuperSU] DB126:
Don't bet on it. Internal focus may have changed. Could be working on something else. Might have determined product can not be successfully commercialized/monetized. Not all decisions play out as intended.
[SuperSU] Angry_ATC:
Hello, boys and girls! Just trying to recover some data from the inner memory of wife`s Samsung Galaxy S5 mini. Exploring its memory and using command "cat/proc/partitions" found this:

shell@kminilte:/ $ cat /proc/partitions

major minor #blocks name

179 0 15388672 mmcblk0

179 1 4096 mmcblk0p1

179 2 4096 mmcblk0p2

179 3 20480 mmcblk0p3

179 4 4096 mmcblk0p4

179 5 4096 mmcblk0p5

179 6 4096 mmcblk0p6

179 7 1024 mmcblk0p7

259 0 8192 mmcblk0p8

259 1 10240 mmcblk0p9

259 2 12288 mmcblk0p10

259 3 8192 mmcblk0p11

259 4 1024 mmcblk0p12

259 5 32768 mmcblk0p13

259 6 1024 mmcblk0p14

259 7 1024 mmcblk0p15

259 8 12288 mmcblk0p16

259 9 1024 mmcblk0p17

259 10 2355200 mmcblk0p18

259 11 307200 mmcblk0p19

259 12 10240 mmcblk0p20

259 13 12574720 mmcblk0p21

179 16 4096 mmcblk0boot1

179 8 4096 mmcblk0boot0

253 0 1048576 vnswap0

shell@kminilte:/ $

So I need to recover some blocks let it be mmcblk0 (15Gb), mmcblk0p21 (12Gb), etc... with the help of daemonsu. Have no any idea how to do this, please help.
[SuperSU] badhabit_wb:
I flashed the patched-boot image and then, after a reboot, booted to a twrp image and installed the zip wiped cache/dalvik and now it's working. Might want to give that a shot.
[SuperSU] jcmm11:
What exactly are you trying to recover? Those are data partitions that you can backup with TWRP for the most useful ones or FlashFire if you want more esoteric partitions.

If you really want to go the manual route then you want the dd command. I recommend NOT going the dd route.
[SuperSU] daddylonglegs:
I am glad to see I am not the only one who could not get Magisk to work on the Pixel on 8.1 either. Everyone telling me it's as simple as just flashing the zip had me ripping my hair out for 7 hours yesterday trying to get it to work.

I am hoping a root solution happens soon. T-Mobile is aware of my tethering and I am 500MB away from my tethering limit :eek:

---------- Post added at 12:08 AM ---------- Previous post was at 12:06 AM ----------

What's the patched boot image? Some sort of special boot image for Pixel users that want to use Magisk? Where do I obtain it?
[SuperSU] badhabit_wb:
Did you try what I did to get my pixel working? It's been working fine since lunch on magisk.
[SuperSU] daddylonglegs:
I think you missed my reply by a few seconds. We must have posted at the same time :)

What's the patched boot image? Some sort of special boot image for Pixel users that want to use Magisk? Where do I obtain it?
[SuperSU] TonikJDK:
Magisk creates the patched boot image and you fastboot flash it. If you are unaware of that step it would explain your problem.

Flash the Magisk app. Put a copy of the stock boot.img file in your ohone. Fire Magisk up and select install and select the patches boot method. That creates a modified boot IMG you then flash to your phone.
[SuperSU] daddylonglegs:
Wow, I had no idea about any of this. Everybody was saying just go into TWRP and flash it, then install the magisk.apk and that was it. No wonder it didn't work for me!

The only thing I am confused about: you say flash the magisk app. I am assuming you mean magisk.zip in TWRP. Then you said to put a copy of the stock boot.img file in my phone, but then to fire Magisk up and select install. When you say "fire Magisk up" do you mean Magisk Manager? Because I am unsure of how to "open" the Magisk app in TWRP. Sorry if I sound like an idiot.
[SuperSU] TonikJDK:
Yes, flash the zip and yes open Magisk Manager.
[SuperSU] badhabit_wb:
Actually magisk manager will create the patched root image. You have to get the stock image from the Google pixel image. if you extract the image to a folder there will be another zip inside and the boot image you need is in that.
[SuperSU] TonikJDK:
Well said, clearer than I was.
[SuperSU] daddylonglegs:
Open Magisk Manager in Android? But when I flash the zip and boot Android I can't even get into Magisk Manager because of all the SystemUI crashes.
[SuperSU] badhabit_wb:
I'd start over. Flash the factory image. Then load the manager and make your patched image. Flash the patched image. Then boot to the twrp image and flash the zip.
[SuperSU] daddylonglegs:
OK so in this order (after flashing the factory image):

1) Install Magisk Manager apk in Android

2) Run Magisk Manager and have it load my stock boot.img and patch it.

3) Boot into TWRP and flash the Magisk-boot.img

4) Then in TWRP flash the magisk.zip from the Magisk thread

Is this correct?
[SuperSU] osm0sis:
Speaking of "the Magisk thread" ... ;)
[SuperSU] badhabit_wb:
I fastbooted the boot image,fastboot flash boot patched_boot.img, and used twrp for the zip.

when you run manager it will put the flash image in the magisk root folder. Extract it to your pc in the folder with platform tools then load it with fasboot commands.
[SuperSU] Wolfcity:
That´s how it´s meant to be.

If it shouldn´t work and you get a bootloop flash your stock boot image again and use the magisk unistaller.zip.
[SuperSU] Badger50:
We'll see if it registers :cool:
[SuperSU] TonikJDK:
1 Copy factory boot.img to phone

2 Boot to TWRP and flash the Magisk zip

3 Boot normally, start manager and patch the boot.img

4 Copy patched boot.img to computer.

5 Boot to stock recovery and fastboot flash the patched boot.img

Anymore trouble or questions please hit the Magisk thread or start a new thread. We will help you there. It's unfair that we are doing this in the SU thread.

EDIT for step 3. Start Magisk Manager and hit settings and put it in beta mode, then patch the boot.img
[SuperSU] martyfender:
I am on a much different device, but a few days ago I successfully backed up my these "esoteric partitions" with the dd command and flashed them in fastboot mode, to a different device with the same rom.

Here are links for the dd commands I used:

https://stackpointer.io/mobile/android-mmc-mmcblk-partition-layout/259/

https://www.xda-developers.com/how-to-discover-hidden-fastboot-commands/

I have never used flashfire, I have heard of it, but never knew much about it.

Thanks for pointing this out. I will give it a try. entering the proper commands in the terminal are tedious, at best.

Can flashfire also restore these partitions?

This is OT, but does anybody know how to pull the IFWI from an Intel device and restore it to another Intel device?

It is my limited understanding that this is where my system bios lives.

Thanks, in advance. Please let me know if you know a better xda thread where this request would be better asked.
[SuperSU] Angry_ATC:
There are some deleted photos and videos. And I suppose that is block named "mmcblk0" of 15Gb size. Just be advised - I`m complete amateur in this type of activity, so I can`t even imagine the command or it`s sequence which help to copy that block to my computer in the type of ".raw". I hope I`m understandable :confused:

And ok will look at this progs
[SuperSU] Juhler:
Does anyone have a working procedure for rooting with SuperSU 2.82 SR5 on Pixel 8.1?
[SuperSU] Sh0X31:
No we wait to. Use magisk until a new Version of SuperSU is released.
[SuperSU] DB126:
Hear that CCMT? Hum, all I hear is silence ...
[SuperSU] :
Hi,

Why I can't have TWRP and SuperSu co-existence on my Xiaomi Mi A1? When I want to reboot to the system, my phone reboots to TWRP... Can't have a fix for the Xiaomi Mi A1? The Xiaomi Mi A1 uses a/b system.
[SuperSU] xell75:
On devices with less security locks like an Galaxy S4, SuperSU 2.82 SR5 works on an Android 8.1 Custom Rom.
[SuperSU] osm0sis:
Working fine here on my Nexus 5X running stock 8.1 as well. I incremental OTA'd through FlashFire and everything. :good:
[SuperSU] jcmm11:
If you're trying to recover deleted photos and videos you're much better off with something like https://play.google.com/store/apps/details?id=com.defianttech.diskdigger

Copying the partitions won't really help you.

---------- Post added at 04:37 PM ---------- Previous post was at 04:28 PM ----------

Yes FlashFire will restore as well. Plus do a few other things. It's powerful, just be careful - it's powerful enough to brick your device. Read all the help stuff (including on Chainfire's site. Links from app. Heed the warnings. Note that the equivalent to a dd dump is a raw dump.

IFWI I know nothing about. Presumably it'll be in a partition with a name that you can recognize.
[SuperSU] gverma1:
Pixel XL 2016 marlin - flashed Google factory image 8.1 using fastboot after removing -w.

Disabled pin and fingerprints.

Fastboot boot latest twrp IMG.

Then in same session, flashed latest twrp zip, ElementalX 3.00, and SuperSU 2.82SR5. It all went fine.

Booted system - bootlooped a couple times and then came back on.

It had Suhide already from my previous install.

Everything working just fine.
[SuperSU] srqrob:
I've heard that this works with Marlin (XL) but not Sailfish. I'm also Marlin. Any similars with success?
[SuperSU] martyfender:
I removed because it was OT.
[SuperSU] Angry_ATC:
I`m just guided by some posts about adb, where one guy solved the problem manually using some complicated commands to copy and decode partitions. Sorry can`t insert any link here before i collect 10 messages :)

It`s on russian, but quite easy to understand what does this man do and why. Seems to be efficient, but not in my case. I just have a lot of unknown memory problems on this Samsung and not able to install anynthing on it, even insert an SD-card =/
[SuperSU] DB126:
Seems this thread (like so many others) is being hijacked with general troubleshooting questions that have little (really nothing) to do with SuperSU in general and 2.82 SR1 in particular. Another side-effect of CCMT's lack of stewardship which leaves the door open for such unfocused dialog.
[SuperSU] martyfender:
Yes, I removed my post as it was OT. Perhaps I need to read how to get help as I have no clue where to post my removed question?
[SuperSU] DB126:
Make liberal use of search tools, either Bing/Google/etc with "XDA" imbedded, XDA labs or some other method. Keyword selection is key. Be prepared to read, read and read some more until you find helpful nuggets to build on. You might initially come up empty only to find a partial solution days/weeks/months later while working on something else. Concise, well focused questions score better responses. Especially if the answer is leverageable beyond the current situation. Kinda the way it goes...
[SuperSU] martyfender:
Thanks, I posted here: [Ask Any Question][Newbie Friendly]
[SuperSU] borglogic:
I've been flashing the Android 8.0 OTA updates for months with out any problems. With Android 8.1 I needed to update TWRP to 3.2.1.0 to fix the password error. When I try to flash SuperSU 20171001 it errors at apply sepolicy.

Am I doing something wrong, or does SuperSU need an update?
[SuperSU] Alxoom33:
Need more details, including what device you are using.
[SuperSU] badhabit_wb:
It needs an update. If you remove password and reboot TWRP will work but SuperSU won't. Magisk works.