yashsingh1/xdaforums huggingface dataset:
[Magisk] xunholyx:
Have you tried downloading the Magisk.zip again? Maybe your current download is corrupted.

Or you could confirm your current download's checksum.

SHA1 should be: ed0d739c3923b19c6a73ee0df1c7888e0353601d

MD5 should be: 3ab4d455e6f27f0098c1a723705c6ea1

Check one or the other to see if you get a match

I'm probably not correct here, but it can't hurt to check
[Magisk] clambert11:
Yeah, it matches. The patched boot image I made didn't work either and that doesn't use the the Magisk.zip. Thanks though.
[Magisk] chooks06:
Phone must be in download mode.

File should be .tar format.
[Magisk] hamonmaru:
Anyone facing latest magisk manager is slow to open?

All menus take times longer to open than previous one
[Magisk] badabing2003:
Thanks [MENTION=4667597]Didgeridoohan[/MENTION]

I captured logcat filtered by Magisk.

I don't see much that would hint at what is going on, (see below) maybe you see something in there.

I rebooted, started logcat and then Magisk Manager, which detected Magisk to be installed, then killed the manager and started it again, which at that point it no longer detected Magisk to be installed.

Stopped logcat.

View attachment logcat.txt

Thanks

BB
[Magisk] badabing2003:
This time I captured from the PC to make sure that the capture started with boot.

I think this one is better, but am not sure if it sheds any light.

Line 707 is when I killed the Manager

Line 719 shows that it I need to update Magisk

View attachment logcat2.txt

Thanks

BB
[Magisk] JIJOK:
I know its a busy thread but need help and have no clue

my phone : -rooted with magisk 18.1

- magisk manager not sure but is not v7 since ask to update

- custom ROM lineage 14

the problems occurs when I try to update magisk manager to v7.0.0 ( 185 ) , it "updates" and show new UI but then it marks as magisk is not installed asking to update ( download zip ). If I quit magisk or reboot, it roll back to old UI again asking to update flashing the zip with TWRP is not working. Logs I get when update, quit and re open are :

213 9922 E magisk : read (4!=0) failed with 2 : no such file or directory

9977 9977 E magisk : write failed with 32 : broken pipe ( 2 identical mesagges )

Any help ? Just uninstall from magisk and re install maybe
[Magisk] martyfender:
https://www.didgeridoohan.com/magisk/ManagerIssues

https://www.didgeridoohan.com/magisk/HomePage
[Magisk] X0LARIUM:
I'm on a Nexus 6P, Android Pie latest ASOP.

And guess what? Magisk slows my system, doesn't allow installs from the Playstore and overall stutters my entire system to a halt.

And I did EXACTLY everything on the "official" post mentioned.
[Magisk] RandomPooka:
That's a bummer. I guess don't use it? It's working fine for most.
[Magisk] X0LARIUM:
Or course I won't. Lol
[Magisk] ante0:
This might be a twrp error. Can you post a link to the twrp you use?
[Magisk] bgamez23:
http : // www . mediafire . com /file/zu8nluc56s7qwqw/
[Magisk] mapbond:
After upgrading to latest Magisk v18. 1 google pay fail to pass. Magisk hide doesn't work. Help is appreciated.
[Magisk] ilia1985:
There is a chinese modified magisk 18.1 installer that installs and works fine on mix 3 system-root.
[Magisk] y2knarayan:
The only way to get Google Pay to work with Magisk is by Disabling Phone and Messaging permissions of Google Play Services App
[Magisk] clambert11:
So another update to this. I tried an older version of TWRP and an older version of Magisk for giggles and it didn't make a difference. Has anyone successfully installed Magisk on a fresh version of stock Android 9.0 with the Feb. security update on a Pixel XL (Marlin)? I'm out of ideas and not finding much online to resolve the issue.
[Magisk] mapbond:
Thanks it works but it temporary solution i believe..

---------- Post added at 02:18 PM ---------- Previous post was at 02:16 PM ----------

It worked but I think it's temporary solution....
[Magisk] Joshxp:
Hello, i just want to ask... On MIUI 10 dont know after which update. After installing Magisk, my face unlock has deleted. Anyone know for solution ? I still want to use magisk too.
[Magisk] Didgeridoohan:
Yes, it shows when you kill the Manager and when it prompts for the update, but it might be the stuff that happens inbetween that is interesting (the stuff that you cut out by filtering strictly on "magisk").

Hm... Interesting. Sounds like you have some app or process that is going rampant/hanging/or something and is causing issues. If you're actually here to get help and not just to rant, grabbing some logs would be a good idea since this is obviously not normal.

Your TWRP is likely too old and not up to the task of installing Magisk. Try the patched boot image method instead.

By "TWRP loaded image via fastboot" I'm assuming you mean that you didn't install TWRP but only booted the recovery image. If so, that's good... :good: If not, try that instead.

[MENTION=4470081]topjohnwu[/MENTION] uses a Pixel 3 XL daily, so the chance of Magisk not working on a Pixel device is low. Was your fresh installation of the February release a clean install? Might be something causing issues in the background.

Also, you might want to take this to the Pixel XL forum if you haven't already... Usually more device specific expertise there.
[Magisk] y2knarayan:
There is no other solution right now
[Magisk] Rom:
@Didgeridoohan

Hello, idk if you have fingerprint sensor on your device and so if you will be able to have an idea of my problem.

After having updating Magisk on my device to v18.1, the option to enable the authentification by fingerprint is unavailable.

With v17, this option was available.

Concerning my device, i use my fingerprint to unlock my device and with several apps/services, it works fine.

I'm not sure that a logcat will be helpfull for this type of problem, or maybe the magisk logfile but it don't show infos concerning fingerprints.

Has you are a "power user" of Magisk, i say myself that u would have an idea :)
[Magisk] LilSasa:
Hi. Can you look into this? Thanks :)
[Magisk] Didgeridoohan:
[MENTION=5332893]Rom[/MENTION] I actually have no idea what that could be. Fingerprint authentication for superuser requests works perfectly for me (don't think I have ever had any issues with that). Have you tried removing and readding your fingerprint?

[MENTION=4850210]LilSasa[/MENTION] Not at the moment, no... I'll see if I can find some time next time I'm at a computer (it's a pain to read logs on a phone). If you haven't heard anything from me in a week or so, remind me. But, I must say that I'm not that good at reading logcats, and it's far from certain that it actually will show anything...
[Magisk] mrspeccy:
A protection against the "socket poking" done by MitNykredit app and other apps has made it into the latest Canary build.
[Magisk] Rom:
Thank you, it works for me.

Simple idea, but I didn't have it in mind yet.
[Magisk] clambert11:
Yeah, I booted TWRP via Fastboot and flashed it that way. The phone was totally wiped clean with the latest factory system image (Feb) and then restored from the cloud. Hitting up the Pixel XL forum is a great idea. I'll try that avenue too. Thank you!
[Magisk] badabing2003:
[MENTION=4667597]Didgeridoohan[/MENTION]

Thanks for the follow up.

Just to update you, restarting fresh resolved the issue, i guess something was corrupted the first time around.

Thanks for your assistance.

BB
[Magisk] YouheiPlayer:
I need help on 18.1 Magisk and MM 7.0,

I successfully updated to 18.1 using TWRP 3.1.1 (MM 6.0.1 verified it).

After updating Magisk, I updated MM to 7.0 but there was a problem. There's only 2 tabs which consist of Home and Settings tab(Settings tab of 7.0 was so inferior when I used 6.0.1, the Magisk Hide went missing and others as well, or there was a malfunction on my part.)

Even so, the settings of the rooted apps I granted root access still works but the SuperSU and Module Tabs in 7.0 were missing.(and quite a few of them is missing/quite almost)

I tried restarting my device or clearing data of the app will do the trick but it didn't.

Clearing Data doesn't do anything.

Restarting my phone... My phone automatically reverts 7.0 to 6.0.1 Magisk Manager after I restarted my device which I really cannot believe my phone "how the heck did that happen?".

After its reverted back to 6.0.1, 18.1 is still active (even though 7.0 didn't detected it.

Note: 7.0 MM is now slower at detecting or determining the statistics of the Magisk's version than before (7.0 takes 5-8 secs plus, 6.0 takes 2-3 secs)

Note2: Not much apps are running and I have much to spare in my 2GB RAM.(1.2gb RAM)

I tried using a rooted app with my 18.1 Magisk but 6.0.1 MM, but it seems to be missing its popout box to grant its rooted access (this part doesn't really have any connections to Magisk but I will still post it as a reference), btw Using Xposed.

Thank you very much in advance for your continued assistance.

[MENTION=8504661]garylawwd[/MENTION]

Thank you for the heads up, will now be careful.

Also, I don't know the term of getting shot and I wouldn't want to be an example. Anyways I edited my post.

Btw, its always internal, I wouldn't use SD card because of many restarting I do (its internal default in settings) and will check every app related to root.

#Updated: I solved my own problem.

This is how I solved it.

Did you know when you update your old app into the latest versions?

Its common sense to say that the last version will be overwritten by the latest version (in short, they will overlapped/auto uninstall-install process)

But Magisk Manager has a kind of a flaw or have some kind of different signature package.

Before installation of MM 7.0, the note of android saying "Are you sure to install this apk, your version/app existing might be overwritten" or along of those lines.

My MM of 6.0.1 did not made any overwritten process, meaning; when I installed MM 7.0-its like I installed a different app with a different signature or a clone of MM.

And the result was, 2 MM installed apk.

1 with a 6.0.1 and another with the 7.0!
[Magisk] garylawwd:
Is magisk manager installed on external memory? If yes move it to internal

And also Lucky Patcher isnt talked about around here, could get you shot..
[Magisk] Mueslix94:
Hey there, may youre able to help me. If I use Titanium Backup in Connection with Magisk I may not merge System App Updates into the System Part, same with link2sd, usw they say I may not given privileges, just magisk Manager says that.

Another Problem with magisk I encountered Was the fact that I now cannot use magisk an more because I turned on in the Manager preferences to use namespace separation, so from that on I never was able to achive root Fights again with the magisk Manager itself. Where are those config files hidden even a change to the Stock / Customkernel I use didn't change anything.

Max anybody help me with those Problems to find a solution? Meanwhile I Was forced to migrate back to Supersu, which after some failiure with the magisk uninstaller allowed me to use my beloved titanium backup to switch Apps storage space.

Thanks 4 your help so far..

BTW there were some Infos in the screen down this post
[Magisk] zipsu:
Did you try flashing magisk uninstaller zip in TWRP? It should get rid of all residuals. Also /data/adb/ directory contains some magisk stuff if the uninstaller fails for some reason, it should make it forget its config.
[Magisk] Mrpookie:
Should have taken a video of the root fights with magisk.

I've had no problem using TiBu with magisk from android 7, 8, or 9 with RR on my turbo btw
[Magisk] Mueslix94:
Yep, nö effect, magisk was still active until removal, but the Connection to the Manager seemed to be brocken and of Course to link2sd or sort of, unexpectedly esexplorer worked and I got toast notification about aquireing root rights, kinda wierd
[Magisk] martyfender:
I believe he asked that question, since [MENTION=4470081]topjohnwu[/MENTION] recommended not flashing TWRP, but only temp booting it with fastboot, as apparently it can cause issues if flashed. I, for one, don't understand this, as I don't have a type A/B device, where the boot.img and recovery are in the same, not separate partitions, apparently the recovery is in the ramdisk.

I am sure that he has a good reason for this recommendation, though. Possibly, the above recommendation could help.
[Magisk] J4jks:
When dirty flashed my rom over magisk 18.1,

it didn't boot ,went to fastboot mode.

from there i went to recovery and took the logs

after flashing rom magisk pached boot with saying found avb1.

My device is Moto G 2014, using los14.1+ magisk 18.1

it happened earlier too

thanks
[Magisk] Mk™:
What needs to be done?

Huawei Y6 Pro(TIT-AL00)

Flashed with PreRoot StockRoM
[Magisk] roscos:
I am in the same condition as you

But I do not understand why Xposed can not be installed from Magisk Repo
[Magisk] chooks06:
I can only guess that it could be the versions in the repo are not updated to be compatible with Magisk 18.1 yet.

I remember seeing some modules updated to unity installer v3.4.

Anyway, I usually flash Xposed directly via TWRP.

Only guessing..:o
[Magisk] Didgeridoohan:
You've already kind of found the solution, but I thought I'd just chime in on what's happening...

Basically there's a bug in Manager v6.1.0 that has been fixed with v7.0.0. This means that if you have v6.1.0 hidden/repackaged it won't be able to install the v7.0.0 Manager properly. More on that here: https://didgeridoohan.com/magisk/Magisk#hn_Updating_from_v18.0_to_v18.1

Sounds like the addon.d survival script is messing things up somehow. What happens if you manually flash the Magisk zip after the ROM?

First thing to try is to toggle MagiskHide off and on. If that doesn't work, do you have Xposed installed? For more troubleshooting: https://didgeridoohan.com/magisk/MagiskHide

And there's also this, of course:

https://github.com/topjohnwu/Magisk/issues/907

But, this only affects some devices so start with making sure that everything works first.
[Magisk] saccentekennedy:
For those on OnePlus who, like me, couldn't update to 18.1 due to the phone not actually rebooting after 18.1 installed from MM (I had to rebuild my phone!)... Has anybody figured out what went wrong and how to solve it?
[Magisk] Kglim:
If i turn on my secret mode in samsung browser safety net checks get fail. Is this a normal thing??
[Magisk] Didgeridoohan:
Care to provide some more details? Are you talking only about newer OnePlus devices with A/B (6/6T), or any OnePlus device? I'm asking because I'm sporting a 3T that I haven't had any issues updating (and I test a lot of Magisk builds). I have not heard about any widespread problem with OnePlus devices in particular...

And did you really have to rebuild your phone? So far I have not found any situation where a non-booting device (as a result from a failed or otherwise broken Magisk installation) couldn't be fixed by just installing a stock boot image and then reinstall Magisk.
[Magisk] J4jks:
Same, after flashing rom, magisk installs with add-on then I flashed magisk again this time it showed arm and so on but didn't boot

Then from fastboot to recovery removed magisk add-on , dirty flashed ROM , with magisk .

Now it boots.
[Magisk] mjemec:
Poco F1 Xiaomi.eu rom 10.2.2 on Magisk 18.1 getting a lof of safety net faliures in the last 24 hours.
[Magisk] saccentekennedy:
Sorry I was light on details. I'm on a 6t. I updated from the prompt in Magisk Manager. On reboot, I got a black screen and no response. Eventually, I managed to reboot into stock recovery. I put in my password and the next thing I know the message, "Wiping all storage" came up! I didn't ask to do a factory reset (unless this happened when the screen was black and I was frantically pushing the buttons).

I ended up booting into Fastboot and reinstalling my ROM, then I had to restore all my apps via TiBU.

In the OP 6t forum on XDA, there are at least 3 of us where exactly the same thing happened. Update... Reboot... Black screen, non responsive.

Hope that helps with more detail?
[Magisk] Didgeridoohan:
Kind of. It doesn't give any hint as to why though... Providing logs and/or exact steps to reproduce might help.

Did you manage to install v18.1 after that?
[Magisk] huangjqiu:
It's weird. I have flashed 18.1 but it shows not installed. How to fix the problem?
[Magisk] teddy0209:
You might have a hidden manager... Check if there's two... Delete the one with magisk it the name...
[Magisk] Didgeridoohan:
Try:

https://www.didgeridoohan.com/magisk/Magisk#hn_Updating_from_v18.0_to_v18.1
[Magisk] zagzag99:
MagiskHide faling on me

I'm suspecting that it happened with 18.1.

I have apps like TeamBlind that identified the phone being rooted and blocked me out although it's been on my hide list before the upgrade.

Anyone else find hide failing ?

Unfortunately I have other apps which I need on daily basis and used to work and now blacklisted my device for being rooted.

Edit: I got temporarily workaround the block by changing fingerprint and adding 'improved hide' with the Props&Hide module but a couple of hours later the apps identified the device being rooted again. :(
[Magisk] clambert11:
I guess I wasn't clear. I did install it this way. Both the zip file and the patched boot.img file. Both gave me the message Can't load Android system. Kinda crazy. I may just try an flashing an older system image because I'm not making much progress.
[Magisk] saccentekennedy:
I haven't even tried to go back near 18.1 at this stage. I wonder whether I should try using TWRP to install it so that even if it borks I can just reflash stock boot image?
[Magisk] remush:
Hi all,

I have used twrp + magisk + a root explorer so I could edit build.prop and get s health working on my Galxy S6 SM-G920I ( Android 7.0 ) ( G920IDVU4FRH2_G920ITEL4FRI1_TEL Stock Rom )

So I have got s health working ok, and want to remove Magisk and twrp....

If I uninstall Magisk using the manager app, phone reboots and ends up in a boot loop showing Samsung logo and reboot.

If I use the Magisk uninstall zip I downloaded I get the same result.

Is there a way to uninstall Magisk from my device without having to flash the stock firmware and wipe the whole drive ?

Thanks :)
[Magisk] badabing2003:
Unfortunately the issue is back.

Kill the manager or wait long enough and it reports that Magisk is not installed.

All the errors in logcat between killing the Manager and starting it again is attached.

View attachment logcat3.txt

Could this have anything to do with it?

02-12 08:33:23.169 9788 9788 E opjohnwu.magis: Not starting debugger since process cannot load the jdwp agent.

Should I be going back to Magisk 18.0 ?

Thanks

BB
[Magisk] AndrOmega:
what's this: Magisk Manager v7.0.1-2019020701-ianmacd

i saw this on some site
[Magisk] guest4711:
It's a bleeding edge build, see https://xdaforums.com/apps/magisk/unofficial-magisk-v10-beta-built-t3521901
[Magisk] martyfender:
It is an unofficial build of Magisk compiled with the source code. That one is several days old. the latest is available here:

https://github.com/ianmacd/MagiskBuilds

The thread for unofficial builds is here:

https://xdaforums.com/apps/magisk/unofficial-magisk-v10-beta-built-t3521901

I use these builds myself. They often include commits by [MENTION=4470081]topjohnwu[/MENTION] newer than what are included in his Canary builds. They are cutting edge, but can also contain bugs. Make sure you have good backups or know how to recover if something goes wrong.

Since the Magisk Manager in these builds are signed with a different key, you must first uninstall your current

Magisk Manager only

, before installing this one or it will fail to install.
[Magisk] vergilbt:
Only for my understanding...

This behavior depends on new Magisk or new Google Pay app?

Google Pay was running last few months with Root by Magisk.

Since last update to 18.1 I can't pass safety and Google Pay isn't accept any transaction in supermarket.

Chance by downgrade Magisk?
[Magisk] Valeryan24:
18.1 Update ctsProfile false on Nexus 6P

Hi, first thanks a lot for all the hard work on Magisk !

I updated this morning Manager to v. 7 on my Nexus 6P rooted, running on LineageOS 15.1 - I had to manually uninstall v. 6 because previously hidden but managed to get v. 7 as default, then updated Magisk to 18.1.

I tried all the steps : clear app data and cache, unhide, reboot, reinstall 18.1 and modules, reboot, re-hide etc... But I still fail the SafetyNet ctsProfile test (false), as basicIntegrity is OK.

Does someone have an idea of what to do to get it work ? :)
[Magisk] woozie.2007:
Hi, anybody has an idea about of enable fingerprint authentication for root access? I tryied to enable this option and says authentication failed. Thank you
[Magisk] warrencoakley:
Install Audio Patch Module first

Then V4A

Then AML Module

Should be good to go
[Magisk] Paschfire:
Device?

Android/ROM version?

Magisk version?

Magisk log?

Logcat?

Any information regarding your device and current setup?

Have you looked through the Notes & Troubleshoots Wiki found within the OP through the linked Announcement thread for possible solutions?
[Magisk] woozie.2007:
moto g5 stock 8.1 rooted with magisk 18.1, I have two moto g5, mine not works but the phone of my wife works. My phone worked before the last december security update. I don't know what to do, but thank you for the answer
[Magisk] zipsu:
I don't know why, but I had the same issue a while ago. Updating didn't fix it and I couldn't be bothered to uninstall it, so what helped was.. enable "hide magisk manager", you can revert it afterwards, but it fixed it for me. It has something to do with the manager not magisk binaries.
[Magisk] mayelz:
should i delete /sbin/.core folder since it is deprecated?
[Magisk] jcmm11:
NO!!

It will, eventually, go away on its own - but at the moment it's a symlink to /sbin/.magisk/. So if you just delete the folder (and it's contents) you'll be deleting Magisk (well, most of it). Plus it would probably just come back at the next boot when Magisk reinitializes itself (minus any modules you had installed etc)

If you just remove the symlink that won't hurt anything, but again it'll just come back at next boot.
[Magisk] woozie.2007:
thank you my friend, it works for me too
[Magisk] Didgeridoohan:
It likely started working because the reboot restarted MagiskHide. Sounds like you're affected by this:

https://github.com/topjohnwu/Magisk/issues/907

Unless someone with an affected device can give actual useful info on what's working and what's not there's never gonna be any fix for potential issues...

I doubt that error has anything to do with it (it's got to do with debugging Java), but like I said earlier my log reading skills are limited. I can't see anything special in there, but it isn't certain that the problem manifests as an error. A full logcat without the heavy filtering might be necessary.

*Shameless self-promoting*

https://xdaforums.com/apps/magisk/module-magiskhide-props-config-t3789228
[Magisk] shneor:
I thank all who worked on this easy to use rooting app. I have a BLU Life One X2 phone, using custom ROM SGRX2. I had a version of Magisk installed, 17.something, all working well, no problems for months. I never hid Magisk. I got an update notice and installed a new Magisk Manager. When I ran it, I received a message that the manager did not work with versions less than 18 and I should either install Magisk 18.1 or de-something the Manager. I decided to install 18.1, which I flashed through TWRP Recovery. Upon reboot, the boot hung for 5 minutes. Tried again, several times, no change. (Stupid, I know in retrospect.) So I decided to reinstall SGRX2. Same thing happened. Tried to install just the boot, no difference. I can boot to recovery, no problem. I can see files in internal storage. I might be able to recover TWRP logs, and maybe see Magisk logs in internal storage, but don't know how to copy them elsewhere. I can remove the sd card if necessary. I would appreciate any help with this,