yashsingh1/xdaforums huggingface dataset:
[SuperSU] shaggyskunk:
Really - I never would have guessed.........

I posted about the SELinux Permissive app - because some people on this thread were talking about it - And even though Google pulled it from the store - It's still available on xda....

Sent From my SM-N910W8 Running SlimLP 5.1.1 RRO Layers
[SuperSU] Chainfire:
Please move talk of your modified kernels/ramdisks and disabling SELinux to another thread (and link it from here?). Thank you.

Haven't had proper time to investigate M root yet.
[SuperSU] jason1332:
We believe in you! :highfive:
[SuperSU] egingell:
48 hexadecimal hours.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] cniels01:
Thanks for all of your hard work! I'm running Android M and would be happy to beta test if another is needed.
[SuperSU] neFAST:
Will you open a new thread on this topic?
[SuperSU] scorp2007:
I have installed on your phone SuperSU Prestigio 3400 DUO, but somehow I do not root rights were given :rolleyes:
[SuperSU] ridobe:
How did you install it?
[SuperSU] SacredDeviL666:
thats installing from playstore without the actual binaries getting installed...
[SuperSU] ridobe:
Yeah, I agree.

edit: [MENTION=6725323]scorp2007[/MENTION] You should download the flashable zip from the first post and flash it in recovery.
[SuperSU] supernova215:
Android M Root

Eagerly waiting for this.
[SuperSU] spevil07:
Root is working at Nexus 6 M Preview.

View attachment 3340345

View attachment 3340346

Preview ROM + Despair Kernel + SuperSU Beta 2.49

Fuc*ing awesome!!! [MENTION=5169465]DespairFactor[/MENTION]

Gesendet von meinem Nexus 6
[SuperSU] narenking:
Flashed Despair Kernel and I can't get 2.49 to flash in TWRP (2.8.6.0).. I was able to get 2.46 flashed, but I'm unable to install BusyBox.

How were you able to flash SU 2.49? Can you now install BuyBox?
[SuperSU] KnifeSkills:
I flashed 2.49 after flashing Despair Kernel r2.4 using twrp 2.8.6.0 and everything is working fine for me. :good:
[SuperSU] kleptonez:
does busy box work? do you have access to system? I did the same but cant seem to mount system as RW
[SuperSU] puritan007:
Did you format data? Yes busy box works. I installed jdx m p4, dispair 2.4, SuperSU newest beta 2.49, good.
[SuperSU] kleptonez:
ooh.. didn't format data. let me backup and try again. thanks!
[SuperSU] kleptonez:
ah, think the problem is the ROM. am using stock Dev image. shall try jdx.
[SuperSU] Apocalypse~:
Is there a similar kernel working for Nexus 5 M Dev Preview, too?
[SuperSU] 19dragon98:
For now no N5 Kernel working with M preview :)
[SuperSU] F4uzan:
I have the source of M Kernel for Hammerhead, but I don't know how to hack it to enable root. Some input will be appreciated, I might be able to enable root in it.
[SuperSU] a g bell:
Cf did ask not to discuss these things here l am going to start a thread in general nexus 5 if anybody interested. Not really worth but hey

http://xdaforums.com/showthread.php?t=3123469

Rooting android dev preview
[SuperSU] silvertrain78:
Please do, and circle back with a link
[SuperSU] climhz:
still sunday, everybody!!!
[SuperSU] a g bell:
Depends on your time zone?

Point of interest? http://xdaforums.com/showthread.php?t=3123469

Rooting android dev preview
[SuperSU] KingMKH:
pleased do something about Rooting G900FD on lollipop
[SuperSU] egingell:
Please do something about the amount of detail in your post. "It's broken" isn't good enough.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] KingMKH:
thank for your attention

the problem is " supersu.zip or recovery file cant deknox and full root the G900FD on lollipop these files just working on 4.4.2"
[SuperSU] munkustrap:
Everything works normal, which means great, as I flashed it thru TWRP 2.8.6 on my LeTV X600 (Lollipop, MTK6795). Unfortunately, the phone could only update by OTA when unrooted, or it will verify the wrong version of /system/bin/app_process64, and /system/bin/install-recovery.sh...

