yashsingh1/xdaforums huggingface dataset:
[Magisk] Android-UK:
After installing this to my Elephone P9000 running resurrection Remix it causes the fingerprint scanner to stop working. Anyone know why or how to fix the scanner?

The scanner does work cause a factory reset restores it BUT once Magisk and flash phh superuser is installed the scanner no longer works and the option to configure it disappears from options.
[Magisk] devilhunter142:
Is there any chance that Magisk for android 4.4 would develop?
[Magisk] wackygoose:
I did it again.... Fastbooted recovery without any error messages but still cant boot into recovery
[Magisk] peterlee928:
do u turn off all passwords and fingerprint locks etc prior to booting into recovery? ive found that the last 1-2 twrp versions work umder that specification.
[Magisk] Michasiu91:
Give my your adress. Beer for you brother ?
[Magisk] Didgeridoohan:
If there's not enough space in the Magisk image it's best to then create a merge image that you make however large you need it to be, copy all the necessary data over to it and then let Magisk take care of everything when you reboot.

I haven't actually looked closely at the inner workings of the systemizer modules, but I always assumed that's what they do. It's what I would do...
[Magisk] rignfool:
Except that the copy from data to system happens after the image is loaded... So there is no chance to resize...

And there is also no way for the developer to know how much of the image you're going to use... Or what you already have installed...

And I think magisk resizes the image at some point automatically?
[Magisk] MrBrady:
Just tried repacking Magisk and Samsung Pay is still detecting root.
[Magisk] Didgeridoohan:
No, with the merge image there shouldn't be any size issues. You can create the merge image however large you feel like before mounting it to copy the data over. All of this would be done when the system is fully booted, in terminal or an app. Then you can unmount the image, resize it, mount again, and so on. When you then reboot, magisk will merge the merge image into the Magisk image and everything should be there.

You can even make the merge image almost ridiculously large, to have some margin, and then resize it to a more appropriate size. Or just let Magisk take care of trimming when merging the image at boot.

I've played with this a little and it works... And it's pretty much how Magisk deals with module installation while the Magisk image is live and mounted (installing through the Manager).

---------- Post added at 19:56 ---------- Previous post was at 19:47 ----------

Are you sure it detects root and not something like USB debugging or Developer options being enabled?

With the Manager repackaged and an app added to the Hide list there's virtually nothing left of Magisk that the app can see.

It's of course possible that it's using other apps or services that are not on the Hide list... It's also possible that it remembers root, so that you'd need to clear data for the app after it has been triggered.

Another thing that may trigger an app is the value from the actual file, default.prop or build.prop, rather than the loaded value. If the prop is set to a triggering value that is...

Or, it's looking for something completely different. A logcat or a strace from when it triggers might show something.
[Magisk] wackygoose:
Didnt had The chance.got twrp working again after a Lot of tries, thanks god this time i had a boot backup.i feel Dumb

---------- Post added at 05:14 PM ---------- Previous post was at 05:01 PM ----------

I had this only with encryption enabled on The device,is There something im missing or i better collect logs?

---------- Post added at 05:14 PM ---------- Previous post was at 05:14 PM ----------

I had this only with encryption enabled on The device,is There something im missing or i better collect logs?
[Magisk] WTF_666:
Simply as soon as you delete Magisk from the system everything starts to work correctly and once you put it back, Spay ceases to function.
[Magisk] rosel11078:
So I just have to flash "f2fs-loopback-bug-workaround-2018.1.24.zip" and nothing else
[Magisk] DenyDarko:
Is it so difficult to use the "Magisk General Support" thread?

I mean it gets really disrespectful to the original OP and the mods who have to babysit this topic on a daily basis. Sometimes even twice a day.

I mean not even a day after [MENTION=1205214]SacredDeviL666[/MENTION] devoted (once again) time to clean the thread and few hours ago another mod it's again one page full of unrelated off-topic.

Unbelievable.
[Magisk] Didgeridoohan:
If you have all necessary apps added to your Hide list and the Manager is repackaged that means it's using something else to detect Magisk. Logs needed to even have the slightest chance of knowing what's going on...

---------- Post added at 21:02 ---------- Previous post was at 21:00 ----------

