yashsingh1/xdaforums huggingface dataset:
[Magisk] Didgeridoohan:
Is that the full installation log? What happens if you try from recovery? Do you have the same issue with other modules or is it just that one (which happens to be abandoned, by the way)?

There's a bug in the Magisk Manager where it sometimes shows MagiskHide as enabled even if it's disabled. You can confirm if it's enabled or not by running the following through a terminal emulator:

su -c magiskhide --status

Only work with apps that detect root and actually need to be on the Hide list (you might create more issues otherwise).

I think I've seen a couple of reports like this previously, but you'll have to be more specific and give some more details. And logs if possible.

https://didgeridoohan.com/magisk/MagiskHelp

As far as I've seen you've asked about help with hiding the Magisk Manager, right? For anyone to be able to provide any more help you're gonna have to be a bit more detailed though. Take a look here for some info about what kind of details (and logs) to provide: https://didgeridoohan.com/magisk/MagiskHelp

It might be detecting root apps you have installed or something about your ROM. More details on hiding root from apps: https://didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps

There's been some issues with bootloops and booting to recovery after updating to Magisk v18, but the only thing you should have to do to make the device work again is to restore a stock boot image. Magisk itself only ever touches the boot image, so if you've restored that the device should boot. The fact that it doesn't likely means that there is something else going on.

Your issues sound device specific, so I would start looking for advice in forums relating to your device. You might have a better chance of getting help there...
[Magisk] 气人小萌新:
thanks
[Magisk] dope77:
Ye that's the full log. Magisk isn't working properly at all on my j6+. Can't do anything except giving su permission. Modules always fail to install, each time I get a new error. Can't update magisk through manager (everything works just fine from twrp), magisk hide not working.

This is another log when downloading a module

- Copying zip to temp directory

- Installing Collective_Dolby_Atmos®-v1.7.9.zip

Archive: /data/user/0/com.topjohnwu.magisk/cache/install.zip

inflating: common/unityfiles/tools.tar.gz

inflating: common/unityfiles/util_functions.sh

Killed

! Installation failed

This is log if I try to update magisk through the manager

- Detecting target image

- Target image: /dev/block/mmcblk0p23

- Device platform: armeabi-v7a

- Existing zip found

- Extracting files

Killed

Killed

Killed

- Unpacking boot image

Killed

Killed

Killed

- Checking ramdisk status

- Patching ramdisk

- Repacking boot image

Killed

! Unable to repack boot image!

! Installation failed

As I said before, everything works fine if flashing is done through recovery
[Magisk] wych42:
Problem solved by downgrade magisk from v18.0 to v17.1 using custom update channel in masgik manager's settings.
[Magisk] Didgeridoohan:
[MENTION=9356964]dope77[/MENTION] I would guess that your device or ROM is shipping with some broken tools that are needed for module and Magisk installation to work properly. Probably not much to do except try a different ROM, maybe...
[Magisk] Harlock1978:
I add the log as requested.

Should I install a Canary Version?
[Magisk] Soumy1234:
It seems that everytime I install a new module, some other modules disable on reboot like greenify and xiaomi camera. I have to reboot again to enable all modules. I've attached the Magisk log
[Magisk] Didgeridoohan:
Even the verbose debug logging would probably not show anything in this case. What we're interested in is what's happening to the app that you try to hide root from, and for that you would need at least a logcat.

I did try the Banking app you have on the hide list in your log and on my device it starts just fine even when it's on the Hide list. That suggest that it's something about your setup that has issues. But what? No idea...

The Magisk log won't show anything about that, especially a non-debug one where you're not installing any modules...

You do have a LOT of modules on there though, running a whole host of scripts and magic mounting files left and right. It's not strange that even a slight hiccup during boot would make one or more modules not work as expected.
[Magisk] Klusio19:
Fast question. After uninstalling Magisk via Magisk App Manager, files in my smartphone are in the same condition like in new phone? Or after uninstalling via app, I need to delete something on root path?

If it's noob question, I'm sorry because I'm noob ;)
[Magisk] Didgeridoohan:
Magisk in itself will leave your device untouched when uninstalling so there's no need for any cleanup afterwards. But, there's always a chance that an app with root access or a Magisk module have done alterations to your device. That can be really hard to know if it is the case though...
[Magisk] Didgeridoohan:
I had to look up what the -d option is, but I don't think you want that one... :laugh:

-d	Dump the log to the screen and exits.

Other than that, using '-v long' should be good. I'm not gonna give any kind of promises that I can read anything from it though. The inner workings of Android is not my forte...
[Magisk] Klusio19:
Thanks for answer. I've got FK manager app, Servicely, and Naptime which need root. I haven't installed any modules without that one stock.

Any of them can do alterations, or you don't know ?

Thanks you.
[Magisk] PWn3R:
I have a device with a boot image that gets detected as "Magisk patched boot imaged detected" on an image straight out of the signed OTA. I tried disabling the checks in the scripts and flashing again from TWRP, but the device won't boot. I'm happy to provide the IMG for science. Anyone else got any images? Device in question is Xiaomi Mi Mix 3, software is the leaked global OTA file.
[Magisk] Soumy1234:
I see. At least I got an explanation. Thank you!
[Magisk] yuri-rus:
There was xiaomi eu stable 10.1 updated without wipes to stable xiaomi.eu_multi_MIPAD4_V10.2.1.0. I put back 18 Magisk, but the system section remains only for reading and file managers do not translate to write. At 10.1 everything was stable, what can be done, or should we roll back to 10.1?
[Magisk] naxil01:
Magisk on honor-7a aum-l29?

Hi. It is possible install magisk on honor-7a aum-l29? This device need to be unlocked?
[Magisk] Didgeridoohan:
[MENTION=3292224]franciscofranco[/MENTION] fanboy, huh? :D I don't think they should do any harm to your /system partition, but they might have changed some of the default values for doze, etc. I'm not that familiar with how they actually work to say anything for sure though...
[Magisk] Saswata Chakraborty:
Most probably a silly question.

Does Busybox (magisk systemless module) slow down the device anyway?

Sorry for asking here.
[Magisk] RandomPooka:
I've often wondered why people are installing busybox. I'm assuming that they have apps that specifically need it, but I have no idea what apps actually do require it.

So, any insight? Why are those of you who are installing busybox actually installing it?
[Magisk] zeduck:
I still have problems when trying to install Magisk 18 with encrypted LG G4 device.

Firstable, I submitted an issue on bug tracker of the ROM I use.

Developer investigated but finally concluded that it could be a Magisk issue.

More details in this issue: https://github.com/Suicide-Squirrel/issues_oreo/issues/13
[Magisk] coolman7:
To brick or unbrick the phone can be device specific. It is ok. But what should be done to prevent from bootloops after upgrading Magisk for my other devices or future uprades to Magisk? Should I always upgrade from TWRP can prevent these kind of bootloops? Which one is safer to install or upgrade Magisk? From TWRP or from Magisk Manager?
[Magisk] Didgeridoohan:
Not quite an answer to your question, but I've started making it a prerequisite for users of my MagiskHide Props Config module to install Busybox. Previously I would either use Magisk's built-in Busybox, but that doesn't contain all the proper applets anymore (binary size reasons) and sometimes would bug out when [MENTION=4470081]topjohnwu[/MENTION] was experimenting, or simply bundle Busybox with the module. Quickly got annoying so now I just make it a prerequisite to install Busybox (preferably [MENTION=4544860]osm0sis[/MENTION]), simply to make sure that all scripts work as expected on different devices and setups.

There likely wouldn't have been any difference installing the update from TWRP, but it's hard to know now... Some people always update from TWRP, simply because they've had some mishaps with the direct install from the Manager on previous occasions. I don't think I've used TWRP to install Magisk for probably a year or so on my daily driver, and I help testing the new builds.... Anyway, I'll try to stop rambling.

You won't get any assurance that things won't go wrong when installing a new version of Magisk. There are quite a few of us helping out with testing new builds and the Canary builds are quite popular. Some issues are caught like that, but there are only so many of us and the number of different Android devices out there are mind boggling. It's simply impossible to know how all different devices will behave with a new update...

The important part when messing with and modding devices like we do is to always have a backup of any important data (if applicable) and a method to recover when things go wrong (because eventually they will).

Edit: I think I failed on the rambling part... :D
[Magisk] tomhopus:
please help, application com.grabtaxi.driver2 can detect the magisk, can you fix it?

sory for my bad English
[Magisk] Klusio19:
(It's my first device with franciscofranco apps, because I heard they are nice :D)

Hmmm. I think we don't understand each other :D. I mean, do I need to remove something manually after uninstalling Magisk in / path. Not /system path. (Because if something is wrong in /system, I can just wipe system and flash ROM via TWRP again , right?)

Do I need to remove something in this path in screenshot, my question is.

Thank you very much for answer again.
[Magisk] Didgeridoohan:
No. Everything Magisk related is stored in /data/adb and that'll be removed when you uninstall.
[Magisk] danlivesey:
I can get magisk running good with root but I just can keep my data from being encrypted, I flashed the no verity zip after a full wipe by trying yes then flash the no verity zip 6.0 and it works and I can do a custom back up and stuf with twrp and all is good, even after 10 reboots but as soon as I flash the magisk it breaks the no verity zip and encrypt again. I've tried full wipe coming straight from stock by odin then flashing the no verity zip and booting up after it then back to recovery and flash magisk but still doant work. I've looked every were but can't find a solution. I've also tried a zip called remove encryption and it works 4ight up until I flash magisk. My phone s7 G930F UK stock 8.0 twrp 3.2.3 magisk 18.0. I only want to use Santander app haha all this for that
[Magisk] LonePaladin:
It looks like I'm in a small minority -- trying to install Magisk on a Lenovo TB-X103F. Ultimately, I hope to have root access and have the Resurrection OS on it. One step at a time.

I've installed TWRP (after a couple false starts), v3.02 made for this tablet. When I try to install Magisk v18, it gives me this:

Updating partition details...
...done
Full SELinux support is present.
MTP Enabled
Installing zip file '/sdcard/Magisk-v18.0.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
************************
* Magisk v18.0 Installer
************************
- Mounting /system, /vendor
- Target image: /dev/block/mmcblk0p20
- Device platform: arm
- Constructing environment
- Unpacking boot image
- Checking ramdisk status
- Patching ramdisk
- Repacking boot image
! Unable to repack boot image!
- Unmounting partitions
[COLOR="Red"]Updater process ended with ERROR: 1
Error installing zip file '/sdcard/Magisk-v18.0.zip'[/COLOR]
Updating partition details...
...done

Here are the contents of the recovery log:

https://pastebin.com/hZZBD3A3

(I only just signed up, so I can't post that as a regular link.) Let me know if you'd rather get it a different way.
[Magisk] Klusio19:
Ok, thank you do much for support.
[Magisk] zeduck:
Was my message noticed?
[Magisk] VSHD:
I flashed safety net universal fix module and magisk got uninstalled.I flash it through twrp,it doesn't get rooted.any help?
[Magisk] lucki1000:
Hello I have a Moto g5 Cedric on aex (pie ROM) and I installed magisk 18 and now I get an message that magisk not usable and I should install the additional setup but if I press install it's failed.

Can anyone help me?
[Magisk] guest4711:
Probably MagiskManager.apk is not installed. Extract it from magisk.zip and install it by hand. If that fails look into the logfiles or post the relevant parts (as attachment, please).
[Magisk] McMannes:
i cant activate mobile pay after my bank's app update. App is always seeing my root. Can anyone help me? Thanks.
[Magisk] guest4711:
You could try [MENTION=4667597]Didgeridoohan[/MENTION]'s "Magisk Hide Props Config" module to help hiding the Magisk (hiding MagiskManager by repacking is already done, isn't it?). You should also read his fine "Magisk Trouble Shooting Guide" with many good ideas.

https://www.didgeridoohan.com/magisk/MagiskHelp
[Magisk] lucki1000:
Worked thanks.
[Magisk] Didgeridoohan:
Two things to try:

Make sure that Magisk is set up to disable forced encryption: https://www.didgeridoohan.com/magisk/Magisk#hn_Disabling_dm-verity_and_forced_encryption

Flash the no-verity zip after Magisk.

Your TWRP probably isn't set up to handle the Magisk installation. I would instead try the patched boot image method (see the release thread for instructions) and then you can use TWRP to flash that.

Someone probably noticed it. If it's really a Magisk issue it might be a good idea to open up a GitHub issue instead. Just make sure to provide as much info as possible showing that it is actually a Magisk issue. Magisk generally doesn't have any issues with encryption (FDE or FBE), so it might actually be a ROM issue after all, but as far as I can see the info you linked doesn't give any clues as to what the underlying cause is.

Don't use that old thing. It is broken and as you've found it can mess up your Magisk installation. I have a module you can try that does pretty much the same thing and works in most cases: MagiskHide Props Config
[Magisk] regularmen:
there are no support thread for this module so apologize for asking this here, I have a questions

so first my phone doesn't support any external card filesystems other than fat32,

but the problem is that I have 128gb of card. I want to put a good use to it (storing large movies, fat32 only limits to 32gb)

apparently, I found a magisk module that seems I'm looking to, this is the one. I installed it, but after it reboots it ask for first boot password (which I did not set) the weird thing is when I typed just anything it confirms that password is correct then claiming that decryption is unsuccessful and it had to be reset.

this is my mistake, because I did not read the module documentation as it requires android 8.1 aosp like system (mine runs android one) and I don't know if it's an issue or not but all is fine after I restored the phone, module removal using magisk recovery module does not work.

I wanted this module to work with mine, what can I do?
[Magisk] LeandritoG:
History:

After I change the kernel I lost the root! Then I tried to update the Magisk to version 18 and the Magisk Manager to a most recent version that I don't remember its version.... But my phone continued without root.

Trying to solve this again I install Magisk 16.3 and Magisk Manager 5.6.4 downloading and installing the files available in this link: https://www.stechguide.com/download-magisk-v16-3/

Without success too!

-

So, darlings.

I'm asking for a tutorial to uninstall all the Magisk things of my phone (if you experts think it is necessary) and I'm asking for a tutorial to root again my phone with Magisk.

And I'm also asking to know the latest STABLE version of Magisk and of Magisk Manager COMPATIBLE with my phone and that will work well!

I have a Galaxy Note 3 (SM-N9005) with [ROM][C9 Pro Port][N900X] AspireTeam C9 Pro v5.0 [18.5.18][Aroma/Smooth/Modded] installed.

Thank you so much!!!
[Magisk] AndrzejDwo:
That's normal after updating/changing the kernel. The way I do it is flashing the newest Magisk uninstaller at first, than flash new kernel and than flash the newest Magisk. Works like a charm.
[Magisk] danlivesey:
If I was reading right I needed to put that code in the command in twrp? I did that and it cant find the file I tried both commands and it's the same. If I flash no-verity after I flash magisk then it breaks the zip and magisk doesn't get installed.
[Magisk] kiwigi:
Hi All, can someone explain why I have all of a sudden two Managers showing in the Apps ?

Could it be that the Titanium update has something to do with it? I haven't changed anything on Magisk since install except hiding Magisk for banking purposes a day or so ago.
[Magisk] jcmm11:
The other thing you can do is to patch the boot image and then flash the patched boot image.

Get a copy of your stock boot image. Start up Magisk Manager. Uncheck "preserve force encryption" and/or "Preserve AVB 2.0/dm-verity"

Now install Magisk using the "patch boot image" option and then install the patched image.

For the file method simply create a file containing the relevant entries

KEEPVERITY=false
KEEPFORCEENCRYPT=false

Use the TWRP file manager to place the file with the correct name (I suggest /cache/.magisk)
[Magisk] Didgeridoohan:
There are a few things I don't understand about your post:

Can't find the file? The command will create the file, so that doesn't really make any sense. Please clarify.

What do you mean by "breaks the zip and magisk doesn't get installed"? If you flash the no-verity after having installed Magisk, what exactly happens? Please clarify.

Edit: and provide the recovery/installation log if you're continuing to have issues.

Could be a few things that have gone wrong. Probably easiest solved by uninstalling both and installing the Manager again.
[Magisk] PWn3R:
Is there any way to try to patch an image from a computer rather than the device? I can provide the boot.img if you want, but the TWRP patch fails and installs a boot image that doesn't boot, and if you try it from the device itself, it detects as already patched, which it is not. Anyone got any ideas?
[Magisk] casouzaj:
Put your phone in fastboot mode whilst connected to your computer, run a command window and enter:

fastboot flash boot patched_boot.img

Note: if you run Windows, you might have to install minimal adb & fastboot.
[Magisk] PWn3R:
I guess I wasn't clear. I can't patch the boot image with the TWRP script or the app. TWRP flashes some jumbled mess that won't actually boot. The Magisk app hangs at the this is a patched image message and the destoys your battery unless you fc the app. The image is not patched and is straight from the signed OTA package.

I'm asking what else can I try, is there a process to try to patch the image from a computer? I'm guessing something needs to be updated in Magisk to make it work on this image.
[Magisk] jcmm11:
Mi Mix = emui 9? Try the Canary build.
[Magisk] PWn3R:
I'll try that, thanks, EMUI is not Mi Mix, Mi Mix is MIUI.
[Magisk] kiwigi:
[MENTION=4667597]Didgeridoohan[/MENTION]

Thanks. I'll see how that goes.

Other than that, all has been working flawless. :)
[Magisk] PWn3R:
Unfortunately, same problem, "Magisk patched boot image detected" when I try to use the Canary app.
[Magisk] jcmm11:
I suggest you get logs and post in the Canary thread
[Magisk] martyfender:
If you have Magisk installed, that is normal to see: "Magisk patched boot image detected". But it is not normal if it can't patch that image with the updated Magisk.
[Magisk] dbGHOST:
Is there any update to the detection mechanism?

About 7 hours ago I used Pay just fine, then 1 hour ago it failed.

Both ctsProfile and basicIntegrity show false right now.

Reflashed fullzip, ctsProfile false, basicIntegrity true; then flashed kernel and Magisk, ctsProfile false, basicIntegrity flase.
[Magisk] PWn3R:
It is not Magisk patched. I can't patch from TWRP or from the app on canary or release. I tried 17.3 and 18.0.
[Magisk] martyfender:
Well, that is strange then, you normally only see that message when the boot.img was previously patched in some way by Magisk.
[Magisk] firozpatel:
hi guys, i dont know if this happened to anyone else, but all of a sudden my google pay stopped working, magisk hide does work as some other apps are hidden and works fine, but just recently i tried to use google pay but with no success, ive set the app with my card details but when i try to use it, just not working, could this be a magisk problem?

im using magisk v18 with latest manager on op6 (9.0.3) with xxx rom and blu spark kernel

thanks for helping guys
[Magisk] Pitel:
ctsProfile suddenly false

Earlier this week, after christmas and new year holdiays, I flashed latest LineageOS and OpenGapps (and Magisk) and suddenly, ctsPtofile is false and I can't use Google Pay nor catch Pokemons. Anyone else has this issue?

Nexus 5X

LineageOS 15.1 20190114

OpenGapps 20190114 nano

Magisk 18.0 (core only mode)
[Magisk] Ninolina:
Same problem here. I have this message as on the screenshots.
[Magisk] ashyx:
According to your previous post you attempted to patch it with twrp.

Have you or have you not ensured that your firmware is complete untouched stock, in particular the boot image?
[Magisk] habylab:
Same here from me. Google Pay isn't working. Fails a safety net check in Google Pay.
[Magisk] Tulsadiver:
I have a question regarding Magisk. I use vrthemer's for flashing mods. I have a regular one for people that do not flash modules and one for people that do because now the magisk.img is what needs to be modified. My question is this: at what point does this change occur? There are modules that don't appear to trigger the change from system to magisk.img as some people install modules but the regular vrthemer works for. I'd like to be able to tell people which one they need to use. Any enlightenment would be appreciated. Thanks.
[Magisk] akxak:
The only way for me to solve this (OP 6, OOS 9.0.3) was a downgrade to Magisk 17.2. With that, MagiskHide worked again, Safetynet/CTR true and Google Pay working.

There is something seriously broken with the new hide approach in 18.0
[Magisk] kaizokan:
I was thinking whether it would be possible to have Magisk's superuser as a stand-alone app. To keep things clean and simple I rather not want to install both Magisk and Xposed (which i only need for the XPrivacyLua module) while still using the open source Magisk superuser : )
[Magisk] castlekeep:
the process of reflashing with a stock rom and recovering from a softbrick are about the same right? they both require the same rom and odin but nothing else?
[Magisk] guest4711:
It's basically the same. And you need a good quality usb cable to make the connection to your computer... (beside of proper drivers).
[Magisk] jcmm11:
Like I said I don't do Samsung but I would guess the answer to both questions is yes (with a slightly higher certainty for the first question). But I'd just go with what@guest4711 said.

The one thing I'll add (since it seems you want to try this ?) I'd probably try patching the eng boot images first, although I'd try the stock images as well. I'd also go with the Canary build.

In any case good luck and let us know what happens!
[Magisk] raptorddd:
I do not use magisk hide don't need to hide root in apps.. but I need magisk 18.0 that work with certain modules.. but I don't like LOGD enabled.. is there a work around to have logd disabled and not use magisk hide.?? In 16.7 logd disabled works ok. But recent modules requires magisk 18.0 to be installed..