yashsingh1/xdaforums huggingface dataset:
[Magisk] pndwal:
As already mentioned, you likely don't need USNF as this is designed to cause fallback to basic attestation when the hardware for hardware attestation exists, but unless RR ROM itself spoofs a certified fingerprint you'll need to set one in MHPC (soon to become MDPC 😜 ).

However if you are still on bleeding edge 706a4922-alpha you need to remove Riru module; it breaks basicIntegrity as noted above. (In the previous build it works fine.)

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-85647153 PW
[Magisk] zoisa:
Hi, i cant find the old version Google Pay that it work without SAfetynet problem, i know i read in some thread but i cant found it, any help? Thx.
[Magisk] rodken:
Try this.
[Magisk] hkdoublecat:
For your research, ctsProfile fail for my situation, basicIntegrity is ok; evalType is Basic:

#1 706a4922-alpha Magisk & App;

#2 Fingerprint and PIN added now.

#3 Riru and USNF removed; no more Riru module
[Magisk] Didgeridoohan:
Do you mean screen lock or the ro.build.fingerprint prop? Because the former does nothing for SafetyNet while the latter is quite necessary to pass CTS.

https://www.didgeridoohan.com/magisk/MagiskHide#hn_Spoofing_device_fingerprint
[Magisk] zoisa:
Thx, i use 2.120.344959027 and it work, is old version with 0 problems safetynet.
[Magisk] camperbh:
I have Riru installed on 706a4922 but safetynet still passes with just MagiskDeny. I didn't even have to set a certified fingerprint (I have a Poco X3 with WaveOS 4.8 16 September patch if that's relevant).
[Magisk] Tuulis:
Hello. I have OnePlus 3T w/ Lineage OS for MicroG.

Is it possible to bypass SafetyNet attestation with this combination?
[Magisk] ipdev:
Are you sure about this? :unsure:

There will be a short time between breaking SafetyNet and Google scanning your device, that PlayStore might still show Device is certified.

Failed cts, will fail SafetyNet.

Failed SafetyNet, will fail Play Protection certification

(Device is not certified)

If you are keeping certified status while failing SafetyNet, then some hack has to be in-place.

Maybe Resurrection added something??

Cheers. :cowboy:
[Magisk] pndwal:
As mentioned, old device w/o hardware TEE components / likely unofficial RR spoofing certified fingerprint. 👍 PW
[Magisk] pndwal:
Re. MicroG / SafetyNet:

https://xdaforums.com/t/magisk-module-universal-safetynet-fix-1-1-0.4217823/post-85502585

https://xdaforums.com/t/magisk-module-universal-safetynet-fix-1-1-0.4217823/post-85510943 PW
[Magisk] ipdev:
True.

They would build using the latest (last) official fingerprint for the device.

Being an older device, normally you do not need to set the matching security date to the print.

What I was questioning was failing SafetyNet and keeping Play certification.

hkdoublecat notes..

My device is oneplus 3T (A3003) on RR rom V7.0.2.

basicIntegrity is ok;

evalType is Basic; just the ctsProfile failed.

Play Protect certification: device is certified.

​

Cheers. :cowboy:
[Magisk] pndwal:
Ah, apologies. Forgot the detail / too quick to respond. 😬 Good point. PW
[Magisk] Tuulis:
I guess I shouldn't install that module since I have MicroG already installed.

I think I'm going to try the regular LOS w/ "microG Installer Revived" module. However, I don't know how to proceed after that since LOS doesn't have the signature spoofing support.

So my question is which modules I should install to get the signature spoofing to work on regular LOS? Sorry, I'm noob.
[Magisk] zzz2002:
I am currently running Magisk f822ca5b (23001) on a Samsung S7 edge using Ivan Meler's lineage 18.1 ROM.

I further understand that for very good reasons this version of Magisk, and more importantly Magisk Hide, is no longer supported.

