yashsingh1/xdaforums huggingface dataset:
[Magisk] McTRASH692:
Just to verify, is this compatable with nougat?

Searched in Magisk Manager/Downloads and only found marshmallow version,

Just want to make sure this one is compatable with nougat,
[Magisk] Wolfcity:
For me it works on 7.0 and with magisk 18.
[Magisk] McTRASH692:
Thank you, I'm on 7.1.1 so should work,

Will confirm when tested,
[Magisk] yochananmarqos:
mm = Magisk manager, not Marshmallow ?
[Magisk] McTRASH692:
Oh, ok , I thought it meant Marshmallow, thanks for clearing that up,
[Magisk] McTRASH692:
To confirm it does work on 7.1.1,

Had to install through recovery,
[Magisk] skullkid383:
we already knew this it works on any version of android
[Magisk] gnabtib8:
Delete
[Magisk] Bakuryu91:
Hi,

Sorry for the late reply, I was away for a while.

The OOS OTG enabler module was the solution for me, since my issue was that the USB port is disabled by default on OOS ROMS. What ROM are you on? There is probably a setting to enable USB_OTG on your ROM (this OOS OTG enabler module simply sets the "persist.sys.oem.otg_support" to true, but I believe there is such a setting for other ROMs as well).
[Magisk] j4n0p0g1:
Hi sir I just installed the Magisk Recovery after I rebooted my phone and then went to the Terminal Emulator and typing ' / data / media / mm ' there is not execution happen it all says "no such a file or directory "that's just what it says. Please help. I'm confused. Thanks
[Magisk] VR25:
/data/media/mm -- that's what you should've ran.

Everyone,

This project is not dead. It's just not a priority right now.
[Magisk] j4n0p0g1:
Yes I already ran that ' /data/media/mm ' but the problem has the same. It all says ' No such a or directory '
[Magisk] j4n0p0g1:
Yeah ran that but the problem continuously appear.

Please help me! Thanks
[Magisk] micgeb:
Test it with a terminal app. Type su and /data/media/mm. Or look with a filemanager in the directory. Is the file mm inside?
[Magisk] j4n0p0g1:
Yes! There is a file 'mm' in the /data/media and ow! That message appear when I execute the ' . /data/media/mm' in terminal. What should I do?
[Magisk] shadavis08:
I can not get saftey net to check. Anytime I tap on it to check its like a dead button now. Anyone know what's going on?
[Magisk] jcmm11:
Tap on the right hand side (the circular arrow)
[Magisk] shadavis08:
What are you talking about? Which arrow lol
[Magisk] shadavis08:
Huh
[Magisk] Wolfcity:
Huh? I got it on the right side....

Maybe tap on the place where it should be.
[Magisk] shadavis08:
It's white that's why and I have a theme overlay. Got it thanks man.
[Magisk] Wolfcity:
Good to hear that.:good:
[Magisk] micgeb:
You must mount the /data first in twrp.
[Magisk] j4n0p0g1:
Ow? Is it needed? I got ctr recovery? the twrp on wasn't touching when I installed it on my phone
[Magisk] VR25:
Yeah, obviously data must be mounted first. If /data/media/mm fails, try sh /data/media/mm.
[Magisk] neekless:
Magisk is moving towards deprecating magisk.img (already in the canary), which breaks the function of this module. Do you plan to update this module to work with the new mechanism when it reaches stable?
[Magisk] VR25:
Yes, I will keep updating it.
[Magisk] mnurolcay:
Magisk Manager shows an update, but when I try to install it, it's failing to install. I'm using Magisi 18.1 and Magisk Manager 7.0 on OnePlus 5T Android Pie. Log file attached.
[Magisk] imakul8:
Uninstall the older version first then install the newer version.
[Magisk] mnurolcay:
Tried, same thing. Installing through magisk failed again.
[Magisk] opz187:
are u running the canary build?

bc that may be it
[Magisk] mnurolcay:
no, as i mentioned before; Magisk 18.1 / Magisk Manager 7.0
[Magisk] jcmm11:
Uninstall the older version then run the following from your PC

adb uninstall com.topjohnwu.magisk

to finish the job.

(Courtesy of https://www.didgeridoohan.com/magisk/ManagerIssues)

(Since you're still rooted you may be able to accomplish this from a terminal emulator by using the command (as root)

pm uninstall com.topjohnwu.magisk

)
[Magisk] VR25:
That's a classic Pie issue. Try installing from TWRP. This will be fixed in the next version.
[Magisk] mnurolcay:
Done, thanks :good:
[Magisk] papoy1019:
Looking Forward. Kudos!
[Magisk] koniii:
Working fine on KitKat on Magisk v18.1
[Magisk] electroblood:
This mod saved me a whole bunch of grief today. Thank you.
[Magisk] pr1jker:
Yep. Me too. Thanks to the dev!
[Magisk] godofsalt:
Yeah me 3!!!

Tanx VR25! Has helped me and am sure it's gonna help a lot of people in the next 24hrs...

Seeing how LOS 16 has Landed Today!!
[Magisk] oroboros74:
This module is so extremely useful that it should be part of Magisk directly!

But I'm having problems setting it up:

- First time, after first install, I opened recovery terminal (I'm using OrangeFox, which is based on TWRP)

- I typed "mm" (without quotes) in the recovery terminal.

But nothing happened.

Maybe the instructions aren't clear enough, or maybe I'm misreading them. Any hints?
[Magisk] Ænimal:
Which magisk version? Did you try /data/media/mm ? If that's not working it is probably recovery related
[Magisk] oroboros74:
Magisk is 18.1.

When I open Recovery Terminal it shows:

sh-5.0 /tmp

and in this case typing "mm" does nothing

I just tried /data/media/mm and that shows the menu with list, disable modules, etc. So can I assume it's installed correctly at this point?

If so, then what is the use of "mm" after first install?
[Magisk] VR25:
"/data/media/mm" works anytime.

"mm" works only after install/reinstall, and before you reboot. It it doesn't, your recovery is to blame.

I never used OrangeFox recovery.

Before the next release, I may guide your through gathering debugging information to help find what's wrong.
[Magisk] oroboros74:
OK, so despite "mm" not working, I can still use it using the longer path - cool!

I would suggest to change the USAGE part in the readme, then, because how I read it, I understood that it was imperative to run "mm" right after installing/updating (i.e. otherwise it wouldn't work). Here's my suggestion:

### USAGE

After install and reboot:
- To use, simply open recovery terminal and run "/data/media/mm" (no quotes).
- Follow the instructions/wizard. Everything is interactive.
- You can also run "mm" from recovery terminal the first time, right after installing/updating.
[Magisk] Ænimal:
Deleted
[Magisk] SomniusX:
S7 Edge latest twrp, latest resurrection remix on android pie, 3-4 magisk modules and no ruri/edxposed (yet), had my fair share of problems yesterday and i re-flashed everything after clean install. A user mention this module, that i skipped cause i didn't know existed, and i tried installing it a couple of minutes ago.

I get the following

Any ideas?

edit: i flashed the zip manually and rebooted into recovery, now another strange thing..

i do a

mm

i get

sh: mm: not found

i changed to /data/media

cd /data/media/
/data/media # mm
sh: mm: not found

now what!? it doesn't want to run? :P

when i do just the m and tab'it it displays all commands that start with m but not "mm"
[Magisk] VR25:
Try sh /data/media/mm
[Magisk] SomniusX:
So it needs shell elevation. OK I'll try it and report back. Thank you
[Magisk] jcmm11:
No not she'll elevation. But try entering the full path or, after cd'ing to the directory, try ./mm

Typing just mm will use the existing PATH, no matter where you're located.
[Magisk] Mike.K.krd:
Hi!

If I delete the module, the changes made by it are not saved, right?
[Magisk] jcmm11:
Which module? What type of changes?
[Magisk] Mike.K.krd:
Oh, my mistake, sorry. I've wrote in wrong thread :eek: Question was about LKT module
[Magisk] Naagraj:
Installation fails via Magisk Manager on my Mido (SD625 4/64GB).

Resurrection Remix 7.0.1 (9 Mar 2019 build)
[Magisk] VR25:
That's a Pie specific issue (to be fixed).

Meanwhile, install from TWRP.

To use, run sh /data/media/mm (recovery terminal).

Advice: befriend XDA search tools!
[Magisk] VR25:
Not exactly...

The advantage of using "sh /data/media/mm" over "./data/media/mm" is that it works even if the file lacks execute permissions.
[Magisk] Naagraj:
I haven't tried running shell commands via receovery terminal. Could you please tell me a bit step by step? TIA
[Magisk] Wolfcity:
I don't think there's anything more to explain.

Just flash the module in TWRP, open the in-built terminal and run sh /data/media/mm

The module should start and you should be able to do the things you wanted to do with it (uninstall a buggy module or whatever).
[Magisk] Naagraj:
Thank you sir. Installed this module and tried the command as well.

It should be a must have module for everybody. In case a module comes in buggy, this is a savior
[Magisk] Nosferatu.:
So I flashed the module in Magisk. I boot into TWRP. I can see the "mm" file in the directory. I run the command and it doesn't do anything. From the last few posts I've read am I supposed to also flash it in TWRP as well as Magisk before running that command for it to work?
[Magisk] Wolfcity:
Just do it like mentioned here:
[Magisk] Schroeder09:
Just tried installing this on my pixel 2 xl (stock ROM) with Android pie March 2019 update. I get the installation failed message right away. Am I doing something wrong?
[Magisk] dijeypee:
Is there a way to flash this on magisk without twrp? How to execute?
[Magisk] PacoBell:
Tried to install this on Pixel 2 XL running Q Beta and it immediately failed with this error:

"- Copying zip to temp directory

- Installing Magisk_Manager_for_Recovery_Mode_(mm)-2018.8.1.zip

(!) Magisk is not activated! Abort

Installation failed"

Magisk is definitely installed and functioning.
[Magisk] yung40oz84:
Dang, that's why it doesn't work, lol. Ugh! Can you make an updated build for canary? Or is that asking too much ?? thanks for your work!
[Magisk] VR25:
If /data/media/mm exists, go to recovery terminal and run sh /data/media/mm. Else, install mm from recovery, then run that command.
[Magisk] VR25:
[MENTION=6044187]yung40oz84[/MENTION] et al, Magisk 18.2+ versions are not supported. Generally, I only support stable releases. Playing with canary stuff on a production device is a bad idea.

Did you try installing from recovery?

Simply extract zipFile/mm to /data/media/. That's an alternate way to install it.

Which Magisk version is that? Did you try installing from recovery?
[Magisk] PacoBell:
Due to Q Beta, I must run Magisk Canary. But I will try installing from TWRP and get back to you.
[Magisk] coldgin_:
It's already been stated by the dev in this same page that the app doesn't work in Magisk canary. So don't waste your time trying via TWRP. You will have to wait until 18.2 turns stable.

Regards.
[Magisk] Zander_Sig:
list of commands?

Hey guys, this sounds like a awesome thing to disable modules. I freaking hate bootloops.

Problem for me .. I've always had trouble typing in commands in any terminal.

Can someone post a detailed list of what to exactly type in the TWRP Recovery Terminal? Just the main and most important commands will be fine.

If you can type them up so if I had to I could just copy and pastev them. I don't think you can copy and paste in the terminal... I was just saying that as an example of what I'm looking for. I think it will help out a bunch of other people besides me?

Thanks OP for this and everyone else!
[Magisk] Wolfcity:
If you check the above post I think it's not worth to do so because the actual magisk beta 19.0 (and future stable) is coming without any magisk img and so the modules aren't stored there anymore.

If you want to get rid of a module that causes a bootloop when on magisk 19 just use the filemanager in TWRP and navigate to /data/adb/modules. Then delete the folder of the module in question (or move it out of the way).

Or use the old method to force magisk into "core-only" mode by touching /cache/.disable_magisk (note the trailing dot before disable).

For the last days of 18.1:

Just flash the module in TWRP, open the in-built terminal and run sh /data/media/mm

The module should start and you should be able to do the things you wanted to do with it (uninstall a buggy module or whatever).
[Magisk] Adriano-A3:
mm isn't working on Magisk 19

mm is the main module for Magisk. It's the first one that I ever installed after flashing Magisk

Pls update it dev

Thanks in advance
[Magisk] bggold:
No need read previous post.
[Magisk] Adriano-A3:
Sure. My bad.

Now I got new modules structure.

To disable a module, just navigate to /data/adb/modules/MODULE and add a file named disable. Done.
[Magisk] bggold:
There ya go.
[Magisk] dijeypee:
You mean extract all the files in the zip magisk manager for recovery mode or the file named mm inside the zip? :(
[Magisk] thezinq:
How can I resize magisk.img with this tool?

I'm using Magisk v18.
[Magisk] Adriano-A3:
I created an alternative for Magisk v19 guys

Hope you enjoy it

Click here
[Magisk] Nosferatu.:
Appreciate it but how is this any different than just going into TWRP and deleting (or moving directory) for the module in question?
[Magisk] coldgin_:
Well, here you have a menu with options... It's very much easier to use than a file manager, at least for the average Jhon.

Just MHO....

Regards.
[Magisk] oroboros74:
Average Joe here. Haven't used it yet, but definitely looks useful.

But I'd recommend you collaborate with OP here if possible...
[Magisk] VR25:
**2019.4.4 (201904040)**

- Complete redesign

- Magisk 17-19 support (including `uninstall.sh`)

- Toggle core only mode

- Updated information (copyright, documentation, and module description)
[Magisk] shouk_1987:
Great work man

Keep it up
[Magisk] culiacanazo:
This is the ultimate level of laziness any lazier and he risks a comma!

I've seen the date. What I have never seen is a zip request to avoid the strenuous twrp terminal
[Magisk] huangsijun17:
Thank you for the update.
[Magisk] fOmey:
If you ever consider adding a UI aroma would work great for this project.. If I remember correctly it supports shell commands..
[Magisk] simpang:
Someone pliss help me..wat shud i do now to make recovery mm work in my phone?i just a nubi.
[Magisk] ireneusz.irzyk:
/data/media/mm

Wysłane z mojego Redmi Note 5 przy użyciu Tapatalka
[Magisk] simpang:
I also do dat as shown as on the pic..
[Magisk] coldgin_:
You must add an space after the command "sh" as stated in the module's description in the magisk repository.

In your Pic is shown that you are writing it incorrectly.

Regards.
[Magisk] VR25:
Run */mm or /sdcard/mm or

sh /sdcard/mm.
[Magisk] simpang:
Yes bro,its work now..thx very much.

---------- Post added at 08:44 AM ---------- Previous post was at 08:43 AM ----------

Yes,thx bro..
[Magisk] amg314:
mm 2019.4.4 problem

I am using arm64 tablet under Oreo (microG, Xposed), Magisk 18.1, MM7.1.1

Failed to install mm 2019.4.4 using either Magisk Manager 7.1.1 or TWRP. In both cases, the mm flashing passed without errors.

However, in the TWRP terminal, I got the following error:

sh /sdcard/mm

mount: losetup failed 1

Manual says that losetup returns 1 if the device is not configured.

PS Version mm 2018.8.8.1 works OK.
[Magisk] VR25:
Do you get the same error after running mount /data/adb/magisk.img /mnt on recovery terminal?
[Magisk] amg314:
Thank you for your prompt reply.

For now, version 8.8.1 is fine with me.
[Magisk] wliu88:
i got this message

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

mm version 4.4

Magisk version 19.0
[Magisk] zimmerma379:
I’d like to install a Magisk module, but have seen reports of it sometimes causing bootloops. Therefore, I've installed the “Magisk Manager for Recovery Mode” here to protect myself -- and could use it to remove the offending module should it misbehave. The problem is I’ve (accidently) encrypted my phone -- which means “/sdcard/mm” and “/data/adb/modules” are inaccessible from TWRP and therefore I cannot use “Magisk Manager for Recovery Mode”. ;-(

Would another solution be to use a Magisk-uninstaller.zip? With Magisk completely removed, wouldn’t that prohibit ANY (including an offending) Magisk modules from running? Or will the Magisk-uninstaller.zip also fail because my phone is encrypted? Or can some Magisk modules still run (and misbehave) even after removal of Magisk? Damn that Android auto-encryption!
[Magisk] CanMan1:
Create the file .disable_magisk, and place it in /cache to enabled Magisk core mode (no modules loaded). Then boot, disable the bad module, and disable core mode in Magisk manager.

Instructions from official Magisk troubleshooting
[Magisk] zz358840:
me too.

but,I have two devices,xiaomi mi9 and google pixel 2.

mm and Magisk version is same,why xiaomi mi9 not support?

mm version:4.4

Magisk version:19.1
[Magisk] Ulf3000:
works fine on galaxy s7 exynos .. use */mm .. thanx to the op , really important utility
[Magisk] zimmerma379:
Thanks!

Thx! -- this looks like a nice solution! I'll check it out...
[Magisk] VR25:
...But you didn't answer the question... :confused:

I'll be working on updates soon. Installation logs would be greatly appreciated!

Wrong place for this kind of question...

Head to the Magisk support thread.
[Magisk] Schroeder09:
Edit: ignore and delete post please.
[Magisk] arddy1:
Is your data encrypted? This module wont work if your phone is encrypted and the twrp doesnt support encryption. Currently there's no encryption supported twrp yet for Mi 9
[Magisk] Bblatt:
case sensitive

can you make not case sensitive
[Magisk] VR25:
Sure, but this can potentially reduce the pattern matching effectiveness.

Nevertheless, what's you reasoning?
[Magisk] Lusty Rugnuts:
Just FYI...

Blu Life One X3 phone, Nougat 7.0.04.13, TWRP 3.2.3 bootloader, Magisk 19.2 root.

I tried all the variations on the command to get mm running in TWRP Terminal mode, but none worked. I kept getting 'mm: not found' error.

So I searched for the file, and it's at /data/media/0/mm.
[Magisk] wliu88:
my issue resolved by new update of recovery, there's nothing wrong with magisk or mm itself.

the root cause is previous recovery didn't decrypt data partition properly, it's working now after new recovery updated.
[Magisk] VR25:
Have you tried running "sh /data/media/0/mm"?

If that path exists, it's odd that /sdcard/mm doesn't.
[Magisk] Lusty Rugnuts:
No, all I have to do is go into TWRP terminal, and enter "/data/media/0/mm", and it runs... the instructions in the original post showed "/data/media/mm", but I'm running my Android 7.0.04.13 single-user (no guest mode, no adding users) via a Magisk module, so it adds a '0' (ie: the user is 0) to the path.

I wanted to let others know that mm might not be where the OP says, so trying to run it from the OP's instructions wouldn't work.
[Magisk] jc1266:
Hi all , I have done everything ..can someone teach how to romove modules ,, pls need help , thanks

What should I type ..? Thanks pls help
[Magisk] VR25:
According to the OP, the latest version's path is actually /data/media/0/, not /data/media/. An alternate path is /sdcard/mm - meaning, you can also run */mm.

Input unique patterns that match the modules you want to remove, and press [enter].

e.g., xpo for xposed, xpo|vip|font for exposed, viper, and all fonts.
[Magisk] jc1266:
Will try later ..thanks for help
[Magisk] jc1266:
Hi , thanks for the help ,. And it is a good module , thanks again
[Magisk] srose sp:
Ok but where is enter no matter what i type or press its always says goodbye or quit
[Magisk] jc1266:
Hi May I know what is mm-master zip , what is for . If my phone already bootloop with some magisk module , can Iflash mm module zip from magisk repo .? To save from bootloop ?

Thanks in advance
[Magisk] VR25:
Not sure whether you're doing anything wrong or mm has issues. Please, upload multiple screenshots displaying what you're trying to do.

Thanks

It seems you donwloaded the repository's main branch (master) from GitHub. Flashing that won't work. Download mm from Magisk Manager.
[Magisk] dani971989:
HELP

HELP

my phone got bootloop after process smali patcher coz my bad signal now i'm flash again my phone, please help me https://drive.google.com/file/d/1OGkb1bnLo1EYcrUTcVExZzL8IvWitwj6/view?usp=drivesdk
[Magisk] VR25:
If that's a Magisk module, you can disable/remove it with mm and your system will boot again.

1) Install from recovery

2) Run */mm on recovery terminal and follow the wizard.

If that Smali Patcher variant is not a Magisk module, this is the wrong thread.
[Magisk] iamMG:
Just dropping by to say: Thank you! Saved my device from bootloop problem. :)
[Magisk] dani971989:
Help me my phone got bootloop 2times, i can't trying again coz https://drive.google.com/file/d/1OGkb1bnLo1EYcrUTcVExZzL8IvWitwj6/view?usp=drivesdk[/QUOTE]
[Magisk] raosahab:
[2019.4.4] Magisk Manager for Recovery Mode (mm)

What is (mm) here does is directing to Android 6.0 marshmallow users ?
[Magisk] Wolfcity:
You have to ask the developer to get an exact answer but as this module is a magisk manager for TWRP and the command to use it is "mm" I would think it stands for.... magisk manager.

It has definitely nothing to do with android 6.
[Magisk] raosahab:
Ok but without confirming I don't want to flash because if something gone wrong I have to flash rom again that I does not want.

BTW thanks for your help.
[Magisk] VR25:
Wolfcity gave you the answer. ;)
[Magisk] raosahab:
Ok Bro Thanks for your help. I flashed it and done well.
[Magisk] houston_:
Hey there, just wanted to test this module, since I will try to install a module that normally bootloop my device.

But in twrp I try to run the script by typing "sh /sdcard/mm", but it is not found.

Taking a look into the mount options, I can't find my /sdcard either. Trying to use the "select storage" button, I see a "0MB" Partition. If I press the /sdcard there, nothing happens.

Do I need to mount my /system r/w? (Tried it, but seems not to work)

My device is a unlocked cubot x18 plus, treble enabled but stock, Android 8.

TWRP 3.2.3 is installed (by twrp builder, unofficial). Latest Magisk version 19.x.

No boot-pin enabled, but don't know if my internal memory is encrypted, TWRP won't ask for any key on bootup.

Any ideas?

If I flash this module with twrp, I need the /data partition to be mounted? (another thing that won't work, I guess...)
[Magisk] VR25:
/sdcard/ should point to /data/media/0/. So, try "sh data/media/0/mm". Obviously data must be mounted. Magisk modules are stored in there, too. If you still can't run mm, extract it manually to any data folder and run it as "sh /path/to/mm".
[Magisk] OmegaMode:
Also stopping by to say thank you for this. Saved me from a format phew :victory:
[Magisk] Triviox:
Thanks! I used it in Galaxy S5 with TWRP, now im in Xiaomi A2 and didnt install TWRP.

Could i use this module in fasboot? Or only works in custom recovery? Thanks!
[Magisk] Babad00k:
Only in Custom Recovery!
[Magisk] delevic:
I was looking for something like this. Excellent job!
[Magisk] Sage:
magic! (isk) :D
[Magisk] debmaj2:
I guess a lot of functions have been stripped off in the latest update with Magisk 19.3 . I see only Core Only, Remove and Disable (and another option on the top of the list).
[Magisk] satyajeetb:
donot work for devices with encrypted internal storage

as my device is encrypted and there is no workaround for decryption as of now.

Following step dont work due to lack of access to internal memory(sdcard) from recovery. " First time (right after installing/updating) - run `mm` or `sh /sdcard/mm` on recovery terminal." pls do something to bypass dependency on internal storage for encrypted devices.
[Magisk] Chmouf:
Same menu on my Samsung S8+
[Magisk] pingopower:
does not work with Magisk 19/App. hiding since magisk.img is obfuscated.

losetup fails to find the image
[Magisk] th3_jok3r:
I use mm but after select the module with R I press enter twice and nothing happens, I tried uninmod tôo but got I cant mount img
[Magisk] Wolfcity:
That's because the 19.x magisk builds are working without any image. You can remove modules by different methods. Take a look here:

https://www.didgeridoohan.com/magis...agisk_functionality_bootloop_loss_of_root_etc
[Magisk] fiction.ee:
Thank you so much for this module! This module has saved me a lot of time, especially after installing other modules and encountering boot loop.