SuperSU v2.79 SR3
Posted on 2017-01-14, 98 comments, 397 +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.

This is a minor bugfix update, a new stable will be released soon.

Some users reported bootloops on SR1 and SR2, for whom the last stable worked fine. If this still happens on SR3, report it to the BETA thread on XDA, otherwise I will consider these reports fixed.

Links

Download flashable ZIP: https://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip

SuperSU BETA thread on XDA: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133

Changelogs

  • Fix erroneously deleting SuperSU's copy of app_process on 6.0 since 2.79-SR1

  • GUI: Fix app_process requirement detection when supersu context used

  • Fully eliminate sugote binary, no longer needed due to SELinux handling improvements in earlier versions

  • Support /system/xbin/sush as default shell

  • Adjust LD_PRELOAD filtering to exclude suhide's libraries

  • ZIP: Motorola: default to systemless mode

SuperSU Download

+1397
Nick Sanchez commented on 2017-01-14 at 23:08:

Is this for all root devices

Cody Smith commented on 2017-01-15 at 02:08:

+Nick Sanchez I doubt it, as some devices like the QC S7/S7E require a system-less root method, and I'm sure there are others that require that.

Mike Grimes commented on 2017-01-15 at 02:15:

Should be for all. It Will select system or systemless automatically.

Gary Sosa commented on 2017-01-15 at 04:55:

Works great on Pixel XL, flashed in TWRP after flashing Pure Nexus, reflash TWRP, boot into os and flash vendor image, then SuperSU

unonice commented on 2017-01-15 at 05:16:

Nexus 6P? running Nougat 7.1.1 January .. Everything is all good here, no issues ???? .. keep up the great work .. +Chainfire​ you the Man ????

febry valdy commented on 2017-01-15 at 05:30:

Waiting for stable...

Yuri Ledda commented on 2017-01-15 at 13:40:

after flashing this beta I can not flash a rom

Arttu L commented on 2017-01-15 at 14:06:

+Yuri Ledda more info needed to help. What you mean by "cannot flash ROM"?

Kmxoo Ls A commented on 2017-01-15 at 20:08:

Pues a mi; después de flashear el zip y reiniciar se queda en pantalla negra y no hace nada ?, tengo un moto G4 con Android 7.0.

Espero que la siguiente actualización si le funcione a mi dispositivo, porfa compatibilidad para mi moto G4 ?

Marco Antonio Rodriguez Ramos commented on 2017-01-17 at 01:47:

lpoo

p

io

V.RAMA SAMY commented on 2017-01-17 at 02:02:

Id 'nt know how is this useful

Manuel Rodriguez commented on 2017-01-17 at 04:17:

Hello, Greetings from Venezuela, I have on the smartphone brand Wiko Jerry android 6.0, and wanted to see if this type of smartphone has a chance to root, without making a modification to the system, just wanted to be root, without changing the rom.

Hola, Saludos desde Venezuela, tengo en smartphone marca Wiko Jerry android 6.0, y queria ver si este tipo de smartphone tiene oportunidad de root, sin hacer modificación al sistema, solo quería que quede root, sin cambiar la rom.

febry valdy commented on 2017-01-17 at 04:18:

+Manuel Rodriguez try kingroot

Manuel Rodriguez commented on 2017-01-17 at 04:24:

+febry valdy no confio en Kingroot, es una app dañina.

he did not trust in Kingroot, it is a harmful app.

Mike Grimes commented on 2017-01-18 at 01:50:

+febry valdy kingroot is full of malware! Anyone who uses it deserves it

febry valdy commented on 2017-01-18 at 01:54:

+Mike Grimes ?

Rt Ben commented on 2017-01-18 at 06:56:

It's okkk Think you too match

Manuel Rodriguez commented on 2017-01-18 at 07:13:

yo tengo un smartphone Wiko Jerry

Device: V2802AN

Product: V2802AN

Android Version: 6.0

API Level 23

Build ID MRA58K

y quiero estar seguro de que funcione el SuperSU y no vaya a dar problemas despues de hacer la instalación.

I have a smartphone Wiko Jerry

Device: V2802AN

Product: V2802AN

Android Version: 6.0

API Level 23

Build ID MRA58K

And I want to be sure that the SuperSU works and will not give problems after the installation.