In addition I am also getting an interesting message from google that Magisk is a dangerous app that must be removed immediately (I ignore it). But I wonder how long before Google just removes it without asking.

So my question is, with What and How do I replace Magisk and Magisk Hide? My objective is to allow me to use various banking and financial apps.
[Magisk] hkdoublecat:
Yes, it is the case that my devices is certified while still failed in ctsProfile.

Not aware it is something abnormal.
[Magisk] 73sydney:
@pndwal

Calling Marvin, theres a new Magisk alpha literally just appeared on TG :)

3:15AM Sydney time folks (we're in the same city), lets see how long before he announces it and the changelog :)

Taking bets via PM :P
[Magisk] jons99:
yeah it's working fine
[Magisk] Fif_:
You'll need these Magisk modules:

microG installer

Riru

LSPosed

And you'll also need the FakeGapps Xposed module from WhewInc: https://github.com/whew-inc/FakeGApps/releases

The release marked "LSPosed scoped module support" (https://github.com/whew-inc/FakeGApps/releases/download/lsposed/app-release.apk) works well.
[Magisk] Chandru123:
Installed the new alpha over the last stable one, everything works as expected. I believe the zygisk was automatically enabled in this build and also did not need to reinstall the USNF 2.1.1. Can someone confirm is it still needed??
[Magisk] Deadmau-five:
Worked for me on my Pixel 5a.

Used this post: https://xdaforums.com/t/magisk-general-support-discussion.3432382/page-2375#post-85573473

And this video:

(though this didnt work. I added the above and then it did work. May need to hide additional banking apps to work)

Also changed my props to pixel 3a
[Magisk] ipdev:
Definitely not normal. :D

Since Google uses SafetyNet as part of the certification, it should fail certification.

Something appears to be blocking Google from seeing that you are failing SafetyNet.

Either purposely or by accident. ;)

Cheers. :cowboy:
[Magisk] zgfg:
I was on 63cfe7b4-alpha, DenyList was enforced and configured and SafetyNet was passing

(For my Xiaomi Mi 9T and Xiaomi.eu Stable, I didn't need any additional module or hack to pass SN)

Now I updated to b6298f86-alpha (first installed apk, then patched and flashed the boot.img) and SN was still passing

However, in the Settings, Zygisk was disabled and DenyList was grayed out.

Upon enabling zygisk, I was able to check DenyList - all was ok and configured as previously, primarily the GMS and SNET to pass SafetyNet).

However - SafetyNet was failing then - but until I rebooted

Finally, upon reboot, everything is ok: Zygisk, DenyList, SafetyNet, Device Certified, root apps and previous modules ok (including Viper4Android)

---

Btw, one thing is not ok - I cannot open any post from XDA app, from Show All alerts (it takes forever, staying empty)- I had to use browser to post this

I thought first it was a problem on the XDA ZenForo side but not - it's a problem with WebView caused by Zygisk that came with this Alpha version:
[Magisk] pndwal:
[Reserved]

Just took this space to say I really hope we get official TJW Magisk build before 50000 posts... It just might cheer me up.

However, lets see if post 48000 proves auspicious... I'm so depressed... and I already have a headache just thinking about it ... I need a coffee.

[The only source of hot drinks on this entire ship is a benighted piece of equipment produced by the Sirius Cybernetics Corporation called a NutriMatic Drinks Synthesizer. It claims to produce the widest possible range of drinks personally matched to the tastes and metabolism of whoever cares to use it. When put to the test, it invariably produces a plastic cup filled with a liquid almost, but not quite, entirely unlike coffee. 😕

"Share and Enjoy," drones the drinks machine.

"Share and Enjoy" is of course the company motto of the hugely successful Sirius Cybernetics Corporation Complaints division. Their marketing division also defines 'android' as "Your Plastic Pal Who's Fun To Be With."... I can only pull off that feat by employing a magiskal mask and several spoofing modifications... No wonder the Complaints division alone now covers the major land masses of three medium sized planets and is the only part of the Corporation to have shown a consistent profit in recent years.]

Marvin
[Magisk] pndwal:
Latest @vvb2060 Magisk Alpha (Chinese translated):​

Magisk (63cfe7b4-alpha)​

[General] Based on 63cfe7b4, the content that has been merged upstream is no longer listed

[App] Correctly process any data from magiskd

[App] Support SharedUserId

[App] Delete the backup file after restoring the boot image

[App] Built-in current version update log

[App] Use the local version when the stub cannot be downloaded, now it can be used completely offline

[Busybox] Fix the default shell path

[App] Switch to the modern time API of Java 8

[DenyList] Dealing with suspicious props

[App] Update the SafetyNet extension, update the version of snet.jar to 18

[App] Fix that the timer of the authorization pop-up window may not be initialized

[Sepolicy] Sepolicy with built-in LSPosed

https://github.com/vvb2060/Magisk/b...f1013cfb8f5/app/src/main/res/raw/changelog.md

And well done all you Magisphiles!

48000 posts!

🎊🎉⚡🍰🎈🤡.

Here's your reward! ... Do I get a prize?

Someone wake up Nigel!

Nigel? 🧀 - PW 🥝
[Magisk] Fidom:
I have magisk version 1eb83ad8-alpha-31 (23001)

I see the notice "requires additional setup. Do you want to proceed and reboot". After the reboot I see the same notice every time. What's wrong?

I don't see any modules except "systemless hosts". I updated the list by pressing the icon in the right top corner. Where is the modules? How to turn it on?
[Magisk] Soumy1234:
I think you forgot to install the Magisk Framework. Installing the app isn't enough. You have to press install next to the "Magisk" banner at the top right area.
[Magisk] zgfg:
You have one version of Magisk Alpha app and completely different (few versions older) Magisk - observe the differences in version strings of "Installed" on your first screenshot

And btw, you probably have wrong Update Channel (Canary, while you are running Alpha?!)

- Inspect Update Channel in the Magisk apk Settings, and make sure you switch to Alpha (bcs you have both Magisk and Magisk apk from Aplha), not Canary or Stable

- Then take Magisk Install from the main Magisk app window, you can use Direct Install or Patch and Flash

If you want instead Stable and Canary, you have to install the old Stable or Canary Magisk apk, then patch and flash your img
[Magisk] Fidom:
I've tried different update channels: "alfa", "canary", "stable" - everything is the same, I don't see any modules.

I needed the module "Magisk Hide Props Conf" to enable the Google Pay. I've just installed this directly from the source zip archive.
[Magisk] Fidom:
I've changed the update channel to "Alpha" and Installed the app (framework), rebooted, and still don't see modules except 2 (I installed "Magisk Hide Props Conf" directly from the zip)
[Magisk] zgfg:
First of all decide do you want Stable, Canary or Alpha (if you don't know the news and diffeences in Allpha and how to properly onfigure it, better stay on the old Stable).

Be aware that new Alpha is coming every second day, with differnces in how it must be configured - if you are not up on all that, please better stay away from Alpha.

And be prepared for bugs in Alpha - after all, it is Alpha, and it serves now for testing all that new staff like DenyList, Zygisk, etc - e.g., Zygisk just broke WebView in 63cfe7b4-alpha

Then, make sure to install the SAME version of that Stable (or Alpha), both Magisk app and Magisk ('service"), plus (of course) you must switch the Update Channel to that Stable (or Alpha if you REALLY wish Alpha)

If you still want Alpha, then be aware that since the Aplha app version you are running - it DOES NO MORE connect to Magisk Repo and you will not be able to install any module from the Repo. That was extesively mentioned and discussed here.

That might be a good reason to go back to Stable (slthough, when TJW releases new Stable, there will be no more Repo there either)

However, MHPC has its own thread on XDA, and there, in its OP post, there is a direct link to MHPC Github - you can download the module there and thus install MHPC without bothering with Repo that might be closed also soon
[Magisk] Fidom:
What is MHPC in two words? I am new here.

Did I understand right that to use stable Magisk, I should again reinstall stable apk and then probably patch boot.img again with fastboot?

And if I just change the update channel in current "alpha" app from the "alpha" to "stable", then it won't work and I won't see any modules anyway in the repository?
[Magisk] zgfg:
MHPC = Magisk Hide Props Config (you compained that you cannot find it or so)

Yes, to go back to Stable you must install the Stable apk (maybe you would need to uninstall Magisk Alpha app because you will be downgading the app, where both Stable and Alpha use the same package names and usually the Apk installer does not allow downgrading the apps versions)

There might be another problem - since that version you have your Magisk Alpha app, there wass no more MagiskHide but the new DenyList. However, you had (discrapances on your side) an older version of Magisk Alpha 'service' that still had MagiskHide.

I don't know when you switch back to the old Stable, would the MagiskHide settings be messed up due to the new DenyList

Maybe you should try to fully Unistall Magisk first (an option from Magisk app). Then to install the old Stable app, etc

(For everybody: Please don't play with the Alpha beast unless you are deeply up to all the new stuff and changes it brings, and you well understand how to handle the Alpha)
[Magisk] Chandru123:
Reverted to the previous build. Again apps started crashing while browsing. :(
[Magisk] ipdev:
Since Nigel and Marvin are not keeping up. :p

John has been busy..

vvb2060 is a few hours behind John. ;)

Lot of zygisk and deny stuff still being implemented.

For those using vvb2060's Alpha builds..

Expect vvb2060 to pull the changes and update alpha again soon. ;)

Just remember, vvb2060 is incorporating SafetyNet and old MagiskHide stuff back into the alpha builds.

I wish vvb2060 would turn it into a module instead of incorporating it back in. :rolleyes:

Then again, seems John has not yet finished updating the Magisk base yet. :unsure:​

When John is finally done with this update.

The Release Notes will be it's own article. 🙃​

Cheers all. :cowboy:
[Magisk] midgo12:
Hi Guys.

I am on Magisk Canary and was passing safety net up until today.

Can anyone suggest where to look or what to check to see why it has failed.

On Latest OOS 11.0.3.1GM21BA EU build.

OnePlus 7pro GM 1910.

Thanks for any help given...
[Magisk] ipdev:
[MODULE] MagiskHide Props Config - SafetyNet, prop edits, and more - xdaThread - Link

Great module if you want (need) to modify your device.

Didgeridoohan does an excellent job at maintaining and updating it. ;)

Cheers. :cowboy:
[Magisk] midgo12:
Tried this.

As well as a few other things like safety net fix latest as well as change my device with MHPC but still no success with my issue post #48011 above yours...
[Magisk] cosy6ay:
WebView is not working with he latest alpha magisk.
[Magisk] pndwal:
Please say if you changed anything, what are results for basicIntegrity, ctsProfile, evalType, which modules you use (especially USNF version), what is configured in MHPC, confirm that ROM is stock (looks like it is), installed app and Magisk both show f822c85b.

Meantime, try toggling MagiskHide off and on again in settings, disable all modules not necessary for SafetyNet, reboot and run Check SafetyNet again. 👍 PW
[Magisk] midgo12:
Doh...

I feel like a doufas now...://

I tried a lot of things but not toggling Magisk Hide off and on.

All good now the blue square is back:)
[Magisk] pndwal:
Yep, haven't had much time since 7 AM AUS time this morning... I think the mouse is asleep... The android just keeps going and going (on energiser batteries), but must prioritise! (I haven't moved to latest Alpha yet.)

