Oreo xposed SafetyNet bypass? - Moto G4 Plus Questions & Answers

Is this possible? I tried universal safetynet fix but it doesn't work.
Any help is appreciated.

AsianLSX said:
Is this possible? I tried universal safetynet fix but it doesn't work.
Any help is appreciated.
Click to expand...
Click to collapse
AFAIK you can't pass safetynet when using xposed

If you're using systemless Xposed then go to magisk then to modules and deselect Xposed. Reboot. Then try passing safety net. Still if it doesn't work, flash the universal crapety crap and then check. Should work.
After your work is done. Again select Xposed and reboot to get Xposed up and running

Ayan Uchiha Choudhury said:
If you're using systemless Xposed then go to magisk then to modules and deselect Xposed. Reboot. Then try passing safety net. Still if it doesn't work, flash the universal crapety crap and then check. Should work.
After your work is done. Again select Xposed and reboot to get Xposed up and running
Click to expand...
Click to collapse
This doesn't let me permanently pass SafetyNet, once I reboot to reenable Xposed it doesn't pass SN anymore.

AsianLSX said:
This doesn't let me permanently pass SafetyNet, once I reboot to reenable Xposed it doesn't pass SN anymore.
Click to expand...
Click to collapse
Again you didn't understand what I meant. Even I had this problem. You CANNOT pass safety net and have Xposed at the same time. One you need to leave

Ayan Uchiha Choudhury said:
Again you didn't understand what I meant. Even I had this problem. You CANNOT pass safety net and have Xposed at the same time. One you need to leave
Click to expand...
Click to collapse
That's what I wrote already. You cannot use both.

Related

"Custom Status" on Boot, how to remove? [SOLVED]

Did several searches but find no guidance on how to deal with this result of rooting. (I'm terrible at finding stuff here!)
I used the [How-To] Root G900VVRU1ANE9 to achieve root and noticed the Custom with padlock after a second reboot (may have been on first, I failed to notice).
What is the preferred way to deal with this situation if there is one?
Update:
Wanam Xposed module for Xposed Framework did the trick.
Thanks for the helpful info.
Use triangle away. Or use an xposed module.
SCClockDr said:
Did several searches but find no guidance on how to deal with this result of rooting. (I'm terrible at finding stuff here!)
I used the [How-To] Root G900VVRU1ANE9 to achieve root and noticed the Custom with padlock after a second reboot (may have been on first, I failed to notice).
What is the preferred way to deal with this situation if there is one?
Click to expand...
Click to collapse
Wanam Xposed module for Xposed Framework has an override for that.
tgeery said:
Wanam Xposed module for Xposed Framework has an override for that.
Click to expand...
Click to collapse
Doesn't seem to work with the NI2 update?
SCClockDr said:
Did several searches but find no guidance on how to deal with this result of rooting. (I'm terrible at finding stuff here!)
I used the [How-To] Root G900VVRU1ANE9 to achieve root and noticed the Custom with padlock after a second reboot (may have been on first, I failed to notice).
What is the preferred way to deal with this situation if there is one?
Click to expand...
Click to collapse
ldeveraux said:
Doesn't seem to work with the NI2 update?
Click to expand...
Click to collapse
You can rename SysScope.apk in system/app. If it dosen't cause any problems you can delete it. If I am correct I think the backup and reset feature will be affected but that dosen't matter as we use safestrap for that anyways. I don't bother with this because the custom padlock doesn't bother me.
[SOLVED]
Wanam Xposed module for Xposed Framework did the trick.
Thanks for the helpful info.
SCClockDr said:
Wanam Xposed module for Xposed Framework did the trick.
Thanks for the helpful info.
Click to expand...
Click to collapse
It worked for me too (eventually). I think i just has to restart like 10 times!
Obviously if using ART, XPosed won't work?

Magisk

Has anyone tried Magisk (http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382) on the A7 yet? I'd love to be able to root and still have ability to use Android Pay.
tdgillihan said:
Has anyone tried Magisk (http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382) on the A7 yet? I'd love to be able to root and still have ability to use Android Pay.
Click to expand...
Click to collapse
Was wondering about this too. Not entirely confident about what things to reflash in case things go wrong otherwise wouldve tried this.
So just took a risk and tried it and the phh's SuperUser didn't provide root. Might have to do something with how the latest SuperSU doesn't work either?
reddrago said:
So just took a risk and tried it and the phh's SuperUser didn't provide root. Might have to do something with how the latest SuperSU doesn't work either?
Click to expand...
Click to collapse
Chinese A2017 it worked... But I used the super user app as suggested by Tenfar on his rooting guide...
tdgillihan said:
Has anyone tried Magisk (http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382) on the A7 yet? I'd love to be able to root and still have ability to use Android Pay.
Click to expand...
Click to collapse
I've tried it on my Moto X Play. Magisk and Xposed have no influence on Android Pay. But rooting (Phh's SU with Magisk) caused SafetyNet test turned red. It looks like Google suceeded to eliminate any coexistence between root and AP.
piskr said:
I've tried it on my Moto X Play. Magisk and Xposed have no influence on Android Pay. But rooting (Phh's SU with Magisk) caused SafetyNet test turned red. It looks like Google suceeded to eliminate any coexistence between root and AP.
Click to expand...
Click to collapse
Did you try using AP or check with SafetyNet after flipping the switch in Magisk to show it as unrooted?
tdgillihan said:
Did you try using AP or check with SafetyNet after flipping the switch in Magisk to show it as unrooted?
Click to expand...
Click to collapse
Just ran SafetyNet and reverted to unrooted after. As far as I know failing with SafetyNet means that AP won't work.
ultramag69 said:
Chinese A2017 it worked... But I used the super user app as suggested by Tenfar on his rooting guide...
Click to expand...
Click to collapse
Really? Hmmm, that's weird. Have you confirmed root and have you tried AP?
Always thank those who are helpful...and just ignore those who aren't.
piskr said:
Just ran SafetyNet and reverted to unrooted after. As far as I know failing with SafetyNet means that AP won't work.
Click to expand...
Click to collapse
The whole point of this is that you flip the switch and you're temp unrooted for whatever duration you chose. 5min is default I think. If you didn't try that then you never really checked to see if it would work before dumping it.
Always thank those who are helpful...and just ignore those who aren't.
tdgillihan said:
The whole point of this is that you flip the switch and you're temp unrooted for whatever duration you chose. 5min is default I think. If you didn't try that then you never really checked to see if it would work before dumping it.
Always thank those who are helpful...and just ignore those who aren't.
Click to expand...
Click to collapse
Ok, thanks, I'll find the time to try it again. But temporally unroot with Chainfire superSU didn't help. I used superSU without Magisk though, it was systemless and it worked with AP in the beginning. Seems that AP checked only system changes then. It worked till recently when Google obviously cut off AP from rooted phones.
piskr said:
Ok, thanks, I'll find the time to try it again. But temporally unroot with Chainfire superSU didn't help. I used superSU without Magisk though, it was systemless and it worked with AP in the beginning. Seems that AP checked only system changes then. It worked till recently when Google obviously cut off AP from rooted phones.
Click to expand...
Click to collapse
If you're running a custom ROM it may or may not work. Some are saying it does and others not. But if we're talking about the A7 here that'll be stock for now.
Always thank those who are helpful...and just ignore those who aren't.
tdgillihan said:
Really? Hmmm, that's weird. Have you confirmed root and have you tried AP?
Always thank those who are helpful...and just ignore those who aren't.
Click to expand...
Click to collapse
I'm using apps that require root, have the sd card fix done so EVERYTHING can use the sd card, file managers can't usually move or delete files on unrooted device, use clocksync so I have accurate time and have titanium backup installed. Haven't played with titanium backup but everything else works brilliantly...
Used Root Checker by joeykrim and it confirmed root...
It is phh's SuperUser app on playstore. Seems to work fine...
ultramag69 said:
I'm using apps that require root, have the sd card fix done so EVERYTHING can use the sd card, file managers can't usually move or delete files on unrooted device, use clocksync so I have accurate time and have titanium backup installed. Haven't played with titanium backup but everything else works brilliantly...
Used Root Checker by joeykrim and it confirmed root...
It is phh's SuperUser app on playstore. Seems to work fine...
Click to expand...
Click to collapse
Wait, are you saying that the su in tenfars locked bl root is phh's? I didn't know that. That's good, then when he gets it working for the 2017u this should work on it as well.
Always thank those who are helpful...and just ignore those who aren't.
tdgillihan said:
Wait, are you saying that the su in tenfars locked bl root is phh's? I didn't know that. That's good, then when he gets it working for the 2017u this should work on it as well.
Always thank those who are helpful...and just ignore those who aren't.
Click to expand...
Click to collapse
Don't know , I just downloaded the root manager Tenfars recommended from play store...
It works fine...
Are there any new reports on this subject? I have been able to successfully install Magisk and PHH SU on a Nexus 6P , but using the identical procedure on my Axon 7 (U) does not work. I am puzzled.
Magisk installs fine (busybox is detected) on A2017U but root + Magisk does not work. Going to keep testing some options and methods and I'll let you know.
SuperSU fails during install after extract.
phh-superuser install completes but no root.
lokissmile said:
Magisk installs fine (busybox is detected) on A2017U but root + Magisk does not work. Going to keep testing some options and methods and I'll let you know.
SuperSU fails during install after extract.
phh-superuser install completes but no root.
Click to expand...
Click to collapse
No luck so far, my gut thinks it's an issue with the kernel / boot.img patch. Sorry guys I'm going to keep banging on this one but it might take me a bit as I don't have a linux box up right now. Can someone that has a Chinese model get me a copy of the patched boot.img?
lokissmile said:
No luck so far, my gut thinks it's an issue with the kernel / boot.img patch. Sorry guys I'm going to keep banging on this one but it might take me a bit as I don't have a linux box up right now. Can someone that has a Chinese model get me a copy of the patched boot.img?
Click to expand...
Click to collapse
that's my thought too, since magisk seems not to create a log in /cache as it should and doesn't reaveal itself via logcat it looks like it doesn't realy get executed.
The guys in the common magisk were not realy able to help, guess we have to dig more into the init.rc script / boot.img patch. But might be that it get's fixed with v7 anyway, hope @topjohnwu is able to get it done quickly (or maybe has some ideas he how to debug it more, i didn't get an answer from him in the common, probably way too crowded magisk thread - goddamn pokemongo!)
Subscribing. Would like to get this working as well.
Edit: I've gone ahead and opened up a thread so it is easy to find: http://forum.xda-developers.com/axon-7/how-to/guide-installing-magisk-systemless-phhs-t3524270
We're up to Magisk V9 now and it still doesn't work. I'm almost certain it has to do with the execution of the patched boot.img, due to the write-protected /system partition. I finally got it working by using the the method in the guide I posted.

Help w tuten1000's Guide: Root + custom kernel + clean rom

In the last week I received my xperia x compact completely stock. First thing I do when I get a new phone before even activating it is root it. I was utilizing this guide to root my xperia x compact "Guide: Root + Custom Kernel + Clean rom + TA for X Compact" and I am stuck on the step where you are instructed to flash the modified XC-GenesisKernel-v1.04-nodrm kernel and SU. Flashing this kernel always results in a boot loop (Ive waited more then 30 minutes for it to resolve). I reflash the stock service exchange unit - 34.1.A.1.198 MM firmware to get back a functioning phone. The guide recommends:
"Run xperifirm and download the "service exchange unit - 34.1.A.1.198" firmware for posterity and latest rom for your region."
Am I supposed to use the most current nougat firmware for the following steps and only use the service exchange unit firmware if I need to downgrade to the lower original firmware? The thread for the XC-GenesisKernel states it is for nougat roms, which would explain a boot loop when I try to use the service exchange unit MM rom. Ideally Id like to stay on MM so that I can use xposed. Root and the phone being fully functional with no loss of camera and such is my main desire, xposed is secondary. I have a Backup TA of my DRM keys, the phone bootloader is unlocked, and I am looking for a little direction / clarification, any help in this respect is greatly appreciated.
Thanks
efaustus9 said:
help in this respect is greatly appreciated.
Click to expand...
Click to collapse
Click the first link in the guide and read it.
XperienceD said:
Click the first link in the guide and read it.
Click to expand...
Click to collapse
Thanks, I read through it and I see indeed the latest nougat firmware is what I should use in the later steps of tuten1000's guide and is the source of the boot loop I am experiencing.
If possible I would like to stay on marshmallow so I can used xposed framework. Are you aware of or can you recommend a kernel I can flash that will give me root, fingerprint, and use of most DRM functions while still on marshmallow.
Maybe you can try my guide using Magisk with full DRM, Xposed and root. But you need to flash back to MM first if you need Xposed.
https://forum.xda-developers.com/x-compact/how-to/android-pay-safety-net-rooted-unlocked-t3610342
itandy said:
Maybe you can try my guide using Magisk with full DRM, Xposed and root. But you need to flash back to MM first if you need Xposed.
https://forum.xda-developers.com/x-compact/how-to/android-pay-safety-net-rooted-unlocked-t3610342
Click to expand...
Click to collapse
Excellent itandy, this this just what I had in mind. I never downloaded and flashed a nougat rom as xposed was important to me. In following tuten1000's guide I did flash the XC genesis kernel as well as SU in recovery. This resulted in a boot loop but a prerequisite in your guide is a /system partition without any trace of su. Since I reflashed the stock service exchange unit 34.1.A.1.198 MM firmware I should be good to proceed right?
efaustus9 said:
Excellent itandy, this this just what I had in mind. I never downloaded and flashed a nougat rom as xposed was important to me. In following tuten1000's guide I did flash the XC genesis kernel as well as SU in recovery. This resulted in a boot loop but a prerequisite in your guide is a /system partition without any trace of su. Since I reflashed the stock service exchange unit 34.1.A.1.198 MM firmware I should be good to proceed right?
Click to expand...
Click to collapse
You're all good to begin with MM stock ROM.
itandy said:
You're all good to begin with MM stock ROM.
Click to expand...
Click to collapse
It worked beautifully, thank you so much itandy :victory:
Anyway to get rid of the device is not secure screen on boot?
efaustus9 said:
It worked beautifully, thank you so much itandy :victory:
Anyway to get rid of the device is not secure screen on boot?
Click to expand...
Click to collapse
This is a common request but the answer is no.
itandy said:
This is a common request but the answer is no.
Click to expand...
Click to collapse
Okay, it would be nice to be rid of but it is a worthwhile trade off.
In your guide you mention a safety net, and installing xposed breaks it. What is this safety net and what is the draw back to breaking it? Am I locked out of certain apps or functions?
efaustus9 said:
Okay, it would be nice to be rid of but it is a worthwhile trade off.
In your guide you mention a safety net, and installing xposed breaks it. What is this safety net and what is the draw back to breaking it? Am I locked out of certain apps or functions?
Click to expand...
Click to collapse
SafetyNet is the security checking API used by some apps like Android Pay and Pokemon Go to make sure your device is not tampered with. Simply put it makes sure your device is stock, not unlocked, rooted or modified. Magisk currently is able to bypass SafetyNet checking for root and some other "unwanted" apps. But Xposed will still be detected because it works in much lower system level. And with Magisk you can simply disable Xposed temporarily and reboot if you want to use, say, Android Pay.
itandy said:
SafetyNet is the security checking API used by some apps like Android Pay and Pokemon Go to make sure your device is not tampered with. Simply put it makes sure your device is stock, not unlocked, rooted or modified. Magisk currently is able to bypass SafetyNet checking for root and some other "unwanted" apps. But Xposed will still be detected because it works in much lower system level. And with Magisk you can simply disable Xposed temporarily and reboot if you want to use, say, Android Pay.
Click to expand...
Click to collapse
ah very informative, thanks again.
I installed the xposed framework SDK23 in Magisk manager, it is showing up as installed under modules in magisk but xposed is not in the app drawer and I cant seem to access it.
efaustus9 said:
ah very informative, thanks again.
I installed the xposed framework SDK23 in Magisk manager, it is showing up as installed under modules in magisk but xposed is not in the app drawer and I cant seem to access it.
Click to expand...
Click to collapse
You need to install Xposed Installer separately. Try this unofficial app.
https://forum.xda-developers.com/xposed/material-design-xposed-installer-t3137758
itandy said:
You need to install Xposed Installer separately. Try this unofficial app.
https://forum.xda-developers.com/xposed/material-design-xposed-installer-t3137758
Click to expand...
Click to collapse
Haha once again you come through. You are really helping me get this all sorted with so little fuss, I am very grateful.
This is my first xperia experience, I am coming from a samsung s3 running a KK slimrom and things are a bit different on this device. Any other pointers or recommendations for this new phone? Is there a way to make the soft key bar transparent so I can actually utilize the full 4.6"?
efaustus9 said:
Haha once again you come through. You are really helping me get this all sorted with so little fuss, I am very grateful.
This is my first xperia experience, I am coming from a samsung s3 running a KK slimrom and things are a bit different on this device. Any other pointers or recommendations for this new phone? Is there a way to make the soft key bar transparent so I can actually utilize the full 4.6"?
Click to expand...
Click to collapse
I remember there're mods (maybe Xposed modules) to make the navbar autohide. Maybe you'd also like to check out my navbar Xposed module. See my signature.
itandy said:
I remember there're mods (maybe Xposed modules) to make the navbar autohide. Maybe you'd also like to check out my navbar Xposed module. See my signature.
Click to expand...
Click to collapse
Great, I will definitely check out your app. Ideally Id like to mimic what I believe is called the "immersive mode" in supported apps. In this mode the app takes up the full screen and the icons are replaced with three persistent minimal dots.

