yashsingh1/xdaforums huggingface dataset:
[SuperSU] sithsu89:
Thanks again for all your hard work. Tremendous job. I can't hold a candle to you total awesomeness! It is a very hard work, but a labour of LOVE.
[SuperSU] 2pacincuba:
Hello Developer, i flashed cm 13 + supersu + gapps on my moto g Falcon!

For some reason supersu is unistalling, and even if i try install by Google play, not works!

This inssue only happens on Marshmallow, in Lollipop work normal!

Sorry for my bad english!
[SuperSU] osm0sis:
Nevermind, I think I figured out a good way using e2fsck. ;)
[SuperSU] ianmacd:
I have just noticed that my Samsung Galaxy Tab S2 (T710) still had a 32Mb su.img after using FlashFire to flash the ZIP of SuperSU 2.76, in spite of su.img never having been modified by anything else.

As a second check, I returned my S7 Edge to stock firmware, rerooted it with CF Auto Root (which is evidently still 2.74 based), and then used FlashFire to reflash the 2.76 ZIP over the top. Again, this resulted in an unmodified 32Mb su.img.

Am I missing something?
[SuperSU] osm0sis:
Is resize2fs present in your recovery?
[SuperSU] ianmacd:
I used FlashFire, not TWRP, but yes, I do have a /system/bin/resize2fs.
[SuperSU] ashishpmb:
Dear [MENTION=631273]Chainfire[/MENTION].

Your great Super SU is a staple for all devs out there.

There is one group over at Echoe who use your work which is integral to their work,give you credit (hooray) but charge it's members a full 10 Euros. I was told that over the last few days 7000 people paid 10 Euros each for work that cannot operate without your hard work.

Question,do you know that your free excellent work is being charged for in part and even though you receive credit, have you been made aware that to a large extent Echoe is selling your and other Devs like [MENTION=469480]zubi[/MENTION] work?
[SuperSU] osm0sis:
FlashFire creates its own /sbin, but I'd imagine it should be present.. pretty much every other thing from TWRP is there (except getprop). I'm not sure why it isn't working for you. My commands should do the trick however.
[SuperSU] ianmacd:
Yeah, it's odd that it doesn't work on two completely different devices.

Can I run your script on a live system or would I need to install TWRP? I suppose su.img is in use and can't be resized live. And I don't think I can use FlashFire to run a script, either.
[SuperSU] heimdallZ:
After update to 2.76 supersu refuz to giv authorisation for some application.
[SuperSU] ktmom:
You don't say what apps, but if any are working, the ones that don't, need to be updated (e.g. ESFileExplorer). If you are dead set on using older apps, search this thread for compatibility. This has been discussed a gazillion times ☺
[SuperSU] grep_i:
You do not need to install a custom recovery to use it you can also only boot it with the use of adb and fastboot commands.

On a live system with USB debugging enabled you do from A shell on your computer with your phone connected through USB

adb reboot-bootloader

fastboot boot path-to-recovery-image

Now it will boot your TWRP recovery without it being installed on your phone
[SuperSU] Nimueh:
I had that problem with ES File Explorer Pro and found a fix through googling (all credit goes to the original poster):

I copied the files with MiXplorer and it worked like a charm, ES requested root privs again and all was good :)
[SuperSU] Psychofrantics:
Guys, Sorry if it has been asked thousand times already but I am unable toi find any definitive answer.

How can I root PA 6.0.1 in system mode? I am suning a custom kernel. When I flash latest supersu, it always install in systemless mode.

I know that for obtaining system mode, you have to make sure that /data/.supersu doesnot exist. I cannot find that file in PA. However there is a supersu folder﻿
[SuperSU] ketanjog143:
when i flashed SuperSu 2.76 stable then my moto g3(XT1550) marshmallow went in boot loop but when i flashed SuperSu 2.62 beta then it rooted ... is there any problem with SuperSu 2.76 stable version??????????/
[SuperSU] grep_i:
Search for compatibility mode on this thread or the beta thread it must been answered many times by now.
[SuperSU] ianmacd:
This may be the problem:

|root@gts28wifi:/data # ls -l su.img
-rw------- root root 33554432 2016-07-17 01:52 su.img
root@gts28wifi:/data # resize2fs su.img 96M
resize2fs 1.42.9 (28-Dec-2013)
The filesystem is not need to resize.It is very close to size to resize

Then again, maybe that's because the image is in use on the phone. If I 'adb pull' it to my laptop, I can resize it there without issue.
[SuperSU] :
I'm a bit out of touch with the SuperSU news (only been installing via Play Store) and the search function didn't give me much info on my question.

I'm currently running a stock 5.1.1 rom, so now the 2.76 stable flashable zip here is auto-systemless right, and to edit the settings I'll need the Play Store manager, because the zip did not install the app itself. Am I right?
[SuperSU] ianmacd:
I thought that this didn't work on (some) Samsung devices. Am I wrong? It's an S7 Edge in this case.
[SuperSU] neeraj.lambaa:
On my moto g2 to root it.

I flash three version of super su but every time got bootloop.

Version 2.51 ,2.74,2.56 etc.

sent from moto g2014 with cm13
[SuperSU] ktmom:
2.76 when flashed through recovery goes through a series of checks to decide if it should/could be installed systemless. Else it installs as a system app. The apk through the play store updates an existing root install. They both have the settings available after install. The play store apk is included in the flashable zip.
[SuperSU] grep_i:
I see two TWRP images for Samsung galaxy S7 on the selection page.

The normal S7 and the edge both with exynos based processor so if you don't have the Qualcomm version it should work don't know the procedure for Qualcomm based processor devices

But there is a thread with descriptions on it.

http://xdaforums.com/galaxy-s7/development/recovery-twrp-3-0-0-0-touch-recovery-t3334685
[SuperSU] ianmacd:
Ha, sorry, no that's not what I meant. I meant that I don't believe that fastboot works on Samsung devices. At least, that's what I've read, so I've never actually tried it.
[SuperSU] grep_i:
No I am not aware of that I guess you should try to find out.
[SuperSU] Pkt_Lnt:
[MENTION=6952047]grep_i[/MENTION] is correct, my command was incorrect.

http://xdaforums.com/showthread.php?t=2277112
[SuperSU] grep_i:
That's what I thought too but I tried it last week and couldn't get it working with that command with adb version 1.0.32

It only worked with

fastboot [B]boot[/B] recovery.img

So maybe try both, one of them will work for a version
[SuperSU] shoey63:
Don't Samsung devices have a recovery partition? If so, then

fastboot flash recovery recovery.img

is the way to go. Then boot to recovery from the bootloader menu and flash.
[SuperSU] fmc000:
I don't think so. "fastboot boot" only expects a boot image and eventually a ramdisk. "fastboot flash" expects a partition (recovery in this case) and an image (recovery.img). Please document yourself before giving answers.
[SuperSU] Pkt_Lnt:
You are correct, mine was not.

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

---------- Post added at 08:41 AM ---------- Previous post was at 08:39 AM ----------

You can boot a recovery without installing it, however my command line was incorrect and [MENTION=6952047]grep_i[/MENTION] is correct.

Bottom of post #6.

http://xdaforums.com/showthread.php?t=2277112
[SuperSU] fmc000:
I know it, actually I use that syntax quite often as I have a device with a locked bootloader without known exploit: that's the only way I can boot a recovery on it.
[SuperSU] grep_i:
There could be various reasons someone does not want to install a custom recovery I'm not going into detail about it though.

So booting a custom recovery could be a way to get things done.

And what I described is the correct way to boot a custom recovery with the use of adb and fastboot.

Did this on Windows, Linux and one time on a Mac and it always worked.

Your code is correct but unnecessary for this case.
[SuperSU] ianmacd:
After copying su.img to a new file elsewhere on the file-system of my S2 Tab (T710) and S7 Edge (G935F), I can now say with absolutely certainty that the resize2fs on these Samsungs doesn't work for this operation.

