yashsingh1/xdaforums huggingface dataset:
[Magisk] devsk:
Any update on this issue? This is kinda critical issue. Why does magisk need to depend on logcat for anything, when logcat can roll over?
[Magisk] Looki90:
Me too, even install the latest magisk 14.5 doesn't work.

Any clue??
[Magisk] Pkt_Lnt:
The very through and excellent Troubleshooting guide by Didgeridoohan has some info to try.

https://xdaforums.com/apps/magisk/guide-magisk-troubleshooting-t3641417

Especially post #4 titled: Hiding root and passing Safety Net

https://xdaforums.com/showpost.php?p=73145987&postcount=4
[Magisk] kailassc:
Now Tez is not working for me too...!!
[Magisk] Pkt_Lnt:
https://xdaforums.com/showpost.php?p=74899595&postcount=21279
[Magisk] candiesdoodle:
Tez is working fine with SuperSU. Which means it's probably not got anything to do with Safteynet. You guys should try uninstalling the magisk APK and try again
[Magisk] Looki90:
Especially post #4 titled: Hiding root and passing Safety Net

https://xdaforums.com/showpost.php?p=73145987&postcount=4[/QUOTE]

I use custom ROM.

Magisk log proc_monitor: Your karnel device doesn't support mount namespace.

Is the reason why I have issue?
[Magisk] Looki90:
log from Magisk Manager
[Magisk] DodoGTA:
Obviously yes
[Magisk] Looki90:
so i need root my phone and then install magisk?
[Magisk] Chaos234:
Hello,

HCE App is every time detecting Magisk (Manager), even with specific settings so that it shouldn't be deteced. Any possibility to avoid this?
[Magisk] yung40oz84:
This is the first time I've ran into this..... It says I have no free space in Magisk. I will let me flash 2, maybe 3 mods and then they flash, but don't work. They won't display the mod info and the app is not in my app drawer. Why isn't it expanding? Is there a way to override this so I have the room I need? I am running Omni, 8.1, OP5T, Magisk 14
[Magisk] yung40oz84:
I'm sorry I forgot the image....
[Magisk] yung40oz84:
This is interesting as well because in recovery it says it is mounted and resizing, but obviously it is not doing so.... I got recovery log and pic.
[Magisk] RIPAciD:
No, "RESTORE STOCK" is an option in MagiskManager, it restores the boot img backup.

Galaxy S5 G900F, stock kernel and ROM is ALEXNDR.

Everything is working as it should, except that bank app. Forget about it, I don't use paygo anyway...
[Magisk] moham_96:
[MENTION=4470081]topjohnwu[/MENTION] can you add "log full content" as in supersu feature
[Magisk] yung40oz84:
One more thing. i also tried to change the size of magisk in TWRP terminal and keep saying run the efsck -f command or whatever it is and I do that, then try to resize and it keeps saying the same exact thing over and over. how can I just mod the zip to flash at a larger size up front? Obviously it is not working, lol
[Magisk] Didgeridoohan:
It's been fixed and will be in the next release.

Your device's Linux kernel is too old and does not support features needed for MagiskHide.

Does this happen only in TWRP or also when installing through the Manager? Have you tried resizing the image manually?
[Magisk] leaskovski:
Not

Managed to find the files. They were in the /cache folder. Here you go...
[Magisk] birdy3:
Hi,

Using magisk 14. When enable any magisk module like viperandroidfx or greenify, gallery samsung account etc. starts force closing. Any idea?
[Magisk] _alexndr:
[MENTION=4470081]topjohnwu[/MENTION]

[I have asked this question already in beta's thread, but my post has been removed. Maybe here is better place to ask]

I have a "dev" question related to the latest versions of Magisk (v14+)

Is there a simple way to create an installer which can add a post-fs-data.d sh script in case of encrypted devices?

In case of previous version of Magisk (up to v13.x), if my installer detected encrypted data, it just created /cache/magisk.img which contained only .core/post-fs-data.d/0000alexndr file (which is sh script). At next boot it was merged with /data/magisk.img so I achieved my goal with no problem.

Could you give me any dev's advise in case of Magisk v14+?

If there is no possibility to do it at this moment at all - could you introduce again the ability to merge /cache/magisk.img with /data/magisk.img in case of encrypted devices? I know, your installer does not require it anymore, but it would be very good functionality for developers (like me) who still care about data encryption in their work :cool:

Thanks in advance :good:
[Magisk] DiamondJohn:
Logcat.
[Magisk] birdy3:
Magisk log?
[Magisk] DiamondJohn:
I am no Magisk expert, but the fact that the FC's you are getting are NOT during the install (and I'm assuming not during boot, but it could be on start of app during boot), I would be first checking my logcat, but your Magisk log is not going to hurt.
[Magisk] birdy3:
Thank you for your reply. The problem is that when any module become active after reboot. The samsung cloud says unfortunately stopped every few minutes and cant open gallery when tap icon it tries to open and says unfortunately closed.
[Magisk] goodoldie1996:
I've had magisk installed for a while now and been using Google's new payment app called Tez. It used to work fine, but from the last few days, it's showing the rooted device warning and I'm unable to use it. I've tried using magisk hide on tez but it's not working. Currently using Paranoid android 7.3.1, Op3t.
[Magisk] crimemastergogo9999:
Same here. Safety net is passing but tez doesn't work. I am on resurrection remix 5.8.5 yu yureka.
[Magisk] birdy3:
12-20 16:17:02.007* 1423* 1423 I Magisk* : hide_daemon: Permissive detected, hide the state

12-20 16:17:02.007* 1423* 1423 I Magisk* : hide_utils: Re-linking /sbin

12-20 16:18:03.297* 3006* 3187 I Magisk* : proc_monitor: com.google.android.gms.unstable (PID=7330 ns=mnt:[4026542211])

12-20 16:18:03.312* 7336* 7336 I Magisk* : hide_daemon: Permissive detected, hide the state

12-20 16:25:27.533* 3006* 3187 I Magisk* : proc_monitor: com.google.android.gms.unstable (PID=14883 ns=mnt:[4026542209])

12-20 16:25:27.538 14895 14895 I Magisk* : hide_daemon: Permissive detected, hide the state

Is this means anything?
[Magisk] birdy3:
This is logcat also.
[Magisk] Didgeridoohan:
Your Magisk installation is not working as it should, but you already knew that, right? :p What's your device, ROM, kernel, etc?

Try uninstalling and starting clean, preferably with the v14.5 beta or if you're feeling adventurous, an unofficial snapshot of the current code (may be very unstable).

Magisk works perfectly on an encrypted device. I have it installed on 4 devices, all encrypted.

A verbose logcat (uploaded somewhere rather than a screenshot) would be useful.
[Magisk] iamnotstanley:
Hello guys!

Can I somehow enable an advanced SU access log like it was in SuperSU?

I want to see what the rooted apps do. I mean in SuperSU Pro was a setting named Logging - Full content, and I could seen what the app did with root access.

For example: if HelloWorldApp used root access, in SuperSU > Logs I could seen it executed echo "Hello World!" in /system/bin/sh

Yea, I know, it's a very specific question/request, but I need that.

Any solution with Magisk or maybe with some other app?

Magisk version: v14.0

