SafetyNet ctsPrifile pass on 12.5.1.x - Xiaomi Mi 10T / 10T Pro Questions & Answers

I would really like to use my banking apps on my phone, but because of failing SafetyNet, I can't.
It seems that kdrag0n's safetynet-fix won't work on the 10Ts -- there is this GitHub issue concerning MIUI.
I also tried MagiskHidePropsConf but I couldn't get the boot scripts to run, no matter which of the 3 boot stage options I picked, or whether using backgrounding or not.
Has anyone got a 12.5.1+ stock MIUI passing SafetyNet?
If no, which ROM would you recommend for regular stable releases? I see that Pixel Experience currently has no maintainer for our device.

Related

Recieved an HTC M8 - which ROM for MM/Nougat and working Android pay/banking apps?

Have just got an M8, sadly its on an really old version of android 5.1 and looking to update it using a custom rom.
one issue though is i really like Android pay/Banking apps to work so cant root or leave bootloader unlocked i dont think?
which ROM would you recommend preferably noughat if you feel its stable on the M8 and how can i make sure both android pay and banking apps work successfully ? do i need to make sure something is locked/not touched?
many thanks! an eager HTC fan!
jackvdbuk said:
Have just got an M8, sadly its on an really old version of android 5.1 and looking to update it using a custom rom.
one issue though is i really like Android pay/Banking apps to work so cant root or leave bootloader unlocked i dont think?
which ROM would you recommend preferably noughat if you feel its stable on the M8 and how can i make sure both android pay and banking apps work successfully ? do i need to make sure something is locked/not touched?
many thanks! an eager HTC fan!
Click to expand...
Click to collapse
don't root the rom or use a rootless rom
you can use magisk but safteynet is getting updates this days and magisk will get updates also it's just need time
unlocked bootloader is fine on this device only root is breaking safteynet
ahmed.ismael said:
you can use magisk but safteynet is getting updates this days and magisk will get updates also it's just need time
Click to expand...
Click to collapse
Magisk 13 beta is out, which should pass Safetynet. But it is beta, and some folks are having various issues/bugs.
Also, on my current daily driver device (OnePlus 3T) I've tried Magisk 12 with the Magisk module "Universal Safetynet Fix" and it passes Safetynet.
Link to various Magisk threads, if the OP is interested: https://forum.xda-developers.com/apps/magisk
You are completely right, it's the typical "cat and mouse game", where Google doesn't like Safetynet bypassed, will keep updating it; and topjohnwu (dev of Magisk) will keep trying to bypass it. Really annoying, for those of us that just want control of their phone (for simple things like Viper4A, Titanium, etc.) but still want access to banking apps, Netflix, etc.

Having problems using andorid pay on global nightly build

Yes, I know lots of people asked this thing already.
Many says only stable china/global version can use AP.
But my case I used universal safetynet fix magisk module. Which means I can pass safetynet check.
Still can's use the function under nightly build. I tried on stable version it works perfectly fine.
Is there anything else other than pass safetynet I need to do?
I am able to add a credit card+all other membership cards to AP apps.
q13017 said:
Yes, I know lots of people asked this thing already.
Many says only stable china/global version can use AP.
But my case I used universal safetynet fix magisk module. Which means I can pass safetynet check.
Still can's use the function under nightly build. I tried on stable version it works perfectly fine.
Is there anything else other than pass safetynet I need to do?
I am able to add a credit card+all other membership cards to AP apps.
Click to expand...
Click to collapse
Use Magisk hide

Looking for a ROM