masoud pooladi commented on 2017-01-20 at 12:52:

tnx

Walter White commented on 2017-01-21 at 12:53:

Any solution for encrypted S7 (Android 7.0) to root?

Paulo Carl Williamson commented on 2017-01-24 at 22:53:

SuperSu for Lineage plz

John Johnson commented on 2017-01-25 at 01:23:

D'oh! I can't believe I'm actually posting here with this; inviting your fury...now. Anyway, in case it matters, on a non-verizon Google Pixel:


fastboot oem unlock

fastboot boot boot-to-root.img

Repeated reboots, as expected. However, after the second or third reboot, it's stuck in boot loop with the following, perhaps relevant, trace in logcat:


<pre>

01-24 19:17:25.383 29430 29430 F art     : art/runtime/runtime.cc:422]   native: #12 pc 0000000000153400  /system_root/system/lib64/libandroid_runtime.so (???)                                                                      [209/1896]

01-24 19:17:25.383 29430 29430 F art     : art/runtime/runtime.cc:422]   native: #13 pc 0000000000f642e8  /system_root/system/framework/arm64/boot-framework.oat (Java_com_android_internal_os_Zygote_nativeForkSystemServer__II_3II_3_3IJJ+228

)

01-24 19:17:25.383 29430 29430 F art     : art/runtime/runtime.cc:422]   at com.android.internal.os.Zygote.nativeForkSystemServer(Native method)

01-24 19:17:25.383 29430 29430 F art     : art/runtime/runtime.cc:422]   at com.android.internal.os.Zygote.forkSystemServer(Zygote.java:139)

01-24 19:17:25.383 29430 29430 F art     : art/runtime/runtime.cc:422]   at com.android.internal.os.ZygoteInit.startSystemServer(ZygoteInit.java:672)

01-24 19:17:25.383 29430 29430 F art     : art/runtime/runtime.cc:422]   at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:768)

01-24 19:17:25.383 29430 29430 F art     : art/runtime/runtime.cc:422] 

01-24 19:17:25.383 29430 29430 F art     : art/runtime/runtime.cc:422] 

01-24 19:17:25.384 29430 29430 F libc    : Fatal signal 6 (SIGABRT), code 6 in tid 29430 (main)

01-24 19:17:25.384   534   534 W         : debuggerd: handling request: pid=29430 uid=0 gid=0 tid=29430

01-24 19:17:25.398 29521 29521 E         : debuggerd: Unable to connect to activity manager (connect failed: Connection refused)

01-24 19:17:25.399 29521 29521 F DEBUG   : * * * * * * * * * * * * * * * *

01-24 19:17:25.399 29521 29521 F DEBUG   : Build fingerprint: 'google/sailfish/sailfish:7.1.1/NMF26U/3562008:user/release-keys'

01-24 19:17:25.399 29521 29521 F DEBUG   : Revision: '0'

01-24 19:17:25.399 29521 29521 F DEBUG   : ABI: 'arm64'

01-24 19:17:25.399 29521 29521 F DEBUG   : pid: 29430, tid: 29430, name: main  >>> zygote64 <<<

01-24 19:17:25.399 29521 29521 F DEBUG   : signal 6 (SIGABRT), code ~~6 (SI_TKILL), fault addr ------~~

01-24 19:17:25.402 29521 29521 F DEBUG   : Abort message: 'art/runtime/jni_internal.cc:492] JNI FatalError called: frameworks/base/core/jni/com_android_internal_os_Zygote.cpp:481: Unable to construct file descriptor table.'

01-24 19:17:25.402 29521 29521 F DEBUG   :     x0   0000000000000000  x1   00000000000072f6  x2   0000000000000006  x3   0000000000000008

01-24 19:17:25.402 29521 29521 F DEBUG   :     x4   00000000000000f4  x5   0000800000000000  x6   00000076062e3000  x7   0000000000000000

01-24 19:17:25.402 29521 29521 F DEBUG   :     x8   0000000000000083  x9   ffffffffffffffdf  x10  0000000000000000  x11  0000000000000001

01-24 19:17:25.402 29521 29521 F DEBUG   :     x12  ffffffffffffffff  x13  0000000000000000  x14  0000000000000000  x15  0016e00b593a325e