Magisk Manager version: 5.4.3 (64)
[Magisk] kailassc:
now its a common problem for everyone.. need a fix for this :(
[Magisk] drewski_1:
Fix - don't use Tez :p

j/k - I hadn't heard of it. Seems like way too many payment apps popping up!
[Magisk] kailassc:
Dude.. u haven't heard about tez?? Its a payment app released by Google exclusively for India.. And its been widely used all over the country
[Magisk] Sy1ar:
Just installed tez to check if it's affecting all or some, using latest beta and it works as expected, make sure that your device passes safety net and tez is checked in magisk hide.
[Magisk] kailassc:
See this.. issue is there for many others.. the app was working fine till yesterday.. suddenly it stopped working!!
[Magisk] Naxar:
Hi, i've some problems with 2 modules, It says that Will be enabled after reboot, but nothing happens. How Can i resolve?
[Magisk] _alexndr:
Thanks for the answer but you misunderstood my question.

Magisk works perfectly on my device (Samsung Galaxy S7)

I asked about method to inject anything else to e.g. /magisk/.core/post-fs-data (located in fact inside /data/magisk.img) in case of encrypted device with already installed Magisk 14+. In case of Magisk up to V13.x it was possible by creating /cache/magisk.img. In case of Magisk v14+ it is NOT possible such way :(

Why it is so important for me and other devs? I have real-life example which met me today :(

Today I tried new systemless Xposed v89.0 which caused the bootloop in my device :( I had no access to /data from TWRP and there is no uninstaller for systemless Xposed which work fine in case of encrypted devices. In past, in case of Magisk up to v13.x there was a lifebuoy (rescue method) - I could create /cache/magisk.img, mount it from TWRP to /magisk, create e.g. my own .../.core/post-fs-data.d/rescure_script which will reverse the changes made by Xposed installer and phone will be "saved" such way (with all our /data).

In my case I had to wipe all data :( (fortunately I have always up to date backup of my critical data)

Anticipating the question - no, flashing official stock did not help (it is well known fact that flashing pure stock over rooted + encrypted Samsung device, running Nougat, may cause also bootloop)
[Magisk] Stunherald:
Hello, unfortunately neither stable nor beta 1456 works for me. I hope your *magic* is powerful enough to resolve this. Details bellow. If more info/tests needed please let me know.

Device: Sony Xperia X Performance 8132 (Dual-Sim)

Initial Firmware: Stock 7.1 (F8132_41.2.A.7.35)

What has been done:

- Custom recovery: TWRP 3.2.1.0

- Kernel modified by TA_PoC to restore original DRM keys (dm-verify, Sony RIC, Force-encrypt - all disabled) -> System boots and stable, DRM OK

- Kernel patch by Sony Stock Patcher to be able to install Magisk (Xperia X Perf has ELF64 which is not supported) -> System boots and stable, DRM OK

- I've used Magisk Manager 5.4.3. to patch the boot.img by Magisk 1456. I did not used the stock kernel image but the modified one from TA_PoC in order to retain the DRM key solution. Magisk patches the image successfully (Stock boot image detected).

- patched_boot.img flashed via fastboot

Result: Device starts, SONY logo is showed, then XPERIA loading logo is there for several seconds, then the phone reboots.

All logs attached.

Thank you in advance for taking a look on this. I've tried to search around but id did not found same/similar issue for my case. Also if i did something wrong i apologize for it and will be very glad for pointing me to the right direction.

Alex

EDIT: I forgot to add magisk_debug.log. Now it is included in "XP_X_P_magisk_logs_2.zip" archive.
[Magisk] ^subash^:
Please let me know if you found any solution.
[Magisk] Didgeridoohan:
Bloody Samsung... I have no other answer to that... :laugh: Seriously though, I'm the wrong guy for that kind of stuff. :)

I'm curious though: why was it that you couldn't access /data through TWRP? Is that another Samsung thing?
[Magisk] DiamondJohn:
By that he means: go into adb or a shell and enter something like

logcat -d > /sdcard/mymagisklogcat.log;

Then copy and paste that into something like www.hastebin.com and post the link here.
[Magisk] _alexndr:
I thought we both know that we are talking about an encrypted device ;) so basically encrypted /data shouldn't be natively mountable through TWRP ;)

I do not understand the sense of using encryption if we can get access to the /data through TWRP
[Magisk] SignetSphere:
Any update on my inquiry? Like I said earlier I know I won't really pass SafetyNet since I have Xposed Installed. I just want to know why Magisk Manager keeps on crashing whenever I tap the SafetyNet check.
[Magisk] sToRm//:
Looks like the TA.img is not accessible in /data/local/tmp/ and the system can't connect to the trim area. I read that ta_poc doesn't work with magisk, but I don't know if it's true. Haven't tried it by myself.

The last time I had a look in ta_poc, I noticed that the TA.img is merged to the ramdisk. But that's not really good, because as far as I know, changes aren't persistent/saved. Maybe it's a compatibility problem, too.

Did you try to flash magisk with TWRP and then manually patch the ramdisk? Maybe this could fix it. If you want to, you could upload the boot.img from before and after patching with magisk.
[Magisk] bagajohny:
On magisk v14.0 it was working like a charm 2 days ago but from yesterday it stopped working. Don't know about beta version of magisk. Google is always changing its policies. Hope a fix comes along.
[Magisk] Paradox♀:
Thanks for the links but I've magisk is already hidden from Tez :(
[Magisk] rajah sulayman:
I installed version 5.4.1 (courtesy of this thread) and for some reason it can't connect to the internet to check for updates or download/install anything. I have no idea why it's doing this, as everything else on my phone can get online, and I can't seem to find any solutions online. Has anyone heard of this happening? Are the update servers (I tried both Stable and Beta) down?
[Magisk] beardymarrow:
TWRP can mount /data. It just asks you for the encryption key (pin/password). At least that's what happens on my op3t.
[Magisk] DodoGTA:
GitHub isn't down right now, so can you access GitHub (https://github.com) on a web browser? If no, then a firewall might be blocking it

Some info: Magisk Manager uses a .json file hosted on a GitHub repository to check for updates (at least on the official version of it)
[Magisk] alexbk66:
After using SystemPanel2 attached is the result - Magisk looking bad. Can't believe nobody else has this problem, only me?
[Magisk] daddylonglegs:
It took a lot of trial and error but I got Magisk installed on my 2016 Pixel. However, I have not been so lucky with my wife's 2016 Pixel XL. I am able to get root which is great, but I can't install any modules. I receive the error "Installation failed. Magisk is not enabled!" every time I try to install a module (oddly enough I was able to install the BusyBox magisk module, but nothing else).

I even tried flashing the module in TWRP and it doesn't work there either!

This is a 2016 Pixel XL with the 8.1 Oreo update (not a custom ROM). Here are the steps in how I installed Magisk. Maybe that will give some sort of clue?

1) I installed the magisk.apk that is included in Magisk-v14.5(1456).zip

2) I opened Magisk Manager and had it patch her phone's stock boot image

3) I got patched_boot.img from the phone, and then flashed patched_boot.img

4) I booted to TWRP's img and installed Magisk-v14.5(1456).zip in there. It said everything was successful.

