SuperSU v2.78 SR4 (Pixel TWRP)
Posted on 2016-11-15, 77 comments, 385 +1's, imported from Google+/Chainfire

NOTICE: This content was originally posted to Google+, then imported here. Some formatting may be lost, links may be dead, and images may be missing.

If you are not using a Pixel device, the only change in this SuperSU release is improved detection of file-based encryption. This should get rid of the issue where some Nexus devices suddenly got encrypted after flashing SuperSU.

The rest of this text applies only to Pixel and Pixel XL

Earlier today Dees_Troy released the alpha of TWRP for these Pixels. TWRP unfortunately breaks the boot-to-root images I prepared for the Pixels earlier. We do talk so this came as a surprise to neither of us.

As everybody probably knows by now, both normal Android boot as well as recovery share a boot image now. This requires some trickery to get everything we want up and running.

Both SuperSU and TWRP need to replace /init. Funnily enough, my first roots for the Pixels actually did this in such a way that flashing it over TWRP would not have been an issue (not the other way around, though), but this functionality was later removed as a size optimization.

That optimization has now been adjusted to keep both working at the same time.

Aside from that, there have been various fixes to the installer script to work around the differences between the boot-to-root/CFAR environment and TWRP.

That being said, issues can occur, so please take care to follow the instructions exactly.

It is very important to keep in mind the differences between using TWRP and flashing SuperSU through the ZIP file, or using boot-to-root (and in the future: CF-Auto-Root).

When switching between the two, you must re-flash your firmware's stock boot image. Advised is to flash to both boot partitions:

fastboot flash boot_a /path/to/boot.img

fastboot flash boot_b /path/to/boot.img

Failing to do this can lead to bootloops, or cause the device to always boot into Android (instead of recovery), or cause the device to always boot into recovery (instead of Android).

boot-to-root / CF-Auto-Root

These have not been updated to SR4, just use the SR3 version from the post linked further below.

  • reflash stock boot.img

  • fastboot *boot /path/to/boot-to-root.img*

You will end up with only SuperSU.


See Dees_Troy's post linked below for the links to download both the twrp img and zip files.

  • reflash stock boot.img

  • fastboot *boot /path/to/twrp.*img

  • TWRP install *twrp.*zip

  • reboot into recovery

  • TWRP install

You will end up with both SuperSU and TWRP.

Full unroot

If you're using TWRP, please note that the 'full unroot' functionality present in the SuperSU GUI will (if it works at all) restore the original TWRP boot image from which SuperSU was flashed, rather than return you to the real stock boot image.


Let me just note again that suhide is not compatible with the Pixels (or Android 7.1 for that matter). Expect bootloops if you try to use it.


Flashable ZIP download:

SuperSU BETA (SR) thread at XDA:

Dees_Troy's Pixel (+XL) TWRP Alpha post:

Pixel 'boot-to-root' images with v2.78 SR3:


  • sukernel: improve FBE detection

  • suinit: TWRP compatibility on slot-based systems

  • ZIP: TWRP compatibility on slot-based systems

SuperSU Download

michael pap commented on 2016-11-15 at 18:59:

Ok is this version works in s7edge on N beta rom???

Chainfire commented on 2016-11-15 at 19:01:

+michael pap no, and until there's a downloadable flashable firmware for me to test with, it won't be.

michael pap commented on 2016-11-15 at 19:02:

But there is, i download mine from xda thread

Chainfire commented on 2016-11-15 at 19:08:

+michael pap please link a non-edge firmware then. I'll put it on my list to check out. However, the S7 is my daily-driver so I don't like to tinker with it much.

Aaron DeArmitt commented on 2016-11-15 at 19:08:

dang, u fast!

Aaron DeArmitt commented on 2016-11-15 at 19:10:

so after we flash stock boot, and do the steps to get superSU and TWRP, we can flash a custom kernel or no?

John hale commented on 2016-11-15 at 19:11:

I can confirm on my pixel xl both root and TWRP are working! Great job +Chainfire and +Ethan Yonker

Aaron DeArmitt commented on 2016-11-15 at 19:11:

+John hale have you then flashed a custom kernel after that process with fastboot flash kernel?

John hale commented on 2016-11-15 at 19:12:

