yashsingh1/xdaforums huggingface dataset:
[Magisk] hfam:
Awesome!! [MENTION=4667597]Didgeridoohan[/MENTION], you are a legend and have my undying gratitude. Thanks so much for the quick reply and for the continuing education! You're right, it's definitely not intuitive (to me anyhow) but your explanation made it easy!

Now I'm able to continue to use the same method of sec updates and patching boot I prefer, while opening up more flexibility in how and when I apply a particular version!

Im now setup using the custom link for v20 json, so I can install Nov Q update and just use current MM to patch the boot with 20.0 (currently installed on Oct update) until I'm ready to (or need to) install the next Magisk update.

Again, eternal thanks for this and all you do to support Magisk for so many of us! Thanks also to the rest of you who provide so much support out here, you know who you are! ;) :cool:
[Magisk] hackermssharma:
But just before 1 day everything is working fine i wonder how suddenly riru core module is breaking the saftynet?
[Magisk] Johnn78:
Can be fixed on some new update of Magisk or the change is permanently ?
[Magisk] martyfender:
I believe is was by design.
[Magisk] Didgeridoohan:
One variant of the issue, possibly.

Google updated something in their side, maybe?

Unless Google changes how SAR works, it's unlikely that [MENTION=4470081]topjohnwu[/MENTION] will make any changes either. Consider it permanent, for now.
[Magisk] meiser:
Hi,

after updating to Magisk 20.1 with Magisk Manager 7.4.0 (running on Xiaomi Mi 9T Pro with LineageOS 16.0), the app always opens automatically after a system start - after shutdown or reboot. It's hidden and the app name is "Assistant".

Can someone confirm this behaviour?

Regarding the EdXposed issue, a solution/workaround was posted at GitHub .

Regards,

meiser
[Magisk] halfbytecode:
With Magisk 20.1 and Magisk Manager 17.4, Magisk Manager crashes every time the phone boots.

Crash log: https://del.dog/xiyakezala

Phone is Oneplus 5T running AOSiP 9.

[MENTION=4470081]topjohnwu[/MENTION]
[Magisk] lekiaM:
Are people here successfully flashed V20.1 on OOS v909? Without issues or rootloss?
[Magisk] Johnn78:
Anyway, with 19.3 there wasn't any problem which means that something changed in v20 & the system is uneditable.
[Magisk] winstonlu89:
I'm having this behavior on my p2XL also, stock rom. the app opens itself 3 times after boot.

only happens if I've hidden the app to another name.
[Magisk] sadiku:
Can someone check your SafetyNet if still pass, somehow I got the fail today, it was pass before.

Magisk:20.1

Magisk manager:7.4.0

Phone: pixel 2, Android 10.
[Magisk] BHUSHAN7988:
Did you use edxposed if yes fails for me also

Magisk 20.1/7.4.0

OP6T

Edxposed 4.6.0 sepolicy within edxposed zip
[Magisk] sadiku:
Yes, I have Edxposed 4.6.0 installed, but it was pass until today I got fail, so stranger..
[Magisk] meiser:
Please scroll back to read the thread, the topic is already covered.

But again, regarding the EdXposed issue, a solution/workaround was posted at GitHub.
[Magisk] sadiku:
Thank you so much.

The workaround is work for me.
[Magisk] Didgeridoohan:
As I've already stated, and from what you can read in the link to the release notes I've posted for you, that's intentional and following Google standards. You'll just have to live with it (or stay in the past).
[Magisk] Kursem:
Hello everyone, I have a question regarding Magisk installation. I have an old device which is Vivo V5 1601 running on FW 3.14.5 based on Android Marshmallow, with bootloader already unlocked. I have been thinking to root this phone for fun, but it doesn't have any working TWRP build, it didn't even have dedicated forum here, that's why I'm going to ask it here. So, I'm using boot image patching method, with boot.img taken from Vivo website. I've also attached the stock boot image file if anyone want to look at. Anyway, I've patched to stock boot image with Magisk Manager, then copy the magisk_patched.img file to my PC. After that, I reboot my device to bootloader, I checked first to make sure if my bootloader are unlocked it does say yes, then I flash it with fastboot boot magisk_patched.img command using minimal adb fastboot 1.4.3 portable. Then, after it's completed, I reboot my device but it went into system repair mode. So I went back into fastboot mode to flash stock boot.img and it did boot successfully. I didn't know where I went wrong, does anyone could help me out please? Thanks in advance!
[Magisk] tbqstp:
Yes, over v20 (I'm encrypted, with installed Magisk mods: viper legacy and systemless hosts).

Steps:

1) Using codeworkx latest recovery (twrp-3.3.1-0-20190713-codeworkx-cheeseburger.img) flashed boot.img extracted from OOS v909

2) Flashed Magisk v20.1

3) Wiped cache/dalvik

4) Rebooted
[Magisk] Macusercom:
I've got the same thing going on. I'm using a OnePlus 6 with a clean flashed OOS 10.0.0. It doesn't happen with the normal non-hidden Magisk Manager. Maybe it's a bug that will be fixed or it is intentional and necessary :confused:
[Magisk] wilsonhlacerda:
EDXPOSED x SAFETYNET

yes, there were some Google updates that started detecting EdXposed modules are running. If disable the modules on EdXposed Manager (not on Magisk Manager) it is enough to pass SafetyNet again.

Thus I found an WORKAROUND: put Google on black list. More info check the Issue on Github: https://github.com/ElderDrivers/EdXposed/issues/386
[Magisk] mixlex:
Ok here. It was a clean flash of v909.
[Magisk] ungasX8:
am i the only getting one cts profile false again ?
[Magisk] lekiaM:
Thanks. I'm gonna try that procedure. Its time for a clean flash (anyway)

Cheers:highfive:
[Magisk] hackermssharma:
Same here bro suddenly edexosed breaking the saftynet for me also
[Magisk] eg1122:
Check this post

https://xdaforums.com/showpost.php?p=80807687&postcount=33
[Magisk] hackermssharma:
Thankx mate worked
[Magisk] Strephon Alkhalikoi:
So important you had to say it half a dozen times. ;)
[Magisk] hackermssharma:
Sorry my internet is slow so i continuously getting the toast that post creation felled. So i keep posting again and again and when internet speed get back they all get posted
[Magisk] martyfender:
That seems to happen more frequently here on xda for me and I have a high speed cable internet connection. I think it is either xda or a backend problem.

Irregardless, I have found just waiting after hitting post button, instead of continuously re-hitting it eventually works, most, but not all of the time. Go back a page or two then come forward to the current and you will often see your result posted. However, there may be a better way. I would suggest that you go back and edit out all of your duplicates, though, to help others reading in the near future.

Thanks
[Magisk] ahmadpower:
Is this a general problem and bug? And we have to wait for it to be solved, or it has another solution?
[Magisk] Strephon Alkhalikoi:
Relax sir, as I was only teasing. The wink emoji was supposed to let you know I wasn't serious.
[Magisk] ktmom:
Did you follow the update instructions as stated in [MENTION=4667597]Didgeridoohan[/MENTION] post I quoted for you yesterday?
[Magisk] _litz:
Sooooo ... I'm stuck.

Brand new Pixel 4. Fastboot is unlocked. Put the boot.img on /sdcard, installed Magisk Manager.

Instructions say to click "Install" next to "Magisk is not installed", to patch the boot image.

There is no "Install" next to "Magisk is not installed" ... soooo ..... ?

Edit ...

On a lark, I used my old phone to patch the boot image ... shockingly, it worked.

I still have no option for "Install" or "Update" in Magisk Manager though.
[Magisk] ktmom:
Does your phone have internet connected (either mobile data or WiFi)? If yes, then I guess I would try uninstalling then re-installing Magisk Manager.
[Magisk] PoochyX:
You messed up the brand new Pixel 4 [emoji19]

([emoji3590]09-09-18[emoji3590])
[Magisk] _litz:
Well, no .... I patched it on my old phone, booted right up w/full magisk. So, I dunno.

I'm still setting things up, will see if the install options light up when all is done.
[Magisk] ktmom:
Magisk manager functions require internet access. You'll be fine when you get connected.
[Magisk] _litz:
So yeah, it's working. Titanium Backup, not so much. Freezing on just about every app restore.
[Magisk] ahmadpower:
Thanks for the reply.

I'm sorry didn't notice it before...

I think you and [MENTION=4667597]Didgeridoohan[/MENTION] are talking about the procedure for upgrade mentioned here :

https://github.com/topjohnwu/magisk_files/blob/master/notes.md

But I have now the latest version already which is v20.1.

So I tried to follow the steps after having the latest version already... I removed the hide Magisk option, then Fully rebooted, then started the option again, then rebooted again... But the problem still exist.
[Magisk] Didgeridoohan:
There are some bugs with the Manager and broadcasts, which is why [MENTION=4470081]topjohnwu[/MENTION] is currently trying other ways of having the Manager and daemon communicate.

That commit is in the current Canary builds (20102), so if you're up for helping with testing you could install that and see if things work better.
[Magisk] BillGoss:
I find that TB does fine on apps that are just a single APK (eg Gmail, Keep), but with apps that are split (eg Chrome, Maps) it hangs and I have to install them from the Play Store (and then restore the data).
[Magisk] outrage_uk:
I have managed to download an OTA update file (payload.bin) and extract the boot.img . (Android P with A/B Partitions)

The Manager is unable to patch it.

Is this likely to be a corrupt boot image, or a problem with Magisk?

I have attached the boot.img I am trying to use.
[Magisk] fash_ahmed:
I'm facing an issue of Safetynet failures after update to 20.1 and manger 7.4.

But magisk hide is still working on all my bank apps, though I had to clear data of the apps, otherwise they were detecting root.
[Magisk] fash_ahmed:
I'm using OOS 9.17 and have blacklisted all Google services in Edxposed.
[Magisk] ashyx:
I don't think it's a complete boot image, just a diff patch as it has a BSDF2 header.

You need the complete boot image.
[Magisk] tek3195:
Hello, I searched first but didn't find what I needed. I'm using Magisk with android pie (go edition) in Recovery Mode . This little cheap tablet is iffy on how it responds to hardware buttons or I just don't have the timing down yet. I am looking to boot or reboot from command line without using the buttons. When installing a module the manager handles the reboot and boots to a rooted system. Any manual reboot not done correctly with HW buttons is not rooted. So, how do I use the command line to reboot to rooted system ? May be more to it than I realize, but what cmd line does the manager use for same task ?
[Magisk] racunid:
Hi, I have a Samsung M30s. I want to root via Magisk Boot. I have done every step until the last step. And it works, after installing the xposed module it always reboots continuously?
[Magisk] _litz:
Which is exactly the same solution I found .... :)
[Magisk] Gitossan:
Dear all,

I have problem regarding magisk.

Whenever I try to hide magisk manager, it always failed. The other functions are normal.

Sorry I cant give outside link because I'm new user.

But this my screenshot link about the error

h*tp://im*ur.com/gallery/zDEiqFx

My phone is redmi note 5a prime

Os 7.1.2

Original rom miui 8.5.1 global stable

Internal storage free about 8gb

I root my phone via twrp

I already try using magisk version 18->20.1->19->20 but still has that problem.

I uninstall magisk via twrp using magiskuninstaller. So my file is clean.

I dont use custom kernel, custom rom, exposed.

I just install 1 modul= hide prop.

Thats all.

I hope user here can help me solve the peoblem.

Because now one bank apps can detect root when magisk hide active. So i need to hide magisk manager.
[Magisk] Qnorsten:
Go to playstore and disable play protect while performing the hiding in magisk manager
[Magisk] Gitossan:
Still got notification that hide magisk manager failed
[Magisk] ktmom:
You indicated that you tried a couple of different versions. Then flashed the Magisk uninstaller.

Did you also remove the manager at that time?

That's what I would do, remove the manager, flash the uninstaller in recovery, reboot to system, then return to recovery wipe caches and flash the current stable release? This way everything is on the same version (Magisk manager release needs to match Magisk release).

If that doesn't work, then you'll need to grab logs[\URL]. Specifically using the canary build (Magisk and manager) for the verbose logging, while attempting to hide the manager.
[Magisk] Komekokos:
Safetynet broken after update google play services with edxposed...
[Magisk] spawnlives:
Known issue try this work around

https://github.com/ElderDrivers/EdXposed/issues/386#
[Magisk] Gitossan:
Remove magisk manager with drag it icon to trash icon? Or click uninstall in bottom of magisk manager interface?

I dont wipe cache. How to do that?

I just watch youtube video when rooting my phone. And wipe cache isnt in the video.

Canary things make me confuse.
[Magisk] Komekokos:
Thanks I've tried it but unfortunately doesn't work in my case, anyway I'll follow the previous link to find a solution, many thanks
[Magisk] spawnlives:
After blacklist have you reboot the phone.
[Magisk] Rouzo7:
Need Help

TWRP Log

Updating Partition Details...

...Done

Full SELinux Support is present.

MTP ENABLEd

installing zip file '/sdcard/Magisk-v20.1.zip'

Checking for digest file...

************************

*Magisk v20.1 Installer

************************

- Mounting System

- Target Image: /dev/block/mmcb1k0p10

- Device Platform: arm

- Constructing Environment

- Unpacking Boot Image

- Checking ramdisk status

! Boot Image Patched by unsupported programs

! Please Restore back to stock boot image

- Unmounting Partitions

Updater procces ended with error: 1

Error installing zip file '/sdcard/Magisk-v20.1.zip'

Updating partitions details...

...Done

Error [MENTION=7245510]samsung galaxy s[/MENTION]M-A510FD...

help me...
[Magisk] Komekokos:
Well, I forgot to toggle on 'app list mode' from settings, once done that safetynet passes again. Thanks again :good:
[Magisk] Didgeridoohan:
Both the problem and the solution where presented to you right here.

Take a look at this:

https://didgeridoohan.com/magisk/Magisk#hn_Boot_image_patched_by_other_programs
[Magisk] Sutan99:
Does Magisk have a network traffic monitoring module in the status bar? because if it can be handled by one app (Magisk), why do I have to install another app, it can save RAM. On the other hand, Xposed is also detected dangerous by Google Play Protect, the notification is very annoying.
[Magisk] Gitossan:
I forgot to say that I use lazyflasher too after install magisk,

because in video that I watche, this lazyflasher can stabilize magisk.

I already try several suggestion from this thread but I still got hide magisk manager failed
[Magisk] Ricardo Flowers:
I installed the most recent magisk that came out which is 20, and in every rom pie that I install gives this error here that is in logcat.
[Magisk] Idiyeet:
Hi. Quick question about the latest version that came out for Magisk.. v 20.1 to be specific. If I update my Magisk to it, it won't do the new hiding method by itself will it? Or is that a manual type thing and I'm safe to update?
[Magisk] Karitoriki:
Why the hell is this a thing?
[Magisk] Didgeridoohan:
Because one of the main functions of Magisk is to hide itself... Most find that more important than theming.
[Magisk] Didgeridoohan:
I haven't had the opportunity to follow the thread to close recently. Have you by any chance posted a logcat from when the hiding fails? If not, do that please, while using the current Canary debug build (always use that when reporting bugs)

A lot more details about your device and issue would be necessary for anyone to be able to help properly.

If you're talking about the stub apk, that will be automatically used when hiding the Manager on Android 9+ system that have proper broadcasts working. The next update probably won't bother with broadcasts though since [MENTION=4470081]topjohnwu[/MENTION] is currently working on a new communication method for the Manager and the daemon.

Sounds like you're worried about something... What could that be?
[Magisk] Ricardo Flowers:
simply magisk is not giving root permissions
[Magisk] xunholyx:
You can't turn them on in Magisk Manager > menu > Superuser?

I think that the toast notifications might not be working right now, but you should be able to allow root access that way.

EDIT: I've read your log now and I think I remember something similar happening a few versions ago for some users:

11-09 10:16:55.777 495 6158 W Magisk : su: request rejected (10215)

11-09 10:16:55.777 495 6158 E Magisk : write failed with 32: Broken pipe

Try using the Magisk uninstall.zip followed by a reboot, then setting it up again by reflashing the current Magisk.zip
[Magisk] digger16309:
OP5 running Oxygen Pie 9.0.9 and Magisk 19.3.

I'm also running a few EdXposed modules via Riru etc...

My Safetynet is broken and I've seen various comments around XDA about a) not going to Magisk 20 on Pie, b) using a custom Magisk to fix the safetynet issue. But I don't know if that is for Pie or Q.

Everything is working fine except safetynet.

What is the easiest path to victory to get safetynet back working, but keeping EdXposed running glitch-free as well?
[Magisk] spawnlives:
The issue is with the edxposed module not magisk.

Maybe try this work around.

https://github.com/ElderDrivers/EdXposed/issues/386#
[Magisk] ktmom:
Which is what I told him a day or so ago \_(ツ)_/
[Magisk] joaovictorbest:
Problem when trying to update

My magisk is not updating alone just like every time, I try to download and install for it as always is the new version 7.4.0 (253) does not install the apk. Something like this appears when it's on the installation screen "An error occurred when installing the package".
[Magisk] Ricardo Flowers:
So, this magisk I installed is the last one ... already tried to uninstall and install again but does not work, still the same error.
[Magisk] ktmom:
Then switch to the canary channel, and if the problem persists, provide logs

https://www.didgeridoohan.com/magisk/MagiskHelp#
[Magisk] Aaagogo:
Hi all, i installed Piix3lify and i'm trying to remove/uninstall the google wallpaper app but i can't find it with Root Uninstaller;

APK Name: com.google.android.apps.wallpaper

can anyone point me to the location of the apk folder, i would like to manually removed it from recovery; i checked the usual places; system/app and system/priv_app but to no avail.

thanks in advance.
[Magisk] lividhen99:
The thing about modules, is that they don't edit the system, at boot magisk simbolicy links where the module is to the rest of the system, so it is not going to be there when the os is not booted. So, in short, the apk is located at /data/adb/modules/pix3lify/system
[Magisk] SirLoinOfBeef:
ASUS Zenfone 6 - Android 10 Stock ROM

Problem: Installing Magisk results in boot failure, freezing on the Zenfone 'bouncing balls' boot screen.

Device: ASUS Zenfone 6

ROM: Stock ASUS Android 10 ROM - WW-17.1810.1910.68

Magisk version: I have tried both 20.1 and canary 20.2-a6e62e07 (20102)

Magisk Manager version: 7.4.0

Magisk worked fine on ASUS' stock Android 9 based ROMS, but since the release of Android 10 based ROMs I have had problems installing. I extract the boot.img from the ROM, copy it to the internal memory, patch it using Magisk Manager (which claims to have succeeded without error), then flash the patched boot image using adb and fastboot. The phone then fails to boot.

ADB logcat result: https://anonfile.com/w5r9wdA5nd/log_txt
[Magisk] lividhen99:
It says you have modules installed. If possible, try deleting, (someone correct me if I'm wrong), /data/adb/modules, or I believe reflashing your stock system image will clear modules too. I'm not sure how, but there is also a way to install a magisk that by default starts up in core only mode, so that it doesn't load modules, but you might have to ask someone else about that.
[Magisk] Aaagogo:
thank you for not just posting the location but explaining where the location is.
[Magisk] vijer:
Huawei Mate 9

Carbon 6.1

Android 8.1.0

Magisk v17.2

Magisk Manager v6.1.0

The issue I am having is that if I update the Manager then it tells me it doesn't support v17.2. The old Magisk Manager doesn't have an option in Settings for Patched Boot image method. What do I need to do?

Thanks
[Magisk] guest4711:
You are a victim of a known problem with some MagiskManager versions probably: MM fails to update when it is hidden. The workaround is described here ever and ever: Unhide MM (MM - settings - restore MN). This will update MM. Update Magisk, too. Then hide MM again.

If this does not work, uninstall Manager and flash the new Magisk zip.
[Magisk] xunholyx:
I believe what you are looking for is in system/product/priv-app/WallpaperPickerGooglePrebuilt.apk

I could be wrong though
[Magisk] Idiyeet:
Okay, what do you mean "proper broadcasts"? So do I just not update Magisk then? I'm worried about bricking my phone and if that's the way Magisk is hiding itself then I'm just better off maybe staying stock soon.
[Magisk] Didgeridoohan:
Your phone won't brick because of the Manager and how it hides itself. Magiskhide hasn't really changed for a while and is working quite well. The weak spot is the Manager, and that's what the new hiding method is about.

For some details on broadcasts, take a look here:

https://github.com/topjohnwu/Magisk/commit/0f74e89b44e6af6a7939ebf24050ce92546c2b5c

And for some info on the possibly future way of doing things, take a look here (for those who are interested):

https://github.com/topjohnwu/Magisk/commit/25c557248cab19f9761bbeb5a8ba110318d79d85
[Magisk] Idiyeet:
So if I update the Magisk itself, ill be fine and my phone will run as it is currently correct? Don't mean to be critical.
[Magisk] Didgeridoohan:
Probably. There's always a chance of stuff going wrong, so make sure to have a backup.

All I've done so far is to address your worry about the new hiding method, which only has to do with the Manager and has virtually no chance of causing those kind of issues.
[Magisk] pep01:
Why does this happen with the latest version of Magisk Manager? The App is constantly looking for updates.

Enviado desde mi SM-G965F mediante Tapatalk
[Magisk] MCR31:
I there.

I have a Samsung s9 snapdragon running GSI Q.

Magisk 19.3 and manager 7.2.0.

My issue is that apps are getting freeze. You click the app and it takes forever to load or even no loaded at all.

I red about flash magisk twice and it works for a while.

Any idea?
[Magisk] digger16309:
Thank you! That was the issue!
[Magisk] Didgeridoohan:
Can't replicate with either the stable or the Canary Manager, and not on any of the official upate channels. Are you using a custom channel?

Don't have any ideas about that, but wanted to take the opportunity to ask if you got any insight on the resetprop issue from your ROM's developer?
[Magisk] MCR31:
Yes, PixelExperience are using a old resetprop, I switched to phh vanilla GSI and I passed safetynet with magisk 19.3 but now I'm facing this other issue.
[Magisk] guest4711:
You blocked internet access for MM probably. Either using a firewall like AfWall or restricted data usage.
[Magisk] Sephious13:
I'm running into issues with the Magisk Manager 7.4.0 (253) on my Galaxy S10+. Right now, the recovery mode option is unchecked and remains unchecked no matter what I try. I am unable to reboot in a rooted configuration. I'm concerned that another attempt to flash the boot image may not be wise, and would appreciate any help.
[Magisk] Komekokos:
Same here
[Magisk] Didgeridoohan:
The "Recovery mode" checkbox only has an effect when actually patching a recovery image. At any other times it does nothing.

Did you follow [MENTION=4470081]topjohnwu[/MENTION]'s installation instructions?