yashsingh1/xdaforums huggingface dataset:
[SuperSU] mtw4991:
Thanks, didn't quite get the /system part when reading hence my question. Got stock system on N7 with 2.61 system less root. Running Ubermallow on N6P, so the answer would be no, can't do it.
[SuperSU] quickdraw86:
Finally, a fellow FX supporter! Kudos on good taste.
[SuperSU] adrman:
+2
[SuperSU] mobileman88:
EDITED
[SuperSU] tsadev:
Let me rephrase that: it should work with the 2.61 beta, this post should give a better understanding of what I mean.

If 2.52 (or any other version) is installed then you should flash a stock system.img to remove all traces of it, uninstall any updates (/data/app/eu.chainfire.supersu-* I believe) and Pro if you have it, then continue with installing stock boot.img > custom kernel > supersu 2.61.

Here is the quote I was referring to in my last post:
[SuperSU] Cares:
Deleting Spotify fixed it. My Spotify generally worked fine but would sometimes crash. Either way I'll leave it uninstalled for now. Thanks so much for your diagnosis.

Sent from my Nexus 6P
[SuperSU] tsadev:
Not a problem, glad I could help!
[SuperSU] maximumentropy:
T-Mobile WiFi Calling is working for me on Nexus 6 with 6.0.1 (MMB29K) and systemless v2.61
[SuperSU] USBhost:
Wait WiFi calling won't work with

System root?
[SuperSU] backslashV:
waiting for new image files for 6 and 6p

the old boot.img is causing severe battery drains on nexus 6p and also camera does not load. on nexus 6 the battery percentage shows an incorrect value. please update them asap.
[SuperSU] maximumentropy:
Nobody said anything of the sort.
[SuperSU] USBhost:
OK good I almost lost my mind
[SuperSU] tsadev:
2.60+ has an automated boot.img patcher, you no longer need manual creation of boot images.

Flash stock boot.img + system.img

Uninstall Pro if you have it

Install any custom kernel you may be using

Install SuperSU 2.61

Reinstall Pro if you had it

Though if you are having battery issues I would skip the custom kernel and see if you still have issues.
[SuperSU] backslashV:
Thanks. Have you tried that yourself on nexus 6p?
[SuperSU] 1122qqww:
Thank you very much for your effort.
[SuperSU] tsadev:
I don't own one, but I have been reading through this thread since about page 300 so I'd like to think I know what I'm doing ;)

That being said the procedure I gave is collected from parts of this thread including Chainfire's own posts, and this post from Chainfire on another one of his threads; it has worked for multiple Nexus users but I'm sure someone with the 6P could pipe up and tell you specifically whether it works with your device or not.
[SuperSU] backslashV:
I just looked at 2.61 and it is the systemless one. unfortunately some of my apps dont work with systemless root (secure settings being one of them)
[SuperSU] white7561:
[MENTION=631273]Chainfire[/MENTION] hey. So im using like custom samsung rom that modified. So the root is in there. (Supersu 2.49) and now if i want to use 2.52 how can i do that? Cuz the orig rom that modded already rooted itself? And then if i use systemless root. That means that if i change my kernel. It will lost? So i must flash again? Thx . using note 4 5.1.1
[SuperSU] backslashV:
thank you. does this alter the system partition?
[SuperSU] Ingenium13:
Yes

Sent from my Nexus 6P
[SuperSU] backslashV:
Thanks. How did you come up with this code? Where did you learn that?
[SuperSU] GloriousGlory:
Anyone losing root after every reboot with 2.61?
[SuperSU] mobileman88:
Do a systemless root with 2.61 and stock boot image. No more issues
[SuperSU] ashyx:
Not everyone just the noobs or the impatients.

For anyone that has been on the development side of things we share your pain and personally think you're doing a stellar job maintaining your patience in even replying to half of the senseless posts I see here.

