yashsingh1/xdaforums huggingface dataset:
[SuperSU] shoey63:
Ok, so :-

- Formatting /system in TWRP and rebooting to recovery with mount read only box ticked sets lifetime writes to 0

- Flashing/fastbooting system.img "should" do the same thing (in my case it didn't so I formatted first)

- mmcblk0p24 may not be the system block path for your device

- to find out, use a root explorer to navigate to dev > block > platform and open the folders there till you find by-name > system

- Your explorer should give you the true block path of /system.

- If it doesn't, use FX file explorer with root add-on
[SuperSU] occtec:
Hi guys I seem to have an issue with systemless root procedure on my son's N5. He is currently on Cataclysm latest beta build and running ElementalX 6.07. When i attempt to root the device using SuperSU 2.65 it seems to install to system. I have verified this in SuperSU. Not sure where I'm going wrong as I have followed the same procedure on my N5 without issue. Any help would be appreciated, cheers.
[SuperSU] H4X0R46:
Just following up on this, ElementalX kernel seems to have caused this issue! Letting you all know, I switched to Elite kernel and the phone doesn't freeze!

Sent from my Nexus 6
[SuperSU] duki994:
Don't do that on LG devices. They require BUMP (to sign boot.img) and bootloader that's not patched to fix that exploit. Systemless can't be used on LG.
[SuperSU] GieltjE:
Can't we build a detection? Now flashing it will auto flash the systemless and break LG devices.
[SuperSU] sansnil:
I missed your original post but for what it's worth I'm seeing the same thing with my N6 and ElementalX. I had no clue what the cause was so thanks for following up as it helps me out too.
[SuperSU] Aftrburnr:
Just wondering if I'm rooted properly?

T-Mobile Galaxy Note 10.1 2014 Edition LTE SM-P607T

Fresh flash stock Lollipop 5.1.1 USB Debugging on

Odin twrp-2.8.7.0-lt03ltexx-4.4.img.tar

I then flashed BETA-SuperSU-v2.65-20151226141550.zip and let the system do it's thing. TWRP was asking to root. I did not let it. After tablet finally booted, root checker says I was rooted. A root file manager works but trying Titanium Backup, it says couldn't get root. So, some things to figure out there, maybe some more tweaks?

Now while booting tablet and also while powering off, I get in upper left corner in yellow is:

Set Warranty Bit : kernel

Does this happen to any of you?

I see just released earlier today, BETA-SuperSU-v2.66-20160103015024.zip Maybe I should try it? If I do need to, how would I update SuperSU with the new version? Just flash the updated .zip with TWRP?

Thanks!
[SuperSU] joderme:
Does systemless still have bad wakelock/battery drain issues?
[SuperSU] Ingenium13:
I never had any wakelock or battery issues on systemless.

Sent from my Nexus 6P
[SuperSU] edrickmph:
Deleted.
[SuperSU] nathanchance:
Right here, from this thread/post.
[SuperSU] Neverendingxsin:
Ummm what?
[SuperSU] egingell:
What do you mean "still"? Root doesn't *do* anything unless/until invoked at which time it does its thing and quits thereby continuing to do nothing.

Sent from: SGS4 - JB 4.2.2 MF9
[SuperSU] mielletseed:
Have you ever heard about the knox flag on Samsung devices? Since you modified your system you triped it (and the check is done on every boot).
[SuperSU] Aftrburnr:
Yep, I do know about the Knox flag, I think Samsung started it about android 4.3 :( Bought the tablet used and while I was checking it out b4 buying it, I saw that Knox was already tripped lol Oh well, no biggie ;) The price was right! But, on the stock 5.1.1 unmodded rom, that yellow msg didn't come up even tho Knox was tripped.

Just kinda strange that that comes up now on every boot/shutdown and as I've not seen that b4, I was questioning whether I was fully rooted or needed to do something else? I thought possibly SuperSU was doing it. I have other Samsung devices rooted that I didn't trip Knox and I guess that's why I don't see it on them.

Also, Titanium Backup says I'm not rooted or it's not seeing root for some reason...

Thanks!
[SuperSU] TR2N:
Delete...
[SuperSU] NZgeek:
Are you using a Samsung device with a 5.1-based ROM? If so, the latest 2.66 build might have a fix for you. It looks like it could have been SELinux-related.

If you're using something else then I'm not aware of any battery issues.
[SuperSU] Chainfire:
SuperSU does not have a wakelock/battery drain issue that I know of.

Some Samsung devices have an issue where the device never enters deep sleep. This is not actually due to root, but due to having a non-stock boot image or recovery image installed (both systemless root and TWRP will trigger this). The bootloader checks if boot/recovery are official Samsung, and if they are not, some areas of the flash memory are write protected. Presumably to prevent tampering with parts of the phone that might cause the device to violate FCC (and similar agencies) regulations.

So far no issue. But then Samsung also uses write-back caching on these partitions and it doesn't turn that off when they are write protected. As a result, cache synchronization fails, but the cache needs to be synchronized before entering deep sleep - and thus the device is kept awake.

The stop-gap solution is to disable this caching completely, which is what the 000000deepsleep script does, which you can find mentioned or quoted in many posts around the forum. From SuperSU 2.66 onwards, that script is automatically installed on Samsung devices when systemless root is used.

HomerSp figured all that out and wrote a source patch, which as far as I know is used by all the custom kernels.

It's not a SuperSU issue, it's not a root issue, it's not an SELinux issue... I'd be hard pressed to even call it a Samsung issue, as the issue never occurs if you use a Samsung device as it is intended. If I were Samsung I'd fix it anyway, but knowing both Samsung as well as Google engineers all too well, all of them will treat it as a 'not my problem or responsibility' issue and it will never get resolved. Corporate culture for the win.
[SuperSU] milojoseph:
Everytime i update the superSu it say it failed to update when trying to patch during twrp and when i reboot i loose root. You have a thread to discuss update problems and many samsung users are having these problem.

I am on a custom rom 5.1.1 with xposed twrp and lost root. I will post this on the update problem thread of yours as well. Thank you
[SuperSU] shoey63:
Systemless root is great :good:

I know it is intended to make OTA updates easier, but it can work the other way too.

You can totally annihilate your /system partition with experiments, then if they don't work, just re-flash system.img, and you are back to stock /system and rooted :)
[SuperSU] alex00006:
Hi

I'm with su 2.65 rooting s6G920i stock rom

Root sucerfull

But

After reset factory data

This su 2.65 erased

Why after reset factory this su clear
[SuperSU] shoey63:
That's because systemless root uses /data. Wipe /data and systemless root is gone. You need to re-flash it.
[SuperSU] dragos281993:
I can asume that it's called "systemless root" cause it's not written on system anymore. In the "Experiment su..." thread there is something that sounds like this : "A backup is made (/data/stock_boot_<sha>.img.gz) of the original boot image before patching it". Maybe I understood it wrong, but I think the root is written in data, meaning that the factory reset which cleared the data + cache + dalvik cache partitions, cleared the SU as well.

Anyway, you can just flash SuperSU again. It doesn't take ages.
[SuperSU] alex00006:
Tnx my friend

---------- Post added at 04:20 PM ---------- Previous post was at 04:19 PM ----------

Buddies,

I just root my device with SU 2.65 and then reroot and flash it with SU 2.56

This technique leads me to when I reset factory not to lose Su. I mean with this, after reset factory the SU won't erase.

Now I have a question in my mind,

Is this process cause me any trouble or problem or It's OK?

Cause I don't want to lose Su after reset factory
[SuperSU] MrPib:
2.66 works perfectly on my 6.0.1 N6.

Thank you, CF!
[SuperSU] Alxoom33:
Same for me. No issues.
[SuperSU] w0rinal:
*deleted*
[SuperSU] coreydkoster:
I missed typed, yes, delete that.

Then reboot.
[SuperSU] ddrum2000:
Brillant! Thank you. I suspect that was the problem the whole time.
[SuperSU] Aftrburnr:
On a T-Mobile Galaxy Note 10.1 2014 Edition LTE SM-P607T Lollipop 5.1.1 I'd like to update BETA-SuperSU-v2.65-20151226141550.zip to the new release BETA-SuperSU-v2.66-20160103015024.zip. How should I go about doing this? Can I flash the latest version with TWRP over the old with everything being ok or should I just re-do the whole thing from scratch?

Thanks!
[SuperSU] mbk17:
I flashed 2.66 on a fresh root through TWRP. SuperSU and a rootcheck app tells me I have 2.52. I need 2.60 or later to use a specific kernel. Anyone have any suggestions?

Thanks.
[SuperSU] boxcar8028:
Just wanted to report back. Just flashed v2.66 over v2.65 on my n7 and 6p both stock 6.0.1 without any issues. Everything booted up smoothly. Great way to start the new year with a SU update. Thanks, CF, great job!
[SuperSU] kchaisu:
Since I have been using Beta SuperSU 2.65 and 2.66, I have no problem on my old HTC Desire S, CM-13 sagaopt. Also I use with [MENTION=1143630]osmosis[/MENTION] busybox. Thank you very much Chainfire and osmosis, for your kind contribution.
[SuperSU] LoopDoGG79:
I have a Note 4 from T-mobile. Ive tried using this several times and everytime my phone will have freeze ups and random reboots after several days. I know, I should of provided a logcat. Has anybody attempting to use this on TW experienced instability after flashing SU beta 2.65?
[SuperSU] GroteBozewolf:
Did anyone try systemless root on a Nexus 4 with the stock 5.1.1 rom?

I know it does not require systemless, I was just curious. Because it would also solve the Google Pay issue for me.
[SuperSU] dbzgod:
[MENTION=631273]Chainfire[/MENTION] updating from 2.65 to 2.66 breaks data on Canadian Note 4.

IMEI and baseband become unknown. Downgrading back to 2.65 restored it.

Not sure what log to provide or how to go about getting one in this case, as it installs fine in twrp and apps get root access without issue.
[SuperSU] Maxr1998:
My Nexus 4 (with custom rom, should be the same though) is running systemless just fine. So to install, make sure you have a stock system and boot, and then flash the SuperSu 2.66 in TWRP.
[SuperSU] Aftrburnr:
Well, I went ahead and just flashed the new over the old. Seems to have gone fine. It didn't fix my problem with Titanium Backup tho not getting/seeing root. Can or how should I fix this?

Error msg: This attempt was made using the "/system/xbin/su" command.
[SuperSU] amnher:
Is this possible to do with SuperSU 2.66? This is regarding regarding OTA update

*Assuming I have custom recovery and rooted

1. Unroot using SuperSU

2. Install OTA using built-in

3. Reflash root
[SuperSU] berndblb:
Why don't you do exactly as the error says and copy the apk to priv-app?
[SuperSU] krazyace35:
Can the old system supersu be flashed over systemless root or will I have to flash my system.img backup

Sent from my HTC One M9
[SuperSU] H4X0R46:
Glad it did! ElementalX must need to be updated, it's my favorite kernel, but for the time being I will be using Elite until I find something nicer! :)
[SuperSU] jeffreii:
I'm looking for confirmation that that's ok to do. I'm under the impression that adding files to /system would modify it, which is exactly what systemless is avoiding...though I suppose we could simply later delete the file? Is there not a better workaround that should be deployed by the dev?

Thanks for the clarification and sorry if any of this is obvious. I have read dozens of pages of this and related threads to try and understand the process, but I am definitely not an expert on the subject.

Thanks :)
[SuperSU] KonoeKyon:
Yeah just mounting it r/w makes it modified. So unless you want to be able to take OTA updates with only having to reflash stock kernel+recovery, you can't use that app. Just deleting it won't work. And if you read the WIP thread there's information on how to allow it to be mounted r/w.
[SuperSU] Empty Hand:
So when I flashed 2.66 and put in the systemless command in TWRP, there was no xbin_bind in su when I booted up. Was that removed from 2.66?
[SuperSU] Aftrburnr:
I see xbin_bind in mine and just went from 2.65 to 2.66 but could be different devices do different things? Didn't see it mentioned in the change log either...
[SuperSU] Alxoom33:
Don't know what you're seeing. But Elemental X running just fine with 2.66 Systemless. On N6 running Cataclysm 6.01.
[SuperSU] GroteBozewolf:
Great. Did you have to force it to use systemless (using echo SYSTEMLESS=true>>/data/.supersu)?
[SuperSU] Maxr1998:
Oops, forget everything I said. SuperSu only works in system mode below Android 6.0 (except from some Samsung devices with 5.1.1), missed that you have stock 5.1.1.. So systemless is not possible for you.
[SuperSU] H4X0R46:
Maybe SuperSU 2.66 fixed the issue, I may flash it with elementalx and see if it's fixed! Thanks for the feedback!

