yashsingh1/xdaforums huggingface dataset:
[SuperSU] Wolfcity:
But you can read:

Read the first post. There you will find download links for superSU. They are for all devices.

Doesn't matter this was sent from
[SuperSU] mehsad89:
I need version stable for cm13

No for test

first post download link supersu version beta for test
[SuperSU] bdwilk:
Stable versions.

http://xdaforums.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703/post68475511
[SuperSU] :
Test versions runs fine on my S3 with CM13 and S4 with CM14.1
[SuperSU] andy hall:
use the stable version for cm13, flash the zip
[SuperSU] ambasadii:
great so I not need to do the same :)

[MENTION=631273]Chainfire[/MENTION]

but I attach my boot.img (S7 Edge G935F) patched with SR4 without init (patch) that all worked without any bug!
[SuperSU] smohanv:
Installed systemless using TWRP terminal command. How would I now find that it is flashed systemlessly. Thanks.

Sent from my EVA-L09
[SuperSU] shaggyskunk:
Searching the Thread for Systemless and you would have found this (among other posts) post with information on how to verify if you have Systemless ;)

http://xdaforums.com/showthread.php?p=67135909

Sent From My SM-N910W8 ??
[SuperSU] Akhilesh S V:
Hi guys what is the correct way to upgrade from SR4 to SR5
[SuperSU] Ja_som:
Download SR5 zip file and flash it
[SuperSU] andrew2432:
Running sr3 on cm13 runs fine
[SuperSU] Hermankzr:
I was successfully rooted with the official SuperSU-v2.78-201609011115.zip but it was stated as systemless.

Is it fine? I don't exactly know if the latest CF-Auto-Root is systemless or not or all current root on MM is systemless.

I don't care about it. Just wanna know difference between systemless and installed as system.

Oh, i have rooted this way :

> flashed TWRP 3.0.2.0 via ODIN

> once boot to TWRP, there's an option to keep it read only or allow modify system. I choose allow.

> flashed SuperSU-v2.78-201609011115.zip via TWRP

> reboot

Done. That's how i get root in case someone confuse about root. You can try with SR5 or CF but do it at your own risk !
[SuperSU] ayush rao:
Deleted
[SuperSU] ambasadii:
yes exactly restoring orginal file_contexts.bin solves the problem
[SuperSU] ulxerker:
the differences and advantages of systemless root you can find here.
[SuperSU] denyo81:
Finally! The SR5 release fixed the WiFi problem on nougat for my klte.

Big thanks Captain Chainfire [emoji41]
[SuperSU] ruchern:
https://plus.google.com/+Chainfire/posts/24xhJN724HG

Does this work for flashing ROMs (especially CM) that uses their own superuser app?

[MENTION=631273]Chainfire[/MENTION]
[SuperSU] shaggyskunk:
Sure does - Most CM Roms require you to go to Developer Options and Root Access to enable Apps and Adb - I don't - And just Flash SuperSU v2.78 Stable or v2.78 SR5 which I'm currently running on all my devices running CM14.1 Based Roms.

Sent From My SM-N910W8 ??
[SuperSU] ruchern:
I am referring to the FRP part.

I am now running cm-14.0. Just want to check if I can prevent CM's root from installing with that settings whenever I update it.

It says Factory Reset and didn't say anything regarding updating ROMs.
[SuperSU] zelendel:
Cm doesn't use this superuser and no. The only way to prevent the it is to build it without root access.
[SuperSU] Idebutterpiep:
SuperSU v2.78 SR5 by Chainfire works on Nougat 7.0 Beta 1 Samsung S7 edge.

Thank you Chainfire.
[SuperSU] bdwilk:
SR5 working on OnePlus One running RR N

It also rooted well on Cyanogen OS 13.1
[SuperSU] BrianDickens:
Thanks for SR5, SR4 wasn't working on cm-14.1-20161202-NIGHTLY-titan (Moto G (Titan)), no SIM card detected. With SR5 everything is perfect again :)
[SuperSU] actinhic:
SR5 works on CM14.1 trltexx. Thank you!
[SuperSU] _alexndr:
Are you sure that there are no issues at all? I'm asking because I (and a few other users) experienced major issues described here:

http://xdaforums.com/showpost.php?p=69870416&postcount=8225

