First of all i want to know how can i Stay encrypted and Install magisk 13.3 ?
currently i'm using SuperSU 2.82 SR3,My data is decrypted.
Rom:C185B184
Google Play: Uncertified
Last night,i've tried Suhide,and i couldnt pass ctsProfile...
and also Suhide has some bugs,like u cant uninstall any app when its activated and u cant Deactivate Suhide,unless u do full unroot.
And Also how can install Viper4Android's Driver Using SuperSU ?
Flash this for Magisk 13.3: https://mega.nz/#!I4FQzbyA!gBZelHmD3lGGwzGISUXkf7GQTUAq5i785d_qPHQOaVE
Or 13.5: https://mega.nz/#!V8EXRRoB!Dlv4gxa7smUhnacjVzHRVemLtZtKKTBfdQ5z0NhCQwY
Though you say you are decrypted now, flashing 13.3 or 13.5 will re-encrypt your /data.
If you want to stay decrypted, flash official 13.3 or 13.5.
Flash back your stock B184 boot image first.
As for SafetyNet, the build you're using is a beta, and pretty recent so it may not be approved by Google (and since beta it might not be approved later either). The even more recent build for your model is B186, and that's definitely not approved yet (released 14th of August).
You should be able to install V4A if you set selinux for permissive. Or you can flash this: https://mega.nz/#!J1FyiSLT!WQVsJ3DWNq3l-HDKcg06ISB4J5COpdabR8Q36A_R_LE
Or if you switch to Magisk there's a V4A module for it in Magisk Manager - Downloads.
i've installed B186 and its certified.
so can tell me how to install magisk on a fresh rom ? 0- 100
cause i've tried this before and i've faced bootloop !
Safetynet Problem
So I've figured it out until u don't unlock bootloader, u can pass safetynet without any problems.
Once I've unlocked my bootloader, I've got CTS Profile error...
Plus I'll get random FC since upgraded to B184 using Hwota method!
I'm on B186 right now and I've got FC again in chrome during this reply :laugh:
Update!
Help me @ante0
ezraiil1 said:
So I've figured it out until u don't unlock bootloader, u can pass safetynet without any problems.
Once I've unlocked my bootloader, I've got CTS Profile error...
Plus I'll get random FC since upgraded to B184 using Hwota method!
I'm on B186 right now and I've got FC again in chrome during this reply :laugh:
Click to expand...
Click to collapse
Did it pass CTS and basic on B186 before flashing magisk?
The FC, does apps close suddenly without warning? If so I think it's something else because it happens to me too on C432 B194. Same for people on c636 B188.
Could be the phone manager that's too strict.
ante0 said:
Did it pass CTS and basic on B186 before flashing magisk?
The FC, does apps close suddenly without warning? If so I think it's something else because it happens to me too on C432 B194. Same for people on c636 B188.
Could be the phone manager that's too strict.
Click to expand...
Click to collapse
Yes,I've Tried it before unlocking bootloader and it passed successfully ,and google play Status was certified too.
before installing magisk,right after i unlockd bootloader!
and then i install magisk and tried again,then both basic integrity and CTS profile failed.
Yes,Sometimes when u r using apps,they suddenly close and jump into app drawer,and when i open them again they start over.
(like chrome,Clash royale,Last Day on earth,Instagram...)
ezraiil1 said:
Yes,I've Tried it before unlocking bootloader and it passed successfully ,and google play Status was certified too.
before installing magisk,right after i unlockd bootloader!
and then i install magisk and tried again,then both basic integrity and CTS profile failed.
Yes,Sometimes when u r using apps,they suddenly close and jump into app drawer,and when i open them again they start over.
(like chrome,Clash royale,Last Day on earth,Instagram...)
Click to expand...
Click to collapse
Is magisk hide enabled in Magisk Manager? If not, check log in Manager to see if it tried to enable. Else try enabling USB debugging and disable then enable Magisk hide.
If it enables after that you're in the same boat as the rest of us. Mine actually worked flawlessly for a week or so, then I had to keep enabling USB debugging to get it running....
Not sure of it's intentional by Huawei that USB debugging gets disabled. Same goes for adb, have to enable USB debugging after each reboot to get it running. I guess a Tasker script could be made to enable it, and disable/enable magiskhide at boot.
I rooted my mate 9 l09c432 with magisk and everything was working fine safetyNet check returned a pass, however in magisk hide option I clicked FUSED LOCATION, after which CTS and Basic-integrity shows false, I've tried everything from complete uninstall to removing any remnants of root in system files and also re-rooted however its still saying false on both of those things.
Google play store says device uncertified now, can anyone help? Other than that root is working I'd just rather try fix this issue now instead of it coming back to bite me later.
Cheers
device info: xiaomi mi8 lite, unlocked bootloader, magisk root, twrp, android 10, passed safetyNet
I installed Smali Patcher and my gps completely stopped working. My real location doesn't show on google maps or any other apps that use gps. Enabling google map accuracy doesnt work either, as well as enabling/disabling mock location. Is there anything I can do? It worked completely fine before installing smali patcher. I also tried disabling smali module in magisk but nothing changed.
Not so long ago I uninstalled smali patcher module through twrp and problem still occurs
Reflash phone's Stock ROM to get rid off of all modifications you applied so far.
I flashed lineageOS and location still doesn't work... I have no clue why. I wiped everything.
jwoegerbauer said:
Reflash phone's Stock ROM to get rid off of all modifications you applied so far.
Click to expand...
Click to collapse
so I flashed my stock rom (miui) and it's working now
Idk why it didnt work with lineageos
Hi people!
For some reason face unlock stopped working with root after updating to OOS 11 stable. I manually updated to OOS 11, but without root face unlock works fine on 11.
I've tried cleaning storage for the face unlock app, removing the face data to add again (if rooted, the process gets stuck at around 75% of face scan and says 'face not recognize' or something along those lines.
If I remove magisk, face unlock works fine, like I don't even have to re add the face or anything, it just works. And I already added face unlock to magisk hide but with no effect.
Have any of you encounter this problem? Back in OOS 10, face unlock worked fine with Magisk. Last resort is to try a clean OOS 11 install but I'm hoping to find a solution before trying that.
hmbto said:
Hi people!
For some reason face unlock stopped working with root after updating to OOS 11 stable. I manually updated to OOS 11, but without root face unlock works fine on 11.
I've tried cleaning storage for the face unlock app, removing the face data to add again (if rooted, the process gets stuck at around 75% of face scan and says 'face not recognize' or something along those lines.
If I remove magisk, face unlock works fine, like I don't even have to re add the face or anything, it just works. And I already added face unlock to magisk hide but with no effect.
Have any of you encounter this problem? Back in OOS 10, face unlock worked fine with Magisk. Last resort is to try a clean OOS 11 install but I'm hoping to find a solution before trying that.
Click to expand...
Click to collapse
It is weird, i used OOS11 stable with and without root and none seems to encounter this problem. Assume to be a glitch due to some other apps. I can only suggest to take a backup first and do a clean install by erasing your internal storage and reinstalling OOS11 and rooting it. Hope it helps.
So the latest 31.0810.1226.77-1.1.138-2203 update has introduced Android 12..and killed Safetynet bypass. The kdragon Safetynet fix 2.2.1 no longer works and the device doesn't pass basic attestation either. Is there a workaround that doesn't involve unrooting it or are we ****ed for the time being? Goddamn Magisk had to deprecate their Magiskhide and safetynet bypass features. /rant
Just re-flash magisk should be enough. Else re-flash safetynet-fix-v2.2.1.zip after magisk.
course if you havent got TWRP installed you would have to re-flash the boot.img to get magisk working again.
I usually do that after every firmware update, reflashing the patched boot.img, and I already had the latest kdrag0n safetynet fix (2.2.1 as of now). This time after restarting on android 12, safety net failed and the Google pay app reported that my device is no longer certified. Guess I'll try again. Wait..is there finally now a TWRP for ROG 5? I miss using it from my old 1+3.
Edit - didn't work.
There is no TWRP for A12.
You will have to make a new patched boot image for A12. Go to Magisk and patch boot.img taken from Payload.bin (Payload dunper required) and flash it. That will get you root back.
Then you can use the universal safety net fix zip inside magisk.
BakaValen said:
Then you can use the universal safety net fix zip inside magisk.
Click to expand...
Click to collapse
Getting root on 12 is not the problem. The kdrag0n safetynet fix stopped working after upgrading to 12. I have the latest Zygisk version 2.2.1 that was updated last December.
I am on A12 latest. Rooted with safetynet passed using the fix. You must be doing something wrong.
Explain your process
Did the same process I've followed for every system update - patch boot.img with the payload dumper and patch script as described in this forum before applying the update, and flash it afterwards. The safetynet fix that had already been installed and working under 11 stopped, and removing and reapplying it does nothing.
Flash version 2.2.1.
I'm telling you. There is a process not being done correctly.
I'm on the latest A12 for the 5s with safetynet pass.
Send screenshots of install process (magisk black screen bit)
BakaValen said:
Flash version 2.2.1.
I'm telling you. There is a process not being done correctly.
I'm on the latest A12 for the 5s with safetynet pass.
Send screenshots of install process (magisk black screen bit)
Click to expand...
Click to collapse
Yes, I'm using 2.2.1. The flashing process appears to have worked, as shown -
It's the latest Magisk with zygisk enabled. FWIW here's the result of running safetynet test also.
KaiserSnorezay said:
Yes, I'm using 2.2.1. The flashing process appears to have worked, as shown -
It's the latest Magisk with zygisk enabled. FWIW here's the result of running safetynet test also.
Click to expand...
Click to collapse
Are you running Shamiko withLSPosed/Xprivacy + blocking tracking for Goog Play Services and the relevant apps? Safetynetfix 2.2.1 alone is no longer a full solution whether you're on A11 or A12 and regardless of your Magisk version...
If you mean adding play services to the deny list, then yes. Got rid of xprivacylua as it didn't help. Used it to block reading identifiers and tracking for play services and other components, to no avail. Right now even the basic integrity test is failing.
Update - Installed Shamiko, disabled the 'enforce denylist' in Magisk so that it takes over the job and rebooted..and nothing different.
Passed here just fine... all you need is a clean magisk install, then...
hide the magisk app itself.
enable zygisk, reboot.
flash zygisk version of usf https://github.com/kdrag0n/safetynet-fix/releases/tag/v2.2.1
optionally: flash shamiko, reboot, then select play store and play service in deny list without enabling it.
check again in YASNAC, should pass now.
Don't know WTF is wrong this time, compared to every previous time it would just simply upgrade with no problems.
Installed this month's system update.
Uninstalled Magisk.
Patched the boot.img with Magisk, flashed it.
Reinstalled the Magisk apk. It was rooted, all my settings and modules showed up as usual.
Toggled zygisk to off, just to be sure, restarted, turned it back on, restarted.
NOTHING. Again the ****ing Safetynet fails.
KaiserSnorezay said:
Don't know WTF is wrong this time, compared to every previous time it would just simply upgrade with no problems.
Installed this month's system update.
Uninstalled Magisk.
Patched the boot.img with Magisk, flashed it.
Reinstalled the Magisk apk. It was rooted, all my settings and modules showed up as usual.
Toggled zygisk to off, just to be sure, restarted, turned it back on, restarted.
NOTHING. Again the ****ing Safetynet fails.
Click to expand...
Click to collapse
Google changed something today, as Google Pay now detects root when I had used it just yesterday without issue. It appears the safetynet fix needs fixing.
Strephon Alkhalikoi said:
Google changed something today, as Google Pay now detects root when I had used it just yesterday without issue. It appears the safetynet fix needs fixing.
Click to expand...
Click to collapse
Re-check that all GPay sub components are added to your Shamiko deny list and Shamiko configured properly (i.e with Magisk's own deny disabled). Also check and ensure that tracking is blocked for Gpay in Xprivacy.
If you don't have any one of those installed - you need it to be completely covered. Even if you pass Saftynet. Safetynet Fix and Magisk hide alone won't cut it, at least not currently. Tough apps like banking and payment apps will detect you.
Many people skip one or more of these and run into frustration with root detection..
I noticed that if I add Google play services (all components) to the Magisk deny list, it doesn't persist after reboot. Could that be it? Is it unable to modify the system partition? I'm using Shamiko, with Magisk enforce deny list option disabled.
Andrologic said:
Re-check that all GPay sub components are added to your Shamiko deny list and Shamiko configured properly (i.e with Magisk's own deny disabled). Also check and ensure that tracking is blocked for Gpay in Xprivacy.
If you don't have any one of those installed - you need it to be completely covered. Even if you pass Saftynet. Safetynet Fix and Magisk hide alone won't cut it, at least not currently. Tough apps like banking and payment apps will detect you.
Many people skip one or more of these and run into frustration with root detection..
Click to expand...
Click to collapse
It may be a glitch, as GPay is currently not complaining about root when I pull up one of my stored cards. Regardless, I don't have Shamiko installed, but will look into it so long as it doesn't require Xposed or any of its derivatives.
EDIT: Confirmed to be a glitch. Not more than five minutes prior to this edit I used GPay without trouble.
Did some more testing, given I had to install the latest June firmware anyway. Fully removed Magisk (I hadn't done this earlier) and reinstalled, it passes. The culprit for failure turned out to be LSPosed. When enabled, it fails SafetyNet. I can manage without it but if anyone knows a workaround please do tell.
KaiserSnorezay said:
Did some more testing, given I had to install the latest June firmware anyway. Fully removed Magisk (I hadn't done this earlier) and reinstalled, it passes. The culprit for failure turned out to be LSPosed. When enabled, it fails SafetyNet. I can manage without it but if anyone knows a workaround please do tell.
Click to expand...
Click to collapse
Same boat here. I got safetynet fix passed literally right after I disabled LSPosed. I glimpsed through the issues in LSPosed Github repo but they don't seem to be working on this.
I dont have any issues with safetynet.