yashsingh1/xdaforums huggingface dataset:
[SuperSU] :
Encrypted by default in Nexus 9... :(

Check here... https://support.google.com/nexus/answer/2844831?hl=en-AU...
[SuperSU] Ja_som:
Thanks...

[MENTION=631273]Chainfire[/MENTION] can you please tell us how is it with encryption and your root?

Can we encrypt devices after CF auto-root?

Thank you.
[SuperSU] :
Yup, you can successfully root with CF Auto Root...

Dunno about re encrypting afterwards though... :(
[SuperSU] Chainfire:
CFAR no longer wipes /data. It doesn't touch it at all anymore, really.
[SuperSU] Murshad007:
Running Smoothly in My device

Sent from my LG G Flex F340K Stock KitKat 4.4.2 Rooted

using XDA Free mobile app
[SuperSU] Pkt_Lnt:
Please correct your post.

http://xdaforums.com/showpost.php?p=56851767&postcount=7415
[SuperSU] :
Thanks for the heads up... :good:
[SuperSU] Krunk83:
I'm getting root access on apps but they aren't showing up in my app list. Should this concern me? On CM12 5.0 and superSU 2.19.

OnePlus One
[SuperSU] Lord_Flaya:
After last update I install as system app and reboot. Then supersu gets updated from play store and is no longer system app. I repeat the process and the same thing happens over and over. Any clues? I have verified that I have full root.

Hit thanks if I helped you.
[SuperSU] sirbanger:
Hello, curious what "mount namespace separation" option is? Also is it checked by default?

Thanks.
[SuperSU] MrKaon:
Been answered few times by other users including Chainfire himself.

You don't read dude, do you[emoji1]
[SuperSU] rxxt:
Thx for that information, just what I was looking for!! :svetius:
[SuperSU] shawnbrennan55:
Play store does not have root access so it cannot write to the system partition. Updates to system apps are always written to /data/app. If you flash the updated version from recovery then the apk should be deleted from /data/app.
[SuperSU] :
Flashing the zip via TWRP/CWM will make it a system app...

If you update it via Play Store, go to SuperSU>Settings>System>Install SuperSU into System....

The Phone will reboot automatically and voila SuperSU is a system app now... :good:

---------- Post added at 10:13 AM ---------- Previous post was at 10:12 AM ----------

Of I were you I would have been concerned... :rolleyes:

---------- Post added at 10:15 AM ---------- Previous post was at 10:13 AM ----------

Yup, checked by default...

Wow, that's what I get back after helping someone... :mad:
[SuperSU] MJD:
I keep getting a message saying I need to update supersu binaries. I can't see any option to do this. Can someone point me in the right direction please?. I have the latest SuperSu from the PlayStore, do I need a different one?

Thanks in advance.
[SuperSU] Lord_Flaya:
Well, yes this is what I did. But after reboot it gets updated again and again and again. Last night It happened 6 times. Even after flashing from cwm it gets updated from play store and the cycle begins anew.

Hit thanks if I helped you.
[SuperSU] Chainfire:
v2.24 release notes: https://plus.google.com/113517319477420052449/posts/7sti4Z27usv
[SuperSU] Chainfire:
v2.24 replaced by v2.25. Hopefully this one works better!
[SuperSU] CyberpodS2:
Bump for v2.25 still working at the should on quoted setup.

Are you still looking for backward compatability checks?
[SuperSU] Chainfire:
Always :)
[SuperSU] PeQuEsan:
Question to chainfire... Do you expect any improvement in flashable zip that patches Lollipop kernel, or that is and will probably be ok and you only need to update SuperSU, as you seem to be doing with the beta test versions?

Thanks a lot.
[SuperSU] lalec:
And with all this trouble you still let play store automatically update your apps? Remove the market link from within TB or change your play store settings.
[SuperSU] Chainfire:
v2.27 released, please read the release notes before flashing.
[SuperSU] deathsquad737:
Working like a beast. v2.27 on. My LG g3 vs98510b

A.L.B/E.B.B
[SuperSU] WeT-Klb:
How to update previous SuperSu?

Hi,

i rooted my Galaxy Note 2 LTE 4.4.2 with Ghettoroot - so SuperSu 2.02 was installed.

Then i wnt to Playstore and bought the SuperSu Pro-license.

How can i get updates for SuperSu / SuperSu Pro? Playstore always tell me there are no updates available - but i still stuck on v2.02. Playstore even only Show 2.01.

SuperSu tells me it is a System app. Would it help to check "Install new" (clean up for new Installation with Google Play Store)? I translated this by my own as i use german language.

BTW - I can´t change my recovery as i don´t want to Trigger Knox.

I use the original stock Firmware.

C U

WeT-Klb
[SuperSU] thebrainkafka:
Nice
[SuperSU] Lord_Flaya:
I don't mind play store updating my apps, but it bugs me that it "updates" to the same version as soon as I install supersu to system.
[SuperSU] emanuele1986:
Be enough supersu2.27 flashable to root my nexus 4? Or i have to use also cfroot?
[SuperSU] Srandista:
Should be enough, SuperSU 2.27 is not changing kernel, like CFAR does.
[SuperSU] 3DSammy:
As this latest (still beta) root method does not involve an altered image how does one backout an already rooted image and apply this new method when officially released? Will that be the best thing to do going forward?

I read that where there are concerns that this latest method may be blocked with the next Lollipop update.

Thanks
[SuperSU] ramjet73:
Please read the release notes as [MENTION=631273]Chainfire[/MENTION] requested.

ramjet73
[SuperSU] emanuele1986:
thank you, i want to flash semaphore kernel. Have i to flash super su before or after the flash of kernel?
[SuperSU] Oops...:
Sequence doesn't matter.
[SuperSU] Srandista:
It shouldn't matter, but I personaly flashed kernel first, and then SuperSU.
[SuperSU] tracerit:
I'm having an issue with supersu not prompting me. When a new app needs root access it'll just time out. If I go to supersu and change prompt to grant, then that app will get root access. Seems like the prompt is there but isn't showing up?

I'm guessing something must've happened because all the apps that were granted root access before this still get root access, it's just the new apps that time out.

Any ideas? I've tried in installing and reinstalling supersu from the playstore.
[SuperSU] Rushing:
2.27_beta flashed with openrecovery-twrp-2.8.2.0-mako.img started with total stock 5.0 lollipop except twrp recovery

Working Great on my mako, thanks for root BossMan

will update if any need
[SuperSU] albert_htc:
I rooted stock nexus 5 lollipop with cfautoroot

How do I reverse that and flash either beta 2.27 or the full version when released ?
[SuperSU] corumuk:
for info, coming from factory image and rooted with cfautoroot, flashed 2.27 on my nexus 10 from twrp and supersu fc's after boot and has vanished from the app drawer. playstore shows it as installed but fc's when open is selected. root explorer stops responding when in root folder and toggling r/w.
[SuperSU] PeQuEsan:
You just need to reflash stock kernel (boot.img) from lollipop to revert changes done by cf autoroot. Then flash 2.27, and you're done.
[SuperSU] :
Flash the zip via TWRP.... :good:

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

To get prompts, go to SuperSU>Settings>Under Access tab change Default access to Prompt and reboot... :good:

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

Looks like the new version didn't roll to your region....

I'm from India and in my PlayStore SuperSU is still stuck at v2.01... :eek:

I just flash the latest zip from this thread...

You can download the zip and extract it, and voila there's the SuperSU apk which you can use to sideload and manually update SuperSU... :good:
[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. Please help me.
[SuperSU] dk1870:
Issue with xmodgames...

Hey there. I just flashed up to 5.0 on my nexus 10. Rooted and flashed SuperSU 2.27. I can get in to SuperSU just fine so obviously its rooted. I uninstalled xmod and redownloaded it and when i open it it tells me that my nexus isnt rooted and that i can download a app called King Root. So I did, opened it and it showes a big green check mark saying that its rooted. Now i know that xmod has granted permissions and im rooted, but why does it tell me that xmod doesnt have the right permissions. I have screen shots of everything.
[SuperSU] ramjet73:
Please read the release notes

Another reminder that the release notes for the 2.27 beta that [MENTION=631273]Chainfire[/MENTION] asked everyone to read before downloading that version specify that reports and problems for SuperSU 2.27 should be posted in his SuperSU beta thread or his G+ post.

If you are already using the 2.27 beta version and haven't read the release notes, please take the time to do that now. :good:

ramjet73
[SuperSU] Scott:
Wow I feel like an Ass... I never saw that request... I am going to go fix all my threads now.

Edit: DONE!

Thanks for all the work you do!
[SuperSU] :
Flash the SuperSU zip through TWRP... :good:

---------- Post added at 11:01 AM ---------- Previous post was at 10:55 AM ----------

Can you please explain how to remove SuperSU settings from settings tab in custom roms???

I'm running PA, flashed SuperSU via TWRP and SuperSU now handles root operations...

But it bugs me to find Superuser settings still left behind although it is of no use...

Is there any way to remove this superuser settings which is baked into the rom???

Another thing is that why does CM, PA and all other major custom roms use the prehistoric Superuser instead of the immensely popular and frequently updated SuperSU??? :confused:

---------- Post added at 11:03 AM ---------- Previous post was at 11:01 AM ----------

This has got to do with XMod rather than SuperSU... :eek:

Off topic, how can a XDA member whose post count is 1 post in development thread??? :confused:

I mean dude, your 1st post on XDA is on SuperSU thread and that's legendary... :cool:
[SuperSU] dk1870:
Nice.:laugh:. Yes i do only have one post, and yes I did come to SuperSU because thats what Im working with along side XMod, but I did goto XMod first about this and have yet to get a reply, so i came to the next best place thinking that someone might have an idea. Tx for all your had work!!!
[SuperSU] Zach1928:
Question- I lost root after flashing TWRP and Omni on my transformer pad and SuperSU from the play store isn't working. Will flashing the SuperSU 2.16 zip from recovery re-gain access? Thanks!
[SuperSU] Srandista:
Of course, you lost root after flashing another ROM. Just install SuperSU from recovery and you're good to go ;)
[SuperSU] Scott:
Simply put... Haters are gonna hate.

SuperSU is not open source. When you build a ROM from (open) source generally you try to add in a (open) source level Super User app. Hence, you get old stuff.

If Chainfire gives up the source code and posts it on git or whatever I know I would use it in my ROMS. Also, when I build source ROMS, I intently leave out the built in Superuser for the same reason you stated... Its not as good as SuperSU.

When I build ROMS from stock images (Sense, Touchwiz, etc) I do include SuperSU.
[SuperSU] gorilla p:
Yeah, I agree, but some ROMs have SuperSu tab in settings.

Idk what device you use, but if its at all popular, there is probably a Dirty Unicorns build for it. DU has a SuperSu option.
[SuperSU] roundaway:
Unlocked, TWRP 2.8.2.0, Stock Lollipop, previously rooted with CF-Root.

Decided to fastboot the stock boot image so I could try the 2.27 beta. Now I can't boot into recovery. Reinstalled TWRP via fastboot but no good. When at bootloader and rebooting into recovery I get the TWRP splash but then the rom boots. When I use adb reboot recovery same thing. What did I do wrong?

Sorry, wrong thread. Ignore
[SuperSU] yatsura2k:
I seem to have a problem with v2.16 (and later) on my Moto G (UK retail 4.4.4).

When 'Default access' is set to 'Prompt', the GUI appears but I am unable to interact with it,

so eventually it times-out and the root acces request is denied.

Changing theme doesn't help.

If 'Default access' is set to 'Grant' things work normally.

This issue does not exist with 2.02 and earlier.

Any ideas ?
[SuperSU] mindmajick:
I bet if you read the last ten pages or so you'll find the answer.
[SuperSU] yatsura2k:
D'Oh ! Missed that, sorry :(
[SuperSU] :
Go to SuperSU settings and disable Tapjacking protection... hope this helps... :good:

---------- Post added at 09:58 PM ---------- Previous post was at 09:57 PM ----------

I use condor with CM/PA...
[SuperSU] yatsura2k:
Thanks !

It's easy to find more information onec you know to look for 'Tapjacking protection'.

In my case Lux is the culprit, so the solution is to either disable Tapjacking protection, or 'pause' Lux

when I need to grant access to something.

Lux's developer has also committed to implementing a receiver for SuperSu's 'hide overlays' intent in the next version.
[SuperSU] :
Open source

Apologies beforehand, I may be naive/this may have been answered before/this is not meant to hurt anyone!!!

[MENTION=631273]Chainfire[/MENTION] Why not make SuperSU open source??? Are there any disadvantages? :confused:

Seeing GravityBox, Superuser, CWM being all open source I'm asking this...

Making this open source will also help it to be included in custom roms... :victory:

Just asking out of curiosity Sir...
[SuperSU] Chainfire:
Because I don't want to. It's been a long debate and people have been whining about it for years, and I see more drawbacks than benefits. Before anyone starts, this is not a discussion we're having here, so don't even go there. If you need open source, use an open source solution. SuperSU isn't one.
[SuperSU] atomic339:
Why someone want to revert stock kernel? What differences are between stock and cfautoroot?
[SuperSU] Srandista:
Because of testing purposes, for newest SuperSU beta 2.27, which don't need to have modified kernel to work.
[SuperSU] :
This is pretty much sufficient Sir, an answer from your end. :)

Of course not Sir, I'm grateful to have received a reply from you and that itself has served as the cure for my itch... :D

Of course not Sir, SuperSU is the best solution I've ever found and it's not without reason people refer to ya as God of android development... :angel:

As I posted above [MENTION=631273]Chainfire[/MENTION], I'm not complaining at all Sir.... was just curious...

Thanks again... :good:
[SuperSU] Chainfire:
Opinions on the future of the ACCESS_SUPERUSER permission can be spewed here: https://plus.google.com/113517319477420052449/posts/Ka3ujLb4bJu
[SuperSU] Chainfire:
v2.30 BETA out now - BETA-SuperSU-v2.30.zip - RELEASE NOTES - please read the release notes and test ASAP :)
[SuperSU] A7med9050:
droidvpn