+Aaron DeArmitt yea I'm using Franco atm

Aaron DeArmitt commented on 2016-11-15 at 19:12:

+John hale awesome, thanks my man!

John hale commented on 2016-11-15 at 19:13:

+Aaron DeArmitt no problem.

Aaron DeArmitt commented on 2016-11-15 at 19:18:

+John hale what was your exact process? I just tried with EX and I got a boot loop, I flashed stock boot.img of course, then booted to TWRP img, then flashed TWRP, then flashed SuperSU, booted up, back to boot loader and flashed kernel and boot loop

John hale commented on 2016-11-15 at 19:21:

+Aaron DeArmitt everything I have done can be found on my YouTube channel.

michael pap commented on 2016-11-15 at 19:25:

+Chainfire​​ here is link with Beta Nougat for many variants of S7 flat. I hope it can be helpfull

Aaron DeArmitt commented on 2016-11-15 at 19:30:

+John hale Thta is only TWRP installation, no root, and no custom kernel, what were your steps? EX completely borked me

Aaron DeArmitt commented on 2016-11-15 at 19:40:

+John hale did you not flash stock boot images before hand, I am guessing that may have been your case, or did you flash kernel very last and was on stock boot image?

John hale commented on 2016-11-15 at 19:40:

+Aaron DeArmitt I have not flashed stock since I did the ota

Aaron DeArmitt commented on 2016-11-15 at 19:48:

+John hale I mean the stock boot.img? So you started with Franco, in the directions it says to flash the stock boot.img before doing TWRP and SuperSU.....

John hale commented on 2016-11-15 at 19:49:

+Aaron DeArmitt I started with Franco and just flashed away. It's a nexus if it broke I'd flash back. Big deal. But it worked just fine ergo it works. ?

Aaron DeArmitt commented on 2016-11-15 at 19:50:

+John hale alright thanks bud, Imma start with a custom kernel I think

John Derksen commented on 2016-11-15 at 19:55:
Aaron DeArmitt commented on 2016-11-15 at 20:04:

Anyone that wants to know, I was able to flash Franco after following this process, booting up, then you will have no supersu binary, go back into TWRP and flash superSU again and it will be good to go. I tried the same process with EX kernel, and I got a bootloop, flashed supersu again, and then lost TWRP. I think this is because Franco does not modify ramdisk and EX kernel does, if I am correct in this statement

Christian Walker commented on 2016-11-15 at 20:21:

I also flashed Franco kernel and reflash su zip and all is good

Aaron DeArmitt commented on 2016-11-15 at 20:26:

+Christian Walker​ I think ex is screwy because of modifying ramdisk, but I'm not developer so not certain, but I think, lol. I don't know if could completely start with EX, and maybe it stay but I wanted follow directions and flash stock boot.img first

Milan Cosovic commented on 2016-11-15 at 20:33:

How to get passed the encrypted TWRP folders. I have tried removing my pattern security.

Christian Walker commented on 2016-11-15 at 20:33:

Yeah I did same thing,flashed stock boot first and all was well

Christian Walker commented on 2016-11-15 at 20:34:

+Milan Cosovic try rebooting twrp

Milan Cosovic commented on 2016-11-15 at 20:39:

+Christian Walker​ just by fastboot boot twrp? I tried about 5 times...

Christian Walker commented on 2016-11-15 at 20:41:

In the twrp it says this happens sometimes, try rebooting within twrp

Jon Prather commented on 2016-11-15 at 20:42:

+Chainfire I managed to patch for pixel devices to prevent bootloops, but suhide... hides the bind mounts I used to overlay them. Is there a method by which I can exclude those binds from suhide?

Milan Cosovic commented on 2016-11-15 at 21:14:

+Christian Walker can't since if you do that it boots into stock recovery. Tried 3 more times. Ahh well.

Jamie McInteer commented on 2016-11-15 at 21:18:

+Aaron DeArmitt I started with Ex. Everything worked perfectly.

Christian Walker commented on 2016-11-15 at 21:19:

+Milan Cosovic are you sure you have no security set up, did u try your old pin?

Milan Cosovic commented on 2016-11-15 at 21:20:

+Christian Walker yeah never had a pin. Only pattern. Doesn't ask me for anything.