Keep up the good work :thumbup::thumbup::thumbup:
[SuperSU] :
As a noob... Who has had to learn a lot, for my own knowledge sake, and done a lot of research, i have to thank you [MENTION=631273]Chainfire[/MENTION] for your hard work. Going through other threads like Xposed and layers... What would they be without their root? ? thanks!
[SuperSU] kontini:
Root Explorer works good. He was talking about the root explorer switch inside ES file explorer.

You are doing a great work with managing boot images and system-less root but we need to properly manage files in /system partition. It seems to be more a problem of partition size. Forget OTA just to answer me, would partition resizing solve the problem?
[SuperSU] Ingenium13:
That would possibly break applying factory images as well. At the very least you'd have to resize the filesystem after each update.

But I fail to see how this question belongs in the SuperSU thread.

Sent from my Nexus 6P
[SuperSU] kontini:
If I rooted my phone and I can't manage my files I think I'm not having full root privileges

And I fail to understand how my question was answered by you. Thanks Anway
[SuperSU] jc monkeyballs:
Well it stops working for me with 2.61 and works again if I flash stock boot.img. there's a thread about it on the Nexus 6P subReddit so I'm not completely alone.

Seems it works for some people though so it's tough to figure out.
[SuperSU] Phrodini:
Is there a way to get rid of do not install in twrp after flashing 2.6.1.?
[SuperSU] Ja_som:
No, we need to wait for the TWRP update.
[SuperSU] a g bell:
I am correct with systemless root it will mean no way of deleting all the crap/apps that Google pre install on a stock rom?
[SuperSU] shoey63:
Root is root. Systemless or otherwise. Delete whatever you like ;)
[SuperSU] smitharro:
You scared me off! I'm not some kind of dumb ass noob. I'll not be posting here anymore. I'm sorry but I don't feel comfortable in this thread.

Written with my XT1068 using Tapatalk on CM13
[SuperSU] sunnytexas:
Chainfire - Using your Seamless Root in non system area in MM 6.0 is seen by some Bank Institution Apps, in which triggers banking apps to block use of banking functions such as logging in to the bank institution for banking purposes. The apps usually will say " Root is not permitted with app"! I wasn't sure if you knew this issue with MM 6.0 and SuperSU seamless root method?
[SuperSU] mpgrimes:
You're complaining about a patched boot image when you unlock your boot loader, flash custom recovery, rom and kernel?

Flash stock, relock bootloader and go home....
[SuperSU] smitharro:
And this is why... Disrespectful.

I wasn't complaining, just ignorant. Anyway I'm off,. I won't be complaining anymore.

Written with my XT1068 using Tapatalk on CM13
[SuperSU] belek1979:
How to clean up 2.52 root? I want to update to 6.0.1 and then make systemless 2.61 root, but I've read that I need to clean previous versions of root...
[SuperSU] Srandista:
You have to flash system.img and boot.img, then install 2.61 through recovery.
[SuperSU] nEUTRon666:
Came from a 6.0 Build with a normal root method. Flashed the 6.01 update, which also replaces boot and system image, flashed 2.61 and everything worked ouf of the box, systemless root, yeah :)

Another question:

SuperSU makes a backup of the original boot image, then patches it. If i now flash a custom kernel (after systemless root) and some day an OTA arrives and i unroot using supersu (which should replace the original boot image) this still should work, or ? I mean replacing the original boot image over the custom one...
[SuperSU] Chainfire:
As long as you haven't replaced anything else, yes, the original boot image will be restored.
[SuperSU] Chainfire:
v2.62 posted

v2.62 posted in the WIP thread. Got to go, no time to write more info right now. Let me know how it works out!
[SuperSU] bobby janow:
Flashed it over 2.61 and it's working fine. However, all my root apps were working before too, so someone else will have to test those.
[SuperSU] foxfire450:
It has fixed the issue with Secure Settings weirdness for me.
[SuperSU] Midomad:
Flahed the 2.62 version on superSu app info still showing 2.61!
[SuperSU] Captain_Throwback:
This one works perfectly on my One A9. Thanks for your hard work, Chainfire!
[SuperSU] eradicator006:
2.62 works great on my g3 running cm13. The custom_kernel_patch.sh addition is perfect for automatically bumping the kernel.