Informing [MENTION=631273]Chainfire[/MENTION]. These devices will need some other fix to enlarge su.img to 96Mb.

Both devices give:

The filesystem is not need to resize.It is very close to size to resize.
[SuperSU] grep_i:
I guess it is not possible because the su. img is already at the most possible 32 mb as set before.

To change this you should probably remove the old su.img and create a new one with 96 mb size or else I do not see how to resize it.
[SuperSU] osm0sis:
Use my commands from within TWRP?
[SuperSU] egingell:
^This. TWRP's commands and binaries are independent from the ROM (ie it has its own).

Sent from: SGS5 - MM 6.0.1 / SGS4 - LP 5.0.1
[SuperSU] ianmacd:
I tried it on the S7 Edge and, unfortunately, I was right that it doesn't work. adb reboot-bootloader simply reboots the phone, i.e. back to the OS.

---------- Post added at 23:19 ---------- Previous post was at 23:01 ----------

I tried it on my tablet and, yes, TWRP correctly resized the image. Thanks.

I'm aware that TWRP has its own binaries, but the image resizing that SuperSU 2.76 natively attempts is performed, as far as I can tell, by /sbin/launch_daemonsu.sh.

Looking inside that file, resize2fs is called without a path, so whichever $PATH is in effect at the time is the one that is used. That presumably results in the ineffective invocation of /system/bin/resize2fs on these Samsung devices.

I don't have TWRP on my S7 Edge, so I'll have to either install it or look up how to create a flashable ZIP for FlashFire if I want to resize the image on that device as well.

Actually, now that I think about it, TWRP won't even work on the S7 Edge, because /data is encrypted.
[SuperSU] Pkt_Lnt:
no dash

adb reboot bootloader
[SuperSU] stang5litre:
Hey [MENTION=631273]Chainfire[/MENTION] is there anyway to make a flashable of the adb package you made for the s7e? Other wise can't build any roms :(> Been trying to do it myself but coming up short . Thanks for all your hard work!!
[SuperSU] ianmacd:
reboot-bootloader with a dash also exists as a command. :)
[SuperSU] grep_i:
Strange.

That is the right command.

Does that mean your phone has a different bootloader not accessible with the default Android Debug Bridge tools, I guess not because you said it would reboot the phone by using the command.

That is normal but it should boot to a bootloader menu.

When it shows that menu you should execute the fastboot command.

It's that I don't own a S7 myself my neighbor does but I will not see him until Friday because of different work schedules.

Friday I will borrow his phone and test it myself and report back.

One quick question do you have Exynos or Qualcomm processor ?
[SuperSU] egingell:
When I do 'adb reboot bootloader', I get Odin mode.

Sent from: SGS5 - MM 6.0.1 / SGS4 - LP 5.0.1
[SuperSU] tet-bundy:
that's because samsung replaced standard fastboot mode with odin mode. in other words there is no fastboot mode on samsung devices..

Gesendet von meinem ONE E1003 mit Tapatalk
[SuperSU] Artieza:
I really don't want to waste this theme by discussion about third-party app. But need to notice if app still can ask SuperSU for root, all further behavior is on Chainfire.

App2SD by Sam Lu doesn't have Link2SD functional. I told about Apps2SD by Vicky Bonick. I can't so simple check it. Just don't have free space to move all stuff back before linking by other program.
[SuperSU] ashyx:
Does [MENTION=631273]Chainfire[/MENTION] know about this. Have you got links, evidence?
[SuperSU] egingell:
People charge for root-required apps all the time. Just because SuperSU is included doesn't change anything. As long as they're not charging for just SuperSU and nothing else, they're fine.