01-24 19:17:25.402 29521 29521 F DEBUG   :     x16  0000007602ccfee0  x17  0000007602c79250  x18  0000000000000000  x19  0000007606397b40

01-24 19:17:25.402 29521 29521 F DEBUG   :     x20  0000000000000006  x21  0000007606397a98  x22  0000000000000000  x23  0000000000000016

01-24 19:17:25.402 29521 29521 F DEBUG   :     x24  0000000000000000  x25  0000000000000000  x26  000000760243e180  x27  0000007ffe740981

01-24 19:17:25.402 29521 29521 F DEBUG   :     x28  0000007ffe740cc8  x29  0000007ffe740880  x30  0000007602c766f8

01-24 19:17:25.402 29521 29521 F DEBUG   :     sp   0000007ffe740860  pc   0000007602c79258  pstate 0000000060000000

01-24 19:17:25.668 29521 29521 F DEBUG   : 

01-24 19:17:25.668 29521 29521 F DEBUG   : backtrace:

01-24 19:17:25.668 29521 29521 F DEBUG   :     #00 pc 000000000006b258  /system_root/system/lib64/libc.so (tgkill+8)

01-24 19:17:25.668 29521 29521 F DEBUG   :     #01 pc 00000000000686f4  /system_root/system/lib64/libc.so (pthread_kill+64)

01-24 19:17:25.668 29521 29521 F DEBUG   :     #02 pc 0000000000023ce8  /system_root/system/lib64/libc.so (raise+24)

01-24 19:17:25.668 29521 29521 F DEBUG   :     #03 pc 000000000001c76c  /system_root/system/lib64/libc.so (abort+52)

01-24 19:17:25.668 29521 29521 F DEBUG   :     #04 pc 00000000004300fc  /system_root/system/lib64/libart.so (_ZN3art7Runtime5AbortEPKc+456)

01-24 19:17:25.668 29521 29521 F DEBUG   :     #05 pc 00000000000e5818  /system_root/system/lib64/libart.so (_ZN3art10LogMessageD2Ev+1576)

01-24 19:17:25.668 29521 29521 F DEBUG   :     #06 pc 000000000032972c  /system_root/system/lib64/libart.so (_ZN3art3JNI10FatalErrorEP7_JNIEnvPKc+152)

01-24 19:17:25.668 29521 29521 F DEBUG   :     #07 pc 0000000000151564  /system_root/system/lib64/libandroid_runtime.so

01-24 19:17:25.668 29521 29521 F DEBUG   :     #08 pc 0000000000152cec  /system_root/system/lib64/libandroid_runtime.so

01-24 19:17:25.668 29521 29521 F DEBUG   :     #09 pc 0000000000153400  /system_root/system/lib64/libandroid_runtime.so

01-24 19:17:25.668 29521 29521 F DEBUG   :     #10 pc 00000000025ea2e8  /system_root/system/framework/arm64/boot-framework.oat (offset 0x1686000) (com.android.internal.os.Zygote.nativeForkSystemServer+228)

01-24 19:17:25.668 29521 29521 F DEBUG   :     #11 pc 00000000025e9f64  /system_root/system/framework/arm64/boot-framework.oat (offset 0x1686000) (com.android.internal.os.Zygote.forkSystemServer+144)

01-24 19:17:25.668 29521 29521 F DEBUG   :     #12 pc 00000000025f293c  /system_root/system/framework/arm64/boot-framework.oat (offset 0x1686000) (com.android.internal.os.ZygoteInit.startSystemServer+888)

01-24 19:17:25.668 29521 29521 F DEBUG   :     #13 pc 00000000025ef4d0  /system_root/system/framework/arm64/boot-framework.oat (offset 0x1686000) (com.android.internal.os.ZygoteInit.main+1244)

01-24 19:17:25.668 29521 29521 F DEBUG   :     #14 pc 00000000000d27e8  /system_root/system/lib64/libart.so (art_quick_invoke_static_stub+600)

01-24 19:17:25.668 29521 29521 F DEBUG   :     #15 pc 00000000000df230  /system_root/system/lib64/libart.so (_ZN3art9ArtMethod6InvokeEPNS_6ThreadEPjjPNS_6JValueEPKc+252)

