yashsingh1/xdaforums huggingface dataset:
[SuperSU] Ch3vr0n:
[MENTION=631273]Chainfire[/MENTION] I've been following this as you probably have noticed but I probably missed this out isn't fully clear to me. Say systemless becomes fully stable, I would using TB to remove some stock gapps result in /system getting remounted as rw and subsequently cause OTA's to fail?

Verstuurd vanaf mijn Nexus 5 met Tapatalk
[SuperSU] Chainfire:
Definitely
[SuperSU] Ch3vr0n:
Follow-up. Leaving stock apps, but simply using TB to make backups (Which is it's main purpose) would that cause a remount and ota fail? If yes, what's the added benefit of systemless over the current system method?

Verstuurd vanaf mijn Nexus 5 met Tapatalk
[SuperSU] jgcaap:
Anyone have access to the commits which where added to the kernel by chain fire?
[SuperSU] yelupic:
AdAway provides a customizing symlink option to a hosts file wherever you want it to point to (i. e. /data/local/"). - Doesn't this work?
[SuperSU] anakdayak:
r u on sony device? Must i clear cache and dalvik after flash? Tnx mate waitimg for the answer.
[SuperSU] shaggyskunk:
No as per my Signature - Samsung Galaxy Note 4 - And - No you don't have to wipe or clear anything.

Have a Nandroid Backup of your current Rom - Boot into Recovery and just Flash the SuperSu zip - Reboot ?

Sent From My SM-N910W8 Running SlimRemix V5.3
[SuperSU] Rapper_skull:
[MENTION=631273]Chainfire[/MENTION] I flashed 2.62 over 2.61, but first I removed /system/bin/su and /system/xbin/su I previously created. Now I see there's /system/xbin/su that is a symlink to /su/bin/su. Is it virtual or something actually got written to /system?

Inviato dal mio Nexus 5 utilizzando Tapatalk
[SuperSU] shoey63:
It's "virtual", made possible by Chainfire's scripting.

Btw. I love how TWRP now persists, instead of being overwritten by stock recovery on reboot :thumbup:
[SuperSU] Rapper_skull:
Well, while it's very useful for root apps that are not yet updated, the old version was not detected by some root-unfriendly apps that check for the existence of that file.
[SuperSU] TR2N:
Delete
[SuperSU] metaphz:
Currently on 2.61 on a Nexus 6P with ElementalX kernel installed. Do I need to re-flash stock boot.img before flashing 2.62?
[SuperSU] snovvman:
Same question for 2.62 to 2.62-3. Though based on this statement "If you are coming from a SuperSU 2.60 system-less install, or were not rooted at all, then you can just flash the ZIP without any special prior instructions" taken from this post, I'd say you can just flash away.
[SuperSU] abdoelah01:
On chroma latest build 12/10, tried to install 2.62 with no avail. Installed the rom clean with gapps and then installed 2.62, when I try to push the boot.img beforehand I get an error about moto fail or something?

Wut do? :'(
[SuperSU] fir3drag0n:
Same problem here with a nexus 5x and newest supersu
[SuperSU] aliw32619:
i flashed twrp.img and 2.62-3 over latest sony z3 concept software but it doesn't boot , it always boots on twrp

Edit: i get this when flashing the boot.img

patching init.*.rc , fstabs, file_contexts, dm-verity

--- Failure, aborting
[SuperSU] shoey63:
You sure you didn't flash twrp to the boot partition instead of recovery?
[SuperSU] aliw32619:
yeah i typed this command in cmd : fastboot flash recovery z3TWRPrecovery.img
[SuperSU] tsadev:
Just got my Verizon G3 back from LG (sneaky bastards updated me to stock 5.1.1, good thing I could still downgrade ;)), and 2.62-3 works perfectly with latest CM13 nightly using this script, thank you so much for sharing the magic! (literally :p)
[SuperSU] fir3drag0n:
I fixed it by manually flashing the newest supersu apk (I do have the pro version).
[SuperSU] kontini:
Sorry, I'm sure OT but...

Z3 has had a proper recovery mode available just the day before yesterday.

So, have you properly create a recovery partition in this way?

Where is your TWRP supposed to be flashed? Boot or recovery partition? (some xperias use even a FOTAKernel partition). I guess it was made to be flashed at boot partition, maybe I'm wrong, but I used to repack recoveries inside boot images of xperias because xperias didn't have recovery partition and the decision to boot the recovery was taken during boot sequence by pressing a volume button, if not the phone boots straight to OS
[SuperSU] belek1979:
How to verify in app if it is 2.62 or 2.62.3 version?

Everything works gr8 after flashing 2.62.3 on 2.62, but I see in app 2.62...
[SuperSU] Andi17:
Is the latest Version of SuperSu 2.62 http://xdaforums.com/showpost.php?p=64161125&postcount=3

Only for marshmellow of can i use or for lollipop and kitkat too?
[SuperSU] shoey63:
He's using the concept mm rom, which already has a recovery partition and proper bootloader menu
[SuperSU] funiewski:
sorry for OT,so if I use superSU 2.62 and your twrp for z3c, power and vol - simultaneously, than release power and after that vol button the phone will enter twrp recovery, but where to find proper bootloader menu?
[SuperSU] ManHands:
You were in the bootloader when you were using the volume buttons to enter recovery. Reboot to bootloader if you're still in TWRP from the menu.
[SuperSU] berndblb:
You too?

http://xdaforums.com/showpost.php?p=64204285&postcount=3358
[SuperSU] visualarts:
Thanks man for all you did!

But I've come across a problem after flashed the system-less 2.62-3 on my Samsung S6 edge that the battery started to drain quite faster than unrooted. Stand-by for a night may consume 40% of the battery, while it was only 6%-8% in the before. The battery usage indicates that the "Android OS" was awake for the whole night. I don't know if there is anything I can do on this issue. Thanks again!
[SuperSU] Flyview:
Hey [MENTION=631273]Chainfire[/MENTION] I've been using the context switching you helped me out with about a year ago to make the root commands work in my app LeanDroid. You probably don't remember but when Lollipop was new you showed me how to use your supersu library to switch context to system. Maybe I'm not remembering correctly but this was in order to get around selinux restricting my root commands which involve system processes. I have been requiring my users to have SuperSU as their root, as for example CyanogenMod's built in root still isn't working. Is SuperSU still the only root option that allows context switching?
[SuperSU] ashyx:
Maybe your boot image is the wrong format. Supersu requires a standard gzip boot.img to unpack and patch it.
[SuperSU] Lefteris Fragiadakis (Frago):
Flashed 2.62-3 on HTC One A9 and root work excellent in all apps expect Titanium Backup,I don't know why,Flashed in Clean Install,System App Remove work fine,I used this instead of titanium
[SuperSU] JulianJenner:
2.62v3 working perfectly with Xiaomi Redmi Note1. On stock ROM and customs too... Thanks [MENTION=631273]Chainfire[/MENTION]!

PussyFap v4 ROM - Redmi Note 1W
[SuperSU] Groot:
Forgive me for this question but i really cant find a simple answer for my inquiry...

I'm using cm12.1 latest nightly and have supersu 2.52 installed. Should i just flash the 2.62.3 version of supersu directly or there are things that i need to do prior to doing so? Thanks guys and sorry once again
[SuperSU] ktmom:
Have you read the wip thread? http://xdaforums.com/showthread.php?p=64161125
[SuperSU] espero1990:
Thanks!
[SuperSU] chashmaa:
Bro my 9505 4.4.2 have carHDRom with default 2.02 supersu. Can I flash 2.52 over it?
[SuperSU] Pkt_Lnt:
Bro, as I stated in the [Stable] thread, you need to ask your ROM developer! Bro :rolleyes:
[SuperSU] Alxoom33:
Nobody else knows what's compatible with your rom. That's why.
[SuperSU] Pkt_Lnt:
You really should quote the poster who I answered, since the original question if NOT from me. I don't need it explained, since I already provided the same explanation that you just provided to me. :confused:
[SuperSU] daviddiazayuso:
My friend root his n910w8 with super su 2.62 for 5.1 and he lose his lte for h+ help
[SuperSU] sefrcoko:
I would flash stock cok3 for n910w8 through odin, then twrp through odin, then supersu 2.62 through twrp. I didn't lose lte on my N910W8 with supersu 2.62. Pm me if you need more help, not to sidetrack the thread here. Thx
[SuperSU] shaggyskunk:
Check the APN settings - No reason to lose LTE!

Sent From my SM-N910W8 Running SlimRemix V5.3
[SuperSU] ettore88:
SuperSU v2.62.3 beta

Hi guys!!!My question to you...I installed on my Samsung S5(CM 12.1 LP 5.1.1)SuperSU v2.62.3 beta from TWRP recovery...I have trouble with Titanium Backup restore!!!Can i overwrite SuperSU v2.62.3 from recovery with SuperSU v 2.62?Regards:confused:
[SuperSU] RusherDude:
[MENTION=631273]Chainfire[/MENTION]

So far, SuperSu 2.62 on N5 on 6.0.1 works great. The only problem for now.. is on TWRP, when it everytime time is ask to install root because it doesn't find it.

This is minor, but remebers me to old 4.0~ times. Could it be fixed somehow by SuperSU or needs to be adressed by TWRP team because the simlinks aren't possible there and thus the file will never be found?

Keep the excellent work!
[SuperSU] an0therus3r:
Flashed 2.62 recently over CM13 Marshmallow for OnePlus One with TWRP 2.8.6.0 (no issues btw with root/supersu)

Disabled cm13 build in root function and since then I'm having issues with flashing new rom using cyandelta, it gives some java io error.

Could this be a supersu issue maybe? Root is enabled and active for cyandelta.
[SuperSU] daviddiazayuso:
Sorry he fix it taking out the battery thnks
[SuperSU] Starymari:
I'm a little scared ask but I've read almost the whole thread and couldn't find the answer. Is there anyway to use the systemless with a custom rom? I'm using Dirty Unicorns 6.0.1 on my N6 (Shamu).
[SuperSU] Crazy Chuckster:
Ok so I just did the OTA update to 6.0.1 on my Nexus 5x. I then unlocked the bootloader, installed twrp latest version, wiped user data then pushed and installed 2.62-3

Everything seems fine but I have a question, does installing 2.62-3 install the supersu app or is play just putting it on there because it was on my 5 and i copied over the settings?
[SuperSU] Alxoom33:
Of course you can! First uninstall root usingvSu uninstaller zip that's been floating around this thread or use the SuperSu uninstall feature and then flash SuperSu 2.62.zip.
[SuperSU] fir3drag0n:
Hi,

if I flash 2.62-3 systemless with my Nexus 5X, the camera doesn't work anymore :confused:
[SuperSU] Alxoom33:
Try resorting your Nandroid and try again. Do you use a custom kernel?
[SuperSU] fir3drag0n:
nope, stock. I just flashed the stock image.

then the bullhead-mdb08i-boot-systemless.zip
[SuperSU] dadykhoff:
Flash the stock boot image then flash SuperSU 2.62-3.zip in TWRP, no need for pre-modified boot.img's anymore! Good luck.
[SuperSU] Ch3vr0n:
You don't need to flash a modified systemless boot file, that's not being 'stock' as per instructions. Stock is stock, not modified boot. Flash STOCK boot, then directly flash the latest beta 2.62-3 SuperSU zip. The zip file will do the rest.

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] gorilla p:
Can someone please point me to the flashable nexus boot image zips?