Sent from: SGS5 - MM 6.0.1 / SGS4 - LP 5.0.1
[SuperSU] kostassfirakis:
Samsung tab s2 user (sm-t715) android 6.0.1 will there ever be system root option? I have a custom kernel which adds selinux support, but what ever I try to install to system is deleted after system reboot.. even if I flash with twrp
[SuperSU] osm0sis:
Fair enough! Should probably be posted as a FlashFire issue on that thread however, since the issue is more it not having a replacement resize2fs or not taking precedence over the system one. :good:
[SuperSU] ianmacd:
But this has nothing to do with FlashFire, I thought. /sbin/launch_daemonsu.sh is part of SuperSU and is run at boot time, I think. Or am I wrong about that?

I've just created a flashable ZIP for FlashFire and gave that a shot, but that gives resize2fs: command not found.

Oh well.

I suppose I could just enlarge su.img on my laptop and then copy it back into place from the SD card (via a FlashFire ZIP). I'm not sure whether that has any hidden dangers, though.
[SuperSU] scattey:
It didn't log even if the full logging was turned on. I am using v2.76 SuperSu. It didn't happen before as far as I know. It happened only once and all other commands of this app and other apps were logged.
[SuperSU] osm0sis:
I was thinking more FlashFire should be including anything TWRP does (especially if the SuperSU zip tries to use it), so it'd better be filed under a FlashFire bug, but I guess it could go either way?
[SuperSU] :
So, no one is getting a camera crash on Android N preview 4? I searched the thread, but no mention at all. Is Android N preview 4 unsupported?
[SuperSU] dechronic:
Wrong thread
[SuperSU] Ja_som:
No crash on my N5X, I have no issues with root...
[SuperSU] bpdamas:
First, I went back to July 5th when this was released and read up to the end. It looked like it was slightly discussed but I didn't see anything definitive or why. I have an HTC One M9 running stock rooted ROM, s-off, with unlocked bootloader, TWRP 3.0.2-0 installed, on version 3.41.651.4. When I try installing 2.76 I get a bootloop I can't get out of. I had to hold down the volume button to go into recovery and flash a stock boot.img to get it to boot. I tried different combinations of clearing cache, dalvik, etc. and nothing worked. I get a bootloop every time I try to flash 2.76.

2.65 works just fine and I was able to flash that without issue and get root. Just curious to why this is happening and if anyone wants any logs to help troubleshoot the issue, just let me know what you need. Maybe it's a known issue and I can't use 2.76 but I didn't see that anywhere either.
[SuperSU] ktmom:
I don't have an HTC. I have seen posts confirming M9 running on 2.76.

That said, I would start by saving the log from a supersu flash from a clean start, including a factory reset and fresh rom. Look at the log to see if it's installing in system or systemless then I would try forcing the opposite.

If you didn't do a factory reset that might be all you needed. A always, make sure to back up your phone before fussing ;)
[SuperSU] Ja_som:
Only FYI, flashed DP5 factory image on my N5X, rooted with CF Auto Root and then updated SuperSU app via Google Play and binaries via SuperSU app, everything works...

Thanks [MENTION=631273]Chainfire[/MENTION] :good:
[SuperSU] bpdamas:
I don't think I am going to factory reset my phone to install the newer version of supersu. Thanks for the suggestion, though. Maybe I haven't been keeping up on supersu, but I don't remember this ever being an issue.
[SuperSU] grep_i:
I came around the following tutorial when browsing the internet maybe this can help you get TWRP installed on your device and from there you can continue your other actions.

It works on your device SM-G935F

http://www.stechguide.com/install-twrp-recovery-and-root-galaxy-s7-edge/
[SuperSU] ianmacd:
Thanks, but installing TWRP isn't the issue. That's easy enough to do and I've had it on this phone before.

The problem with the G935F is that its /data partition is encrypted. TWRP doesn't understand this encryption, so you need to either wipe /data and reformat it unencrypted, or live without TWRP being able to access it.

