yashsingh1/xdaforums huggingface dataset:
[Magisk] Pretoriano80:
Hello, i'm struggling to fix an issue that i have with one of my Magisk module for Amazon FireTV 4K.

Basically the module works perfectly with Magisk 20.3 but it fails with any higher version (tested with 20.4 ,21.0 and the Debug version)

It seems that for some reason the post-fs-data.sh fails to do its magic, it's triggered by Magisk but only a part of the script works (line 22 and 23 of the script is printing in the log file, but that's all).

Also, if i run the script manually after boot is complete, everything is fine.

If anyone can help me with this, it will be much appreciated, thx!

post-fs-data.sh - > https://pastebin.com/b9XUYfNQ
[Magisk] Audioboxer:
I take it everyone else with a Pixel 3/Pixel is now facing safetynet failing on HARDWARE?
[Magisk] dcarvil:
Probably a good assumption - mine fails on Hardware. Works fine forcing Basic with the MHCP module.
[Magisk] BeriBGood:
Safetynet seems to be detecting magisk again as of today.

I did not change anything to my system. Yesterday was working, today failed test.

Anyone can confirm?
[Magisk] twcobra:
Sounds a bit risky to me. I have had issues with multiple Superusers together. Like I said I kept it simple and it actually worked. I would run the

UnSUzip

Remove Magisk if installed

Flash the PHH HideSU zip

boot then remove the SuperSu app

Install PHH Superuser app from Playstore.

Give all your apps permission.

Let me know if Pokemon now works to make sure I dont have some random bug going on that is letting me in. XD
[Magisk] ashyx:
Thanks I realized it's the disable file causing the issue.

I just deleted the Magisk image in data and reinstalled.

