Clear yes on busybox. Never used tibu, thus no comment on that.unfortunately im prob in the same boat. quick question on magisk - can i use tibu and busybox with magisk? if so, then bye bye supersu
Gesendet von meinem Moto G 2014 LTE mit Tapatalk
[BETA][2017.10.01] SuperSU v2.82 SR5
- Thread starter Chainfire
- Start date
Gesendet von meinem Moto G 2014 LTE mit Tapatalk
unfortunately im prob in the same boat. quick question on magisk - can i use tibu and busybox with magisk? if so, then bye bye supersu
TiBu works fine with Magisk. I use it all the time. There is a busybox Magisk module readily available to download via the Magisk app.
casouzaj
Senior Member
unfortunately im prob in the same boat. quick question on magisk - can i use tibu and busybox with magisk? if so, then bye bye supersu
I have both of them installed in my Sony Xperia Z3 Compact running CarbonROM (BusyBox as a Magisk module, though) and they work great under Magisk v15.1.
awesome! i had read somewhere that magisk and tibu are not compatible. glad to hear that that is incorrect.
EDIT
so here is what i read elsewhere... is this incorrect?
"However, Magisk's built-in root management system will not allow you to modify files on the Pixel or Pixel XL's system partition. This means that certain apps, like Titanium Backup, will not work properly with this root method."
Last edited:
awesome! i had read somewhere that magisk and tibu are not compatible. glad to hear that that is incorrect.
EDIT
so here is what i read elsewhere... is this incorrect?
"However, Magisk's built-in root management system will not allow you to modify files on the Pixel or Pixel XL's system partition. This means that certain apps, like Titanium Backup, will not work properly with this root method."
I'm not sure where that come from, but my app restore from yesterday's ROM install on my Pixel XL (and all of the ones since Magisk has been released for the Pixels back in February/March'ish of last year) beg to differ with the assertion. I build ROMs, so I am constantly having to wipe & perform clean installs. I'd go insane without TiBu.
I can also access and modify/add/delete/change permissions on system files using FX file explorer without issue. Some file explorers do have issues with Magisk & Pixels, that's a known problem, but I've always used FX and it has always worked.
Edit - Added screenshot, works fine on Pixel XL, 8.1, Magisk.
Attachments
Last edited:
so i use tibu to restore/back up app data, other data (texts/phone logs/wifi connections), and freeze system apps. all that is doable via magisk?
Yep. I added a screenshot go my post above of a happy TiBu just taken a minutes ago. It has full functionality. EDIT - It has full functionality *as far as I can tell*. I have never backed up anything besides apps & app data. I have frozen system apps without issue though.
As a side note, I want to be clear that I would NOT be having this conversation if chainfire were still developing SuperSU. The only reason I am responding in what would otherwise be a rude intrusion into this thread is because (it appears) the company that bought it isn't interested in supporting it at this time. Mods please feel free to move or delete my posts if they aren't kosher.
Last edited:
Ibuprophen
Senior Member
Thank you very much @hokiealumnus
It appears that CCMT (aka @SuperSU Release on the forum) won't support anything on the xda-developers forum at all.
Please correct me if I'm wrong @Chainfire but, based on what I've seen, I really don't believe that CCMT realizes that the xda-developers forum is where SuperSU had gotten its start and had grown to where it is now.
CCMT also should take under consideration how strong of a community that the xda-developers is and can potentially impact the SuperSU in a negative way if they continue to ignore the primary fan base here.
I can also understand where Chainfire is coming from too. I've got a feeling that he's tried (possibly on multiple occasions) to let CCMT know this. As always, Chainfire still has my support since he's always provided excellent support to the end and its CCMT that has lost my support.
I, personally, will continue to use SuperSU as long as it still works for me but, like a bad habit, I'll stop as soon as it no longer works for me.
I just feel bad for those members here that are having issues with it on their devices.
Anyways... Have a Happy New Year Everyone!!!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
It appears that CCMT (aka @SuperSU Release on the forum) won't support anything on the xda-developers forum at all.
Please correct me if I'm wrong @Chainfire but, based on what I've seen, I really don't believe that CCMT realizes that the xda-developers forum is where SuperSU had gotten its start and had grown to where it is now.
CCMT also should take under consideration how strong of a community that the xda-developers is and can potentially impact the SuperSU in a negative way if they continue to ignore the primary fan base here.
I can also understand where Chainfire is coming from too. I've got a feeling that he's tried (possibly on multiple occasions) to let CCMT know this. As always, Chainfire still has my support since he's always provided excellent support to the end and its CCMT that has lost my support.
I, personally, will continue to use SuperSU as long as it still works for me but, like a bad habit, I'll stop as soon as it no longer works for me.
I just feel bad for those members here that are having issues with it on their devices.
Anyways... Have a Happy New Year Everyone!!!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
I agree completely, but it is a shame for the people that paid for the pro su app like myself. I paid for the app for the support.Thank you very much @hokiealumnus
It appears that CCMT (aka @SuperSU Release on the forum) won't support anything on the xda-developers forum at all.
Please correct me if I'm wrong @Chainfire but, based on what I've seen, I really don't believe that CCMT realizes that the xda-developers forum is where SuperSU had gotten its start and had grown to where it is now.
CCMT also should take under consideration how strong of a community that the xda-developers is and can potentially impact the SuperSU in a negative way if they continue to ignore the primary fan base here.
I can also understand where Chainfire is coming from too. I've got a feeling that he's tried (possibly on multiple occasions) to let CCMT know this. As always, Chainfire still has my support since he's always provided excellent support to the end and its CCMT that has lost my support.
I, personally, will continue to use SuperSU as long as it still works for me but, like a bad habit, I'll stop as soon as it no longer works for me.
I just feel bad for those members here that are having issues with it on their devices.
Anyways... Have a Happy New Year Everyone!!!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Sent from my Pixel 2 using Tapatalk
I use tibu with Magisk for the past year just fine. There is busybox module within Magisk you can simply download and useunfortunately im prob in the same boat. quick question on magisk - can i use tibu and busybox with magisk? if so, then bye bye supersu
---------- Post added at 05:16 AM ---------- Previous post was at 05:14 AM ----------
I restored my nexus 6p tibu backup on a pixel just fine nothing to worry about
Well, Chainfire never let alone people who only have the free app. I also bought the pro version but only like a way to say thanks for all his support here.
I will use it until stop working because it's the most stable option at the moment.
likewise - i shouldnt be having a magisk discussion in a supersu thread. only because of the current lack of support for supersu from the new owners. and other (semi?)noobs like myself can at least know other options and compatibility
Time passes and things change. I paid for the premium but feel like it was a bargain over the years. We have an alternate that works fine, magisk, and I for one am thankful for that. Chainfire did a great job time will tell if CCMT continues to support supersu or it fades into the past.
I have done the same as you to say thanks. But I was making a point. Do not buy the paid version at this time, you will get what?
What do you get for the Pro version as of right now..??
Honestly, all the apps that I use from Chain fire are paid apps. Example ; Flashfire.
All the apps that I use on system are paid apps, supported the developer..
Examples ; Titanium Pro, Busy box pro, Root explorer pro,..........
Sent from my Pixel 2 using Tapatalk
Interestingly CCMT has link to XDA at the bottom of the SUperSU official website pages, but apparently they have no intent (so far) to participate or even read the discussion.Thank you very much @hokiealumnus
It appears that CCMT (aka @SuperSU Release on the forum) won't support anything on the xda-developers forum at all.
Please correct me if I'm wrong @Chainfire but, based on what I've seen, I really don't believe that CCMT realizes that the xda-developers forum is where SuperSU had gotten its start and had grown to where it is now.
CCMT also should take under consideration how strong of a community that the xda-developers is and can potentially impact the SuperSU in a negative way if they continue to ignore the primary fan base here.
I can also understand where Chainfire is coming from too. I've got a feeling that he's tried (possibly on multiple occasions) to let CCMT know this. As always, Chainfire still has my support since he's always provided excellent support to the end and its CCMT that has lost my support.
I, personally, will continue to use SuperSU as long as it still works for me but, like a bad habit, I'll stop as soon as it no longer works for me.
I just feel bad for those members here that are having issues with it on their devices.
Anyways... Have a Happy New Year Everyone!!!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Ibuprophen
Senior Member
The xda-developers information for the SuperSU on the Play Store is just some residual information that was placed when Chainfire had posted the Free and Pro there.
I'm only assuming that Chainfire had left it unchanged, probably, with the understanding that CCMT would be including the xda-developers for support and information. I doubt Chainfire can change it now that it's transferred to them.
I had paid for the Pro version not long after the Pro was placed on the Play Store and the only thing that I'm satisfied with regarding my paying for it is both that it was not a ton of money and also that my purchase went to Chainfire (and including a few donations over time).
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Glad to see I'm not the only one still hanging on lol! And, I paid for pro also....Thank you very much @hokiealumnus
It appears that CCMT (aka @SuperSU Release on the forum) won't support anything on the xda-developers forum at all.
Please correct me if I'm wrong @Chainfire but, based on what I've seen, I really don't believe that CCMT realizes that the xda-developers forum is where SuperSU had gotten its start and had grown to where it is now.
CCMT also should take under consideration how strong of a community that the xda-developers is and can potentially impact the SuperSU in a negative way if they continue to ignore the primary fan base here.
I can also understand where Chainfire is coming from too. I've got a feeling that he's tried (possibly on multiple occasions) to let CCMT know this. As always, Chainfire still has my support since he's always provided excellent support to the end and its CCMT that has lost my support.
I, personally, will continue to use SuperSU as long as it still works for me but, like a bad habit, I'll stop as soon as it no longer works for me.
I just feel bad for those members here that are having issues with it on their devices.
Anyways... Have a Happy New Year Everyone!!!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
I'm sorry guys but after reading this study:
https://www.reddit.com/r/Android/comments/54xdmp/ccmt_who_exactly_are_the_owners_of_supersu/
I got cold feet and switched to Magisk (so far without any problems - at least until the next OTA Google update). Supersu still does not work on my Pixel.
Besides, I don't trust secretive companies to have access to the root of my phone. The fact that the company in question seems to be in secretive country (no offense) and doesn't give a $#1t for the customer base for a month does not help either. Sorry - too many cons to stay even if chainfire comes back and fix SuperSU one last time before walking away for good.
BTW I also have SuperSU Pro for a long time and don't regret paying for it as the money went to chainfire.
Happy New Year everybody!
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
2533This thread is for SuperSU releases that are still in testing, and are not yet available through the Play store. The main thread for stable SuperSU releases is located here: https://xdaforums.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703. The changelogs are in the old release thread.
Please keep track of the version numbers in the thread titles, as the latest test release may not always be newer than the latest stable release.
The latest test release is:
SR5-SuperSU-v2.82-SR5-20171001224502.zip
RELEASE NOTES
That is a recovery flashable ZIP (I recommend FlashFire or TWRP). If you want to install via APK, it is also present inside the ZIP, in the common folder.617unSU Script zip -- Unroot with ease!
Originally this was a little zip to help with uninstalling the old system-modifying version of SuperSU. It properly restores all the original files the SuperSU installer backed up (so, file-based OTA friendly!) and removes any files added by the installer/app. I figured other people might find it handy as well so it's attached below. Be aware, if you flashed SuperSU twice mistakenly, the SuperSU installer wasn't written to recognize that and so you've lost your originals; a system.img flash WILL be necessary in your case.
Due to popular demand by the custom ROM community using this to unroot and pass SafetyNet checks/use Android Pay, etc., the script has been expanded to unroot Koush's SuperUser, ROM su binaries, as well as SuperSU Systemless (su.img and BINDSBIN), phh's Superuser (which is also systemless), and now Magisk and LineageOS addonsu.
Note: To completely remove all traces of the systemless roots, you still need to flash a different, unrooted boot.img, likely the default one that came with the ROM. You can extract it from the ROM zip (or a /data/stock*.gz backup from your root solution before flashing unSU) and flash it using TWRP's awesome "Flash Image" functionality, or, "dirty flashing" the ROM zip should also work.
My development work on my many projects comes out of my free time, so if you enjoy this project or anything else I've done on xda, please consider sponsoring my ongoing work using my GitHub Sponsors profile. For a one-time donation you can hit the donate link from my profile. Thank you for your support!
P.S. If you found this handy then please check out my Odds and Ends thread for more flashable goodness.
Previous download counts: 58944; 158506; 59850; 226692578f2fs 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 @Chainfire '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.189@ everyone
This post is likely an important one going forward, it could be the answer to various issues people have on 6.0 related to /system.
The conversation below pertains specifically to Nexus 6 @ 6.0.1, which has an almost full /system, but I'll bet the issue exists on all Nexus devices.
So after some further investigation, something pretty odd is going on.
ext4 (the filesystem) has various types of reserved blocks.
I suspect the tools on booted Android do not count one type of reserved block. Indeed, when you use "df" utility (both toolbox and toybox), it shows 15mb or so free. Using the same "df" utility in recovery (busybox) shows 0b free. It does show that not all blocks are in use, but the remainder is likely reserved.
If you use a root shell on either booted Android or in recovery, trying to write contents to a new file in /system will fail. To make matters worse, file creation succeeds, but writing content does not, so you end up with a 0 byte file. You need to delete a few extra megabytes of files, before you are able to write even 1 byte to a new file!
Many editing tools remove the old file and write a new file at the same spot rather than truly editing a file. I'm not sure if the latter has any chance of succeeding, but the former would definitely fail in this scenario.
While the issue is understandable technically, it is likely to trip up a lot of tools, as the error is generated at the least expected moment.
This issue is a magnet for file corruption and bootloops. Beware this issue when modifying anything on /system!
DEVS Immediate hunch is that the difference is explained by usage of struct statfs's bfree vs bavail member.
TL;DR Yes, even though TiBu and whatever other tool are showing you megabytes free, adding/modifying files is likely to give unexpected results on a (near-)full /system partition, and an unlucky edit can definitely prevent the device from booting! Can't give you exact numbers right now, but before modifying files or adding files to /system, I would recommend deleting files until you have at least 30-ish mb free.