Hi there

i want first to thank you about this program

But i do have a small issue is that my droidvpn doesn't work as long as supersu is enabled, it would be working only when i disabled supersu

So could you please help me about that

Thanks
[SuperSU] 78Staff:
You would have to decompile the settings apk and remove the header for the superuser app. Then you would need to create a new header linked to an intent that would open the SuperSU package. I saw some commits on github a while back for aosp, but don't have the links anymore...

EDiT - here is was...

http://xdaforums.com/showpost.php?p=54519190&postcount=6212
[SuperSU] CyberpodS2:
NI2 Acheron Rom on retail S5 running safestrap with tons of xposed modules. Updated to 2.30 from 2.27 with no ill effects. Being a layman, your 1 or 2 question means nothing to me so my vote is whatever you think is best. Thanks for your great work bro!
[SuperSU] Takamoto:
Hi all..I have this situation..

..is dangerous disable those action? ..now is always in background?

Tnx..:)
[SuperSU] egingell:
[MENTION=631273]Chainfire[/MENTION] has stated that he will not provide support if Xposed is running.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] Takamoto:
what a pity, I was hoping for help..
[SuperSU] isaak:
In your first Greenify screenshot, there is a reference to 'keyguard is unlocked' (keyguard = lockscreen, I think that part of greenify was badly translated in your language) ... probably it is inherent to the Pin protection offered as pro feature in SuperSU but I'm not entirely sure.