But good to know for future reference.
[Magisk] Captain_Throwback:
Since some pages have passed, quoting here again since I already see people asking the same questions I already covered below.
[Magisk] Keksdroid:
Followed these steps, root works, PoGo doesnt :( cant pass SafetyNet Test... not sure whats wrong. Maybe my ROM automatically installs some files since it has inbuilt root. But SuperSU+suhide was working fine before the safetynet update..
[Magisk] Dalamar666:
Any ideas about avoid problem with CTS validation?

I think that full uninstalling xposed is required. But I found some xposed files in /data/locale...

Someobe could provide a full uninstaller, script, or similar?
[Magisk] galarond:
ok, im getting several problems here, im using now Dr ketans ROM with NOTE 5, it was rooted so i wiped everything and flashed the 2 zip files for magisk, installed the apk and nothing more, i dont use xposed at all.

after the update of ocurse im unable to play so like everybody here says is so simple to fix it i tried...

went to twrp flashed the uninstall zip for magisk, wiped cache/dalvik, reboot, then manualy desistaled magisk, supersu was still there so i went to the app and tried the fully unroot option, failed somehow so i went twrp again and manually erased all named su (as far as i can see), uninstaled supersu manually and rebooted again.

long story short, not working, what im i supposed to do now, im not even trying to use root i just want to get the veryfication passed without root but somehow i cant?

what can i do next? i dont wanna flash a stock rom.

tnx
[Magisk] knipp21:
Since safetynet finds magisk now, could there be a way to hide magisk itself?

I love the future of magisk so I'm just wondering if that could be an easy way, since hidesu is working, just not with magisk beside it.
[Magisk] Captain_Throwback:
http://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/post69000445
[Magisk] knipp21:
Thanks, this thread is so active, I missed it!
[Magisk] linkultima:
Im also havig prooblems with customs roms on NOTE 5, I have tried Sick Rom, Darth Stalker rom and unrooted both of them fully (restoring boot image) and just by removing SU from system and no luck at all.

Installing su hide fails or if it gets to install safetynet always gives an error, I guess it detects a custom kernel . I looking for a stock kernel to flash but cant seem to a recent one... Im thinking on going stock rom and rooting from zero on stock rom.
[Magisk] knipp21:
Safety net was updated. Will continue to fail will v8 is released.
[Magisk] linkultima:
Hi, I know safety new was upudated but flashing phh's SU with hide included is working for most people but now for me or some custom rom users :(

So I think it also detects custom kernel or something like that because even if I just unroot the phone it fails safety net :( in all my tests with 3 custom roms

Regards.
[Magisk] knipp21:
Do you have magisk? Its detecting magisk
[Magisk] galarond:
I tried with stock kernel and no luck on note 5, still fails, cant restore the boot.img cause noe im having some flashing issues (cant flash stock anymore for misterious reasons).
[Magisk] linkultima:
Nope, none of the custom roms come with magisk, even though I have tried also flashing magisk uninstaller to be sure ... working with custom roms si a little harder I think because we dont know what else is being detected now.

Before the update everything worked fone on my custom roms with su hide, now after the update after unrooting and cleaning everything I can think of, ist not workin :(

I have flashed back to stock and I will wait for a solution that works also for custom roms and custom kernels, at least for TMO NOTE 5 section :)

---------- Post added at 09:31 PM ---------- Previous post was at 09:14 PM ----------

Now I tried flashing phh superuser-r266-hide and it fails throwing ERROR:1 Error installing zip file :( I dont know what else to do now :(

EDIT: Found the solution, unzipped the original superuser-r266-hide.zip and zipped it again using my computer, now it flashed the file but Im tuck in samsung's logo with boot loop... well no root for me then :(
[Magisk] snke:
So Magisk is not needed anymore for Pokémon Go users?
[Magisk] Captain_Throwback:
Magisk can't be used to circumvent SafetyNet anymore, which means if you have Magisk installed, Pokemon GO won't work.
[Magisk] snke:
Ok thanks, not even suhide works now...
[Magisk] RandomPooka:
It's there any procedure to remove the phh superuser v17 that works with magisk v6? I was going to just uninstall magisk and hope that it takes out superuser with it, but I really didn't want remnants accidentally left behind. Figured that I'd ask, just in case I missed an Uninstaller zip while cruising through the thread.
[Magisk] dcroz:
yes it does. https://www.reddit.com/r/TheSilphRo...to_keep_root_again_and_still_play_pokemon_go/
[Magisk] Didgeridoohan:
If I'm gonna guess (and I'm gonna have to since I know nothing of your setup), it sounds like Google Play Services might have updated and your device now uses hardware backed key attestation, which will cause CTS to fail.

Some more details:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_Unlocked_bootloader_3

If that's not it, you'll have to be a bit more specific.
[Magisk] zgfg:
To be able to get help, pleasr be specific:

- stock or custom ROM

- Basic Integrity or CTS failing

- Does CTS Profile fail showing Hardware attest

- If so, did you install MHCP and enable Force CTS Basic attest

If not familiar with some terms, please find, there were tons of posts in this thread. Also in XDA MHCP thread (OP post #1), Magisk Github: WiKi and MHCP module documentation
[Magisk] BeriBGood:
I am terribly sorry, you are perfectly right and I should have known better and give more information.

Well I fixed it with a good old "disable magiskhide" and "enable magiskhide" and a reboot...

Strange but it worked so I am not complaining.

Thanks for your information, I did not know about the new measures and this was very informative for the future.
[Magisk] J.Michael:
Can you get a log file of the script's execution? "set -x" at the top of the script and see exactly where it is failing? I don't know if you can redirect STDOUT and STDERR within a script, but maybe you could run this script from within a stub, capturing all output.
[Magisk] Pretoriano80:
Yeah, i will try to get a more detailed log, thanks for the hint. Magisk logs did not helped, so i was trying ti fix it blindly.
[Magisk] NinetoFive:
I'm having an attestation fail on hardware too. Didn't install the Pixel November security update yet, so i'm guessing it is indeed google play services being updated today forcing another check.

I also have on GPay SQLite Fix (disabling it didn't help either)

Welp, it was a good run
[Magisk] CountryBoy_71:
Good Afternoon All,

I truly hope that I am not re-hashing previously provided information...I have been searching for an answer to my issue, specifically on the Huawei BAH-W09 without much success.

I will try and provide all necessary information and steps I have taken to now.

1. unlocked bootloader

2. installed twrp 3.2.0 (https://xdaforums.com/mediapad-m3/development/twrp-t3914531)

3. wiped all

4. installed LOS17.1 & GAPPS (latest)

5. booted into LOS and finished setting up OS

6. back into recovery, updated to twrp 3.3.1 (from the same link as above) and flashed Magisk Zip v20.2

7. rebooted back into OS

8. installed magisk apk

The issue I am having is that when I open up magisk apk, it is showing me that magisk is not installed. I am sure that there is something I did/didn't do properly but I haven't been able to find out how to resolve this issue. Hopefully I have given you enough information to provide some feedback but please feel free to let me know if you need more.
[Magisk] casouzaj:
Make sure Magisk Manager is installed in the internal storage.
[Magisk] andisetyawan11:
yesterday i used last magisk and edxpossed canary cts pass,no problem,end than i flash modul magidk dts x ultra,it change my device model to zte . . . . , cts change failed, i uninstall that modul,still failed cts,i clean flash n reflash rom ,magisk n edxpossed canary,but still failed, :(
[Magisk] CountryBoy_71:
There is no option to install Magisk in a particular storage or did you mean that it should be installed from the internal storage and not an sd-card?
[Magisk] casouzaj:
If another storage is available, Android may install Magisk Manager there. Go to Settings > Apps & notifications, slide down to reach Magisk Manager (or whatever name you gave it whilst hiding it) > Storage, and if a button like' Change' is shown, tap on it and, if it's not on the internal shared storage, select it and tap on 'Move'. Wait for the action to finish and launch Magisk Manager again.
[Magisk] CSX321:
FWIW, my Pay still works. I just went and got a snack at the kiosk in our break room. Pixel 3, still on the final A10 update, Magisk 20.4, Manager 8.0.2. I only marked the relevant database read-only manually, instead of using the module. Didn't even go through and change any of the attest values. It's just always worked. I've been putting off the update to A11, mainly because I don't want to mess up a good thing!
[Magisk] hfam:
Pixel 2, A10 August, Magisk 20.0, no modules, core mode only, no hiding/renaming. Safety net is working fine for me according to the MM test. No idea if/when that'll go away at some point. Awaiting Magisk 21.0 stable before I update to A11, as you indicated, if it ain't broke....
[Magisk] CountryBoy_71:
Thank you very much [MENTION=346743]casouzaj[/MENTION], that did the trick! All showing installed and working. One last question before I close this off. Currently I am running the v7.5.1. apk Is it safe to update that to the latest version(s)?
[Magisk] pndwal:
Use MagiskHide Props Config module and select Force Basic Attestation, choose manual 'f' option, select a device as close as possible to yours (Newer is often better for best device specific functionality) to spoof. Nb. You only need to use a model prop that differs slightly from the actual model to cause the mismatch that triggers fallback to Basic). :good: PW
[Magisk] casouzaj:
It's up to you. I updated my Manager to the latest release, on my Sony Z5 Compact phone, loaded with LOS 17.1 and the stable Magisk v20.4. Everything is fine! If you decide to update Magisk Manager, check if it is kept in the internal storage afterwards.
[Magisk] iamrance.asa:
So my phone has been failing SafetyNet recently and I'm not exactly sure why. It just started when I deleted the EdXposed module via twrp from the data/adb/modules/Edxposed because it was causing a bootloop. When it rebooted, all of my modules were gone and Magisk was reset. Then I started having an issue where SafetyNet was tripped.

What I tried:

1. Uninstalling Magisk

2. Uninstalling Magisk via Uninstaller.Zip

3. Changing device fingerprint via MagiskHide Props Config

-- this worked for a bit but ultimately is just a patch of another problem and fails if change signatures (I changed to pixel 4 XL and forced attestation -- which passed SafteyNet but then when resetting fingerprints it fails and when using Pixel 2 XL signature and forced attestation it fails as well)

4. Reflashing complete rom (dirty)

Information about my device:

Device: Pixel 2 XL

Build: RP1A.201005.004

Magisk: v21

EdXposed: Not Installed

Any recommendations on how to pass without deleting data?
[Magisk] yhogievo:
Am not surprised that there's banking app that still trips, and saying that i have rooted my device (UOB with V-Key App Protection).

No matter how i tried, it's still failing. MagiskHide is on, Safetynet is not failing (it has basic now, compared to the original hardware-backed attestation), and the Magisk Manager is hidden with random package name.

I am using MIUI 12, Android 10, Magisk 21 and Manager 8.0.2 without any xposed module installed. Anyone have suggestion for this one (and the only one) app that failing on rooted device?
[Magisk] guest4711:
Have you tried all suggestions in [MENTION=4667597]Didgeridoohan[/MENTION]'s great FAQ? https://didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
[Magisk] Philnicolls89:
I'm not sure about recent versions, but edxposed has been causing safety net failures for quite some time. Have you tried clearing data from Google play store and Google play services? This is needed after uninstalling edxposed.

Also when using magisk hide props config, you shouldn't need to change device fingerprint, usually just selecting force basic attestation and selecting a device similar to yours is enough to pass safety net.

Although I am not to familiar with pixel so maybe that device needs you to change fingerprint aswell.
[Magisk] CSX321:
Nevermind. Looks like this morning it no longer works. :(
[Magisk] AndDiSa:
Just updated my Pixel 3a to the latest Android 11 version (05/11/2020). Having installed MHCP module forcing SafetyNet to basic attestation method everything is still fine, i.e. SafetyNet CTS and basic security are passing and Google Pay still works (having manually changed the database to read only).

No need to change fingerprints or anything else.
[Magisk] iamrance.asa:
I tried clearing Google Play Services, Google Play Store, as well as Google and GMS then rebooting but it ended up still failing still. Well, I should say that cts profile keeps failing with both the fingerprint and forced attestation as Pixel 2 XL (my actual phone) while they both fail without those turned on. This is all with MagiskHide active.

Strangely, I switched back to Pixel 4 XL as my signature and used forced attestation and now both are passing. So maybe there's something failing on Pixel 2 XL's fingerprint in Config Props?

Anyway, I appreciate your help. I'm just going to leave it as is since there's only one more month of support left by Google, anyway. I'm planning on switching to another rom (probably lineage) soon so I will get a fresh start when I do. :)
[Magisk] Philnicolls89:
Are you passing basic integrity check
[Magisk] zgfg:
You don't need fingerprints for the stock, certified firmwares - you may only need to force CTS to Basic attest to hide that Bootloader is unlocked and that is enough for SafetyNet
[Magisk] AndDiSa:
Exactly what I wrote ...
[Magisk] CSX321:
I didn't check this morning when it failed, so I don't know. Just a bit ago I installed the MHPC module and forced basic attestation. Currently passing everything, but haven't tried a Pay transaction yet.

Side note/question... I picked the 3a when using the MHPC force option. Everything seems okay, but was that the correct choice for a Pixel 3? The way I understand the instructions and what I've read, I needed to pick something without hardware attestation, which the nearest match would be the 3a.
[Magisk] Philnicolls89:
You don't need to choose a device from the list that doesn't use hardware, you just need to pick a device that isn't yours but similar to yours, this is enough to confuse the check into forcing basic.
[Magisk] yhogievo:
Almost all of them except the isolation one, maybe it's worth get a look. Thanks for the advice.
[Magisk] zgfg:
My point was that it is well known, general case, not something specific to Pixel and A11
[Magisk] pndwal:
As stated, for stock certified ROM fingerprint change won't be needed. (Needed for some custom ROMs, and uncertified stock (Chinese, etc) ROMs.)

For Force Basic Attestation, select a DIFFERENT device as close as possible to yours (Newer is often better for best device specific functionality) to spoof.

You need to use a model prop value that DIFFERS slightly from the actual model (unlike Fingerprint) to cause the mismatch that triggers fallback to Basic. (You can't spoof your own device!)

Nb. A real model is not needed either, just a different value. 'Cheeseburger' will work to Force Basic Attestation as it doesn't match actual model prop value.

No, this is expected behaviour. Nothing wrong with fingerprint.

Pass is because Force Basic model now differs from actual model as it should. Nb. Default setting uses Nexus 5 for other Google models. PW
[Magisk] iamrance.asa:
I see. Thanks for explaining why it failed. I didn't realize it needed to be a different device. I'm not so familiar with how SafteyNet works. I guess I need to read up on it so I can better troubleshoot it for myself.
[Magisk] neocortex08:
I'm using a Pokémon Go on a Samsung Tab 4... It's not built to handle the game these days which means things crash and a reboot is usually the only fix. I say all this because I've been rebooting my rooted tablet 10 times a day or more for a year now without issue. 2 days ago things changed completely!

Now on every reboot SafetyNet fails. If I uncheck then recheck MagiskHide in the options, then uncheck and check Google Play Services, SafetyNet will again pass... but fails again on reboot.

I have since factory reset, put in a fresh copy of Lineage OS (and gapps), and did nothing more than add the latest versions of Magisk and it's Manager. The issue remains/returns on every reboot. SafetyNet passes, fails on reboot, then passes again if I un/re check the the MagiskHide options.

I tried uninstalling Magisk 21 and installing 20.4 instead, but it didn't help (I installed the older manager from the same 20.4 Magisk release, but it updated as soon as I used the Hide feature to randomize the name and id's).

I'm at my wits end if anyone has any ideas.

Edit: I have not added any modules (edexposed, etc) or done anything else. Not that it should matter since this relatively clean install is acting the same as what worked for nearly a year.
[Magisk] pndwal:
You may need something like magisk_hide_toggle.sh script; This:

https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/post82109139

Or this:

https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/post82117759 (120 delay seems to work better for some)

[MENTION=8010004]guest4711[/MENTION], [MENTION=5237901]Wolfcity[/MENTION] may be able to help you further with script.

It's an old issue seemingly, reported here:

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

...and seems it was resolved, so not sure why it's still occuring, but someone opened a new issue a week ago:

https://github.com/topjohnwu/Magisk/issues/3417 PW
[Magisk] neocortex08:
Thank you so much for this. I'll give it a shot in the morning (though my scripting ability is limited so who knows). Seems to strange I'd be infected with this issue at the same time many others had the same pogo error (but their issue was resolved with a reinstalling of the game) but I'm getting a year old error.
[Magisk] Huyqwerty:
Superuser Grant Issue

a couple of days ago, I opened magisk but it automatically closed so I reinstall it and now I can't grant access to any app, I am really sad right now. I have already set it automatically grant but it still the same

I REALLY NEED A SOLUTION FOR THIS

HELP GUYS :((
[Magisk] hackermssharma:
As u can see saftynet is passing in third party app. But magisk manager not even able to download the api. Using lattest manager stable one tried canary manager too but no luck. If i downgrade to 8.0.0 it works but on repacking magisk with rendom name it again fails to work. Any idea?
[Magisk] neocortex08:
60 and especially 120 seconds was too long for me (had to sit for 1-2 minutes tapping my fingers over and above the 30-60 seconds of the reboot), and I lowered it to 45 which feels much better.

That said OMFG TY! The thing works now.
[Magisk] aagha:
CiT Bank App not working

Any luck with this? I'm having the same issue.

I'm running Magisk 21.0 (21000) and Manager version 8.0.2 (307).
[Magisk] FunThomas76:
has someone running latest G970FXXU9DTJA_G970FOXM9DTJB_G970FXXU9DTJA for S10e running with magisk ?

i flashed it like before (had the august firmware running fine with magisk) but now the phone runs in normal mode but booting with magisk (volume up + bixby + power) always ends in a reboot here after a long lime samsung logo shown

sometime i get the recovery screen that the phone couldn't start normally ...

reboot recovery cause is [system_server:13691]

unable to disable quotas on /dev/block/platform/13d60000.ufs/by-name/userdata because /system/bin/tune2fs is missing

#reason is [RescueParty]#

Supported Api: 3

it is not possible to flash the old august firmware here which i was running before, so at the moment only lastest stock without magisk is possible here

have tried magisk 20.4 and beta channel v21 no difference both not working on s10e

is there a way to create a bootlog to analyse the bad startup ?
[Magisk] zgfg:
Does maybe Magisk Manager complain about not having a connection - close its SafetyNet test and check does it show what are the latest available Magisk and Manager versions (you can also check thriugh the Module tab)

PS: Don't know for 8.0.x, but latest Canary Manager 311 does not even offer SafetyNet test when no connection is available, hence maybe wrong tip, sorry
[Magisk] hackermssharma:
Connection available it showing versions and also i can nevigate to modules but can't download them. My internet working well the problem is in manager app
[Magisk] zgfg:
Tip was also about Manager, since there are users for whom Manager is showing as no connection available, while the phone is connected

You may try deleting data for Manager or uninstalling Manager - it will not affect Magisk data like modules, apps granted root and apps on the Magisk hide list. Just check if Magisk hide option will survive and enable again if needed
[Magisk] ddougg:
Investigate the G7 play specific root guide. You have an a/b partition so you need to flash extra stuff they have in that thread to make your device root. I had one rooted perfect until it fell off the balcony, lol. Follow directions to a T & benefit.
[Magisk] hackermssharma:
Tried all these already but no work for me old versions working well but when i rename old manager with rendom package name then it automaticaly downloads newest version again.
[Magisk] zgfg:
Ofc, Update channel points to the newer. Search in this thread how to e.g. find a link to v7.5.1 from Github to use for Custom chammel

Then hiding Mabager 7.5 1 will stay on 7.5.1
[Magisk] asrar73:
Sbicards app also not working.

Cts profile true

All setting are same as before nothing changed.

Still not working.
[Magisk] asrar73:
Hide app in magisk

Magisk app is also renamed.

Help