I'm not prepared to wipe /data and run with it unencrypted, so I can't use TWRP to resize /data/su.img. The 32Mb image isn't causing me a problem at the moment, but I'd like to enlarge it to be prepared for things to come. I'm going on holiday tomorrow, however, so it's going to have to wait a while. The effort of fixing this is disproportionate to the gain.
[SuperSU] osm0sis:
[MENTION=631273]Chainfire[/MENTION] just added the missing `getprop` functionality to FlashFire so I'd say you should definitely report the broken/missing FlashFire resize2fs functionality there, since it really should be tackled both ways if possible; FlashFire adds resize2fs, and SuperSU zip adds fallbacks or proper usage of the Samsung /system/bin/resize2fs.
[SuperSU] ashyx:
Yes I know that [emoji13] , but what he posted seemed like something else which is why I asked for links and evidence.
[SuperSU] m.dam:
Apphider don't hide apps after update supersu to 2.76

After update to supersu to 2.76 this app

play.google.com/store/apps/details?id=com.thinkyeah.apphider&hl=it

in unable to hide applications. It says the app is hided but it's false.

Well, i thought this app is not functioning correctly with new supersu and installed this one:

play.google.com/store/apps/details?id=com.snsui.appHider&hl=it

but, again, the app is unable to hide apps.

So i reverted supersu to 2.46 and the hiding apps are doing their job again.

Any ideas ?

Telephone: Umi eMax

Android 4.4.4
[SuperSU] egingell:
Tell their devs to fix their apps so they use su properly.

Sent from: SGS5 - MM 6.0.1 / SGS4 - LP 5.0.1
[SuperSU] grep_i:
Maybe KitKat 4.4.4 is not supported by SuperSU v2.76 for lollipop and marshmallow
[SuperSU] egingell:
Unlikely. SuperSU has always been backward compatible for me. But I don't have a KitKat phone nor have I ever, so I can't back that claim up.

Sent from: SGS5 - MM 6.0.1 / SGS4 - LP 5.0.1
[SuperSU] c200amgpacket:
I have Note 5 N920CD I have installed 2.76 *and es file explorer *but i have no root access when I go to switch on the root option on es file explorer

I found a solution t*o copy from /su/bin 7* files to system/xbin

But when I do a rebo*ot the su says to ins*tall su binaries and *fails and then no su *root in device

Can you suggest any *solution?
[SuperSU] fmc000:
It's possibly the most answered question EVER in this thread.
[SuperSU] Craiq:
Hi [MENTION=631273]Chainfire[/MENTION]

as I understand for now, for having systemless root, I need a recovery that can access /data and /cache

Problem is, there is no recovery for s7 that has access to the encrypted /data, but I like to keep it.

So shouldn't it be possible to write the su.img to /data and make the /cache changes with my system rooted phone?

Than reflash /boot and /system with odin to stock. Next we need a new auto-root.tar.md5 that just modifies /boot.

So we have systemless root with encrypted s7 :D
[SuperSU] grep_i:
I came across this guide it also deals with encrypted data.

Maybe this will suffice for you for now.

Read carefully as it ain't easy and needs to be done precisely.

http://www.stechguide.com/install-twrp-recovery-and-root-galaxy-s7-edge/
[SuperSU] DallasCZ:
Hello,

I am using Alcatel IDOL 3 , which got MM update (6.0.1) and i want to modify the ROM, that it incudes the ROOT from begining.

can I use the command to froce systemless "echo SYSTEMLESS=true >> /data/.supersu" in this way in updater script?

I want to make a ROM that includes the superSU root, so i have to force systemless before I execute the supersu zip.

flashing supersu 2.74 without systemless command is not working.

many thanx for any advice.
[SuperSU] Denverfan9:
Used the flashfire method due to fire os 5.1.2 went to reinstall supersu from app store need to update binary message and supersu app wont update its self...did i loose root? If so what method to reroot? Originally used rootjunky supertool....

Thanks

*sry wrong thread
[SuperSU] dlb4all:
Hey people ... i have a problem here . my scripts wont start automaticaly at the boot

Now , im on latest supersu , latest CM13 snapshot , latest blue kernel and i have a nexus 5 and it was OK in the past but i dont know whats changed . oh and by the way the SU installs as systemless . and ive tried both su.d and init.d . no luck

