Related
as far as i know, no-one has managed to root on new firmware. Here's how i did it:
1. Get into developer mode by going to Settings -> About phone and keep on tapping 'Build number' until it says 'Congratulations, you are a developer'
2. exit 'About phone' and go to the new tab 'Developer options' and click 'USB debugging.' Press okay.
3. exit 'Developer options' and go to security, allow 'Unknown sources.'
4. Goto www(dot)kingroot(dot)net (can't do URLs. Srry). download the apk. if you downloaded it to your phone just install. if you downloaded it to pc use a usb to transfer or something- your choice on how it gets there- and install it on the phone.
5. run it and attempt root 2 times. both times should fail. straight after the second fail exit the app, shutdown and turn on. Do not reboot, as this doesn't work if you reboot.
6. Device should be rooted. Use Purify to check. If purify isn't installed, the process failed. If purify cant get root access, the process failed. Try an app that uses root. if a tab doesn't come up, the process failed.
this is how i rooted mine. not sure if it works generically or if it was one-time for me.
I posted it here, as there is no E4g forums, and this seemed like a popular place for the E4g posts.
Stay away from kingroot
Why must stay away from kingroot?
mie_shariff said:
Why must stay away from kingroot?
Click to expand...
Click to collapse
Kingroot dosent root the phone fully its an online root so you information can get access by the app, you phone can unroot any time etc..
I got my phone (SM-G950F a.k.a Samsung Galaxy S8) rooted about a year ago or so...and since, i update MM whenever needed but this time when i tried to update it, it says this:
Unsupported Magisk Version
This versio of Magisk Manager does not support Magisk version lower than v18.0
You can either manually upgrade Magisk, or downgrade the app to an older version.
I cannot go into the app cause that message will pop up and after i press ok it closes by itself!
Any ideea on how to fix this? If i have to re-root the phone please do explain..even then i didn't knew for sure how i did it, but i did it..
Thanks in advance!
Ahh... Me too. I'm sure this somewhere in the extensive Magisk coverage here. Is it too lazy to ask for a pointer to how to
--- downgrade the manager? That's probably easy if I know where to get the apk. Which version should I go for?
--- install the new magisk over the existing version, preferably without wiping the phone?
Sure, I'll search. But it is quite a while since I did anything with magisk, or anything that involved flashing, and I feel a bit lost.
Thad E Ginathom said:
Sure, I'll search. ... ... ...
Click to expand...
Click to collapse
OK, so there's a wiki and stuff. Whilst being babied would be nice, people have better things to do, and I guess I'll just start in reading that wiki and... stuff.
SOLUTION
Deathnes said:
I got my phone (SM-G950F a.k.a Samsung Galaxy S8) rooted about a year ago or so...and since, i update MM whenever needed but this time when i tried to update it, it says this:
Unsupported Magisk Version
This versio of Magisk Manager does not support Magisk version lower than v18.0
You can either manually upgrade Magisk, or downgrade the app to an older version.
I cannot go into the app cause that message will pop up and after i press ok it closes by itself!
Any ideea on how to fix this? If i have to re-root the phone please do explain..even then i didn't knew for sure how i did it, but i did it..
Thanks in advance!
Click to expand...
Click to collapse
Delete the Magisk Manager app as you would do with any other, download the proper version in .apk (check the official thread) and install it.
In the thread, under Sources, you have the link to the GitHub repo. Scrolling down you will find the README.MD file and the link to the Downloads page where all past releases are available.
From https://www.xda-developers.com/how-to-install-magisk/ you can read:
The Magisk framework is now installed on your device. To manage it, you’ll need the aptly named Magisk Manager. This is what will allow you to install modules. Download the latest Magisk Manager APK here and make sure you have “Unknown sources” enabled in the Settings. Install the app and open it up.
The Manager app allows you to adjust root settings and also install modules, which are installable mods. The app doubles as a repository for a bunch of great modules that can easily extend the functionality of your device. Using the Manager app is an important part of getting the most out of this root method.
Click to expand...
Click to collapse
That is, the app Magisk Manager is independent from the Magisk framework you have installed. Deleting the app does not affect Magisk.
vomae said:
... ... ... the Downloads page where all past releases are available.
Click to expand...
Click to collapse
I'd reached there, although not done it yet. As you say, my phone is still working, Magisk is still working, it is just the manager app that needs dealing with. None the less, I appreciate your time and effort. You paint a clear picture for others who come this way.
Thanks.
Open the updated app & ignore the error, then checkout the option showing update magisk(not manager), go for it, dont select any preservations & click on direct install(which is recommended by app itself).
Flashing of the update will begin, then after reboot your problem is solved.
Magisk Manager has many improvements and features over the last year...
Hello:
I need help with setting up the magisk manager which is now the magisk app.
I downloaded the magisk manager app some weeks back, but I never set it up. But when I checked it out some hours ago, I discovered that it had been updated to magisk 22.0. The magisk manager is said to be dead, and we now have a new magisk app.
So, my question now is: how do I set it up for use. Please give me a comprehensive tutorial on the installation and set up.
I am made to understand that the app now comes with a custom recovery and there is no need to install one any longer.
When I am on the installation screen, I find preserve ADB 2.0 for DM veritycheckbox: and preserve force encryption: checkbox. Then I find method: I don't understand these checkboxes. Which do I check and which do I uncheck.
I find the next button on the right side of the screen, and when I tap on it, I find option on the top of the screen, then I then find select and pach a file radio button: the box here is unchecked. I don't know what to do here.
Then there is the let's go button, which is disabled.
Then after the installation, how do I now use it to root my phone.
So, I am a layman here, and I need help with all these. Please help me out.
I have a Samsung galaxy grand prime J2 phone.
I am also a blind android user, as I use the screen reader talkback to access the phone.
Thanks for your assistance.
This is a tutorial on how to set up your phone so that you can consistently pass SafetyNet. Note that all this is from my own experience, and if what works on one device blows up another, that's not my problem and I'm not responsible for that. I will attempt to keep this tutorial as clean and simple as possible, but if you have any further questions that are more specific you are welcome to ask.
In order to be as simple as possible to understand, this guide assumes the following:
- You have a PC. Windows, Mac, the almighty Linux, it makes no difference.
- You have the android platform tools on your PC
- Your device has an unlocked bootloader.
- Your device does not have support for signature spoofing.
- Your device does not have Google's official play services on it.
- You have a working brain.
If one or more of the above is incorrect, you'll have to make more use of the last item on the list.
If the last item on the list is incorrect, you're beyond hope.
Now, the guide:
Step 1: Get some magisk on your phone
Setting up magisk is incredibly simple, and I won't be going into detail here. I would recommend installing the regular magisk app and patching your boot image, as that is what I've done.
Note that you do not need the magisk manager app for this guide at all.
I've attached the magisk app I used to this post. You'll need to install the app and make use of the "install" section of the home page.
Once magisk is installed and set up, you'll need to enable zygisk in the magisk settings. Then reboot.
Step 2: Installing MicroG
I am not going to list through all the possible way you can install microG. Instead, have a link to microG's wiki:
index - MicroG
r/MicroG: Subreddit about microG, a free-as-in-freedom re-implementation of Google’s proprietary Android user space apps and libraries. This …
www.reddit.com
Now here comes the important bit:
From everything I have seen, it appears clear that google stores information about each device that registers with it, and that this in turn will affect SafetyNet.
Therefore, the best way to prevent this leading to SafetyNet failing is to prevent connection with google completely - till the phone is ready.
Before you install microG, make sure your phone has both wifi and data turned off. Leave these off till the setup is complete. Note that only the phone needs to be disconnected, nothing else matters.
In essence, this means that google sees nothing till your device is setup correctly, and then SafetyNet has nothing to complain about.
Now that you've read every word of the above paragraph, go ahead and install microG on your phone.
Make sure you've got all the different components: Core, GSF Framework, FakeStore, and DroidGuard helper. If your installation method does not handle all of this for you, then it sucks, and you shouldn't have used it. Regardless, you can find apks for all of these at https://microg.org/
Step 3: Don't touch
As I've already made clear above, do not change any microG settings at this point. Don't enable device registration (if it's disabled), don't enable safetynet, and just generally leave microG settings alone for now. Oh yeah, and don't turn on wifi or data.
Step 4: Tricking SafetyNet
Everything up till now has just been preparation for actually tricking SafetyNet. So now that we've got all that out the way, let's get down to details:
First, downloads:
Download the latest zip: https://themagisk.com/magiskhide-props-config/
Download the latest zygisk zip: https://themagisk.com/universal-safetynet-fix/
Move these over to your phone and install them both as magisk modules.
Once these modules are installed and you've rebooted, connect your phone to your pc.
Open a terminal/command prompt in your platform tools folder, and type "adb shell props". You may need to grant the superuser permission from your phone.
Then choose option 1.
You'll then need to choose a device from the list available.
The key here is that we need to spoof our device fingerprint, so google thinks the device is certified, even if it actually isn't.
If your device is approved by google, then simply select your device model.
If not, things get a bit more unclear. Not every fingerprint will work for every device - If your device is vastly different from the one you are trying to spoof things may not always work correctly. The best advice I can give here is to choose a device that matches yours as closely as possible. As an example: if your device is made by Xiaomi but is not approved by google, I would select a fingerprint belonging to a Xiaomi device.
Keep in mind that if you try a fingerprint that does not work, you cannot simply switch it to something else and try again, as the SafetyNet history for the device has to be clean.
Once you've spoofed your device fingerprint and rebooted, you're almost ready to test out SafetyNet and google sign in. But first:
Step 5: Do you need signature spoofing?
To ensure things work as smoothly as possible, it's important to make sure you have signature spoofing working before you test SafetyNet. If you've got your own solution to that great. If not:
The first thing I have to point out is that a lot of sigspoof methods on google nowadays are outdated and semi-functional at best, working for a handful of devices. As this guide is intended to be a universal solution regardless of your device, the only answer is lsposed and fakegapps.
Download the latest zygisk zip: https://themagisk.com/lsposed/
Transfer it to your phone and install it as a magisk module.
I've attached the full lsposed manager apk to this post, as the parasitic one sucks. Install it and the fakegapps apk which I've also attached to this post.
You'll now need to enable fakegapps, and turn it on for anything that might need access to spoofing. This includes the system framework, all the microG stuff, and any app that needs to be fooled by microg. Then reboot.
Step 6: Ready to test
Everything should now be set up correctly.
Check the microG settings to make sure signatures are correctly being spoofed.
Enable device registration (if disabled).
Enable SafetyNet attestation.
At this point your phone should still be completely disconnected from the internet.
If you're happy everything is set up correctly, turn on your wifi or data, and test SafetyNet attestation.
Step 7: Done.
Hopefully you now have working SafetyNet and google sign in. If this does work for you, it means that safetynet is now stable on your device, and you are free to install whatever you want on it.
If it didn't work, keep in mind that this hasn't been tested on every device in existence. All I know is that this consistently works for me.
If your phone doesn't turn on, you probably need to charge it.
If your phone has exploded, you probably have a Samsung.
Thanks everyone for reading my guide, I hope you enjoyed! (Maybe it even worked)
RESERVED FOR STUFF
Your guide is well made but I have some things I would change.
1) Since everything has to be done offline and adb is used in linux installation at least I would recommend adding an tip with adb push ~/Downloads/safetynet-tools.zip /storage/emulated/0/Downloads.
Furthermore cause of it I recommend attaching a single zip with
tools so they can be moved easily to the device.
2) there is missing Information: you said in the guide that safety net trips extremely easily. During the entire process the device cant be connected to the internet but what if you want to install another app. For example what if you want to install another app later lets say Netflix for example. I know for a fact it requires safetynet. It would be configured automatically will it? This would conclude to permanetley lock safety net till its reinstalled.
hypethetime said:
Your guide is well made but I have some things I would change.
1) Since everything has to be done offline and adb is used in linux installation at least I would recommend adding an tip with adb push ~/Downloads/safetynet-tools.zip /storage/emulated/0/Downloads.
Furthermore cause of it I recommend attaching a single zip with
tools so they can be moved easily to the device.
Click to expand...
Click to collapse
Hi, I think you may have misunderstood slightly. Only the phone has to be offline, you can still connect it to a PC and download the files on the PC. The only important thing is that the device doesn't communicate with google till you are ready for it to.
hypethetime said:
2) there is missing Information: you said in the guide that safety net trips extremely easily. During the entire process the device cant be connected to the internet but what if you want to install another app. For example what if you want to install another app later lets say Netflix for example. I know for a fact it requires safetynet. It would be configured automatically will it? This would conclude to permanetley lock safety net till its reinstalled.
Click to expand...
Click to collapse
Once the process is complete, you can install whatever else you want and safetynet will not stop working. The main thing is that the process of setting up the device so that it can be approved is very easy to mess up, so that part has to be done carefully.
I'll edit the guide to make these points more clear.
Sense_101 said:
Hi, I think you may have misunderstood slightly. Only the phone has to be offline, you can still connect it to a PC and download the files on the PC. The only important thing is that the device doesn't communicate with google till you are ready for it to.
Click to expand...
Click to collapse
I knew you always were able to use pc and you miss understood me. I at least often had the problem with transferring files for some reseason and for this adb push is extremey helpful.
Regarding instaling more apps thank you for the answer and how quickly it came.
Sense_101 said:
This is a tutorial on how to set up your phone so that you can consistently pass SafetyNet. Note that all this is from my own experience, and if what works on one device blows up another, that's not my problem and I'm not responsible for that. I will attempt to keep this tutorial as clean and simple as possible, but if you have any further questions that are more specific you are welcome to ask.
In order to be as simple as possible to understand, this guide assumes the following:
- You have a PC. Windows, Mac, the almighty Linux, it makes no difference.
- You have the android platform tools on your PC
- Your device has an unlocked bootloader.
- Your device does not have support for signature spoofing.
- Your device does not have Google's official play services on it.
- You have a working brain.
If one or more of the above is incorrect, you'll have to make more use of the last item on the list.
If the last item on the list is incorrect, you're beyond hope.
Now, the guide:
Step 1: Get some magisk on your phone
Setting up magisk is incredibly simple, and I won't be going into detail here. I would recommend installing the regular magisk app and patching your boot image, as that is what I've done.
Note that you do not need the magisk manager app for this guide at all.
I've attached the magisk app I used to this post. You'll need to install the app and make use of the "install" section of the home page.
Once magisk is installed and set up, you'll need to enable zygisk in the magisk settings. Then reboot.
Step 2: Installing MicroG
I am not going to list through all the possible way you can install microG. Instead, have a link to microG's wiki:
index - MicroG
r/MicroG: Subreddit about microG, a free-as-in-freedom re-implementation of Google’s proprietary Android user space apps and libraries. This …
www.reddit.com
Now here comes the important bit:
From everything I have seen, it appears clear that google stores information about each device that registers with it, and that this in turn will affect SafetyNet.
Therefore, the best way to prevent this leading to SafetyNet failing is to prevent connection with google completely - till the phone is ready.
Before you install microG, make sure your phone has both wifi and data turned off. Leave these off till the setup is complete. Note that only the phone needs to be disconnected, nothing else matters.
In essence, this means that google sees nothing till your device is setup correctly, and then SafetyNet has nothing to complain about.
Now that you've read every word of the above paragraph, go ahead and install microG on your phone.
Make sure you've got all the different components: Core, GSF Framework, FakeStore, and DroidGuard helper. If your installation method does not handle all of this for you, then it sucks, and you shouldn't have used it. Regardless, you can find apks for all of these at https://microg.org/
Step 3: Don't touch
As I've already made clear above, do not change any microG settings at this point. Don't enable device registration (if it's disabled), don't enable safetynet, and just generally leave microG settings alone for now. Oh yeah, and don't turn on wifi or data.
Step 4: Tricking SafetyNet
Everything up till now has just been preparation for actually tricking SafetyNet. So now that we've got all that out the way, let's get down to details:
First, downloads:
Download the latest zip: https://themagisk.com/magiskhide-props-config/
Download the latest zygisk zip: https://themagisk.com/universal-safetynet-fix/
Move these over to your phone and install them both as magisk modules.
Once these modules are installed and you've rebooted, connect your phone to your pc.
Open a terminal/command prompt in your platform tools folder, and type "adb shell props". You may need to grant the superuser permission from your phone.
Then choose option 1.
You'll then need to choose a device from the list available.
The key here is that we need to spoof our device fingerprint, so google thinks the device is certified, even if it actually isn't.
If your device is approved by google, then simply select your device model.
If not, things get a bit more unclear. Not every fingerprint will work for every device - If your device is vastly different from the one you are trying to spoof things may not always work correctly. The best advice I can give here is to choose a device that matches yours as closely as possible. As an example: if your device is made by Xiaomi but is not approved by google, I would select a fingerprint belonging to a Xiaomi device.
Keep in mind that if you try a fingerprint that does not work, you cannot simply switch it to something else and try again, as the SafetyNet history for the device has to be clean.
Once you've spoofed your device fingerprint and rebooted, you're almost ready to test out SafetyNet and google sign in. But first:
Step 5: Do you need signature spoofing?
To ensure things work as smoothly as possible, it's important to make sure you have signature spoofing working before you test SafetyNet. If you've got your own solution to that great. If not:
The first thing I have to point out is that a lot of sigspoof methods on google nowadays are outdated and semi-functional at best, working for a handful of devices. As this guide is intended to be a universal solution regardless of your device, the only answer is lsposed and fakegapps.
Download the latest zygisk zip: https://themagisk.com/lsposed/
Transfer it to your phone and install it as a magisk module.
I've attached the full lsposed manager apk to this post, as the parasitic one sucks. Install it and the fakegapps apk which I've also attached to this post.
You'll now need to enable fakegapps, and turn it on for anything that might need access to spoofing. This includes the system framework, all the microG stuff, and any app that needs to be fooled by microg. Then reboot.
Step 6: Ready to test
Everything should now be set up correctly.
Check the microG settings to make sure signatures are correctly being spoofed.
Enable device registration (if disabled).
Enable SafetyNet attestation.
At this point your phone should still be completely disconnected from the internet.
If you're happy everything is set up correctly, turn on your wifi or data, and test SafetyNet attestation.
Step 7: Done.
Hopefully you now have working SafetyNet and google sign in. If this does work for you, it means that safetynet is now stable on your device, and you are free to install whatever you want on it.
If it didn't work, keep in mind that this hasn't been tested on every device in existence. All I know is that this consistently works for me.
If your phone doesn't turn on, you probably need to charge it.
If your phone has exploded, you probably have a Samsung.
Thanks everyone for reading my guide, I hope you enjoyed! (Maybe it even worked)
Click to expand...
Click to collapse
I have a Samsung galaxy note 10 plus running LineageOS 19.1. I'ts unlocked, and rooted with Magisk. Is there something about Samsung phones that are more likely to "explode" trying to install MicroG?
WheelingPigeon said:
I have a Samsung galaxy note 10 plus running LineageOS 19.1. I'ts unlocked, and rooted with Magisk. Is there something about Samsung phones that are more likely to "explode" trying to install MicroG?
Click to expand...
Click to collapse
Yeah, that's a joke
WheelingPigeon said:
I have a Samsung galaxy note 10 plus running LineageOS 19.1. I'ts unlocked, and rooted with Magisk. Is there something about Samsung phones that are more likely to "explode" trying to install MicroG?
Click to expand...
Click to collapse
Samsung phones have a history of "blowing" up. First they were actually dangerous in very few cases but now they can expand and pop of the back of your phone. As long as you switch the battery then your safe to use it.
AOSP Rom (signature spoofing unsupported, without MicroG installer)
After Root install patch for spoofing via NanoDroid Patcher
Open Magisk settings -> Enable Zygisk + Enforce DenyList, install module MagiskHide Props Config -> reboot
Open Termux or ADB, type su to set root permission then type props (option 1)
Install MicroG via APK or offical F-Droid app, grant Signature spoofing permission
If you want using play store, install patched version (F-Droid add repo NanoDroid)
Open MicroG Settings -> Self-Check -> make sure all box checked
Turn on Google device registration, Google SafetyNet, if CTS fail then install Universal SafetyNet Fix
Install magisk module App Systemizer, Busybox for Android NDK to change MicroG to system app
When I first rooted my phone, everything was fine but after a few days some apps started showing up as "This app won't work on your device"
It wouldn't be a problem since I can just download the APK's, but I need to use the Revolut app, it is only available as a mobile app and when you don't install it from the Play store, it just doesn't work.
Can anyone show me a workaround for this?
Maybe a way to trick play store into letting me download all the apps as usual
or a way to trick the app into thinking it's been installed from the play store.
I thought about locking the bootloader again (OEM) but it'll wipe all data, and I don't want that. Because it's been a few months since I rooted my phone and I have a lot of data.
My phone is Samsung Galaxy S10E - SM-G970F if this info means anything.
hmm, try unrooting it, install all apps you need, and then re-root it again.
NikolaTechGuy said:
hmm, try unrooting it, install all apps you need, and then re-root it again.
Click to expand...
Click to collapse
Rooting wipes all the data tho
Quidney said:
When I first rooted my phone, everything was fine but after a few days some apps started showing up as "This app won't work on your device"
It wouldn't be a problem since I can just download the APK's, but I need to use the Revolut app, it is only available as a mobile app and when you don't install it from the Play store, it just doesn't work.
Can anyone show me a workaround for this?
Maybe a way to trick play store into letting me download all the apps as usual
or a way to trick the app into thinking it's been installed from the play store.
I thought about locking the bootloader again (OEM) but it'll wipe all data, and I don't want that. Because it's been a few months since I rooted my phone and I have a lot of data.
My phone is Samsung Galaxy S10E - SM-G970F if this info means anything.
Click to expand...
Click to collapse
you must pass safetynet as well as play integrity api in order for the apps to reappear. You can check this status by downloading the application YASNAC for safetynet status and Play Integrity API checker for checking play integrity status.
If your using magisk then you can flash safetynetfix module from here.
Flashing it should make the Basic integrity and cts profile check from False to true in yasnac
It should also turn Basic Integrity and Device Integrity from a Cross to a Tick
Strong integrity will always fail for rooted users. so forget abt that
Then go to apps > find playstore > storage > clear data
Open playstore again and you'll see an outdated UI dont worry it'll restore on the next app opening
in playstore then tap on your profile picture at the top right then go to settings. Scroll down and see if the device is play protect certified.
If it is the apps should reappear.
This is way too overkill tbh. you could just install Aurora store and call it a day since its litt playstore without accounts and stuff.
Captain_cookie_200 said:
you must pass safetynet as well as play integrity api in order for the apps to reappear. You can check this status by downloading the application YASNAC for safetynet status and Play Integrity API checker for checking play integrity status.
If your using magisk then you can flash safetynetfix module from here.
Flashing it should make the Basic integrity and cts profile check from False to true in yasnac
It should also turn Basic Integrity and Device Integrity from a Cross to a Tick
Strong integrity will always fail for rooted users. so forget abt that
Then go to apps > find playstore > storage > clear data
Open playstore again and you'll see an outdated UI dont worry it'll restore on the next app opening
in playstore then tap on your profile picture at the top right then go to settings. Scroll down and see if the device is play protect certified.
If it is the apps should reappear.
This is way too overkill tbh. you could just install Aurora store and call it a day since its litt playstore without accounts and stuff.
Click to expand...
Click to collapse
Yes but if I install it from the Aurora store I won't be able to use Revolut probably.
Also I installed the module, and though the YASNAC check has 2 ticks, the Play Integrity checker says failed on "Device integrity" and "strong integrity." What do i do then?
Quidney said:
Yes but if I install it from the Aurora store I won't be able to use Revolut probably.
Also I installed the module, and though the YASNAC check has 2 ticks, the Play Integrity checker says failed on "Device integrity" and "strong integrity." What do i do then?
Click to expand...
Click to collapse
hm what method of rooting do you use?
Captain_cookie_200 said:
hm what method of rooting do you use?
Click to expand...
Click to collapse
if you flashed the safetynet fix in magisk already then im afriad i dont know what else is wrong
Captain_cookie_200 said:
hm what method of rooting do you use?
Click to expand...
Click to collapse
Downloaded the firmware, and changed it using magisk, flashed it using ODIN.
It's Magisk 25.2
Zygisk: Yes
Ramdisk: No
But I also have the "Hide Magisk" option, and Systemless Hosts module
Captain_cookie_200 said:
if you flashed the safetynet fix in magisk already then im afriad i dont know what else is wrong
Click to expand...
Click to collapse
Yep I did.
Quidney said:
Yep I did.
Click to expand...
Click to collapse
i dont know then. i passed safety net on one ui 5 on galaxy A32 4G using that module
Captain_cookie_200 said:
i dont know then. i passed safety net on one ui 5 on galaxy A32 4G using that module
Click to expand...
Click to collapse
I also passed the check after the 25th reboot. It took some time to adjust I guess.
But I cannot hide my magisk launcher, it gets detected by Revolut. Welp
Quidney said:
I also passed the check after the 25th reboot. It took some time to adjust I guess.
But I cannot hide my magisk launcher, it gets detected by Revolut. Welp
Click to expand...
Click to collapse
Actually there is a way to fix that as well.
First of all go to magisk then press the gear icon on top right then select Hide the Magisk app. Allow it to install unknown apps. Give it a good name Let it do its work. do not go to home or anywhere while it is reinstalling the apk as something else
Second of all download shamiko from here.
First make sure you have enforce denylist disabled in the magisk's settings. Yep disabled. if it is enabled toggle it off
Then flash shamiko and reboot. Now once you boot back into the system. Open magisk again (or the new reinstalled renamed magisk app) and go to settings and then go to configure denylist. Now find your app and press the checkbox
Now see if it bypasses the root detection. if not then clear all your apps in your recents and try again. This trick always helps to get around apps with root checks.
Captain_cookie_200 said:
Actually there is a way to fix that as well.
First of all go to magisk then press the gear icon on top right then select Hide the Magisk app. Allow it to install unknown apps. Give it a good name Let it do its work. do not go to home or anywhere while it is reinstalling the apk as something else
Second of all download shamiko from here.
First make sure you have enforce denylist disabled in the magisk's settings. Yep disabled. if it is enabled toggle it off
Then flash shamiko and reboot. Now once you boot back into the system. Open magisk again (or the new reinstalled renamed magisk app) and go to settings and then go to configure denylist. Now find your app and press the checkbox
Now see if it bypasses the root detection. if not then clear all your apps in your recents and try again. This trick always helps to get around apps with root checks.
Click to expand...
Click to collapse
Just noticed since you have magisk hide your either using magisk delta or an older version of magisk. I guess you could just use magisk hide but incase that isnt working the method above is the way to go.
Captain_cookie_200 said:
Just noticed since you have magisk hide your either using magisk delta or an older version of magisk. I guess you could just use magisk hide but incase that isnt working the method above is the way to go.
Click to expand...
Click to collapse
I have 25.2 (25200), Zygisk.
But There's an option in the settings right now it says "Restore the Magisk App" because I've already hidden it.
Captain_cookie_200 said:
Actually there is a way to fix that as well.
First of all go to magisk then press the gear icon on top right then select Hide the Magisk app. Allow it to install unknown apps. Give it a good name Let it do its work. do not go to home or anywhere while it is reinstalling the apk as something else
Second of all download shamiko from here.
First make sure you have enforce denylist disabled in the magisk's settings. Yep disabled. if it is enabled toggle it off
Then flash shamiko and reboot. Now once you boot back into the system. Open magisk again (or the new reinstalled renamed magisk app) and go to settings and then go to configure denylist. Now find your app and press the checkbox
Now see if it bypasses the root detection. if not then clear all your apps in your recents and try again. This trick always helps to get around apps with root checks.
Click to expand...
Click to collapse
I'm on the phone with my friend while she sleeps so I cannot reboot the phone >_<
But I'll update you tomorrow probably if it works.
Quidney said:
I have 25.2 (25200), Zygisk.
But There's an option in the settings right now it says "Restore the Magisk App" because I've already hidden it.
Click to expand...
Click to collapse
oh i see. wait how.do you have magisk hide then
Quidney said:
I'm on the phone with my friend while she sleeps so I cannot reboot the phone >_<
But I'll update you tomorrow probably if it works.
Click to expand...
Click to collapse
oh i see. i just tested it on my device and yes it works. the shamiko method is listed prevents the root detection. hope it works fine for you
Captain_cookie_200 said:
oh i see. wait how.do you have magisk hide then
Click to expand...
Click to collapse
I don't have "Magisk Hide" I think that is another feature (Superuser -> Hide) which does not exist for me.
Quidney said:
I don't have "Magisk Hide" I think that is another feature (Superuser -> Hide) which does not exist for me.
Click to expand...
Click to collapse
magisk hide was removed. anyways try the shamiko method and tell if it works
Captain_cookie_200 said:
magisk hide was removed. anyways try the shamiko method and tell if it works
Click to expand...
Click to collapse
Yep everything worked out. I have Revolut now, and it doesn't detect magisk or root.
I still don't have Google Pay, but that's a job for future me.