Would be good; had the same thought. 😜

I think his strategy is just to keep Alpha and hide/deny working with all John's commits merged for testing purposes on a regular basis.

Agree! - John's strategy seems to be to implement all changes as a set for next build and test them together... It'll be interesting when it comes. 😁 ...

He's likely watching Alpha incremental testing / getting feedback from@vvb2060 and others in the meantime, which will help him however... He's bound making private builds and testing himself (or perhaps using Alpha) also.

By virtue of the major and MASSIVE changes occurring to produce next Beta / Canary builds, @vvb2060's bleeding edge Alpha will necessarily bleed more profusely than normal for a while I'm guessing...

As mentioned, if users are not in it for testing or for a thrill ride they will probably be best to go back to cutting edge Canary, or Stable.

😜 PW
[Magisk] elreydenj:
Sorry, i left that part out. Yes, i am using Magisk strictly for AP support. Hope to see a working scenario with SuperSU in the future. Thanks all.
[Magisk] Skyrocket2Paradise:
These steps worked perfectly on my 6p thanks
[Magisk] TheSt33v:
Bug Report

Device Model: Motorola Droid Turbo (XT1254)

Android Version: 5.1

Installed Mods: None. Phone is running unmodified latest official build from Motorola. Only Magisk v2 was flashed.