Now I think we should ask to [MENTION=631273]Chainfire[/MENTION] if this lockscreen permission may be stopped in free version without issues. :)
[SuperSU] visceralpsyche:
2.30 beta running well on Purity ROM 4.4.4 on the Nexus 5 :)
[SuperSU] iwearthebelt:
Attempting to update SuperSu Pro from the Play store , receiving an error "application has bad package manifest".

Problem was on my end, a reboot fixed the issue.
[SuperSU] polobunny:
Same here. Reboot fixed the issue.
[SuperSU] Fadtydawg:
Updated from play store smoothly! S4 verizon. NG6 sch-I545. Thanks +Chainfire! !
[SuperSU] A7med9050:
Supersu

Hi there;

First I would like to thank you about this program, it's such a great one*

but I do have a small problem is that the droidvpn doesn't work since I have rooted my device and installed supersu. It's always *disconnected

It would only work if I disabled supersu, however the droidvpn has been granted by supersu*

please help me about this issue*

Thanks
[SuperSU] mrrocketdog:
just flashed SuperSU v2.16 on att sghi747. all good. thank you for continued support [MENTION=631273]Chainfire[/MENTION]. :good:

"all i can really do , is stay out of my own way and let the will of heaven be done"
[SuperSU] Chainfire:
v2.35 out now - release notes
[SuperSU] ironia.:
ON nexus 5 Did you suggest twrp 2.8.1.0 or the latest 2.8.2.0?