As it appears StatixOS is going to no longer be maintained for whatever reason, I'm stuck with a soon to be outdated ROM on my, to me, expensive phone. So I have a simple question...
What ROMs are there for this phone? I'm aware there are some that aren't listed here, but I'm looking for one with the same features as Statix (plus some other features). I'd also prefer it if the ROM were official, as that tells me it's receiving proper support and likely won't be dropped for some time.
Karitoriki said:
As it appears StatixOS is going to no longer be maintained for whatever reason, I'm stuck with a soon to be outdated ROM on my, to me, expensive phone. So I have a simple question...
What ROMs are there for this phone? I'm aware there are some that aren't listed here, but I'm looking for one with the same features as Statix (plus some other features). I'd also prefer it if the ROM were official, as that tells me it's receiving proper support and likely won't be dropped for some time.
Click to expand...
Click to collapse
Stock is so good now days that a custom rom is not needed anymore.
Use the stock rom with a custom kernel and you can find find a few addons to your liking.
Sent from my Pixel 3a XL using Tapatalk
vandyman said:
Stock is so good now days that a custom rom is not needed anymore.
Use the stock rom with a custom kernel and you can find find a few addons to your liking.
Sent from my Pixel 3a XL using Tapatalk
Click to expand...
Click to collapse
Unfortunately I don't find that to be the case - the stock ROM doesn't offer the options that I like, such as navbar/statusbar cust., custom fonts, and precise DPI control, among others. Addons and third party apps can accomplish a lot of it, but very imperfectly, being more prone to bugs and issues than the same feature built into the ROM itself.
After having given Bootleggers ROM a try, I was VERY unimpressed, running into issues with it just minutes after booting and, even later after setting some things up, facing frozen apps, UX not responding properly and some rather suspicious activity (such as it somehow knowing what email I originally logged into my phone with, despite doing MULTIPLE full system wipes prior to install and being the ONLY custom ROM that triggered a "Severe security alert" from google upon trying to sign in), I've decided to stick with StatixOS until the LineageOS devs get off their butts and make an official ROM for this phone, as the unofficial one doesn't support eSIM which is required for Google Fi. StatixOS has the features I want, it's actually stable unlike Bootleggers "stable" build, and GPay works on it.
Note that my gripes with Bootleggers and the unofficial LineageOS are not meant to say you're not working hard at making a ROM - it's entirely a subjective review, and as a ROM enthusiast I understand the time and effort that goes into making a ROM even run partially right.
Have you tried Dirty Unicorns?
Or stock with edxposed and GravityBox (this is what I am currently using and it has been working perfectly for the last 2 months)?
How do you get GPay to work on StatixOS, I have tried using Magisk hide but it still detects root?
rzcay69 said:
How do you get GPay to work on StatixOS, I have tried using Magisk hide but it still detects root?
Click to expand...
Click to collapse
It may be an isolated case, but I had all google play services modules hidden along with google pay and other google apps (just in case they talk to each other), along with the safety patch module from magisk.
creeve4 said:
Have you tried Dirty Unicorns?
Or stock with edxposed and GravityBox (this is what I am currently using and it has been working perfectly for the last 2 months)?
Click to expand...
Click to collapse
I'm using the latest DU official for bonito right now, and at first everything was working wonderfully - except Google Fi is running into some issues on it where I can't send messages or make calls without being connected to wifi or enabling mobile data. I might reflash Statix, or I might just live with having to keep mobile data on when I'm not at home or work until they patch it up.

ROM ❯ PIXEL 2 XL ❯ OFFICIAL ❯ ProtonAOSP 11

