yashsingh1/xdaforums huggingface dataset:
[SuperSU] osm0sis:
Further down arter97's timeline he points to Jan 6th as having the necessary info to fix. Reading back I think it's actually on Jan 5th and is apparently kernel/recovery-side and requires an update to the latest f2fs or at least include the following:

https://git.kernel.org/cgit/linux/k...le.git/commit/?h=linux-3.18.y&id=7a895023cc2c

I guess TWRP and ROM/custom kernels will all need this.

[MENTION=912474]Dees_Troy[/MENTION] [MENTION=1162986]Captain_Throwback[/MENTION] [MENTION=4878287]_that[/MENTION] [MENTION=4684315]flar2[/MENTION] [MENTION=3292224]franciscofranco[/MENTION]
[SuperSU] Chainfire:
This should be solved next update.
[SuperSU] Chainfire:
Arter told me he will post all the details here in a bit.
[SuperSU] chipiko:
I restored and all is well. Guys please a ROM for HTC Desire 610 !!!! Most of the description is not compatible with my phone.
[SuperSU] arter97:
f2fs with Android story is always complicated.

So why is SuperSU broken with many custom ROMs:

systemless SuperSU saves a raw ext4 image in /data/su.img and mounts it as a loopback device and to various locations upon boot.

The problem with f2fs, is that most kernels included in custom ROMs have issues with managing loopback devices.

This is not SuperSU issue, rather, kernel developers has to incorporate the necessary fix for f2fs.

This “fix” is rather dumb :

https://git.kernel.org/cgit/linux/k...y&id=0d5ed69805ee57d7b416c4a6b47c3b67284db105

The f2fs head, Kim Jaegeuk forgot to add those pointer to post-4.10 versions of f2fs backports.

(The stock OnePlus 3T’s kernel source code seems to already have this fix. This explains why OxygenOS didn’t have any issues with SuperSU.)

So you have 2 choices :

A. Cherry-pick that fix separately

B. Merge f2fs version all the way up to 4.10(latest f2fs-stable.git is updated to 4.10)

But there are more stories to be told, unfortunately.

Both 2 methods introduce a new problem : breaks all previous f2fs versions to read the data.

There is no on-disk-format change introduced by the new “fix”, but it turns out that older versions of f2fs has an issue which is exploited only when newer version of f2fs is used to write data.

You need this additional fix, if you have no intention to update f2fs to the latest 4.10 version :

https://git.kernel.org/cgit/linux/k...y&id=7a895023cc2c06c08a6cccb71e112255eb0837ee

Without this fix, the kernel will panic upon reading any data.

So we took care of the method A.

However, there is still an issue with method B : deadlock.

As noted in https://review.lineageos.org/#/c/95316/ , there are deadlocks present on the latest version of f2fs(from 4.8, iirc).

It took about a month to bisect it, and I got the culprit commit :

https://git.kernel.org/cgit/linux/k...y&id=de62dad6f502c67fd01b5c0b1f7f242836ce90d0

I’m still yet to hear from the upstream developers, but I can confirm that reverting that commit fixes the deadlock.

Our internal AOSPA builds are running on 4.10 f2fs with that commit reverted.

TL;DR

It’s not [MENTION=631273]Chainfire[/MENTION] 's fault.

You have to ask the kernel developer to fix the issue.

2 methods for the kernel developers

A. Incorporate only the necessary 2 fixes to fix loopback images :

https://git.kernel.org/cgit/linux/k...y&id=0d5ed69805ee57d7b416c4a6b47c3b67284db105

https://git.kernel.org/cgit/linux/k...y&id=7a895023cc2c06c08a6cccb71e112255eb0837ee

B. If you want to upstream f2fs to the latest 4.10, revert this to avoid deadlock :

https://git.kernel.org/cgit/linux/k...y&id=de62dad6f502c67fd01b5c0b1f7f242836ce90d0

(A little credit would be appreciated, as it took me a frustrating month to bisect this)

Thanks.
[SuperSU] lordmago:
It's written in SuperSU app, wether it's installed systemless or not.
[SuperSU] mekayzer:
Man you are the boss
[SuperSU] Chahk:
Deleting /data/su.img resolved the bootloop for me. Thanks!
[SuperSU] veez21:
Well, this sums up almost everything. Probably a "smoother" sailing for devs and the other guys from now on.
[SuperSU] djb77:
Thanks for this info, I'll look into it :)
[SuperSU] theoverseer:
Can anyone shed any light on why my Shell commands within Tasker are no longer working in the two recent SR builds?
[SuperSU] chipiko:
Thank you for the information. I will remain at the current version. But TWRP can delete some applications that came with your phone? Where are we all searched through TWRP? Thank you !
[SuperSU] RenderBroken:
Your hard work neither goes unnoticed nor is it not appreciated. Thanks for all you do. Thanks for the information. This resolves the issue I was having with Upstream F2FS.

I know devs can be under appreciated and under funded for that matter. I donated without reservations.

34U15922V7690451X

Kind Regards,

Zachariah
[SuperSU] grep_i:
Thanks[emoji1]

I love your work and a lot of others love your work too.

After two days of struggling to get things working with f2fs filesystem I found your post a nice and detailed piece about f2fs which if I should have known this before testing (I would not even tried it then).

Now I know why I did not get it to work easily and reverted back to ext4 because it was not possible to root properly the root send to come and go it's not stable.

Also could not boot up normally all the time, sometimes it booted to full system keeps working for 30 second to a minute and then bootloops go to full system again and on and on.

So after formatting /data and /cache to f2fs it automatically reformats /cache back to ext4 during the flashing of the ROM (in my case Nexus 5 stock ROM December 2016 patch level) but not /data that partition stays f2fs.

Also restoring files back to f2fs did not seem to work it complains about the destination not being ext4 and stops, in my testing it did react like that, maybe I did something wrong there but I would not know for sure.

For now I stay out of the f2fs business as it does not seem to be full grown to me.

Keep up the good work,

Peace and respect
[SuperSU] dahawthorne:
People, can I make a plea for a bit of common sense when replying. At least 6 people have copied arter97's entire long post, completely unnecessarily, which means that we have to spend more time scrolling than reading.

Copy only the part to which you're replying, and if it's a "thank you" then even that is unnecessary.
[SuperSU] anshumandash:
I too have the same question as above. Also any link to a working twrp on N4?
[SuperSU] Laurentius26:
Hi Chainfire,

No problems on Nexus 5 with stock Lollipop and latest Supersu v.2.27 beta.

Thank you. :)
[SuperSU] fonephanatic:
No, it should not break root
[SuperSU] occtec:
I am lead to believe otherwise. Isn't the latest beta for stock kernel only for test & report??
[SuperSU] Srandista:
No, you got that wrong. Chainfire was asking people to test it on stock, to verify, if root works on completly stock devices without need to change kernel. But of course its still working with custom kernels as well. My Nexus 7 is completly stock, but my Nexus 5 have franco kernel, an its working with 2.27 without any problem too.
[SuperSU] occtec:
Well that's fantastic news, thanks for clarifying. So if I'm on Franco do I need to flash stock kernel first?
[SuperSU] Srandista:
No, you don't. Just install SuperSU straight from TWRP and you are good to go ;)
[SuperSU] occtec:
Awesome, thanks for your help!
[SuperSU] chiwou:
Hi,

currently running Rastapop on my N5 but after I installed the latest beta 2.27 the SuperSU app is gone from the App Drawer.

Is there a way to "restore" the shortcut?

Thanks and take care

-Chris

PS: with the latest beta Helium runs fine on Lollipop
[SuperSU] scoobyjenkins:
If you have Nova Launcher, you can long press on a home page, select shortcuts, then activities and scroll down to SuperSU, that will put a shortcut to the app on the home screen.

Tapatalked that shiznit.
[SuperSU] Gustave17:
Not sure, but with RastaPop, Shortcut isn't in settings?
[SuperSU] chiwou:
Yeah ? currently using Google Launcher, but I try Nova just to look if it's hidden too.

No couldn't find it in settings either

---------- Post added at 11:29 AM ---------- Previous post was at 11:23 AM ----------

OK found the issue, I changed the icon to the old SuperSU one.

Restored to the default one and everything is okey dokey ?
[SuperSU] Ja_som:
I only want to report, that 2.27 is working without any issue on my Flo with complete stock Android 5.0

