yashsingh1/xdaforums huggingface dataset:
[Magisk] Turbopuschel:
I think I understand what to do and how to do it. But it didn't help.

First, I uninstalled Magisk again, extracted the boot.img from a flashable stock ROM .zip file and flashed it via fastboot (command: fastboot flash boot PathToBoot.IMG). Result: no boot.

Then I flashed the stock ROM via the Xiaomi flashing tool without it deleting data (I think that's what you meant by dirty flashing...?). Still no boot.

I can only boot after installing Magisk again.
[Magisk] Didgeridoohan:
In that case it might be a dm-verity thing or something like that. Not my forte...
[Magisk] jenslody:
Can you run

find / -name "magisk*.img"

in the TWRP terminal ?

To get a recovery-log click on "Advanced -> Copy log". TWRP willtell you where it places the file (normally to the sd-card).
[Magisk] thebrainkafka:
Do I need additional AdBlock (adaway) when using magisk? Or is it build in magisk?

Thx
[Magisk] Ex_FallenSkyTear:
is normal that lineage don't find magisk root...?
[Magisk] kojak1989:
Hi, i'm on LG G6 and Fulmics 2.1 ROM and I think that modules doesn't work for me because I installed Product Sans font module and nothing happened any ideas why ? I have latest version of Magisk.
[Magisk] Matteo Bertocchi:
What do you mean? Do I have to tell you where the exact problem is, in order to gain help?
[Magisk] Pkt_Lnt:
Unless we have your device (and not one else says that do) then logs are the *only* way to troubleshoot. Get a Recovery log to start. To get a recovery-log,flash the Magisk zip, then immediately in TWRP click on "Advanced -> Copy log". TWRP will show you where it places the file (normally to the sd-card). Copy that file and link it here or on something like pastebin.com and link it here.
[Magisk] Didgeridoohan:
You can activate Systemless Hosts in the Manager, but you'll need to use an app or module for the actual adblocking. The Unified Hosts Adblock module by [MENTION=6037748]Zackptg5[/MENTION] works really well. You can install it through the Downloads section of the Manager.

Don't think so. There are plenty of reports of it working on Lineage.

If you've only tested that one module, it's hard to say anything for sure. Try other modules as well, especially ones that install an app or a script that can be run from a terminal emulator. Easier to know if they work or not... And logs are always useful when asking for help (magisk.log, magisk_debug.log, etc).
[Magisk] DeathHacker:
Am I the only one with the problem that su -p doesn't actually preserve environment variables? I made a bug report on the Github repo, but it seems the issue tracker was removed.

Every time I try using either -p, -m, or --preserve-environment it doesn't actually keep them.

Tested with Magisk 13 through 1437 beta, none of which worked.
[Magisk] hassan_eldhraawy:
I'm not sure if this is the correct place to post this issue but I almost losing root everyday!

I'm on Resurrection remix nougat on max hydrogen and installed latest magisk and latest magisk manager , searched though and find that it's a common problem with magisk hide which I'm not using .. any fix for this annoying problem?

Thanks in advance
[Magisk] beavis5706:
Ran find / -name "magisk*.img" and this is what I get:

find: /sys/kernel/slab/L2TP/IPv6: No such file or directory

find: /sys/kernel/slab/L2TP/IP: No such file or directory

/data/magisk.img

/data/magisk_merge.img

I have attached my recovery log
[Magisk] Didgeridoohan:
I remember that one... Have not heard about it since.

Since the issue tracker got removed (was simply getting to cluttered with nonsense to be useful), could you post the details here so we can pass it on to [MENTION=4470081]topjohnwu[/MENTION]?

"Latest" is such a vague term. Version numbers are much more useful...

If you haven't already, give the v14.3 beta a try. And have you actually disabled MagiskHide in the Manager settings? It's enabled by default...

That recovery log looks like it's saved from another instance than the one where you're actually trying to remove the module. You'll have to save the log right after...

And what about the info I asked about earlier?

https://xdaforums.com/apps/magisk/m...systemless-t3432382/post74454906#post74454906
[Magisk] DeathHacker:
Certainly.

The problem is this: there is an option called --preserve-environment present in the MagiskSU binary. It's decribed as an option that will keep the prexisting environment (for example, TERM, which otherwise I have to set manually after).

Expected:

$ export TEST=testvalue; su --preserve-environment
# echo TEST: $TEST
TEST: testvalue

Got:

$ export TEST=testvalue; su --preserve-environment
# echo TEST: $TEST
TEST:

I have tried this with lots of SU implementations, including MagiskSU versions 13 to 14.3 beta, phh's SU, and Lineage's addonsu, all resulting in the exact same behavior. (They all share a common root SU implementation)

My current workarround is a wrapper, dumping the environment to a temp file, su'ing into a root shell, and "loading" the previous environment from that temp file.
[Magisk] tyty23:
My phone Redmi note 3 pro not sure why and how after installed a YouTube background play module from magisk and when i rebooted my phone all modules that was installed gone and I try to reinstall but seems like it's processing for every install and come out with those log but when rebooted still nothing has happened ,Can anyone please tell me what is happening?Thank you
[Magisk] IamIrene:
after I updated my stock rom, then flash with magisk 14.0

sometimes it can't pass the safetynet

but is working after few restart

this issue didn't happened at all for my previous stock rom

should I flash the latest magisk beta 14.3?
[Magisk] royal_eagle:
Hi guys,

Someone have any issue with Airwatch after updating to the last version 14.4?
[Magisk] beavis5706:
OK I'll run it again. No clue how I would find magisk.log and magisk_debug.log or my magisk image. I am totally new to magisk.
[Magisk] teddy0209:
14.4? It hasn't been released as far as I know... Except if your talking about a closed beta, unofficial beta, or the release for pixel2's...
[Magisk] royal_eagle:
I got it from the app it self afyer upgrading to 5.4.1, so after reading you, i understand now that it's not an official version.thank you mate
[Magisk] dr.bathman:
[MENTION=4470081]topjohnwu[/MENTION] request.. kindly add compatibility of magisk to dual boot patcher. Thank you.
[Magisk] beavis5706:
Here are the correct recovery logs. There are two of them. Recovery1 is running Mount Magisk and deleting Greenify4Magisk module via file manager in TWRP. Recovery2 is running Greenify4Magisk_Uninstaller_v2 found here https://xdaforums.com/apps/magisk/module-greenify4magisk-t3606277.

Let me know where to find magisk.log, magisk_debug.log and my Magisk image and I'll post those.
[Magisk] Didgeridoohan:
Those logs seem normal...

Try this:

Use the Mount Magisk script in TWRP and add a file named remove to the Greenify4Magisk folder (simplest way is to just rename the auto_mount file).

Boot up and see if things are back to normal. If not, you'll find the Magisk log in /cache and the debug log and Magisk image in /data.
[Magisk] beavis5706:
I fixed it!

I tried what you said but that didn't work. So I went to gather up the magisk files but I couldn't find the debug log so I did a search and came across two Greenify4Magisk folders. I can't for the life of me remember where I found them because I can't find those same folders again but I swear one them was in /dev/source and the other/dev/target.

Either way I moved them to my sdcard, rebooted and viola! Everything in Magisk now working properly. Thank you so much for your help.
[Magisk] beryindo:
error redmi note 3 snapdragon

error redmi note 3 snapdragon

./enable
./enable[15]: /dev/busybox/ps: not found
MagiskHide: Removing dangerous read-only system props
MagiskHide: Killing com.google.android.gms.unstable
./enable[65]: /dev/busybox/ps: not found
MagiskHide: Starting MagiskHide daemon
./enable[68]: /magisk/.core/bin/magiskhide: not found
[Magisk] beavis5706:
Interesting Magisk discovery

I had the same problem I had earlier but with a different module. This time the Dolby Atmos Lenovo A7000 [6.5] Atmos (1.1.4) plugin. Installing the module caused the list of installed modules in magisk manager to disappear, broke SafetyNet and I was unable to uninstall the plugin by any available means.

This is when I discovered something. Normally the plugins reside in /magisk. However when a bad plugin is installed the plugins now appear in two folders, /dev/source and /dev/target and no longer appear in the /magisk folder. This applies to all plugins, even the ones that worked before. All the plugins that were in /magisk are now in /dev/source and /dev/target. Deleting the bad plugins from /dev/source and /dev/target cause the working plugins to now reappear in /magisk and upon reboot the source and target folders that were in /dev are no longer there. This is why I couldn't find them earlier in my previous post.

This is why installing a bad plugin causes the module list in magisk manager to be empty. The plugins are somehow moved from /magisk to /dev/source and /dev/target and now magisk manager cant see them. This is why every uninstaller for a bad module doesn't work. It's looking in the wrong places.
[Magisk] seshanth:
Magisk beta v14.3 :

It shows unable to patch boot image .But v14.0 installs without any problem. Does this mean this device will not be supported in next updates. :(

Thanks...
[Magisk] moozer:
Rooted okay, but getting these errors on safetynet check. What am I missing?
[Magisk] Younex:
If I understand correctly, Magisk DISABLES forceencrypt ?!

Because the OP states otherwise, or at least, is very vague...

"Remove dm-verity, forceencrypt, unlock partitions blocks to support remount to rw"

What magisk does : it removes dm-verity, it forces encryption = it forceencrypts, and it unlocks partitions blocks...

If instead,

magisk disables forced encryption, it should say :

"Remove dm-verity, forceencrypt, AND unlock partitions..."

Or "Remove dm-verity, forceencrypt. Unlock partitions..."

This is just my opinion :)
[Magisk] Pkt_Lnt:
1 - we have no clue what device you have, how can we know if your device is / will be supported?

2 - no logs, no way to troubleshoot

Upload logs - recovery, Magisk, Magisk debug

Upload stock boot image and the failed patched one
[Magisk] Didgeridoohan:
You'll need to bring a lot more details than that if you wan't help... From the short log snippet you posted it seems like you're using an old version of Magisk, or?

Anyway... Proper logs and more details needed.

It'd be really nice to see that magisk.log and magisk_debug.log...

https://xdaforums.com/apps/magisk/guide-magisk-troubleshooting-t3641417
[Magisk] derAndroidler:
I don't know, why you should remove force encryption?!? I think encryption is good for your security?!? :confused: :confused:
[Magisk] Didgeridoohan:
Disabling the forceencrypt flag is not the same as removing encryption. It just gives you the option to use your device without encryption if you want to. Some people do...
[Magisk] derAndroidler:
That's interesting. 14.3 is still beta and 5.4.0 is actual. Where did you get these strange versions :confused:

---------- Post added at 17:30 ---------- Previous post was at 17:28 ----------

But why it's the default option then :confused:
[Magisk] Didgeridoohan:
There was a Manager v5.4.1 and Magisk v14.4 released specifically for the Pixel 2 XL, just to let Pixel 2 XL users root their phone. Users with other devices have used that test release as well, with mixed results.

Just so you have the option. You don't have to do anything with it and can even keep the forceencrypt flag enabled if you want to...
[Magisk] bagajohny:
Unable to pass safetynet. Any suggestions?

Here's logcat
[Magisk] andynx1:
Curious.

Moto G5+, LOS15, Magisk 14.2 installed, manager 5.4.0, everything working perfectly.

I tried to let magisk manager install 14.3, and it failed to install. So, I downloaded v14.3 and flashed with TWRP. The result is that I'm no longer rooted, and magisk is no longer installed, yet I pass the safetynet check:

(where are my log files?? don't know where to find them)
[Magisk] andynx1:
OK, I found the log file. But my XDA app won't let me attach it to a forum post... :(
[Magisk] DodoGTA:
Rename its extension to .txt
[Magisk] Pkt_Lnt:
www.pastebin.com and provide the url link here
[Magisk] Ex_FallenSkyTear:
mine too, if a file is in a external sd, transfert log file in a internal memory for fix.
[Magisk] andynx1:
https://pastebin.com/f33L5qhy

My debug log...
[Magisk] Pkt_Lnt:
I see nothing about 14.3 in there only 14.2 (unless someone sees something I missed)

How about flash 14.3 again in TWRP and immediately get the recovery log and post that?
[Magisk] andynx1:
OK. Did the same again (flashed v14.3 from TWRP), same result.

I deleted the old debug log, so this is a new one. But, in order to access it, I had to restore my (v14.2) nandroid - to gain root.

https://pastebin.com/GCwfZ71Z

Edit: doh! seems to contain info about v14.2 again, not the failed v14.3 flash.
[Magisk] Pkt_Lnt:
Second log is the same as first with no magisk 14.3 info.

We need to see the recovery log.

Flash the Magisk zip, then *immediately* while still in TWRP click on "Advanced -> Copy log". TWRP will show you where it places the file (normally to internal storage). Get us a link to that log.

Do not boot back to the system after flash, immediately find and save the log in twrp.
[Magisk] andynx1:
Hey, I *really* appreciate your help!

https://pastebin.com/CpEDPt86
[Magisk] Dauntless:
I'm trying out the following extension:

https://github.com/TheCjw/Magisk-Frida-Server

The module correctly loads (after commenting the permissions for debug_server), but these files are then mounted to /magisk/Magisk-Frida-Server/system/xbin. How can I link them to /system/xbin? I can't execute them from within /magisk/ mount.

How should a module add anything to /system/xbin? This doesn't appear to be a typical use case? Is there any documentation about how the magisk mount works exactly? The github documentation isn't really helping me on this.
[Magisk] Didgeridoohan:
That's how Magisk modules work... They Magic Mount whatever is in the module's system directory (/magisk/<module name>/system) to /system.

Useful documentation:

https://github.com/topjohnwu/Magisk/blob/master/docs/README.MD

https://github.com/topjohnwu/Magisk/blob/master/docs/module_repo.md#magisk-module-format

---------- Post added at 23:10 ---------- Previous post was at 23:10 ----------

Have you tried a clean install of v14.3, rather than trying to update?
[Magisk] Pkt_Lnt:
Nothing really stands out to my limited knowledge to this, maybe one of the real pros can see something more. DodoGTA , jenslody, Didgeridoohan

I did see this:

- Flashing new boot image
cat: write error: Broken pipe
- Unmounting partitions
- Done
I:Updater process ended with RC=0

So you have the same no root and 14.2 installed? Guessing if so you had to restore a nand to get it working again?
[Magisk] Dauntless:
That's what I thought. So why do the files exist in /magisk/Magisk-Frida-Server/system/xbin, but they don't exist in /system/xbin? I'm trying to access them from adb under su.
[Magisk] andynx1:
Thanks... as Didgeridoohan said, probably better to uninstall and start again.

But, as my current setup on v14.2 works just fine (and I erm don't know what I'm doing!), I'll wait until I need to install the latest version - then clean install.

Thanks again.
[Magisk] Veid71:
Whenever I install anything from magisk it says successful but then nothing pops up in my modules even after restarting anyone have any advice?
[Magisk] exodius48:
Error negative download progress

[MENTION=4470081]topjohnwu[/MENTION] I get this error download progress while downloading dolby atmos le eco module. Probably error caused by downloading big file.

RR 5.8.5 final, magisk 14.0, magisk manager 5.4.0
[Magisk] srose sp:
Why some modules like magiik charging switch installed but not showing anywhere except magisk module?
[Magisk] bagajohny:
Can anyone help me with the safetynet problem? Am I missing something? I have attached the log file.
[Magisk] jenslody:
Because some modules only work from a console, e.g the great "Unified Hosts Adblock", the "Terminal .."-modules and (if I remember correctly) also "Magic Charging Switch".
[Magisk] jenslody:
This is known and fixed in newer (internal test and Pixel 2) versions and should only be a cosmetically problem anyway.

There might be other issues with downloading (and repackaging) zips on some (Samsung only ?) devices.
[Magisk] Didgeridoohan:
The module you linked is incomplete (no files under /system/xbin, no module.prop), so I'm assuming you're using an updated one? Is there an "auto_mount" file in /magisk/Magisk-Frida-Server/?

Logs would (as always when troubleshooting) be useful. Recovery log from installing the module, Magisk log, magisk_debug.log, etc.

Logs would be useful... A recovery log from installing a module would be a good start.

With some modules you'll have to run commands in a terminal emulator. There's usually something about that I'll the module instructions.

Nexus devices shouldn't have much issues passing SafetyNet. It all depends on your setup though. What ROM you're using, do you have Xposed installed, etc...
[Magisk] jenslody:
The broken pipe part is normally no problem, it happens because the cat-commands fills the boot-devices with zeros to be sure there is nothing left from previous installs.

If this appears in the log depends on the device/rom (e.g. it happened on stock MM on my J5, but not with the GZR-Validus I use now).

I would try a clean install as suggested before.

At least flash a stock boot-image and you can copy your /data/magisk.img to a safe place (external sd) before, so you can restore the modules from there (in TWRP) if you want, or if they keep stuff there like "Terminal Debloater" etc.

Before you (probably) restore (from) the old magisk.img, make sure it works without it.
[Magisk] bagajohny:
I'm using Tesla ROM nougat with no xposed installed. Clean flash.

Magisk v14.

EDIT : Everything is fine after flashing elementalx kernel
[Magisk] Pkt_Lnt:
[MENTION=2909700]andynx1[/MENTION] Here is more help as I had suggested earlier. I know you plan to do a clean install when ready, but keep this handy for when you try. And thank [MENTION=8340552]jenslody[/MENTION] for this too. :good:
[Magisk] Veid71:
ive been uninstalling it and reinstalling it so i dont have the logs anymore but now i cant even install it and boot into my phone, it just boots into twrp for some reason
[Magisk] Didgeridoohan:
No logs or details = can't help...

After flashing it in TWRP, save the recovery log and then hook up to a computer to get the log from your device.

To get out of a bootloop caused by the module you can either use the Magisk uninstaller script to remove Magisk altogether, or use the Mount Magisk script to mount the Magisk image and then use the TWRP file manager to remove the module folder under /magisk.
[Magisk] Veid71:
thanks I'm assuming the twrp boot loop issue was because i was flashing twrp right after flashing magisk ( i didn't do it this time and it allowed me to boot into my phone) but now I am still having the same issue i was before with magisk not actually installing the modules even though it says they were installed successfully even after reboot nothing show up in my modules section, but i have root access and can grant root permissions do you know where i can find the magisk log? im lookin in a file explorer and i cant seem to find it anywhere in the magisk folders, i know it has the one in the app but that doesnt give me much only like 10-20 lines and its only got like 2 errors in it that i dont think have anything to do with the issue one is

"bind_mount: /system_root/system -> /dev/magisk/mirror/system

fopen: /cache/magisk.log failed with 1: operation not permitted"
[Magisk] Didgeridoohan:
A recovery log from installing a module in TWRP would be useful and there might be a magisk_debug.log in /data that possibly could shed some light on things.
[Magisk] Veid71:
alright here they are thank you for all the help :)
[Magisk] Didgeridoohan:
The module you're installing is detecting that you already have the module installed. That particular module has a feature where if you flash the same version again, it'll uninstall the module. Possibly useful if you're experiencing issues... If you don't have the module installed already, I'd suggest going to the Unified Hosts AdBlock thread and ask for advice/report a bug. Make sure to include logs and lots of details about your setup.

Is that the only module you've tried? And you're using an A/B device, right (Pixel, maybe)?
[Magisk] Veid71:
no it does it with any module i try, ive tried to install the xposed one aswell and it does the same thing, i see that its downloaded if i use a file explorer and look in one of the magisk folders but it doesnt pop up under the modules for some reason and yes i am using the pixel XL

---------- Post added at 06:00 PM ---------- Previous post was at 05:29 PM ----------

hey i apologize for double posting but ive found something kind of odd... i think it might be a pathing issue, i see the magiskmanager folder under sdcard which has the modules that i downladed and installed, but i also see a magisk folder under system(root) in my file explorer that has remained empty, but when i moved the unified hosts module into it it popped up under my modules section, (im not sure if it works or not but atleast i can see it and activate or deactivate it, so is it not reading the magiskmanager file under my sdcard? also when i rebooted my phone it cleared out the module on my magisk folder but is still under my magiskmanager file and is no longer in my module section
[Magisk] Didgeridoohan:
So... Are you saying, that when you install a module, either through the Manager or in recovery, that it gets installed into the MagiskManager folder on your internal storage (sdcard)? Not just that the zip gets downloaded to that folder, but that it unpacks it to it's own directory and inside you have a module.prop file together with any other module files?

If that's the case there's something seriously weird going on. All modules should install in the /magisk directory you found under system. The MagiskManager folder should only contain the module zips that gets downloaded... Could you post the recovery log from installing a different module than the Unified Hosts AdBlock?
[Magisk] Veid71:
no i dont think it is unpacking them because they are still in .zip but ive attached the new recovery log, i also triedto install volume_steps_increase-14.0.0 and it gave me the same issue through twrp "system could not mount" then it gave an error, but when i downloaded and installed the greenify4magisk through magisk it says it worked fine but still no module in the modules section
[Magisk] Didgeridoohan:
Ok. No weird issues then...

The recovery log shows that system can't be mounted for Greenify4Magisk either. Making an uneducated guess I'd say it's a Pixel thing... Try the ViPER4Android FX module. It's in the Magisk repo (Downloads in the Manager) and is known to work on A/B devices.
[Magisk] Veid71:
nah it gave me the same issue in twrp, but i know it cant be a pixel issue because i used to have magisk with all these modules on it before
[Magisk] davidlikeandroid23:
I have a problem with magisk, it puts me that the cts profile is false but in the basic integrity it gives me true, how do I solve it?
[Magisk] Didgeridoohan:
So the question is: what changed? I guess it's time for a clean install...
[Magisk] DodoGTA:
The Magisk module attached to this post will most likely fix your issue (Or you can try Universal SafetyNet Fix but it's too big for this particular case)