01-24 19:17:25.668 29521 29521 F DEBUG   :     #16 pc 0000000000429964  /system_root/system/lib64/libart.so (_ZN3artL18InvokeWithArgArrayERKNS_33ScopedObjectAccessAlreadyRunnableEPNS_9ArtMethodEPNS_8ArgArrayEPNS_6JValueEPKc+108)

01-24 19:17:25.668 29521 29521 F DEBUG   :     #17 pc 00000000004295bc  /system_root/system/lib64/libart.so (_ZN3art17InvokeWithVarArgsERKNS_33ScopedObjectAccessAlreadyRunnableEP8_jobjectP10_jmethodIDSt9__va_list+380)

01-24 19:17:25.668 29521 29521 F DEBUG   :     #18 pc 000000000034544c  /system_root/system/lib64/libart.so (_ZN3art3JNI21CallStaticVoidMethodVEP7_JNIEnvP7_jclassP10_jmethodIDSt9__va_list+604)

01-24 19:17:25.668 29521 29521 F DEBUG   :     #19 pc 000000000009f06c  /system_root/system/lib64/libandroid_runtime.so

01-24 19:17:25.668 29521 29521 F DEBUG   :     #20 pc 00000000000a1684  /system_root/system/lib64/libandroid_runtime.so (_ZN7android14AndroidRuntime5startEPKcRKNS_6VectorINS_7String8EEEb+692)

01-24 19:17:25.668 29521 29521 F DEBUG   :     #21 pc 0000000000002260  /system_root/system/bin/app_process64

01-24 19:17:25.668 29521 29521 F DEBUG   :     #22 pc 000000000001a594  /system_root/system/lib64/libc.so (__libc_init+88)

01-24 19:17:25.668 29521 29521 F DEBUG   :     #23 pc 0000000000001ccc  /system_root/system/bin/app_process64

</pre>

The zip file with the relevant image is

John Johnson commented on 2017-01-25 at 01:36:

Well what d'ya know, flashing with this one worked just right:

:D

Russell Moss commented on 2017-01-26 at 22:32:

is this safe to use with rooted S7e on G935U? I remember them saying dont update from v2.76 (play store)because it will not work with a different version.

Adrian Maya commented on 2017-01-27 at 15:16:

How does this work

Adrian Maya commented on 2017-01-27 at 15:16:

Idk know how to do it

Adrian Maya commented on 2017-01-27 at 15:17:

Some one send me both the links please ???

Yesaya Kefin commented on 2017-01-30 at 03:02:

why my supersu can,t work?

Yesaya Kefin commented on 2017-01-31 at 06:09:

okay thank you later I will try to find a reference to this issue

Gleisson Bonifacio commented on 2017-02-01 at 03:14:

Vc são bons em, o meu g900md agora tem acesso root. Quero aprender a programar e ser fera como vocês.

Melii Ssa commented on 2017-02-03 at 02:00:

J'ai un problème sur mon téléphone les binaires n'arrivent pas a faire la mise a jour je fais comment?

Yesaya Kefin commented on 2017-02-03 at 03:28:

what do you say?

Melii Ssa commented on 2017-02-03 at 03:32:

Translate i speak french

Yesaya Kefin commented on 2017-02-03 at 03:41:

oh i'm sorry.

Melii Ssa commented on 2017-02-03 at 03:44:

Le binaire de Su doit être mis a jour. Failed

Yesaya Kefin commented on 2017-02-03 at 03:50:

SuperSU essayer d'abord enlevé et installé nouvelle SuperSU SuperSU qui connaissent son ont un cache du gag

Mehdi Mehrous commented on 2017-02-04 at 04:09:

Premièrement il faut aller à la liste des applications et Unrooter le telephone depuis les paramètres de l'application supersu après redémarrer en mode recovery et installer le zip puis effectuer un wipe du cache et du dalvik.

HEADS TAILS commented on 2017-02-04 at 05:49:

Always found this su a little temperamental, a bit like its programmer...also paying over the odds for theses apps today..not happy..shame theirs so little choice, like being locked into a phone contract they've got you by the balls until a year later and a better offer from different provider becomes available. .Xx

Yesaya Kefin commented on 2017-02-04 at 07:26:

Ceci est le meilleur conseil dans le champ de commentaire

Elite Electronics commented on 2017-02-06 at 12:07:

+Chainfire​ I've contacted you through hangouts

Kmxoo Ls A commented on 2017-02-07 at 21:50:

Ya pude hacer root mi Moto G4 con Android 7, pero el único problema que me da es en ajustes en el apartado de aplicaciónes me da un cierre forzado y esto mismo me pasaba en la versión Android 6. Al parecer lo demás funciona bien

Levitico Soares commented on 2017-02-10 at 16:49:

Is this file compatible with any device with Android 6?

زمان السيد commented on 2017-02-11 at 02:00:

مرحبا لماذه لا يمكن أن يحدث هاتفي سامسوج كلكسي s5 ارجو المساعده طلب الاتصال بدخدمه العملاء

Dennis Lee commented on 2017-02-12 at 21:02:

Thanks, works on SM-915G 6.0.1. However, the cf-autoroot for this phone is not working. It fails at flashing the cache somehow.

Florin Daniel commented on 2017-02-16 at 18:56:

cine ma ajuta si pe mine am instalat SuperSu Pro sa instalat sim da doar sal dezinstalez doar atat

Cezar Esguerra commented on 2017-02-18 at 12:44:

09499572411

Thomas Deisler commented on 2017-02-18 at 20:50:

I'm trying to root my Pixel device (Build NMF26V). OEM Unlock: no Problem. Boot twrp.img - then flash twrp.zip - everything okay. But when I tried to install SU.zip, it didn't root the device. The next thing I did was booting the boot-to-root.img - that ended in a Bootloop. Had to flash-all.bat to stock Factory Image.

Question: What twrp do I need to use? RC1? Alpha1? Alpha2? I tried with RC1, because it's the latest.

Next Question: I flashed Factory Image with Build Number NMF26V, because I'm from Europe. Was that right? Can I flash NMF26U, too?

Thomas Deisler commented on 2017-02-18 at 22:17:

Okay got it. Wasn't the latest SU

Major Mike commented on 2017-02-20 at 00:42:

Thank you for the update, just a quick questions, will this work without issue with the last 7.1.1 image for Nexus 6 (shamu)? I am about to do it and was hoping to save some trouble if not. TIA.

Ifanwildadimas Ifan commented on 2017-02-20 at 12:39:

clasn of clans saya level 25 aku citer yang tidak pernah kalah melawanku

Dark Ages commented on 2017-02-22 at 11:45:

I'm running Resurrection Remix Nougat on hlte note3.

Do I just flash it through TWRP? I want to do a clean install of RR with out. Have been having a lot of random reboots will this help?

Manuel Rodriguez commented on 2017-02-25 at 08:02:

esta versión servirá para smarphone Wiko Jerry Game Changer. con Android 6.0 [37] ? ?

Nichole Fraser Nichols commented on 2017-02-26 at 01:44:

I know this isnt the appropriate thread to ask this and Im far too nervous to root my Pixel XL but Ive been looking for a way other than rooting to get miracast on my device. I have a smart tv and fire stick....anyone wanna PM some solutions? Id be very grateful. Sorry for asking here...Just looking for some solid help and this thread seems full of ppl who can offer it. Thanks in advance.

nikhil saha commented on 2017-02-26 at 05:20:

How can i add otg support & volte support on my intex aquafish os jolla mobile.please sagest to me.

Gregory Dudek commented on 2017-02-26 at 06:11:

After the Nov 2016 update several people, including me, have found that boot-to-root.img leads to a "soft" boot loop (fixable by reinstalling the update). I realize this is not a support thread, but the problem with the method is not obvious on the xda forum and many people have had problems so I thought a comment here might help.

--

Fixing the boot loop once it occurs seems to be straightforward I didn''t lose any data.

--

I am not 100% certain, but I believe the problem in my case was caused by using an old version of adb to do the install of boot-to-root.img I don't know for sure what changed in adb, but I suspect it is related to support for the a/b partition model on the Pixel. Using a frsh adb allowed by to do a successful install.

مشاري جبريل commented on 2017-03-02 at 17:32:

good

Manuel Rodriguez commented on 2017-03-04 at 22:31:

aquí uno pregunta y no le intentan decir nada. que mal, y así quiere reputación?