Thank you Chainfire, your apps are great ;)
[SuperSU] Mr.Jay:
Anyone?

Sent from my Nexus 5 ?
[SuperSU] kong:
The only way to know is to create a backup and try it yourself.
[SuperSU] Shiningbro:
Works also great with self compiled CM12 Nightly´s. :)
[SuperSU] relevant_placeholder:
The red overlay you're mentioning is astronomer mode, not night mode.
[SuperSU] svarte:
Nexus 5.

Flashed boot.img then the beta.

Wakelock Detector now works fine.
[SuperSU] albert_htc:
Can I flash my kernel using flashify ?

Sent from my Nexus 7 (2013) KitKat 4.4.4
[SuperSU] Chainfire:
CF.lumen can do both these things ... :)
[SuperSU] Pkt_Lnt:
Only you can provide insight by running a logcat while running your tasks and then post a link to it here. No one else can see into your phone from remote. ;)
[SuperSU] theoverseer:
this is the error within tasker :

17.54.23/E Run Shell: ->

17.54.23/E Run Shell: ->

17.54.23/E Run Shell: ->

17.54.23/Shell runBackground su

svc data disable root: false timeout: -1

17.54.23/Shell start process-thread ID 104

17.54.23/E add wait type Shell1 time 2147483647

17.54.23/E add wait type Shell1 done

17.54.23/E add wait task

17.54.24/E Error: 137
[SuperSU] Strephon Alkhalikoi:
[MENTION=6161558]dahawthorne[/MENTION]: Common sense is uncommon.
[SuperSU] ryankabir:
I'm surprised such a common yet untitled issue is not getting more hits. Anyway - I was definitely trying to figure this exact query out and you have given the explanation. TY!
[SuperSU] dahawthorne:
And you needed to add a seventh copy of this long post because...?

[MENTION=2807229]Strephon Alkhalikoi[/MENTION]

"Common sense is uncommon."

You got that right... :)
[SuperSU] veez21:
I "

" a part of the quote. Does that still count? :laugh:
[SuperSU] dahawthorne:
As long as I don't see it and avoid wasting time scrolling through most of a page to see what you've commented, that works for me... :)
[SuperSU] ashyx:
[MENTION=4898097]arter97[/MENTION] is more than enough. No need to requote.
[SuperSU] veez21:
Yeah, figured that much after I quoted him :silly:
[SuperSU] KatariaMax:
hello how to know if root and busybox are installed systemless
[SuperSU] Badger50:
Most all of the custom roms already have busy box built in. However, you can always install it if need be. Pretty much all of the rooting options are systemless now a days.

Sent from me :)
[SuperSU] Pkt_Lnt:
Look in the app.
[SuperSU] KatariaMax:
Hello i uninstalled and reinstalled and now i get this View attachment 4000315

so i am guessing root is systemless now i am on samsung romand have already installed wanam xposed to change into systemless do i need to wipe data
[SuperSU] Pkt_Lnt:
Why are you guessing when it tells clearly and explicitly that it is systemless?
[SuperSU] grep_i:
Little bit exaggeration of your side, this is the 3th all the rest are with spoiler or hide tags those people used common sense and there are more of them than of the long posts so in this particular case:

"Common sense is common "[emoji56]
[SuperSU] bdwilk:
"Hide" doesn't work on XDA labs so we see them all. Just saying.
[SuperSU] napetost:
Can I flash the zip by using xbin mod?
[SuperSU] dahawthorne:
[MENTION=6952047]grep_i[/MENTION] : " all the rest are with spoiler or hide tags"

As Bdwilk says, the entire post appears on XDA Labs, which is where I was reading the forum. I'm sure spoiler or hide tags have some sort of purpose, but to my mind if you want to hide something then the simple way is not to post it, right...? :)

I'm making a general point about the thoughtless cluttering of all threads, not just this one. We all know that almost every thread has pointless copies of posts we've already read. The proper way to respond to a post is by referencing the point to which you're replying (as I've done above), not copying the entire post, which is a lazy and inconsiderate action disrespecting the entire community.
[SuperSU] grep_i:
Maybe it is time for XDA to consolidate to one app or one set of working instructions one can not keep track of what works in one app and what not before they post something, everyone is always posting from the perspective from the app one is using theirselves in my case XDA premium v5 and the tags do work in there.