Logs: No logs appear in /cache

Issue: Phone boots straight to bootloader menu. The boot logo and boot animation never appear.

TWRP backup of stock boot: https://mega.nz/#!i9pRzZqR!onWz4Q5blvMY7gjPCjWIyGuAop5KTw4TGUSGhfprWtA

TWRP backup of Magisk patched boot: https://mega.nz/#!30YDlDSD!BhSS9KieBR9aisdu5YflIDpbFHrV4AyOqGSugjZSKIQ
[Magisk] allen099:
Unfortunately my purchase didn't work after installing all of the v2 files and magisk app. I posted in the phh superuser thread.
[Magisk] anantharam:
Wow!!!

I just tried the v2 and it works on my device!

Thank you so much... :good:
[Magisk] bmn.2312:
WOW

:crying::cyclops::cowboy:
[Magisk] spartan018:
Still seeing the same issue with Magisk v2. Maybe v3 will do it?
[Magisk] mykenyc:
Hey i was wondering if anyone with some hint of Dev in them know if i did this right, i tried to make a surround sound mod using the current one for the Nexus 5x and it works, but i want to make sure i did the right steps per the instructions?

*5x users please don't flash this even though it works, i want confirmation i did all the steps right by Developers who know how to use Magisk.
[Magisk] danielcr12:
topjohnwu[/MENTION] my phone (Moto X+1) boots fine, but the touch screen is redered usless, i wont read any imput. i have ro reflash my rom (Cm12.1) to make it work again.
[Magisk] gohamstergo:
when you dont post logs, your post is meaningless.
[Magisk] devsk:
This issue remains even with v2. [MENTION=4470081]topjohnwu[/MENTION]: any ideas here?
[Magisk] flatpedals:
Nexus 5, MOB30Y, Magisk v2, phh's root, systemless xposed 86.4. Android Pay works if I unmount root and on enforcing. No need to disable xposed framework and reboot or anything.