PillowFace McGee commented on 2017-03-05 at 16:31:

How can I install this? Do I need to use my pc and go to the twrp bootloader?

Guido D.R. commented on 2017-03-06 at 16:45:

Just flashed via TWRP 3.0.2-2 on my Note5 SM-N920W8 flawless thank you!

paul bedard commented on 2017-03-08 at 07:08:

Not working keeps getting deleted

Андрей Серафимов commented on 2017-03-11 at 14:41:

SuperSU??????= 1 big problem for you!???"Uploaded Binary", "Uploaded Binary"...!!! And NOT WORKS!!!???SuperSU - this is FULL SHIT!!! ?????

KingoRoot RULES and works very, very best!!! ???

Dark Ages commented on 2017-03-11 at 23:12:

Help. I've installed the latest version with Magisk and I seem to have lost root.

Joseph Yeung commented on 2017-03-16 at 15:28:

+Андрей Серафимов You must either work for Kingoroot or be a spyware loving moron ?????

Андрей Серафимов commented on 2017-03-17 at 07:56:

+Joseph Yeung , You are very ugly and smell like shit. You need to wash it frequently...Good Luck with SuperSUks!???

KingoRoot really works!

Alexander Beznosikov commented on 2017-03-17 at 18:53:

Huawei Y3ii LUA-L21 LTE, mtk6735m 64bit, Android 5.1, TWRP 3.1.0, Installation after SuperSU - bootloop

Joseph Yeung commented on 2017-03-17 at 23:27:

+Андрей Серафимов SuperSU never claimed to be a rooting tool, you blithering idiot. Enjoy having your phone spied on by our Chinese government and your bandwidth being used for DDOS cyberterrorism thanks to KingoRoot! ?????

Alexander Beznosikov commented on 2017-03-18 at 11:35:

I've tried many programs (Kingroot, KingoRoot, Baidu and others) but I can not get Root.

nhat dang minh commented on 2017-03-18 at 16:19:

+Joseph Yeung you dont need talk to him Андрей «БесОгонЪ» Серафимов. He is a child, dont know what is a good for root systemless and a child alway like "china toys-EASY tools (EASY make virus)" with full spyware-virus. Kingroot: EASY 1 click VIRUS and a child just EASY with him unless it'll cry. Just dont care him because a foolish child dont know what can they (xda development) do. A child need milks to shut up his mouth :))

Андрей Серафимов commented on 2017-03-18 at 19:16:

+Joseph Yeung , You are a fool)))That I can steal? I'm not a secret agent, not the President Merkel, which is already hacked...)I Have no accounts with millions of dollars, I have no Nude photos)))so If you are afraid of hacking, you need to live in a cave and use only Slippers.)))

Андрей Серафимов commented on 2017-03-18 at 19:25:

+nhat dang minh​​​​​ , And what do you want? Apparently a plate of rice with rice cake with spicy sauce, and a pair of elephants for you and your wife.)I repeat, I have nothing to steal or run the viruses. And if they will, then for your information it was invented antiviruses. In the end, you can reflash an electronic device. It is to reflash and you should be SuperSU.

"Children" you say? Have you ever heard of protective systems?)))Norton, Avira and others you names tell you anything?)

Where are you? You are only good with milk)))Or this shit SuperSUCKS)))???

In addition to this app, don't forget to buy the laptop!)Otherwise it is not properly work. This is "milk", that is such a cow...)

A little about fear...If you are all Chinese, don't look under the lid of your appliance, TV, refrigerators, and even clothes!)Otherwise you go your whole life scared...)))There's not written "made in USA")And if written, then you have more to fear this, because US watching you more than the other countries combined.)))

Dark Ages commented on 2017-03-19 at 17:41:

After a week of fighting with Magisk I have come back to you. Tried and tested SuperSU is still my SU of choice. I still am unable to get Adaway to work could it be related to SU?

Evert Eckhardt commented on 2017-03-23 at 18:12:

+Dark Ages I switched to MagiskSU on Magisk v11.6 today to see how it runs. Not experiencing any trouble so far.

PairedPrototype commented on 2017-03-28 at 10:31:

Working well with my test build of Magisk v11.6 for multi-slot devices. +1