It s possibile flash supersu with temporary twrp ??

Tnx a lot

[emoji2]
[SuperSU] regisso66:
All ok on my N5, multi-user ok too.
[SuperSU] osm0sis:
[MENTION=631273]Chainfire[/MENTION] are there any other contexts that could work? system_app doesn't allow cpio to unpack symlinks anymore with the official Lollipop release.

Edit: Nevermind! Turns out just the default init context works now where it didn't before. Must be your patched sepolicy. Great work! :)
[SuperSU] VivaErBetis:
Newest 2.35 version working flawlessly in nexus 4 and nexus 10 both lollipop stock.

Thanks [MENTION=631273]Chainfire[/MENTION] :)
[SuperSU] CsR0501:
SuperSU 2.35 Working awesome in moto x kk 4.4.4 (Retail Brasil) [emoji111]

Thanx [MENTION=631273]Chainfire[/MENTION]!

Enviado desde mi XT1058 mediante Tapatalk
[SuperSU] FletchF:
Is there any chance that OTA Survival mode will re-appear at some point? Or is it simply not possible on Lollipop?
[SuperSU] CyberpodS2:
Upgraded to 2.35 through play and tested out the additional donation feature. All looking good bro! Thanks again!
[SuperSU] SavanTorian:
works perfectly on note 4 910F (4.4.4) :) thx alot [MENTION=631273]Chainfire[/MENTION] :good::good:
[SuperSU] bjorn96:
2.35 working fine on Z2 4.4.4, thanks [MENTION=631273]Chainfire[/MENTION]