From what I can gather, we just need to flash stock boot image, flash latest systemless root and we are good to go? Can the boot image be changed after that? I thought custom ROMs would change that.
[SuperSU] chazall1:
I am on the latest Cataclysm 6.01. I fastboot flashed the Cataclysm boot.img. Reboot, go into recovery, Flash SuperSu 2.62-3

Then flashed my Kernel. All is good
[SuperSU] Nikos2k:
https://developers.google.com/android/nexus/images

yup

you'll also need to remove previous supersu, if it was the system based one (2.52)

they could, but it wouldn't work if they changed it back to stock

it still has to be modified to permit root with supersu
[SuperSU] ettore88:
Hi guys!!!My question to you.I installed Super SU 2.62-3.I have a custom rom on my Samsung S5(CM 12.1 and Boeffla).I have many issues with Titanium Backup!It doesn't work!Does not restore backups!!!and It does not create backup...Insufficient free storage space...(absurd!)Hw can I fix it?Regards
[SuperSU] ettore88:
Guys,but these last versions don't work on LP 5.1.1?On Marshmallow all ok,but i repeat with LP don't work on Titanium!!!(I try on LP 2.62...)I've been down them all, over and over. Can everyone give me an answer?
[SuperSU] ashyx:
This is irrelevant to this thread, it's been reiterated countless times already, it even states in the changelog and after the installation NOT to allow twrp to install SuperSU as twrp doesn't currently detect systemless root.

This is down to Teamwin to fix in their next release.
[SuperSU] deepayanneogi:
Which one is latest su for 6.0.1 aosp roms ?
[SuperSU] KonoeKyon:
2.62-3 is the latest one
[SuperSU] wingfat:
2.62v3 working perfectly with Moto X Pure. On stock ROM (MM). Don't know if related but can only use additional SD card as portable storage. Format will fail if "use as internal storage" is chosen.

Thanks [MENTION=631273]Chainfire[/MENTION]!
[SuperSU] wizardwiz:
2.62-3 works just fine on my Nexus 5 (MM 6.0.1)
[SuperSU] Vadzhik:
Nexus 7 (2013) wifi, android 6.0.1, supersu 2.62-3 titanium backup can not delete system applications.
[SuperSU] gorilla p:
See if "Root App Deleter" works for you. Available on playstore. Only thing that's worked for me for a little while now
[SuperSU] Ja_som:
I had same issue, I installed BusyBox and it works again, try it...
[SuperSU] snovvman:
N6P, 6.0.1, 2.62-3. After flashing SuperSU and boot, root is fine. Reboot, root is there. Reboot again, root is gone (same after more reboots). When I launch SuperSU (v.2.62), the error "...no SU binary installed" appears.

Next, I reboot into recovery, reflash 2.62-3, the above observation repeats. I started over by re-fastbooting the factory boot image and reapplying the SuperSU patch. Same results. This issue is discussed in the N6P Q/A forum, here.

Has anyone seen this problem or know the resolve?
[SuperSU] jeffgt14:
So I've done nothing but install the 2.62-3 zip completely stock Nexus 5X in 6.0.1 and it breaks the safety net check. Is there something this new zip is doing from 2.62 that breaks it? Used twrp 2.8.7.2 to install it and this was right after installing the stock factory image.
[SuperSU] Alxoom33:
If you want to pass saftey net, either delete/su/xbin_bind folder or go back to the 2.61 version.
[SuperSU] Crazy Chuckster:
Im not sure how to do that, can you explain how to delete that folder?
[SuperSU] jeffgt14:
That did it! Thank you got viper4android working and passing the safety net check now!

---------- Post added at 04:09 PM ---------- Previous post was at 04:08 PM ----------

Just delete it in Root Explorer. It's simple.
[SuperSU] jesssiii:
I used Root Explorer and under root tab, went into su folder and checked the box next to the xbin_bind and choosing delete. Then reboot.
[SuperSU] Crazy Chuckster:
Thanks guys!

Everything is working perfectly on my 5x, now rooted with the newest systemless but there is one last question. Every time I reboot I get the following message "Your device software cannot be checked for corruption. Please lock the bootloader."

Is that normal?
[SuperSU] ntegra:
Previously posted this in the wrong thread (FlashFire)...

Can't find SuperSU via searching apps in app drawer (or from "OK Google" on homescreen)...

I have tried 2.61, 2.62, & 2.62-3. If I just install normal from Play store 2.46, no issue.