But I have a banking app, eToken BCR, that runs fine on Magisk and phh, but even with xposed disabled it doesn't.

It works only if I uninstall xposed framework.

Any idea?

http://xdaforums.com/android/help/etoken-bcr-bypass-root-check-smali-code-t3420443/page2
[Magisk] mahmutuslu:
s7 edge works ?
[Magisk] grep_i:
Not quite
[Magisk] topjohnwu:
An update will release soon to fix the current issues e.g. Samsung devices.

Please be patient :)
[Magisk] grep_i:
[MENTION=4470081]topjohnwu[/MENTION], you're great keep up the good work
[Magisk] ShapeShifter499:
Maybe I'm missing it but where did the downloads for "phh su" and "SuperSU" go? I cannot find any links.
[Magisk] Captain_Throwback:
Read the 2nd post.
[Magisk] dimm0k:
is there an easy way to remove systemless SuperSU and systemless Xposed instead of starting from 100% stock?
[Magisk] ShapeShifter499:
AH, thanks. >.<
[Magisk] janarp:
with magisk v8 I lost root... installed this way: 1) uninstall magisk 2) restore stock_boot.img 3) supersu 2.78 4) suhide 0.55 5) magisk v8

edit: something went wrong... now trying to go back magisk v7 and same issue... no root... but when I uninstall magisk I have root again and still see there is magisk v7 installed