Sendt from my D6503
[SuperSU] deviljoe9900:
2.35 working fine on gt-i9205 5.0 ,thanks [MENTION=631273]Chainfire[/MENTION]
[SuperSU] relevant_placeholder:
Reporting IAP working fine, thanks.
[SuperSU] daystrom:
Is it possible to update from BETA-SuperSU-2.30 to UPDATE-SuperSU-2.35 via the Play store?

When I update from the Play store, opening SuperSU prompts me that the binaries need updated.

When I continue, the installation fails and am told to reboot and try again (which again fails). Installing the zip from TWRP works but just want to know if it is possible to update from a beta version?﻿
[SuperSU] tarroyo:
Is it ok to update the binary for kitkat roms or does it only affect lollipop?
[SuperSU] :
Thanks for the new material app icon, it's pretty much awesome... :highfive:
[SuperSU] GldRush98:
Nexus 5 here. Was on 2.27, flashed 2.35 in TWRP 2.8.1.0.

First boot - Hung on "Android is upgrading" screen on boot. Left for 6-7 minutes and nothing, just stuck there.

Forced power off, and booted back up.

Booted up fine this time. SuperSU is updated and working.

The new icon is HOT!!!

Thanks for the hard work man. This makes Android really enjoyable ;)
[SuperSU] CyberpodS2:
I'm on 4.4.4 and all is fine on v2.35
[SuperSU] thirdcoastraised:
2.35 working perfectly on my SPH-L720T as usual. Thanks [MENTION=631273]Chainfire[/MENTION]