but by using the unroot function in SuperSU, it will only replace the app_process64 with the backuped app_process64_original in the same directory(maybe there are others, I didn't get them all), but delete both the install-recovery.sh AND install-recovery_original.sh, which causes stuck on boot after OTA. I have to manually backup the original install-recovery.sh and adb push it back to /system/bin/ after unroot to get my device OTA.

Suppose this can be fixed given SuperSU can recover other backup files seamlessly when unroot?
[SuperSU] kutulu32:
in the newest firmware of lg flex2 5.1.1 SuperSU cannot be installed(no root) . Anybody found a way ? should we wait for a newest version of SuperSU?
[SuperSU] brando56894:
I can't flash 2.49 at all on my N6 using TWRP 2.8.6.0, it just reboots TWRP each time I try to flash it. Doesn't matter if I try to flash it to an LP ROM or M.
[SuperSU] k4bbe:
Sounds like a corrupt or bad download... I've noticed that behaviour as well with some zips that were bad. Download and go again I would suggest. [emoji41] [emoji106]
[SuperSU] IaKnightHawke:
I had success with using the apk from the common folder. I did try using TWRP method 1st no luck. System specs: Lg G3 vzw variant. Skydragon 4.0 lollipop rom (version 5.0.1) with Skydragon 4.1 kernel. LSpeed 2.2 mod. Beats audio ,ViperFx and ViperHifi audio mods.
[SuperSU] KingMKH:
hello

can anyone tell something about problem of rooting G900FD on lollipop with supersu????

current packages (recovery mode & zip file) cant full root and deknox in lollipop just working on 4.4.2 please share your info about this problem.

thanks
[SuperSU] Iceman248:
I have a question on the check mark to the right of the trash icon in version 2.49 when using a tablet. It was clickable, so I did so, now with same app even after ungranting and other apps, it's greyed out. What it is exactly?
[SuperSU] nEUTRon666:
Android M love?
[SuperSU] RandomPooka:
Stop
[SuperSU] a g bell:
Look and you will find
[SuperSU] MrKaon:
Need to flash custom kernel.
[SuperSU] Jonny_12-:
5.1.1 Galaxy S6 Edge

So I gave my phone the 5.1.1 update after rooting it of course. But it seems like I lost root access. Supersu says there is no binary installed and that it cannot install it. Someone suggested flashing the .zip via twrp which I did but it got me stuck in bootloader and I had to use my backup of my rom to undo it. I was wondering how to get root access again with this 5.1.1 rom because someone on another posted showed how to fix the ram issues but I need root access for it, thanks.
[SuperSU] Mariner_1712:
This did it!

Thanks.
[SuperSU] khairulez:
You're welcome [emoji4]
[SuperSU] kmcphee:
Working fine for me.
[SuperSU] BookCase:
I had the same issue, went into supersu settings changed default action from prompt to grant
[SuperSU] BookCase:
Example...
[SuperSU] mirroalex:
Thanks for the Info, it is somehow temporary solution, I dont want to grant permission to any process, so it need permanent solution...
[SuperSU] jurben:
I don't think it is about supersu.

Android searchs the zip in /data/local/ and if it is there it is used, if it isn't there android searchs in /system/media/
[SuperSU] Chainfire:
I don't think these are related, to be honest.
[SuperSU] Chainfire:
Please provide a logcat of you opening SuperSU, allowing it to update the binary using 'normal' method, then failing, then opening SuperSU again - all without rebooting.
[SuperSU] Chainfire:
"Unable to get root permissions" is pretty vague. Do you even get the popup? Please describe in much more detail what happens.
[SuperSU] hasitur:
ASUS MeMo PAD HD 7 ME173X

Framaroot for SuperSU v2.11 installed

Thanks.
[SuperSU] JaCh0o:
Thank you, for taking care about this issue. Here is my logcat (I'm not sure did I prepared this file properly).

SuperSU 1.92 using 'normal' method gives positive result (successful), but after random while, when entering SuperSU again ask to update binaries (no root permissions again). Looks alike su binaries are related from /bin/su. Just my thought.

I got this logcat.

If you any I can install update to newer SuperSU (will get installation failed).

logcat194.zip - from command prompt logcat: reboot > enter SuperSU 1.94 > Update binaries > Normal > Successful

logcat202.zip - from command prompt logcat: reboot > enter SuperSU 2.02 > Update binaries > Normal > Failed

logcat211.zip - from command prompt logcat: reboot > enter SuperSU 2.11 Beta > Update binaries > Normal > Failed
[SuperSU] Chainfire:
Just in case it's not clear: I would like the logcat from 2.11
[SuperSU] Alex_rac:
Hi i ve manager to get it work using the rootkit for xperia z2(for Windows) But i ve overwrited the files with the ones provided in the 2.11 beta zip ( files situated in the common folder and in the arm folder)

At this point i think that the problem is in your install script ( maybe wrong permissions)?
[SuperSU] Fivesack622:
Chainfire,

If it helps you, I am willing to wipe my phone, reflash 4.4.2 with Odin so it's a fresh install again, reroot and install SuperSU and see what happens with no other apps installed to completely rule anything else out. This is the only day I can really do that though because it is my only day off. I can provide locats of each reboot until it asks for a binary update again as I did in post 156 and 157. I have seen it take up to close to 10 reboots before it finally asks for that binary update however.

The other thing I could also try is to unroot with SuperSU and try another root method if you think it's something related to towelroot. The only other root method I have read that works is Kingo though.

Either way, I'm willing to try either option it if you think it might help or make some kind of difference. Just let me know and I'll get on it...
[SuperSU] Chainfire:
I have not had a chance to review your logcats yet, unfortunately. Been away for the weekend to a conference and I'm just catching up on everything. Wiping and re-installing would be a good attempt, though I suggest making a full backup with TWRP before doing so (if that is possible on your device).

Big chance the issue will not reappear though.
[SuperSU] Fivesack622:
Locked bootloader so no TWRP for me. I'll back up my apps with Titanium, get started, and let you know what happens.
[SuperSU] JaCh0o:
I've added logs to post. Currently got error in TWRP 2.8.0.1 (strange becouse month ago i could flash this file):

"E: Unable to open zip file"

when trying to flash BETA-SuperSU-v2.11.zip or BETA-SuperSU-v2.08.zip. As soon as I'll manage to flash it will provide logcat.

EDIT: Same error by CWM Gummy Recovery and TWRP 2.7.1.3:

E: Can't open /storage/sdcard0/BETA-SuperSU-v2.11.zip

EDIT2: Menaged to flash - error coused by corrupted zip file (needed to redownload). Logcat form SuperSU BETA 2.11 added to post.
[SuperSU] onewaydown:
I'm having the same problem too. Always Grant is a workaround but if you set that back to Prompt, the issue returns.
[SuperSU] Fivesack622:
Wipe and fresh system install didn't work. After the fourth reboot, it asked for a binary update and failed. I have attached the logcats starting with the installation of Beta 2.11 and ending with the prompt to update the binary.When it failed I did not reboot and opened SuperSU again, just as you asked another member to do.

The last logcat (failed binary update) will have to be in my next post as I have a four attachment limit.
[SuperSU] NeoLogY:
If I were you, I would check again with the person who fix the ram issue, how did he get rooted on 5.1.1. As you said flashing zip through recovery got stuck, which version did you flash? Tried 2.49? As this one more lollipop compatible.

Sent from here to there
[SuperSU] paleman27:
Worked 4 me! Thanks!
[SuperSU] edgarf28:
[MENTION=631273]Chainfire[/MENTION] SuperSu 2.49 (and older) doesn't work indeed on the just released Android 5.1.1 update for the Galaxy S6 (Edge) G920T & G925T models.
[SuperSU] Schwamm:
Huawei Ascend G7

I have a Huawei Ascend G7 L03, i've installed CWM (Philz Touch Recorery) to get root access, then I've installed the SuperSu.zip downloader from Chainfire web, so, I dont have the "Install su binary" alert, but when I open a Root App (SD Maid por example) there is no "root access alert" so the app cannot have root access, but when I go to settings on SuperSu, I change the option from "Prompt" to "Allow" and then every Root app have permissions.

So, what's going on? I like so much this app, i have already a Moto G (1st Generation) rooted whit this method, please, give me an answer or something, thanks!!
[SuperSU] ->---:
After auto deny for Titanium Backup, it was updated recently and the permission was asked when I slept, there was no way to get superuser access by simply starting Titanium again as it was on SuperSU 2.46. I had to set permission from asking to allow and then start Titanium but I am not sure if this will work permanently or just for the moment because the app does not show up within the SuperSU list.

Edit: After I set allowance back to ask, removed Titanium from tasklist and started it again, I was asked for SuperUser rights again. Strange behaviour :confused:
[SuperSU] cakletzing:
SuperSU 2.49 Fixes No Prompt Issue

SupersSU v2.49 works fine on ATT SGS5 with the FlashFire 5.0 Stock OC4

and fixed the issue I was having of no prompt when apps requested root!

Thanks Chainfire! And, I'll throw in a pitch that anyone who uses SuperSU

should get the PRO version!!!
[SuperSU] ** A - R **:
Update

[MENTION=631273]Chainfire[/MENTION]

No New Update (atleast Beta) ?

Thanks .

Your Feedback's Heartly Appreciated.

---------- Post added 23-06-2015 at 12:06 AM ---------- Previous post was 22-06-2015 at 11:27 PM ----------

My SU Pro Tweaks

1. Permission - Grant

2. Show Notifications - Disabled

3. Logs - None

4. Keep logs - Never

:)
[SuperSU] NZgeek:
So anything that wants root will get it, and there are no notifications or logs to tell you what got root and when?

Nice! Your phone note has about the same level of security as an iPhone (XARA flaw) or a Samsung S5/S6 (keyboard updater flaw).
[SuperSU] ** A - R **:
NP, For Me :D :p

But I just Hate dose Annoyances !

& I dont think dat flaw will occur !, As I do not have Any Account Signed :)
[SuperSU] sp@wn:
Thanks.

It works for Wakelock Detector!!
[SuperSU] Rinoceros:
Let me guess; you are probably not using either anti-virus and firewalls on your pc's, isn't it? :silly:
[SuperSU] ** A - R **:
MS Essentials :) ;)
[SuperSU] ** A - R **:
[MENTION=4163343]NZgeek[/MENTION]

Apart from My Tweaks.l,

S6/S5 Being Non-Rooted That Flaw came !!

Then What Kind of SECURITY is that !!
[SuperSU] windy2020:
samsung galaxy s5 G900F

Hi chainfire just a question my s5 has been flashed to the new baseband G900FXXU1BOE5 I have tried using ur cf auto root and when it installs my phone restarts and stays on s5 logo with recovery at top , then I have to turn phone of and it stays on same screen so I have to reflash custom recovery to get my phone just to boot and re install my os, is ur update not working with the new firmware flash , or are u working on a new update for this , thanks and apoligize if not in correct forum,
[SuperSU] alphahere:
T-Mobile S5 - G900T - 5.1.1 + Supersu causes bootloop.

G900TTMB1FOF6_TMB (Android 5.1.1) with supersu version 2.46 causes a bootloop (soft brick). See this thread for more details.

http://xdaforums.com/tmob...5-1-1-t3140695

I the program that is causing the bootloop is /system/xbin/daemonsu when it replaces /system/bin/app_process32.

I guess this is the same problem the previous poster has.

Any additional information needed to help solve the problem?
[SuperSU] NZgeek:
Try the 2.49 beta - the zip download is on the first page of this thread. There have been some fixes to Lollipop on Samsung devices that will probably help you.

---------- Post added at 08:56 AM ---------- Previous post was at 08:53 AM ----------

If you have TWRP (or PhilZ or CWM) recovery, download the beta zip from the first post and install that via recovery.

CF-AutoRoot probably contains SuperSU 2.46, but you'll need the fixes added to the 2.49 beta in order to get your phone to boot.
[SuperSU] alphahere:
I tried the latest beta and got the same result. I forgot to mention this in my post. Thanks for the tip.
[SuperSU] windy2020:
the thing is I cant even get on to the proper recovery screen like I said I install recovery phone restarts then it shows Samsung s5 logo and recovery before it is spose to go into recovery but it doesn't just hangs on that black screen , that's my problem with this new update on mybaseband its impossible to get past that first recovery screen.
[SuperSU] pnr2020:
Will there ever be a way of rooting g920f on 5.1.1 without using custom kernel
[SuperSU] egingell:
Maybe, but this is the wrong place to ask.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] CyberpodS2:
I would take this to the forum for your device. I have a Verizon s5 and there are specific instructions for it. Between safestrap on 4.4 and flashfire on lollipop you need to be using the correct tools.
[SuperSU] MaLiXs:
today i'm feeling againb like a noob... I can't find the menu to change de default launcher... A I have installed google now launcher and I won't get the toast that let me choose my launcher
[SuperSU] bombadier:
Not like this the right place but I will take pity on you, settings -> home or clear defaults for GNL
[SuperSU] kmcphee:
Help your self. For a senior member pathetic
[SuperSU] z31k:
For a senior member, that response is pathetic. You should know better, be polite & considerate. This is XDA.
[SuperSU] steviemch:
No need for that response. If you don't want to help, simply ignore the post and go on about your business.

sent by neural subspace transceiver node.
[SuperSU] hispanico957:
For LolliPop 5.02 on xperia Z3 compact you suggest 2.49 beta respet the old stable 2.46 ?

Thank

Hispa
[SuperSU] NeoLogY:
Even though it's stated as beta, 2.49 was built specifically for Android L compatible/friendly. Also been updated for Kinguser replacement issue. BTW, it won't harm your device just for trying it(don't trust me on this one).
[SuperSU] ceza1380:
I want to ask you guys a question. I wonder if my apps get root permissions. For example when I open Power Nap app it says Power Nap got root permission. So my question is, isn't my root apps get root permissions till I open app manually?
[SuperSU] bombadier:
That is a toast telling you when it is using root permissions, you can turn toasts off have a look in the app
[SuperSU] ceza1380:
Yeah but does it get root permissions when I don't open app? It shows toast when I open app manually! Not on home screen.
[SuperSU] egingell:
As was stated, the toast tells you exactly when the app used root. Apps that run in the background can use root as well.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] MaLiXs:
Nobody are perfect... I have post this in the wrong thread.

Envoyé de mon Galaxy Nexus en utilisant Tapatalk
[SuperSU] sdeft:
Why do I get the message " su binary needs to be updated" with all LP AOSP ROMs that I have tried ?

It is strange as in the updater-script of the ROM supersu.zip is flashed from recovery successfully (during ROM installation).
[SuperSU] Rinoceros:
And if you enter SU, what is the value under settings? Does it show it's working ( can be seen by the version, directly on top)?

Edit:

It might be this issue: http://xdaforums.com/showpost.php?p=60933992&postcount=9156

Read the last line.
[SuperSU] sdeft:
it does work...i think the answer is in the post you provided...
[SuperSU] Rinoceros:
Yeah, it happens half of the time I reboot one of my devices. So don't worry :D
[SuperSU] kmcphee:
You're right I apologize to everyone on XDA
[SuperSU] kmcphee:
I also apologize to you for my comments. I not this way. I was totally out of line.
[SuperSU] tke1384:
I'm hoping I'm posting in the correct forum. I'm trying to root my new SM-N915P Sprint Samsung Galaxy Note Edge. I have TWRP twrp-2.8.7.0-tbltespr installed and from what I can tell working. I've attempted to install UPDATE-SuperSU-v2.46 and after getting boot loop found this thread and tried BETA-SuperSU-v2.49 from page 1 of this thread. Unfortunately, I end up in the same boot loop. Glad I followed procedure and made a backup before installing so I have a working phone but no root. Any advice would be appreciated. Thank you in advance.
[SuperSU] GatoL0c0:
This isn't a thread for rooting.
[SuperSU] tke1384:
Thanks, I thought since this bata tool was recommended to resolve the very error and it installing this tool that creates the boot loop there might be a connection. Thanks for the quick response and have a great day.
[SuperSU] shaggyskunk:
Search xda for CF Auto Root for your device

If you have TWRP installed - And there's a Custom Stock TW based Rom for your device - You can simply Flash the Custom TW based Rom - Enable Developer Options - Enable Root Access - Apps and ADB - You can skip CF Auto Root altogether - If that's what you want.

Sent From my SM-N910W8 Running SlimRemix v1.8.1
[SuperSU] tke1384:
Thanks for hitting me back shaggyskunk. Unfortunatly, that's what started me down this path to begin with. I followed the instructions for crossfire from this thread:

http://xdaforums.com/note-edge/general/easy-steps-stock-odin-n915tuvu1anjl-sm-t2943993

I know it's for a T-Mobil device but it was indicated to follow the same procedure for Sprint phones. Micky387 has suggested before to someone else in another thread it may just mean waiting for an updated version of CF to be released. I'm good with that if that's the case just thought I would investigate every lead I could find.

Thanks everyone who replied. Really good knowing how many people out there take an interest in helping others in our similar hobby.
[SuperSU] z31k:
I've been touting this throughout the sprint note edge forums.. The ONLY way to root would be through a custom kernel with root pre-installed.. CF-autoroot will not work on Samsung 5.1.1. Unless CF comes out with a 5.1.1 version specifically for us. Until then, all we can do is keep searching for a way.. Or wait.. So far, I have come up with nothing.. I tried it from ping-pong, kingroot, cf-autoroot, adb, everything.. It's not looking too good.
[SuperSU] aadil7:
Hi guys,

I hope you are well.

This may have come around but I could not find it due to the sheer volume of posts so I hope one of you guys can assist me.

I was able to successfully apply SuperSU 2.49 and root my s5 on BNL9.

I believe it has not reset my knox counter because firstly the app did not notify me and secondly it showed up as void when I downloaded a knox checker app.

Can anybody advise me on how to reset the knox counter please or what steps I should take.

thanks
[SuperSU] shaggyskunk:
If you used CF Auto Root to gain Root - You've Tripped the Knox flags - There is currently (possibly never) no way to reset the Knox flags - Generally - The only other way to get Root - Is to use Odin to flash a custom recovery - And Flash a custom Rom - Trips Knox as well.

Sent From my SM-N910W8 Running SlimRemix v1.8.1
[SuperSU] aadil7:
Thanks for the response.

What if I flash an old rom 4.4.2 -> use CF auto root -> upgrade rom to 5.0 -> flash rom?
[SuperSU] shaggyskunk:
Knox is already Tripped - Can't change that by flashing anything else.

Chainfire states this in the OP of his threads

Sent From my SM-N910W8 Running SlimRemix v1.8.1
[SuperSU] tetakpatak:
Knox is tripped, no way to reset it. Don't worry about that, the benefits of root are higher.

tetakpatalked from Nexus 7 flo
[SuperSU] Jerry060599:
Root not working on m9 with twrp 2.8.7.0 using chainfire, need help.

I have tried everything I think would remotly work, but my phone simply wont go through with the rooting process. I tried flashing chainfire through twrp 2.7.8.0 but everytime the log gets to replacing files, the phone reboots itself into the system, stopping the root. I can;t get any log either because my phone simply jumps out of the recovery on its own. Any ideas?

extra info:

phone: t-mobile htc m9 hima

bootloader unlocked

s-on

twrp 2.8.7.0 and 2.8.5.0 (I tried both)

chainfire beta 2.49 and the lastest official stable build (I tried both)
[SuperSU] Snowby123:
Did you try flashing with flashfire?