Steps I did in S7 edge G935F:

1. Flashed Nougat 7.0 Beta 1 (G935FXXU1ZPK4) using PC Odin

2. Set up Google account (as Beta 1 performed wipe data)

3. Flashed TWRP 3.0.2.4 using PC Odin

4. Entered TWRP and chose "Keep read only"

5. Flashed SuperSU 2.78 SR5 from external sdcard

6. Flashed ZPK4 stock recovery using PC Odin (I do not need TWRP anymore as I want to keep original /system)

As you can see - clean install and a lot issues... :(
[SuperSU] andreoide:
Deleted by myself sorry
[SuperSU] olejonbj:
On CyanogenMod 14.1 Android 7.1, can I just flash this in TWRP as usual, or do I have to do anything special in TWRP or elsewhere?
[SuperSU] ipdev:
[MENTION=3573070]olejonbj[/MENTION]

Depends on your device and rom.

(A little more info might help. ;) )
[SuperSU] olejonbj:
[MENTION=7280276]ipdev[/MENTION] Google Nexus 5 (original) running CyanogenMod 14.1-20161202-NIGHTLY-hammerheadcaf (the latest recommended version, and also the latest TWRP for Nexus 5).
[SuperSU] bdwilk:
Flash in TWRP
[SuperSU] ipdev:
[MENTION=3573070]olejonbj[/MENTION]

Installed fine on my Nexus 5 and 7 running official cm nightly using twrp.

- Not sure about caf builds.
[SuperSU] Techinator:
would i be able to install this into a custom rom without having to boot into a bootloader and go into my recovery?
[SuperSU] egingell:
Unlikely.

Side note: I never had this problem with my SGS4 with 4.4.2.

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] andrew2432:
Don you run a custom os on that smg900?
[SuperSU] egingell:
No.

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] andrew2432:
Sr5 does well??
[SuperSU] egingell:
I don't know. I gave that phone to my mom.

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] Azlun:
Will su.d works before Android system init process?

Anybody have been tried to use systemless bind su.d/ scripts to override init*.rc system/ root folder file such as init.rc or init.common.usb.rc?

I am trying to open the USB Diag COM port for Pixel XL to make more LTE bands enabled for all.

so I want whether know su.d/ is right place to write su.d/0000enableDiag in a systemless purpose,

mount -o bind su/sysroot/init.common.diag.rc.userdebug system/init.common.diag.rc

or else, another approach: writing a flashable zip file with update-script may be not my strength currently.
[SuperSU] Chainfire:
Nothing runs before init except the kernel itself.
[SuperSU] Azlun:
Thank you very much for Dear sir! Then su.d runs scripts after Android init, so even I success to make init.common.diag.rc mount with the user debug ver. copy. It will not make system to handle sys.usb.config=diag,adb correctly, I will turn to flashable zip coding with systemless bind feature inside it.
[SuperSU] bgcngm:
[MENTION=631273]Chainfire[/MENTION], Xiaomi Mi 5 owners have been facing installation issues when data and cache are converted to F2FS. I usually stick to CM's built-in root functionality, but back when used SuperSU, my device was running with ext4 filesystem and this was never a problem. Apparently, the installer is failing to mount /data (mounted by default because Xiaomi Mi 5 has internal storage only - no external sdcard) and everything else fails. Is this a known issue?

Could you please take a look at the attached official TWRP recovery log?
[SuperSU] Idebutterpiep:
Sorry today I have issues with the camera app. It closes before I want to take photos.:crying:
[SuperSU] Cares:
I'm going to assume that SR5 is compatible with 7.1.1 that was just released today for the Pixel. Will report back...
[SuperSU] Evo_Shift:
Just updated to 7.1.1 and flashed SR5 and everything seems to be working. I didn't actually flash TWRP but just booted into TWRP to flash SuperSU.
[SuperSU] Chainfire:
Why are you assuming it fails to mount /data ? It rather looks like it fails to mount /data/su.img
[SuperSU] Cares:
Or you could read what I wrote........and not be pretentious about it.

7.1.1 was released today. SR5 was released 11/30. How exactly would his SR5 release be relevant to something in the future?

Edit: Tested my root apps and whatnot. Everything seems to be working properly with SR5 and 7.1.1. I actually flashed TWRP but I think I might revert to stock recovery and boot TWRP and flash SuperSU in the future.
[SuperSU] olejonbj:
[MENTION=7280276]ipdev[/MENTION] Just flashing in TWRP worked yes. A few reboots happened after reboot, as described. Then everything normal.

Now my question is, will choosing a Full Unroot in SuperSU fully unroot my phone so no app can detect that I run CyanogenMod 14.1 (Android 7.1)?

EDIT: I use CAF from here, it is official. Seems to be a good choice. REMEMBER: You need the caf version of TWRP to use it!
[SuperSU] CyberZeus1977:
Is SuperSu still disabling force-encryption?

Thanks

Sent from my interstellar 6P!
[SuperSU] ipdev:
Short answer - No.

(Tested only because it worked on an unofficial cm13 build awhile ago, don't remember what device it was.)

Long answer - Not for this thread. (Look for me in the caf thread, I might have a question for you. ;) )
[SuperSU] olejonbj:
[MENTION=7280276]ipdev[/MENTION] No way at all to unroot CyanogenMod 14.1? I found this website with specific instructions for Nexus devices and Marshmallow, as it introduced systemless root, so I guess it applies to Android N as well. Will NONE of these ways work? And if I try, can I just restore my TWRP backup and everything is back to normal CyanogenMod rooted?

https://www.google.no/amp/www.howtogeek.com/248619/how-to-unroot-your-android-phone/amp/
[SuperSU] ulxerker:
yes ... so if you're on a decrypted device it'll stay like that.
[SuperSU] ipdev:
I never said you could not unroot ....

(I went back and forth a few times between root and no-root tonight on my n5.)

- Last reply about this in this thread. We can pick it up in an n5 thread.
[SuperSU] r80ies:
I updated to stock 7.1.1 on my 6P and I cannot get Viper4Arise to recognize root. Any thoughts or suggestions would be appreciate.
[SuperSU] ruchern:
Install SuperSU APK and do a permanent unroot from the settings tab.
[SuperSU] olejonbj:
Installing the APK doesn't work on CyanogenMod 14.1, it wants to update the binary which doesn't work in none of the two ways and causes bootloop. BUT flashing SR5 straight from TWRP works fine.

One question: If I do a full unroot now when SuperSU is working, will I be able to restore from a TWRP backup if unroot fails, without any problems?
[SuperSU] objecttothis:
Device: Motorola Moto X Pure XT1575 (Clark)

OS: Android Nougat 7.1 AOSP (CM 14.1 Nightlies)

Problem: In the CM File manager I get an error when trying to browse to my external SD Card telling me that I need elevated permission to access the folder and that I should try switching to root access mode. When I switch to root access mode it pops up a toast notification telling me that SuperSU granted root access to the CM File manager. When I try browsing again I get the same error.

The SuperSu log is telling me that SuperSu Pro is required for that feature. Are you realoy telling me that I can't access my sd card unless I pay 3.75USD?

SuperSU 2.78 SR5 was flashed via twrp recovery.
[SuperSU] bdwilk:
It's a cm bug not supersu bug. Use a third party file manager.
[SuperSU] anshsharma123:
Does this latest version break sensors on 7.1? Like the previous versions?
[SuperSU] bdwilk:
Never had a broken sensor from SuperSU running CM14.1 or RR N (7.1)
[SuperSU] anshsharma123:
Okayy, for me the previous versions broke sensors on Cm14.1 (Kenzo)
[SuperSU] bdwilk:
You didn't say for which device earlier so I just answered for "in general" Everything runs great on OPO, ASUS Z00L, LG G2 F320.

2.78 SR5

CM 14.1 and RR N
[SuperSU] ruchern:
Install the binary, do not reboot then immediately do a full unroot from the settings tab.

After which you can reboot and flash SR5 over it and see if it works.

Yes you should be able to restore a TWRP if unroot fails. There should be no problem if your backup image is no problem.
[SuperSU] olejonbj:
Thanks. There's no binary to install as I flashed SR5 from TWRP. Anyway if a restore can be done then why not try. Got another Samsung Galaxy S II with CM 12. 1 I can try it on first, just to check.
[SuperSU] delro92:
Just update my stock Nexus 6P to 7.1.1. Is it possible to install SuperSu in /system? I need root to survive a factory reset but systemless can't do that. How do I get traditional/system root?
[SuperSU] racing_md:
Got to root/vendor/etc and rename audio_effects.conf file to audio_effects.conf.bak reboot and try again. I had the same issue
[SuperSU] mobileman88:
Flash it with flash fire. No need to flash system root
[SuperSU] zer0se7en:
Seems like a nice update. Loving the Display size setting. We can change DPI.