Create a /data/custom_kernel_patch.sh with the following contents and it will bump the kernel for the g3:

#!/sbin/sh
printf '\x41\xA9\xE4\x67\x74\x4D\x1D\x1B\xA4\x29\xF2\xEC\xEA\x65\x52\x79' >> $1

BTW, there is a mistake in the update-binary script for the custom_kernel_patch.sh part. The if statement looks for /data/custom_kernel_patch.sh then calls 'sh /data/custom_boot_image_patch.sh'. The filenames should be the same, shouldn't they? I fixed that on my local copy.
[SuperSU] belek1979:
Stock system.img and stock boot.img, then 2.61/2.62 from TWRP. What will happen with my encryption?

I had (on my nexus 6) 2.46 with 5.1.1. Then I made a dirty update to 6.0.0 and flashed 2.56 systemless. There was no root. So I installed 2.52. Everything was OK. Now I uninstalled 2.52 (full unroot from the app). Reboot and... there is still root! Xposed, gravitybox, doubletap, es file explorer all have root! Hoe it is possible?
[SuperSU] corkiejp:
On Nexus 9 Wifi, Just flashed it over 2.61.

ES File Explorer's - Root explore - now works, was able to create and delete a text file in system.

Flashing it removed my updated ElementalX kernel so had to reflash it as well.

Also your zip installer, still says "Modified Boot Required" or something along that lines.

Thanks for all your hard work.

John
[SuperSU] Ja_som:
Not for me :(

I still can grant access, but after I restart app, it is disabled again...

But 2.62 works same as 2.61 for me, good :)

Thanks Chainfire ;)
[SuperSU] ilfrick:
[MENTION=631273]Chainfire[/MENTION] Flashing 2.62 on I9505 with JDC Team AOSP 6.0, over the Beta 2.52 results in a bootloop.

Is there anything I can provide you with to help troubleshooting and development?

Had to reflash rom, gapps and so on to fix it. [MENTION=3545504]smeroni68[/MENTION] thought I'd let you know as well.

Thanks!
[SuperSU] The Gingerbread Man:
I appreciate this might not be right thread for this question how ever I'm after a little support.

I'm using 2.61 on nexus 6p 6.0.1 chroma 7/12/15. I have used the full unroot option in SuperSU becasue I was trying to use this app which detected my root. So I used the unroot option within SuperSU and the app still thinks I'm rooted. Even though I'm clearly not. Su in terminal returns command not found.

I was hoping someone might have an idea why this is happening?
[SuperSU] Ch3vr0n:
You didn't follow instructions, you need to reflash /system and /boot if you had 2.52 or earlier. AOSP/CM13 isn't guaranteed to work yet. It's not chainfire's fault you didn't follow instructions.

Verstuurd vanaf mijn Nexus 5 met Tapatalk
[SuperSU] The Gingerbread Man:
Was that in response to my question? A quote before hand would be helpful to know who this is meant for. And if it is meant for me I'm not trying to blame anyone, I was just trying to ask for help.
[SuperSU] belek1979:
Is it true that if I have encrypted nexus 6, and update it to stock system and boot and flash 2.62, then I will be still encrypted?
[SuperSU] bobby janow:
How can the app still think you're rooted even when using 2.61? You mean it's reading the sdcard and seeing something? Would dirty flashing the rom do anything? This is the problem I have with roms that pre-install root for you. Does Chroma do that? If that's the case you might want to see if there is a version without root.
[SuperSU] Ketawa:
I think it was for #3606, where the poster installed SuperSU 2.61 over 2.52 without flashing stock system or boot.
[SuperSU] Chahk:
Flashed stock 6.0.1 boot and system on Nexus 6, flashed 2.62 in TWRP. When I went to reboot, TWRP did not prompt to install SuperSU. :good:
[SuperSU] Neverendingxsin:
Flashed right over 2.61 systemless on my 6P and all is well :)
[SuperSU] ashyx:
Holy cheeses, every time I come back to this thread I leave doing this >>:banghead::banghead::banghead:

People (aka noobs) currently there are 362 pages to this thread, cant at least one of you attempt to use the thread search function at the top of the page instead of asking the same questions a million times over? :banghead::banghead::banghead:
[SuperSU] belek1979:
do you wipe cache/dalvik after flashing SuperSU 2.62? Is it recommended? Maybe it mess with SuperSU???
[SuperSU] haseoxth:
Thanks a lot sir [MENTION=631273]Chainfire[/MENTION], 2.62 works flawlessly on my phone all my apps just work like the way they had before.:good:
[SuperSU] SamuriHL:
[MENTION=631273]Chainfire[/MENTION] just reporting back that 2.6.2 has the same problem on the Samsung 5.1 kernels that I experienced before. Basically I tried to flash 2.6.2 on top of 2.6.1 and it noticed that the boot img was already patched and went to restore the stock one and failed. At that point it aborted. I can just flash the stock boot img and the everything's fine.
[SuperSU] Nikos2k:
Try 2.62

But if for some reason you need the system-based root, just flash system.img and then install 2.52

(without changing the boot.img which is already modified by 2.61)
[SuperSU] IronTechmonkey:
Pardon a bit more OT but, expanding on that notion: Searching is both a rule and something each person should do out of self interest as well as community interest. The answers found by doing good searches may be more complete than the suggestions, if any, shared in response to un-researched "How do I "X"? posts. One particular challenge for less experienced members is that SuperSU dev is so dynamic right now (seriously, it is like watching an action movie) that, to keep up on it one really needs to keep up with 3 or more related threads. No excuse for not searching - just more exiting reading containing some great tech-fu.
[SuperSU] Smultie:
Then I'm afraid something went wrong. It should show 2.62
[SuperSU] Midomad:
Yes i know,

Happened to me with 2.61 and 2.62,

Maybe cause i'm using a custom kernel

When i install superSu apk it show the new version.
[SuperSU] H4X0R46:
Just chiming in here, I had 2.61 installed with elementalx kernel, worked fine, I installed 2.62 and then elemntalx kernel and it didn't boot, so I flashed the stock boot.img from a stock image, installed supersu 2.62, and then elementalx and it worked like a charm! This systemless root thing is confusing sometimes, but like everything else, we get used to it ;) Working great! Great work Chainfire! :D

EDIT: I should add that my device is a Nexus 6!
[SuperSU] bzowk:
Hey Guys -

I'm having a big issue with SD cards on my A9 (Marshmallow). It's been a hot topic in the HTC One A9 forums and it was suggested I post here about it. My A9 is currently rooted, s-off, and flashed with 2.62.

