First of all i think there is a need in common thread about Magisk.
I am on XT1685 with 137-35 ver. and exprerienced some Magisk issues. MagiskSU works well on 12.0, 13 beta and 13.3. But SafetyNet is not. My particular problem is not mountable magisk.img. And there is a suggestion that may be caused by f2fs issue on some Lenovo devices (or something else). In different threads there are a lot of different messages about working/not working SafetyNet so i think we need clarification. Most people don't even bother to point out OS version, stock, custom kernel, model etc. So let try to gather information about issue together.
SafetyNet status: not pass
Model: XT1685
OS: Stock 137-35
Kernel: Stock
Magisk: 13.3
Have you also tried the universal safetynet fix and it still doesn't pass?
That's peculiar, I'm on 13.3 with a 1687 running -35 with extended kernel by @attack11 and pass without universal safety net fix.
Dahenjo said:
Have you also tried the universal safetynet fix and it still doesn't pass?
Click to expand...
Click to collapse
Magisk modules don't work with stock kernel
For OP, you should try a custom kernel, probably this will fix your safety issue
atrac17 said:
That's peculiar, I'm on 13.3 with a 1687 running -35 with extended kernel by @attack11 and pass without universal safety net fix.
Click to expand...
Click to collapse
Same there. Yesterday flashed attack11 Extended Kernel V4 for NPN25.137-35 then flashed Magisk 13.3. All is green without USNF. Tried V5 but there was broken camera.
CaptPetrenko said:
Same there. Yesterday flashed attack11 Extended Kernel V4 for NPN25.137-35 then flashed Magisk 13.3. All is green without USNF. Tried V5 but there was broken camera.
Click to expand...
Click to collapse
V5 is for -67. That's why you had trouble.
atrac17 said:
V5 is for -67. That's why you had trouble.
Click to expand...
Click to collapse
Yeap.
Have you faced issue that folder binders or folder mounter not working of any kind. If you got a working then tell me. I am on 35
manjot7798 said:
Have you faced issue that folder binders or folder mounter not working of any kind. If you got a working then tell me. I am on 35
Click to expand...
Click to collapse
What do you exactly mean? In my case Magisk could not mount magisk.img into /magisk on system start
CaptPetrenko said:
What do you exactly mean? In my case Magisk could not mount magisk.img into /magisk on system start
Click to expand...
Click to collapse
I mean folder mount apps, the app in which you can free space, in which you have to mount the folder or can search it up on play store as folder mount or app2s all in one tool. It didn't seem to work on magisk 13.3 whereas it worked on magisk 11.6
manjot7798 said:
I mean folder mount apps, the app in which you can free space, in which you have to mount the folder or can search it up on play store as folder mount or app2s all in one tool. It didn't seem to work on magisk 13.3 whereas it worked on magisk 11.6
Click to expand...
Click to collapse
Can not say something about that. I never mounted folders. Use only Root Explorer for file managing. Do you have problems with SafetyNet? Could you send Magisk log? May be your mounting problem has common roots with stock kernel issue and read-only preferences
XT1687
NPNS25.137-33-5
Security patch level is May 1, 2017
I used this video as my guide: youtube[dot]com/watch?v=zUPTFnzAvSo
Root was successful with Magisk 13.3 (including installation of ElementalX-G5-1.01) but ctsProfile and basicIntegrity are false with Safety Net check. The creator of the video had us flash universal safety net fix v1.zip and updated safety net fix v2.zip which I did, but the SafetyNet check still fails. On his video, both items passed.
Not sure what went wrong for me.
He advised users (in the comments) to flash a different kernel, then flash the two safety net zip files again. Good advice or not? Can someone elaborate?
I can confirm all green via these steps: from stock, install extended kernel v4, install magisk v13.3, and all green. Updated to magisk v14 via Magisk manager, all remains green.
Quote:
Originally Posted by atrac17
That's peculiar, I'm on 13.3 with a 1687 running -35 with extended kernel by @attack11 and pass without universal safety net fix.
After updating to v. 14.0 ctsProfile error occured. I rolled back to 13.3 version but there was the same error. I flashed the latetst beta of universal fix and ctsProfile check went through. Don't know would it work with 14.0 ver.
brandonsisco said:
I can confirm all green via these steps: from stock, install extended kernel v4, install magisk v13.3, and all green. Updated to magisk v14 via Magisk manager, all remains green.
Click to expand...
Click to collapse
CaptPetrenko said:
After updating to v. 14.0 ctsProfile error occured.
Click to expand...
Click to collapse
Hi,
Most of the work regarding the cts check can be done with a custom kernel.
And one relevant factor is remove the parameters "androidboot.verifiedbootstate" and "androidboot.veritymode" from the command-line (patching the "/proc/cmdline" file).
See this post: http://forum.xda-developers.com/showpost.php?p=73712158&postcount=471
If you like to pass the SafetyNet, then first use a patched kernel or request to developers to include this patch!
Don't waste your time with other complex solutions!
Hi,
If you like to pass SafetyNet in stock and have full support for Magisk then install this kernel:
https://forum.xda-developers.com/showpost.php?p=73783900&postcount=483
Regards.
Lineage OS 14.1 & LOS kernel with Magisk 14 does not pass.
brandonsisco said:
I can confirm all green via these steps: from stock, install extended kernel v4, install magisk v13.3, and all green. Updated to magisk v14 via Magisk manager, all remains green.
Quote:
Originally Posted by atrac17
That's peculiar, I'm on 13.3 with a 1687 running -35 with extended kernel by @attack11 and pass without universal safety net fix.
Click to expand...
Click to collapse
I changed to the v4 extended kernel, Magisk V14.0, and also getting all green on the SafetyCheck with the 35 rom. BUT MagiskHide does not work: when I look at the logs I see
fopen:/magisk/.core/hidelist failed with 2: No such file or directory
Does MagiskHide work for you?
Yes working for me I suspect you have mounting error above that in log?
---------- Post added at 08:41 PM ---------- Previous post was at 08:39 PM ----------
I suggest install stock then extended kernel then magick fresh
snaggletooth1 said:
XT1687
NPNS25.137-33-5
Security patch level is May 1, 2017
I used this video as my guide: youtube[dot]com/watch?v=zUPTFnzAvSo
Root was successful with Magisk 13.3 (including installation of ElementalX-G5-1.01) but ctsProfile and basicIntegrity are false with Safety Net check. The creator of the video had us flash universal safety net fix v1.zip and updated safety net fix v2.zip which I did, but the SafetyNet check still fails. On his video, both items passed.
Not sure what went wrong for me.
He advised users (in the comments) to flash a different kernel, then flash the two safety net zip files again. Good advice or not? Can someone elaborate?
Click to expand...
Click to collapse
Hi, I came from the same video and I did all the steps he put in there. I did the root process with Magisk 13 then I updated to 14 version (a days ago) and everything is working ok.
Related
I just installed magisk and it is working fine in f2fs file system.
This will cause any problem?
Wonder Wicked Witch said:
I just installed magisk and it is working fine in f2fs file system.
This will cause any problem?
Click to expand...
Click to collapse
Interesting, I have some questions. What rom, kernel and twrp version? Does SafetyNet pass? And do magisk modules work?
razr96 said:
Interesting, I have some questions. What rom, kernel and twrp version? Does SafetyNet pass? And do magisk modules work?
Click to expand...
Click to collapse
Right Now I'm using Resurrection remix 5.8.5 kernal 3.18.31 twrp 3.1.1.1
It works in any custom rom, it is mostly useful for lineage os and los based rom because in los you cannot root easily, Magisk with ext4 filesystem is required. I'm not sure with the modules, super user works, safety net pass failed. If you just want root access you can give a try....
It works fine when you have a different kernel. A dev. on here reported that the only reason it doesn't work is because of how Lenovo implemented F2FS in the kernel.
No problem, everything works fine except that Safety net won't pass.
Has anyone been able to get a v4a module working on 16.4 and the may update? I tried installing the module by viper50 and ahirion that has worked so well in the past... Doesn't seem to be enabling for me this time around for some reason. Any ideas?
Or other mods to recommend?
V4a v2.5.05 working fine with magisk 16.4 and may update here.
EnIXmA said:
V4a v2.5.05 working fine with magisk 16.4 and may update here.
Click to expand...
Click to collapse
Same here, everything working smoothly with v4afx_v1.6.9.zip and magisk 16.4. Viper also works on P dp2.
Taebom said:
Same here, everything working smoothly with v4afx_v1.6.9.zip and magisk 16.4. Viper also works on P dp2.
Click to expand...
Click to collapse
Are you flashing in magisk or twrp? Which module are you using? Thanks!
I'm neither of the other posters, but flash V4A via Magisk using the module authored by Viper520, ZhuHang, Ahrion, and Zackptg5. Be certain that you select the new driver and the materialized version of the app for V4A to work properly.
Strephon Alkhalikoi said:
I'm neither of the other posters, but flash V4A via Magisk using the module authored by Viper520, ZhuHang, Ahrion, and Zackptg5. Be certain that you select the new driver and the materialized version of the app for V4A to work properly.
Click to expand...
Click to collapse
This ^^ : point upwards: ! Especially the underlined part; it took me a whole lot of trial and error to figure this last part out...
In any case, I used the latest Magisk module (if you check the details of the modules, it'll show when it was last updated). If anything, supposedly you could just install straight away, but V4A gave me errors. I had to uninstall the existing V4A, reboot, install via Magisk module, and reboot before it worked. You (@Cowbell_Guy) might, at the very least, have to walk through the same steps for whatever reason...
Hope this helps...
cannot pass safety net on miui 10 global beta .
i installed root using magisk 16.
everything works fine ( Gcam, viper4droid etc)
but my safetynet is broken.
cts profile mismatch is true.
i m unable to find any solution.
tried universal safety net fix through twrp it says no magisk installed but root is working properly.
can anyone fix it?
wirex13 said:
cannot pass safety net on miui 10 global beta .
i installed root using magisk 16.
everything works fine ( Gcam, viper4droid etc)
but my safetynet is broken.
cts profile mismatch is true.
i m unable to find any solution.
tried universal safety net fix through twrp it says no magisk installed but root is working properly.
can anyone fix it?
Click to expand...
Click to collapse
Install the fix through magisk directly. Not twrp.
change your device fingerprint in build. prop file.. and then reboot ..voila!
you can replace fingerprint with stable rom v9. 5.13
Can anyone share the stable rom's fingerprint from their device?? It will be very helpful.
Edit :-I have found a fix and stable rom's fingerprint in this thread.
https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228
And its working very well. Hope that helps you. Ask me if you need any help about enabling this module because its a bit different than others.
otonieru said:
Install the fix through magisk directly. Not twrp.
Click to expand...
Click to collapse
its says
Copying zip to temp directory - Installing ... Failed! !
wirex13 said:
its says
Copying zip to temp directory - Installing ... Failed! !
Click to expand...
Click to collapse
If that so, theres chance your magisk installation was derp. Try reinstalling magisk first. Or use the safetynet prop fix module, not the universal one.
RockStar8 said:
Can anyone share the stable rom's fingerprint from their device?? It will be very helpful.
Edit :-I have found a fix and stable rom's fingerprint in this thread.
https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228
And its working very well. Hope that helps you. Ask me if you need any help about enabling this module because its a bit different than others.
Click to expand...
Click to collapse
i used above steps but in terminal it says
"the settings boot script does not appeared to run during boot"
this means the module doesn't work.
dipak9477 said:
change your device fingerprint in build. prop file.. and then reboot ..voila!
you can replace fingerprint with stable rom v9. 5.13
Click to expand...
Click to collapse
can u provide ro fingerprint
ro.build.fingerprint =
wirex13 said:
i used above steps but in terminal it says
"the settings boot script does not appeared to run during boot"
this means the module doesn't work.
Click to expand...
Click to collapse
The module itself has Redmi Note 5 Pro Oreo MIUI 9.5 Stable signature added in its database. You just need to download and flash the module from magisk and reboot. Then open terminal and run command su then allow root access then run command props choose change device signature then choose Redmi Note 5 Pro then Confirm and Reboot. Just remember to reboot after installing the module and then use terminal commands.
dipak9477 said:
change your device fingerprint in build. prop file.. and then reboot ..voila!
you can replace fingerprint with stable rom v9. 5.13
Click to expand...
Click to collapse
just replace miui version in ro. build. fingerprint with V9.5.13.0.OEIMIFA
Hi,
does anybody use EdXposed module for Magisk?
I flashed Riru core v18 and EdXposed v0.3.1.7_beta in Magisk.
If EdXposed v0.3.1.7_beta magisk module is activated, mobile data does not work? Is anyone facing a similar problem?
The problem is definitly with EdXposed, since it does not matter which Riru core version I use. If I use EdXposed v0.2.9.9_beta2, then mobila data works, but this version of EdXposed is really buggy.
I am on stock Pie rom V10.0.7, but it was the same with V10.0.4.
zk_eu said:
Hi,
does anybody use EdXposed module for Magisk?
I flashed Riru core v18 and EdXposed v0.3.1.7_beta in Magisk.
If EdXposed v0.3.1.7_beta magisk module is activated, mobile data does not work? Is anyone facing a similar problem?
The problem is definitly with EdXposed, since it does not matter which Riru core version I use. If I use EdXposed v0.2.9.9_beta2, then mobila data works, but this version of EdXposed is really buggy.
I am on stock Pie rom V10.0.7, but it was the same with V10.0.4.
Click to expand...
Click to collapse
I´m in CrDroid Pie + Magisk 18.1 + Riru 18 + EdXposed 0.4.01_beta_SNAPSHOT and all working fine
Have a similar problem when haved 3.1.7 but i´m not sure the EdXposed, reinstalled crdroid and works fine, now upgraded to EdXposed 0.4.01_beta_SNAPSHOT and all works fine
I tried the EdXposed 0.4.01_beta_SNAPSHOT, but unfortunately it is the same.
zk_eu said:
I tried the EdXposed 0.4.01_beta_SNAPSHOT, but unfortunately it is the same.
Click to expand...
Click to collapse
Maybe the rom or kernel, i´m in custom rom and all works fine
Riru 17.1
EdXposed 3.1.7
Stock pie 10.0.7.0
No issues here
I think I have found the problem. I seems that EdXposed and Camera 2 API are somehow interfering with each other.
I does not matter if I use Magisk module Camera2_API_Enabler-v1.0.0 or activate camera 2 API threw SU ADB with:
1. setprop persist.camera.HAL3.enabled 1
2. setprop persist.camera.eis.enabled 1
The result is always the same. My mobile data won't work. If I disable Camera 2 API, then mobile data works.
Well, I posted this bug on EdXposed GitHub site and got an answer. Apparently this bug can be solved by changing selinux to permissive. Worked also for me (even on v0.4.1.2_beta). Hope it helps someone with the same issue.
Can someone send a quick guide on installation process?
ncar123 said:
Can someone send a quick guide on installation process?
Click to expand...
Click to collapse
Download the files:
EdXposed Manager
https://github.com/ElderDrivers/EdX...eowcat.edxposed.manager-4.5.0-450-release.apk
--------------
Riru-Core
Ver. 19 (If you use Magisk 19+)
https://github.com/RikkaApps/Riru/releases/download/v19/magisk-riru-core-v19.zip
Ver. 19.1 (if you use Magisk 17-18.+)
https://github.com/RikkaApps/Riru/releases/download/v19.1/riru-core-v19.1-magisk-v17.zip
--------------
EdXposed (Select one, i´m using Sandhook without problems)
SandHook
https://github.com/ElderDrivers/EdX...osed-SandHook-v0.4.5.1_beta.4463.-release.zip
or
Yahfa
https://github.com/ElderDrivers/EdX...dXposed-YAHFA-v0.4.5.1_beta.4463.-release.zip
After download the files, intall EdXposed Manager apk
Go to Magisk Manager -> Modules -> + -> Flash Riru-Core (Not reboot)
Modules -> + -> Flash EdXposed
Reboot System
Thats all
leechgid said:
Download the files:
EdXposed Manager
https://github.com/ElderDrivers/EdX...eowcat.edxposed.manager-4.5.0-450-release.apk
--------------
Riru-Core
Ver. 19 (If you use Magisk 19+)
https://github.com/RikkaApps/Riru/releases/download/v19/magisk-riru-core-v19.zip
Ver. 19.1 (if you use Magisk 17-18.+)
https://github.com/RikkaApps/Riru/releases/download/v19.1/riru-core-v19.1-magisk-v17.zip
--------------
EdXposed (Select one, i´m using Sandhook without problems)
SandHook
https://github.com/ElderDrivers/EdX...osed-SandHook-v0.4.5.1_beta.4463.-release.zip
or
Yahfa
https://github.com/ElderDrivers/EdX...dXposed-YAHFA-v0.4.5.1_beta.4463.-release.zip
After download the files, intall EdXposed Manager apk
Go to Magisk Manager -> Modules -> + -> Flash Riru-Core (Not reboot)
Modules -> + -> Flash EdXposed
Reboot System
Thats all
Click to expand...
Click to collapse
DONE
but my gcan doesn't work...
---------- Post added at 02:27 PM ---------- Previous post was at 01:47 PM ----------
zk_eu said:
Well, I posted this bug on EdXposed GitHub site and got an answer. Apparently this bug can be solved by changing selinux to permissive. Worked also for me (even on v0.4.1.2_beta). Hope it helps someone with the same issue.
Click to expand...
Click to collapse
Can you elaborate?
ncar123 said:
DONE
but my gcan doesn't work...
---------- Post added at 02:27 PM ---------- Previous post was at 01:47 PM ----------
Can you elaborate?
Click to expand...
Click to collapse
Gcam nothing about with Xposed
Maybe you need activate Camera2Api or need a custom kernel (Ex. Butterfly)
Have a stock Rom o custom rom?
leechgid said:
Gcam nothing about with Xposed
Maybe you need activate Camera2Api or need a custom kernel (Ex. Butterfly)
Have a stock Rom o custom rom?
Click to expand...
Click to collapse
Stock rom
root
Magisk
Edxposed
camera2api in magisk
10.0.9.0
Also tried manually in build.prop
Doesn't work....
ncar123 said:
Stock rom
root
Magisk
Edxposed
camera2api in magisk
10.0.9.0
Also tried manually in build.prop
Doesn't work....
Click to expand...
Click to collapse
Uninstall camera2api in magisk
Try with this
https://forum.xda-developers.com/mi-a2-lite/how-to/guide-how-to-enable-camera2-api-t3851414
Steps -> 1,3,4,5,10,11 and try with this cam https://f.celsoazevedo.com/file/cfiles/gcm1/MGC_6.2.024_IPSGCA_V18ORE.apk
leechgid said:
Uninstall camera2api in magisk
Try with this
https://forum.xda-developers.com/mi-a2-lite/how-to/guide-how-to-enable-camera2-api-t3851414
Steps -> 1,3,4,5,10,11 and try with this cam https://f.celsoazevedo.com/file/cfiles/gcm1/MGC_6.2.024_IPSGCA_V18ORE.apk
Click to expand...
Click to collapse
Tried manually in build.prop, it doesn't work maybe it is something in selinux
---------- Post added at 06:16 PM ---------- Previous post was at 05:35 PM ----------
Something really weird, turned the selinux to permissive , didn't work, tuned back to enforcing and now it works
Well hope it stays that way, thx everyone
EDIT:
Now it stopped working, I'm clueless
2ndEdit:
Played with build.prop and magisk camera2api
It works, I guess some stuff turn that off, well I don't know
leechgid said:
Download the files:
EdXposed Manager
https://github.com/ElderDrivers/EdX...eowcat.edxposed.manager-4.5.0-450-release.apk
--------------
Riru-Core
Ver. 19 (If you use Magisk 19+)
https://github.com/RikkaApps/Riru/releases/download/v19/magisk-riru-core-v19.zip
Ver. 19.1 (if you use Magisk 17-18.+)
https://github.com/RikkaApps/Riru/releases/download/v19.1/riru-core-v19.1-magisk-v17.zip
--------------
EdXposed (Select one, i´m using Sandhook without problems)
SandHook
https://github.com/ElderDrivers/EdX...osed-SandHook-v0.4.5.1_beta.4463.-release.zip
or
Yahfa
https://github.com/ElderDrivers/EdX...dXposed-YAHFA-v0.4.5.1_beta.4463.-release.zip
After download the files, intall EdXposed Manager apk
Go to Magisk Manager -> Modules -> + -> Flash Riru-Core (Not reboot)
Modules -> + -> Flash EdXposed
Reboot System
Thats all
Click to expand...
Click to collapse
Hi,
I followed this method, and my phone is now stuck on the loading bar on start-up (the multi color moving bar)... What happened ?
What should I do:
Flash the original boot image, or can I flash the magisk patched img file ?
Thanx !
I was using it with AOSP Extended Last build and magisk 18.1...but signal phone is not working sometimes...so i leave it.
takhama said:
Hi,
I followed this method, and my phone is now stuck on the loading bar on start-up (the multi color moving bar)... What happened ?
What should I do:
Flash the original boot image, or can I flash the magisk patched img file ?
Thanx !
Click to expand...
Click to collapse
It is strange:
If I flash the stock image, the phone will start
If I reflash it with the magisk patched file, it will stay stuck (I removed edxspoed apk, and resinstalled magisk apk)... This edxposed framewok seems to have broken something. I think I'm good to reflash the ROM....
takhama said:
Hi,
I followed this method, and my phone is now stuck on the loading bar on start-up (the multi color moving bar)... What happened ?
Click to expand...
Click to collapse
EdXposed is a magisk module. If you disable Magisk or EdXposed then the system will boot again. Flashing/booting the vanilla boot image is one way to do it. You could then use Magisk app to disable EdXposed.
Another way is to start TWRP and use the shell to modify/remove files in /data. I don't know the specifics of this, but the mm (Magisk manager cli) module puts a script in /sdcard that allows managing Magisk modules from TWRP.
a1291762 said:
EdXposed is a magisk module. If you disable Magisk or EdXposed then the system will boot again. Flashing/booting the vanilla boot image is one way to do it. You could then use Magisk app to disable EdXposed.
Another way is to start TWRP and use the shell to modify/remove files in /data. I don't know the specifics of this, but the mm (Magisk manager cli) module puts a script in /sdcard that allows managing Magisk modules from TWRP.
Click to expand...
Click to collapse
Unfortunately, I am not able to do this:
My phone can start with the stock boot image, but here magisk will show no module (because saying magisk is not installed)
With the magisk patched boot image , impossibe to start....
I'll try using TWRP before flashing everything. Thanx !
zk_eu said:
Hi,
does anybody use EdXposed module for Magisk?
I flashed Riru core v18 and EdXposed v0.3.1.7_beta in Magisk.
If EdXposed v0.3.1.7_beta magisk module is activated, mobile data does not work? Is anyone facing a similar problem?
The problem is definitly with EdXposed, since it does not matter which Riru core version I use. If I use EdXposed v0.2.9.9_beta2, then mobila data works, but this version of EdXposed is really buggy.
I am on stock Pie rom V10.0.7, but it was the same with V10.0.4.
Click to expand...
Click to collapse
This is an outdated EdXposed, Riru - Core and Magisk. I recommend installing the latest one.
UNIVERSAL SafetyNet FIX
(A515x Edition)
ABOUT THIS:This is a universal fix for SafetyNet on devices with hardware attestation and unlocked bootloaders. It defeats both hardware attestation and the new SafetyNet CTS profile updates released on January 12, 2021. The only requirement is that you can pass basic attestation, which requires a valid combination of device and model names, build fingerprints, and security patch levels.
Passing basic attestation is mostly out-of-scope for this module; this module is meant to defy hardware attestation, as well as reported "basic" attestation that actually uses hardware under-the-hood. Nonetheless, it features a few basic attempts at helping pass basic attestation on some devices, especially older devices and devices running stock ROMs.
HOW DO I USE IT?
Code:
1. Simply install the module by Magisk, reboot
2. Enable Magisk Hide and enjoy
**ITS ONLY for A51 OneUI 2.5 or 3.0
CREDITS TO:
@kdrag0n (Original developer of this mod)
@spit85 (For his important information and experience applying it to other devices )
SafetyNET Patch A51
Its based on the stock keystore so it doesnt affect anything
is it working One UI 2.1 refined v1.0 ?
Fatih27 said:
is it working One UI 2.1 refined v1.0 ?
Click to expand...
Click to collapse
It should be the same keystore. You can test it. If your phone doesn't boot, boot to recovery and delete the module there.
Hi, I do the steps but it keeps saying that the certification failed :/
EDIT: Solved
My sefty net passes but after that i can't access mobile setting
It says the settings has stopped
ameer419 said:
My sefty net passes but after that i can't access mobile setting
It says the settings has stopped
Click to expand...
Click to collapse
You are using a Samsung galaxy a51? Android 10 or 11?
spit85 said:
You are using a Samsung galaxy a51? Android 10 or 11?
Click to expand...
Click to collapse
Android 10
ameer419 said:
Android 10
Click to expand...
Click to collapse
That's strange. It should work on android 10. I hex patched that keystore by my self. Maybe you got another magisk module that conflicts with these one. Do you have magisk props hide module? If yes, delete that module. You don't need it with these safetynet patch. And these patch is only for stock rom or stock base roms
spit85 said:
That's strange. It should work on android 10. I hex patched that keystore by my self. Maybe you got another magisk module that conflicts with these one. Do you have magisk props hide module? If yes, delete that module. You don't need it with these safetynet patch. And these patch is only for stock rom or stock base roms
Click to expand...
Click to collapse
Yes at that time i have that module but after this problem...i unroot my device
ameer419 said:
Yes at that time i have that module but after this problem...i unroot my device
Click to expand...
Click to collapse
Then root your phone again and only instal this module. I should work. Or flash the boot image again with Odin and root it over twrp recovery
spit85 said:
Then root your phone again and only instal this module. I should work. Or flash the boot image again with Odin and root it over twrp recovery
Click to expand...
Click to collapse
Yeah i m going to root it tomorrow
Just after rooting....do i have to install thia module
Would u like to suggest me to install any other module to pass safety net
ameer419 said:
My sefty net passes but after that i can't access mobile setting
It says the settings has stopped
Click to expand...
Click to collapse
Hi, If u are in RefinedUI 2.0 its a bug but I have already fixed it, check the small updates section of the Refined thread
BlassGO said:
Hi, If u are in RefinedUI 2.0 its a bug but I have already fixed it, check the small updates section of the Refined thread
Click to expand...
Click to collapse
I m on ui2.5
ameer419 said:
I m on ui2.5
Click to expand...
Click to collapse
With RefinedUI?
BlassGO said:
With RefinedUI?
Click to expand...
Click to collapse
Bro I have not so much knowledge about thi....i don't know it's refined or not....how to check
ameer419 said:
Bro I have not so much knowledge about thi....i don't know it's refined or not....how to check
Click to expand...
Click to collapse
I guess you are on stock rom and only unlock the bootloader and rooted the phone. If you have the Samsung galaxy a51, this patch work. If you have another phone model, it's possible that's the reason your phone trips in settings
spit85 said:
I guess you are on stock rom and only unlock the bootloader and rooted the phone. If you have the Samsung galaxy a51, this patch work. If you have another phone model, it's possible that's the reason your phone trips in settings
Click to expand...
Click to collapse
Yes... i have stock rom unlocked bootloader
I will try thi today after rooting because i unroot my phone due to settings has stopped issue
Updater process ended with ERROR 1
Error installing zip file "/external_sd/SafetyNet_Patch_A515_a10-11.zip
or
Updater process ended with ERROR 123
Error installing zip file "/external_sd/SafetyNet_Patch_A515_a10-11.zip
mikola08 said:
It doesn't want to install on android 11
Click to expand...
Click to collapse
Magisk crashes when tapping from "install from storage"
Using
[ROM][A515x] RefinedUI v2.0 [OneUI3.0 - Android11]
[ROM][A515x] RefinedUI v2.0 [OneUI3.0 - Android11]
FEATURES [ 2.0 - REMAKE ] - NDataX replaced with BlueFly (An improved version) - Mixplorer removed (Problems with Google File Manager) - Added the option to remove the Magisk App from the /system (Abnormal State) - The OMC was updated with the...
forum.xda-developers.com
A short splash screen shows up with an blue folder icon.
Any idea how to fix that?