Had no problems updating from 7.0 to 7.1.1. Now with TWRP and rooted with SuperSU SR5.
[SuperSU] _litz:
Updated my Nexus 9 to 7.1.1, flashed SR5 ... SU app opens without error.

But nothing is able to request root ... requests just sit there forever ...
[SuperSU] mobileman88:
Give it some time to settle
[SuperSU] ulxerker:
what phone do you have?
[SuperSU] Idebutterpiep:
After three days of using same issues you wrote above.:crying:
[SuperSU] ruchern:
Root request takes awhile after you just flashed SuperSU.
[SuperSU] MrKaon:
Everything is perfect on Nexus ??
[SuperSU] ulxerker:
yep, as always ... Nexus just rulez and is always the first in getting updates :cool:
[SuperSU] zeroprobe:
nm
[SuperSU] grep_i:
Which Nexus guys and what are we talking about.

I guess not Nexus Samsung i9250 ???
[SuperSU] :
Exactly how many reboots?

---------- Post added at 05:04 PM ---------- Previous post was at 04:58 PM ----------

@chainfire is it possible to skip the mount Img file and let's say try load the files from /cust or /product partition? The files should be working from these partitions since they're loaded on boot as well. This way we could modify the cust partition and let the files be there
[SuperSU] vandyman:
Nexus 5X and Nexus 6P.
[SuperSU] olejonbj:
I think it rebooted once or twice.
[SuperSU] :
Well that's normal. Specially if you u use systemless su
[SuperSU] WhammyDroid:
Has anyone noticed/reported an issue with the SuperSU app not showing log information after updating to SR5? I was on SR1 previously. Updated to SR5 when 7.1.1 dropped for the Nexus 9.
[SuperSU] WhammyDroid:
[MENTION=631273]Chainfire[/MENTION], screenshot of location included.
[SuperSU] olejonbj:
Just flashed again and it rebooted once, just to add that to the previous question. It reboots almost immediately after rebooting once, and then boots normally.

---------- Post added at 09:43 AM ---------- Previous post was at 09:42 AM ----------

One in my case.

1) Flash zip

2) Reboot system option in TWRP

3) Phone reboots

4) Just a few secs go by with the Google logo displayed (Nexus 5)

5) Reboots again into normal operation
[SuperSU] ashyx:
You're missing the point, it doesn't matter how you installed supersu, you can still use the uninstaller in the supersu app.
[SuperSU] :
Yeah as said that's normal.
[SuperSU] storm119:
After updating RR N from 7.1 to 7.1.1 today....SuperSu SR5 still working good as for now ;)

edit: btw anyone know if there is any ill/side effect from 5 December security patched with SuperSu...?

TIA
[SuperSU] FernBch:
SR5 is working on the Verizon Pixel. All seems fine...
[SuperSU] UltraM8:
Guys, how can i mount /su to flash scripts thru TWRP? Making an update-binary script
[SuperSU] jcmm11:
See the SUmount

script from here
[SuperSU] iampatricktan:
Guys, how to install the latest SuperSU in Systemless mode? I'm kinda confuse.
[SuperSU] jcmm11:
It defaults to systemless. So just flash it and you should be good to go
[SuperSU] ziaulh.ch:
Works fine on HTC ONE M9 Android Nougat!
[SuperSU] dratsablive:
I tried flashing on my M9 and got bootloop/reboot. Will have to do a system restore with software from HTC site and then try latest TWRP.
[SuperSU] DAS82:
2.78-SR5 has been working fine on my Galaxy S5 with Marshmallow MMB29M.G900PVPU3CPG1 stock ROM.

Thanks!
[SuperSU] youssef0789:
Why is SuperSU SR5 Breaking The Sensors On Android Nougat On The Xiaomi Redmi Note 3 SnapDragon Variant
[SuperSU] CyberZeus1977:
If I change kernel, must I flash SuperSu again to keep root?