play fortnite with custom ROM/Rooted

Here's how to play fortnite with custom ROM and/or root.
Works for me Galaxy S8 G950F.
1 - disable usb debugging in developer options.
2 - Download and install Fortnite installer and Fortnite app.
3 - Enable magisk hide and hide fortnite app.
4 - Magisk manager settings and select hide magisk manager.
5 - Reboot and enjoy.
If these steps don't work for you then do this.
6 - You have to delete the following folder then do the steps in OP.
/storage/emulated/0/MagiskManager
Thanks to @ashabraja2 for letting me know about this.
callumbr1 said:
Here's how to play fortnite with custom ROM and/or root.
Works for me Galaxy S8 G950F.
1 - disable usb debugging in developer options.
2 - Download and install Fortnite installer and Fortnite app.
3 - Enable magisk hide and hide fortnite app.
4 - Magisk manager settings and select hide magisk manager.
5 - Reboot and enjoy.
Click to expand...
Click to collapse
It works! Thx
Sent from my Samsung Galaxy S8+ using XDA Labs
callumbr1 said:
Here's how to play fortnite with custom ROM and/or root.
Works for me Galaxy S8 G950F.
1 - disable usb debugging in developer options.
2 - Download and install Fortnite installer and Fortnite app.
3 - Enable magisk hide and hide fortnite app.
4 - Magisk manager settings and select hide magisk manager.
5 - Reboot and enjoy.
Click to expand...
Click to collapse
I tried this on S9 LightROM and it doesn't work for me. It just kicks me out of the game after jumping from the bus. What ROM are you running?
ashabraja2 said:
I tried this on S9 LightROM and it doesn't work for me. It just kicks me out of the game after jumping from the bus. What ROM are you running?
Click to expand...
Click to collapse
Renovate ROM. Did you hide the magisk manager also? In magisk settings?
callumbr1 said:
Renovate ROM. Did you hide the magisk manager also? In magisk settings?
Click to expand...
Click to collapse
Yes, I even used Magisk core on top. Still getting kicked. I'll try RiCE ROM then.
ashabraja2 said:
Yes, I even used Magisk core on top. Still getting kicked. I'll try RiCE ROM then.
Click to expand...
Click to collapse
It shouldn't matter about the ROM it's magisk. Try disabling OEM unlock also. For me the exact steps above work perfect.
callumbr1 said:
It shouldn't matter about the ROM it's magisk. Try disabling OEM unlock also. For me the exact steps above work perfect.
Click to expand...
Click to collapse
But if I disable OEM unlock, my phone can't get past the "Galaxy S8" splash screen. I had to reflash the stock firmware, which is not an option since I'll be out of town for a few days with no PC at hand.
ashabraja2 said:
But if I disable OEM unlock, my phone can't get past the "Galaxy S8" splash screen. I had to reflash the stock firmware, which is not an option since I'll be out of town for a few days with no PC at hand.
Click to expand...
Click to collapse
Ahh yes I see, strange. All the steps work for me and others. Ask in lightrom telegram group? Maybe yash can help
callumbr1 said:
Ahh yes I see, strange. All the steps work for me and others. Ask in lightrom telegram group? Maybe yash can help
Click to expand...
Click to collapse
I've flashed Renovate Ice on my phone and have tried all the steps you listed in OP. Does Fortnite check Knox 0x1 by any chance? (Renovate Ice does not have an OEM unlock option)
ashabraja2 said:
I've flashed Renovate Ice on my phone and have tried all the steps you listed in OP. Does Fortnite check Knox 0x1 by any chance? (Renovate Ice does not have an OEM unlock option)
Click to expand...
Click to collapse
OEM unlock should be optional. Fortnite only checks for adb and it uses safety net. So long as magisk the apk is hidden (in magisk settings) and Fortnite is hidden (magisk hide) it should work for you also. There is a file you can edit to bring the OEM toggle back if you wanna try that
just delete magiskmanager folder .....will surely work give it a reboot
callumbr1 said:
OEM unlock should be optional. Fortnite only checks for adb and it uses safety net. So long as magisk the apk is hidden (in magisk settings) and Fortnite is hidden (magisk hide) it should work for you also. There is a file you can edit to bring the OEM toggle back if you wanna try that
Click to expand...
Click to collapse
So I've figured it out, and I'll leave this here incase anyone else reads this. You have to delete the following folder then do the steps in OP.
/storage/emulated/0/MagiskManager
Thanks for the help man, appreciate it.
ashabraja2 said:
So I've figured it out, and I'll leave this here incase anyone else reads this. You have to delete the following folder then do the steps in OP.
/storage/emulated/0/MagiskManager
Thanks for the help man, appreciate it.
Click to expand...
Click to collapse
Thanks buddy I'll add to OP
s9 port rom with su install no magisk. any one?
mtayabkk said:
s9 port rom with su install no magisk. any one?
Click to expand...
Click to collapse
Need magisk, for magisk hide
Hey, I am using Cherish OS with no magisk but still I cannot get into the game
I haven't flashed magisk yet and my usb debugging is also on
jeet2114 said:
Hey, I am using Cherish OS with no magisk but still I cannot get into the game
I haven't flashed magisk yet and my usb debugging is also on
Click to expand...
Click to collapse
Try installing magisk and use magisk hide to hide fortnite then hide magisk apk