Sent from my SPH-L720T rooted deodexed NG5 ROM
[SuperSU] tom1807:
I had no issues to install it and then update the Binaries.

I used "Normal" due in the past it didn't work through the "TWRP" option.

But my update was from 2.23 and not 2.30

My question now, which boot.img is now useful.

The previous patched which was included with CF-Autoroot or can we install the normal standard boot.img again which was included in Lollipop?

Cheers

Tom
[SuperSU] daystrom:
I believe the oem boot.img is fine to use now.
[SuperSU] Scipizoa:
I got an pro update from playstore and for first time since root it asked to update binaries. It did so with no issues except upon restart it bootlooped until it ran out of battery. I plug it in to charge. Turn it on and it fully boots up xD su 2.35 nexus 7 2013
[SuperSU] CPaladin:
Oh boy, what is changed this time:crying:

Puzzle & Dragons(PAD) NA is broken(quits on launch) with the update to 2.3.5. Now this game always had some issue with root and other low level tweak of system because of the presuming remaining root check code in the Japanese version. But of course to be compatible with lollipop, codes are likely to be changed and the linked analysis might be out-dated.

When I upgraded to lollipop a few days ago I found out the flashable zip method(2.27 beta) wasn't working(again quits on launch), so I tried the CF-autoroot method(2.2.0), and it worked fine. So I guess there's something chainfire changed in order to root that conflicts with PAD. And with the update to 2.3.5, it breaks the game again, and neither direct upgrade from play store nor CF-autoroot method works this time, so I'm rolling back to 2.2.0 for now. Anyone care to look into it?
[SuperSU] FedUpChoosing:
Howdy,

I'm still on 4.4.4 on a nexus 7 2012, it's been rooted for a long time, the 2.35 update showed up in the playstore so I upgraded as I have with each update, the binary update via normal, worked fine and asked to reboot, a normal process.

I have the problem now that when the permissions prompt seems to ignore input, I've tried tapping all over the place but it does no good

Any advice welcome on what happened and how to fix it

Cheers
[SuperSU] pkelly517:
Got Lux?
[SuperSU] maddoc1007:
latest version not working cm7

htc hd2 cm7 gingerbread 2.3.7 latest version 2.3.5 from playstore not working when click on update binary it force closes everytime rebooting phone doesnt work previous version worked fine first time super su has not worked am a super su pro user
[SuperSU] CyberpodS2:
Update: Shortly after doing the update to 2.35 including the pro apk I let my phone do a bunch of play updates including some xpos ed updates. Upon rebooting the phone had approx 3 minutes before getting sluggish and hot booting to a bootloop. Only clearing caches would let it boot but them same cycle. Tried 2.30 and tried removing the pro apk but could not get it back. Ended up restoring nsndroid. Did all the play updates bedides supersu and xposed updates first. Rebooted and still good. Did both 2.35 updates and still good to go.

It seemed like a memory leak or spiral thing. I know xposed nulls out troubleshooting but thought I would report what I experienced on the slim chance others doing the play store update saw the something similar.
[SuperSU] muniz_ri:
Brilliant! the latest update reset the Device Status back to "official" on my G900A.
[SuperSU] satamateur:
Is it working on lollipop flashed via fastboot,....
[SuperSU] Celestial Fury:
I totally forgot I previously translated Super SU (under username Fury). Translators get Pro, right? I've updated the latest strings now. How do I get the Pro licence? :confused: