yashsingh1/xdaforums huggingface dataset:
[SuperSU] Jerry060599:
I actually do not know what flashfire is. From a brief view of it though, it looks like it requires root. I currently do not have root on my device, hence my posting here. :(
[SuperSU] Snowby123:
Here is a thread you might find helpful. Although designed for the Samsung Galaxy S6, The opening post says there is an experimental build for the One M9; unlocked bootloader required

http://xdaforums.com/galaxy-s6/general/root-pingpongroot-s6-root-tool-t3103016
[SuperSU] Jerry060599:
M9 is supported on that thread, but, unfortunate, I may have backed myself into a corner by upgrading to android 5.1. Is there anyway to diagnose the issue? This issues seems to be pretty rare for I can't seem to find any past cases. Could it be something I did that singled me out?

Maybe this list of what i did can help?

1. Bought phone tday at t-mobile.

2. got home and immediatly ran a software update with the stock os

3. updated to 5.1 and proceded to unlock bootloader.

4. flashed twrp 2.8.7.0

5. made a nandroid backup of stock os

6. flashed cyanogenmod 12.1 unofficial build beta 2 for m9 and gapps package

7. found ramdom crashes to much to bare, so i restored to factory settings (from the previous nandroid backup)

8. attepted to root using chainfire beta.

9. panick ensues as I tried both chainfire cersions with both twrp recovery.

(another odd thing i noticed is that the mount system check box under mount seems to be unchecked everytime I mount usb storage or reload recovery. Could it be that the phone is having trouble mounting system somehow?)

p.s. I just want to say thank you for the time you spent helping me out with this. I am completly out of tricks so any help is greatly appreciated :)

edit: I just noticed that everytime the phone self reboots, I get a HTC error report notification wherein I can check the crash log. Would that be of any help?

edit 2: Here is the crash log obtained from the crash notification:

http://pastebin.com/BzAvTXxF
[SuperSU] Snowby123:
You have said multiple times that you tried to root by installing supersu. Simply installing the apk will do you nothing. You need to have the su binaries properly installed to have root. Also, I don't know how to read Crash reports so all I learned from skimming through that is you took the report today. Did you try reading through any of the root tutorials found online? I have found at least three different techniques through a simple Google search.
[SuperSU] Jerry060599:
I have rooted before so I didnt really feel the need to initailly. After running into this issue, though, I went out to find all the rooting vid/posts there is for m9. All of them require the use of twrp and chainfire. idk... either that or I missed some very important posts. :(
[SuperSU] Snowby123:
Did you try any of them? You said you have twrp so it does not sound impossible
[SuperSU] Jerry060599:
Yes, I actually went ahead and downloaded three different versions of super su, none of which worked. All three crashed in the same way. Right now I am trying to find a way to get the crash log out so we would hava something to go on, but sense twrp outright crashes, there is no way I know to retrieve it through twrp and adb cant access cache when the phone is booted up. Is there any other way?
[SuperSU] Snowby123:
I don't know personally how to solve that. However I believe you would get more people to help you if you shared your problem in the Q&A section of the one m9 forum
[SuperSU] Jerry060599:
Ok, thank you for your time :) link to the thread incase anything come up. http://xdaforums.com/one-m9/help/root-m9-twrp-2-8-7-0-using-chainfire-t3167476
[SuperSU] Paschfire:
It is normal that the system partition umounts at time's(no check in box), most Rom zip's and mod's including superSU have a script tell the system partition to mount and unmount. Before, after, even during there installation process. So unless you need to mount the system for a specific reason, just leave TWRP to control its mount position.
[SuperSU] Jerry060599:
Is this compatible with the latest firmware version? (2.7.531.6) From what i have seen on other dev threads, the firmware could potentaily be the cause.
[SuperSU] Frank Westlake:
I just glanced at the tail end of this and saw references to crypto. If this device is encrypted that might be the problem.

Frank
[SuperSU] NeoLogY:
Good to see you Frank. Its been a while.
[SuperSU] Jerry060599:
I believe I have my cryto turned off.
[SuperSU] alazizie:
Hi,

Can you please make an option to backup granted and denied apps list? So that no need to grant permissions or deny them again for the same apps after flashing a new rom.

Thank you
[SuperSU] Snowby123:
That would be super convenient, yet I can't imagine how difficult it would be to add that feature
[SuperSU] shaggyskunk:
You can just go into SuperSU settings and change the SU Access from Prompt to Grant - But are you sure that you want to do that?

50,000,000+ people are running SuperSU as is - Doubtful that Chainfire will see the need....

There's already a Script that you can install to survive Nightlies etc

Sent From my SM-N910W8 Running SlimRemix v.2.2
[SuperSU] maxed4901:
Urgent help requested

Hello... [MENTION=631273]Chainfire[/MENTION]. I am on exodus lollipop 5.1 nightlies 1/8/15. I started getting "SUbinary needs update notice so I flashed the beta 2.49 here. But still it says I need to update binary. How can I resolve this? SuperSU is baked into the ROM. Device is one plus one.
[SuperSU] Fadtydawg:
Runs great sg4 Sch-i545 OC1
[SuperSU] F-L-Y-E-R:
In cyanogenmod there is an option to disable built-in super user, go through the settings you should find it.

If it doesn't exist, go to SuperSU settings and check 'install SuperSU into /system'. I am not completely sure but one of those makes SuperSU default root app.
[SuperSU] maxed4901:
Super su binary

Mine says it's already installed into system. For readers; this issue seems to be caused by the ROM and not the superSU. I flashed the beta 2.49 but no resolve which should have been resolved as I was on stable 2.46 n 2.49 though beta should have updated the binaries. There's no record of any other users facing this issue on exodus 5.1 and the developer decided to make a billboard out of my many enquiries. No reply at all. Having screen lag and sort of issues can be prioritised as medium but root issues are sensitive and m ashamed of Exodus realy. Already ditched it because its not an accountable rom for me..

That said, I have flashed latest 5.1 cyanide + CM nightly with different kernels as well. The issue only seems to be when I flash exodus late builds. Maybe something [MENTION=631273]Chainfire[/MENTION] could look at as well. Exodus claims to be based on CM builds.
[SuperSU] vel_tins:
LP 5.1.1 - Any chance to use the "old-style" updater-script to root?

My device:

i-mobile IQ II

Android One, LP 5.1.1, Snapdragon 410

NO TWRP/CWM available and I guess the "BETA-SuperSU-v2.49.zip" can only be flashed by TWRP(?)

But I've patched the stock recovery, so that I can flash any update.zip (the "old fashioned" ones).

I managed to copy all necessary files from "BETA-SuperSU-v2.49.zip" to the phone and to chmod them correctly.

But su/daemonsu can't be started, even if I try manually, no error message, nothing.

Additionally, the su binary is not recognized by the SuperSU app.

I guess, the Selinux "chcon stuff" is missing somehow.

Any ideas, how to edit the "updater-script", to get the whole thing working?

My updater-script:

show_progress(0.500000, 0);
mount("ext4", "EMMC", "/dev/block/mmcblk0p25", "/system");
package_extract_dir("system", "/system");
set_perm_recursive(0, 0, 0755, 0644, "/system/app");
set_perm(0, 0, 0755, "/system/xbin/su");
set_perm(0, 0, 0755, "/system/app/SuperSU/SuperSU.apk");
set_perm(0, 0, 0755, "/system/xbin/daemonsu");
#set_perm(0, 0, 0755, "/system/bin/daemonsu");
#set_perm(0, 0, 0755, "/system/bin/su");
set_perm(0, 0, 0755, "/system/xbin/supolicy");
set_perm(0, 0, 0644, "/system/lib/libsupol.so");
set_perm(0, 0, 0755, "/system/xbin/sugote");
set_perm(0, 0, 0755, "/system/xbin/sugote-mksh");
set_perm(0, 0, 0755, "/system/bin/.ext/.su");
set_perm(0, 0, 0755, "/system/etc/install-recovery.sh");
set_perm(0, 0, 0644, "/system/etc/.installed_su_daemon");
set_perm(0, 0, 0644, "/system/etc/hosts");
#delete("/system/app/SuperSU/SuperSU.apk");
delete("/system/app/SuperSU/Superuser.apk");
delete("/system/app/Superuser.apk");
show_progress(0.200000, 0);
show_progress(0.200000, 10);
show_progress(0.200000, 0);
clear_misc_command();
unmount("/system");
[SuperSU] Mrcactuseater:
You need to chill right down man and explain carefully, and in detail, what is wrong.
[SuperSU] Tylog:
Do you really believe when you post in such a unfriendly style people are willing to help you?

Punctuation marks are not pack animals , maybe you should reconsider your post, then you get certainly more help.
[SuperSU] :
How's about turning off cap lock. Try some proper sentences. Give some constructive details of your issue.... And maybe someone can help.

Otherwise, no point posting if all you got is nonsense. :good:

Darth

Forum Moderator
[SuperSU] svnhvn:
:sly:
[SuperSU] mmonaghan34:
For anyone here to be able to help you, we at least need what rooting methods you have tried, device, exact android/rom version and what state said rooting methods have left your device in, from your post it just seems like a rant more than a request for help though, people are more willing to help if you ask politely rather than caps lock and over usage of the same punctuation everywhere, eg "!!!!!!!!!!!!!"
[SuperSU] ->---:
Does somebody know if 2.49 will ever come out of beta status? Maybe it was already mentioned somewhere in the thread and I missed it.
[SuperSU] Snowby123:
I am assuming it will at the end of this month or the next because chainfire said he will be away from the forums most of the summer. But that is just my guess.
[SuperSU] CyberpodS2:
With millions running it, I wouldn't sweat it being named a beta. Just install it. :)
[SuperSU] ->---:
I run it for months now. It just has some touch of unfinished business that it is a permanent beta and I thought that maybe the project is silently abandoned.
[SuperSU] a g bell:
OK anybody rooted dev preview m3 on nexus 5 And found the SuperSU apk is missing?
[SuperSU] Ja_som:
No issue with Despair kernel...
[SuperSU] rpr69:
Or Blue Spark.
[SuperSU] MrKaon:
SuperSU doesn't support Android M yet.

Root access is possible with only modified Kernel (Selinux disabled), which is not a proper way. :eek:
[SuperSU] rpr69:
SuperSU works fine for me, and my kernel is permissive, not disabled. Not as good as enforcing, but until we get actual kernel sources, I think it's the best we can get at the moment.
[SuperSU] wizardwiz:
does this version (V.249 Beat) support only Android M or Lollipop as well ?
[SuperSU] DocteurN:
Yes Lollipop as well [emoji6]
[SuperSU] wizardwiz:
so download it from the first page and flash it via TWRP ?

EDIT: flashed it. working like charm

Thanks
[SuperSU] TEFjLONjDON:
How to Flash without TWRP? AND is root access a Prerequisite? Or...

OK now I sound like a knob but any one got any ideas how to get root on SM-G360T1 Im on Android 5.1.1 after i have root i can use this Beta-Supersu v2.49 to test on this device..

this Device has an ability to turn of the lock on the Bootloader.. IE... Developer options

Veiw a screen shot Here "ScreenShot of OEM Bootloader Protection on / off toggle switch. " https://www.dropbox.com/s/o2o6ldm605tt54p/Screenshot_2015-08-27-10-14-24.png?dl=0

I can Flash TWRP with Odin but have no Touch Support in TWRP recovery 2.8.7.1

That version is for GALAXY CORE PRIME "LTE" not "T(1)" (SM-G360T1)

I have the factory stock ROM from where http:/www.sammobile.com/firmwares

View a screenShot Here "All the released ROMs for Samsung Galaxy Core Pime varients on SamMobile site" https://www.dropbox.com/s/k3xb5ciab0eu0tf/Sammobile_Firware_ROMs_for_SM_G360T1.jpg?dl=0

We have the Stock recovery.img and boot.img located here thanks to bogarty.

What we don't have:

A working TWRP or CWM recovery.

A Rooted Kernel

A or CF_Root

If any one can be of assistance please feel free to Comment here on RichCal's Thread "Galaxy Core Prime SM-G360T1 Root?" or PM one of us...

Thank you in advance..

:fingers-crossed:
[SuperSU] mcnamaragio:
Is there any planned release date for 2.49 ?
[SuperSU] shaggyskunk:
What's wrong with the beta version? Works just fine

Sent From my SM-N910W8 Running SlimRemix v.3.8
[SuperSU] mcnamaragio:
It's not on the Play Store so I have to tell my users to download it from here
[SuperSU] shaggyskunk:
Well - This is Chainfire's Thread - So it's not a mystery link - And "my users"?

Sent From my SM-N910W8 Running SlimRemix v.3.8
[SuperSU] n.praveen13:
This thread isn't updated in a while. Is the development stopped?
[SuperSU] USBhost:
He's just away for most all of the summer

So just give him some more time
[SuperSU] AmphybiouS:
No way to root Galaxy Note 4 with the firmware 5.1.1?

I tried with custom kernel but not work for me.

Thank you.
[SuperSU] dilawer99:
please help me to root INTEX CLOUD 4G Star

I m new to 5.0...i tried this but not get success....it said...INVALID OTA PACKAGE..

scater not working...like this...

Please help me to root...i have fully loaded titanium backup folder nd need to restore it...:(
[SuperSU] egingell:
Sounds like you're trying to use the stock recovery to flash this. You can't do that. You *must* use a custom recovery.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] dilawer99:
bro...is there any way to root it....i dont know about stock recovery..

please helpnme to root only....i m from medical line...and dont know the basics of stock...recovery etc. please help me to undrstand..
[SuperSU] Pkt_Lnt:
This thread is NOT about rooting a device, that is not what SuperSU does. Check in the XDA forums for your phone make and model for help on rooting.
[SuperSU] Snowby123:
I was just about to say that
[SuperSU] gargleblarg:
http://www.xda-developers.com/root/

You should also read the forum rules.
[SuperSU] Phil3759:
Note 4 SM-N910F updated to 5.1.1 stock Samsung ROM

Tried SuperSU stable 2.46 and latest 2.49 Beta

- Bootloops and no way to get back to ROM

- Factory reset with /data and /cache wipe didn't fix boot loop

- Manual clean up of /system from su bins did not fix it

Ended up with a factory reset and formatting /system + whole restore of ROM

If you need info, let me know how to provide logs

Meanwhile, trying an alternative solution
[SuperSU] white7561:
First. Install custom recovery

Then install modded kernel that works for 5.1.1(cuz the stock one cant be rooted)

Then flash supersu beta(for best experience)

Reboot
[SuperSU] Phil3759:
Thanks,

I am aware of that. Just didn't find anywhere in thread a description about the issue under SuperSU

Wanted to post an info to developer, and if he needs logs to develop for Note 4 Qualcom edition

When kernel sources are out for N910F, I will recompile a proper kernel

Meanwhile: I built a stock kernel from sources, you can find in development section. It works perfectly on SuperSU
[SuperSU] organick87:
[MENTION=631273]Chainfire[/MENTION], thank you for all your years of hard work, dedication and innovation that you've brought to XDA as well as the entire Android community. I know you will be slowly phasing yourself out of future SuperSU projects and i hope your values carry over to the new project devs. Excited to see the future of root, but sad to see you make your exit. Time to enjoy life! thanks again!
[SuperSU] Ironjim4102:
Thanks [MENTION=631273]Chainfire[/MENTION] you are one of the reasons Android has advanced as much as it has. Good luck in all you do!
[SuperSU] USBhost:
https://plus.google.com/+Chainfire/posts/XJYJFPtS9Qb

just F.Y.I.
[SuperSU] c3v1t:
Thanks [MENTION=631273]Chainfire[/MENTION] for all you work on SuperSU project, I wish all my best for your new projects. Thank you again!
[SuperSU] SamuriHL:
Thanks for all you've done for the community, [MENTION=631273]Chainfire[/MENTION]. Your work has been tremendous. Enjoy the new projects! Looking forward to see what craziness you've got going on. :)
[SuperSU] Salar14:
system ui has stopped

I flashed beta supersu v2.49 zip file via TWRP and now device has root access but the phone says system UI has stopped . and there is no wallpaper no notification bar ans home key and recent apps key does not work . plz help

device sm -g900f android :5.0

Thanks
[SuperSU] shaggyskunk:
what device & os? TW or AOSP?

Sent From my SM-N910W8 Running SlimRemix V4.8
[SuperSU] Salar14:
I Said. galaxy s5 sm-g900f os :android 5.0 build number : LRX21T.G900FXXU1POG9

TWRP custom recovery
[SuperSU] shaggyskunk:
Sorry - it's early haven't had coffee yet..

Anyway - Just to be sure - You're running a Stock Rooted Rom with TWRP installed?

Which version of TWRP are you running - 2.8.7.0?

Sent From my SM-N900W8 Running Dirty Unicorns 9.7 TEST :)
[SuperSU] Salar14:
yes the latest version for galaxy s5 (2.8.7.0) I flashed .tar file via odin. from this site twrp.me
[SuperSU] gargleblarg:
You said, "now device has root access". Did you have root access before you tried flashing the file?
[SuperSU] Salar14:
no . actually when android version was 4.4.2 device had root access but when upgraded to android 5.0 no. then i flashed supersu v.2.46 via TWRP and didnt work then i installed BETA supersu v2.49 via TWRP and device now has root access BUT system ui has stopped ...

---------- Post added at 01:40 PM ---------- Previous post was at 01:09 PM ----------

Fixed by Factory Reset!
[SuperSU] Flyview:
Hi [MENTION=631273]Chainfire[/MENTION] hoping you could shed some light on my situation as you have in the past.

Device: Nexus 5

ROM: M Developer Preview 3

Kernel: ElemantalX 5.0.3

SuperSU: 2.49 beta

In my app LeanDroid I use SuperSU to run some root commands. Most are still working in the switch from Android 5.1.1. to 6.0. developer preview 3. There is however one command that is not working (the value is not affected, delete doesn't work). Here is the command:

settings put secure location_providers_allowed gps

What's strange is changing other values in the secure settings seems to be working. I suspect it has been blocked by Google from being changed by other processes. I have however tried a few things to help like set the selinux context, or the "user" for the command. I've tried:

su --context u:r:system_app:s0

settings put secure location_providers_allowed gps

settings --user 1000 put secure location_providers_allowed gps

None of the above is working, and I suspect the context switching doesn't matter since it looks like somehow my selinux was set to permissive by default. Any thoughts?
[SuperSU] Chainfire:
I think you should wait for 6.0 sources to drop (next week?) so you can properly investigate. But you are right, if SELinux is permissive, the context shouldn't matter usually. I add usually, because it is always possible some framework code has added checks for the current context name, even though SELinux is not enforcing - unlikely, though.
[SuperSU] Flyview:
I guess so. I believe the relevant code would be in SettingsCmd.java (https://github.com/android/platform...om/android/commands/settings/SettingsCmd.java) though that is obviously an older version.

Another question I forgot to ask: I require users to specifically have root through SuperSU since afaik yours is the only one that allows context switching. Is there a way to specifically detect not just whether there is root access but whether they are using SuperSU for root?
[SuperSU] palmbeach05:
[MENTION=631273]Chainfire[/MENTION] thanks for all the support you have provided with supersu. Out of curiousity, will there be a final beta/public release before the project changes hands and you step away completely?
[SuperSU] Chainfire:
"su -v" and "su -V" give details about which SuperSU binary and version is available. Be sure to write "exit" to su's STDIN in case the su binary isn't SuperSU and doesn't know these parameters, and a shell is inadvertently opened and the call does not return.

https://github.com/Chainfire/libsup...src/eu/chainfire/libsuperuser/Shell.java#L357
[SuperSU] Chainfire:
If everything goes as agreed upon, it will be quite some time before I step away completely. The last version before official handover is 2.49.
[SuperSU] dmroopesh:
Thank you for your years of hard work which made us see the bigger picture of android roms. All the best for your future ventures.
[SuperSU] Ch3vr0n:
[MENTION=631273]Chainfire[/MENTION] does the SuperSU 2.46 work with M for nexus 5 / 7v2 or will i need 2.49 or even a later version?
[SuperSU] shaggyskunk:
You may want to read this:

https://plus.google.com/+Chainfire/posts/XJYJFPtS9Qb

Sent From my SM-N910W8 Running SlimRemix V4.9
[SuperSU] kevtrysmoddin:
The latest is always best
[SuperSU] Ch3vr0n:
[MENTION=4351374]shaggyskunk[/MENTION] and what part of that makes reference to 2.49 supporting M. Oh wait, not 1 bit. And I already have read and.

[MENTION=4176778]kevtrysmoddin[/MENTION]g no it isn't when 2.49 first appeared I saw nothing but problem replies inhere.

Verstuurd vanaf mijn Nexus 5 met Tapatalk
[SuperSU] shaggyskunk:
SmartA$$ What it should mean to even the most dense - is that Chainfire is not involved with SuperSU anymore - He's done - retired....So - Addressing a post to him is not likely to get any response - smh

Sent From my SM-N910W8 Running SlimRemix V4.9
[SuperSU] Ch3vr0n:
Might want to read again, he's not. That post states he will retire and REMAIN INVOLVED for the next 2 years. And FYI be responded to others in post 1912

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] Chainfire:
The reports of my death have been greatly exaggerated - first quote that comes to mind.

I've announced that I'll be gone from this project in at most two-ish years, not that I've left it.
[SuperSU] Chainfire:
I've not really looked at M as there's no final yet. Last year I spent way too much time on the preview versions of L, only for final to work significantly differently root-wise. Not making that mistake again. So I don't really know.

I think I've seen people mention it works as-is on permissively modded kernels, not sure though.
[SuperSU] Ch3vr0n:
[MENTION=631273]Chainfire[/MENTION] thanks, I can't /won't blame you for that. I remember the problems you had. I'll then just keep an eye on this thread after m has been officially released next week. Won't update directly.

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] shaggyskunk:
Yeah - My bad

Sent From my SM-N910W8 Running SlimRemix V4.9
[SuperSU] RandomPooka:
No way. Didn't you see the post up above? You've already left. Presumably, you're on staff for the manned mission to Mars or something. I don't know. How dare you presume to know what you're doing better than some random XDA user???? :)

Thanks so much, BTW, for everything you've done for Android
[SuperSU] nmlssit:
M is out.

Can anyone confirm root is working?
[SuperSU] Ja_som:
Will see after a while, but it was OK on dev. preview, but with custom kernel...
[SuperSU] iopxiang:
It seems to cause bootloop. (N5)
[SuperSU] nmlssit:
Strange, i've been reported root is working on N5, custom kernels too.
[SuperSU] lparcshinoda:
no, it's now. latest superSU beta is actually rooting marshmallow
[SuperSU] swat4samp:
Do we need custom kernel too? Just like in dev preview?
[SuperSU] Ja_som:
So, as on dev. preview, SuperSu works on N5 with Despair Kernel
[SuperSU] domigr:
bootloop on nexus 7 (Marshmallow) after i flash supersu2.49...
[SuperSU] iopxiang:
Could you give me a link to that kernel? Thanks.
[SuperSU] mskulltula:
You need to flash a different kernel before flashing su.
[SuperSU] djkinetic:
root only works on custom kernels with M right now.
[SuperSU] Franzie3:
does this go for the factory image that came today as well? Im just making all backups before i go and flash the image
[SuperSU] haseoxth:
Yes
[SuperSU] Ja_som:
Here is his thread

http://xdaforums.com/google-nexus-5/orig-development/kernel-despair-kernel-t3123747
[SuperSU] MrKaon:
It is out now flashed it in Nexus 5, NO root with selinux enforce mode. :cool: