Is there any way on stock rom, I can disbale signature verification? I'm on Android 10, latest Magisk.
Related
Anyone tried to patch this on k1 marshmallow? it was a success when i was on lollipop. But when i update my k1 to marshmallow
i can't seem to patch it,been doing a lot of factory reset but its not successful.
signature verification status always true (patched)
disable .apk signature verification (patched)
Disable signature verification in the package manager (not patched)
Lucifu said:
Anyone tried to patch this on k1 marshmallow? it was a success when i was on lollipop. But when i update my k1 to marshmallow
i can't seem to patch it,been doing a lot of factory reset but its not successful.
signature verification status always true (patched)
disable .apk signature verification (patched)
Disable signature verification in the package manager (not patched)
Click to expand...
Click to collapse
Have you tried unchecking only patch dalvik cache?
OverBit said:
Have you tried unchecking only patch dalvik cache?
Click to expand...
Click to collapse
i did,i ended up downgrading to lollipop for the mean time
I got a OnePlus 3 with a modified TWRP recovery for Multirom. My primary rom is rooted Kali Nethunter and I patched a custom kernel for it. My secondary rom is a Stock OxygenOs 4.0.2, it is not rooted and I flashed the elemental X Kernel for it.
If i am right, this kernel has the verified boot Flag disabled for using Android Pay, PGO etc..
But I can't pass the SafetyNet check...
So my question is how do I bypass SafetyNet? I want to keep Nethunter as a rom either primary or secondary. I can't install Magisk on it because when I flash the NH rom it automatically flashs the normal SuperSu with it. I thought this setup I made would work. So what does SafetyNet detect?
Would be nice if someone could help me.
I have tried everything to bypass safetynet I even tried flashing stock rom with untouched system image and I still get safetynet fails
does the new update adds verified boot meaning that if the device has an unlocked bootloader it won't bypass safetynet ?
AlMaghraby said:
I have tried everything to bypass safetynet I even tried flashing stock rom with untouched system image and I still get safetynet fails
does the new update adds verified boot meaning that if the device has an unlocked bootloader it won't bypass safetynet ?
Click to expand...
Click to collapse
You need magisk to pass safety net since you unlocked your bootloader
Just flash LeeDroid and be done with it. Easy.
I formated restored untouched system image installed magisk and universal safetynet fix v2beta5 and all good thanks for the info.
I am using moto g5. I installed many pie custom ROM such as Bootlegger,Pixel experience,Viper OS. But all ROM have been failed to run Banking apps. I tried magisk module but same result. please help!!!!!
pacemaker.santo said:
I am using moto g5. I installed many pie custom ROM such as Bootlegger,Pixel experience,Viper OS. But all ROM have been failed to run Banking apps. I tried magisk module but same result. please help!!!!!
Click to expand...
Click to collapse
same here.
after entering password and user name it closed
Hey all,
I am rooted with Magisk 17.3 on global hardware and global ROM stock MIUI 10.2.2.0, but I cannot install any Magisk modules or flash Magisk ZIPs in TWRP. I know root works because I've edited system files and allowed a few apps root permissions. But when I try to install something with Magisk Manager (6.1.0 since 7.0.0 doesn't work < v18) I get this error: /data/adb/magisk_merge.img mount failed... abort or it tells me Magisk 17.x+ isn't installed. (I've tried the Magisk Mod Uninstaller, Youtube Vanced, and LKT). When I try to flash a Magisk ZIP in TWRP it gives me Error: 1
I did some searching and some people were getting this due to their filesystem being formatted as f2fs in the past, but I verified that the Mi Mix 3 uses EXT4 using DiskInfo.
Did I miss something during the rooting process? I unlocked the bootloader, flashed TWRP in fastboot, flashed Magisk 17.3 in TWRP, and verified root was achieved with Rootchecker. The Magisk Manager app also says it's installed and passes SafetyNet. Anyone have any ideas?
Do you use a custom kernel?
Try the latest Magisk canary build and see if that works
JetzNicht said:
Do you use a custom kernel?
Try the latest Magisk canary build and see if that works
Click to expand...
Click to collapse
No it is the stock kernel that came with the MIUI 10.2.2.0 global build. Should I be using one?
Quick update: I am able to install some modules now by downloading them in Magisk, then booting to TWRP and flashing the ZIP there. I was able to get Magisk Mod Uninstaller (mm) and LKT to run for example using this method. YouTube Vanced still gives me the Error: 1 when I do this however.
The try a custom kernel, had the same problems with any modifications to the system with stock kernel.
As far as I know there are only two kernels atm, friendly fire and androplus.