When inserting a brand new SD card and choosing to format internally, I get a popup towards the end of the format saying its a slow card (when it isn't) and once format complete it says the card is corrupted. I know its not the card as I've tried 3 different brand new ones which were UHS-1.

Initially, I rooted by copying over a different boot.img, copying an su.img to the data part, flashing TWRP, wiping data, then installing SuperSU apk. Noticed issue immediately after this. Proceeded to go s-off as was told that may fix so installed and paid for Sunshine. This caused me to wipe again so did so but still didn't fix issue. Finally, today I downloaded the 2.62 zip, then flashed via TWRP; but still same issue.

There is a thread for it in the A9 forum plus mentioned in A9's primary root post.

If you have any suggestions or things you think I should try in meantime, please let me know.

Thanks!
[SuperSU] chazall1:
No issues when updating when I follow this order.

I flashed the stock boot.img or boot.img from your ROM.

Reboot

Flash SuperSU

Flash Kernel

Boot up and all is great.
[SuperSU] sidamos77:
Nexus 5, 6.0.1, 2.62.

Working: Autorun Manager, BetterBatteryStats, BusyBox Free, ES File Explorer, Kernel Adiutor, LeanDroid, PNF Root, Titanium Backup.

Not working: Wakelock Detector

Thanks!
[SuperSU] H4X0R46:
That's what I had to eventually do, it failed when I tried to install the new version on top of 2.61 and elementalx, but this is what helped! :P
[SuperSU] Nbay64:
[MENTION=631273]Chainfire[/MENTION] v2.62 is working on Samsung Galaxy Tab S2. Everything is working as it should be, however there is one small problem. For some reason, Google Play Movies won't play anything. It's only Google Play Movies that won't work, everything else is fine. Any idea what the problem could be?
[SuperSU] lordmago:
Hi [MENTION=1162986]Captain_Throwback[/MENTION], for what I can read, you were successfully able to root your M8 with SuperSU 2.61.

I searched the thread but I couldn't understand how, I missed some steps... Can you please tell me which stock boot &/or system you flashed before flashing SuperSu 2.61? Where did you find it/them (maybe some GPE thread)?

I would like to flash SkyDragon Sense rom http://xdaforums.com/htc-one-m8/development/rom-sd-4-0-sense7-port-sdkernel-t3062378, that installs automatically SuperSu 2.52 ...

I have an M8 WWE with super CID.

Can you please give me some hints?

THanks in advance!
[SuperSU] belek1979:
Nexus 6 (unlocked, unencrypted), 6.0.1 (dirty update to stock system and boot images), 2.62 (via TWRP, wipe cache/dalvik).

Working (still unencrypted): Xposed, ES File Explorer, Greenify, GravityBox, DoubleTap2wake.

Thank you Chainfire
[SuperSU] rahaar:
Just like additional info this Issue don't happen without root,

without root formating sdcard as internal storage works good....
[SuperSU] Captain_Throwback:
I just flashed the ROMs and then flashed SuperSU. I haven't tried the ROM you mentioned. You'll have to talk to your ROM dev about that.
[SuperSU] corkiejp:
Tip: If your looking just for info/post from chainfire, try clicking on his name and view his forum posts.
[SuperSU] springer.music:
[MENTION=631273]Chainfire[/MENTION]

Does this mean that if I'm running unencrypted and rooted with 2.62 and for whatever reason I need to unroot, the phone will then reboot using a completely stock boot.img with "forceencrypt" enabled?

If so, would you be able to add some sort of warning when you select "full unroot"? Or even better a way to change "forceencrypt" to "encryptable" in the stock boot.img that gets refreshed?

Thank you
[SuperSU] Cares:
What happens if i flashed v2.62 and didn't do "echo FSTABSYSTEMRW=true>>/data/.supersu" on my Nexus 6P? Can I go back and do it still? I'm assuming I should be using something like Terminal Emulator to type this?
[SuperSU] tsadev:
You should do some reading. I believe you will need to reflash 2.62 in order for it to work though.

Send an email to the developers of that app and let them know they need to update their su detection methods.

As [MENTION=1162986]Captain_Throwback[/MENTION] said, you should take it up with the ROM developers; though next time please use the private messaging functions instead of hijacking a thread.

Because I'm a nice person though (sometimes ;)), I would imagine you can flash that ROM, uninstall 2.52 via SuperSu unroot or other methods, then install 2.62.

FOR NOOBS IN THIS THREAD: As of 2.60+, SuperSu comes with a built-in boot.img patcher, you no longer need to look/ask/whine for a boot.img for your device.
[SuperSU] xenyz:
Did you actually try installing BusyBox with the app?

I'm running Marshmallow 6.0.1 on a Nexus 4 (unofficial 'stock' ROM) and the system/xbin overlay prevents BusyBox (stericson) installer from working.

Workaround for me: umount /system/xbin, install BusyBox, reboot.
[SuperSU] dmantilal:
With my Nexus 9, running Android 6.0.1 and SuperSU 2.62, BusyBox Pro (stericson) installed fine.
[SuperSU] mistermojorizin:
what's the preferred way of updating a 6.0.1 rom with SuSU 2.61 beta installed, to SuSU 2.62 beta?
[SuperSU] mobileman88:
Just flash it in TWRP
[SuperSU] egingell:
You know that whole first post that says how to install it? That way.

(Edit: Not directly, but click links and read the last couple pages of this thread.)

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] shag_on_e:
Thank you Chainfire, you are a beast. I don't know how you wrap your head around all these changes, but man I appreciate it. I must say Android is becoming a pain in the donkey to su.
[SuperSU] :
Even with these instructions I still can't get my Nexus 6 to boot. I've tried it with r35 and r36 of franco kernel. I'm unencrypted as well.
[SuperSU] mobileman88:
Have you tried standard boot.img of it works?
[SuperSU] :
I foolishly flashed the 2.52 beta, as opposed to 2.6.2. Thank you so much for a quick response.
[SuperSU] mobileman88:
Glad to hear it's working now
[SuperSU] JaCh0o:
Possible to correct this in next version?