Christian Walker commented on 2016-11-15 at 21:21:

Put in your pattern based on phone dialer and put in the numbers you would have swiped

Ir. Vitor Fabiano Carvalho de Oliveira commented on 2016-11-15 at 21:49:

Da pra fazer funcionar no LG Prime Plus?

Lee Mulligan commented on 2016-11-15 at 21:55:

Is Flashfire going to be updated any time soon with an up to date version of SuperSU only it's still on 2.78SR1. Thanks.

Mark Williams commented on 2016-11-15 at 23:44:

got TWRP & SuperSU-SR4 running without issue. Follow the instructions above, fyi ;) Question though, if I want to install a custom kernel such as Despair, Franco, etc, do I still need to flash the stock boot image first, then flash the custom kernel? Also, do we need to reflash SuperSU v2.78-SR4 after flashing the custom kernel?

Gilles Ouellet commented on 2016-11-16 at 00:21:

I understand all the steps... One question though. When i'm in TWRP from boot, i can't get any files off the phone? It's not showing up only shows root? Any ideas? (i created a folder in solid explorer for those 2 zips files but can't see them in TWRP)

Thanks alot Team!!!!!!

Myc Clark commented on 2016-11-16 at 01:44:

Just curious, what is the last firmware that is supported for this root method? I'm running P now and am caution of taking the OTA update as I don't want to reflash the phone to regain root.

Aaron DeArmitt commented on 2016-11-16 at 02:43:

+Jamie McInteer ya I tried ex kernel, Sharkey kernel, and franco, and if you have the kernel flashed before u start the process of installing TWRP and superSU they all stock as the kernel, so I don't want to over step my boundaries, but I did not need to use the stock boot image for any of the three time I tried those kernels, and had no errors and no errors all night.

Subhajit M commented on 2016-11-16 at 04:29:

+Pratik Kumar FUCK OFF

Georges Zucka commented on 2016-11-16 at 14:42:

I read comments on the XDA site that the boot-to-root method only works for NDE63P or earlier. Would that be true also for this method?

James Ford commented on 2016-11-16 at 14:51:

I have been having issue on my 6p with root, it says it rooted but when i try to use the function in my root apps they crash.. could this be because i have flashed a zip for google asistant and it now says Pixel as the device name?

SamuiDroid commented on 2016-11-16 at 19:14:

+Chainfire​​​​ You could implement the mode of the automatic root of supersu?

Because I do not trust kingroot

Your application does not go out of Huawei mediapad t1-a21L

Henil Ahir commented on 2016-11-17 at 01:57:

Is this work on galaxy note 2

Enaze Uddin commented on 2016-11-17 at 02:17:

+Georges Zucka I'm wondering the same.

Gökhan Boz Videoları commented on 2016-11-17 at 07:51:

+Chainfire Android One GM5 PLUS root network problem help

Georges Zucka commented on 2016-11-17 at 12:50:

+Georges Zucka I am now able to answer my own question: I applied the above method (to be exact, I did everything described at ), using the NDE63U factory image for the Pixel, and it worked.

Jorge Castillo commented on 2016-11-17 at 20:26:

Does this work with the qualcomm S7 variant with the Eng-root ?

ABHIMANYU KUMAR commented on 2016-11-18 at 13:43:

What about redmi note 3..?

Tariq Al.azaki commented on 2016-11-18 at 18:19:

قوه القوه

newton deus commented on 2016-11-19 at 18:45:

Works fine on S4 mini Cm14.1 ROM

杨勇 commented on 2016-11-20 at 03:32:

Can you give me all the SuperSU files?


rached saadani commented on 2016-11-20 at 15:49:

Wifi not working thanks

Marc MERLIN commented on 2016-11-20 at 16:53:

+Chainfire just wanted to give huge thank you for making this work on Pixel(XL) just a few days before I needed to migrate off a bad device to a new one. Thanks to you I was able to use TiBackup and move my data easily.

I've just bought SuperSu Pro and if you have a donate link I can send another thank you to, let me know :)

By the way, initially I didn't want to buy the SuperSU Pro because the author was "codingcode" whereas your app is "chainfire" that looked fishy and I was afraid someone else might want to get money from your work. Your SuperSu app mentions in app purchases as donations (which I didn't find) and no reference to SuperSu Pro as a way to send you money. Maybe make it more clear how to send money to say thanks and/or a paypal link?