any suggestions ?
[SuperSU] grep_i:
Need to be more specific maybe start by giving all your latest thingies version numbers, we don't know what is latest to you ?

If you are not aware if something changed between the time it was all working and the time it stopped working, it's gonna be pretty damn hard for us to know it for you.
[SuperSU] dlb4all:
Alright , Latest CM13 snapshot ( its a 3 month old rom) , supersu 2.76 stable , blue kernel v96

And i think thats pretty much it .

And about that other thing , everything was alright couple of weeks after flashing the new rom but things went south pretty quick . but hey , i already checked . its not a kernel thing , cause i changed it and no results

thanks for reply by the way
[SuperSU] grep_i:
In that case I would advise you to start over.
[SuperSU] neeraj.lambaa:
Super su for Motorola xt1068 marshmallows. Which of version is stable?

sent from moto g2014 with cm13
[SuperSU] ktmom:
http://xdaforums.com/showthread.php?p=67614969
[SuperSU] dlb4all:
Yeah thats exactly what im trying to avoid ... but mostly im looking to see whats causing this
[SuperSU] grep_i:
Guess that's unavoidable if you do not know how and when the problem exactly started and are not in a state that you can provide log to do some research on than it will pretty much be quicker to start over and this time keeping track of all the steps you are taking and report it directly when it goed miss again if it goes miss again.
[SuperSU] Pkt_Lnt:
A logcat will show you.
[SuperSU] dlb4all:
Hmmmm... a logcat during boot time ... that might work :good:
[SuperSU] Jaco1013:
thread created for my problem
[SuperSU] dlb4all:
What if i wanna force the installer to do a SYSTEM root instead of SYSTEMLESS ?

What should i change in the installer script ?
[SuperSU] jamaljmys:
hello guys

which release could root new build NPD90G for android N DP ?

thanks
[SuperSU] grep_i:
Reboot to recovery

In TWRP, go to "Advanced" then "Terminal"

Type these two commands:

echo SYSTEMLESS=true>>/data/.supersu
echo BINDSYSTEMXBIN=false>>/data/.supersu

Flash SuperSU, it should install as system

Or download the following zip from the attachment and flash it before flashing SuperSU

created by [MENTION=5490832]vaibhavpandeyvpz[/MENTION]
[SuperSU] grep_i:
Reboot to custom recovery (in my case TWRP)

In TWRP, go to "Advanced" then "Terminal"

Type the following two commands:

echo SYSTEMLESS=[COLOR="Red"]false[/COLOR]>>/data/.supersu
echo BINDSYSTEMXBIN=[COLOR="red"]true[/COLOR]>>/data/.supersu

Flash SuperSU as usual and it should install as systemmode

Or download the following zip from the attachment and flash it before flashing SuperSU

created by [MENTION=5490832]vaibhavpandeyvpz[/MENTION]
[SuperSU] dlb4all:
Lifesaver !!! thanks bro :good::good:
[SuperSU] tvisforme:
What are the advantages of system vs systemless? I am currently using 2.76 systemless, my understanding is that systemless was instituted to adapt to the increased security requirements for Marshmallow. Since the option now exists to do either, is systemless root better, equal to or less desirable than system?
[SuperSU] Pkt_Lnt:
The developer site called XDA has your answer.

http://www.xda-developers.com/chainfire-releases-root-for-android-6-0-without-modifying-system/
[SuperSU] ianmacd:
You don't need to have a custom recovery to enjoy systemless root. Just install root on your S7 using CF Auto Root.
[SuperSU] tvisforme:
Hi, thanks, I did read that eight months ago. I was actually hoping to get some input as to which approach is more desirable after two-thirds of a year's worth of tweaks and refinements.
[SuperSU] nicolap8:
Your (double) response seems to be the opposite of what the user want!

But he thanked you, so maybe he wanted the opposite. :D

I note that continue to be an enormous confusion on "system/systemless" SuperSU installation. Time (for someone) to write a good article.