Related
Steps:
1. Download Magisk V11.1 & uninstaller
2. Root device (use @rrvuhpg root guide)
3. Download and flash Systemless SuperSU
4. Reboot and fully unroot device (don't restore stock boot image)
5. Reboot
6. Reboot into recovery
7. Flash Magisk & reboot
8. Wait for device to reboot fully (it takes a long, long time)
9. Download Magisk Manager from Play Store
10. If root is there, then you're done
Alternate Method:
1. Root Device (use @rrvuhpg root guide)
2. Download and flash Systemless SuperSU
3. Reboot and install Magisk Manager from Play Store
4. Open Magisk Manager and go onto the install tab
5. Press "detect" on the boot image location section and press "Magiskify" (I kept both advanced options unchecked)
6. Once flashed and rebooted, you're done.
Notes:
1. Rebooting after flashing Magisk takes ages, if there is a problem with booting then just flash the Magisk uninstaller. Just try to wait at least 10 minutes for the reboot after flashing Magisk, just don't crap yourself and uninstall the Magisk.
If you have questions or need help, just ask.
is this for single or dual sim XA??
caosugai said:
is this for single or dual sim XA??
Click to expand...
Click to collapse
For all XA and Ultra
rrvuhpg said:
For all XA and Ultra
Click to expand...
Click to collapse
Did it work for you then?
BadmanBristow said:
Did it work for you then?
Click to expand...
Click to collapse
No problem for me on F3112 with Magisk 11.1 and SuperSu 2.79 on 33.2.B.3.105 firmware. Only SafetyNet fail (CTS profil mismatch).
rrvuhpg said:
No problem for me on F3112 with Magisk 11.1 and SuperSu 2.79 on 33.2.B.3.105 firmware. Only SafetyNet fail (CTS profil mismatch).
Click to expand...
Click to collapse
Use MagiskSU instead, fully unroot device with SuperSU but don't restore the boot.img etc. Go to recovery and use the Magisk uninstaller then reflash Magisk 11.1 and if you unrooted, then it will install MagiskSU. It is Magisk's new official root
rrvuhpg said:
No problem for me on F3112 with Magisk 11.1 and SuperSu 2.79 on 33.2.B.3.105 firmware. Only SafetyNet fail (CTS profil mismatch).
Click to expand...
Click to collapse
Also Systemless xposed causes safety net fail and you need to activate Magisk hide in the settings as well
BadmanBristow said:
Also Systemless xposed causes safety net fail and you need to activate Magisk hide in the settings as well
Click to expand...
Click to collapse
And selinuxmode needs to be enforcing but Magisk takes care of that itself so don't worry, just double check it's enforcing, Magisk will turn it permissive itself only when needed
BadmanBristow said:
And selinuxmode needs to be enforcing but Magisk takes care of that itself so don't worry, just double check it's enforcing, Magisk will turn it permissive itself only when needed
Click to expand...
Click to collapse
Thank you for your tips but XA is not my daily phone anymore, now I have a Oneplus3 and XA is just used as test/dev unit. I hope it will help other users.
Magisk should help with maintaining root after the latest and future Xperia XA updates (most likely will work with Nougat update too)
Android Pay
does this let you use android pay
jbenitez821 said:
does this let you use android pay
Click to expand...
Click to collapse
It does, but if you use systemless xposed, you will need to disable it and then it will work.
Thank you very much for this guide.
Can't I use just Magisk installer without unrooting the rom? If I'm not wrong Magisk has is own root manager
I tryed to install Camera 60fps Recording Module but i got error the zip is stored in : intenal storage ....
Is this safety net important to have it in green to pass this CTS ? I have done method 2. Magisk manager form store and then I installed Magisk 12. In installation panel when I tap detect it detecs (auto) mmcblk. Is it all ? Does it work ?
Where can I find the Systemless SuperSU?
I have been trying to change to Magisk with this guide but it failed in the 1st method, the 2nd one gives the root with super su but i wanted to use Magisk alone, so i have been researching and by flashing the stock boot.img (i used the one provided in the thread "Stock kernels built from sources") Magisk was installed and worked except for the SafetyNet. Do someone passes SafetyNet or have a suggestion?
Veniak04 said:
I have been trying to change to Magisk with this guide but it failed in the 1st method, the 2nd one gives the root with super su but i wanted to use Magisk alone, so i have been researching and by flashing the stock boot.img (i used the one provided in the thread "Stock kernels built from sources") Magisk was installed and worked except for the SafetyNet. Do someone passes SafetyNet or have a suggestion?
Click to expand...
Click to collapse
To pass the Safetynet check the only way is to use encrypted partition but you will lose the ability to mount/backup the /data partition with TWRP.
rrvuhpg said:
To pass the Safetynet check the only way is to use encrypted partition but you will lose the ability to mount/backup the /data partition with TWRP.
Click to expand...
Click to collapse
How can i encrypt it and why does it is an issue? I only want to have my phone rooted with Magisk passing SafetyNet
Hi All,
Been a root user for a few years, so i know the power of the typical root apps such as SU, Magisk and Xposed.
I was messing around last night an managed to find a way to get magisk fully installed on my phone and it passed the safety net ( see pictures). There are pictures to prove i have got magisk, Also there may be a easier method but this is what i used.
Ensure you are on RR as i have not tested.
Here is my method:
1. Download both attached files
2. Reboot to recovery
3.flash SU
4.Reboot
5. Once system loads open up SU app and go through the initial setup
6. reboot back into recovery
7.flash Pixel Magisk RC112
8. REBOOT
9. go into the SU app and into settings, scroll down to full uninstall and click thorough the popups and uninstall.
10. your phone will reboot and go into the magisk app and thank me.
Thanks for reading
EDIT: ALTERNATIVE METHOD BELOW:
How I got this on pn, elemental and flashing the right zip in the op was the key for me, the 2 zips in the first post of this thread
Install pn
Install TWRP
Reboot system
Reboot recovery, install elemental
Reboot to system
Reboot recovery install magisk sr3 zip one on op
Reboot system
Set up super su
Reboot recovery, flash rc112
Reboot system
Super su full unroot, check yes to both
Should reboot system
Open and set up magisk manager,
Go to settings and check hide magisk and systemlesd
Seems to work better on pn
This follows the first post of this thread works good for pn
If magisk manger doesn't show up in your launcher
Install https://github.com/topjohnwu/MagiskM...ger-v4.2.6.apk
CREDIT: mac796
Here's another way new rr already comes with magisk manager on it. Just wipe in TWRP, flash newest rr, reboot system once and then flash this experimental magisk zip in TWRP
https://www.androidfilehost.com/?fid=457095661767148610
Also when your done make sure to check hide magisk inside manager. And also if your a titanium backup user, you need to go to preferences, troubleshooting, check force busy box, and sq lite. That will make it work with new magisk root
Remember to check busy box in magisk manager app,
And give it a couple reboots, takes a bit to kick in.
Edit no longer have to do anything to get titanium backup to work, just check Magisk hide and systemless
Edit. Will work on big and small pixel
Edit updated new Magisk zip
Credit Goodwinc
Looks promising, will it works on pn rom or is it rr rom exclusive for now?
Sent from my Pixel using Tapatalk
ansontyl96 said:
Looks promising, will it works on pn rom or is it rr rom exclusive for now?
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Not sure I was taking to somebody last night who was trying it, he hasn't got back to me
Currently I'm using suhide, but I'll prefer magisk if it works since it's open source!
Sent from my Pixel using Tapatalk
ansontyl96 said:
Currently I'm using suhide, but I'll prefer magisk if it works since it's open source!
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
At the very end of my method I had to reboot once to get it all working right.
For the full unroot part do I need to restore the boot and recovery img?
If I choose no it reboot with SuperSU app disappear but still rooted with SuperSU as shown in the magisk app
restore the boot and recovery, it should delete the app and no super su left on your device.
Awesome. Gonna try this out tomorrow morning.
Are there any other useful modules for magisk? I havent looked into them since it was in v6 or v7...
only thing i use is hide su or magisk
everything else seems irrelevant for me, but if you find something let me know.
Here is my procedure: I was on newest RR with ElementalX and SuperSU.
I followed these steps: recovery -> dirty flash RR and flash Elemental X, MAGISK experimental zip, TWRP zip -> reboot = No SuperSU but magisk root works and safety net check failed in Magisk -> go back to recovery -> flash Elemental X, MAGISK experimental zip, TWRP zip -> reboot, No SuperSU, magisk root works, safetynet passes, hide magisk from other apps in magisk setting -> profit (android pay, venmo, snapchat, all are working)
rohitece06 said:
Here is my procedure: I was on newest RR with ElementalX and SuperSU.
I followed these steps: recovery -> dirty flash RR and flash Elemental X, MAGISK experimental zip, TWRP zip -> reboot = No SuperSU but magisk root works and safety net check failed in Magisk -> go back to recovery -> flash Elemental X, MAGISK experimental zip, TWRP zip -> reboot, No SuperSU, magisk root works, safetynet passes, hide magisk from other apps in magisk setting -> profit (android pay, venmo, snapchat, all are working)
Click to expand...
Click to collapse
Good deal. I had to do a clean flash. You might end up with bugs
mac796 said:
Good deal. I had to do a clean flash. You might end up with bugs
Click to expand...
Click to collapse
thanks, i'll keep an eye out.
Anybody know whether this decrypts the Pixel? I don't have a Pixel yet so I can't test
http://www.theandroidsoul.com/disable-verity-force-encryption-pixel-xl-decrypt/
xdadevnube said:
Anybody know whether this decrypts the Pixel? I don't have a Pixel yet so I can't test
http://www.theandroidsoul.com/disable-verity-force-encryption-pixel-xl-decrypt/
Click to expand...
Click to collapse
I have not seen anyone say they have decrypted the phone, Magisk is just now working on a few roms. I wouldnt bother, this phone has the processor for decryption.
So I take it that even with this it is one or the other with regard to having root (su) working or safety net passing for Magisk. You cant have true SU where you can alter system/app folders with Magisk root, you need true super su. So if I use Magisk root it limits me a little bit. But if I dont I cant use stuff like android pay, LOL
mac796 said:
Here's another way new rr already comes with magisk manager on it. Just wipe in TWRP, flash newest rr, reboot system once and then flash this experimental magisk zip in TWRP https://drive.google.com/open?id=0B1xZ4VKT4JKZTnhTdGxDcWlkMXM.
Also when your done make sure to check hide magisk inside manager. And also if your a titanium backup user, you need to go to preferences, troubleshooting, check force busy box, and sq lite. That will make it work with new magisk root
Edit. Will work on big and small pixel
Click to expand...
Click to collapse
Thank you, worked like a charm on my regular pixel with RR.
jawonder said:
Thank you, worked like a charm on my regular pixel with RR.
Click to expand...
Click to collapse
That's great. I'm trying to get a hold of another guy that said he got it to work on pn. I tried but ended up having to start over and flash stock. I'll tell u this if you haven't tried restoring a backup with rc2, don't, it caused all kinds of problems. I went back to rc1.
I can't get Titanium Backup to work . I did check "force busybody and SQlite" in Troublshoot settings,
jawonder said:
I can't get Titanium Backup to work . I did check "force busybody and SQlite" in Troublshoot settings,
Click to expand...
Click to collapse
You might have to reboot once, and I uninstalled and reinstalled it. It works. I even used it to back to my stuff after rc2 took it all away lol
---------- Post added at 09:29 PM ---------- Previous post was at 09:26 PM ----------
jawonder said:
I can't get Titanium Backup to work . I did check "force busybody and SQlite" in Troublshoot settings,
Click to expand...
Click to collapse
Make sure and enable busy box inside magisk manager settings. That might do the trick and I installed busy box like normal to, not sure if I had to, I think it might be built in to that app
I can confirm that Magisk v11.6 installs and appears to function perfectly on my stock, unrooted, bootloader unlocked MCG24.251-5-5 device. Also, MagiskHide is not enabled by default, so keep this in mind if you're using a work device or any other situation where you might get in trouble for failing safetynet. That's all I know so far.
Go forth and Magisk!!!
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Pics or it didn't happen
And last, but certainly not least...
So I can root without unlocking the bootloader using sunshine?
Sparksys said:
So I can root without unlocking the bootloader using sunshine?
Click to expand...
Click to collapse
No.
Sparksys said:
So I can root without unlocking the bootloader using sunshine?
Click to expand...
Click to collapse
No. Sunshine unlocks your bootloader, so you can then root.
Sparksys said:
So I can root without unlocking the bootloader using sunshine?
Click to expand...
Click to collapse
There will never be a free root for this device unless you develop it, so you can save yourself the time asking in so many different threads.
Can anyone tell me where you get the "magiskSU" app from I can't find it in that thread.
Tokogon said:
Can anyone tell me where you get the "magiskSU" app from I can't find it in that thread.
Click to expand...
Click to collapse
MagicSU is included with the Magisk package. You can enable or disable it using the Magisk Manager app once it is installed.
TheSt33v said:
MagicSU is included with the Magisk package. You can enable or disable it using the Magisk Manager app once it is installed.
Click to expand...
Click to collapse
Do you have a screenshot of where I can find it in settings? I've been searching for an hour and I've reset my phone twice and installed it but can't see it lol.
I want to play Pokemon Go so bad again.
Tokogon said:
Do you have a screenshot of where I can find it in settings? I've been searching for an hour and I've reset my phone twice and installed it but can't see it lol.
I want to play Pokemon Go so bad again.
Click to expand...
Click to collapse
Sorry, I was wrong about being able to disable it. There doesn't seem to be an option for that. But as long as Magisk Hide is enabled, Pokémon Go works fine for me.
More complicated question:
If I'm rooted via Computerfreek's debloated stock ROM, is there any point to running Magisk--and if so, how would I switch from SuperSU to MagicSU
y8s said:
More complicated question:
If I'm rooted via Computerfreek's debloated stock ROM, is there any point to running Magisk--and if so, how would I switch from SuperSU to MagicSU
Click to expand...
Click to collapse
The only advantage gained would be the ability to pass safetynet/use Android Pay/play pokemon go while rooted. To switch, uninstall SuperSU by selecting the full unroot option in the SuperSU app, then flash Magisk.
TheSt33v said:
The only advantage gained would be the ability to pass safetynet/use Android Pay/play pokemon go while rooted. To switch, uninstall SuperSU by selecting the full unroot option in the SuperSU app, then flash Magisk.
Click to expand...
Click to collapse
It's mostly for intellectual curiosity and maybe android pay.
But it didn't work--at least how I went about it.
I went into SuperSU and did a full unroot but did not restore the boot image (should I have?)
Then downloaded and flashed the latest 11.6 magisk
When the phone came back up, SU was gone but Magisk didn't re-root it. There were no options to do so.
Tried a second time and wiped caches but no change.
I'm going to go out on a limb and guess that Magisk needs the OG boot image to work properly?
y8s said:
It's mostly for intellectual curiosity and maybe android pay.
But it didn't work--at least how I went about it.
I went into SuperSU and did a full unroot but did not restore the boot image (should I have?)
Then downloaded and flashed the latest 11.6 magisk
When the phone came back up, SU was gone but Magisk didn't re-root it. There were no options to do so.
Tried a second time and wiped caches but no change.
I'm going to go out on a limb and guess that Magisk needs the OG boot image to work properly?
Click to expand...
Click to collapse
I installed it on stock MCG24.251-5-5 and Superuser is an option that appears in Magisk Manager. Yes, you should probably have the stock boot image before installing Magisk. I think the Magisk installer is designed to detect existing installations of SuperSU and not install its own superuser if it's detected, so if the full unroot didn't clean itself up properly for whatever reason, that might be why it didn't install with superuser.
It says:
...
-(Recommended) Restore your boot image back to stock
-Download the latest Magisk zip file
-If you choose to use SuperSU (only support Android 6.0+), first flash SuperSU in systemless mode
...
Which zip of super su should I flash therefore before flashing magisk zip?
I am currently, after restoring a backup, running your MGC stock with stock kernel, but I try installing bhb27s kernel now.
Ultimately I simply want to hide root+xPosed against my banking app...
€DIT: Wait, so SuperSUB may not be necessary, but is it safe to install magisk over bhb27s kernel?
I would do the following:
-Install newest v44 kernel from March, 12
-Reboot and look if Wi-Fi still works ...
-install Magisk 11.6
-Check if phone still works
-then install a working xposed
-Check if everything works
Is that correct or should I use another kernel version? I don't want another bootloop or damaged wifi^^
Einheit-101 said:
It says:
...
-(Recommended) Restore your boot image back to stock
-Download the latest Magisk zip file
-If you choose to use SuperSU (only support Android 6.0+), first flash SuperSU in systemless mode
...
Which zip of super su should I flash therefore before flashing magisk zip?
I am currently, after restoring a backup, running your MGC stock with stock kernel, but I try installing bhb27s kernel now.
Ultimately I simply want to hide root+xPosed against my banking app...
€DIT: Wait, so SuperSUB may not be necessary, but is it safe to install magisk over bhb27s kernel?
I would do the following:
-Install newest v44 kernel from March, 12
-Reboot and look if Wi-Fi still works ...
-install Magisk 11.6
-Check if phone still works
-then install a working xposed
-Check if everything works
Click to expand...
Click to collapse
I don't see any problems with that plan, but you should know that xposed will insta-fail safetynet. If you want to hide modifications from anything that uses safetynet, xposed in any form is not an option. The only thing that works for me is Magisk 11.6's built in root, no xposed, no other modifications. With that, I can use Android Pay, Pokemon Go and my banking apps just fine as long as Magisk Hide is turned on. Android Pay and PoGo are blocked by default, but you need to make sure to go in and manually check the box next to every other app that you want to hide stuff from.
Also, if you insist on using SuperSU instead of the built in Magisk root (why???), you will also have to install the latest version of suhide (and I'm not positive that works anymore).
.I did not exactly know Super SU is just an option so I will not install it. Wish me luck
Also I hope there will be a way to hide xPosed however my banking app does not use SafetyNet, there is still hope, I don't care about Pokemon Go.
€DIT::: Everything working perfect - however safetynet fails when checking with Magisks own test. I guess it detects the Bootloader?
€DIT2::: Now after another reboot safetynet is successfully bypassed. My banking app still doesn't work - looks like they found a way that is even better than safetynet.
I just haven't had time to dig up another boot.img and flash it. I might revert back to SuperSU and come back to this later.
Einheit-101 said:
.I did not exactly know Super SU is just an option so I will not install it. Wish me luck
Also I hope there will be a way to hide xPosed however my banking app does not use SafetyNet, there is still hope, I don't care about Pokemon Go.
€DIT::: Everything working perfect - however safetynet fails when checking with Magisks own test. I guess it detects the Bootloader?
€DIT2::: Now after another reboot safetynet is successfully bypassed. My banking app still doesn't work - looks like they found a way that is even better than safetynet.
Click to expand...
Click to collapse
Try clearing the data for your banking app. Maybe it's set up so that once it fails, it never checks again. Also, clear cache/dalvik cache in TWRP if you haven't already. Also also, did you remember to block the banking app in magisk hide?
Hello,
i wanna hide root (because of Super Mario Run) and tried to install Magisk, but i get an installation error.
I have no idea if Magisk uses the correct partition, i also tried the boot0/boot1 partition, but no luck.
My P9 lite is running Nougat (VNS-L31C432B370)
Did anyone succeed in installing Magisk on the P9 lite? Or are there any other "hide root" apps i could try?
Thanks!
In my b371 works fine.
I installed magisk from play store and at the first start it asks to install itself in boot partiton.
i can't even install it in recovery, the phone justs reboots during installation.
how did you root? what kernel are you using? i'm using elite-kernel v3 for 370
i assume you're using phh's SuperUser?
well, maybe i give the 371 update a try...
I use elite-kernel. I rooted simply installing phh su from play store. Then I installed magisk from play store and it auto flash itself the zip. It works. Try
Paolo83 said:
I use elite-kernel. I rooted simply installing phh su from play store. Then I installed magisk from play store and it auto flash itself the zip. It works. Try
Click to expand...
Click to collapse
I follow your steps, but it gives me installation error. In which block have you installed mmcblk0p28? What recovery do you use?
Thank you
This recovery https://forum.xda-developers.com/hu...ecovery-twrp-3-0-2-android-nougat-03-t3511937
The partition is autodetected mmcblk0p28
Try to set selinux to permissive
It seems that everything is correct. But it does not hide the root, it does not pass safety net.
Paolo83 said:
Try to set selinux to permissive
Click to expand...
Click to collapse
THIS!
Installation works now, thanks dude!
@gvalro
i get "CTS profile mismatch"
Don't care, Super Mario Run works fine now with root enabled.
edit: naaah, the game crashes at some point, guess there's no perfect solution except unrooting your phone
realCyphox said:
THIS!
Installation works now, thanks dude!
@gvalro
i get "CTS profile mismatch"
Don't care, Super Mario Run works fine now with root enabled.
edit: naaah, the game crashes at some point, guess there's no perfect solution except unrooting your phone
Click to expand...
Click to collapse
try to enable magisk hide in setting
any have boot.img backup with Magisk working? in my case after reboot, Magisk need "reinstall"
simo255 said:
try to enable magisk hide in setting
Click to expand...
Click to collapse
Yes , is enabled
After installing Magisk, fingerprint disappears.
gvalro said:
Yes , is enabled
After installing Magisk, fingerprint disappears.
Click to expand...
Click to collapse
yes it was for me either, when i enable magisk hide, fps disappear :/
BadWolfYe said:
any have boot.img backup with Magisk working? in my case after reboot, Magisk need "reinstall"
Click to expand...
Click to collapse
autoquote for petition.
[GUIDE] HOW TO UPDATE TO RUI 2.0 AND ROOT IT
--> Disclaimer: I'm not responsible if you brick your device. Use at your own risk and always backup your data! <--
0. Download linksF.14 OTA: Download
Magisk app: Download
OrangeFox beta: Download
ADB/Fastboot tool: Download
Patched boot.img: Find attached
vbmeta.img: Find attached
Patched safetynet fix: Find attached
1. Update your deviceUpdate your device to the latest firmware version (F.14). Therefor flash the provided OTA zip via stock recovery or OrangeFox beta recovery.
It is recommended to use the stock recovery. You can also update your device to the latest firmware by using the build in update function.
2. Root your deviceBoot into fastboot mode. To boot into fastboot mode, shut down your device and then press the volume down button while clicking on the power button.
Now you have successfully booted into fastboot mode. Connect your device with your computer and flash the patched boot.img and also disable verified boot.
Therefor just type following 3 commands:
1. fastboot flash boot patched_boot.img
2. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
3. fastboot reboot
Your device should boot up. Now install the Magisk app and you have successfully rooted RUI 2.0.
3. Fix SafetynetInstall the patched "safetynet-fix-v.2.2.0-zip" module via Magisk. It will fix safetynet (Basic integrity and CTS). It works perfectly and won't brick your fingerprint etc. Thanks to @osm0sis
4. Get Widevine L1If you have unlocked your bootlader, Widevine will be set from L1 to L3. This will reduce the quality of certain streaming apps like Netflix from FullHD to SD quality.
However, you can get Widevine L1 back by contacting the Realme support. For more info, check the guide from @hack-os: Widevine L1 FIX
Reserved
DarkImperator said:
3. Fix Basic integrity check (Safetynet)Unfortunately, it is not possible to pass safetynet with rooted RUI 2.0. However, you can still pass basic integrity, which should be fine for most banking apps.
To do so, open the Magisk Manger app and click on the settings button on the top-right corner. Enable "Zygisk" and "Denylist". Then click on "Configure DenyList".
Click on the 3-dots on the top-right corner and select system-apps. Now search for "gms". You should find "Google Play Services". Click it and enable "com.google.android.gms" and "com.google.android.gms.unsuable". Now reboot your device and it should pass basic integrity.
Click to expand...
Click to collapse
I have rooted with magisk alpha and my snet passed easily.
To pass snet using magisk alpha:
1. Keep zygisk disabled.
2. Enable MagiskHide.
3. Configure DenyList for "com.google.android.gms" and "com.google.android.gms.unsuable" then reboot and done.
Eng.Raman said:
I have rooted with magisk alpha and my snet passed easily.
To pass snet using magisk alpha:
1. Keep zygisk disabled.
2. Enable MagiskHide.
3. Configure DenyList for "com.google.android.gms" and "com.google.android.gms.unsuable" then reboot and done.
Click to expand...
Click to collapse
Thanks for the info. I already tried it once with Magisk Alpha and the same settings as you, but CTS still failed. I'm gonna try it again and update the guide.
Edit: @Eng.Raman Unfortunately, it doesn't work. Installed Magisk Alpha, also cleaned all data of Google Play Store and Google Play Services multiple times and rebooted multiple times. But CTS still fails.
Do you maybe have installed some modules, like Riru or LPosed?
DarkImperator said:
Thanks for the info. I already tried it once with Magisk Alpha and the same settings as you, but CTS still failed. I'm gonna try it again and update the guide.
Edit: @Eng.Raman Unfortunately, it doesn't work. Installed Magisk Alpha, also cleaned all data of Google Play Store and Google Play Services multiple times and rebooted multiple times. But CTS still fails.
Do you maybe have installed some modules, like Riru or LPosed?
Click to expand...
Click to collapse
Don't dirty-flashing alpha over canary. completely uninstall magisk canary then clean install magisk alpha.
Yes ,I have installed some modules but they don't affect the test result, even without magisk and lsposed modules I have passed snet.
Eng.Raman said:
Don't dirty-flashing alpha over canary. completely uninstall magisk canary then clean install magisk alpha.
Yes ,I have installed some modules but they don't affect the test result, even without magisk and lsposed modules I have passed snet.
Click to expand...
Click to collapse
Yes, I know. That's exactly what I did. I uninstalled Magisk Canary completely including the app and went back to stock boot. Afterwards I installed Magisk alpha app, patched boot.img, flashed patched boot.img an rebooted.
Just a couple of minutes ago a new version of magisk alpha was released, and also with that version CTS fails.
Nevertheless, I found out something interesting. With Magisk Canary, CTS fails and Advice tells me to Lock bootloader. With Magisk Alpha CTS still fails, but I get no advice.
DarkImperator said:
Yes, I know. That's exactly what I did. I uninstalled Magisk Canary completely including the app and went back to stock boot. Afterwards I installed Magisk alpha app, patched boot.img, flashed patched boot.img an rebooted.
Just a couple of minutes ago a new version of magisk alpha was released, and also with that version CTS fails.
Nevertheless, I found out something interesting. With Magisk Canary, CTS fails and Advice tells me to Lock bootloader. With Magisk Alpha CTS still fails, but I get no advice.
Click to expand...
Click to collapse
What is your Momo app and magisk Detector results? Can you screenshot ?
Eng.Raman said:
What is your Momo app and magisk Detector results? Can you screenshot ?
Click to expand...
Click to collapse
Yes. Have installed both and attached the screenshots. Have not added any of those apps to my DenyList.
DarkImperator said:
Yes. Have installed both and attached the screenshots. Have not added any of those apps to my DenyList.
Click to expand...
Click to collapse
Your momo app shows " The environment is broken" and this is related to enabling MagiskHide.
To get rid of this message and to see full results either add config "app_zygote_magic" or install momohider-mod zip attached.
Eng.Raman said:
Your momo app shows " The environment is broken" and this is related to enabling MagiskHide.
To get rid of this message and to see full results either add config "app_zygote_magic" or install momohider-mod zip attached.
Click to expand...
Click to collapse
EDIT: @Eng.Raman had to install MomoHider and add config "app_zygote_magic". Now Momo gives me the message.
DarkImperator said:
Installed MomoHider, but it still said "The environment is broken". So I disabled MagiskHide. Only as MagiskHide was disabled, I received a message from Momo. Screenshot attached.
Click to expand...
Click to collapse
That's weird you can't even hide magisk and su file.
Eng.Raman said:
That's weird you can't even hide magisk and su file.
Click to expand...
Click to collapse
Yeah, Magisk alpha seems not to fix CTS on my device. Safetynet-fix (https://github.com/kdrag0n/safetynet-fix) does, but it also bricks my in-display fingerprint reader. So at the moment it seems like I can't bypass CTS.
DarkImperator said:
Yeah, Magisk alpha seems not to fix CTS on my device. Safetynet-fix (https://github.com/kdrag0n/safetynet-fix) does, but it also bricks my in-display fingerprint reader. So at the moment it seems like I can't bypass CTS.
Click to expand...
Click to collapse
My fingerprint also works well.
Are you tried to pass the snet with the latest USNF-2.1.2? May it works for you.
Eng.Raman said:
My fingerprint also works well.
Are you tried to pass the snet with the latest USNF-2.1.2? May it works for you.
Click to expand...
Click to collapse
Yes, USNF and safetynet-fix both brick my in-display-fingerprint.
With Magisk alpha/canary there is no issue with my fingerprint.
DarkImperator said:
Yes, USNF and safetynet-fix both brick my in-display-fingerprint.
With Magisk alpha/canary there is no issue with my fingerprint.
Click to expand...
Click to collapse
Try clean installing magisk custom it has MagiskHide without DenyList, builtin snet checker and online modules repo as magisk stable, the latest custom magisk build is 23015.
Eng.Raman said:
Try clean installing magisk custom it has MagiskHide without DenyList, builtin snet checker and online modules repo as magisk stable, the latest custom magisk build is 23015.
Click to expand...
Click to collapse
What exactly do you mean with Magisk custom? I was not able to find other 23015 builds than from topjohnwu and vbb2060
DarkImperator said:
What exactly do you mean with Magisk custom? I was not able to find other 23015 builds than from topjohnwu and vbb2060
Click to expand...
Click to collapse
TheHitMan7 Custom Magisk ( Github Link ) updated 6 hours ago.
Also he has two TG channles one named as "Magisk Custom" for downloading the debug builds and the 2nd one named as "Custom Magisk" for supporting and discussions.
Eng.Raman said:
TheHitMan7 Custom Magisk ( Github Link ) updated 6 hours ago.
Also he has two TG channles one named as "Magisk Custom" for downloading the debug builds and the 2nd one named as "Custom Magisk" for supporting and discussions.
Click to expand...
Click to collapse
With enabled Magisk Hide it will fix basic integrity check, but not CTS. And it also bricks my in-display-fingerprint. Guess I'll stay with Magisk Canary, till there might be an update to fix those issues.
Hello guys.
When trying to add my bank card in google pay, I have an error that this phone can't be used to pay because it's rooted.
jalal.sy said:
Hello guys.
When trying to add my bank card in google pay, I have an error that this phone can't be used to pay because it's rooted.
Click to expand...
Click to collapse
I have the same issue with my banking app that doesn't allow NFC payments even though I've done everything to hide root.