Nexus 6P-6.0.1-SuperSU 2.62.3
[SuperSU] ntegra:
http://www.androidauthority.com/goo...rrupted-and-modified-android-software-629180/
[SuperSU] Alxoom33:
Yes, flash a custom rom and kernel and the warnings will go away.[emoji2]
[SuperSU] Fabiomessina:
Delete
[SuperSU] star_throne:
Flashed full stock factory image, then twrp, then cataclysm mod, then Hells-Core kernel and then SuperSU 2.62-3 and when i booted the app said i dont have the supersu binaries installed. Then i flashed SuperSU 2.62-3 and it works for some time, then it says the same thing. Flashing supersu again and again and it always does this after some time.
[SuperSU] ClayTdoG:
Can someone give me a step by step explanation on how to install this please? My attempts have led to a secure boot lock every time, im on a lg g3 vs985 with twrp 2.8.7.0 and im currently using cm13.
[SuperSU] Alxoom33:
That's strange. Sounds like you did things correctly. Did you check MD5 binaries at each step? You cold try the full Cataclysm rom and then flashing EX 3.0.7 kernel on enforcing setting. Then flash SuperSu 2.6x.
[SuperSU] star_throne:
Im pretty sure that the problem is in kernel, elementalx worked earlier today with normal 6.0.1 cata. Guess i will now just wait for the dev to fix the kernel, hells core been the best for me for what i have tested.
[SuperSU] Alxoom33:
I prefer Elemental X and the EX Kernel Manager. [emoji2] [emoji106]
[SuperSU] bobby janow:
Try it this way: Stock, twrp, cata mod, reboot into rom. Everything working? Then back to twrp and flash supersu 2.62-3 and THEN hellscore kernel not the other way around. If that doesn't work then try a different kernel.
[SuperSU] gorilla p:
Just to be clear, I plan on going forward with this. I will be doing the following.

Unrooting via SuperSU system app,

Factory Reset

Push factory Stock Img (N4/Mako) from PC

Boot to stock ROM.

Reboot to Bootloader

Push TWRP recovery img from PC

Boot to Recovery (TWRP) and Flash custom ROM.

Boot to custom ROM. Once ROM is booted, reboot to recovery and flash latest systemless root.

If ROM includes root, I assume we need to remove it before rebooting to recovery to flash systemless root?( thought we would just flash systemless root right after the ROM to avoid the ROM installing root and having to remove it.)
[SuperSU] jcsww:
Most custom ROM's are pre-rooted, so you will have to flash the unroot first.
[SuperSU] ettore88:
Hi!!!Could you show me a version of SuperSU compatible with LP 5.1.1?I'm still using SuperSu 2.52 beta ...These latest versions are only for Marshmallow?

Inviato dal mio SM-G900F utilizzando Tapatalk
[SuperSU] claytonjn:
It's embedded in the settings app, so the launch point from the app drawer doesn't exist.
[SuperSU] snovvman:
A few posts up from yours, here, I describe a similar problem and linking to others who experience the same.
[SuperSU] ashyx:
It clearly states the latest version is 5.1.1 compatible.
[SuperSU] wind0zer:
Tested systemless SuperSU-v2.62 with cm13 nightly on Galaxy Tab pro 8.4 st320/mondrianwifi and it's working alright. Used host blocker Adaway, and xposed without any issues so far.
[SuperSU] ettore88:
Thank you very much!!! I've already posted several times my problem ... (Titanium Backup does not work with the latest vs. ..) I have a Samsung S5, 12.1 CM, Boeffla Kernel,TWRP recovery ... Could someone help me to fix it?

Inviato dal mio SM-G900F utilizzando Tapatalk
[SuperSU] lucarp78:
Install busybox and then retry TB.
[SuperSU] ClayTdoG:
I get secure booting error 630 every time I attempt to install this, what am I doing wrong?
[SuperSU] ettore88:
Many THX!Tonight i'll try.[emoji6]

Inviato dal mio SM-G900F utilizzando Tapatalk
[SuperSU] italia0101:
I get this too,
[SuperSU] shaggyskunk:
What do you mean that TB isn't working with SuperSu 2.52?

Is TB saying that you don't have Root - Or it's not backing up or restoring? Check your SuperSu logs to make sure that TB is granted SU permissions - If it's not - Click on TB in SU and Change it to Grant.

If it's not backing up or restoring - Clear Data - Cache and Dalvik from TB - Uninstall TB - Check on the location of TB on your device - ie: sd/Titanium Backup and delete it - Reboot - Download TB from the store and make a new TB backup of your User Apps.