ProtonAOSP
Android 11 ROM​
ProtonAOSP is a minimal Android fork (custom ROM) focused on UI/UX and performance, with a touch of privacy.
Screenshots
Screenshots of the latest version
Installation
This ROM is currently distributed as factory images, similar to stock. Flash it the same way you would flash stock factory images. Don't forget to wipe all data using "fastboot -w" before booting the ROM.
Firmware is included, so there is no specific requirement for which version of the stock ROM you are coming from.
You can also use the quick & easy web installer, which allows you to install and update the ROM from any computer or phone without using the command line. The installer works entirely within your web browser and completes in as little as 4 minutes, depending on the speed of your internet connection. Consider using the web installer instead of installing manually.
More detailed installation instructions and guides
Features
List of current features, with accompanying screenshots and explanations
Downloads
Downloads and changelogs for all versions
Builds with and without minimal Google services (gapps) included are provided for convenience.
Using the quick and easy web installer is recommended unless you have a specific reason to download and install the ROM manually.
Support
If you have questions or concerns, please read the Frequently Asked Questions before asking. It saves time for everyone involved, especially you, and allows us to provide higher-quality answers for all users.
Website with comprehensive documentation
Join the Telegram group for support and extras
Please consider donating to support development if you found this helpful: recurring donation to keep the project alive in the long term or buy me a coffee
Kernel source code
ROM source code
Looks so tempting, downloading as I type.
Quick check - for the updates in future, would we still need to wipe data before booting if already in the previous ProtonAOSP version .
Thank you for bringing love to our pixel series !
Love to know what you have changed to alter battery usage before i download it, every other 11 ROM drains like a bathtub, even at idle
According to the Pixel 5 thread this ROM passes safetynet w/o magisk. looks interesting. Downloading now!
componentchunk said:
According to the Pixel 5 thread this ROM passes safetynet w/o magisk. looks interesting. Downloading now!
Click to expand...
Click to collapse
It may be like the other new 11 based ROM that turned up on here yesterday, and have its device name set to Pixel 5/5a to pass SafetyNet out of the box
https://forum.xda-developers.com/showpost.php?p=83885115&postcount=12
Its not the way i would do it, but each to his own.
Not booting for me. Stuck on splash screen. Clean flash of proton-aosp_taimen_11.2.0-gapps.zip on twrp-3.4.0-1-taimen then wipe data before reboot.
twiddles said:
Not booting for me. Stuck on splash screen. Clean flash of proton-aosp_taimen_11.2.0-gapps.zip on twrp-3.4.0-1-taimen then wipe data before reboot.
Click to expand...
Click to collapse
fastboot flash boot boot.img (stock October). That booted it for me until he can update a fix. This ROM btw is phenomenal on battery life
twiddles said:
Not booting for me. Stuck on splash screen. Clean flash of proton-aosp_taimen_11.2.0-gapps.zip on twrp-3.4.0-1-taimen then wipe data before reboot.
Click to expand...
Click to collapse
Same, I've tried flashing/sideloading from Lineage 17 and stock P/Q/R. Stuck on splash for 10+ mins before I force reboot into bootloader to retry each time
kdrag0n said:
ProtonAOSP • Pixel 2 XL
Click to expand...
Click to collapse
Hello. Proton is incredible. Very fast, smooth and tenacious. Tested it from the first version. Thank you very much. I want to clarify something else for myself: Do I need to flash in both slots if a stock is installed?
palimatix said:
Looks so tempting, downloading as I type.
Quick check - for the updates in future, would we still need to wipe data before booting if already in the previous ProtonAOSP version .
Thank you for bringing love to our pixel series !
Click to expand...
Click to collapse
No, you only need to wipe data if switching from another ROM.
73sydney said:
Love to know what you have changed to alter battery usage before i download it, every other 11 ROM drains like a bathtub, even at idle
Click to expand...
Click to collapse
I didn't do anything specific for battery; it's just that battery tends to be better on custom ROMs than it is on Pixel 2 stock, partially due to being less bloated.
73sydney said:
It may be like the other new 11 based ROM that turned up on here yesterday, and have its device name set to Pixel 5/5a to pass SafetyNet out of the box
https://forum.xda-developers.com/showpost.php?p=83885115&postcount=12
Its not the way i would do it, but each to his own.
Click to expand...
Click to collapse
My ROM reports a fake security patch level to SafetyNet so basic attestation will always pass. However, I've observed that Google has started to roll out hardware attestation for the Pixel 2, so I also modified the model name with an invisible character to revert it back to basic. The Pixel 5 name is not used.
twiddles said:
Not booting for me. Stuck on splash screen. Clean flash of proton-aosp_taimen_11.2.0-gapps.zip on twrp-3.4.0-1-taimen then wipe data before reboot.
Click to expand...
Click to collapse
componentchunk said:
Same, I've tried flashing/sideloading from Lineage 17 and stock P/Q/R. Stuck on splash for 10+ mins before I force reboot into bootloader to retry each time
Click to expand...
Click to collapse
Sorry for the inconvenience, the problem lies in a botched SafetyNet fix that was missed in testing due to not flashing all partitions. You can make it boot temporarily by flashing the stock boot image. A hotfix that boots out-of-the-box will be up shortly.
pablo9023 said:
Hello. Proton is incredible. Very fast, smooth and tenacious. Thank you very much. I want to clarify something else for myself: I tested it from the first version. Do I need to flash in both slots if a stock is installed?
Click to expand...
Click to collapse
No, ideally the latest stock ROM would be installed in both slots beforehand but that's only because this build is missing firmware. A hotfix will be up shortly with the latest firmware included.
Nice, got gpay working with magisk.
Unfortunately stuck on splash after installing edxposed. This is definitely an unreasonable request but if xposed edge features could be built natively into the rom I wouldn't need xposed
componentchunk said:
Nice, got gpay working with magisk.
Unfortunately stuck on splash after installing edxposed. This is definitely an unreasonable request but if xposed edge features could be built natively into the rom I wouldn't need xposed
Click to expand...
Click to collapse
Xposed will never be supported, you are on your own if it's broken. I wouldn't recommend using it because it can cause all sorts of weird bugs.
A hotfix update has just been released to fix issues with a botched SafetyNet fix that caused most apps using HTTP outside of a browser to break, including Google Translate, SMS/MMS, and many others. I've figured out a new way to fix SafetyNet that doesn't come with those pitfalls, so SafetyNet is still passing out-of-the-box and apps will no longer break. A bug with sensitivity in the Active Edge settings has also been fixed, and missing firmware has been re-added so there is no need to flash the latest stock ROM first.
Re-download v11.2.0 from GitHub for the fixes. I've decided to re-upload it rather than bumping the version because the previous SafetyNet fix was very broken and also caused boot failures if boot.img wasn't replaced.
kdrag0n said:
A hotfix update has just been released to fix issues with a botched SafetyNet fix that caused most apps using HTTP outside of a browser to break, including Google Translate, SMS/MMS, and many others. I've figured out a new way to fix SafetyNet that doesn't come with those pitfalls, so SafetyNet is still passing out-of-the-box and apps will no longer break. A bug with sensitivity in the Active Edge settings has also been fixed, and missing firmware has been re-added so there is no need to flash the latest stock ROM first.
Re-download v11.2.0 from GitHub for the fixes. I've decided to re-upload it rather than bumping the version because the previous SafetyNet fix was very broken and also caused boot failures if boot.img wasn't replaced.
Click to expand...
Click to collapse
Great work, and thank you for the fast updates. Really looking forward to using the ROM when I clean format next time. Waiting for Google to release the last Security patch in December before making the jump, don't want to clean install every month. I usually stick with a ROM for a few months at a time.
Just to clarify if anyone is confused: this is an Android 11 ROM, not Android 10. XDA DevDB has no option for 11 so I had to put 10. I've just edited the DevDB info out of the post now and added 11 to the header so there should be no more confusion.
I am testing proton, so far its fast, snappy, and stable, one word of caution for anyone who uses my recommendations. Do not patch the boot.img as I always recommended, this landed me in a bootloop. Once I wiped the device clean, and started over (installed ROM+GAPP), then setup the device, then once setup, reboot to BL/TWRP (ADB TWRP), and installed MAGISK zip version from within TWRP, it booted fine. It only has an issue if you patch the boot.img from within MAGISK itself then ADB the boot.img. Normally this is the only method I use, but it will not work properly with this ROM (which is perfectly fine as the zip works great and passes safetynet out of the box)!
This ROM doesnt have all the goodies I am used to, BUT its a VERY decent, and stable 11 ROM so I DO recommend users to at least try it if you are looking for a decent 11 ROM. Battery life for me is on par with 10 so I do not see any major show stoppers using this as a DD. I will run it for a few days and report anything found (if anything is found), otherwise, its great.
GROOVYJOSHCLARK said:
I am testing proton, so far its fast, snappy, and stable, one word of caution for anyone who uses my recommendations. Do not patch the boot.img as I always recommended, this landed me in a bootloop. Once I wiped the device clean, and started over (installed ROM+GAPP), then setup the device, then once setup, reboot to BL/TWRP (ADB TWRP), and installed MAGISK zip version from within TWRP, it booted fine. It only has an issue if you patch the boot.img from within MAGISK itself then ADB the boot.img. Normally this is the only method I use, but it will not work properly with this ROM (which is perfectly fine as the zip works great and passes safetynet out of the box)!
This ROM doesnt have all the goodies I am used to, BUT its a VERY decent, and stable 11 ROM so I DO recommend users to at least try it if you are looking for a decent 11 ROM. Battery life for me is on par with 10 so I do not see any major show stoppers using this as a DD. I will run it for a few days and report anything found (if anything is found), otherwise, its great.
Click to expand...
Click to collapse
thank you very much for your assessment! I also find this rom to be very stable, snappy and the slight changes to the stock rom are very well thought out - next to perfect! big thanks to the dev krag0n!
I'm coming from an Android 9 Custom ROM and I wanted to switch to this, the instructions states that it should just be a simple flash. Should I still start from a clean reinstall of stock Android 11 or does flashing this come with that already?
kdrag0n said:
I didn't do anything specific for battery; it's just that battery tends to be better on custom ROMs than it is on Pixel 2 stock, partially due to being less bloated.
Click to expand...
Click to collapse
Stock has battery issues, all other 11 based ROMS ive tested have hadthe same battery issues. So i was asking in case you managed to find and fix the issue, because Google so far hasnt
I'll give it a crack anyways and see what its like, cheers
kdrag0n said:
My ROM reports a fake security patch level to SafetyNet so basic attestation will always pass. However, I've observed that Google has started to roll out hardware attestation for the Pixel 2, so I also modified the model name with an invisible character to revert it back to basic. The Pixel 5 name is not used.
Click to expand...
Click to collapse
fwiw, there is no evidence that Google has or plans to force hardware attestation on Pixel 2/XL. i monitor reports of these things over in the magisk threads, and as part of my own magisk module, and theres no suggestion it will happen to Pixel 2/XL, more likely it will happen with 4+ than the old Pixel 2/XL....
Ill probably change the fingerprint back to Pixel 2/XL and Android 11, personally i dont see the point of spoofing another device when the Pixel 2/XL is still officially supported...just my opinion, no offence meant
73sydney said:
Stock has battery issues, all other 11 based ROMS ive tested have hadthe same battery issues. So i was asking in case you managed to find and fix the issue, because Google so far hasnt
I'll give it a crack anyways and see what its like, cheers
fwiw, there is no evidence that Google has or plans to force hardware attestation on Pixel 2/XL. i monitor reports of these things over in the magisk threads, and as part of my own magisk module, and theres no suggestion it will happen to Pixel 2/XL, more likely it will happen with 4+ than the old Pixel 2/XL....
Ill probably change the fingerprint back to Pixel 2/XL and Android 11, personally i dont see the point of spoofing another device when the Pixel 2/XL is still officially supported...just my opinion, no offence meant
Click to expand...
Click to collapse
My Pixel 2 XL has been getting hardware attestation in all of my tests recently if the model name is set to "Pixel 2 XL". It's possible that I'm being A/B tested and most users don't have this problem, but either way, I haven't been able to pass SafetyNet without changing the model name because of it.
Either way, I've added hacks into the system in my ROM to avoid spoofing the model name while still defying hardware attestation and passing SafetyNet despite being on a mismatching security patch level. I agree, I don't want to change the model name just to pass SafetyNet, so I've been coming up with other solutions to avoid doing that.