OP8P lost my fingerprint will next OTA fix it back?

Question. My device did an OTA from Android 11 to 12 in doing so, I lost root. I bricked my phone trying to root again using the wrong boot.img until I found the correct boot.img and rooted it. In doing so in the process, it must have killed something once I fixed it, I lost my fingerprint reader.
US OP8P (rooted with Magisk) on C.21 fingerprint reader not working. If I wait for the next full stable update using OTA Magisk root method to regain root back....will that fix the fingerprint reader or the presistent.img partition without me having to wipe my device and start over?
I have no error messages it just does not work but it did just before I flashed the wrong boot.img and went into a boot loop. Again, boot loop fixed using the right C.21 boot.img no fingerprint.
I really want it back, but I do want to do a full wipe since I travel so much and need my phone.
Help or advice on the question. Please?
Please list out what Module are you using in your Magisk.
Note, it's a known problem if you're using outdated USNF module it will broke fingerprint. i don't use USNF and it's fine.
addition: if you're not using USNF and it's still broke. you can try the guide on how to restoring the fingerprint to work again. there's a guide in here. please search it first and try.
dewa5227 said:
Please list out what Module are you using in your Magisk.
Note, it's a known problem if you're using outdated USNF module it will broke fingerprint. i don't use USNF and it's fine.
addition: if you're not using USNF and it's still broke. you can try the guide on how to restoring the fingerprint to work again. there's a guide in here. please search it first and try.
Click to expand...
Click to collapse
I have not looked in here earlier I did a google search I found something related to an MSN program or something like that to downgrade and fix, but it is was a full wipe....was hoping not to do that. Is that what you are referring to it is a different fix?
Magisk Modules I have on 12 which is the same on Android 11:
Call Record - SKVALEX
Dialer Framework for Google Phone
Systemless Hosts
Universal SafetyNet Fix
Zygisk - LSPosed
dewa5227 said:
Please list out what Module are you using in your Magisk.
Note, it's a known problem if you're using outdated USNF module it will broke fingerprint. i don't use USNF and it's fine.
addition: if you're not using USNF and it's still broke. you can try the guide on how to restoring the fingerprint to work again. there's a guide in here. please search it first and try.
Click to expand...
Click to collapse
Also what is USNF what does that mean? Thx
parcou said:
I have not looked in here earlier I did a google search I found something related to an MSN program or something like that to downgrade and fix, but it is was a full wipe....was hoping not to do that. Is that what you are referring to it is a different fix?
Magisk Modules I have on 12 which is the same on Android 11:
Call Record - SKVALEX
Dialer Framework for Google Phone
Systemless Hosts
Universal SafetyNet Fix
Zygisk - LSPosed
Click to expand...
Click to collapse
It was the Universal Safety Net Fix (USNF)
dewa5227 said:
It was the Universal Safety Net Fix (USNF)
Click to expand...
Click to collapse
Thank you....
Found it, and this fix worked. Much appreciated the assistance, and pointing me in the right direction!!
Magisk Module for ColorOS​
GitHub - wuxianlin/ColorOSMagisk: Magisk Module for ColorOS
Magisk Module for ColorOS. Contribute to wuxianlin/ColorOSMagisk development by creating an account on GitHub.
github.com

Categories

Resources