Sent From my SM-N910W8 Running SlimRemix V5.3
[SuperSU] secguy:
Is there a reason why only 5.1/samsung is supported in systemless mode? I'd like to try on a Sony Z1 with 5.1.1 stock rom (14.6.A.1.236) but not sure if I should.
[SuperSU] snovvman:
I went back to system root for now. If you're looking for more info for a N6P, see my post here. There is a link in the post that directs you to the latest modified boot so you can system root.
[SuperSU] clevebb:
Just upgraded to CM13 on oneplus one. Tried with system root, but cf.lumen didn't work. I used SuperSU 2.63 and it's working great! There was one bootloop, not really a loop, more like restarted in the middle of booting once.
[SuperSU] ettore88:
Hi!!!Thank you very much! Unfortunately, TB does not work with the latest vs 2.62.3/2.62 on 12.1 CM (Samsung S5). I can't make backups (I get: "insufficient free storage space!) ... Doesn't work either I'll restore!!I also installed BusyBox ... There's nothing to do! Ever experienced all this ...What do you think?Hw can I fix it?
[SuperSU] RusherDude:
Anyone managed to update Busibox stericson? It says theres a new update and it seems to update, but when I reboot, it keeps me telling I have the old version.

Maybe it has something to do with the fake symlinks or something?

Im using SuperSu 2.62 on stock 6.0.1.
[SuperSU] star_throne:
Hmm.. I got the Hells Core kernel working on Cataclysm now with chainfires boot.img but then i get the known battery % problem. Any way i could fix this?
[SuperSU] ettore88:
Where can i find the log of errors that generates by TB?

Inviato dal mio SM-G900F utilizzando Tapatalk
[SuperSU] KonoeKyon:
Don't use the modified boot.img. Just use SuperSU 2.62-3 and flash that over the stock kernel, then you can flash HellsCore overtop.
[SuperSU] haseoxth:
I have the same issue.

Use a kernel made for 6.0.1, with old 6.0 kernels (like Chainfire's modified boot.img) you will have percentage display problem.
[SuperSU] drothenberger:
I think this is due to the new /system/xbin overlay in 2.62. If you want the update to stick, you either have to umount /system/xbin before you update or install into /su/xbin_bind. You will need to reboot after the install either way.

Another alternative is to install in /su/bin.
[SuperSU] star_throne:
I switched to pure nexus, tired of trying to get this working. For your busybox issue, try this http://xdaforums.com/android/software-hacking/tool-flashable-busybox-v1-23-2-stericson-t3219431 (1.24.1 is latest right?)
[SuperSU] Ch3vr0n:
No stock /system : not following instructions = no support from chainfire. There's no reason to not do it, it doesn't wipe your user data, you don't have to reinstall apps,...

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] sefrcoko:
Same with me on n910w8 running stock 5.1.1 cok3 rooted with supersu 2.62. Maybe the TB app devs need to release an update?
[SuperSU] ettore88:
Hi many thx 4 your reply.There is only uncheck the "mount namespace separation" option in SuperSU and restart the phone.Now TB works fine!Many thx to you all!Bye[emoji6]
[SuperSU] frikakwa:
Give a try to Busybox on Rails! ;)
[SuperSU] mrro82:
Working fine on my nexus 5 running lollipop preview.

Sent from the jaws of my Hammerhead!
[SuperSU] Chinaboy5216:
Running great on the Chinese Note 3 SM-N9008V

Thanks Chainfire
[SuperSU] Frank Westlake:
Try the debug.2.0.zip ( http://xdaforums.com/showthread.php?p=56291448) to get some debugging data for Chainfire. I don't know yet if it works on the Note 4. In Recovery, install SuperSU 2.17 then without leaving Recovery install the debug zip. If it successfully saves a data zip then send that to Chainfire.

Frank
[SuperSU] rcobourn:
Debug log attached.
[SuperSU] Frank Westlake:
You might be trying to avoid another bootloop and that is understandable, but debug.zip doesn't help much unless it is processed immediately after installing SuperSU and in the same instance of Recovery (TWRP in this case). If you do this again you can edit the post and replace the data zip.

Thanks for confirming for me that debug.zip works on the Note4.

Frank
[SuperSU] rcobourn:
Okay I did that first but it captured so little I thought I had to let it boot loop first then run debug. I actually kept the first debug run, but Tapatalk doesn't seem to support uploading it, will do when I get back to a computer.
[SuperSU] scoobyjenkins:
I use my browser (chrome) to upload to XDA, you can share this thread to a note app or email and copy/paste the link for quick access, unless it's already bookmarked!

Tapatalked that shiznit.
[SuperSU] rcobourn:
Actually it did capture more the first time, I may not have been fully awake yet. :). Anyhow, updated my attachment.