Sent from my Nexus 6
[SuperSU] shoey63:
Well I have systemless mode on my Sony Xperia Z (C6603) running stock 5.1.1

Anything is possible with android :beer:
[SuperSU] Didgeridoohan:
Does this mean your phone was rooted with 2.52 prior to you trying to flash 2.66? If so, you need to completely remove 2.52 before you can flash 2.66. There are clear instructions about this in the WIP-thread.

Otherwise you need to give a lot more information about your setup.
[SuperSU] anakdayak:
Hi i'm on sony xperia z1 rooted with supersu 2.46.Is it possible i just flash the beta 2.66 on top of 2.46?
[SuperSU] JochenP:
You have to flash original untouched boot.img to remove old SuperSu
[SuperSU] shoey63:
Flash in recovery, and it should work. You won't get systemless though - not without serious tweaking.
[SuperSU] shaggyskunk:
Any benefits (sorry for asking - I just jumped in briefly)?

Sent From My SM-N910W8 Running CMRemix 6.01
[SuperSU] shoey63:
If 2.46 is doing what you need it to do, just stick with it ;)
[SuperSU] shaggyskunk:
Yeah I'm on 2.52 - And the Dev who is building my Rom is trying to get Enforcing working properly without any other issues - CM based 6.01 on Samsung Note 4 - I know that I'll have to do some reading to catch up - I've only been peeking in once in a while - But I'm not sure if 2.52 is doing what is needed - I'm not worried about getting systemless root - Rom is already rooted - I'm just curious about Permissions denial on a Samsung with Enforcing... But like I said - Got me some reading to do

Sent From My SM-N910W8 Running CMRemix 6.01
[SuperSU] sabret00the:
Does anyone know if there's a SuperSu 2.6x installer can mod the kernel without modding/removing the signature that's required for it to work on the LG G3 (D855)?
[SuperSU] alex00006:
Hi

I have s6 and android 5.1.1

i with su 2.66 root successful

Tnx China fire

no problem deep sleep ok

But

not work titanium backup and restore app and data !!!!!

i use last version titanium

plz guide

Tnx friends
[SuperSU] shaggyskunk:
I wouldn't ever regret supporting a Great Developer - Ever!

But if you want to delete apps - Have a Nandroid of your current setup - Use Root Explorer and navigate to the apks that you want to delete - For System Apps - look in System Priv-App - System App and Data/data.

Delete the ones you want - Reboot and Done.... Just be sure that you know what you're doing ?

Sent From My SM-N910W8 Running CMRemix 6.01
[SuperSU] Manuel15:
There are other apps you can use to delete system apps,I used this app some times (https://play.google.com/store/apps/details?id=com.jumobile.manager.systemapp&hl=it)
[SuperSU] wilflare:
I just saw this line - "If TWRP offers you to keep /system read-only, indeed keep it read-only."

Does this mean when we first set-up TWRP, we choose the option "Keep read-only"

Would that affect the flashing of nandroid backups, etc?
[SuperSU] osm0sis:
There is adhoc bump and whatever else support by adding a script to /data that does the image modification. Search the thread for other users who have it set up. :good:
[SuperSU] pnr2020:
Thank you for that great advice

---------- Post added at 04:42 PM ---------- Previous post was at 04:41 PM ----------

Thank you for that going to check it out now
[SuperSU] pnr2020:
Thank you for that going to check it out now

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

Cheers mate very useful going to try it out
[SuperSU] alex00006:
hi

Now is the best version for Root anaroid 5.1.1 (Example for rooting s6 android 5.1.1)???

2.65 or 2.66 ????????
[SuperSU] Blac Caesar:
[MENTION=631273]Chainfire[/MENTION] SuperSU v2.66 running perfectly on OnePlus One; [MENTION=2040569]jgcaap[/MENTION] build of CM-13
[SuperSU] osm0sis:
Use the latest. You'll be fine.
[SuperSU] dbzgod:
Also to add to it I didn't notice any deep sleep issues before, when I wake up my phone only losses 2-3% after sleeping about 7hrs.
[SuperSU] NZgeek:
If you're concerned about keeping the system read-only and not breaking dm-verity, you won't be restoring Nandroid backups.

Nandroid backups only work at the file level for standard partitions, not block level. When you restore the files, the files are just written or normally, which means they won't pass any block-level checks.

You'd be better off keeping the related system.img and restoring that using dd when you restore your backup.
[SuperSU] yung40oz84:
I'm confused because it did not make /su/bin as it says in 2.65, now I am on 2.66, and everything is working properly as far as layers and what not, but I was just wondering does it always create the /su/bin? I was completely fresh stalk, flash cataclysm mod, then SuperSU 2.65, then AK Kernel.
[SuperSU] Captain_Throwback:
TWRP allows you to restore a system image, so this isn't always correct. It depends on the type of backup that was made.
[SuperSU] osm0sis:
Any idea if direct system.img flashing is going to be added to the Image flashing menu?
[SuperSU] Captain_Throwback:
Any image can be added to the image flashing menu on a per-device basis. I doubt that'll be done for all devices by default as most don't need it.
[SuperSU] osm0sis:
Sweet! Well hopefully it can be done for the Nexus devices for the next release, since we certainly have readily accessible Factory Images. :)

It'll be especially helpful while we wait for Chainfire to update FlashFire. :D
[SuperSU] dastinger:
I tried asking this on two different places and still got no definitive answer. I'd like to do it asap so why not try it here.

I found lots of posts regarding system -> systemless but none with instructions on how to go systemless to system root. I'm on Cataclysm + ElementalX on a Nexus 6P. Any clear instructions?

Thank you!
[SuperSU] osm0sis:
My unSU post explains how to remove all traces of systemless root. Then you'd just have to remove /data/.supersu to undo any overrides and flash the SuperSU zip again.
[SuperSU] dastinger:
Thanks a lot!

Just to make sure, the latest SuperSU zip for system root is 2.56, right?
[SuperSU] nathanchance:
2.56 is systemless, 2.52 is the latest for pure system root. Starting with 2.64 and above, system root is prioritized during installation (if it can be done, it will) but systemless root can still be achieved through a terminal command so it is a smart/hybrid installer.
[SuperSU] osm0sis:
If it's possible to do system root the latest zip will detect that and do so, so the latest (2.66 at the moment) is still the way to go.
[SuperSU] dastinger:
Thank you both so, as long as I don't have systemless already installed, whenever I flash 2.64 and above it will prioritize system root? How can I know if it roots using system or systemless method?

This is important because I am on 2.65 already (starting with 2.61) and Secure Settings is not working. I'm troubleshooting and, since I think the issue is with systemless, I want to make sure that traditional method is used.

Sorry for so many questions.
[SuperSU] nathanchance:
While SuperSU is flashing, it will tell you which root it chooses or you can go into SuperSU > Settings > Install SuperSU into /system and see why it is greyed out to tell.

Delete /data/.supersu, go into SuperSU > Settings > Full unroot, dirty flash your ROM if you are on one OR the stock boot.img if you are on stock, then flash SuperSU 2.64+ again. It should choose system root if it is possible.
[SuperSU] Aftrburnr:
Titanium Backup not getting/seeing root

Can or how should I fix my problem with Titanium Backup not getting/seeing root? Using SuperSu 2.65 and now 2.66... On a T-Mobile Galaxy Note 10.1 2014 Edition LTE SM-P607T Lollipop 5.1.1

Error msg: This attempt was made using the "/system/xbin/su" command.

Thanks!
[SuperSU] shaggyskunk:
I don't know why you're having a problem - I've flashed 2.66 on three different devices today - Nexus 7 running 6.01 - Note 3 & Note 2 running 5.1.1 - No issues with Root & TB.

You didn't allow TWRP to install SU after you flashed SuperSU 2.66?

Sent From My SM-N910W8 Running CMRemix 6.01
[SuperSU] Aftrburnr:
No, sure didn't. ;) Root file mgr works. Checking SuperS

