Hi So as many update and update came, in january in order to pass the safety net fix file have to be install over Magisk. So while the current v22.1 have the bug about the api check .. showing the error. Do we still need to install the : https://github.com/kdrag0n/safetynet-fix/releases file from jan16 or it's now fully embeded into Magisk over v22 ? And is that file is the lasted and only one we need ...or don't need anymore ?
Thanks, i wan't able to find info for that.
That workaround is extremely unlikely to ever be embeded in Magisk...
Related
So I'm in the process of getting a GPS spoofer going and I flashed pre March 17' stock firmware (Safety net still passes), Installed TWRP (Safety net still passes), install Magisk Manager APK (Safety net still passes), boot into TWRP and install Magisk and Safety Net fails. All the guides I've read says this shouldn't happen? How do I fix it?
Please elaborate, send some screenshots, some logs or something useful...
But anyways, let's try one thing at least, have you tried going in: Magisk Manager > Settings > and enabling the "Hide Magisk Manager" option? If not, try it out. Does that make any difference?
Cheers
SpartanG01 said:
So I'm in the process of getting a GPS spoofer going and I flashed pre March 17' stock firmware (Safety net still passes), Installed TWRP (Safety net still passes), install Magisk Manager APK (Safety net still passes), boot into TWRP and install Magisk and Safety Net fails. All the guides I've read says this shouldn't happen? How do I fix it?
Click to expand...
Click to collapse
Which one fails? ctsProfile or basicIntegrity?
If ctsProfile fails, change device fingerprint using this https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228
If both basicIntegrity and ctsProfile fails, well that can't be helped... Maybe try installing the latest beta version of magisk if you didn't already
abacate123 said:
Please elaborate, send some screenshots, some logs or something useful...
But anyways, let's try one thing at least, have you tried going in: Magisk Manager > Settings > and enabling the "Hide Magisk Manager" option? If not, try it out. Does that make any difference?
Cheers
Click to expand...
Click to collapse
I don't know how to pull the logs or what would be useful here? As for screen shots, I dunno it's pretty cut and dry lol it passes without magisk installed and then fails both tests as soon as i install it. I hid Magisk using the feature you suggested and it did not change anything. Lookout actually warned me it was risk ware after i hid magisk. (I just flashed stock firmware so yeah, lookout is on there)
n1Bb135 said:
Which one fails? ctsProfile or basicIntegrity?
If ctsProfile fails, change device fingerprint using this https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228
If both basicIntegrity and ctsProfile fails, well that can't be helped... Maybe try installing the latest beta version of magisk if you didn't already
Click to expand...
Click to collapse
Yeah they both fail. I'll try the beta.
Edit: Beta Works!
SpartanG01 said:
I don't know how to pull the logs or what would be useful here?
Click to expand...
Click to collapse
There's a button called "Logs", right above the "Settings" button, when you open the Manager side menu.
Edit: Glad you got it working
SpartanG01 said:
So I'm in the process of getting a GPS spoofer going and I flashed pre March 17' stock firmware (Safety net still passes), Installed TWRP (Safety net still passes), install Magisk Manager APK (Safety net still passes), boot into TWRP and install Magisk and Safety Net fails. All the guides I've read says this shouldn't happen? How do I fix it?
Click to expand...
Click to collapse
Nice to see you got it sorted, but I just wanted to add that it's quite likely that you would have been able to get things working by just toggling MagiskHide off and on again. For future reference... :good:
Hii everyone i recently install a custom rom which is Pixel experience by Hardrock and just rooted using magisk Manager but in safetynet check ctsProfile is showing false Kindley please tell me how to fix this issue.
mukulkumars13 said:
Hii everyone i recently install a custom rom which is Pixel experience by Hardrock and just rooted using magisk Manager but in safetynet check ctsProfile is showing false Kindley please tell me how to fix this issue.
Click to expand...
Click to collapse
Flash this file via recovery ?
I had the same problem recently. The solution of MT above is correct but rather than flashing the file, I used Magisk Manager to download and install it. Go to Magisk's Download screen and search for "SafetyPatchv3".
EyeBalos said:
I had the same problem recently. The solution of MT above is correct but rather than flashing the file, I used Magisk Manager to download and install it. Go to Magisk's Download screen and search for "SafetyPatchv3".
Click to expand...
Click to collapse
Both method will affect same on your system.
Hi guys. I need some help for my rooted galaxy note 8. I had rooted my phone a long ago and all was working good. All apps including banking apps were working fine with magisk hide. But few days ago i wanted to update my phone so i flashed stock rom with odin and updated my device. Earlier my bootloader version was 6 and now its updated to version 8. Then after updating i flashed latest twrp and rooted with magisk. I flashed magisk version 20.1 and magisk manager version was 7.4.0 . Then magisk update was available so i updated to magisk version 20.2 and magisk manager to version 7.5.0 . Now the problem starts. I am facing 3 issues.
1- my phone starts freezing and then reboots randomly. It happens quite frequently atleast 2-3 times in a day. Every time i clear cache partition from twrp but problem persists. I had checked ram also but ram useage is also fine. Please help me with this issue.
2- while searching for the solution of above problem i read somewhere that it might be because of safety net check. Earlier safetynet check was pass but now safety net check was fail. I flashed bypass safety net mod. But when my phone reboot a warning appears that your device has some internal problem. Contact the manufacturer. I pressed ok and phone starts. It seems to work normal but then i realised my device was not connecting to any wifi network. When i click on available wifi nothing happened. So i uninstalled the safety net bypass mod and then wifi start working again.
3- now final thing i want to know. If the above problem did not solve then i have to unroot my phone which i dont want. But if i had to then i dont want to flash stock rom. I want to unroot from magisk app itself. I had edited build.prop file for using samsung health app. So now if i unroot from magisk app will the changes made by me in build.prop file remain or it will revert back. Also will banking apps work or not....
I know its very lengthy post but please help
Wow...
70 views no comment..... it seems all the developers and tech people are enjoying winter break
Try going back to previous version of Magisk. I have Snapdragon N8 so I have supersu. But I did update my A20g with newest Magisk and had an issue. I know you have N8 but was just saying maybe could be new Magisk.
My SM-N950U Still Rooted Note 8
After searching the forum thoroughly, trying multiple found solutions and trying to find the answer on my own I decided to ask here. What is the right procedure to clean flash A12 AOSP-based roms and getting root?
Some time ago, after updating to A11 rom, I noticed I can't use Magisk the way I used to to root my device - 'no ramdisk' status made me forget about rooting for a while. Now I want it back at any cost. This is why I want you to answer some of my questions, including the one above:
1. Is 'ramdisk: no' status caused by A11 and above versions?
2. Is there a way to have ramdisk status 'yes' on A12 ROM to root the device without having to patch boot.img?
3. Magisk installation doc has totally different way of rooting in my situation. According to it, for ramdisk status 'no' the only solution is 'Magisk in Recovery'. However, every time I saw someone talk about no ramdisk magisk patching, they were patching the boot image - it works fine and is even suggested by Magisk app. Who is wrong here and which solution is the right one?
4. Is there a way to get SafetyNet to pass on patched boot.img? Is there a way to get it to pass on a rooted A12 rom?
5. Some time ago, I have accidentally flashed european vendor instead of chinese one (I own chinese K20 Pro). I had no problems with it so I ran it for a few months and then flashed it back to chinese. Might this be the source of ramdisk issue?
Big thank you to anyone who replies. I have no important data on my device so there is no need for a data-safe solution. I feel like existing flashing/rooting guides seem outdated as they mention A10 at best. After more than 2 years of owning this device I still love it and am not going to replace it anytime soon and I hope there are still people like me! Cheers!
deadw0lf said:
After searching the forum thoroughly, trying multiple found solutions and trying to find the answer on my own I decided to ask here. What is the right procedure to clean flash A12 AOSP-based roms and getting root?
Some time ago, after updating to A11 rom, I noticed I can't use Magisk the way I used to to root my device - 'no ramdisk' status made me forget about rooting for a while. Now I want it back at any cost. This is why I want you to answer some of my questions, including the one above:
1. Is 'ramdisk: no' status caused by A11 and above versions?
2. Is there a way to have ramdisk status 'yes' on A12 ROM to root the device without having to patch boot.img?
3. Magisk installation doc has totally different way of rooting in my situation. According to it, for ramdisk status 'no' the only solution is 'Magisk in Recovery'. However, every time I saw someone talk about no ramdisk magisk patching, they were patching the boot image - it works fine and is even suggested by Magisk app. Who is wrong here and which solution is the right one?
4. Is there a way to get SafetyNet to pass on patched boot.img? Is there a way to get it to pass on a rooted A12 rom?
5. Some time ago, I have accidentally flashed european vendor instead of chinese one (I own chinese K20 Pro). I had no problems with it so I ran it for a few months and then flashed it back to chinese. Might this be the source of ramdisk issue?
Big thank you to anyone who replies. I have no important data on my device so there is no need for a data-safe solution. I feel like existing flashing/rooting guides seem outdated as they mention A10 at best. After more than 2 years of owning this device I still love it and am not going to replace it anytime soon and I hope there are still people like me! Cheers!
Click to expand...
Click to collapse
Although Magisk official guide on Github is not clear about, for MIUI you should patch boot.img, not recovery, and do not pay attention to Ramdisk no.
However, when patching boot.img, watch to the log window and you will see it reports there that it found Ramdisk
And that procedure works fine on A11 as well - I have it (MIUI 12.5.2 on my side)
I suppose you have the official A11 and you installed over custom A12 ROM).
Old Magisk v23 was released before A12, hence you should IMO go for the new Canary or Alpha 23016
Btw, you will be IMO better askung in the Magisk General XDA thread
zgfg said:
Although Magisk official guide on Github is not clear about, for MIUI you should patch boot.img, not recovery, and do not pay attention to Ramdisk no (when patching boot.img, watch to the log window and you will see it reports that it found Ramdisk)
And that procedure works fine on A11 as well - I have it (I suppose you have the official A11 and you installed over custom A12 ROM)
However, old Magisk v23 was released before A12, hence you should IMO go for the new Canary or Alpha 23016
Btw, you will be IMO better askung in the Magisk General XDA thread
Click to expand...
Click to collapse
Thank you for replying.
I am aware of Magisk Canary, I used it to root my current A12 rom. Yes, I flashed it over the latest chinese MIUI firmware. Is there any way to pass SafetyNet with it though?
deadw0lf said:
Thank you for replying.
I am aware of Magisk Canary, I used it to root my current A12 rom. Yes, I flashed it over the latest chinese MIUI firmware. Is there any way to pass SafetyNet with it though?
Click to expand...
Click to collapse
If you are on Canary 23016 (latest), you must enable Zygisk, and reboot
Then enable Enforce DenyList and go to Configure DenyList, enable Show System and OS apps, find Google Play Services and checkmark com.google.android.gms and
com.google.android.gms.unstable, and reboot again
If you were on the official, certified ROM, that would be enough to pass SafetyNet (since new Magisk app has no more the built-in SN checker, use one from PlayStore like YASNAC)
With your custom ROM you would probably need Universal Safety Net Fix= USNF 2.2.1 (latest).
Maybe even Magisk Hide Props Config (if USNF not enough) to spoof your unofficial/not Google certified ROM fingerprints - you will need to figure out (pain in the ass with custom ROMs)
zgfg said:
If you are on Canary 23016 (latest), you must enable Zygisk, and reboot
Then enable Enforce DenyList and go to Configure DenyList, enable Show System and OS apps, find Google Play Services and checkmark com.google.android.gms and
com.google.android.gms.unstable, and reboot again
If you were on the official, certified ROM, that would be enough to pass SafetyNet (since new Magisk app has no more the built-in SN checker, use one from PlayStore like YASNAC)
With your custom ROM you would probably need Universal Safety Net Fix= USNF 2.2.1 (latest).
Maybe even Magisk Hide Props Config (if USNF not enough) to spoof your unofficial/not Google certified ROM fingerprints - you will need to figure out (pain in the ass with custom ROMs)
Click to expand...
Click to collapse
This is exactly what I needed, thank you!
I dont have this model phone but i faced the same problem, i just flashed ArrowOS S along with magisk but i didnt realised it has now ramdisk no, before i was using AICP and it has ramdisk yes, so i installed latest version of magisk and the system updated but i dont have root anymore, what can i do?
I use OrangeBox for flashing
Edit: also it does replace the custom recovery?
Hello, I hope you can help me with this.
Yesterday I updated to the latest version of the custom rom I'm using (EvolutionX) and I had to flash the zip file manually through recovery since it didn't install automatically.
After that, magisk stopped working correctly, the root of my banking applications is not hidden, as you can see in the images, I have everything hidden and activated correctly (I think), I would appreciate it if you help me with this since the same thing happened to me a long time ago , and not finding a solution I had to do a hard reset and install a new rom.
The bank app says: "this device does not meet the minimum security requirements for this application"
(Sorry for my english, helpe pls)
alesky0903 said:
Hello, I hope you can help me with this.
Yesterday I updated to the latest version of the custom rom I'm using (EvolutionX) and I had to flash the zip file manually through recovery since it didn't install automatically.
After that, magisk stopped working correctly, the root of my banking applications is not hidden, as you can see in the images, I have everything hidden and activated correctly (I think), I would appreciate it if you help me with this since the same thing happened to me a long time ago , and not finding a solution I had to do a hard reset and install a new rom.
The bank app says: "this device does not meet the minimum security requirements for this application"
(Sorry for my english, helpe pls)
Click to expand...
Click to collapse
Hi, try updating the safety net fix module and also try this
Try Universal SafetyNet Fix 2.4.0 Mod by Displex
remove that old module and install te new one 2.4.0 mod