Wysłane z mojego Oppo Find 7 przy użyciu Taptalka
[SuperSU] Frank Westlake:
JaCh0o, you need to do some more investigating to discover what is deleting the binary (there are several, I don't know which). It could be one of those applications that you ran after updating the binary.

I assume that one of the applications is telling you that it does not have root access. It is likely that application or the one you ran preceding it that is deleting the binary. Try running each application twice sequentially to see if one has access the first run but not the second.

Frank
[SuperSU] JaCh0o:
Oppo Find 7 KitKat vs SuperSU

AS far as i know, you're not right (im openign adaway, titanium and helium) and thats all. after this reenter to supersu app and it needs again to update binaries. Propably something in the background removes su, don't know what... even don't know how to check it. Thought it will be written in logcat. These apps wich i open are regular root depended apps, moreover sometimes while working root depended app (adaway) phone looses root privillage = i enter app AdAway (see that SuperSU gave permission) press check updates, works properly, see "there is update availible" press proceed or smoething like this see that is merging some host sites and then stucks, app works but don't go further, i close app and reenter = need root permission to work. Mainly it updates succesfuly, but sometimes not.
[SuperSU] Frank Westlake:
AdAway gets root access, then later while it's still working it loses root access. Does that happen with other applications -- they get root access then lose it while they are still working -- or does it happen only with AdAway?

Frank
[SuperSU] JaCh0o:
Yes, it happens in any root needling apps. Maybe you misunderstood me, sometimes I run adaway and it's successfully done whatever it needs. Sometimes I enter (with root permission) and immediately I see dialog box about that it need root permission, and sometimes in half of work it loses root permission. Same happens to any other apps.

Wysłane z mojego Oppo Find 7 przy użyciu Taptalka
[SuperSU] Frank Westlake:
One thing that does is alter the environment. Here's a possibility:

'sh' alters the environment it's given.

'su' alters some of what 'sh' set.

'sh' now root, alters some but not all of what 'su' altered.

I already deleted my test but I recall that HOME and LD_LIBRARY_PATH were changed, among others. As an example, my LD_LIBRARY_PATH started at "a:b:c", which 'su' changed to "a:b", and that is how the final 'sh' kept it. But 'su' changes it regardless so this is probably nothing more than just something to write about.

Frank

---------- Post added at 12:11 PM ---------- Previous post was at 12:01 PM ----------

I'm getting closer. Your root access goes off and on and I want to verify one point. When it goes off, does it come back later without updating the su-binaries, or does it only come back after updating the su-binaries?

Frank
[SuperSU] JaCh0o:
It's get back only when I enter SuperSU app and update binaries by normal method. Moreover sometimes last thing I do is update binaries and in the morning I got no root privileges, and SuperSU app isn't informed/concious about that (doesn't show hash tag = SuperSU notification), when I enter SuperSU hash tag appears.

Wysłane z mojego Oppo Find 7 przy użyciu Taptalka