yashsingh1/xdaforums huggingface dataset:
[Magisk] EvilWayz:
Hello. I can get this to work perfectly on my phone, an S7 galaxy using blackdiamond rom v4.

However it does not work on my Kindle Fire 8. I don't know why.

I have tried installing it via Magisk manager, and with twrp. I get the same results.

If i type mm i get this:

sh: mm: not found

if I type */mm

sh: */mm: not found

If i type sh /sdcard/mm

sh: can't open '/sdcard/mm'

It obviously works as a program because it works on my phone.

Is the fact that its a kindle fire the problem? Because Originally i had fire os rooted but it wouldnt pass a cts check and it wouldnt load props. So I switched to the current OS which is lineage 14. Props now loads and i have a clean root but mm still doesnt. Hope this is enough info.
[Magisk] Bogdans29:
How proper remove module whan i mark it

/mm /r /moduleiwanttoberemoved enter

And than what
[Magisk] jaggillararla:
Can we get an option to disable modules via numbers? And to get their full names of the module. Instead of writing their full names to disable em. It's time consuming and not a good option imo.
[Magisk] buffal0b1ll:
You don't have to write the full name of the module to disable it.

https://xdaforums.com/apps/magisk/module-tool-magisk-manager-recovery-mode-t3693165/post79698864
[Magisk] Techguy777:
This module saves you from having to redo your whole phone sometimes it's great.

---------- Post added at 10:42 PM ---------- Previous post was at 10:40 PM ----------

That's a great idea I was just wondering how they could make it easier. It's great except the typing names. I know you can short hand it a little but let's take for instance riru core and edxposed they both disable. Nothing big but I would like the numbers to.

---------- Post added at 10:45 PM ---------- Previous post was at 10:42 PM ----------

Ok I didn't know that I'll have to remember that.
[Magisk] LiNEAGEOSANDROiDEVOLUTiON:
Hi, i always used to use xposed modules without trouble. i now tried magisk on a new device and the 3rd module i installed got me into bootloop.

i still have access to twrp and want to give this a try.

SADLY the download attachment link is not working for me:

410 Gone

nginx/1.15.3

dl.xda-developers.com/4/7/3/6/6/2/1/mm-201904040.zip?key=4x6MFHhQkbIDR_vqUTqpWw&ts=1569053297

---------------------------

mm-201904040_2.zip

---------------------------

Details:

HTTP/1.1 410 Gone

---------------------------

OK

---------------------------
[Magisk] LiNEAGEOSANDROiDEVOLUTiON:
this link works:

https://codeload.github.com/Magisk-Modules-Repo/mm/zip/master
[Magisk] VR25:
Check the attached screenshot.

I will.

Meanwhile, extract mm to /data/adb/ and run it as "sh /data/adb/mm".

This is a device specific issue.

I'll implement a workaround.

Is /data encrypted?

If so, try the alternate (extraction) method mentioned above.

Else, try "sh /data/media/0/mm".

There's a wizard. Run run "sh */mm" (without quotes), pick an option, write a pattern, and hit "enter".

You don't have to write full names/patterns.

Example of working patterns (single and multiple modules): xpo, xpo|vip|sysc|emoj, osed

I'll implement the "full names display" and "choose by number" features.
[Magisk] LiNEAGEOSANDROiDEVOLUTiON:
Hi, I'am sitting in the same boat. As a xposed fan, i gave magisk a try by installing taichi module (claims to be xposed installer systemlessly) but was given a bootloop.now trying to disable this failed module. fron TWRP recovery. and found MM should be lucky here. But couldn't get to use it since.

i extrated mm-master.zip locally. put adb to twrp recovery shell and tried:

/mm-master # adb push mm /data/adb/
adb: error: failed to copy 'mm' to '/data/adb/': remote couldn't create file: Is a directory
mm: 0 files pushed. 0.3 MB/s (3140 bytes in 0.011s)
/ # cd /data
/data # ls -lisah
total 4.0K
6240 0 drwxr-xr-x 2 root root 0 2019-09-24 13:22 .
1 0 drwxr-xr-x 25 root root 0 2019-09-24 13:22 ..
313 2.0K -rw-r--r-- 1 root root 5 2019-09-24 13:22 fcc.dat
312 2.0K -rw-r--r-- 1 root root 5 2019-09-24 13:31 sCaMAH.dat
U1005:/data #

2nd try. other directory

adb push mm /tmp/
adb shell
:/ # sh /tmp/mm

Magisk Manager for Recovery Mode (mm) 2019.4.4
Copyright (C) 2017-2019, VR25 @ xda-developers
License: GPLv3+

(!) No Magisk installation found or installed version is not supported.

i flashed Magisk-v19.3.zip earlier.

out of luck?:verwirrt:
[Magisk] VR25:
It looks like full disk encryption

You have no options in this case.
[Magisk] JamesKinds:
[MENTION=5228676]VR25[/MENTION]

Thank you. Thank you. Thank you!

mm saved my life today.
[Magisk] EvilWayz:
I dont believe my device is encrypted, but how do i do this?

EDIT: in /data/adb/modules there is a mm directory but it only contains .uninstall and two text files.
[Magisk] VR25:
That's the module directory. It contains metadata, license information, and documentation.

Extract zipFile/mm to /data/adb/ and try running it as "sh /data/adb/mm".
[Magisk] EvilWayz:
SO download mm with magisk manager and then unzip to that directory?
[Magisk] VR25:
Yes, but you want to unzip only the file "mm".

It's in the root of the zip archive.
[Magisk] EvilWayz:
BOOM!

THat did it.

But, when I "magic mount" it shows all the modules on except mm. how do i toggle it on?
[Magisk] JamesKinds:
Apologies if I've misunderstood something, but mm is not a module rather it is a command line programme for manipulating various components of magisk including modules. As such mm won't display as a module as it is not one. Hope that makes sense.
[Magisk] VR25:
Indeed it's not a module. Thus, magic mount doesn't apply to it. Toggling that won't make any difference.

The next version will install into /data/adb/mm, and have a symbolic link in /data/media/0/.
[Magisk] PoochyX:
So I would love to use this module however when I type the command in twrps terminal I always get back permission denied

Any ideas what's going on...

([emoji3590]09-09-18[emoji3590])
[Magisk] Wolfcity:
I don't know which magisk version you're running but have you tried to extract zipFile/mm to /data/adb/ and run it as "sh /data/adb/mm" like
posted here:

https://xdaforums.com/apps/magisk/module-tool-magisk-manager-recovery-mode-t3693165/post80385765

https://xdaforums.com/apps/magisk/module-tool-magisk-manager-recovery-mode-t3693165/post80324695
[Magisk] PoochyX:
Using magisk 19.3 and no I haven't tried it like that... Just installed the module and rebooted in twrp and tried the command and it's not working for me

([emoji3590]09-09-18[emoji3590])
[Magisk] musa.mun:
How to uninstall any magisk modulos ? magisk20

My OnePlus 7 is bootlope for installing viper for Android module. I trying to remove this model with flashing mm or uninstall mod this 2 method. ..but not work for removing any module ..at last I flash magisk uninstaller and remove magisk from device... Then my device fully booted...but again I trying to install magisk on my device ...it will again bootlope for old module viper...

Have any way to remove this modules...or installed magisk again without wipe data ..?
[Magisk] Wolfcity:
With the TWRP file manager. Location should be (latest magisk) /sbin/.magisk/modules
[Magisk] musa.mun:
I don't find any magisk folder on sbin
[Magisk] VR25:
If you can't find /data/adb/modules/ with TWRP file manager, your data is probably encrypted and TWRP can't decrypt it. In this situation, wiping data is the only solution I'm aware of. Without decryption, you're locked up.
[Magisk] Wolfcity:
Right. If you plan to do that remember you have to format data in TWRP (the option where you have to confirm with "yes"), just swipe to wipe data won't encrypt it.
[Magisk] Sivabalan:
First boot in to twrp recovery and flash magisk uninstaller.

Then reflash you rom zip.

Now flash the twrp installer zip.

Boot in to system....you should get your device running with user-data intact.

If you need magisk, again boot in to recovery and falsh the latest magisk and boot. Now those magisk modules related files would have gone and your device should boot with magisk installed.
[Magisk] HippoMan:
Magisk-v20.1?

Will this utility work for modules installed via Magisk-v20.1?

Thank you very much.

.​
[Magisk] homasholz:
yes, its working for me on 20.1
[Magisk] Ringsofsaturn777:
untick to disable and delete/thrash icon to remove permanently

untick to disable and delete/thrash icon to remove permanently
[Magisk] joelstitch:
I'm getting the error "Filed to map file" when flashing the zip.
[Magisk] BeachNYC:
May I ask you, did you ever find out how to toggle things on in this program? I know the OP says to "Follow the instructions/wizard. Everything is interactive." but I can't figure out how to do such a basic thing as toggling .
[Magisk] HippoMan:
Double-checking that this will work with my device and software

I just want to see if anyone knows whether there would be any problems running this utility on my device with my software setup ...

* One Plus 7 Pro running OOS 10.0.2

* twrp-3.3.1-70-guacamole-unified-installer-mauronofrio.zip

* Magisk-v.20.1

I'm about to flash a Magisk module that might cause a bootloop, and before I do, I want to make sure that I can use this uninstaller, so that I have an easy path for uninstalling that module in case I need to.

Thank you in advance.

.​
[Magisk] joelstitch:
Is working fine for me running 10.0.3 on a Oneplus 7 Pro

I would still make a nandroid backup just in case.
[Magisk] HippoMan:
Thank you very much. Yes, I plan to do the nandroid backup.

Also wondering if anyone has had problems with the 3.3.1-70 TWRP with this utility.

.​
[Magisk] HippoMan:
Better to download or to build?

I downloaded mm-201904040.zip from the OP. I also cloned the github repo and built the module via build.sh. The resulting mm-201904040.zip is slightly different from the one I got from the OP. Which of the two is more up to date, and which is safest to use?

% bash build.sh

zip warning: _builds/mm-201904040.zip not found or empty
adding: build.bat (stored 0%)
adding: build.sh (deflated 44%)
adding: check_syntax.bat (stored 0%)
adding: check_syntax.sh (deflated 20%)
adding: install.sh (deflated 65%)
adding: License.md (deflated 66%)
adding: META-INF/ (stored 0%)
adding: META-INF/com/ (stored 0%)
adding: META-INF/com/google/ (stored 0%)
adding: META-INF/com/google/android/ (stored 0%)
adding: META-INF/com/google/android/updater-script (stored 0%)
adding: META-INF/com/google/android/update-binary (deflated 67%)
adding: mm (deflated 60%)
adding: module.prop (deflated 25%)
adding: README.md (deflated 47%)
adding: uninstall.sh (deflated 18%)
adding: .gitattributes (deflated 25%)
adding: .gitignore (stored 0%)

% sum /opt/local/ftp/mm-201904040.zip _builds/mm-201904040.zip
48757 23 /opt/local/ftp/mm-201904040.zip
52066 23 _builds/mm-201904040.zip

(The one in /opt/local/ftp is the one that I downloaded from the OP).

Thank you.

.​
[Magisk] VR25:
Logs, please...

1. Pick an option (e.g., "d) Disable", you know the opposite of that is "enable").

2. You'll be shown a list of modules and their corresponding status flags (e.g., enabled/disabled).

3. Input a pattern (e.g., xpo) or multiple patterns (e.g., xpo|vip) that match the desired module.

Whatever flag* you choose to toggle is flipped like a coin.

* Changes are handled by Magisk itself and take effect early on the next system boot.

There are multiple ways of uninstalling modules.

As long as TWRP can decrypt data (or you don't use encryption), you can safely proceed without a nandroid.

If the version codes (e.g., 201904040) are the same, everything else is the same as well. In this context, higher number always indicates a more recent version.
[Magisk] HippoMan:
A small issue ...

I'd like to report a small issue ...

I have installed mm-201904040.zip and installed it via Magisk (v20.1) onto my OP7 Pro running 10.0.2.

When I go into recovery (TWRP 3.3.1-70), I can invoke it via sh /sdcard/mm, and it runs fine.

Good job!

However, if I mistype something when running the utility and try to correct it via the backspace key of TWRP's terminal emulator, all I get is ^H on the screen. When I am not running this utillity, the terminal emulator's backspace key indeed erases characters.

The only way I could erase faulty input from within the utility is to select Ctrl-u, which erases the entire line.

This is certainly not a major issue, because I can still use Ctrl-u to correct typing errors. However, I believe it would be helpful if the utility can configure its tty driver to properly respond to the terminal emulator's backspace key.

Thank you for considering this request ... and again, thank you for this excellent utility!

UPDATE: It turns out that this behavior is one of the effects of the read command in the shell that TWRP uses for its Terminal (i.e., /sbin/sh). Putting the following command into the mm shell script should fix this issue ...

stty erase ^H

.​
[Magisk] zunga:
Thank you so very much, Mr. Developer. You just saved me a hell lot of work restoring my phone. God bless you.
[Magisk] forum_dyskusyjne:
Ok.

You right,

I have question, working with latest Magisk 20.3?

If YES, maybe worth correct sign Magisk version in first post?
[Magisk] Mysticblaze347:
Wondering the same. Guess I'll have to test soon. Last I knew the modules list didn't show to remove via recovery / commands
[Magisk] 4radea:
Thank you. :D
[Magisk] Sync0x0007:
Commands

So i had a bootlop. Tried to remove the module with remove feature. Selected the module and it was showing it with [X] (Marked for Removal)

Then i quit but theire was nothing showing like its removing it.

Still had the bootlop, only unistalling magisk helped.

Am i missing the comment to actually remove it ?
[Magisk] amg314:
To delete any Magisk module remove module folder in /data/adb/modules using TWRP file manager
[Magisk] Sync0x0007:
Yea I tried that at first. After doing that it was booting to lockscreen and continued the bootloop back and forth
[Magisk] EgoGone:
I'm basically a complete noob at this and after Googling for about an hour I can't find an answer to my question.

What does this part mean exactly? "- First time (right after installing/updating) - run `mm` or `sh /sdcard/mm` on recovery terminal."

What terminal do I use? Windows 10 cmd using adb/fastboot command? Booting the phone into recovery gives no options for a terminal and the commands aren't working in cmd. What is the recovery terminal that I'm missing?
[Magisk] PoochyX:
Dude you run that from command in the terminal of your TWRP recovery for your device
[Magisk] amg314:
What module initiated bootloop?

Was this bad module removed after you deleted its folder in data/adb/modules?
[Magisk] Sync0x0007:
It was edxposed. First got riru. That worked

But After edxposed made it bootloop.

Deleting did just what i described above.

Only Flashing Magisk uninstall made it work again.

Is edxposed hidden somewhere Else?
[Magisk] amg314:
As I know, you need install both riru-core and riru edxposed (YAHVA or SandHook) modules from Magisk repo.
[Magisk] palmbeach05:
Initial install of module not working with new canary versions, they changed things up with how the magisk version is identified
[Magisk] EgoGone:
I have a Google Pixel 4 XL running Android 10. There doesn't seem to be a stable version available of TWRP for me unless I'm not looking in the right areas. Team TWRP hasn't had an update on Android 10 functionality since Oct 13th 2019.
[Magisk] PoochyX:
Some phones are lucky to have TWRP period and updates are well like a sweet desiring pleasure of sheer indulgence
[Magisk] VR25:
For now, how you have to do is extract zipFile/mm to somewhere and run it as sh /somewhere/mm. That's an alternate way of "installing" this module. I'll update it after the upcoming stable ACC release.

That's one reason why I'm setting my modules to self-disable after a bootloop event. Perhaps, I'll also create a module that disables every single Magisk module after a bootloop event.
[Magisk] oniemjan:
One future user is typing this message... :laugh:
[Magisk] HippoMan:
Could you describe the method you use in your software to determine that a bootloop is taking place?
[Magisk] VR25:
#!/system/bin/sh
# Advanced Charging Controller (ACC) Initializer

(
# some code...
id=acc
# some more code

# bootloop lock file
[ -f /data/adb/${id}-data/logs/bootlooped ] && exit 0
touch /data/adb/${id}-data/logs/bootlooped

# additional code

# remove bootloop lock file
rm /data/adb/${id}-data/logs/bootlooped

# yet more code
&) &

exit 0

Essentially, a lock file is created before module initialization* takes place.

Once the initialization is complete, the lock file is removed.

If the lock file is found on the next boot, module initialization is aborted.

* This applies to my modules only, as they won't be using Magisk's Magic Mount feature. The framework I use is completely different from the stock and other third party Magisk module templates.

You should use post-fs-data.sh** to run the code. I use service.sh, because my framework makes it possible.

** Just test for boot_completed before removing the bootloop lock file.
[Magisk] HippoMan:
Thank you!

So this code needs to be executed as part of a Magisk module's startup sequence.

Is there a way that some code outside of a Magisk module itself could check for a boot loop? I'd like to be able to install something that does the following during system startup ...

pre-magisk-startup.sh:

#!/system/bin/sh
[[ -e /path/to/lockfile ]] && {
rm -f /path/to/lockfile
# disable all Magisk modules
# write a message that sits on the screen for a little while, saying that Magisk modules have been disabled
# reboot
}
touch /path/to/lockfile

post-magisk-startup.sh:

#!/system/bin/sh
rm -f /path/to/lockfile

I'd like to cause pre-magisk-startup.sh to always get run during system boot, immediately before any Magisk module initialization takes place.

Then, I'd like the normal Magisk module initialization to begin.

And finally, I'd like post-magisk-startup.sh to get run immediately after all Magisk module initialization has completed.

What do I need to do in order to get these two scripts to run in this manner? Is it even possible?

Thank you very much.

UPDATE: I added a needed "rm" command to pre-magisk-startup.sh

.​
[Magisk] njascgil:
Thank you for your interest!

I ran Magisk Manager (either "mm" or "./data/magisk/mm"), typed "e" or "u", and entered part of the name of the module in question ("hide", in this case). Using the "e" or "l" option afterwards showed the module as "OFF" or not present, respectively.

After rebooting to recovery, "e" or "l" gave the same info. However, if I shut down the phone the powered it up again directly to recovery, the module was again activated or present...

Meanwhile, I noticed that the problem might not lie with MM. Even if I mount magisk.img to /Magisk, deleting the module in TWRP file manager only sticks if rebooting to TWRP...

In the Magisk General Support thread, it is being mentioned it must be something related to corruption in the Magisk image file. At the time, I tried to run the "f" (fsck) option, but no errors were found. Meanwhile, as I reinstalled Magisk, my original image file is gone...
[Magisk] tomaasz:
I have ununderstanding for this

I written "matching Green" and received "not found"
[Magisk] VR25:
No, no... you write "Green", not "matching Green". What you type must match the entire name of what you want to remove -- or an instance of it.

[MENTION=7476746]njascgil[/MENTION], have you tried the same procedure with a fresh magisk.img? Usually, when you have an extremely corrupted .img file, even fsck can't help.
[Magisk] beavis5706:
OK I got it to work. I was doing it right but it took a long time for the module to disable module. However this attempt proved useless. Despite repeated attempts to delete, move, rename and now disable the Greenify4Magisk Module it always reappears upon reboot. I simply cannot get rid of this module.

Xposed was so much better. At least there if you had an incompatible module you just removed it. With magisk if you get a bad module good luck trying to get rid of it.
[Magisk] njascgil:
I just put aside a few minutes to test it and yes, everything works just fine with this new/clean magisk.img

(However, in the TWRP terminal, I can see a "Segmentation Fault" message just after entering "./data/magisk/mm" and before the options menu appears, but it does not seem to be detrimental to MM operation...)
[Magisk] VR25:
Before you lose hope and step aside, why don't you test a fresh magisk.img as [MENTION=7476746]njascgil[/MENTION] did? -- Remove that file & reinstall your modules. BTW, did you try removing Greenify4Magisk from Magisk Manager (the app)?

Nice to know. About that "segfault" -- it'll be killed soon.
[Magisk] VR25:
# 2017.11.11 (201711110)

- Ability to make magisk.img survive factory resets (mm itself will persist by default).

- mm won't run in boot mode -- now you cannot push the "do not touch" red button even if you wanted to.

- Massive optimizations

P.S., download from Magisk Manager.

Edit: if you want to flash anything else after instilling/updating mm from recovery, you have to reboot recovery first.

Edit 2:

# 2017.11.11-1 (201711111)

- Fixed critical error -- wrong IMG path.
[Magisk] dingolino:
Do you have the newest version in your 1st post or is this still the initial one?

Best regards

dingolino

Gesendet von meinem SM-N950F mit Tapatalk
[Magisk] VR25:
That's the initial version. I'll remove it to prevent further confusion. Unless stated otherwise, current and future versions are to be downloaded from Magisk Manager or from the repository listed.
[Magisk] dingolino:
Hi,

I have a noob question:

>simply run "/data/media/mm" on terminal.

This is clear so far and not realy a problem.

However for me the Magisk Manager is somehow a emergency tool - to have it just in case, that I am able to deactivate magisk module in case of a bootloop from recovery. So I will not use it quite often and than I fear that I forgot the path name to run "mm".

Is there a possibility that I can create something like a shortcut in TWRP and store this shortcut to have a easy access?

I am not the terminal/console crack who is using this all day long, more the "warm shower guy" who needs a guideline and wants to make it comfortable and foolproof for myself ...

Best regards

dingolino
[Magisk] VR25:
[MENTION=764772]dingolino[/MENTION], in that case, simply re-flash the zip, then run mm instead of /data/media/mm. ;)
[Magisk] dingolino:
That was my backup plan ...

;)

Gesendet von meinem SM-N950F mit Tapatalk
[Magisk] Sam Nakamura:
Maybe I'm just blind but I can't find a valid download link for this module, the thread link just links this thread and Git returns 404 page load error...
[Magisk] Didgeridoohan:
It's in the Magisk repo (Manager - Downloads).

[MENTION=5228676]VR25[/MENTION] The GitHub link in the OP has a parenthesis in the end, that's why there's a 404.
[Magisk] drei.liter.milch:
very useful! thanks for this one :good:
[Magisk] bonbonboi:
What its name would be so we could search within Magisk Manager :confused:
[Magisk] yochananmarqos:
Gee, I wonder what it could be called? :eek::rolleyes:
[Magisk] bonbonboi:
Seems its Magisk Manager for Recovery Mode
[Magisk] VR25:
# 2017.11.25 (201711250)

- Top-to-botton optimizations

- Users no longer have to reboot recovery after flashing mm -- prior to flashing something else

# 2017.11.25-1 (201711251)

- Fixed "non-existent tmpd" error
[Magisk] samteeee:
[MENTION=5228676]VR25[/MENTION]

This sounds like a life saver, Thank you.

Can this be used on A/B partition system, i.e Pixel 2 XL?