THIS PROJECT IS NO LONGER SUPPORTED.
# F2FS Loopback Bug Workaround
## README.md
### Copyright (C) 2017-2018, VR25 @ xda-developers
#### License: GPL v3+
---
#### DISCLAIMER
This software is provided as is, in the hope that it will be useful, but without any warranty. Always read/reread this reference prior to installing/upgrading. While no cats have been harmed, I assume no responsibility under anything which might go wrong due to the use/misuse of it.
A copy of the GNU General Public License, version 3 or newer ships with every build. Please, read it prior to using, modifying and/or sharing any part of this work.
To prevent fraud, DO NOT mirror any link associated with this project; DO NOT share ready-to-flash-builds (zips) on-line!
---
#### DESCRIPTION
Some kernels from devices with F2FS-formatted data partition (i.e., Motorola) have a bug which prevents loopback devices (.img files) from being mounted read-write. This limits systemless modifications that can otherwise be achieved with Magisk.
This module works by moving magisk.img to the cache partition (EXT[2-4]-formatted) and linking it to its actual location (i.e., /data/adb/magisk.img). The other half of the process consists on automatically recreating magisk_merge.img shortly after boot and handling it the same way as magisk.img.
With this workaround, a patched kernel is dispensable.
Cache partition's size is essentially the only limiting factor -- and that's pretty much self-explanatory.
/cache/magisk_.img is automatically backed up to/data/adb on boot (only if modified) & restored on install. Thus, whenever cache is wiped, magisk_.img and its respective symlink can easily be restored by simply reinstalling the module.
---
#### PRE-REQUISITES
- Magisk v15+
- F2FS-formatted data partition
- EXT[2-4]-formatted cache partition
---
#### SETUP STEPS
Fist time
- Install from custom recovery as a regular flashable zip.
Upgrades
- Install from Magisk Manager or custom recovery.
- Reinstall after cache wipes to restore magisk.img backup.
---
#### NOTES/TIPS
Always install large modules from custom recovery only. In fact, I recommend installing every module from recovery if your device's cache partition has a very small size (i.e., only a few Megabytes).
To revert changes, uninstall the module, boot into custom recovery and delete </data/adb/magisk.img> & <magisk.img.bkp>. Lastly (while still in custom recovery), move </cache/magisk_.img> to </data/adb/magisk.img>.
Updates and reinstalls can be carried out from Magisk Manager as well.
---
#### ONLINE SUPPORT
- [Facebook Support Page](https://facebook.com/VR25-at-xda-developers-258150974794782/)
- [Git Repository](https://github.com/Magisk-Modules-Repo/f2fs-loopback-bug-workaround/)
- [XDA Thread](https://forum.xda-developers.com/apps/magisk/guide-magisk-official-version-including-t3577875/)
---
#### RECENT CHANGES
**2018.10.9 (201810090)**
- Bug fixes
- Latest module template, with added sugar.
- Magisk 15-17.2 support
- Updated documentation
**2018.9.2 (201809020)**
- Improved compatibility
- Major optimizations
- Updated documentation
**2018.8.1 (201808010)**
- General optimizations
- Striped down (removed unnecessary code & files)
- Updated documentation
**2018.7.24 (201807240)**
- Fixed modPath detection issue (Magisk V16.6).
- Updated documentation
Works with stock roms as well ?
My cat lost two and half lives because of this thread. Sadly, the disclaimer is in order, so I can't sue.
Is this for Nougat or Marshmallow?
does this work on nougat update or only on MM?
Can someone please confirm if it will work on retin channel with dual sim... I am running stock nougat... Will it work or does it only work on MM rom...
Anybody know how to fix notifications without breaking safety net?
VR25 said:
DISCLAIMER
Not taking responsibility for any thermonuclear war or cat harm. Do it at your any risk.
NEEDED
[Unlocked Bootloader] https://youshouldknowthisbynow.com
[Latest TWRP] https://forum.xda-developers.com/mo...recovery-unofficial-twrp-moto-z-play-t3495629 credits @Alberto97
[Latest FSFS patched Kernel] https://forum.xda-developers.com/moto-z-play/development/kernel-stock-kernel-f2fs-patched-t3546732 credits @tomparr
[Latest Magisk zip] https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 credits @topjohnwu
[Latest Magisk Manager app] https://play.google.com/store/apps/details?id=com.topjohnwu.magisk&hl=en credits @topjohnwu
PROCEDURE
0. reboot bootloader
1. fastboot boot twrp.img
2. adb sideload fsfs patched kernel
3. adb sideload magisk
4. reboot system
5. install magisk manager from play store
6. reboot bootloader [yes, again]
7. fastboot boot twrp.img [yes, again]
8. adb sideload magisk [yes, again]
9. reboot system [yes, ag... you get the point]
10. open magisk manager settings, enable "magisk hide"
11. reboot, done
Click to expand...
Click to collapse
Works like a charm.
I however did not temporarly boot into TWRP, I flashed it as such.
mhp1995 said:
does this work on nougat update or only on MM?
Click to expand...
Click to collapse
I'm on Android 7.0 Nougat.
Thanks!
Erwin
fortunz said:
My cat lost two and half lives because of this thread. Sadly, the disclaimer is in order, so I can't sue.
Click to expand...
Click to collapse
Hopefully your cat is ok now
jjdavis699 said:
Is this for Nougat or Marshmallow?
Click to expand...
Click to collapse
mhp1995 said:
does this work on nougat update or only on MM?
Click to expand...
Click to collapse
mhp1995 said:
Can someone please confirm if it will work on retin channel with dual sim... I am running stock nougat... Will it work or does it only work on MM rom...
Click to expand...
Click to collapse
It should work on both Marshmallow and Nougat, as long as you pick the appropriate kernel for your system version (6 or 7). @mhp1995, I don't think the software channel matters. It should work across all (retus, retin , reteu, etc.).
xxBrun0xx said:
Anybody know how to fix notifications without breaking safety net?
Click to expand...
Click to collapse
No idea at this point, man. I've never had to fix mine. Perhaps only some people have it...?
@erwin, I chose not to touch the stock recovery to keep OTA installations straightforward. Easy for everyone.
one question... if i wanted to install viper4android and xposed framework, should i download it from the magisk download tab or shud i flash them manually via TWRP? thanks
mhp1995 said:
one question... if i wanted to install viper4android and xposed framework, should i download it from the magisk download tab or shud i flash them manually via TWRP? thanks
Click to expand...
Click to collapse
There are specific versions of these modified for systemless root. DO NOT install the standard versions. You should follow the instructions given in Magisk Manager app to download and install.
VR25 said:
There are specific versions of these modified for systemless root. DO NOT install the standard versions. You should follow the instructions given in Magisk Manager app to download and install.
Click to expand...
Click to collapse
Ok :good: I think xposed is not available at the moment for nougat ..Its WIP....If possible when the time comes try to include installing xposed via Magisk tutorial in this thread too.... Coming to the posts, u mind if i add this rooting tutorial in my all-in-one thread? Of course credits will be given
mhp1995 said:
Ok :good: I think xposed is not available at the moment for nougat ..Its WIP....If possible when the time comes try to include installing xposed via Magisk tutorial in this thread too.... Coming to the posts, u mind if i add this rooting tutorial in my all-in-one thread? Of course credits will be given
Click to expand...
Click to collapse
Oh, yes the availability... I forgot to mention that. Hopefully a proper Xposed version will be available for nougat very soon. When that happens, I'll update the thread.
About adding the tutorial to your thread... sure, go ahead.
I honestly declare I didn't read whole thread - is this method work for stock Nougat rom - I need root for Titanium Backup only for now , since facebook messenger goes crazy on my new phone MZP :-/ . Or maybe there is a way to restore old conversations ,not restored automatically in Facebook Messenger - anybody knows how to do it ? . On every phone I had I used root for two things mainly - Titanium Backup and to block adds - dns66 do block adds very well without root but , Titanium Backup has no alternative for me .
Just for the records: Magisk 12 release works fine.
@sebx_g1 incredible 2 pages! That are more than 10 postings! Sure nobody can read so much. And nearly all ask or answer your question, but it is just too much ...
tag68 said:
Just for the records: Magisk 12 release works fine.
@sebx_g1 incredible 2 pages! That are more than 10 postings! Sure nobody can read so much. And nearly all ask or answer your question, but it is just too much ...
Click to expand...
Click to collapse
[emoji4] but voting is only 3 works 2 not, so?
Wysłane z mojego XT1635-02 przy użyciu Tapatalka
What is expected to be done for next OTA to work? Just restore Nandroid backup of boot partition and everything should be ready for patchlevel newer than January 2017, right? And afterwards f2fs fixed kernel and Magisk again for having root again of course.
(twrp not flashed, no logo modified, system should be untouched)
---------- Post added at 09:14 PM ---------- Previous post was at 09:11 PM ----------
sebx_g1 said:
[emoji4] but voting is only 3 works 2 not, so?
Click to expand...
Click to collapse
Xposed does not work on Nougat by now. Magisk does. The 2 negative votes you counted referred to Xposed
Anyone have an adblock that works with systemless and passes safetynet? Do we need to check the "enable systemless for adblocks" in Magisk settings?
DNS66 do the same what do adblock, you can use it without root. But yes, there is special version of adblock systemless.
Wysłane z mojego XT1635-02 przy użyciu Tapatalka
Worked fantastically, thanks a lot!
Hi.
I'm trying to install Magisk on a Lenovo Tab 4 8 Plus.
I've unlocked my bootloader and flashed LineageOS 17.1 and GApps.
I've set the tablet up but realised I need to install Magisk. I've downloaded v21.2 zip ( and 21.1 ) and tried flashing them via TWRP. TWRP isn't my default recovery I boot into that first.
In TWRP I'm selecting Install and then the v21.1 or v21.2 zip file. Everything appears OK but I get as far as 'Adding addon.d survival script' and nothing further seems to happen.
Powering off the tablet brings it backup on Lineage OS and nothing has changed.
Any ideas ?
Thanks
Here's Jonny said:
Any ideas ?
Click to expand...
Click to collapse
Perhaps try the patch image method instead:
Installation
The Magic Mask for Android
topjohnwu.github.io
Thanks I'll try that in the morning.
I take it I should be following this: https://topjohnwu.github.io/Magisk/install.html#patching-images
Thanks
Thanks, I've not installed Magisk using the patch.
I'm trying to change my fingerprint using this post HERE
So I've installed Install MagiskHide Props Config and Busybox for Android NDK.
How do I open a terminal to enter the commands ?
Thanks
Just download a terminal emulator from F-Droid or the Play Store.
You've got more instructions on how to use the module in its docs:
MagiskHidePropsConf/README.md at master · Magisk-Modules-Repo/MagiskHidePropsConf
This tool is now dead... Contribute to Magisk-Modules-Repo/MagiskHidePropsConf development by creating an account on GitHub.
github.com
Thanks I had downloaded Termux but didn't realise I needed su first !
Hi,
Issue with: Magisk 22006 and other 22+
Channel: Canary, but also on others
Plattform: Android 6.0 Marshmallow, armeabi-v7a
Device: Samsung Note 4 SM-N910F
UI: TouchWiz
Recovery: TWRP
Magisk_install_log
- Target image: /dev/block/
- Device platform: armeabi-v7a
- Installing: 66e30a77 (22006)
! Unable to check signature
! Installation failed
- I get this log when I try to install Magisk within the Messenger.
- Patching by TWRP with Devik delete works.
- SU requests afterward pop up properly, may be granted, but are not remembered
Issue 1: Magisk (Manager) does not install/patch within the app, creating that signature error
Issue 2: Magisk (Manager) does not detect patched Magisk, shows only n/a
Issue 3: Magisk (Manager) wants to install current Manager though it is installed
Issue 4: Magisk (Manager) does not offer all features to control SU, hide, etc., though Magisk is patched and SU requests working
Done so far without solving the problem:
- uninstalled/reinstalled Manager
- unpatched/repatched stock boot vi TWRP
- repatched Magisk boot-image
Last Version without these Issues:
Magisk 8.0.7 (pre 22)
Please help, its driving me nuts.
leppit said:
Hi,
Issue with: Magisk 22006 and other 22+
Channel: Canary, but also on others
Plattform: Android 6.0 Marshmallow, armeabi-v7a
Device: Samsung Note 4 SM-N910F
UI: TouchWiz
Recovery: TWRP
Magisk_install_log
- Target image: /dev/block/
- Device platform: armeabi-v7a
- Installing: 66e30a77 (22006)
! Unable to check signature
! Installation failed
- I get this log when I try to install Magisk within the Messenger.
- Patching by TWRP with Devik delete works.
- SU requests afterward pop up properly, may be granted, but are not remembered
Issue 1: Magisk (Manager) does not install/patch within the app, creating that signature error
Issue 2: Magisk (Manager) does not detect patched Magisk, shows only n/a
Issue 3: Magisk (Manager) wants to install current Manager though it is installed
Issue 4: Magisk (Manager) does not offer all features to control SU, hide, etc., though Magisk is patched and SU requests working
Done so far without solving the problem:
- uninstalled/reinstalled Manager
- unpatched/repatched stock boot vi TWRP
- repatched Magisk boot-image
Last Version without these Issues:
Magisk 8.0.7 (pre 22)
Please help, its driving me nuts.
Click to expand...
Click to collapse
I am not used to forums, and this is my debut on xda. I just followed Magisk, noticing I am not allowed as a new member to post about at the canary magisk bug reporting there and was redirected to xda.
Since there is no reply so far, did I do anything wrong, do I have to move the topic somehow?
Thanks for help!
leppit said:
Hi,
Issue with: Magisk 22006 and other 22+
Channel: Canary, but also on others
Plattform: Android 6.0 Marshmallow, armeabi-v7a
Device: Samsung Note 4 SM-N910F
UI: TouchWiz
Recovery: TWRP
Magisk_install_log
- Target image: /dev/block/
- Device platform: armeabi-v7a
- Installing: 66e30a77 (22006)
! Unable to check signature
! Installation failed
- I get this log when I try to install Magisk within the Messenger.
- Patching by TWRP with Devik delete works.
- SU requests afterward pop up properly, may be granted, but are not remembered
Issue 1: Magisk (Manager) does not install/patch within the app, creating that signature error
Issue 2: Magisk (Manager) does not detect patched Magisk, shows only n/a
Issue 3: Magisk (Manager) wants to install current Manager though it is installed
Issue 4: Magisk (Manager) does not offer all features to control SU, hide, etc., though Magisk is patched and SU requests working
Done so far without solving the problem:
- uninstalled/reinstalled Manager
- unpatched/repatched stock boot vi TWRP
- repatched Magisk boot-image
Last Version without these Issues:
Magisk 8.0.7 (pre 22)
Please help, its driving me nuts.
Click to expand...
Click to collapse
Dude I am expecring the exact same issue!!
I fresh installed Rom Marshmallow 6.0.1 on an old Tab. + installed TWRP + old Magisk 21.4. And when I update the Manager to v.22. the same error as you describe appear!!!
Magisk_install_log
- Target image: /dev/block/
- Device platform: armeabi-v7a
- Installing: 66e30a77 (22006)
! Unable to check signature
! Installation failed
Did you finally manage to update the manager/ Magisk Root to v.22 ??
...good to know, I am not alone and my message reached somebody.
But sadly not, still hoping, somebody could help us, or I get permission to post the issue at github.
Yes sure reached ))
Why you want be allowed to post on github, sure you can.
Here is a advice about doing so I goted...
Magisk 22+ not detect and/or crashing on android 6.0.1 arm v7a · Issue #4107 · topjohnwu/Magisk
Device: Samsung Galaxy Note 4 Android version: 6.0.1 Magisk version name: 22 Magisk version code: 22006 Magisk 22+ not detect and/or crashing on android 6.0.1 arm v7a Magisk 21.4 works great. but w...
github.com
it was recommended to me to open a new issue case, Did not had time to try to post...
Anyway can of found a "workaround" only install 21.4, and stay quietly there... after all it is an old device + old ROM, and in my case, I dont use it much... What I found out during all my reseachs , flash/unFlash/ Root/ unRoot/ Backup and Restore ( belive me I tried a lot ), is Magisk do not dance well with old arm +old devices + Marshmallow. I respect a lot the work that is being done around it (Magisk), and it is fine on RECENT MODEL/Roms models I mean...
I said that because I had a second pb, with Booting a restored Backuped on this arm device, and OS is Marshmallow + Magisk Root. You may also check about it
RheinPirat said:
saoudien07 said:
No vbmeta disponible, If I am not wrong it is not for Samaung devices....
I tried all possible combination, when I do the backup, I usually Backup everything, exept Cache. Just in case, always possible to choose what everyone want to restore later...
Then when I restore, I restore: System + Data + Boot. I read System Image is no need, I even tried 3 of them:
Restore with System only, stuck on Splash
Restore with System IMAGE , stuck on Splash
Restore with both ticked, also stuck
Currently I am testing Fresh Rom + TWRP + SuperSU Root (old Root), then Backup and sees if the Restore works...
I already installed SuperSU Root ...
If still Restore pb, I ll go with Fresh Rom + TWRP, only, without any Root of anyKind...
Update:
Magisk is guilty of all my headache!!!!
As I said I tried Fresh Rom + TWRP +SuRoot (old Root method).
Then I backuped, clean everything in TWRP + reboot to TWRP, and restore the Backup just made, and it works flowlessly!!
It seems Magisk is not really going well with old arm device, only assumption here, I am no dev.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Solution: Found out that kind of Magisk to be guilty:
I tried a restore of a Backup: Rom + Magisk + Marshmallow, and it stuck on Boot forever, I decribed about it above...
Finally it was not related to Partition being Restored. Tried a Restore of a Backup ( Rom + SuperSU + Marshmallow) and it works fine. Then tried to restore Backup giving problem, and after restore flash Stock Boot of Marshmallow Rom (Obtained from Stock Rom), and if booted fine to OS.
I even tried Restore + unRoot with Magisk Uninstaller 17.01.2021, and it do not help, should be with Stock Boot !!
So my recommendation for this old device/arm/Marshmallow is, to unRoot the device before to do a Backup!!
At least when you will to restore that made backup, you wont have problem to restore it, as I had, please re-Root, is also an additional flash.....
error
Magisk 21.4 will still work for you OK just don't update the manager to 22 build.
everything has changed from 22 onwards to accommodate newer phones where old methods won't work. flash 21.4 zip, boot and install the manager that goes with it. NEVER UPDATE AGAIN!
3mel said:
Magisk 21.4 will still work for you OK just don't update the manager to 22 build.
everything has changed from 22 onwards to accommodate newer phones where old methods won't work. flash 21.4 zip, boot and install the manager that goes with it. NEVER UPDATE AGAIN!
Click to expand...
Click to collapse
lol, that is what I realized about Magisk, anyway I stay on 21.4 and it is fine for me, less headache
...well, thanks so far.
The reason bothered with 22.00 again and again are my banking apps. Even the last one now detects the old Magisk and quits...
But old Magisk at least lets me access its settings.
You have any hope, they will support oöd phones in future releases and fix the bugs?
leppit said:
You have any hope, they will support oöd phones in future releases and fix the bugs?
Click to expand...
Click to collapse
Of course old devices are supported... So far, Magisk supports Android 4.2+ (from the next release Android 5+). As long as bugs are reported properly they'll be looked into and fixed if possible (unless you've been spamming enough to be banned, you should have full access to submitting issues on GitHub, as long as you follow the issue template).
Example:
This issue was fixed in Canary build 22007 that was released just a couple it days ago.
leppit said:
...well, thanks so far.
The reason bothered with 22.00 again and again are my banking apps. Even the last one now detects the old Magisk and quits...
But old Magisk at least lets me access its settings.
You have any hope, they will support oöd phones in future releases and fix the bugs?
Click to expand...
Click to collapse
yep that its why I prefere stay on 21.4, because the settings is fully accessible and operational.
I noted when updated to v.22, Device is still rooted!! App requiring Root are still functional as supposed to with Root presence, but the issue is with the Manager itself. No more access to settings and so on... and of course they are important!!
About Banking apps, and root detecting, what I use to do, is clean everything and start over from zero.
Some would see this as a placebo, but I pass a run of cleaner before to start over, perso I use SD Maid.
Recently , it helped fix me an other issue with an app, even being uninstalled some of its stuff remain on the phone, and everything was removed, Then, new installation, and the app re-work as expected... So maybe give it a try...
About Magisk, as said devs are always doing there best, so a good report of the issue + log, and everythings appropriated, should of course help them fix the issue.
Didgeridoohan said:
bugs are reported properly
Click to expand...
Click to collapse
Hopefully I finally did so (maybe I missed a bot in the preview, but would be nice, if there were a check before you issue, so it wouldn't hav to be closed and reissued again .... or a at least some examples in the advise... how shall I know which is the proper way to present version name and version code...)
Magisk 22101 (22.+) not detected by Manager ("N/A"), but SU still working on Android 6.0 (+) Marshmallow with Samsung Note 4 SM-N910F TouchWiz, armeabi-v7a and other devices · Issue #4174 · topjohnwu/Magisk
Device: Samsung Note 4, SM-N910F, armeabi-v7a Android version: Android 6.0, Marshmallow Magisk version name: f623b98 Magisk version code: 22101 Full Magisk Version Information: f623b98 (22101) (20)...
github.com
leppit said:
Hopefully I finally did so (maybe I missed a bot in the preview, but would be nice, if there were a check before you issue, so it wouldn't hav to be closed and reissued again .... or a at least some examples in the advise... how shall I know which is the proper way to present version name and version code...)
Magisk 22101 (22.+) not detected by Manager ("N/A"), but SU still working on Android 6.0 (+) Marshmallow with Samsung Note 4 SM-N910F TouchWiz, armeabi-v7a and other devices · Issue #4174 · topjohnwu/Magisk
Device: Samsung Note 4, SM-N910F, armeabi-v7a Android version: Android 6.0, Marshmallow Magisk version name: f623b98 Magisk version code: 22101 Full Magisk Version Information: f623b98 (22101) (20)...
github.com
Click to expand...
Click to collapse
Hi,
I got the same issue as you on my note 4 SM-N910C.
Do I need to boot into TWRP recovery and uninstall the current version of Magisk and re-flash the 21.4 zip file?
Thank you.
Jeffrey
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I installed the 21.4 version and it's working for root access but failed to pass the safetynet checked.
I downloaded the app-debug.apk (Canary) and installed it. It fixed the safetynet checking but loss the Magisk installed app, it backed to the 1st picture "Installed: N/A"
Don't know how to fix it.
Same here. I'm attempting the 21.4 work around. Flashed rooted stock 6.0.1 on verizon Samsung S5, coming from LineageOS 14.1, and attempting Lineage 18.1 from HaggertK.
My main reason for wanting updated Magisk is the use of downloaded modules, such as charge controller, and systemless hosts for ad away.
actionville said:
Same here. I'm attempting the 21.4 work around. Flashed rooted stock 6.0.1 on verizon Samsung S5, coming from LineageOS 14.1, and attempting Lineage 18.1 from HaggertK.
My main reason for wanting updated Magisk is the use of downloaded modules, such as charge controller, and systemless hosts for ad away.
Click to expand...
Click to collapse
Do you able to use the adb or fastboot command? If yes, can share the steps...really appreciate it...tqvm...
try oter third kernel eg. ramkernel
same issue N910F any solution yet?
Guys n gals!
Canyie posted new test build 20 days ago now, but NO-ONE reported testing yet!
https://github.com/topjohnwu/Magisk/issues/4174#issuecomment-985646477
Anyone here still interested in a fix?... Any testers / punters who can send logs?
PW
Today I have installed Built-In BusyBox module by zgfg to overwrite meefik's busybox binaries in /system/xbin which I couldn't remove due Resource or Device Busy error.
Then I found out that busybox is one of the ways to detect modified android so I want to remove it but module unfortunately doesn't come with uninstaller so I am stuck with busybox in my /system/xbin directory with no way to remove. All I found on Magisk's docs is to replace files or directories not remove them but 2018's version said that removal is possible, just that it is hassle or something.
Can anyone help?
Additional info: I don't have any Custom Recovery and don't tell me to get one.
Click to expand...
Click to collapse
NOTE! To help others with same problem I am planning to compile answer as Magisk Module so please open PR in this repo:
Click to expand...
Click to collapse
GitHub - UltraStudioLTD/BuiltIn-BusyBox-Uninstaller: Uninstall busybox
Uninstall busybox. Contribute to UltraStudioLTD/BuiltIn-BusyBox-Uninstaller development by creating an account on GitHub.
github.com
Have you tried removal via TWRP?
How to disable Magisk modules without Magisk and TWRP recovery
Hi, I installed an incompatible Magisk module in the past, which cause bootloop of my phone. Co I dirty flashed my ROM (Pixel Experience) to get my phone work again. My current situation is that I cannot flash Magisk because an incompatible...
forum.xda-developers.com
lemon567 said:
Have you tried removal via TWRP?
How to disable Magisk modules without Magisk and TWRP recovery
Hi, I installed an incompatible Magisk module in the past, which cause bootloop of my phone. Co I dirty flashed my ROM (Pixel Experience) to get my phone work again. My current situation is that I cannot flash Magisk because an incompatible...
forum.xda-developers.com
Click to expand...
Click to collapse
I don't have TWRP and I can't install any Custom Recovery.
Please don't tell me to follow that or this instructions to install them, I followed everything and still no luck.
What you could do is enter safmode of your phone (Google how to enter safe mode for your phone) and remove the files manually or use the BusyBox cleaner zip and flash it in magisk manager and if you're lucky it will remove it
Release v1.29.0-YDS-201807132149 · yashdsaraf/bb-bot
Bot to compile, package and release busybox for all android architectures - Release v1.29.0-YDS-201807132149 · yashdsaraf/bb-bot
github.com
Unfortunately safe mode in my phone is kinda broken, I think. Cause every 3rd party app was not only disabled but also disappeared like magic. Also I don't trust unknown ZIPs so I haven't tried that link.
**I solved problem by disabling every Magisk module I had, rebooting and after that it succeed in deletion with no problem**