yashsingh1/xdaforums huggingface dataset:
[SuperSU] Ozgurce:
Here is the recovery log. As I read it I think there is space error on the last lines.
[SuperSU] egingell:
The person you quoted was attempting to root via the Play Store download not from recovery.

As for you, the moment you reflashed the boot image ("new sboot"?), you lost root.

Sent from: SGS5 - LP 5.1.1 / SGS4 - LP 5.0.1
[SuperSU] Battlehero:
Just so we are clear sboot.bin = Bootloader not Boot.img (Kernel)
[SuperSU] Ozgurce:
sboot is not boot image. Its bootloader for samsung phones.
[SuperSU] tet-bundy:
I think i didn't claim su works only to switch to root, but simply root is the only user of interest in this case.

But anyway su does not mean "switch user" but means "substitute user identity"... Which doesn't differ much. But in this case, i know for sure the closest suggestion is simply wrong. Or at least not the original meaning.

Gesendet von meinem SM-G800F mit Tapatalk
[SuperSU] fmc000:
Well, I started working with Unix systems about 25 years ago and unless something has changed very recently (I mean last night) "su" really is the acronym of "switch user". We could actually start talking about "real user ID" and "effective user ID" and how the privileges are managed in Unix systems but that will be quite off topic and disrespectful for the OP, so I'll stop here.
[SuperSU] tet-bundy:
In this case u are likely to know it better I'd say [emoji16]

Thx for clarification.

Gesendet von meinem SM-G800F mit Tapatalk
[SuperSU] _Arne_:
Battery indicator wrong

Hey Dude,

sorry to correct you: su really is the acronym of "Super User"

The proof is simple: Go the Unix Heritage Archives, look in the early Bell Labs Editions and you will see, that /bin/su was only able to give you super user permissions..

And guess what Dennis and Ken wrote in the first line: /* su -- become super-user */

A few years later the BSD world startet to call it "substitute user".

And no, su was no Multics command, so the search ends here... 40++ years ago at Bell Labs.

And now to the topic of this thread:

After installing the latest BETA SuperSU on my Nexus 6 running MMB29Q the battery indicator reads 4.xxx% and the battery status is fixed on "charging".

I'm pretty sure that the reason for this comes with BETA-SuperSU-v2.67-20160121175247.zip.

Is there anything I can do other than waiting for the next Beta-SuperSU release?

Thanks in advance,

.//. Arne
[SuperSU] jwds1978:
This all is getting somewhat off-topic, but depending what context to which you're referring, 'su' as in the command is 'substitute user'... Allowing you to assume the identity of another user, not to switch user accounts.

With that said, not wanting to derail things further nor get a hammer upside the head from a mod, I'll leave my opinion on it at that and not make any further replies regarding it specifically. We should really get back on topic though. ☺
[SuperSU] Mao04:
This usually happens when you flash one of the newer versions of superSU over a kernel that was previously modified like we had to when systemless first came out. Reflash stock kernel and reflash 2.67. 2.67 automatically applies the needed modifications to the kernel now.

Search back through the thread for more info on this.
[SuperSU] ithehappy:
Hi, I am using SuperSU 2.65, but whenever I flash a kernel, then the SuperSU binary gets uninstalled or something and I have to flash 2.65 from recovery again, not really a big deal, but kinda annoying. So I googled a bit and found that some people recommend 2.52, now I don't understand. Should I use this Beta 2.67 or 2.52? If its the latter then could someone redirect me to its download link? I searched on Google but not sure about the results.
[SuperSU] dragos281993:
The SuperSU binary is now installed on the "data" partition, hence the name "systemles root". The binary gets uninstall only if you wipe the data partition. Install the latest SuperSU 2.67 and make sure you flash stuff in the right order too.
[SuperSU] OMJ:
when SuperSU is flashed, it modifies the boot.img...if u flash a custom kernel after, u must flash SuperSU again. 2.67 is the latest but does not work on all devices (like mine, M9), if 2.67 causes a bootloop, flash 2.65.
[SuperSU] alex00006:
hi