edit2: solved it... magisk v8 running fine now... my issue was that stock_boot.img ...just taken boot.img from rom zip file and all is good now
[Magisk] andrew2432:
Passing safety net still? Or just working for pogo?
[Magisk] cohiba90:
Hi!

I have updated the mod in my mobile and all is fine but in my brother's mobile is impossible.

When i start magisk manager, i have an message "No root access, functionality limited" but all is green (like the screemshoot)

When I go to "modules", "phh's SuperUser r259" is there but i can't check it.

I re-install again the phh's SuperUser R259.zip three times but all time is the same.

What can i do?

Thanks
[Magisk] chudy_85:
go to magisk apk and then go to setting

push hidemagisk and reboot device

check sefetynet
[Magisk] zapahacks:
Ok guys, so I'm kind of confused.

There are 3 Magisk V8 version, the one in the main post and mod/mod V2.

- 1st question: with version should I use?

- 2nd question: I am in stock rom, no root, no nothing, safetynet passes and I have my boot.img. So the steps would be:

a. Flash boot.img

b. Flash phh-superuser-magisk-r259.zip

c. Flash Magisk V8/mod/mod2 (according to the answer of question 1)

d. Reboot and instal Manager 2.1

e. Go to Settings on the manager, check hidemagisk and reboot

Then I will have root and magisk working without triggering safetynet?

Thanks, any help would be appreciated, just a little confused here but I did read the last 4 pages and the first one :)
[Magisk] mortysantiago:
I have flashed the uninstaller but V7 still shows up as installed when I open the app. Anyone know why this isn't uninstalling?
[Magisk] eberhardweber:
Was unable to get this to work on my Tab S 10.5.

Ran the Magisk uninstaller, flashed old boot.img, SuperSU, SuperSU Hide and Magisk v8 in this order, and the Tab S still freezes at boot.
[Magisk] Ch3mist:
I too have this problem
[Magisk] Tkkg1994:
Only works on custom kernels on tab s

Sent from my SuperMan powered SM-G930F
[Magisk] Artim_96:
Ignore the mods, they are not from the dev, is just a stupid self-promoter. If you stick to the guides everything works fine. Do use v8 from main post and only from there.

If you are already on a never modified system, start with Magisk. Afterwards phh. When you install the app should be irrelevant, it might just crash without root
[Magisk] eberhardweber:
Yeah? :eek: What's changed from Magisk v7 that facilitates the need? I do have Magisk v7 running fine.
[Magisk] zapahacks:
Thanks!!

I flashed Magisk V8, then phh. I rebooted but I don´t see any superuser app. Also, safetynet turned to blue. I tried opening the app and it shows all in green, but it says no root acces. So I cheked the Enable Magisk Hide and rebooted, but it goes back to the same (no root, phhs superuser appears in black in the modules and can be choosen, and safetynet is blue:fail)

Is there anystep that I am missing?

Thanks again
[Magisk] paranoia_gu:
You should install phh superuser app. You can download from Google play.
[Magisk] preusstang:
Hi. Nexus5X just upgraded to v8 from v7. I'm on the magisk version of phh r259. I enabled Magisk Hide and rebooted. SafetyNet fails and all my apps still have root. Not sure what's up. I'm on Pure Nexus Nougat and it was a clean install before I originally put v7 and phh r259 on. Any ideas?