Random Googler commented on 2017-03-28 at 15:12:

Will it work on SM-N910T running lineageOS 14.1?

Sorry scared for da bootloop!

Random Googler commented on 2017-03-28 at 15:26:

Bit the bullet...

Works just fine Note 4 SM-N910T running lineageOS 14.1!

Also For Tab Pro 8.7

محمد معافا commented on 2017-04-01 at 11:58:

صديقي العزيز

ارجوا ان تحلوهذة المشكلة برمجيات SU بحاجة للترقية ارجوا ان ترسلو رابط الترقية ولكم كل التقدير

Javier Saviola commented on 2017-04-03 at 22:47:

Lineage 14.1 on samsung mega 5.8 gt-i9152. Rom ok.. Flash chainfire latest supersu ok..but the problem the phone still cant rooted. Please somebody advice if im misstepped during installation procedure.. Cc +Chainfire

bahram rakee commented on 2017-04-09 at 11:11:

ok

Bhagwan Keswani commented on 2017-04-11 at 04:24:

hello +Chainfire my oneplus 3 oos 4.1.1 android 7.1.1 says no su binary installed even after multiple attemps to do so,tried different procedures but its not working,hope you fix this too in your stable update,while updating there is a patch but stock one recovered it say and after reboot the same dialog again and again

Nasar Ahmed commented on 2017-04-16 at 05:51:

I flashed this .zip via TWRP on my Samsung Note 5 (SM-N9208) on Android 7.0. But stuck on creating image for ever, even after trying for whole night.. Please do update to cover Android N charges in Samsung.

http://i63.tinypic.com/sb4mq1.jpg

Jonathan White commented on 2017-04-19 at 02:16:

+Javier Saviola Have you enable root access for apps in developer mode in lineage?

carlos giovanni commented on 2017-04-24 at 19:55:

Me ayudarían en convertir a root un alcatel pixi 3(4.5) 5017a

Jonas McClure commented on 2017-04-25 at 19:33:

+Nasar Ahmed Go into the TWRP terminal (advanced > terminal) and type 'mount -o bind /dev/urandom /dev/random' without the quotes. BEFORE trying to install SuperSU. After you type that in, install your zip file and enjoy 7.0!

kader meeran commented on 2017-04-27 at 04:21:

A

Chris Sucharda commented on 2017-05-02 at 00:16:

Is it working on pixel may update?

Brian Gold commented on 2017-05-02 at 03:29:

SR3 seems to be broken after installing the May security update. Pixel XL after flashing the initial google splash page flashes by and phone keeps rebooting in a loop like this. Going back to April's update until it can be further investigated by Chainfire.

Javier Saviola commented on 2017-05-03 at 18:08:

+Jonathan White Sorry for late reply.. Yes already enable root access.. But still can't root..

Boris Levit commented on 2017-05-04 at 09:59:

+Brian Gold Same thing on my Pixel Sailfish

Haraesh Jayalingam commented on 2017-05-06 at 16:04:

+Brian Gold Same here. Just saw your comment and going back to April update as well. Guess we'll have to wait until SuperSU is updated

Brian Gold commented on 2017-05-06 at 16:06:

+Haraesh Jayalingam There are two different fixes now. One is flash the bootloader from April or Chainfire released a flashable fix for this.

Bernie John Gumapac commented on 2017-05-15 at 03:28:

Is this working on nougat 7.1.2?

Brian Gold commented on 2017-05-15 at 03:29:

+Bernie John Gumapac yes may update.

Bernie John Gumapac commented on 2017-05-15 at 05:41:

OK. Thank you.

Aurélien Requiem commented on 2017-05-20 at 23:34:

+Chainfire SR3 is broken on PixelXL with stock rom.Th device bootloops within a few seconds.

+Brian Gold how did you switch back to the April update?

دنيا دنيا commented on 2017-05-28 at 23:07:

اخي الروت معي شغال بعد ما حدثته مارضي يشتغل الروت ايش السبب

Brian Gold commented on 2017-05-28 at 23:08:

I flashed the bootloader from April with adb

Harry Hanks commented on 2017-05-29 at 15:30:

Testing to see if it works. I'm not sure. But I have faith in this app.

Chainfire commented on 2017-05-30 at 19:29:

Continued here:

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