[q] Gpay on lineage 19.1

Hey guys, has anyone gotten Gpay to work on lineage 19.1? I have done the following and have had very odd results. Firstly, I am passing safteynet and my device is registered as play certified in Google play store. I'm seeing where sometimes gpay won't open at all and when it does it says it is unable to load my payment methods.
Specs:
OS - linageOS 19.1 (latest build as of this post)
GAPPS - Mindthegapps (latest build as of this post)
Steps taken:
Installed magisk, enabled zygisk and rebooted
Installed magisk hide props module then rebooted
Installed shamiko module then rebooted
Installed universal safteynet fix (zygisk) then rebooted
Configured denylist in magisk checking GPS (all), and Gpay (all) rebooted
Changed device fingerprint with magisk hide props module to a certified one then rebooted
Additional steps taken:
I cleared data from GPS, play store and Gpay and rebooted
I tried a different device fingerprint and rebooted (clearing data like above afterwards and rebooting again)
I have done a complete fresh install of my OS and tried again from scratch.
I also tried seeing is renaming magisk would help at all, it didn't
It appears I'm getting nowhere with this. If anyone has gotten it to work and has some insight it's be greatly appreciated!
Nevermind, looks like it was an issue from having the pixelify module installed as well. After I removed it it started working just fine.
deathblade said:
Nevermind, looks like it was an issue from having the pixelify module installed as well. After I removed it it started working just fine.
Click to expand...
Click to collapse
Hey deathblade!
Thanks for helping me out on the other thread.
Just wanted to check in, did you use the official build or the unofficial one with the Pixel Goodies? I'm intending/hoping to have full functionalities of Google Pay using the unofficial build, but from your post it seems that I can't have the Pixel experience if I want the ROM to work with Google Pay?
HW898 said:
Hey deathblade!
Thanks for helping me out on the other thread.
Just wanted to check in, did you use the official build or the unofficial one with the Pixel Goodies? I'm intending/hoping to have full functionalities of Google Pay using the unofficial build, but from your post it seems that I can't have the Pixel experience if I want the ROM to work with Google Pay?
Click to expand...
Click to collapse
I'm using the official build. I think the unofficial has everything needed to use Gpay and have some pixel things baked in. So might be worth a look in your case
deathblade said:
I'm using the official build. I think the unofficial has everything needed to use Gpay and have some pixel things baked in. So might be worth a look in your case
Click to expand...
Click to collapse
Aite, I will try out the unofficial one and see if GPay works there too. Thanks for the headsup!
HW898 said:
Aite, I will try out the unofficial one and see if GPay works there too. Thanks for the headsup!
Click to expand...
Click to collapse
I just remembered, the unofficial is setup to pass safteynet out the box, but more maybe needed for Gpay to work. Once you flash it try it out, if you run into issues I can provide what I did to get Gpay working
deathblade said:
Nevermind, looks like it was an issue from having the pixelify module installed as well. After I removed it it started working just fine.
Click to expand...
Click to collapse
Hi there, trying out the official build after experiencing some problems on the unofficial one. Any alternatives to pixiel-ing the ROM?
HW898 said:
Hi there, trying out the official build after experiencing some problems on the unofficial one. Any alternatives to pixiel-ing the ROM?
Click to expand...
Click to collapse
Not that I've found, however I did notice if you install the pixelify module then uninstall it, it does seem to leave some stuff behind. Like I still have the option to use Hold for me and direct my call. So it might work out where you can install it to get the things you want then remove it to get Gpay working
deathblade said:
Not that I've found, however I did notice if you install the pixelify module then uninstall it, it does seem to leave some stuff behind. Like I still have the option to use Hold for me and direct my call. So it might work out where you can install it to get the things you want then remove it to get Gpay working
Click to expand...
Click to collapse
I see... So these also means stuff like Now playing etc. will be gone too right?
Also, did you experience the problems I've faced in the unofficial build? sounds cannot change etc. as posted in main thread
HW898 said:
I see... So these also means stuff like Now playing etc. will be gone too right?
Also, did you experience the problems I've faced in the unofficial build? sounds cannot change etc. as posted in main thread
Click to expand...
Click to collapse
Nope now playing is still there. I really only used it the module to force call screening to show up. But I have pretty much everything I remember from stock plus a few phone related goodies. I never tried the unofficial build but on the official I do not have that issue
deathblade said:
Nope now playing is still there. I really only used it the module to force call screening to show up. But I have pretty much everything I remember from stock plus a few phone related goodies. I never tried the unofficial build but on the official I do not have that issue
Click to expand...
Click to collapse
I see... I will try installing the official one without magisk as I won't want to meddle with rooting stuff for now, will get back with results asap!
deathblade said:
Hey guys, has anyone gotten Gpay to work on lineage 19.1? I have done the following and have had very odd results. Firstly, I am passing safteynet and my device is registered as play certified in Google play store. I'm seeing where sometimes gpay won't open at all and when it does it says it is unable to load my payment methods.
Specs:
OS - linageOS 19.1 (latest build as of this post)
GAPPS - Mindthegapps (latest build as of this post)
Steps taken:
Installed magisk, enabled zygisk and rebooted
Installed magisk hide props module then rebooted
Installed shamiko module then rebooted
Installed universal safteynet fix (zygisk) then rebooted
Configured denylist in magisk checking GPS (all), and Gpay (all) rebooted
Changed device fingerprint with magisk hide props module to a certified one then rebooted
Additional steps taken:
I cleared data from GPS, play store and Gpay and rebooted
I tried a different device fingerprint and rebooted (clearing data like above afterwards and rebooting again)
I have done a complete fresh install of my OS and tried again from scratch.
I also tried seeing is renaming magisk would help at all, it didn't
It appears I'm getting nowhere with this. If anyone has gotten it to work and has some insight it's be greatly appreciated!
Click to expand...
Click to collapse
Just also wanted to clarify in the case I decide to install magisk, which module do you install exactly? All of them? Zygisk/hide props module/shamiko/universal safetynet fix?
HW898 said:
Just also wanted to clarify in the case I decide to install magisk, which module do you install exactly? All of them? Zygisk/hide props module/shamiko/universal safetynet fix?
Click to expand...
Click to collapse
Ok so here is the breakdown:
Zygisk is not a module, but an implementation method used by modules. Magiskhide props is used to change the device fingerprint to a valid one that registers as protected by google play. Shamiko is for hiding root from Google play services, and Gpay (and whatever other apps may need it). Universal safteynet fix is used to help pass google safteynet checks (security). Not listed is the pixelify module used to add pixel exclusive features but of course with it install it cause havoc on Gpay and other apps so once installed it should be uninstalled.
TLDR
Yes all of them
deathblade said:
Ok so here is the breakdown:
Zygisk is not a module, but an implementation method used by modules. Magiskhide props is used to change the device fingerprint to a valid one that registers as protected by google play. Shamiko is for hiding root from Google play services, and Gpay (and whatever other apps may need it). Universal safteynet fix is used to help pass google safteynet checks (security). Not listed is the pixelify module used to add pixel exclusive features but of course with it install it cause havoc on Gpay and other apps so once installed it should be uninstalled.
TLDR
Yes all of them
Click to expand...
Click to collapse
Aite thanks for the help mate! just installed but apparently, i couldn't find gapps despite sideloading it.. might have to reinstall again
Hmm safetynet fix seems to fail, can't pass cts profile.. any step by step guides by any chance?
deathblade said:
Ok so here is the breakdown:
Zygisk is not a module, but an implementation method used by modules. Magiskhide props is used to change the device fingerprint to a valid one that registers as protected by google play. Shamiko is for hiding root from Google play services, and Gpay (and whatever other apps may need it). Universal safteynet fix is used to help pass google safteynet checks (security). Not listed is the pixelify module used to add pixel exclusive features but of course with it install it cause havoc on Gpay and other apps so once installed it should be uninstalled.
TLDR
Yes all of them
Click to expand...
Click to collapse
HW898 said:
Hmm safetynet fix seems to fail, can't pass cts profile.. any step by step guides by any chance?
Click to expand...
Click to collapse
That's where magisk hide props comes in. I don't have a full guide that I know of but I could do a quick wtite up tomorrow for you
deathblade said:
That's where magisk hide props comes in. I don't have a full guide that I know of but I could do a quick wtite up tomorrow for you
Click to expand...
Click to collapse
I got it working after following a guide~
Unfortunately features like now playing isn't working. the rest is pretty much okay tho
HW898 said:
I got it working after following a guide~
Unfortunately features like now playing isn't working. the rest is pretty much okay tho
Click to expand...
Click to collapse
You install the pixelify module? Also can you explain how it's not working?
deathblade said:
You install the pixelify module? Also can you explain how it's not working?
Click to expand...
Click to collapse
Nope, I didn't. Other than the modules to hide from banking apps as mentioned above, I installed a pixel launch module here to make it for pixel-like: https://forum.xda-developers.com/t/app-mod-pixel-launcher.4442077/
Other than that nothing else.
It doesn't;t work in the sense that it does not pick up music, even popular ones. The settings are there though, I can see them. It just doesn't identify any songs
HW898 said:
Nope, I didn't. Other than the modules to hide from banking apps as mentioned above, I installed a pixel launch module here to make it for pixel-like: https://forum.xda-developers.com/t/app-mod-pixel-launcher.4442077/
Other than that nothing else.
It doesn't;t work in the sense that it does not pick up music, even popular ones. The settings are there though, I can see them. It just doesn't identify any songs
Click to expand...
Click to collapse
This is the pixelify module I installed then removed, you can give it a try.
GitHub - Kingsman44/Pixelify: Magisk module to enables pixel exclusive features and ui
Magisk module to enables pixel exclusive features and ui - GitHub - Kingsman44/Pixelify: Magisk module to enables pixel exclusive features and ui
github.com

Categories

Resources