guys

I'm use su 2.67 on note5 and stock rom 6.0.1

but not work for rom ..

i waiting for new version su for Android 6.0.1

tnx a lot chinfire
[SuperSU] magnamentis:
nothing OT IMO, i have rarely had a better read recently and learned a lot (many details) that i normal user, even though experienced, usually never gets aware of and since all that was related to root and SU and the likes it was not only not OT but really useful to get some better insight.

thanks guys
[SuperSU] Gs2dci:
moto e lte with cm13 working perfectly.

Thanks
[SuperSU] ithehappy:
Thanks. So there's no core difference between 2.65 and 2.67 then, okay. I was only going to flash the latest Beta if I didn't have to flash the SuperSU again after flashing a kernel. So if that's not the case then I better stick with 2.65. I don't really know what systemless root means but I like the older method where I didn't have to flash super su again after a kernel flash. So could you tell me where that can be achievable with older 2.52?
[SuperSU] OMJ:
depends on your OS version...Marshmallow requires a newer systemless SuperSU v2.50+

if you are still on lollipop or older, I would use v2.46

technically v2.65 should detect if you are on older than M, & install into /system w/o modifying boot.img per chainfires notes:

more info here: http://xdaforums.com/showpost.php?p=64161125&postcount=3
[SuperSU] Pkt_Lnt:
Changelogs show the differences between versions.

http://xdaforums.com/showpost.php?p=64916199&postcount=3

http://xdaforums.com/showpost.php?p=23427824&postcount=3
[SuperSU] egingell:
2.65 works fine on Lollipop. The ZIP installed systemless on my SGS5 (5.1) and system on my SGS4 (5.0) - both without any intervention from me.

Sent from: SGS5 - LP 5.1.1 / SGS4 - LP 5.0.1
[SuperSU] ithehappy:
Yes, I am on Lollipop, 5.1.1. I won't have MM in next couple of months at least. Could you please tell me whether this is the right 2.46 version or not? https://download.chainfire.eu/696/SuperSU/
[SuperSU] OMJ:
yep...that's the one I was using when on L
[SuperSU] farid993:
Hi [MENTION=631273]Chainfire[/MENTION]

Official 6.0.1 is out for S6. Could you take a look at it please? Thanks
[SuperSU] Gs2dci:
I use this for now and going well

https://mega.nz/#!6tdxzYLI!bANbUoO2ztLrM_LhddHyu6IeZK7tK8cdj0tuMKIbEBE
[SuperSU] ithehappy:
Hey I just wanted to mention that after flashing this 2.46 version the phone went to bootloop, so went back to 2.65.
[SuperSU] fmc000:
I'm trying to encrypt a MM 6.0.1 (slimsaber - encryption is known to work) installation running SuperSU 2.67 systemless and it continues failing showing just the bootanimation and the encryption process never starts (data is intact after forcing a poweroff).

I tried disabling SuperSU before starting, both unticking the checkbox and by pkill-ing the daemonsu process - nothing worked.

Could it be that SuperSU is interfering with the encryption process? Should I try by reflashing the ROM, trying the encryption process and after that re-root the phone?

Edit: Yes, SuperSU is the "culprit". I had to flash the ROM, encrypt and then reflash again SuperSU in TWRP to encrypt my phone. It worked flawlessly.
[SuperSU] Ohmster:
Dumb Question - Root MXPE

Excuse me, but I want to help someone root their new Moto X Pure Edition and am failing at the process. I am showing her the method I used for SuperSU 2.56 on my Moto X Pure and that means adb and fastboot boot.img, su.img, and superSU.2XX.

Of course it is failing, we are losing WiF, but peeking into these zips, they now appear to do *everything* and maybe do not need to flash boot.img and su.img anymore. If I am doing that and it is no longer necessary, then I am screwing this up for her.

What is the correct way to root an Moto X Pure Edition XT1575 US? Just flash the latest SuperSU in TWRP and that is all? Reboot to joy and a rooted phone?

This sounds dumb but I am missing something here. Can you help me out please? Thnx. :)

EDIT:

The roots I am looking at are here, in post #3, and I don't know what "WIP" means:

http://xdaforums.com/apps...4/post64161125

Thanks for your help.
[SuperSU] Digital Cha0s:
pretty much just flash the latest 2.67 in twrp and root is yours and "WIP" is work in progress
[SuperSU] mrdunlop:
Use the 2.65 SU, the build you are trying to use is to old
[SuperSU] Ohmster:
Yeah I will try again. When I did it last night, we lost WiFi, but, I am still doing this "old school" by not only flashing SuperSU, but boot.img, and su.img as well. Not sure when that stuff got taken out, I did my own phone in like, October. But Chainfire is on a roll! Not simply flash one zip in TWRP, that sure is nice. Can't wait to try it out. Thanks.
[SuperSU] Pkt_Lnt:
The changelogs will help you here in what changed and when.

http://xdaforums.com/showpost.php?p=64916199&postcount=3

http://xdaforums.com/showpost.php?p=23427824&postcount=3
[SuperSU] Ohmster:
Ohhh, yeah, it has all been changed since October. Man, Chainfire is like some sort of programming legend or something. All this in 4-5 months!

Hey, to OTA with this root, how do you do it? Previously one had to reflash boot.img, take the OTA, and then root again. This is do different now, not even flashing boot.img. So how does one take an OTA update? :confused:

Anybody?
[SuperSU] corkiejp:
As seen by your signature you have modified your system with xposed, so OTA's will fail.

Otherwise I was going to suggest you try Chainfire's FlashFire app and see if it will work with your device.
[SuperSU] Ohmster:
Oh man, really? Xposed will tank any OTA update? Ack. So then I would have to backup everything with Titanium Backup, restore clean system minus root and Xposed from TWRP, then I can take OTA and restore TiBu stuff?

Thank you for the FlashFire link, this looks good but I do not have time now to read it all, bookmarked for safe keeping. Good looking out! :good:

EDIT:

BTW, flashed SuperSU v 2.65 in TWRP with NO problemo! I was doing it wrong because I was using adb and fastboot to flash boot.img and su.img like we had to do back in October. Now it is all so easy! You guys rock man, you all helped me out, with a purpose, next day air! Thank you all very much! :)

EDIT 2:

Dude, this FlashFire app is a bit daunting w/out instructions, but I see the relevant part right here:

- For block-level OTAs, flash a stock system partition or restore a (raw!) system (and vendor) backup before applying the OTA. After the OTA action, create a (raw!) backup of system (and vendor). The latter will be restorable to apply the next OTA.

- On systemless SuperSU roots, if you have not modified /system, FlashFire can often install the OTA update directly, and EverRoot after. Let your device download the update, but don't install it - instead, just open FlashFire, it should detect the OTA. (Tested on several Nexus devices)

Now I do not have systemless root because I did this with v 2.56 back in October and had to manually flash this stuff with adb and fastboot. So I do have su in my /system/xbin. Still, this is good stuff. Hope someone starts to make and publish some guides or tutorials for this app. Thanks!
[SuperSU] Ch3vr0n:
With a nexus device it couldn't be much easier. Flash stock system and boot and su in /system/xbin will be gone. Flash SuperSU beta and you're systemless.

Now if you then install xposed again you'll have modified system and void your ota's

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] su35:
Hi osm0sis

Does it work if I don't flash custom recovery and just boot to TWRP from adb? What does the systemless mean? Sorry, I am a new comer.

Do you know which version of SuperSU work for Moto g 2015 (XT1540 android 6.0)
[SuperSU] Ohmster:
I need Xposed though. Since there are no custom roms of merit for the Moto X Pure, I won't be able to mod or adblock w/out Xposed. So, that is something I need and really, with it, I don't much need a custom rom. If I had a custom rom like CM12, I might not need Xposed but I do like it. AdAway, Greenify, Gravity Box, APM+, all good stuff. So, I think I need to keep a clean TWRP backup for any upcoming OTAs, then backup everything with TiBu, update, and restore TiBu. I did that before for a factory reset, and got back *everything* same day with TiBu. Nice!

So you do not like or need Xposed? How do you customize? You have a rom? :confused:
[SuperSU] Ohmster:
Systemless root means you do not alter your system partition by installing the su binary in your system partition. It installs elsewhere and links to system, I believe.

Current version of SuperSU v2.56 should work just fine for you. Install it in TWRP and reboot, done. Get it right here:

http://xdaforums.com/apps/supersu/wip-android-6-0-marshmellow-t3219344/post64161125
[SuperSU] Ch3vr0n:
I'm fine with stock ROM and my adblock works just fine systemless. The XDA topic has a zip file you flash to make it support systemless. Greenify? I use greenpower to maximize battery life and it doesn't modify system

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] egingell:
All he said was that Xposed will break OTAs. Whether he likes it or not is irrelevant.

Sent from: SGS5 - LP 5.1.1 / SGS4 - LP 5.0.1
[SuperSU] Ohmster:
Greenify just puts apps and system apps and services to sleep if you want to. I needed it with my Motorola Razr because the system was taxed to it's limit, the razr is rather outdated. The Moto X Pure has power to burn so Greenify is not *as important* as it was for the razr. But I do not like Facebook and Pandora and how many other apps running 24/7 when I am not using them. Greenify puts them to sleep.

Hmmm, you sound like a real purist. Not that it is bad or anything, but sounds like you really want to keep the rom and system as stock as you can. How come, you keeping it clean for updates or just want "a totally original rom"? My bad, AdAway is not an Xposed module, it is a host file ad blocker. I guess you would have an easier time with OTA than I would. I like to hear about other experienced member's phones. I learn a lot this way, thanks! :good:

---------- Post added at 04:43 PM ---------- Previous post was at 04:37 PM ----------

Ah, keeping it stock as not to break OTA updates! Just trying to find out his reasoning for such a pure system. Whether he likes or needs it, it was relevant to me. It is actually a nice way to go, but I want to customize my system and without a custom rom, I use Xposed and Nova Prime, works for me. But I will dare to say, xposed is not without risk, I have had system damage before using it "willy nilly" on the stock rom and launcher and that was NOT fun at all. After several weeks of self booting and lockups, I had to do a factory reset to get out of it. Now I am *much* more cautious with it and only use a few modules that I really need and like that I know are safe with what I have. Gotta learn somehow, dude. :silly:
[SuperSU] egingell:
AdAway still modifies the system (/system/etc/hosts to be precise) and breaks OTAs.

By the way, I've never been hung up on keeping the system unaltered for OTAs, because there's more than one way to update (Odin and Mobile Odin both come to mind).

Sent from: SGS5 - LP 5.1.1 / SGS4 - LP 5.0.1
[SuperSU] Ch3vr0n:
I just have no need for as much customization. I'm fine with the stock ROM. I swap to custom when the device no longer receives official ROM updates. Which is what I did when my sensation xe's official support stopped at 4.0.4, I went to CM. when that happens with my nexus devices I'll do the same.

Anyway back on topic.

Though I would suggest if you want to hear more about member's xposed phones you ask in the correct section. That's not what this topic is for :)

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] Ketawa:
There is a version of AdAway in the unofficial XDA thread that works without modifying /system.
[SuperSU] Ohmster:
Really! I didn't think that modifying the hosts file would break OTA. Thanks for the heads up.

I didn't come here for Xposed help or other peoples stuff, I came to ask a couple of questions like how to root Marshmallow and about OTA updates. I am finished with it and got some great answers here. I got the SuperSU help that I needed and I must say, it did work perfectly for me, once I understood that now it is a one shot deal, flash in TWRP and reboot. All this changed since last October when I needed fasboot and adb do get it done. The step by step instructions were gone and I was still doing it like I did months ago, and of course, it failed. All of you gave me some really good and enlightening answers, thanks guys! :good:
[SuperSU] bouchigo:
It's in the first post of this thread: http://xdaforums.com/showthread.php?t=2190753

I haven't used any ad blocking in a while, but I happened to see this a few days ago. I might give it a go later at some point.
[SuperSU] Ohmster:
Yeah, it is there! I use this myself, didn't know a systemless version was available. Off topic here, but thnx! :good:

P.S. Dude, AdAway is nice man. This is your phone, "your phone", not some money grubbing corporate phone. So if you don't want ads, why put up with them? Systemless is there, if that matters to you. AA works, I can tell when I do not update the hosts for a long time, then the ads come back like spiders to get you! :silly:
[SuperSU] Ohmster:
Can you take Marshmallow OTA with SuperSU v2.65?

I have a question. I know that Marshmallow has all of this increased security on it from Google and heard once rooted, you cannot install OTA updates anymore. I think I asked that with SuperSU v2.52. But what about systemless root? Isn't SuperSU v2.65 a systemless root? If I have a clean Marshmallow system and root with SuperSU v2.65, can I then install updates or no? I'm talking a clean MM system with no Xposed or anything, just root with SuperSU v2.65.

I can see now why a lot of guys are keeping clean systems. There is a 6.696 GB security update and if updates like this are coming in, it makes sense to get the phone in a state where one could take the updates.

Can anybody help me out, does the new SuperSU allow OTA updates or how would you take OTA updates if rooted with new SuperSU? Thnx :confused:
[SuperSU] shoey63:
Simply do a full unroot from within the app. (It will restore stock boot and recovery)

Then take the update, flash custom recovery again and re-root.
[SuperSU] Ohmster:
Really? I do not have to flash the stock recovery and system from the original XT1575_CLARK_RETUS_6.0_MPH24.49-18_cid9_subsidy-DEFAULT_CFC.xml.zip file before doing this? For sure that simple, [MENTION=4675598]shoey63[/MENTION]?

I hope so. :fingers-crossed:
[SuperSU] shoey63:
Yes really, provided /system is untouched. :thumbup:
[SuperSU] Ketawa:
IMO the easiest way is to use FlashFire. It can basically replace TWRP so you can keep stock recovery and you never need to use fastboot to complete an update. I tested it out on my stock rooted Nexus 5 (backup phone) and took it through about 5 OTAs without any issues. I'll be using it for the next update on my Nexus 6P.
[SuperSU] Alxoom33:
The problem I found is that if something goes wrong, and Su fails you are stuck. I had to use fastboot in order to flash TWRP because I soft bricked yesterday. The biggest problem seems to be that the stock mm system is so bloated you can't add Layers or anything to modify the System wo breaking it.

---------- Post added at 12:15 AM ---------- Previous post was at 12:11 AM ----------

That is a problem with using Flashfire with stock recovery. On a slightly different topic. Is there a way of using or installing Layers outside of the System Partition and having Layers work?
[SuperSU] Ohmster:
Alright I did mine today and want to let you guys know for others that might be trying this and do not have systemless root installed.

My su was in /system/xbin/su so I did not have systemless root. I used SuperSU 2.56 at the time. I did have to restore stock firmware system from the Clark firmware image zip, XT1575_CLARK_RETUS_6.0_MPH24.49-18_cid9_subsidy-DEFAULT_CFC.xml.zip. The nice thing about this zip of factory image is that it does have a nice Windows batch file, Recovery-System.bat. This batch file will restore the stock MM system from a USB connection with adb. Once done, I still could not apply the update, Failed, and a friend reminded me that we did flash boot.img to get rooted, so I had to reflash boot.img from the Clark firmware. NOW I can apply the OTA update.

Once done, I could now restore TWRP with "fastboot flash recovery twrp-3.0.0-1-clark.img". After that, had to force SuperSU 2.65 to install systemless by echoing in TWRP Terminal:

"echo SYSTEMLESS=true>>/data/.supersu"

Without the quotes. Then verify it with:

cat /data/.supersu

Results:

SYSTEMLESS=true

Now I can flash SuperSU 2.56 and the results were quite different, I got the "patching kernel" and other patching results, installed systemless.

Good to go. For me, I had to flash the Xposed zip file and when I returned to system, I had everything back with update.

Next time should not be so bad as the root is now systemless and I can remove it from the app. First time around, I could not remove root without flashing the Clark system and recovery. Hope this helps somebody.

Yes I am sure that FlashFire would be more simple, but until someone posts some tutorials on FlashFire, I have to opt out. :(

Note:

This is how I did it. Not saying I am right or this is the only way, just how I got my system to take the OTA and installed systemless root.
[SuperSU] ofir_a:
Hi

I flash this supersu 2.67 via trwp 3.0.0 but it's seems that I don't have write permission yet even though that after I checked with root checker it's say that I'm rooted.

I'm with htc one m8 sense and marshmallow any idea??
[SuperSU] Ohmster:
Is FlashFire somewhat intuitive or how did you learn to use it? There are no instructions or tutorials posted, only the app, which I have not installed. Since it took me a half a day just to get one OTA, I would love to try this FlashFire out next time. Where did you learn how to use it or is it simple enough to understand? :confused:

Man, half a day to install an OTA! I have GOT to install and learn this FlashFire stuff! :p
[SuperSU] Ch3vr0n:
The instructions are INSIDE the app

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] RandomPooka:
Excellent reference
[SuperSU] Ohmster:
Awesome! Well, I guess that is why I cannot find them. Time to install the app and start learning. Thank you very much my friend! :D

...make that "my friends" including RandomPooka! :)
[SuperSU] Kri$:
Guys, I have a problem.

I have Note Edge (5.1.1 XEO) - after my phone landed on the floor and I have a little scratch on the screen I decided to keep it instead of selling so...

I did wipe, I flashed 5.1.1 XEO again, I have TWRP, I made root by flashing BETA-SuperSU-v2.67-20160121175247.zip using TWRP.

And now is problem - I have root for couple days, and then root is missing like on screenshot below:

There is no SU binary installed and SuperSU cannot install it.

and I have to flash BETA-SuperSU-v2.67-20160121175247.zip using TWRP again and it helps for couple days and again, and again...
[SuperSU] :
Changelog for latest version?
[SuperSU] :
Open your eyes and read first post
[SuperSU] Aakash Kaushal:
Why so much attitude?..u can simply say its in the op,show some respect dude...i know that he asked a noob questionn but u could handle it in better way.. -_-
[SuperSU] Chainfire:
v2.68 BETA

v2.68 BETA is out, release notes here: https://plus.google.com/+Chainfire/posts/54rqimkQiUL

Developers should definitely read those notes.
[SuperSU] egingell:
Because dozens of people daily don't bother reading the OP or any other posts prior to posting a question that has already been answered wasting everybody's time including their own.

If someone came into your place of employment and asked you a question that's literally answered on the door before they even walk in, you, too, would start getting irate after several people have asked.

Sent from: SGS5 - LP 5.1.1 / SGS4 - LP 5.0.1
[SuperSU] alex00006:
hi guys

tnx a lot chinfire

Thank you very much for all your efforts

can i use this su 2.68 for root N920c and

android 6.0.1 with stock kernel ????