Sent from my interstellar 6P!
[SuperSU] bdwilk:
Not in my experience.
[SuperSU] CyberZeus1977:
Thank you!

Sent from my interstellar 6P!
[SuperSU] ziaulh.ch:
http://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133 This one will work just perfect!
[SuperSU] jcmm11:
Actually if you flash SuperSu after a custom kernel you may find that you have to flash the kernel again and that the SuperSU install replaced the kernel
[SuperSU] Ibuprophen:
I just want to know if there is anyone who had success or failure, specifically, who has a Verizon Samsung Galaxy S3 (D2VZW), who flashed this Beta of SuperSU 2.78 SR5 when installing the new CM14.1 Nightly?

I just wanted to get feedback somehow from someone who has this specific device as asked above.

Thank you all!
[SuperSU] ruchern:
I am hoping that this works.

echo "FRP=true">>/data/.supersu

It's annoying to lose Root especially CF SR root after flashing a ROM.
[SuperSU] grep_i:
Than use FlashFire it has an option to keep root during your flashing, it's called ever root
[SuperSU] ruchern:
Oh, I see thanks!
[SuperSU] dratsablive:
That's the one I used.
[SuperSU] ziaulh.ch:
IM on M9. It worked here. Donno your device mate.
[SuperSU] Shailesh1711:
Has anyone tested this on LeEco Le 1s. Will it help me to root systemless on my device?
[SuperSU] dratsablive:
No biggie, downloading the developer ROM to reflash it.
[SuperSU] Ibuprophen:
[MENTION=631273]Chainfire[/MENTION] It was a funny thing i had noticed after flashing both the SuperSU 2.78 SR5 and the Stable version (at separate times of course when i performed a fresh install of the ROM) when i had tried out the new CM14.1 Nighty...

Both of them flashed just fine without any errors but, within the app, i had changed the language option from System Default to the English US and it never stays.

I works in CM13 but, not CM14.1.

Though this is a personal preference and not a show stopper but, it was odd behavior for SuperSU.
[SuperSU] Fif_:
For reference, this seems to happen when the app that requested su dies before SuperSU had a chance to post the su confirmation dialog.

It would then be harmless.
[SuperSU] Bryanx86:
Is there a way for SuperSU to work on an f2fs /data partition? Getting error in twrp and gets stuck in bootloop. I have a nexus 6p running nitrogen os with latest flash kernel. Thanks for any help.
[SuperSU] thelangosta:
I'll get around to this at some point this evening. I just downloaded the gapps but need to get the SuperSU sr5 and the latest cm nightly. My d2vzw is not my daily driver so I can't test everything.
[SuperSU] Ibuprophen:
I appreciate you taking the time to look into it.

I'm not in a race... Patience is a virtue :cyclops:
[SuperSU] olejonbj:
[MENTION=631273]Chainfire[/MENTION] Would be nice if the first post contained the MD5 sum of the zip file so one can be sure :good:
[SuperSU] scary alien:
The .zip files are actually signed, so you can use the jarsigner utility (part of the Java JDK) to verify the integrity of the whole .zip file and the SHA1 digests of each file contained therein:

c:\Users\Scary Alien\Downloads>jarsigner -verify SR5-SuperSU-v2.78-SR5-20161130091551.zip

jar verified.

Warning:

This jar contains entries whose certificate chain is not validated.

Re-run with the -verbose and -certs options for more details.

c:\Users\Scary Alien\Downloads>​

My AFV app will also do this if you want to do it from your Android device (select the file, long-press, select "Verify Jar-type File").

Cheers!
[SuperSU] olejonbj:
Thanks. I'm an app dev so JDK is there, and in PATH, and I'm familiar with that, but Windows no thanks ;) Is this what TWRP does when ZIP validation is on? In that case it would be nice. I always do a shasum of my CyanogenMod Nightly ROM for instance before flashing in TWRP.
[SuperSU] scary alien:
You're most welcome :).

If you're using Linux (or a Mac), you'll also find/have the jarsigner utility on your PC (pretty sure it does require the JDK being installed).

Yes, TWRP will use that same mechanism for verifying the signed .zip file with the validation option you referenced (although they likely use the APIs in their code versus the actual jarsigner utility).