This is how my post looks like for me:

View attachment 4000491
[SuperSU] Chainfire:
This should be fixed next update. If it isn't, do let me know.
[SuperSU] baltics:
deleted
[SuperSU] Uqbar:
Silly question.

How can there be a v2.79 SR2 that's newer than v2.79?

Which one to use?
[SuperSU] corkiejp:
See the changelogs

SR= Service Release = New naming scheme for betas
[SuperSU] Uqbar:
2

Changelog seems clear somehow.

Versioning schema is not, to me at least.

But my question still holds: which one to use?

P.S. You versioning schema is rather uncommon if not counterintuitive, though.
[SuperSU] corkiejp:
[MENTION=1966251]Uqbar[/MENTION] Which one to use will depend on device and android version.

Stick with stable release 2.79 if your unsure.

If on 7.1.1 then the 2.79-SR2 has some changes that apply to that.
[SuperSU] Uqbar:
Thanks. I am on Oneplus 3T with CM13/v6.0
[SuperSU] grep_i:
I don't know what you say, but this can be checked inside the apps,

See screenshots

SuperSU app: if the option under system is grayed out you're systemless

View attachment 4001410

BusyBox app: (if it says it is installed in folder (/su/(x)bin)) you're systemless

View attachment 4001327
[SuperSU] grep_i:
That is another root not related to the one of this forum.

It is called

CM root

and to my knowledge it is not systemless.

In this thread we talk about Chainfire's && CCMT SuperSU also known as

SuperSU
[SuperSU] shoey63:
The service realeases are basically betas for the next stable version. ie: 279 SR2 could be considered 280 Beta 2. Use stable unless there is something in the SR changelogs that try to address an issue your device/rom may be having on the stable track.
[SuperSU] veez21:
And service release makes it sound cooler
[SuperSU] Pkt_Lnt:
And that is what is important. For you phone and options to look and sound cool. :rolleyes:
[SuperSU] Elanza_48:
Hi

I'm gettiing this error while converting any userapp to system app.

Please help.

Running AospExtended rom v3.0 (7.1.1)with superSu v2.79 sr2 (same using the 2.79)

Even same After mounting the system partition to rw manually.

Also facing same while using solid explorer.

I have no idea is that related to superSu or not. !!
[SuperSU] RandomPooka:
Is it seriously that difficult to grasp that a service release number is exactly like adding a decimal place to a versioning number? Android 7.0.0 to Android 7.0.1 is analagous to SuperSU 2.79 to SuperSU 2.79-SR1
[SuperSU] jcmm11:
Toybox problem. The following will NOT work

mount -w -o remount /system
mount -o remount,rw /system

The following will work

mount -o rw,remount /system

If BusyBox is installed with the proper symlinks you can delete /system/bin/mount and force the BusyBox version to be used, which should allow everything to start working again.
[SuperSU] Elanza_48:
It was the error shown by the link2sd apk while coverting greenify to system app.

And if so then can i use the busybox smart install and rebuild all the symlinks ?
[SuperSU] Devilix:
Hi, somebody know if there is any chance to flash SuperSu on GT-I9100 with CyanogenMod 13?