5) I booted into Android and verified that Magisk is installed. It is, and I can get root with apps with no issue.

That's really it. I have no idea why it's saying Magisk is not active. Magisk says it's installed fine and passes Safetynet, and it gets me root with no issues at all.

Does anybody know what else I can try or does anybody see anything I might have done wrong? Thank you! :)
[Magisk] leaskovski:
Well funny that! Anyway, yeah, I decided to remove it and install the 14.5 beta, and now the Manager Hide option is visible.

Now I am able to hide the Magisk Manager which also now means I can use the Barclay Card app on my phone again! Result. Thanks.
[Magisk] rajah sulayman:
I'm able to access github.com via browser, so I'm not sure why the app is saying it can't check for updates. It fails on the SafetyNet check as well (API Error).

Is there a way to root without needing Magisk?
[Magisk] DodoGTA:
Upgrade to Magisk Manager v5.4.3
[Magisk] Jaymin.0.1910:
Hey everyone, I have created a shell flashable zip and I want to sign it. I know, there is a special method for it ( zipadjusting, minsignapk, etc ), but I would like to sign shell-zips directly from my phone, for which, I think Magisk Manager have this functionality built into it and If possible, I would wish to use it. But, I don't know how can this be done, can someone here tell me how can I do it ??? Any help is appreciated :)
[Magisk] SacredDeviL666:
You've posted your logs, next step is to wait for someone to check and get back if not then you would still need to wait.

Not required to ask for an update/eta as this isn't a customer service forum but a forum were users will read and respond when they feel to.

There are countless solutions shared for methods to learn including the entire source for this project. Feel free to go through it or use a version which works or simply don't click safety-net verification because it isn't doing any harm in magisk performance to you or the way it supposed to work when you have xposed installed?

You know the answer for it even if it works so wait for an update to be released which might fix your issue or roll back to a version which will work.

Moved your post to general discussion/bugs forum of Magisk

Thanks
[Magisk] Didgeridoohan:
Like stated above already, TWRP can mount an encrypted /data partition just fine. It just needs the password... If none is set (which you should have if you're concerned about protecting your data), "default_password" can be used.

Without looking at your logs, here are two known solutions to this problem:

Make sure Google play services are up to date.

Clear data for the Manager.

Like already stated above, use v5.4.3. You'll find it in the release thread.

If you read the OP of that thread you'll see that it was a special build that now is deprecated.

As always, logs and details are good to bring when asking for help... Installation log, recovery log, Magisk log, logcat, etc... There are so many to choose from.
[Magisk] championc:
Pass SafetyNet with Xposed installed ?

Is there a way to get SafetyNet to pass with Xposed installed ?
[Magisk] daddylonglegs:
Yes I'm serious. If I had any clue how to edit build.prop without editing build.prop in /system I'd do it. But to tether I need to edit that file or I'm screwed.
[Magisk] SQBI:
Unfortunately, no...

Wysłane z mojego SM-N910F przy użyciu Tapatalka
[Magisk] daddylonglegs:
It's going to be a good week or two before I will be able to hook it up to a laptop and do that. I will definitely do it when I can though. In the meantime I was wondering if any of the steps I took seemed wrong.
[Magisk] diogogomes:
Magisk Manager do not install any module and can't install them with TWRP either

Hi everyone, I have a common problem: this zip is not a Magisk Module. I read a lot about it yesterday and today and nothing fix this issue.

I've installed Magisk 14 on stock 5.0.0 rom though patched boot.img like the official guide. The Magisk Manager works, Magisk Su works but every time I try to install a module I get "this zip is not a Magisk Module".

Can you send some guides or try to help me?

Thanks
[Magisk] JJohnson1988:
You can get the ctsProfile bit to pass, but not the basicIntegrity bit.
[Magisk] Didgeridoohan:
Step 2/3 and 4 are the same thing. Letting the Manager patch the boot image and then flashing it to your device is an alternative to flashing the Magisk zip in recovery. They both do the same thing... Other than that, logs. What modules are you having issues with and are they installing on your device?

Sounds like the zips aren't packaged correctly. Where are you getting those modules?
[Magisk] championc:
So will this allow me to run Android Pay or must i remove Xposed for that
[Magisk] SQBI:
You will have to remove it.

Wysłane z mojego SM-N910F przy użyciu Tapatalka
[Magisk] diogogomes:
Through Magisk Manager and from XDA. None method works...
[Magisk] daddylonglegs:
Any module. No matter what module I pick. Even the youtube background one. It says "Magisk is not active" and the installation fails.
[Magisk] darkeyes22:
Just a suggestion, why is Magisk Hide feature togglable? Why not make it an integrated feature without option of turning it off? I don't think anyone will decide to disable Magisk Hide as it mostly only has benefits anyway.
[Magisk] darkeyes22:
No need to remove, just disable it when you don't need it. Xposed will not patch Zygote as it is disabled, and you should pass SafetyNet completely (Use SN fix from Deic if you're on custom ROM)
[Magisk] Vaith:
magisk_daemon -post-fs use a lot of CPU. I was looking for Android logger and I don't know where I can enable it. Kernel Adiutor it's not showing any options about logger. Same Kernel Adiutor mod. I was searching this thread and found nothing. Some people turned on logcat etc but nobody said how they done it. My battery is draining like a stupid - 30 minutes and 30 battery is gone. I need to charge it on every 2 hours! How to solve it?
[Magisk] wackygoose:
I just wish there was a way to sort downloads by last update. Excluding this I don't have anything else to complain, working very fine indeed.

---------- Post added at 11:57 PM ---------- Previous post was at 11:56 PM ----------

Thread is closed
[Magisk] Stunherald:
Hello sToRm,

Thank you for your reply. I did some testing while avoiding the TA patch completely (for now). So i re-flashed the stock image, flashed TWRP recovery and applied only the Sony Stock Patcher. Unfortunately i am not able to install the Magisk either. It is failing on "Unknown ramdisk format". Tested with 14.0 stable and 14.5 beta. Same results. Logs from 14.5 attached.

Regarding the boot.img ... I suppose backup of Boot via TWRP is sufficient? I can not "dd" w/o root obviously.

Thank you in advance for looking at this.
[Magisk] yung40oz84:
Hmmm, u know what that slipped my mind, trying through the manager, But yes if u look a couple up from the post u quoted I tried all kinds of things and tried to resize manually. It kept telling me to do the other command first, i did that command, tried resizing and it just keeps saying that over and over

Also, it may only be 8.1, becasue I just flashed all the samee mods on 8.0 and it worked fine
[Magisk] yochananmarqos:
In case the Magisk daemon gets killed, toggling Magisk Hide will restart it.
[Magisk] sToRm//:
You can dd with adb shell in TWRP. Just plug USB while recovery is running and type "adb shell" then you can copy and pull what you want. If you can post your original boot.img or kernel.elf and the patched one with fixes, I can compare and maybe patch it. Don't forget to mention or quote, because I don't read all posts here.
[Magisk] jenslody:
8.1 seems to have a bug in make_ext4fs, so it can not create images with 128MB.

The coming Magisk has a workaround for this (just creating 132MB images instead).
[Magisk] akpe:
Hello everyone. Just installed Magisk Manager 5.5.0. In the main screen, the "Preserve Force Encryption" option was turned on. And apparently there's no way to turn it off, I uncheck it and next time I open the app it's checked again. I even tried clearing app data.

I don't have encryption on my device. I guess I can ignore that then?
[Magisk] yung40oz84:
Id like to get a nice solid clear answer about this. I am running OP5T and I only found 1 single dm verity zip that worked to keep my device decrypted on OOS and no verity.

My question is it true that Magisk already does this? That it removes force encryption and dm verity? So I wouldn't have to flash that no verity zip, ONLY Magisk?

Thanks for the help!

UPDATE: I just tried to flash ONLY Magisk without no verity and disable force encrypt zip and the ROM you have to be decrypted for will n ot even boot, so obviously Magisk has some updating to do on this front of things. Thanks.
[Magisk] SignetSphere:
The latest beta (14.6) fixed the issue of mine. Thanks everyone sorry for the trouble.
[Magisk] yung40oz84:
The coming magisk as in the 14.6 just released? I have another bugs with that. When I install zip in recovery it says no magisk.img found, lol. Also, every time I open the app it has the option "preserve force encryption" checked.... Do the modules just needs updated to this version template or is that a genuine bug as far as installing in recovery?
[Magisk] SyCoREAPER:
[MENTION=4470081]topjohnwu[/MENTION]

Please add AMOLED/pure black theme to the manager ?.