Canary Magisk Manager: Link
Canary Magisk Manager (Debug): Link
Latest Release Notes: Link
All Canary Files: Link
The Canary Builds are similar to Google Chrome's: bleeding edge of the source.
Be warned: Canary can be unstable.
The binaries from debug channel are built with debug flag ON
Install Canary Magisk Manager and go to Settings > Update Channel and switch to either Canary or Canary (Debug)
If you need a clean start, download the Canary Uninstaller to uninstall any version of Magisk
How to Report:
Only report bugs/logs using the debug channel!!
Magisk installation failure:
In TWRP: Upload the recovery logs (pull the file /tmp/recovery.log, or select "Advanced > Copy Log" and upload)
In MagiskManager: Choose to save logs after installation and upload
Magisk bugs:
Magisk logs are placed in /cache/magisk.log (For A/B devices, they are actually in /data/cache/magisk.log)
If you cannot boot or stuck in bootloops, grab logcats (and kernel dmesg if possible) on boot
Magisk Manager bugs:
Grab logcat (NOT magisk logs) when the crash occurs, upload the logs and report how to reproduce
SafetyNet / CTS / XXX app won't work after enabling MagiskHide:
Ignored
I just installed this on one of my Nextbook Ares 8A's, x86, Android 6.0.1. It was previously on @ianmacd 's unofficial build. So far, it appears to be working great. I un-installed my previous MM, before I install the new one, downloaded the Magisk.zip in MM and flashed it through TWRP.
How much overhead does the extra logging create? I don't notice any difference. Do you think it will affect battery life?
When I check the magisk.log it does appear that it is continuously logging, because each time I check it the time stamp is updated.
If I am not mistaken, on non debug builds the magisk.log is only created at boot and not updated again until next boot?
Thanks, @topjohnwu for creating this new channel for testers.
Wew, downloading and testing on my 7.1.2, so far so good. Thanks.
Aye official snapshots! Awesome. Been using @kantjers up until now. Thanks for this
Sent from my LG Nexus 5X using XDA Labs
Testing now. Thanks ?
No issues with any of my used modules ?
When patching boot image as install method you should check for storage permission first.
Currently if storage permission hasn't been granted the patch will fail at the very end (when it goes to write the patched image to internal storage), with no indication as to why. The error will just state that it failed.
jcmm11 said:
When patching boot image as install method you should check for storage permission first.
Currently if storage permission hasn't been granted the patch will fail at the very end (when it goes to write the patched image to internal storage), with no indication as to why. The error will just state that it failed.
Click to expand...
Click to collapse
Yes, I think Magisk Manager should ask for the storage permission on first launch and not later when the actual storage permission is need. I have been bit by the storage permission a few time in other instances of using MM.
Good find @jcmm11 , I have not used that option to patch the boot.img.
Any way to fix the phone off charging issue? To recap. When phone is powered of and plugged in. The charging battery icon.stays on and freezes the screen. Only hard reboot gets phone started.
New Canary Build up for Testing!
Support bypassing FGO, CrackProof protections, and Fortnite!
jcmm11 said:
When patching boot image as install method you should check for storage permission first.
Currently if storage permission hasn't been granted the patch will fail at the very end (when it goes to write the patched image to internal storage), with no indication as to why. The error will just state that it failed.
Click to expand...
Click to collapse
This issue is resolved, thank you for your report!
def-g said:
Any way to fix the phone off charging issue? To recap. When phone is powered of and plugged in. The charging battery icon.stays on and freezes the screen. Only hard reboot gets phone started.
Click to expand...
Click to collapse
I'm aware of this issue, will try to figure out the cause of the issue
topjohnwu said:
New Canary Build up for Testing!
Support bypassing FGO, CrackProof protections, and Fortnite!
This issue is resolved, thank you for your report!
I'm aware of this issue, will try to figure out the cause of the issue
Click to expand...
Click to collapse
Cool. To be honest, only a minor inconvenience. Your work is greatly appreciated.
I just installed this build and it appears to be fine on my device. The logcat was taken in Logcatx using the per app logcat for Magisk Manager. If you would like a full system logcat, let me know, or if you would like any other info such as last_kmsg or dmsg, let me know.
I have been installing through TWRP, since recently I have twice experienced data corruption issues with the direct install method in unofficial builds, noted in the unofficial thread.
As always, Thanks
Hi, after fullwipe the MM is not installed on first Phone start? Is this a Bug?
I use a S7 Edge with SM 2.8.
Please Help.
BustedFly said:
Hi, after fullwipe the MM is not installed on first Phone start? Is this a Bug?
I use a S7 Edge with SM 2.8.
Please Help.
Click to expand...
Click to collapse
I suggest you download MM from here and try to install it. I have been flashing Unofficial builds of Magisk for some time and this appears to be a common issue. It should not happen if you did a full wipe of the ROM though.
The latest Canary Magisk Manager.apk download:
https://github.com/topjohnwu/magisk_files/blob/master/canary_builds/app-full-debug.apk
Direct download for all of the latest Canary builds:
https://github.com/topjohnwu/magisk_files/tree/master/canary_builds
Thx.
I try a few build... Offi and unoffi.... The only one without this Bug ist the builds from kantjer. All other cant install the MM after a fullwipe. I try this many times
BustedFly said:
Thx.
I try a few build... Offi and unoffi.... The only one without this Bug ist the builds from kantjer. All other cant install the MM after a fullwipe. I try this many times
Click to expand...
Click to collapse
By fullwipe, I presume you mean full wipe of the ROM? If not, you must remove the Magisk Manager of the unofficial build before installing this one, as it is signed with a different key.
Yes.. I mean fullwipe by twrp and clean Installation of the Rom
BustedFly said:
Yes.. I mean fullwipe by twrp and clean Installation of the Rom
Click to expand...
Click to collapse
After flashing Magisk and rebooting, the app-full-debug.apk will not install? That is a strange issue. Maybe someone else can help.
On one device with @kantjer 's latest build, I first un-installed his Magisk Manager, installed the app-full-debug.apk, opened it, set up the custom update channel to the link in the op: https://bit.ly/2MPKGY5 and hit install, download Zip only, then rebooted to TWRP and installed that downloaded Magisk.zip and rebooted to a working Magisk install.
Hey @topjohnwu,
I've noticed a line just after rebooting using the Canary:
Code:
09-09 14:34:38.542 3913 3913 D Magisk : resetprop: decode with protobuf from [/data/property/persistent_properties]
09-09 14:34:38.542 3913 3913 D Magisk : resetprop: prop [persist.magisk.hide] does not exist
I'm not sure if it's important or not for magisk functionality, however I wanted to report it just in case something is off.
I'm using OnePlus 6 with Open Beta 2 (Pie, 9.0).
I'm going to make it my duty to delete any and all posts that are not relevent to what the developer wants or is asking for.
I'll be checking this thread daily from here on out. If I find myself deleting a ton of any reoccurring member's posts, I'll be escalating to consequences.
Please, thoroughly give your posts some thought prior to submitting them, and ask yourself if whether or not it fits into how or what the OP is asking.
Thank you
So, tried last canary, nothing critical to report apart that FGO doesn't work (it crashes like before with error 61), here there are both magisk log and catlog.
Catlog (too big for xda, dunno why): https://mega.nz/#!LUoBQY6L!X--KKkCCzQn4SLwaIX1hYsmrKzzNfx1TTSGCh1b-0E4
Magisk log attached.
OnePlus 6 OOS 5.1.11, 8.1 July Patch
If anything else is needed I'll provide it right away
Related
Hi guys, I've been having problems getting magisk v11.1 to install correctly.
I have a Samsung galaxy s5 which I use to play about with. I flashed magisk v11.1 which installed properly. After starting up my phone and getting the Magisk manager app it's telling me magisk is not installed. Yet the manager also tells me its properly rooted 6:MAGISKSU (topjohnwu)
The manager gives me the option to download and install v11.1 when I install it through the manager app it says installation succeeded, yet when I reboot I get the same results again. Magisk is not installed, properly rooted.
Does anyone have any ideas what I might be doing wrong?
Ok. This has been reported a few times, but I've not seen it properly troubleshooted yet.
1 - Root is working on your device? You can grant root to root apps?
2 - Do you have a file called magisk.img in /data?
I can't see the file in that directory. I also did a search and nothing came up
I can use root explorer in ES file explorer
Just to make sure: it's supposed to be in the /data folder found in root (where you'll also find /etc, /system, and so on), not in your main storage. If it's not there, that's your problem. That the Magisk image isn't installing correctly.
Could you also upload a recovery log from flashing Magisk in recovery?
Sorry I made a mistake, I was looking in Data>Magisk folder, in / Data there is a file called magisk.img
Awesome. Then that's not the issue then...
Recovery log and Magisk log, please...
Sorry for the noob question, but where do I find the logs?
Exactly the same problem with my NOTE 4 on Android 6.0.1. After Reboot Magisk is gone. Without Reboot works perfect (SU and Safetynet).
Looks like temporary "magisk".
The Boot Image Path is automatic (mmcblk0p17). Maybe change. But which one? There are about 20 paths.
I did a quick search and found another couple of posts in the support thread about this issue. Guess what you all have in common? Samsung... The statistical material is way to small to make any definite assumptions, but it points to a trend. And we know that Samsung doesn't always play nice with Magisk.
Have you guys tried a custom kernel? No guarantees, of course...
Possibly useful logs for troubleshooting:
- Recovery log from installation (saved in recovery right after flashing Magisk, can also possibly be found in /cache/recovery after booting up the device).
- Magisk log. Found and exported from the Manager (make sure verbose logging is enabled), or if that doesn't work it can be found in the /cache folder (accessible though TWRP if nothing else works).
- Logcat from boot. Use a computer, connect the device and use ADB to catch a logcat from boot up until you can confirm that Magisk reports "not installed" (How to logcat).
If nothing works, open an issue on GitHub with a detailed description, logs and boot image attached (just make sure no-one else has opened one before, if so post your information to that issue).
Same problem
Same problem here in a G900F (galaxy s5) with [ROM][G900F][ALEXNDR] CQBW, i can grant access to apps and the magisk.img is in /data, but magisk manager says that magisk is not installed.
Attached magisk and recovery logs
recovery and magisk logs
I tried a custom kernel like you said and it seems to work now. The status is all passes. I used this [EOL][KERNEL] [SM-G900F] [Samsung Stock M/LP] Boeffla-Kernel (25-11-2016) kernel
K3vG said:
I tried a custom kernel like you said and it seems to work now. The status is all passes. I used this [EOL][KERNEL] [SM-G900F] [Samsung Stock M/LP] Boeffla-Kernel (25-11-2016) kernel
Click to expand...
Click to collapse
Did somebody knows something like this above for the NOTE 4 SM-N910F? I have no experience with custom kernels.
Since @K3vG managed to fix the problem with a custom kernel it's very probable that this is a compatibility issue with the stock boot image.
Would any of you fine gentlemen like to contribute to the community and development of Magisk? It'd be helpful if one of you could open an issue on GitHub about this, with details and a copy of the problem boot image. It'd probably also be helpful if the rest of you then could add your boot images...
Of course, there are no guarantees, but if there's an open issue on GitHub with the above mentioned information there's at least a chance that @topjohnwu can take a look at it and possibly even fix the compatibility issue.
Didgeridoohan said:
Since @K3vG managed to fix the problem with a custom kernel it's very probable that this is a compatibility issue with the stock boot image.
Would any of you fine gentlemen like to contribute to the community and development of Magisk? It'd be helpful if one of you could open an issue on GitHub about this, with details and a copy of the problem boot image. It'd probably also be helpful if the rest of you then could add your boot images...
Of course, there are no guarantees, but if there's an open issue on GitHub with the above mentioned information there's at least a chance that @topjohnwu can take a look at it and possibly even fix the compatibility issue.
Click to expand...
Click to collapse
There is already an open issue https://github.com/topjohnwu/Magisk/issues/94
ccerrillo said:
There is already an open issue https://github.com/topjohnwu/Magisk/issues/94
Click to expand...
Click to collapse
Awesome! I checked but missed that one. Then someone should upload a boot image to that issue.
Didgeridoohan said:
Awesome! I checked but missed that one. Then someone should upload a boot image to that issue.
Click to expand...
Click to collapse
What is that image? /data/magisk.img??
ccerrillo said:
What is that image? /data/magisk.img??
Click to expand...
Click to collapse
You'll find boot.img in your ROM zip or factory image. Alternatively you can make a backup of Boot in TWRP and upload that.
K3vG said:
I tried a custom kernel like you said and it seems to work now. The status is all passes. I used this [EOL][KERNEL] [SM-G900F] [Samsung Stock M/LP] Boeffla-Kernel (25-11-2016) kernel
Click to expand...
Click to collapse
I flashed that kernel too, and then i can install magisk, but magisk manager tell's "SafetyNet failed CTS profile missmatch"
What i do:
1.- Flash Alexndr rom (G900FXXS1CQBW_DevBase_v3.8.zip << Android 6.0.1 - stable)
2. Reboot
3.- Flash [EOL][KERNEL] [SM-G900F] [Samsung Stock M/LP] Boeffla-Kernel (25-11-2016) kernel
4.- Reboot
5.- Flash Magisk V11.1
6.- Reboot
7.- Enable Magisk Hide
8.- Reboot
9.- "SafetyNet failed CTS profile missmatch" :crying:
What i'm missing?? What steps did you follow to bypass SafetyNet??
---------- Post added at 09:11 PM ---------- Previous post was at 09:06 PM ----------
Didgeridoohan said:
You'll find boot.img in your ROM zip or factory image. Alternatively you can make a backup of Boot in TWRP and upload that.
Click to expand...
Click to collapse
I got it!! Thanks!
ccerrillo said:
I flashed that kernel too, and then i can install magisk, but magisk manager tell's "SafetyNet failed CTS profile missmatch"
What i do:
1.- Flash Alexndr rom (G900FXXS1CQBW_DevBase_v3.8.zip << Android 6.0.1 - stable)
2. Reboot
3.- Flash [EOL][KERNEL] [SM-G900F] [Samsung Stock M/LP] Boeffla-Kernel (25-11-2016) kernel
4.- Reboot
5.- Flash Magisk V11.1
6.- Reboot
7.- Enable Magisk Hide
8.- Reboot
9.- "SafetyNet failed CTS profile missmatch" :crying:
What i'm missing?? What steps did you follow to bypass SafetyNet??
---------- Post added at 09:11 PM ---------- Previous post was at 09:06 PM ----------
I got it!! Thanks!
Click to expand...
Click to collapse
did u manage to get this fixed?
I mean, did you found a way to get safetynet to pass with a custom kernel?
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 guys.
I'm facing an issue with Magisk (stable and beta) that I never had before. I'm on OP5, PixelExperience, Android Pie (but I've tried also on a Oreo ROM yesterday, not sure if it was stable or beta version of Magisk). Here's the flash routine I do for every single ROM:
- Wipe everything, internal storage included
- Flash ROM
- Flash Magisk
- Boot
In the past few days, Magisk isn't installing MM, don't know why. It always installed MM on every single flash I did in my life, now suddenly it isn't installing it anymore. I haven't changed my flashing "habits", I do the exact steps I wrote above on every single flash (not on updates, of course).
This issue also leads to not being able to install modules from MM, but I can install them via TWRP (I've got the latest blu_spark, I'm decrypted, flashed no_verity_v2 for OP5). When I install modules via MM it says:
! /data/adb/magisk_merge.img mount failed.
I tried re-installing Magisk, using the uninstaller and then first time the stable, then the beta, but they won't installing MM after flashing.
What do you guys think?
Thanks.
EDIT: I've recreated the issue, I've attached the log. I tried 2 different modules, Sysconfig Patcher and Busybox. The first one is installing only via TWRP (via MM it produces the log in the attachments), the second one is istalling via MM correctly.
"update-binary: line 203: make_ext4fs: not found"
Unable to format the .IMG to ext4 it seems so there's no magisk merge image to be mounted
Not entirely sure where to go with that but it could be a start.
Bad version of twrp?
If I understand you correctly, the Busybox module install just fine, no matter if installed through the Manager or TWRP.
Have you tried other modules?
The Sysconfig Patcher module isn't using the official module template, so it's very likely that @VR25 need to fix something in his install script.
Didgeridoohan said:
If I understand you correctly, the Busybox module install just fine, no matter if installed through the Manager or TWRP.
Have you tried other modules?
The Sysconfig Patcher module isn't using the official module template, so it's very likely that @VR25 need to fix something in his install script.
Click to expand...
Click to collapse
Indeed, there's stuff to "fix". I've been working on that for a few days now. I noticed [some] recent ROMs lack a bunch of useful binaries, such as make_ext4fs and resize2fs. So, I'm migrating to Magisk Module Template and relying on Magisk's util_functions.sh for better "future-proof" compatibility.
Didgeridoohan said:
If I understand you correctly, the Busybox module install just fine, no matter if installed through the Manager or TWRP.
Have you tried other modules?
The Sysconfig Patcher module isn't using the official module template, so it's very likely that @VR25 need to fix something in his install script.
Click to expand...
Click to collapse
I tried YTVanced module, downloaded via MM and it installed just fine. So I think that, as VR25 said, the ROMs I've tried these days might have lacked of those utilities. So we might have "solved" this issue.
And what about the fact that flashing Magisk from TWRP doesn't install MM? Is it also related to the fact that those ROMs are recent?
Pipodi93 said:
And what about the fact that flashing Magisk from TWRP doesn't install MM? Is it also related to the fact that those ROMs are recent?
Click to expand...
Click to collapse
That happens once in a while, and may very well be ROM related. Fortunately, it's easy to install manually...
Didgeridoohan said:
That happens once in a while, and may very well be ROM related. Fortunately, it's easy to install manually...
Click to expand...
Click to collapse
Yeah, I thought so too. Because when I was on AICP, MM was installed after flashing. My concern was that "mount failed" was related to the fact that MM wasn't installed during the flashing operation, but I'm glad to see that's not the case and my phone isn't cursed. Thank you!
Since mm isn't working on new Magisk 19, I took it for inspiration and created a simple manager, just for bypass some "bootlooper" module.
Just install it using recovery and run on terminal /data/media/magisk.
v1.0 - Initial build. Enabling and disabling functions
v2.0 - Added module removal function
v2.5 - No need to use storage to work. May avoid issues. Some others minor changes.
All thanks to
- topjonhwu for Magisk
- VR25 for mm
- TWRP team
- Me? Idk
Great work dev[emoji106], thanks
doesn't works for me (doesn't list modules)
mrhamed said:
doesn't works for me (doesn't list modules)
Click to expand...
Click to collapse
To list modules the script needs to write on /cache or /data. It will choose by itself.
Please send some screenshot of issue.
Looks very promising, especially enjoy having a GUI for this.
mrhamed said:
doesn't works for me (doesn't list modules)
Click to expand...
Click to collapse
I'm working to make script use no external files, so script will depends completely on your recovery binaries.
Hope to release it soon.
I suffer a boot freeze because of a bad module.
Cannot use TWRP and don't have module like Magisk Core Only installed.
I cannot boot to rooted system because of bad module.
Can boot non-rooted system only.
For my device LYA (Mate 20 Pro) which for rooting is using root-through-recovery-boot I can patch boot image with whatever Magisk edition which I assume is the best way to recover the device without full wipe.
Can a Magisk version be easily built which will either skip loading custom modules or delete them during boot? After successfully booting rooted I would flash a standard Magisk.
mikeos said:
I suffer a boot freeze because of a bad module.
Cannot use TWRP and don't have module like Magisk Core Only installed.
I cannot boot to rooted system because of bad module.
Can boot non-rooted system only.
For my device LYA (Mate 20 Pro) which for rooting is using root-through-recovery-boot I can patch boot image with whatever Magisk edition which I assume is the best way to recover the device without full wipe.
Can a Magisk version be easily built which will either skip loading custom modules or delete them during boot? After successfully booting rooted I would flash a standard Magisk.
Click to expand...
Click to collapse
I don't know if I got it correctly.
Well... commonly modules won't survive after Magisk removal.
If you can't access TWRP for flash Magisk uninstaller or disable the problematic module, you can try to flash or even boot the ROM's stock kernel through fastboot.
But if such module did others modifications into data, so you'll have to reflash whole ROM.
Are you planning on publishing this on magisk repo?
This has saved my bacon at least 4 times since installing it, many thanks Adriano
Saved me from bootloop module, works like a charm!
Adriano-A3 said:
Since mm isn't working on new Magisk 19, I took it for inspiration and created a simple manager, just for bypass some "bootlooper" module.
Just install it using recovery and run on terminal /data/media/magisk.
v1.0 - Initial build. Enabling and disabling functions
v2.0 - Added module removal function
v2.5 - No need to use storage to work. May avoid issues. Some others minor changes.
All thanks to
- topjonhwu for Magisk
- VR25 for mm
- TWRP team
- Me? Idk
Click to expand...
Click to collapse
It gives me the error "WTF?! The directory was here just now! It's gone! Please try again... Exiting..."
Thx bro, you saved my day
PixelHead0_0 said:
It gives me the error "WTF?! The directory was here just now! It's gone! Please try again... Exiting..."
Click to expand...
Click to collapse
Same here, on Samsung S10+ with August update, latest Magisk and Twrp.
very useful for android 10, thank you sir !
I can't understand how to run it on the terminal
will it work with Magisk 20.0??
Sivabalan said:
will it work with Magisk 20.0??
Click to expand...
Click to collapse
have you tried it? does it work on magisk 20.1
Confirmed working with Magisk 20.1, thanks a ton for this!
working on 20.2 + android 10
see title
Why can't you flash the installer in TWRP? What is it that doesn't work? Or have you missed that from Magisk v22 you can simply rename the .apk to .zip and install it directly in TWRP?
And bug reports are very welcome on GitHub, as long as you follow the issue template (your reports did not follow the template). If your issue is closed automatically, pay attention to the message from the bot...
Didgeridoohan said:
Why can't you flash the installer in TWRP? What is it that doesn't work? Or have you missed that from Magisk v22 you can simply rename the .apk to .zip and install it directly in TWRP?
[...]
Click to expand...
Click to collapse
I missed that indeed o.o
Thanks a lot for the Information
(where the heck is this stated?)
yes i read the bot message but if you have a problem like mine where it is not version or apk specific it is not possible to open a report :/
There's always the release notes:
https://topjohnwu.github.io/Magisk/releases/22000.html
And of course the installation instructions:
https://topjohnwu.github.io/Magisk/install.html
And if you need to do a bug report, always do so for the latest Canary release. Nothing else is interesting... You can always mention other versions and how things work there, but the report need to be for the current Canary.