After flash the zip file, i get always bootloop... :(
[SuperSU] jcmm11:
Assuming you're talking about Stericson's version just don't use the clean install since it won't duplicate existing applets. You just have to make sure the mount applet is created in the BusyBox install. You may already have a BusyBox version with that applet, since most custom ROMs include a BusyBox version.

Using a terminal emulator use "which mount" after deleting /system/bin/mount to ensure you're pointing at the BusyBox version. Then test it to make sure it works.
[SuperSU] shoey63:
SuperSu only works on standard Android boot images. Old Samsung devices like yours (and Note1) do not follow that format and are thus incompatible.
[SuperSU] Elanza_48:
tnx,I got it fixed.
[SuperSU] Devilix:
I don'n know if this is exact... Because, with Resurrection Remix rom SuperSu works fine flashed in "system mode".

And RR is cyanogenmod based, so i'm wondering why, on pure cyanogen i get that... :(
[SuperSU] gothicVI:
Personally I never had issues with SuperSU on my old Samsung Galaxy Ace 2 back then running cm. So I'd give it a shot.

Gesendet von meinem Moto G 2014 LTE mit Tapatalk
[SuperSU] AndDiSa:
[MENTION=631273]Chainfire[/MENTION] I am having some issues with SuperSU 2.79 and Android AOSP 7.1.1 on Grouper. Strange thing is, it depends much on the kernel (probably kernel size). In the installing log I found the following message:

...
- Applying hex patches
sukernel v2.79 (ndk:armeabi-v7a) - Copyright (C) 2014-2017 - Chainfire & CCMT

Loading from [/tmp/supersu/common/hexpatch] ...

Loading from [/sutmp/boot.img] ...

[replace] [49010054011440B93FA00F71E9000054010840B93FA00F7189000054001840B91FA00F7188010054] [A1020054011440B93FA00F7140020054010840B93FA00F71E0010054001840B91FA00F7181010054]

- Flashing boot image
dd: writing '/dev/block/mmcblk0p2': No space left on device
2049+0 records in
2048+0 records out
8388608 bytes (8.0MB) copied, 0.046441 seconds, 172.3MB/s
...

Looks to me as if the patched boot image is too big :(

Trying to boot it leads to a bootloop while the kernel without applying SuperSU is booting up fine.
[SuperSU] osm0sis:
Nope that's a normal message it always displays when zeroing the partition prior to writing. Although it should show the dd records output again for the actual write.
[SuperSU] AndDiSa:
[MENTION=4544860]osm0sis[/MENTION] Exactly, that's my concern, too. It looks to me as if the patched image is 2049 blocks but partition sisze is only 2048. Nevertheless the original size of the boot image has only around about 6.4 MB ...

Edit: probably it's not the size of the kernel and SuperSU, but gcc-4.9 which is causing problems
[SuperSU] Elanza_48:
Sir

Again I'm facing an issue.

When I smart installed the busybox to /su/xbin with all symlinked then when I deleted the mount file from /system/bin and reboot the device then the superSU stops to work prompting binaries are not installed and can't be updated but same after reflashing the supersu.

Again when I install the binaries to /system/xbin following the same the Substratum gives error while compiling the layouts.

Please help !!
[SuperSU] thisisevilevil:
Thanks for the SR2-SuperSU-v2.79-SR2-20170103215521.zip file - I flashed an old version of SuperSU (2.48) on my 7.1.1 rom on my galaxy S4 9506, which caused my device to be stuck in the boot process. After flashing SuperSU 2.79 from recovery it solved the issue.
[SuperSU] steve51184:
Without reading 885 pages is it s known problem/bug that sr2 bootloops a OnePlus 3?
[SuperSU] jcmm11:
Not sure what's happening. It works for me. Only thing I can suggest is to recreate the link in /system/bin and live with it. You can always manually make apps into system apps if that's the only issue. To recreate the link (you can do this from TWRP terminal if su stopped working)

ln -s /system/bin/toybox /system/bin/mount

Make sure system is mounted rw.
[SuperSU] osm0sis:
f2fs? Will need to be fixed in your kernel.

suhide? Outdated.
[SuperSU] steve51184:
I use Boeffla beta 12

And yes suhide is outdated but it's the only option I have to pay Pokemon go on a rooted device other then ones that binclude losing xposed and that ain't gonna happen lol
[SuperSU] jcmm11:
And suhide will continue to bootloop any device with Nov+ security patches until/unless it's updated. You may want to look into rootswitch instead, at least for the moment (Google is your friend).
[SuperSU] steve51184:
Bro I know all​ this x 10 but those are not the question I am asking

I'm short my phone works perfectly but only with SuperSU 2.7.9 works perfectly but 2.7.9 SR2 doesn't
[SuperSU] napolionnardo:
Hi, [MENTION=289094]chin[/MENTION]fire. The reason for this message is to ask for your help. I told you, I installed a rom called Nemesis N7 on my samsung s5 g900h device, at first it was fine, but when installing the latest version of supersu sometimes it turns me off only and the only way to turn it on is to remove the battery and then to press the Porpoises to turn it on. If you can help me please From already thank you very much.

---------- Post added at 09:59 PM ---------- Previous post was at 09:56 PM ----------

Oh, I forgot to tell you that I installed several applications of the S7 Nougat
[SuperSU] corkiejp:
[MENTION=7520878]napolionnardo[/MENTION] Who is "chinfire" and why are you tagging him in this thread?
[SuperSU] Chainfire:
2.79 SR3 is out - https://plus.google.com/+Chainfire/posts/27xToSqi5em - please give it a test flash on your devices.

Let me know if bootloops are/aren't fixed for your devices!
[SuperSU] FReaX908:
SR3 fixes bootloop for me :good: SR1/SR2 always bootloops

I am on n6 pure Nexus mm.

Thank you for the great work!
[SuperSU] corkiejp:
Successfully flashed SR3 on Redmi Note 3 (Kenzo) - xiaomi.eu 7.1.12 and Nexus 9 (7.1.1).

Using flashfire on nexus 9, the supersu app got removed after the flash, installed it from the common folder.
[SuperSU] rikiki81:
Hello!! Anyone tested it on Huawei P9 With Nougat onboard??
[SuperSU] napolionnardo:
Well, I'll do that. Thank you very much. Now I'm going to install this version. A great pleasure to have someone like you.
[SuperSU] lordmago:
HTC10, twrp3.0.3-unofficial, 2.28.401.9 fw, leedroid rom R37, no bootloops
[SuperSU] grep_i:
OPO 3 isn't that the only device that had the f2fs already patched in kernel and thus be usable ?
[SuperSU] vandyman:
SR3 is working well on my Nexus 5X with stock 7.1.1 and FK.

Sent from my Nexus 5X
[SuperSU] gothicVI:
Works great on thea (moto g 2014 LTE) running cm13. Thanks for your work [MENTION=631273]Chainfire[/MENTION]

Gesendet von meinem Moto G 2014 LTE mit Tapatalk
[SuperSU] Einwod:
Why don't you make a backup and try it yourself?
[SuperSU] SimplyCity:
[MENTION=631273]Chainfire[/MENTION], you are magician! Sammy S7E 935f, newest N DPLT based Echoerom. Your newest SR3 not even makes a single issue, it let me SN pass again! Really appreciate! Good work, veeery good! Thank you very much!

View attachment 4003751

Echoe team member / S7E
[SuperSU] alvintimothyjr:
No issues....Moto4g plus. Running latest RR ROM
[SuperSU] doomscooter:
I have issue 2.79 SR3.

In 2.79 SR2 normally but when i flash 2.79 SR3 in HTC M9 stock rom nougat Devs Edition i cant click grant?

EDIT : i try go back flash 2.79 SR2 n 2.79 still i cant click grant? This happen when i flash 2.79 SR3
[SuperSU] daitalos:
no issues for me..in aosp & stock J5 M6..working fine..thanks
[SuperSU] jcmm11:
Try flushing cache for SuperSU?
[SuperSU] ulxerker:
thanks! works perfect on Nexus 5X with stock Android 7.1.1, as always.
[SuperSU] mekayzer:
Thank you Chainfire.

No bootloops and no more lost of root. OPO3 under elemantal 1.03 and RR Rom.
[SuperSU] abalam:
Does this.also works on 4.1.1 N OPO3?
[SuperSU] ulxerker:
yes, it should.
[SuperSU] abalam:
Ok ... so normal disappears my root automatically, so this problem is solved in N builds with f2fs?
[SuperSU] peeyaj:
Having problem with the SR3 version in Redmi Note 3 Pro, with RR Nougat 5.8.0. After flashing via twrp, SuperSU would ask for a binary update, then when you update the binary, it will fail. Tried it a few times to no avail. However, the weird thing is, SuperSU's toast notification still works. Weird. No problem in SR2.
[SuperSU] leech78:
For some reason, my wifi keeps cutting out on SR3 when I lock the screen. Back on SR2.

Phone's running Christer12's 14.1-20170114 ROM.

Please ignore this.

I was in a part of the house where wifi reception is weak.
[SuperSU] eris23:
SR3 same problem as https://xdaforums.com/showpost.php?p=70219469&postcount=8503 and https://xdaforums.com/showpost.php?p=70382605&postcount=8648 on TugaPower N 13.1 (stable still works)