michael pap commented on 2016-11-21 at 10:05:

+Chainfire​ any news about S7 nougat issues? (wifi and camera crash)???

Naithan Edmead commented on 2016-11-21 at 20:27:

+Chainfire​ I need your opinion on something.....

عبدالقدوس السمري commented on 2016-11-22 at 07:43:

I am two Galaxy j7 I installed him en route, but your root did not work all the stuff like the game hacker program possible solution

Ryan Foret commented on 2016-11-23 at 03:34:

+Chainfire​ dumb do I get an OTA update after flashing the boot-to-root?

Monkhbat Urandelkhii commented on 2016-11-23 at 07:53:

Somebody help me

Kevin Ortiz commented on 2016-11-23 at 13:39:


Cyprian Cyprian commented on 2016-11-23 at 14:06:

I am using an infinix hot 2 how can i make it support otg

Brad Churchey commented on 2016-11-24 at 01:27:

Work around for pokemon go for all phones would be awesome!

Marc MERLIN commented on 2016-11-24 at 01:34:

+Brad Churchey I believe you need to use one exposed module. Google "xposed pokemon"

Marc MERLIN commented on 2016-11-24 at 01:39:

I didn't try it, gave you the google resource that should answer your question, go read it :)

Chris Catalano commented on 2016-11-24 at 02:56:

Hey guys, I was trying to get the boot-to-root.img to work and ended up getting the never ending loading screen. I installed TWRP and now my device won't recognize/mount any partitions. Started a thread here, any help would be appreciated. I'm a noob when it comes to troubleshooting android stuff pre OS. I've rooted every phone I've had before, first time I got it this jacked up. I can only boot into recovery.



noor khan commented on 2016-11-24 at 05:55:
Edward Oubrayrie commented on 2016-11-24 at 11:36:

+Chainfire can you expand on why Pixel 7.1 is different from Nexus 7.1 (DeveloperPreview)? DP does not have the same partition layout as Pixel? Or should we expect "fastboot boot" boot-to-root for Nexus as well once 7.1 is stable? Last time you mentioned DP was on the SR2 changelog...

Hilton Augustine, Jr. commented on 2016-11-24 at 15:30:

ANDROID PAY not working. I've been up for a week now rooted with the boot-to-root and SuperSU-SR3 method. Thanks Chainfire! No issues with any other apps requiring root (tasker,titanium,FX file, etc). Just tried to use Android Pay and when I reach the screen to add a card I get the following error:


Android Pay can't be used:

Google is unable to verify that your device or the software running on it is android compatible.


Anybody know what's going on? Do I need to lock the bootloader back? And will it keep root and SU if I do? I read that re-locking the bootloader will factory reset the data, but that's not problem since I have it backed up.


Cyprian Cyprian commented on 2016-11-25 at 09:29:

Anyone who knows how i can root my android one???

Barry Arrindell commented on 2016-11-25 at 15:35:

I can't find su update in recovery when download in phone .cant find please help

Barry Arrindell commented on 2016-11-25 at 15:50:

I have no computer.and I have use kingoroot to root my blu studio 5.0ce and it work but i am still getin full root access to read flash drive so can i use to fix iss

Ryan Foret commented on 2016-11-26 at 14:59:

+Chainfire​ will FlashFire work on the Pixel to update the OTA?

Barry Arrindell commented on 2016-11-26 at 17:09:

I don't understand how to flash how to do it .OK when go into recovery mod I am not finding the file su bb installer zip when I download it ???

Machlen Polfliet commented on 2016-11-29 at 03:20:

+Hilton Augustine, Jr. This is because of the unlocked bootloader. Unlocking your bootloader trips a test put out for security measures by various banking/financial apps along with a few others. Unfortunately, there is no way around this as of now. DO NOT attempt to relock your bootloader while still rooted. If you MUST use Android pay, flash the stock pixel image to get rid of root, then relock your bootloader (this will wipe all data on your device) and Android pay should be functioning.

Chainfire commented on 2016-11-30 at 09:09:

Continued here:

This post is over a month old, commenting has been disabled.