yashsingh1/xdaforums huggingface dataset:
[Magisk] daddylonglegs:
Sorry.

I used to follow a guide on how to get Magisk working on the Pixel but this was back when Magisk did not officially support the Pixel yet. Now I am reading all sorts of people saying all they did was flash the magisk zip in TWRP and it worked on their Pixel.

I flashed Magisk-v14.5(1456).zip in TWRP on my 2016 Pixel (non-XL) that is on the latest 8.1 update. After flashing the Magisk zip, every time I boot my phone, I get an error that says "system ui application has stopped" and I can't do anything on my phone.

There really isn't more to it than that. I would post a log but I was not aware there would be a magisk log since I was under the impression it did not install properly. Where would I find the log so that I can post it?

Thank you very much in advance.
[Magisk] Didgeridoohan:
Ah yes... I saw you posting about that earlier. A long time ago, probably around Magisk v9 or v10 I saw something similar on my Nexus 6. No idea why... Did a clean wipe of my phone and never saw it again.

It really should be as easy as flashing the zip and voila!

You could hook your phone up to a computer and run a logcat to see why it crashes.

You could also pull the Magisk debug log from /data. Boot back to TWRP and you should be able to find it there.
[Magisk] yochananmarqos:
Your issue is not Magisk related. If you were not passing SafetyNet, Android Pay would complain that your device is modified when you tried to pay. Your phone should still be detecting the NFC chip in the card reader no matter what.
[Magisk] Fif_:
Have you tried getting a logcat? ;)
[Magisk] proza:
Will my phone becomes unrooted after auto update from Android M to Android N?
[Magisk] DodoGTA:
If you're talking about non-custom ROM OTA updates, then absolutely yes (You'll need to flash the Magisk uninstaller and reinstall Magisk)
[Magisk] mradonis23:
Pixel XL Running magisk 14.5, elementX 3.0 kernel, Oreo 8.1 with magisk hide enabled. I am experiencing random reboots. Has anyone experienced this? Can anyone offer some advise?

Thanks
[Magisk] justj0sh:
So today I woke up to my phone without magisk and all the apps I converted to system apps before. I presume somehow an OTA update happened while I was sleeping. I downloaded the latest Magisk (14.0) and reflashed it, got back root. I then proceed to attempt to convert apps back to system apps. That's when the problem surfaces. I try to move with 3 different system app movers. Two throw errors that /system cannot be mounted.

Link2SD error: 'mount:/dev/block/bootdevice/by-name/system'->'/system': Device or resource busy

/system/app mover error: Could not remount /system

I manage to manually move it with ES File Explorer in Root Mode. However, the app itself does not detect that it is now a system app despite setting the required permissions.

What gives? Do I need to wipe all data and restart?
[Magisk] yochananmarqos:
First of all OTA's do not install by themselves. Second, why are you trying to move apps into system while using a systemless root method?

It sounds like somehow the Magisk image got corrupted and was no longer mounted. I would flash the Magisk uninstaller, flash your stock boot.img then flash Magisk again. Use modules like App Systemizer or Terminal App Systemizer to systemize apps.
[Magisk] MrBrady:
Can anyone suggest a Magisk Module that limits and/or blocks wakelocks on Android 8.1 similar to Wakeblock? https://xdaforums.com/android/software/wakeblock-blocking-drain-late-t3526313
[Magisk] yochananmarqos:
What's wrong with using Wakeblock?
[Magisk] zee24:
Guys I need help please. I have a pixel xl and magisk has been working since I've known it and it's still working however the only thing is when I open 'magisk hide' the list is empty I'll post pictures to show what's going on. Can someone help me? Thanks
[Magisk] daddylonglegs:
Thanks. I did get a magisk log but it's too large to paste here and I also can't paste it to pastebin so here is a download: https://we.tl/wYFN8ZRCZY

Please let me know what is going on if you can. I would appreciate it so much!
[Magisk] mister_slowhand:
Ok, so my answer to this has disappeared, I can provide further details but of course, log is a bit irrelevant because at some point, all I can get is "error: fork failed: Try again" because of ressources limits reached.

Here is a logcat just after reboot.

The 'top' from ADB shows lots of defunct "logcat" processes, PPID being the "magisk_daemon -daemon" process, PID 260 in this case :

Tasks: 5550 total, 11 running, 337 sleeping, 0 stopped,5190 zombie

Mem: 3905152k total, 3861452k used, 43700k free, 2848k buffers
Swap: 0k total, 0k used, 0k free, 2110084k cached
800%cpu 108%user 89%nice 99%sys 498%idle 6%iow 0%irq 0%sirq 0%host

PID USER PR NI VIRT RES SHR S[%CPU] %MEM TIME+ ARGS [0m
615 system 18 -2 2.5G 228M 160M S 96.6 5.9 10:46.18 system_server
29277 shell 20 0 24M 8.5M 1.4M R 47.3 0.2 0:02.38 top
1350 u0_a31 20 0 2.3G 192M 148M S 40.0 5.0 3:53.30 com.google.andr+
978 radio 20 0 2.1G 69M 44M S 37.0 1.8 2:59.67 com.android.pho+
1503 u0_a31 16 -4 2.5G 240M 181M S 18.0 6.2 1:49.96 com.google.andr+
197 root 20 0 0 0 0 S 14.0 0.0 0:15.84 [exe_cq]
12624 u0_a1 20 0 2.1G 65M 37M S 6.6 1.6 0:56.09 android.process+
11255 u0_a73 10 -10 2.6G 140M 99M S 4.0 3.6 1:24.95 org.faked.isms2+
260 root 20 0 31M 4.0M 3.0M S 3.0 0.1 0:27.15 magisk_daemon -+
291 root -2 0 17M 1.6M 1.2M S 2.0 0.0 0:10.86 lmkd
256 logd 30 10 30M 2.4M 1.4M S 2.0 0.0 0:16.67 logd
198 root -2 0 0 0 0 S 1.6 0.0 0:06.87 [mmcqd/0]
381 root 0 -20 0 0 0 S 1.3 0.0 0:06.51 [kworker/u17:2]
713 root 0 -20 0 0 0 S 1.0 0.0 0:08.38 [kworker/u17:4]
602 radio 20 0 27M 1.4M 1.1M S 1.0 0.0 0:00.78 gsm0710muxd -s +
375 root 20 0 0 0 0 S 1.0 0.0 0:00.70 [dmcrypt_write]
155 root 0 -20 0 0 0 S 1.0 0.0 0:06.33 [kworker/u17:1]
3819 u0_a77 20 0 2.4G 99M 59M S 0.6 2.5 0:19.81 rpkandrodev.yaa+
641 root 20 0 63M 3.8M 2.3M S 0.6 0.1 0:00.47 mtkrild

Disabling MagiskHide in the parameters as suggested here helped a bit, instead of thousands zombies, it creates a lot less but still, after several hours, the phone hangs anyway.

I'm able to make some tests as the phone is not yet used.
[Magisk] justj0sh:
Well I don't know any other explanation on why my system apps were cleared along with magisk without removing magisk manager. I am looking for a solution without having to wipe existing data so I am avoiding flashing stock boot for now. I'm not sure why I used magisk for moving but it worked before so I didn't complain. I understand the irony of it.
[Magisk] yochananmarqos:
Flashing a boot.img (kernel) does not wipe data.
[Magisk] MrBrady:
It doesn't work on Android 8.1 on my P2XL
[Magisk] beingaryanpareek:
Magisk modules completely vanishes after the reboot... Plz help!
[Magisk] Alxoom33:
Need a lot more details to help you.
[Magisk] beingaryanpareek:
I were on supersu... fully uninstalled that and flashed magisk and installed two modules namely ios emoji and injected youtube. But when i reboot my device don't find anything in modules. Plz help
[Magisk] Alxoom33:
What device are you rooting, what is the OS and version? How did you rooting with Magisk, which version s. Nobody can guess what you did to your device.
[Magisk] roxdragon:
Hi. I want make a screenshot of coinbase app. but the screenshot function is locked. There is a module for magisk?

look here: http://repo.xposed.info/module/fi.veetipaananen.android.disableflagsecure

Thank you
[Magisk] Timberlake.C:
Sad...pls help
[Magisk] Wolfcity:
Device? Twrp version? Rom? OS? Logs?
[Magisk] Didgeridoohan:
This is not at all my area, so I can unfortunately not tell you what's going on and why it's happening. There's this little bitty in the log you provided though:

12-12 01:28:41.729 1267 1267 E AndroidRuntime: FATAL EXCEPTION: main
12-12 01:28:41.729 1267 1267 E AndroidRuntime: Process: com.android.systemui, PID: 1267
12-12 01:28:41.729 1267 1267 E AndroidRuntime: java.lang.RuntimeException: Unable to get provider android.support.v4.content.FileProvider: java.lang.IllegalArgumentException: Missing android.support.FILE_PROVIDER_PATHS meta-data
12-12 01:28:41.729 1267 1267 E AndroidRuntime:	at android.app.ActivityThread.installProvider(ActivityThread.java:6242)
12-12 01:28:41.729 1267 1267 E AndroidRuntime:	at android.app.ActivityThread.installContentProviders(ActivityThread.java:5805)
12-12 01:28:41.729 1267 1267 E AndroidRuntime:	at android.app.ActivityThread.handleBindApplication(ActivityThread.java:5722)
12-12 01:28:41.729 1267 1267 E AndroidRuntime:	at android.app.ActivityThread.-wrap1(Unknown Source:0)
12-12 01:28:41.729 1267 1267 E AndroidRuntime:	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1656)
12-12 01:28:41.729 1267 1267 E AndroidRuntime:	at android.os.Handler.dispatchMessage(Handler.java:106)
12-12 01:28:41.729 1267 1267 E AndroidRuntime:	at android.os.Looper.loop(Looper.java:164)
12-12 01:28:41.729 1267 1267 E AndroidRuntime:	at android.app.ActivityThread.main(ActivityThread.java:6494)
12-12 01:28:41.729 1267 1267 E AndroidRuntime:	at java.lang.reflect.Method.invoke(Native Method)
12-12 01:28:41.729 1267 1267 E AndroidRuntime:	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:438)
12-12 01:28:41.729 1267 1267 E AndroidRuntime:	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:807)
12-12 01:28:41.729 1267 1267 E AndroidRuntime: Caused by: java.lang.IllegalArgumentException: Missing android.support.FILE_PROVIDER_PATHS meta-data
12-12 01:28:41.729 1267 1267 E AndroidRuntime:	at android.support.v4.content.FileProvider.parsePathStrategy(FileProvider.java:586)
12-12 01:28:41.729 1267 1267 E AndroidRuntime:	at android.support.v4.content.FileProvider.getPathStrategy(FileProvider.java:557)
12-12 01:28:41.729 1267 1267 E AndroidRuntime:	at android.support.v4.content.FileProvider.attachInfo(FileProvider.java:375)
12-12 01:28:41.729 1267 1267 E AndroidRuntime:	at android.app.ActivityThread.installProvider(ActivityThread.java:6239)
12-12 01:28:41.729 1267 1267 E AndroidRuntime:	... 10 more

Hopefully someone who actually knows what they're talking about can tell you more...

You need to provide logs...

https://xdaforums.com/apps/magisk/module-smali-patcher-0-7-t3680053

The answer to your problem is in the TWRP output in your screenshot... Look here for some further details:

https://xdaforums.com/apps/magisk/guide-magisk-troubleshooting-t3641417
[Magisk] JimZiii:
hey, just got a galaxy ace 4, does magisk work on this old phone?
[Magisk] Badger50:
Not likely. If it's still running kit kat then no. If it's 5.0 lollipop, then maybe.
[Magisk] yochananmarqos:
No. Magisk and Xposed are two completely different things.
[Magisk] cubandanger05:
I'd start by flashing the stock image for your device as it states
[Magisk] beingaryanpareek:
Device- Tomato OS- NitrogenOs 8 Magisk Version 14
[Magisk] daddylonglegs:
So I am starting to think I know why Magisk won't work on my Google Pixel

I get systemUI crashes whenever I try to install it. I think it's because in Android 7.0 I used this Magisk module called EvilTheme patcher. It might be residing somewhere on my phone and when I install Magisk it re-enables it. I have no clue where to begin looking to see if that is the case though.

Does anybody know what I can do to remove what would be causing this? The EvilTheme patcher thread is all but dead and no one replies to it any longer.
[Magisk] kramer04:
Hello

I use V4 module magisk shadysquirrel . It works well except with Samsung music. I don't understand why when I want play music V4 processing stop.

If I stop Samsung music processing works.

Any idea what to do to have processing works with Samsung music ?

Thanks
[Magisk] theandroidguy:
Maybe samsung music doesn't support any equaliser other than its own equaliser thats why v4a stops, try sony music it works great though
[Magisk] Xenomorphys:
My authorization problem refused is worse and worse ...

I spend my time killing Greenify for it to work ...

And it does the same on other applications. So it's not Greenify ...
[Magisk] boilednut:
Intermittent Root Denials for Services

Hello. Over the past few weeks, I've been having an issue with Magisk -- after a random amount of time -- denying root requests from Tasker and Greenify. For Tasker, I have to restart the service for it to regain root. Looking at the included logs, Magisk is denying root because of select failures. I'm running a stock Galaxy S8 Exynos.

I( 3126: 3255) proc_monitor: com.netflix.mediaclient (PID=21367 ns=mnt:[4026533841])

I( 3126: 3255) proc_monitor: com.netflix.mediaclient (PID=22467 ns=mnt:[4026533840])

I( 3126: 3255) proc_monitor: com.amazon.avod.thirdpartyclient (PID=26240 ns=mnt:[4026533822])

I( 3126: 3255) proc_monitor: com.amazon.avod.thirdpartyclient (PID=29796 ns=mnt:[4026533872])

I( 3126: 3255) proc_monitor: com.google.android.gms.unstable (PID=32156 ns=mnt:[4026533824])

I( 3126: 3255) proc_monitor: com.amazon.avod.thirdpartyclient (PID=775 ns=mnt:[4026533867])

I( 3126: 3255) proc_monitor: com.amazon.avod.thirdpartyclient (PID=10993 ns=mnt:[4026533810])

I( 3126: 3255) proc_monitor: com.google.android.gms.unstable (PID=18731 ns=mnt:[4026533874])

I( 3126: 3255) proc_monitor: com.amazon.avod.thirdpartyclient (PID=21058 ns=mnt:[4026533820])

I( 3126: 3255) proc_monitor: com.amazon.avod.thirdpartyclient (PID=14539 ns=mnt:[4026533854])

I( 3126: 3255) proc_monitor: com.google.android.gms.unstable (PID=20747 ns=mnt:[4026533854])

I( 3126: 3255) proc_monitor: com.amazon.avod.thirdpartyclient (PID=21495 ns=mnt:[4026533805])

I( 3126: 3255) proc_monitor: com.amazon.avod.thirdpartyclient (PID=26781 ns=mnt:[4026533875])

I( 3126: 3255) proc_monitor: com.amazon.avod.thirdpartyclient (PID=28632 ns=mnt:[4026533836])

E(31229:31229) select failed with 2: No such file or directory

W(31229:31229) su: request rejected (10229->0)

E(31242:31242) select failed with 2: No such file or directory

W(31242:31242) su: request rejected (10356->0)

I( 3126: 3255) proc_monitor: com.amazon.avod.thirdpartyclient (PID=1669 ns=mnt:[4026533836])
[Magisk] adri_360:
Why safetynet not pass with linked Apps to SD with Apps2SD?

MIUI 8 MM.
[Magisk] jenslody:
You can mount the magisk.img in recovery with MagiskMount or manually and remove the folder of the module.
[Magisk] exodius48:
[BUG REPORT][OREO 8.1] Magisk can't recognized module even after phone reboot

Recently i get issue magisk can't recognized module even after phone reboot if i install module via magisk manager. All module always show with red line "module will be updated on next reboot". But when i install it via twrp, all fine. See attached screenshot!

Even my issue solved by installing all module via twrp but this is just bug report and let [MENTION=4470081]topjohnwu[/MENTION] know it.

Tested on magisk v14 stable & v14.5 beta. Android oreo 8.1 Pixel Experience rom.
[Magisk] JimZiii:
ok thnx, what rooting method would you recommend?

my honor 8 is broken so until i get that back i got this ace 4, but its locked to another carrier and i found an app that says it can unlock it for free but root is needed.

so i basically just need it temporarily
[Magisk] Badger50:
Oh dude, I'm so far removed from Sammy and rooting, about all I remember is that you'll probably need Odin on your pc, and likely SU 2.54, and maybe SafeStrap for recovery. Other than that, I'm of no further assistance. Good luck :good:
[Magisk] cadill:
Crashing Pixel 2 XL

I have exactly the same symptom on my Pixel 2 XL. Magisk 14.5, Manager 5.4.3. After some time (not very long), all apps crash and phone restarts.

I've disabled the Magisk Hide option in the settings and restarted. Phone seems to be better now.

Hopefully there will be a permanent fix soon.

Thanks for this thread.
[Magisk] Alxoom33:
Sorry, I can't help you with that information. Perhaps you can check your device forum.
[Magisk] badhabit_wb:
Just flash the factory image with the -w removed to get rid of that. I got magisk working on my og pixel a few minutes ago. I flashed the patched-boot image and then, after a reboot, booted to a twrp image and installed the zip wiped cache/dalvik and now it's working. Might want to give that a shot.
[Magisk] masdaster:
Thank you for this large support thread and the persons who spend their time to help others finding solutions!

I searched for an existing description of my problem, but I haven't found one. I hope, that I have nothing overlooked and that my English is not so bad... ;)

Since the last update of Magisk Manager to version 5.4.3 I have randomly lost root. I'm using a firewall which applies the rules after each connectivity change. Because of that the app asks for root very often. A few minutes ago the firewall notified my again, that it cannot get sufficient rights. Magisk Manager logged that it rejected the request, even though I granted root access for it before. The app was also marked as allowed in the settings. After waiting a few minutes root access is available until the next 'crash' has happened.

I hope, you can help me. Thank you in advance!

Here is the log:

--------- beginning of main

I( 2439: 2439) Magisk v14.0(1400) daemon started

I( 2439: 2443) ** post-fs mode running

--------- beginning of system

I( 2439: 3825) ** post-fs-data mode running

I( 2439: 3825) * Mounting mirrors

I( 2439: 3825) mount: /dev/block/platform/dw_mmc.0/by-name/SYSTEM -> /dev/magisk/mirror/system

I( 2439: 3825) link: /dev/magisk/mirror/system/vendor -> /dev/magisk/mirror/vendor

I( 2439: 3825) bind_mount: /dev/magisk/mirror/bin

I( 2439: 3825) * Mounting /data/magisk.img

I( 2439: 3825) * Running post-fs-data.d scripts

I( 2439: 3825) * Running module post-fs-data scripts

I( 2439: 3825) * Loading modules

I( 2439: 3840) * Starting MagiskHide

I( 2439: 3840) hide_utils: Hiding sensitive props

I( 2439: 3840) hide_list: [com.google.android.gms.unstable]

I( 2439: 3840) proc_monitor: init ns=mnt:[4026531840]

I( 2439: 3882) ** late_start service mode running

I( 2439: 3882) * Running service.d scripts

I( 2439: 3882) * Running module service scripts

I( 2439: 3840) proc_monitor: zygote ns=mnt:[4026535557]

W( 5876: 5876) su: request rejected (10053->0)

I( 2439: 3840) proc_monitor: com.google.android.gms.unstable (PID=6834 ns=mnt:[4026535565])

I( 6839: 6839) hide_daemon: Permissive detected, hide the state

I( 6839: 6839) hide_utils: Re-linking /sbin

W( 8200: 8200) su: request rejected (10053->0)

I( 2439: 3840) proc_monitor: com.google.android.gms.unstable (PID=12647 ns=mnt:[4026535583])

I(12652:12652) hide_daemon: Permissive detected, hide the state

I( 2439: 3840) proc_monitor: com.google.android.gms.unstable (PID=20747 ns=mnt:[4026535635])

I(20753:20753) hide_daemon: Permissive detected, hide the state

--------- beginning of crash

E(24955:24955) select failed with 2: No such file or directory

W(24955:24955) su: request rejected (10086->0)
[Magisk] dunderball:
I can't get it to work with HSBC USA app, but all they do is shoot out a warning and that's it. I'm surprised it was able to detect it.
[Magisk] daddylonglegs:
What's the patched boot image? Some sort of special boot image for Pixel users that want to use Magisk? Where do I obtain it?
[Magisk] boilednut:
Post Deleted

Post deleted.
[Magisk] RIPAciD:
It doesn't work for me, prob because the app was updated?

Anyone knows if the checked apps in Magisk Hide list are supposed to ask for root permission?
[Magisk] Pkt_Lnt:
Magisk Release thread.

https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
[Magisk] Lamba92:
I don't know, I switched to OnePlus 5 and i'm still stock with locked bootloader so I haven't done further researchs. A friend of mine who got an LG G4 with LineageOS official is not able to make PayGo work. The given error is a generic internal error instead of the root detected error so I suppose it's not magisk the problem and magisk hide is working properly. Maybe they check the bootloader integrity somehow or maybe they have a list of all official ROMs and if you are not using one you're out! I don't know tho, it's just an assumption!
[Magisk] daddylonglegs:
Thanks so much for this reply! Believe it or not, I did all your steps and when I booted into Android, Magisk said I was not rooted.

However I then went into TWRP and flashed magisk14.5 and it works now!! Thank you so much!!

The only issue is I need to edit my build.prop file and that is in the system folder. I understand that the entire point of Magisk is not not touch the system folder, but I have to edit this file. Is there any way to do this? A way to tell Magisk to let me have write permissions to /system for a little bit?

Oddly enough I googled this and no one seemed to ever ask this before
[Magisk] Pkt_Lnt:
Magisk Modules

https://xdaforums.com/apps/magisk/how-to-edit-build-prop-magisk-t3588599
[Magisk] daddylonglegs:
Thank you!

It actually turned out X-Plorer didn't allow changes to the system even though I granted it root access. I tried ES File Explorer, and I was able to edit build.prop that way. I wonder why people go through all the trouble in the link you gave me? Maybe I am missing something?

You did pique my interest about something after I read that link. Does it do "on the fly" system edits or something, without actually editing the system files? The reason I ask is that I really want the day of the week along with the date in my status bar. This is accomplished by editing the file res\layout\status_bar.xml

Is there some way to have an "alternate version" of my status_bar.xml, so I get the day of the week in the status bar without having to actually mess with actual system files?
[Magisk] RIPAciD:
This app doesn't seem to check the bootloader integrity cuz mine is unlocked...

Some things I've tried:

Uninstall Magisk => COMPLETE UNINSTALL -- stock boot image NOT restored (Set Warranty Bit : kernel) >> PayGo fails but manually flashing stock kernel fixes it.

Uninstall Magisk => RESTORE STOCK => COMPLETE UNINSTALL -- stock boot image restored >> PayGo passes.

Now you tell me... :)
[Magisk] muksathegreat:
Wipe data cache and reflash
[Magisk] Pkt_Lnt:
Yes

As you stated above, Magisk is all about *NOT* altering /system. Using a root file manager to add or change anything in /system defeats that entirely.
[Magisk] daddylonglegs:
True, but I made such a minor edit I am sure it is not going to trip anything. It's the same thing that would show up in build.prop if my phone had unlimited tethering.

And where can I learn about editing the system_ui/staus_bar.xml for Magisk?
[Magisk] Xenomorphys:
Nobody can help me?

it gets really boring ...

thanks you very much
[Magisk] tag68:
You know that mounting system rw is preventing OTA because system is marked as changed even if you don't edit anything?

How do you edit something on the system partition without tripping that mechanism?
[Magisk] Lamba92:
Can you please give some details on phone, ROM and kernel used in both steps? By "RESTORE STOCK" you mean the entire ROM?
[Magisk] Maverick_TN:
Anyone else failing basic integrity check now? Think there was an update last night with some if the Google framework.
[Magisk] Maverick_TN:
Either google has caught up again, or something is borked with my flash.