U app shows Titanium Backup asking for root and I grant it but then error msg...
[SuperSU] dastinger:
Alright, gonna start with a Nandroid and follow the instructions.

Thank you so much!

And, again, thank you [MENTION=4544860]osm0sis[/MENTION]
[SuperSU] corkiejp:
Nexus 9 6.0.1 (MMB29S) successfully rooted with 2.66

Nexus 9 6.0.1 (MMB29S) successfully rooted with 2.66.

Hopefully kept my system untouched by using AdAway Systemless Host, Busy Box installed into /su/xbin/ using this app and only booted TWRP instead of flashing it.

Will know in February when I try to side-load the next OTA.
[SuperSU] shoey63:
I know it's a bit OT here, but could you advise what the flags are to to add to the twrpfs.tab, and/or boardconfig.make to make dd backups of /system, and flash system images?
[SuperSU] Captain_Throwback:
I think that's way too OT for this thread. I'm not trying to hijack it with TWRP talk. If you search the TWRP code on github you should be able to find what you're looking for.

EDIT: https://github.com/omnirom/android_bootable_recovery/blob/android-6.0/partition.cpp#L403

EDIT 2: https://github.com/omnirom/android_bootable_recovery/blob/android-6.0/partition.cpp#L589

Now , back to your regularly scheduled posts asking about the difference between system and systemless root, lol

---------- Post added at 08:13 PM ---------- Previous post was at 08:03 PM ----------

It won't be added by default for any devices, I'm pretty certain of that. If you want it for a specific device, submit a patch to Gerrit and [MENTION=912474]Dees_Troy[/MENTION] can make a decision on it there.
[SuperSU] luigidk:
Seems that flashing 2.66 over 2.65 has caused AP to fail now (at POS).

So I've:

- run the unsu.zip to remove SU

- re-installed 2.65 (entered the echo command in TWRP terminal)

- removed su/xbin_bind directory

Now AP is working again - not sure if it is:

- 2.66 or that I had to remove the /su/xbin_bind directory?
[SuperSU] bigknowz:
Thanks

Muy bueno!
[SuperSU] a1exus:
Is it safe to delete /su/xbin_bind? Are there any downside to that?
[SuperSU] nathanchance:
Yes, it is. It allows apps that are poorly coded to make root calls. If you remove it, some apps may not work but I have noticed no downside otherwise. If a root app breaks after you delete it, just let the developer know they need to fix it.
[SuperSU] Sky88:
I'm using SuperSu 2.52 how can flash 2.60& above versions.
[SuperSU] luigidk:
Retested using 2.66 - and the removal of /su/xbin_bind is what fixes the problem with AP.
[SuperSU] NYLimited:
I just flashed 2.66 over 2.52 with TWRP. No problems flashing or afterward. I'm not using systemless, however!
[SuperSU] shoey63:
Ok, but THANKS :beer: (damn, can't hide the images on xda app:p)
[SuperSU] vel_tins:
Ok, so far so good.

But how to "force" the installer, to execute a Systemless root install, which I would prefer because of the OTA's?
[SuperSU] Jacktheskipper:
Just wanted to report in:

Installed the new Factory Image Update MMB29S for Nexus 5 and used 2.66 Zip file from CWM-Touch.

Everything works flawless so far ...