Always happy to see and hear that folks are checking the sums/digests of their files before flashing--that's the whole reason I wrote my AFV app here back in 2010 (with a big thanks and shout-out to [MENTION=2341536]bftb0[/MENTION] if he's still out there :)).
[SuperSU] olejonbj:
Great. Yes when it comes to important stuff I do checksums. I'm a Linux server admin/expert as well so, yeah, a habit.
[SuperSU] :
I'm using LG G3 with Android Now rom. Installed 2.27 through Flashify, but when I open Supersu it just keeps loading(spinning arrow) and nothing happens. What should I do to fix it? I've also, of course, lost root.
[SuperSU] kmcphee:
Comment deleted since someonce took offence
[SuperSU] jmcdonald58:
All went well here MotoX 2014-Many Thanks
[SuperSU] SamuriHL:
I see no one's responded to this yet. You can't, simple as that. Locked phones need a root exploit. There is no way to simply flash the zip. That's only for us who run unlocked phones with custom recovery available.
[SuperSU] USBhost:
Thats why i never get a device that i know wont have root

Good bye at&t, Verizon, sprint

Hello T Mobile
[SuperSU] starbase64:
[MENTION=631273]Chainfire[/MENTION]

The app called "lux" breaks SuperSU popup window, can't press allow or denied.

Here is a log: https://www.dropbox.com/s/2inhybr7n1ejk75/Lux.zip?dl=0
[SuperSU] User_99:
Check Tapjacking in SuperSU settings and you are finished. Already known behavoiur of such apps...
[SuperSU] playahate:
Nexus 5, flashed stok kernel, beta 2.27, flashed ElementalX-N5-2.03 - working ok.

I can add to working apps CallRecorder (recording method CAF + mp3 output)
[SuperSU] filderge:
Flashed using wugfresh's toolkit. Worked flawlessly. Thanks!
[SuperSU] TR2N:
Flashed Stock Boot image over Franco, upgraded to 2.27 and SuperSU works perfect with stock. But flashed franco again.. ;)

Thank you Chainfire!
[SuperSU] VivaErBetis:
That's because you have Tapjacking protection active in SuperSU options. It's a security measure.
[SuperSU] starbase64:
Yes, now works.
[SuperSU] zfuyuan:
Device: Nexus 5 Lollipop with 2.27

Kernel: Stock

Problem: HiroMacro not working.

Steps: Install HiroMacro, Enable Touch Location Debug with the app settings, Start service, Try touching anywhere and location debug does not respond.

I also tried running my previous scripts with location debug off, which does not work either.

No issue with AdAway and Wakelock detector.
[SuperSU] scanno:
Nexus 10. Supersu crashes after boot and manually opening. Stock Android 5.0 flashed with TWRP 2.8.2.0
[SuperSU] yaonos:
v2.27 is working on my N7 today. I just flashed it again now that BBS is no longer installed on my device. It took some time for SuperSu to prompt me in order to allow root accesses to my apps and I still get this same AVCs each time an app requests root. :

W/app_process32_o( 7688): type=1400 audit(0.0:59): avc: denied { write } for name="system@framework@boot.art" dev=mmcblk0p9 ino=326403 scontext=u:r:shell:s0 tcontext=u:object_r:dalvikcache_data_file:s0 tclass=file

The only things changing in those AVCs are the numbers between parentheses following W/app_process32_o and audit. Inode 326403 is /data/dalvik-cache/arm/system@framework@boot.art :

# ls -alZi /data/dalvik-cache/arm/system@framework@boot.art

326403 -rw-r--r-- root root u:object_r:dalvikcache_data_file:s0 system@framework@boot.art
[SuperSU] :
Did ya use CFAR before??? :confused:

---------- Post added at 08:47 PM ---------- Previous post was at 08:47 PM ----------

Please don't spam here!!! :mad:
[SuperSU] mbirth:
I always wonder why people prefer Lux with its stupid overlay (e.g. black becomes dark red) over CF.lumen which really changes the colour temperature (black stays black)...
[SuperSU] raburs:
please help me!

can i flash beta 2.27 over auto root Lollipop 5.0 ?

and someone please give me the link for stock kernel 5.0
[SuperSU] scanno:
No I did not flash the modified kernel for the nexus 10 because in the release notes it stated that 2.27 could be used without a modified ramdisk.