Maybe... It might work. I have never used it myself. Best place for support is the module thread.
[Magisk] WTF_666:
Are you suggesting that you hide all applications on your phone detecting root accesses and then one by one to exclude them from the list to check this?
[Magisk] peterlee928:
sorry for trying to help someone out. wont do it again.
[Magisk] walid77dz:
sorry for the delay. Here is a link to my boot image ( the real name of my boot image in firmware is boot-sign.img, i've changed it to boot.img):

https://ufile.io/0a9uf
[Magisk] rosel11078:
what advantages do I have If I use custom kernel ? I am in Official Stock 7.0 rooted. Which is the best option that I could take, using custom kernel, format /data to ext4 or flashing module "F2FS Loopback Bug Workaround module".
[Magisk] MrBrady:
As [MENTION=8889050]WTF_666[/MENTION] mentioned, remove Magisk and it works. Add Magisk and it throws a security error. Disabling USB Debugging and/or Developer Options doesn't fix the issue.

You mention pulling a logcat or strace when it triggers. What are steps to do that? Hook up phone to computer, run adb logcat, pen Samsung Pay, throw the error, copy and paste the log?

EDIT: I have zero experience with strace.
[Magisk] Didgeridoohan:
[MENTION=8889050]WTF_666[/MENTION] [MENTION=3104236]MrBrady[/MENTION] Have you tried simply rebooting after hiding everything Samsung and repackaging the Manager. Reason I ask: https://xdaforums.com/showpost.php?p=75332855&postcount=42
[Magisk] MrBrady:
Reboot didn't help unfortunately.

Tried rolling back to stock kernel & tdbo - only worked until I added Magisk 15.3, then Samsung Pay threw an error.

Logcat: https://docs.google.com/document/d/178Ku5sUbczZ-T6fz8knWHxJGEWlGyubeb7zb15NoBN4/edit?usp=sharing
[Magisk] SacredDeviL666:
Moved few posts from Beta Thread to General support as it had nothing to do with Beta release or troubleshooting.

Kindly avoid cluttering the beta thread.

Thanks to all for understanding and support as always :highfive:
[Magisk] space_eyes:
With a few apps I get this. Magisk hide not helping me. I think it's another method of detection. Tried a few options... even xposed
[Magisk] jhedfors:
Anyone know if there is a way to disable a sensor (specifically magnetic flip cover) with Magisk? I have tried Xposed modules on my OPO with no luck. I am trying to get Cardboard to work.
[Magisk] f3bandit:
It gives me and error when trying to patch the emotion kernel for the galaxy note 4
[Magisk] Ja_som:
OK, do you also want help from someone, or you just saying that?
[Magisk] f3bandit:
Well I tried to let magisk patch the custom kernel but it states its not a stock kernel and breaks operation .
[Magisk] jenslody:
What's the exact message?

Does it say it's patched by another program ?
[Magisk] Didgeridoohan:
Troubleshooting guide - the section called "Hiding root from apps". That should have a few pointers for you.
[Magisk] f3bandit:
Yes it states its patches by another program, I would really like to have this kernel patched.

Cause the stock kernel kills batteries for some reason. I don't know why. But when I run

The emotion kernel i don't have the battery heating up like a hot piece of metal.
[Magisk] parsifal968:
Chuwi HI10 android 5.1

fresh system reset

root obtained with magisk seem all ok but after EVERY reboot the language and the timezone keep change itself!

how to solve?

(rooting with supersu and no problem with language e timezone on reboot)
[Magisk] modpunk:
I'm looking for an example how to modify/extend the sepolicy from a magisk module. Can someone point me to one?
[Magisk] Artim_96:
Can't be done by a module afaik. That file lies in the ramdisk, which is mostly located in the boot.img. that's what Magisk does on installation

---------- Post added at 11:25 AM ---------- Previous post was at 11:23 AM ----------

Upload Magisk log and create a catlog of bootup. Google for the necessary command. Maybe they can pick up something
[Magisk] Didgeridoohan:
The ViPER4Android modules do some stuff with the sepolicy. https://xdaforums.com/apps/magisk/module-viper4android-fx-2-5-0-5-t3577058
[Magisk] space_eyes:
Yes I found it just after this post. My apologies. But it's a new detection method and I don't know how to figure it out. Will follow up in other thread
[Magisk] Dr. Hurt:
Xiaomi Redmi Note 4 Qualcomm SD625 Oreo ROM

Formatted data to F2FS and now magisk su requests work but are not remembered. I have to grant permission every single time the su command is issued by the requesting app.

Log shows errors related to magisk su database
[Magisk] fiverings:
Hi, I'm new to Magisk (super su won't work anymore) . Can someone confirm that this is how to install Magisk on my Pixel XL with January 2018, update. Twrp installed and working. Tried to install Super su (didn't work).

Open twrp and flash update unsu.zip, boot to system, open twrp again, flash Magisk.zip, 15.3, boot into system and install Magisk manager 5.5.5. Is this correct? Or am I missing some step or file. Any help is appreciated.
[Magisk] DodoGTA:
Yes, it's correct, but installing Magisk Manager isn't really required, because Magisk will automatically install Magisk Manager (in most cases)
[Magisk] fiverings:
About Magisk manager, I read that you copy it to your internal files. So, do I do that, do I tap it and install it or will it just open on it's own.

One more thing. I think the file is called Magisk un root. What's that for?
[Magisk] martyfender:
It's also not a bad idea to have a fresh copy of your ROM's boot.img. UnSU should install the backed up boot.img. To be safe, it is not a bad idea to flash a copy of your original boot.img, before you flash the Magisk.zip, just to be certain you have at clean, untouched boot.img for Magisk to patch.

All of this info and more is here:

Installing Magisk and Modules

https://xdaforums.com/showpost.php?p=73145975&postcount=2
[Magisk] derekr44:
I found something odd that began happening over the last two days. Certain apps that use Google login services (Immortal Conquest & Drippler) either for Google Play Games or just a Google Account login, can't seem to communicate over a cellular data connection. Here's how I seem to think it's Magisk:

Device: Pixel 2 XL

OS: Android 8.1.0 Stock w/January Update (OPM1.171019.013)

Flashing Method: fastboot boot twrp to flash

Notes: Default Magisk settings, no modules installed

Situation 1

1 - Clean flash all stock, run initial setup

2 - Fastboot boot twrp

3 - ADB push Magisk 15.3

4 - Flash Magisk 15.3, no errors, reboot to system

5 - Run SafetyNet check. All passed.

6 - Install Google Play Games, then Immortal Conquest

7 - Open Google Play Games to recognize Google Account as default

8 - Open Immortal Conquest with cellular data connection

9 - Use Google Play Account

10 - No servers visible, seems to fail to pull back any data from Google Play Games

11 - Open Immortal Conquest with WiFi data connection

12 - Servers are available for selection

Situation 2

1 - Clean flash all stock, run initial setup

2 - Fastboot boot twrp

3 - ADB push Magisk 15.3, custom kernel (Flash 2.13)

4 - Flash kernel, no errors... Flash Magisk 15.3, no errors, reboot to system

5 - Run SafetyNet check. All passed.

6 - Install Google Play Games, then Immortal Conquest

7 - Open Google Play Games to recognize Google Account as default

8 - Open Immortal Conquest with cellular data connection

9 - Use Google Play Account

10 - No servers visible, seems to fail to pull back any data from Google Play Games

11 - Open Immortal Conquest with WiFi data connection

12 - Servers are available for selection

Situation 3

1 - Clean flash all stock, run initial setup

2 - Install Google Play Games, then Immortal Conquest

3 - Open Google Play Games to recognize Google Account as default

4 - Open Immortal Conquest with cellular data connection

5 - Use Google Play Account

6 - Servers are available for selection

7 - Open Immortal Conquest with WiFi data connection

8 - Servers are available for selection

I know the issue would seem to be with the game itself, however the same thing happens for a simple news feed app like Drippler with the same steps as above. On a cellular data connection, the service those apps use on the backend to pull back Google Account data is possibly blocked. WiFi is fine.

I'll keep looking, maybe there's a service that needs to be hidden, I don't know. I just thought I would bring this up in case I'm not the only one seeing it.
[Magisk] sdfkjsdlfkkjdfs2:
BUG

on Magisk v15.3 (non-beta)

on Magisk Manager 5.5.5

I can install modules after downloading and installing Magisk for the first time. But when I reboot my phone, I can no longer install modules. Error is:

- Found /data/adb/magisk_merge.img
- Mounting /data/adb/magisk_merge.img to /dev/tmp/magisk_img
! /data/magisk_merge.img mount failed...
Failed!
! Installation failed

Have tested multiple times on Xiaomi Mi A1.
[Magisk] zefyx:
Anyone having issues with Square Enix games not booting, even with passing securenet and magisk hide? Just me?? H'okay.
[Magisk] ZidanBlaster:
I got problem here seems the module doesn't installed properly instead i found this on recovery.log

I:Found no matching fstab entry for uevent device '/devices/virtual/block/loop1' - change

Here's the log
[Magisk] Psycake:
Tried it and it doesn't install.

EDIT: I'm an idiot. No module was installing because the F2FS loobpack bug module hadn't been properly installed. Reinstalled and now it installs correctly. I uninstalled it since my controller mysteriously doesn't need it. Thanks!
[Magisk] thatOneWeeaboo:
try flashing it in the recovery

if it still fails, contact the module's dev
[Magisk] DodoGTA:
Do you have Xposed enabled?
[Magisk] zefyx:
No, I don't. I didn't have a problem with this back with v14. It seems like any game that relies on the obb folder is broken with Magisk enabled.
[Magisk] DB126:
Symptoms suggest data partition is formatted f2fs. If so see post #2 in this thread for discussion and solutions (in which case it's not a big).
[Magisk] trax7:
Flash the F2FS Loopback bug module.
[Magisk] Dr. Hurt:
Thanks but that doesn't solve the issue for me. Using official Pixel Experience 8.1.0 r4 with latest F2FS updates in upstream 3.18.92 kernel.

The magisk app crashes too sometimes.
[Magisk] Psycake:
How do I do this?
[Magisk] thatOneWeeaboo:
if you have a custom recovery installed e.g. TWRP, just boot there and flash it as if it's a regular zip. It'll recognize the zip as a Magisk module and flashes accordingly
[Magisk] Psycake:
Okay, I'll try that later. Thanks!
[Magisk] VincentJoshuaET:
Magisk's log is empty. What could be the reason for that? Thanks.
[Magisk] :
Those facing su permission issues with 8.1 roms on f2fs. Temporary solution is here: Download Magisk 14.6 (we'll use it for later). 1. Flash magisk 15.3, and then flash all the modules you want to use. Skip this if you already set up.. 2. Then go to Magisk manager & select "Uninstall" > "Restore images". Don't worry you won't lose your modules. 3. Flash 14.6 from inside the Magisk manager app. 4. Reboot 5. After boot auto grant permissions from the app.. 6. Losing Su permission all the time problem gone! BE WARNED: : careful which apps you install as Magisk will give every app su permission without asking
[Magisk] VincentJoshuaET:
What device and ROM have you tried this on?
[Magisk] :
Xiaomi mi5, Cosmic 8.1
[Magisk] Didgeridoohan:
Magisk might not be working on your device, or you have a ROM/kernel setup that wipes /cache on boot, or something else.

If you install the beta version of the current Magisk release (only difference is more verbose logging) you can find a more detailed log in /data/adb/magisk_debug.log.
[Magisk] Jonas Cardoso:
Is there a workaround for not losing magisk when installing an update from my kernel? It modifies the ramdisk and conflicts with some magisk file, I use anykernel as the installation script

https://github.com/JonasCardoso/android_kernel_xiaomi_msm8996/tree/lineage-14.1/zip-creator/base
[Magisk] vMAC:
Is there a proper guide to how to upgrade Magisk via MM?

I have a pixel 2XL and I seem to not be able to find proper procedures for upgrading despite my search.
[Magisk] Badger50:
P2XL here as well. Open the app, let it update the app itself. Then open the app again and let it update the zip. Reboot, done :good:
[Magisk] hronis1:
Modules can't be installed

Hello, I recently rooted my phone (xiaomi redmi 4x) via Magisk. When I try to install a Magisk module through Magisk(a led notification hack that makes the led light multiple colors) I get this error:

- Copying zip to temp directory

- Installing led-notification-hack-santoni-3.zip

! Magisk is not activated!... abort

Failed!

! Installation failed

Please help.
[Magisk] Didgeridoohan:
Install Magisk again directly after updating the kernel... That's about it...

Sounds like the module is based on an old module template. But that's just a guess, of course...
[Magisk] tonycapuozzo:
Modules not loaded/executed...

Hello,

I'm facing a very strange issue (or at least, I guess it is). I'd already had a startup script (in /magisk/.core/post-fs-data.d/, which I had used to enable API camera v2) and yesterday I added the following couple of lines into it:

magiskpolicy --live "permissive camera_prop"
magiskpolicy --live "permissive hal_camera_default"

Apparently that got the job done but then I realized that these lines prevented Magisk from loading/executing all the installed modules: these ones kept to be shown (within Magisk's module menu) but they actually didn't get executed.

Ideas ?

(I'm using Magisk v15.3 stable on Xiaomi A1)

Thanks
[Magisk] hronis1:
Template

Template? Template is the version of magisk?
[Magisk] Didgeridoohan:
Most Magisk modules are based on a template provided by [MENTION=4470081]topjohnwu[/MENTION]. It changes and is updated from time to time usually when there's a major Magisk release.

With the current Magisk, v15.3 (which I'm assuming you're using since you haven't informed us otherwise), you can't install modules based on templates that are older than template version 1400. The error you get is similar to the one you posted.

You can check the template version by looking in the zip, in the file named module.prop. If "template" or "minMagisk" isn't 1400 or higher, it's an outdated module. Contact whoever made the module and ask them to update it, or do it yourself.

If it turns out to be something else that's amiss (remember I'm still only guessing since you haven't really provided much info), please post at least the installation log and Magisk log (attach or provide a link, don't copy-paste).
[Magisk] Ja_som:
Tweet from topjohnwu:

Do not install Magisk Manager from the Play Store, it is a fake app with ads spam.

Report them guys.

One:

https://play.google.com/store/apps/details?id=com.mathio.serjam

And second:

https://play.google.com/store/apps/details?id=com.mathio.guide
[Magisk] Jonas Cardoso:
Dont work, get bootloop, this happens only in magisk 15+, in magisk 14 smart boot without module magisk
[Magisk] DenyDarko:
Hey [MENTION=4470081]topjohnwu[/MENTION] ,

I was browsing the modules repo in github and saw some of my currently installed modules being removed (by request).

And I came up with an idea.

How about adding a small text notification for installed modules not in the repo?

It's trivial but well...
[Magisk] beardymarrow:
That's ironic as Google took down the real version a couple of months ago.
[Magisk] Pkt_Lnt:
Go to the Play Store and report it. With hundreds doing that it will get removed quickly and help topjohnwu, :good:
[Magisk] Ja_som:
I did, and also edited my post, added links.
[Magisk] DenyDarko:
Both are gone

And that's what happens when Google is stupid.

They don't realise It's better to keep the official there to ensure legitimate software than force people go and look here and there getting malware.
[Magisk] K1nsey6:
I've installed 15.6 but am still unable to access superuser within the app. As a temporary work around from 15.3 I had done a blanket grant to root which is sticking. I'm just not able to show the list of apps granted root, Magisk crashes when I select superuser. Apps granted are reflected in logs
[Magisk] Didgeridoohan:
I brought your query over to the general thread since it doesn't really belong in the beta thread.

You're going to have to be a bit more specific about your issue since your logs look fine. What makes you think things aren't working as they should?

So your kernel isn't compatible with the current release... Since it's your own, couldn't you take a look at the Magisk source and adapt? Or are least find out where it fails.
[Magisk] DEMONVoz:
1+3, OOS beta 30, oreo, magisk 15.3, clean installing with all wipe. Magisk isn't mounting module's paths. logcat and magisk log in archive. problem with magisk, i contacted with developer of module, he said problem not in module, magisk isn't mounting module paths

View attachment logs.zip
[Magisk] Didgeridoohan:
I already asked if you could be more specific. There's not a whole lot to go on in those logs... Install log and Magisk log looks fine and the logcat is a lot easier to read if you know what you're looking for.

Details, please.
[Magisk] Hyperbomb64:
Has anyone gotten the "Magisk Manager has stopped working" while using 5.5.5? The error occurs when an app asks for root permission. I've granted it forever, but it looks as if magisk is forgetting that I've granted access and then starts denying root and crashing. Just wondering if anyone else has experienced this issue and if they have a fix.
[Magisk] peterlee928:
i just updated my systemless xposed to the newest beta version from magisk manager.

upon doing so, no modules are found in the mm "downloads" section. nor do my currently modules show up. however, oddly enough, my installed modules (including the aforementioned newest xposed framework) show up in the "modules" section.

attached is a magisk log.

any thoughts on how to fix?

any help would be greatly appreciated.

phone stats

verizon pixel xl

systemless root via magisk (15.3)

xposed installed

stock rom with some tweaks via l speed

EDIT

stock rom is running january update

EDIT

after a few more restarts, the aforementioned issue appears to be resolved. i will post an updated log in a follow up message for anyones edification.
[Magisk] peterlee928:
see attached log... as noted above, the originally outlined problem is resolved for now.

much thanks.