yashsingh1/xdaforums huggingface dataset:
[Magisk] Justinmbenedict1:
just wanted to point out a bug in safety net check magisk manager v20.3. Im using unofficial lineage 16 for pixel 2. I had installed the module called "safety patch" which ended up allowing me to pass magisk manager safety net check on both counts, but I noticed that Netflix was still unavailable to me in the playstore. So I knew that something was still being flagged by google. I disabled the safety patch module and installed "magisk hide props config" module which allowed me to change my device fingerprint to that of the correct google pixel 2 release keys. After which Netflix showed up in my play store as expected. So it seems google is checking for something that magisk manager is missing... Thanks for all of the work you've put into this.!
[Magisk] Didgeridoohan:
That's no bug... You likely just had the Play store reported at uncertified. That is known to cause that with Netflix.

Details: https://didgeridoohan.com/magisk/Ma...and_other_apps_wont_install_or_doesnt_show_up
[Magisk] Pisolo:
Magisk Hide.

Hello guys.

Where do I find Magisk Hide in the latest update that all the graphics have changed.

Thank you.

Google translator
[Magisk] Justinmbenedict1:
Maybe doesn't fit the definition of a bug and I guess it might not be safety net related at all.. I don't know enough about it. but I reviewed your documentation on the play store certification and it doesn't seem to be consistent with what I am experiencing. Here's what I've tried.

I already had Netflix showing in play store (don't really care about netflix but its a good test) so I checked the settings and saw "device is certified" at the bottom.

I disabled your module and switched back on the other safety patch module. The certification section disappeared altogether. Didn't say device not certified, it was just gone.

(safety net check passed)

Then just for the hell of it I tried installing a few random fingerprints with your module. I tried Galaxy S9 plus, Pixel 4 , and Pixel 2 XL. checked for certification each time and it was still missing for all. (safety net check passed)

I reinstalled Pixel 2 fingerprint. Checked again immediately after reboot and once again saw "device is certified" without having to clear any data from the play store or anything else.

So it seems to me that google knows that I have a pixel 2 by some means other than the fingerprint and is checking whether my device matches my fingerprint. is that possible? And is it related to safety net? I guess what i was getting at in my original post is that It would be nice if the test in magisk manager would fail under the same circumstances that google is using to flag me as "uncertified".
[Magisk] chooks06:
My experience with "device is certified" is that even if it disappears immediately with changing fingerprints (or clearing device cache in recovery), it will take a while for play services (I think) to do a scan. Probably a few minutes later it will appear.

That's what I've observed so far (purely from users viewpoint).

Cheers!
[Magisk] Didgeridoohan:
[MENTION=10107728]Justinmbenedict1[/MENTION] just like [MENTION=6323980]chooks06[/MENTION] mentions above, the Play Store doesn't continually scan for issues. The only thing that matters is if it shows "uncertified", anything else is "all clear".

And Magisk already do "check" for the circumstances that Google use to flag you: the CTS profile. If you don't pass that, you'll end up as uncertified in the Play Store.
[Magisk] osm0sis:
Alright, now that you've explained your "readback" boot.img works, and it doesn't have any weird pre-header or trailing signature-looking data like your boot-sign.img, I've dug into the readback_boot and magisk_patched images a bit more to see if there are any differences of note.

Your device appears to be A-only SAR with no ramdisk, bootimg_hdr_v1 and signed with AVBv2. After Magisk patching, a basic cpio ramdisk is added, and the kernel and kernel_dtb appear to remain untouched. Since the kernel is already raw format, but there aren't any text strings present, my guess is there is no way to patch skip_initramfs to want_initramfs to make it boot from the added ramdisk like we would on other A-only no-ramdisk devices. Your best shot is using the recovery partition, by dumping the recovery.img and using Magisk Manager to patch it with "recovery mode", then hopefully it'll boot rooted when you choose to boot to recovery since recovery's kernel should use the recovery ramdisk which Magisk will hijack.

More instructions for recovery mode and how to get to actual recovery can be found on the Magisk wiki.

It's possible if there is kernel source for your device that someone could compile ramdisk support back in to allow Magisk in the boot partition, but that's way outside of the scope of this thread and you'll have to look into it on your device forums.
[Magisk] Az Biker:
* * * Thread Cleaned * * *

A few rude / sarcastic comments were deleted.

Let's all please remember that Forum Rules require comments to be respectful and helpful.

There is no justification for violating the rules and posting rude or sarcastic comments about other members.

If you feel another member has violated Forum Rules, simply REPORT their post, and allow Moderation staff to address the problem.

Responding, arguing, attacking, insulting, being rude/sarcastic doesn't just clutter the thread further, it also places you in violation of the rules as well. REPORT the comment and be part of the solution, not part of the problem.

Further comments that violate the rules will not only be deleted, the associated accounts will be reviewed for restriction or removal; ain't nobody got time for that.

Let's get back to respectful, helpful discussion and leave the crazy drama llama stuff for the social media sites :good:

Thanks for everyone's cooperation.
[Magisk] Jesenican:
I have Mi Max 3, xiaomi.eu 9.12.5, latest magisk stable and latest manager canary and magisk hide is not working. I cant use my bank app. Any advice what to do without unrooting my phone. Thanks
[Magisk] warchild98:
Magisk 20.3 is a mess. Why?

Some apps like lspeed or even fstrim (trimmer) won't work anymore.

Supersu denies apps permissions automatically...even with automatic response set to "grant".

Only titanium backup, viperfx, link2sd and adaway works for me...

I'm using Nokia 6.1 with Treble Aosp Extended 9.0

I will downgrade to 20.2 and wait for a fix.
[Magisk] ktmom:
I commented on a similar post a few pages back
[Magisk] Wolfcity:
Can't confirm that. Maybe it's one of your root apps (TiBu?) that's causing trouble. But as you can see I don't use lspeed or fstrim.
[Magisk] slvrhwk:
Hey guys, I finally got tired of ads and after months of deliberation, I decided to install Magisk and root my Pixel 3 and install Adaway. Unfortunately, swarm stopped working properly after rooting. The app just opens and that's it. When I click on check-in, it doesn't find my location. It stopped showing me other people's check-ins. I uninstalled and reinstalled the app, but it wouldn't even go past the login screen. It is one of the apps that I absolutely need. I added it to the Magisk Hide list and that didn't help either. I uninstalled Magisk and it started working again. Can someone please help me figure out why it's not working? Thanks!
[Magisk] warrencoakley:
I had issues constantly with L Speed not working and causing bootloops too. It requires BusyBox too.
[Magisk] jcmm11:
What happens if you disable Adaway? If that fixes it you'll need to whitelist the appropriate sites. DNS logging to find the correct ones. See the Adaway thread for more (search the thread first. Also see the Adaway wiki. Specifically https://github.com/AdAway/AdAway/wiki/LogDNS
[Magisk] slvrhwk:
It doesn't. I tried that first. I was hoping it was due to Adaway. I uninstalled Adaway and it still didn't work. Then I uninstalled Magisk Manager and it started working :(
[Magisk] Justinmbenedict1:
That's where I have to disagree... regardless of whether the check happens right away or not, if I install any fingerprints other than google pixel 2, the next time a check happens I am flagged as uncertified. I'm also going to disagree on your statement of unless it shows "uncertified" anything else is all clear. because my version of playstore (18.5.59-all [0] [PR] 291056213] )will show nothing at the bottom and at the same time Netflix is not available to download and vice versa, it will say device certified and show Netflix. Whether it says so or not if I'm not getting to see Netflix then I am not certified.

Here's what I did to test your theory. Note that I started with device certified and Netflix showing. Once again I reinstalled a different fingerprint. This time google pixel 3 android 9. Rebooted and checked playstore. Device certified had disappeared. I searched for Netflix and it was still showing. So this confirmed what you said about playstore not constantly checking. I then cleared storage for playstore and reloaded it. Still nothing at the bottom of settings. (Did not say uncertified just nothing there) searched Netflix and it was no longer there... CTS profile: true in magisk manager.

So once again I will assert that google is testing for something that magisk manager is missing! Magisk manager passes CTS profile true no matter what fingerprint I install. Google play store (even though it might not check constantly), when it does a check will only certify me with the google pixel 2 fingerprint installed.

Try it for yourself if you think I'm full of it.
[Magisk] AKHIL.cochin:
Hi

i was in 9.0.5 with magisk 20.2 and recently updated my 3T to 9.0.6 and then flashed latest 20.3 . after restart the device showed powering off and turned off .

tried with older version like 20.2 20.1 etc still same s happening .

reflashed rom zip file and all working fine without magisk .

what may be the problem happening with magisk

did only dirty flash from 9.0.5 to 9.0.6
[Magisk] Didgeridoohan:
I don't think you're full of it... You're sharing your findings, that's all. And that's great, because that way we might learn new things. I have tested this stuff though, and I want to add something to your findings that I have seen.

After clearing data for the Play Store, wait. I've seen reports of people having to wait a full day before the certified status and Netflix showed up. Rebooting can sometimes bring them up as well.

I wouldn't be surprised if Google does have some additional ways of detecting stuff that we don't know about yet, but equally I wouldn't be surprised if they don't. If you do find something additional, please share so whatever you find possibly could be added to MagiskHide.
[Magisk] jcmm11:
Have you hidden Magisk Manager by repackaging it? (See settings).
[Magisk] hw-schrauber:
Thanks for your explanations. I have now patched a read back recovery with the app. Unfortunately, this does not start either. But here I also looked at the files. With this file, too, it appears as if MAGISK.app overwrites essential parts of the image. I don't understand why MAGISK behaves like this. At boot.img the file is shortened to 46 byte-filling zeros after the patch. During the recovery, the file is shortened, but 726.407 kB of filling zeros remain. If MAGISK is patched, is the original boot no longer needed? Or why is part of the original data of boot.img / recovery.img overwritten when patching. I come from assembler programming. Maybe that's why I don't understand it. In my imagination, if it is okay that the data will be overwritten, it should actually be the same data packet for the boot as for the recovery. But that's not the case either. Maybe you want to take a look at the data area of ​​boot.img compared to the patched magisk_patched.img in the range from $ 6A05D0 to $ 6A11D0. For me, this looks more like a patch error when calculating the areas available for patching.
[Magisk] andrea0807:
I have a problem with magisk that has been plaguing me for several months now, I can't find the solution. Basically I can't install magisk from recovery every time I update my Rom.

I have one Xiaomi mi 8 with the latest rom xiaomi.eu weekly and magisk Canary v20.4-0dc9f5c3 (20303) installed.

Every week the ROM update comes out, restart in recovery and install the update, copy the logs to the SD memory (recovery.log).

I reboot the system, then reboot into recovery and install magisk v20.4-0dc9f5c3 (20303), copy the logs to the SD card (recovery.2log).

I reboot the system but on reboot magisk is not installed.

To install magisk I must always uninstall magisk with the uninstaller from recovery and then install version 19.5-debd1d7d (19403), only this version installs, then I must update magisk from the magisk Manager app.

It's very frustrating because every time I lose the installed modules and I have to reinstall them.

All this happens only with the ROM xiaomi.eu with the other Roma it doesn't happen.

How can I solve it?View attachment Log.zip

Inviato dal mio MI 8 utilizzando Tapatalk
[Magisk] Lughnasadh:
I can confirm that after clearing cache and data of Play Store and rebooting it can take several hours to almost a full day for "device is certified" to show up. I have to do this once a month when I update to the latest Google security patches. But it always shows up after some time.
[Magisk] DanielMalmgren:
After todays new release of Wizards Unite it seems they've started doing some new trickery to detect root. None of the old tricks seem to work. I'm just hoping that some cunning dev also likes Wizards Unite :)

For the time being I'm thinking about uninstalling Magisk. Now that my phone is debloated and fully backed up I should be able to live without root for a while...
[Magisk] rodken:
Amen.
[Magisk] ktmom:
While it sounds like hiding the manager is the solution for you, I do want to double check that you reverted the hosts file and rebooted before removing Adaway.

Take a look at Didgeridoohan's Hiding root from apps.
[Magisk] slvrhwk:
I can try that today. Can you please tell me how do I revert the hosts file? Is that from Adaway or Magisk?
[Magisk] ktmom:
In Adaway, on the main screen, there is an option to "Disable Ad-Blocking". Just removing the app does not revert the modified hosts file.

What you may have ended up doing is effectively disabling systemless hosts which would have allowed the non-modified hosts file to "re-appear". That might make you think it's related to Magisk when it's due to the ad blocking hosts file containing a redirect preventing your app from working.
[Magisk] dcarvil:
If ad blocking is your only need for Magisk, you can block ads without rooting by changing DNS in Settings, Network & internet, Advanced, Private DNS Mode. Enter hostname dns.adguard.com.
[Magisk] osm0sis:
Nothing is overwritten per se, I checked the unpacked images myself: the patching unpacks the boot.img and adds a new ramdisk.cpio where previously there was none, all else was the same.

You haven't uploaded your recovery.img and magisk_patched.img for it so I can't speak on those, but I imagine it just does what it always does when there's a ramdisk: replace /init with magiskinit and add /.backup to it with the original init and Magisk config.
[Magisk] Jesenican:
Is anyone else having trouble with hiding magisk manager? I always get hiding magisk manager failed. Tried to disabling play protect but results are the same.
[Magisk] hw-schrauber:
Sorry, I have now attached the recoverys. But when it comes to overwriting, I see it a little differently. This area "avbtool 1.1.0 ............" is completely missing in the boot-patched.img. A completely different area is missing in the recovery-patched.img. Please use a HEX editor to compare the two files, then you will see what I mean. It looks like relevant areas of the boot block are overwritten by the MAGISK patch without replacement. It may be that it is correct, but it looks very funny to my senses.
[Magisk] osm0sis:
AVBv2 signature is unenforced on an unlocked bootloader, which is why I haven't mentioned it. Sorry, forgot that wasn't common knowledge. Of course I'm using a hex editor. How else would I have written my previous posts to you? ;)

Use a hex editor and also magiskboot binary or my Android Image Kitchen to unpack your readback_boot.img and magisk_patched.img and you'll see what I mean. These things are in a format, nothing is being incorrectly overwritten, replaced, patched or truncated from anything I've seen so far.

Like I've said a few times now, the kernel and kernel_dtb are both identical on those images, only differences being the added ramdisk.cpio and the corresponding header changes. My only theory is that without being able to patch skip_initramfs -> want_initramfs in your raw kernel there's no way for it to boot from Magisk's added ramdisk.

I'll take a look at your recovery images tomorrow. Where are they attached? :good:
[Magisk] slvrhwk:
Yes, it was this! I went through the entire cycle again and as expected, the app stopped working. Then I disabled ad blocking in Adaway and it started working again.

Do you know what's the solution here? How can I enable ad blocking and still make the app work? I guess I'll have to whitelist the domain. How do I figure it out, though?
[Magisk] kiwigi:
[MENTION=7423542]dcarvil[/MENTION]

I just wanted to check on my S7 where that setting is. Haven't been able to find it yet:o

Edit:

Found it, thanks!
[Magisk] zgfg:
Disable AdAway, use app, analyze Logcat, find which FQDNs it uses (asks to DNS resolve), whitelist them, enable AdAway and try again.

You can also analyze LogCat from with AdAway to find which domain(s) iz blocked for your app
[Magisk] Didgeridoohan:
[MENTION=4487388]jcmm11[/MENTION] actually gave you the answer to that in their original reply to you:

https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/post81608567
[Magisk] TomiSpk:
restore images does nothing

I have searched this thread but haven't seen somebody else with my issue. i am on a pixel 2 XL version 8.1.0. magisk is 20.3 while the magisk manager is on 7.5.1 and i have root. I wanted to install android 10 and to do that i started with getting into Magisk -> uninstall -> restore images. it then shows a loading dialog which says "restoring" and in about 1-5 seconds it's gone and nothing really happens and i still have root and i can reboot my phone normally and not lose the root.

(for most other people it at least says failed to find stock boot image or something but for me it doesn't say anything)

It'd be great if someone knows how this can be solved.

Thanks!
[Magisk] Badger50:
This should help :good:

https://xdaforums.com/pixel-2-xl/how-to/quick-2xl-upgrade-reference-8x-oreo-to-t3826330
[Magisk] TomiSpk:
thanks for the link. looks way too complicated so i'm gonna wait until i feel comfortable doing it. i was hoping i can just follow this simple tutorial:

https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md

any idea why i can't use this tutorial?

thanks again!
[Magisk] Badger50:
It should work, however, I have seen some issues with updating while on A10. You could always fastboot the stock boot.img to return to stock, non-rooted kernel, then go from there. Personally, I'd read that guide several times over to update confidentiality going forward. :good:
[Magisk] TomiSpk:
oh so you are saying that i can manually restore image by fastbooting the stock boot.img and continue following the simple tutorial? i'll try to find a good tutorial about this but it would also be great if you can point me to one.
[Magisk] dcarvil:
It's the same process as rooting your phone, except instead of "fastboot flash boot magisk_patched.img", do "fastboot flash boot boot.img".

Make sure you have the latest platform tools, and are using a boot.img that matches the version installed on your phone.

https://xdaforums.com/pixel-3/how-to/guide-patching-boot-img-magisk-canary-t3964359
[Magisk] marquelito:
Hey, hope someone can help

So, i installed last magisk and patched boot.img, flash it via odin. And in terms of root its all ok. But i cant make any change in system files or even in sbin/magisk/mirror. After change, lets say, a build prop line. After reboot it came to original. Cant even delete system apps or edit anything

Any help? Im on s9+ Android 10

Thank you!!
[Magisk] dcarvil:
See the "Can't edit system files" section at https://www.didgeridoohan.com/magisk/MagiskRootIssues. You will not be able to update OTA after modifying the system partition.

There is a module for modifying build properties. https://xdaforums.com/apps/magisk/module-magiskhide-props-config-t3789228
[Magisk] marquelito:
Yeah i was thinking it was because SAR, but i want to delete apps and edit csc config. So its impossible
[Magisk] Didgeridoohan:
As long as the partitions aren't permanent read-only you can simply mount root (/) rw and then do your modifications as you'd like.
[Magisk] marquelito:
I mounted / rw in explorer but even in this way after reboot files revert to original
[Magisk] HippoMan:
***deleted***

Redundant post. Deleted. Sorry for the bandwidth.

.​
[Magisk] Tejas_Ashok:
I installed the latest app release and it shows that my security is outdated. But my safety net check is successful.

Is it because I unlocked my bootloader?
[Magisk] wangdaning:
It is because your roms security patch is not January. Probably only google devices would show it as up to date, unless you run a custom rom that updates the patch monthly.
[Magisk] vikd007:
Same issue but I m using custom ROM with Jan patch
[Magisk] wangdaning:
If you go to your device's settings->security what does it say?
[Magisk] Tejas_Ashok:
Oh ok thanks for the info
[Magisk] slvrhwk:
Yep. I missed it. That solved my problem. I now have my app working along with Adaway. Thanks again to this beautiful community! :)
[Magisk] bcuraman:
#Solved

Followed the guide in this link: https://xdaforums.com/apps/magisk/magisk-google-pay-gms-17-1-22-pie-t3929950 and it works once more. :D

Hi guys. Need some info in here: my device is rooted with the latest Stable( I think) 20.3, and the Manager is 7.5.1

My security patch level is form 1st January 2020, and so is the security update. A couple days ago, I was able to get Google Pay working fine, without any problems.

However, I formatted and reinstalled the system from scratch. But now, with the same settings, Google Pay recognises the root and won't work. I am running xiaomi.eu rom 20.1.21

What can I do in here to get this issue sorted? I have already added Google Pay, Google Play Services, Google Services Framework, and two other banking apps, which don't detect root.. What can be the culprit in here? Thanks in advance
[Magisk] cohenelad:
Hi, just got into an issue with Magisk 20.3

Until yesterday my bank app (AIB bank) was working correctly on my phone (K20 pro . MiUI 11.2 Xiaomi.eu 20.1.21)

I have tried yesterday to install Xposed on my phone and couldn't complete the process since my phone got stuck on bootloop.

Through some help and guides I found online I was able to delete Xposed and the 2 modules that I tried to install.

But when I tried to open my bank account this morning it gave me an error that my device is rooted and therefore I cannot use the app.

Any idea how to make it work again?

*** UPDATE - Solution found ***

I was able to resolve it and the solution was quite easy (my mistake not to realize that I didn't delete the Xposed APK and the app itself from my phone)

Previously I deleted the file through TWRP file manager but didn't uninstall the app itself :eek:

All I had to do is to delete the apk file and the app, clear data of the banking app and then open it again.

Now it's all working just fine
[Magisk] ktmom:
I think this is less about Magisk and more about Xposed.

My advice is to make sure to clear data and cache for the problem app. If that doesn't work, you may need to dirty flash the ROM again to remove any remnants of Xposed.

You might get better assistance in the Xposed forum.
[Magisk] cohenelad:
Hi [MENTION=6617276]ktmom[/MENTION]

Tnx for the advice.

I was able to resolve it and the solution was quite easy (my mistake not to realize that I didn't delete the Xposed APK file)

All I had to do is to delete the apk file, clear data of the banking app and then open it again.

I wasn't aware that Magisk cannot hide Xposed from root check by the app.