Related
This is a starter thread for getting Nintendo's latest Android app (which has finally come from iOS over three months later), Super Mario Run, to work on Android devices that have been rooted and possibly have no Google Play Store installed. Developers, please contribute your findings!
It worked with root but I got an error when I finished the tutorial. Then I saved my game with a Nintendo account and I cleared game data. I've used magisk hide with this game and I can play again
apfo said:
It worked with root but I got an error when I finished the tutorial. Then I saved my game with a Nintendo account and I cleared game data. I've used magisk hide with this game and I can play again
Click to expand...
Click to collapse
I used magisk too but I can't find where I can hide.. can you help me? Do I need to install a module?
n0m1s said:
I used magisk too but I can't find where I can hide.. can you help me? Do I need to install a module?
Click to expand...
Click to collapse
After you've installed Magisk you just need to go to the Settings in the Magisk Manager APP and enable Magiskhide and then you should See a new tab for Magisk hide in the Manager APP and just select the Apps you want to hide root.
(Sorry for my Bad English)
ApollosRage said:
After you've installed Magisk you just need to go to the Settings in the Magisk Manager APP and enable Magiskhide and then you should See a new tab for Magisk hide in the Manager APP and just select the Apps you want to hide root.
(Sorry for my Bad English)
Click to expand...
Click to collapse
Thanks for that, but it's not working too
ApollosRage said:
After you've installed Magisk you just need to go to the Settings in the Magisk Manager APP and enable Magiskhide and then you should See a new tab for Magisk hide in the Manager APP and just select the Apps you want to hide root.
(Sorry for my Bad English)
Click to expand...
Click to collapse
I did exactly what you did and it worked fine for me.
So do I flash via twrp the zip in the magisk post?
I use magisk to hide mario but when i pass the tutorial send error 804 5100 and have to delete the Account:.xml located in /data/data/com.nintendo.zara/sharedfolder and then log in with my account so brings my save but i complete 1 course and the same error again and have to do it all over again, does anybody find a solution for this?
Is magisk a supersu replacement or can I just install alongside? It also says it requires 5.x so no 4.4?
Magisk work great for me
simbin said:
Is magisk a supersu replacement or can I just install alongside? It also says it requires 5.x so no 4.4?
Click to expand...
Click to collapse
it is a supersu replacement but the magisk is great and has better functions and the moduls are great, forget the turning off part and the the recovery and flash the zip, the magisk do it all for you!
Mago6246 said:
it is a supersu replacement but the magisk is great and has better functions and the moduls are great, forget the turning off part and the the recovery and flash the zip, the magisk do it all for you!
Click to expand...
Click to collapse
Don't think magisk works with cm12 on Amzn Fire Phone bc bootloader isn't actually unlocked. They should limit SafetyNet to Leaderboards - pretty sure that's what all the fuss is about. Fine, Nintendont take my money!
Magisk Manager won't install Magisk on my rooted S7 Edge. I've read that it's not compatible with Samsung devices right now, don't know if that's true. How else can I make Super Mario Run work?
suhide give me bootloop with lineos so I will try magisk
simbin said:
Is magisk a supersu replacement or can I just install alongside? It also says it requires 5.x so no 4.4?
Click to expand...
Click to collapse
Yes, You can use it alongside with SuperSU.
Hi !
Same error for me... I installed Magisk, uninstalled SuperSU, set the Super Mario App to hide but i still get the error...
Did I miss something ?
Thanks
Rooted Nexus 5 running Cataclysm 6.0.1
Miitomo was patched using a special security bypasser made for it, and also with XPosed and RootCloak. Is there a similar method for those who seem to have issues using Magisk?
I myself haven't tried Magisk. I'll see how it works on my Galaxy S7. :fingers-crossed:
Xda, please merge this thread with the other thread that I made. I accidentally made a duplicate.
I do not have Google Play services installed, and it seems to need it.
I'm currently running Magisk with Magisk Hide on and RootCloak as well and it keeps erroring out. Currently the only workaround I've found is deleting the deviceAccount xml file in the app prefs folder. I have a feeling it has something to do with xposed or safetynet that's causing it to fail. I enjoy the game enough that I wouldn't mind buying it, but not if Nintendo is going to lock users out like this.
So I unlocked bootloader and rooted my phone through SuperSu yesterday and flashed a custom rom (RRemix for OnePlus 2) and at first I used Magisk, so I flashed the ROM -> Magisk and then GApps but that didn't grant me root access after checking in the root checker app. I then wiped everything in TWRP and this time flashed ROM -> SuperSu and then GApps and it worked and I had root with no issues. Just wondering why Magisk didn't work here as I heard it's the superior Rooting app.
I don't like messing with my phone too much so if I'm already going through with rooting I might as well use the best programs. I also made sure to use the latest downloads and files so no issues there.
Also, in LineageOS settings it's telling me 'Root Access Disabled' even though Root Checker app is telling me I have root and I can access Root Explorer in ES File Explorer. Is it meant to be like that?
Thanks in advance, I'm new here so my bad if I posted it in the wrong section
Zainn said:
So I unlocked bootloader and rooted my phone through SuperSu yesterday.........
Click to expand...
Click to collapse
I don't have this device but, your best bet is to post this question within the following Q&A thread that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=3146584
Good Luck!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Commodore VIC-20.
"Can't load Android system" and "Factory data reset" tried and does not work
Hi all,
I bought a Pixel 3a, unlocked the bootloader, upgraded it to Android 10, and then tried to root it with Magisk. I must somehow have missed a step because now the phone only boots to:
Android Recovery
google/sargo/sargo
9/PQ3B.190801.002/5674421
user/release-keys
Use volume up/down and power.
Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device.
Try again
Factory data reset
If I "Try again" I end up in the same place after a long time with the Google logo and a reboot. If I "Factory data reset" I also end up in the same place.
My desktop has adb and fastboot, and was able to access the phone until the failed attempt at rooting. Now it does not detect the phone despite the system "bleeping" as if it has found a new device:
>adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
>adb devices
List of devices attached
Is there a way out of this mess?
FD
You're still on P by what recovery says. 0801 image. PQ3B is P. You want QP1A. Please try downloading the recent Q image and follow the official instructions from Google in the link and try again.
https://developers.google.com/android/images
Uzephi said:
You're still on P by what recovery says. 0801 image. PQ3B is P. You want QP1A. Please try downloading the recent Q image and follow the official instructions from Google in the link and try again.
https://developers.google.com/android/images
Click to expand...
Click to collapse
Thank you very much! Using the flash-all script I have managed to get my phone back. I have flashed the original Android 9 the phone came with.
Now, one further question, are there some good (as in unlikely to brick my phone again) instructions on how to root my Pixel 3a? I believe that Android 9 is preferred when using Magisk to Android 10, and I do not mind staying with Android 9, but I would like some instructions on how to root it without bricking it again.
Again, thanks for your prompt reply.
Yours,
FD
Frederick Davies said:
Thank you very much! Using the flash-all script I have managed to get my phone back. I have flashed the original Android 9 the phone came with.
Now, one further question, are there some good (as in unlikely to brick my phone again) instructions on how to root my Pixel 3a? I believe that Android 9 is preferred when using Magisk to Android 10, and I do not mind staying with Android 9, but I would like some instructions on how to root it without bricking it again.
Again, thanks for your prompt reply.
Yours,
FD
Click to expand...
Click to collapse
I followed this guide. it's for a pixel 3 but it's exactly the same for a 3a. There is no TWRP for 10 so doing it this way is the only way for now.
https://android.gadgethacks.com/how-to/root-your-pixel-3-android-10-0200295/
Just use magisk to patch Android 10 boot IMG and Flash it and your rooted on Android 10
Frederick Davies said:
Now, one further question, are there some good (as in unlikely to brick my phone again) instructions on how to root my Pixel 3a? I believe that Android 9 is preferred when using Magisk to Android 10, and I do not mind staying with Android 9, but I would like some instructions on how to root it without bricking it again.
Again, thanks for your prompt reply.
Yours,
FD
Click to expand...
Click to collapse
I have created a (IMHO) very thorough quide on how to root your Pixel 3a. It walks you through rooting with both Android Pie and Android 10 with very clear and precise steps. If you have any questions about it, feel free to post in that thread or reach out to me via a direct message.
There is no limitation on using Magisk or rooting under Android 10. The only thing you cannot do with Android 10 is use TWRP, but that isn't a deal breaker. TWRP is good for making backups of your OS, but as you have found you can still recover from just about any situation using the Google factory images, so while a backup might be beneficial at times, it isn't a necessity. Personally I would definitely recommend using Android 10 because Pie isn't being updated by Google anymore, so you are going to be behind on security updates, etc if you stick with Pie.
Watch this video and you shouldn't have any problems
sic0048 said:
I have created a (IMHO) very thorough quide on how to root your Pixel 3a. It walks you through rooting with both Android Pie and Android 10 with very clear and precise steps. If you have any questions about it, feel free to post in that thread or reach out to me via a direct message.
Click to expand...
Click to collapse
Very detailed indeed, but I still have a question: in your instructions you seem to boot into TWRP to install Magisk, but you do NOT install TWRP itself, just boot it for the installation of Magisk. Is that correct? Why?
sic0048 said:
There is no limitation on using Magisk or rooting under Android 10. The only thing you cannot do with Android 10 is use TWRP, but that isn't a deal breaker. TWRP is good for making backups of your OS, but as you have found you can still recover from just about any situation using the Google factory images, so while a backup might be beneficial at times, it isn't a necessity. Personally I would definitely recommend using Android 10 because Pie isn't being updated by Google anymore, so you are going to be behind on security updates, etc if you stick with Pie.
Click to expand...
Click to collapse
I am going through all this rigmarole to be able to install XPrivacyLua through the Xposed Framework, but the instructions for Xposed (https://www.xda-developers.com/xposed-framework-hub/) seem to indicate you need TWRP as a requisite, hence I think am stuck with Android P (9.0).
On the other hand, I get conflicting information as to whether Xposed for Magisk does (https://www.xda-developers.com/xposed-framework-hub/) or does not (https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268) pass SafetyNet. Most confusing...
FD
Frederick Davies said:
Very detailed indeed, but I still have a question: in your instructions you seem to boot into TWRP to install Magisk, but you do NOT install TWRP itself, just boot it for the installation of Magisk. Is that correct? Why?
FD
Click to expand...
Click to collapse
There is no need to install or boot into TWRP (btw. there is even no working TWRP for Android 10 yet) to install Magisk. It's sufficents to install Magisk Manager on your phone and patch the boot.img extracted from the factory image. Just follow the instructions which have been quoted here in the thread already.
AndDiSa said:
There is no need to install or boot into TWRP (btw. there is even no working TWRP for Android 10 yet) to install Magisk. It's sufficents to install Magisk Manager on your phone and patch the boot.img extracted from the factory image. Just follow the instructions which have been quoted here in the thread already.
Click to expand...
Click to collapse
Dear AndDisa,
As I said, I am rooting my Pixel 3a because I want to install XPrivacyLua, which requires the Xposed Framework; and to install Xposed with Magisk, it lists TWRP as a pre-requisite (see "Method 2: Magisk" in https://www.xda-developers.com/xposed-framework-hub/). Since it seems there is some kind of reluctance to use/install TWRP in this thread, I am asking why that is so. I understand it is possible to install Magisk without TWRP, I am just asking "why?"
Again, thank you all for your help.
FD
TWRP doesn't work on Android 10 at this point so you can't flash it.
Frederick Davies said:
Dear AndDisa,
As I said, I am rooting my Pixel 3a because I want to install XPrivacyLua, which requires the Xposed Framework; and to install Xposed with Magisk, it lists TWRP as a pre-requisite (see "Method 2: Magisk" in https://www.xda-developers.com/xposed-framework-hub/). Since it seems there is some kind of reluctance to use/install TWRP in this thread, I am asking why that is so. I understand it is possible to install Magisk without TWRP, I am just asking "why?"
Again, thank you all for your help.
FD
Click to expand...
Click to collapse
If you read closely in the guide sic linked, he does state the TWRP method is only for P because you can't use TWRP on 10. It is the way partitions are handled in 10 where you really can't read your internal storage and it would have to require a code rework. Until that's done, no TWRP.
Edit: quote from twrp developer about it. https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html
https://github.com/ElderDrivers/EdXposed/pull/354
https://github.com/ElderDrivers/EdXposedManager/releases
You can flash xposed without TWRP. Just install edxposed by downloading and installing through magisk and install the edxposed manager. You don't need TWRP
Frederick Davies said:
Very detailed indeed, but I still have a question: in your instructions you seem to boot into TWRP to install Magisk, but you do NOT install TWRP itself, just boot it for the installation of Magisk. Is that correct? Why?
FD
Click to expand...
Click to collapse
As other have noted, TWRP does not work with Android 10. However, I also wanted to answer your question because it is valid.....
With Android Pie (9), you cannot permanently install TWRP unless you first flash a custom kernel that supports LZMA compression. Using the stock kernel, you can load TWRP using ADB and use it just like normal, but when you reboot the phone TWRP will not be loaded anymore. My instructions are about rooting the phone and not about installing TWRP permanently on the phone and therefore I provided the simplest method to accomplish that goal.
Most custom kernels have been updated with LZMA support, but you should really read the TWRP thread for more information on how to permanently install TWRP on Android Pie
Dear All,
Thank you for all your help and explanations concerning my questions.
I have now rooted my Pixel 3a running Android 9 following the instructions supplied (no TWRP installation), and It seems that Magisk is installed and happy (at least it thinks it is and FX has root access), but I am afraid that EdXposed and XPrivacyLua are not working as expected.
After Magisk, I installed the "Riru - Core" and "Riru - EdXposed (YAHFA)" modules. I then installed the "EdXposed Framework (YAHFA)" (giving the EdXposed Installer superuser privileges; EdExposed reports it is installed and active), and the XprivacyLua module inside it. But now Magisk complains that the SafetyNet checks are failing (this coincides with installing XPrivacyLua, but it is the only module I have in EdXposed), and XPrivacyLua is not actually blocking anything at all (that is, even when I supposedly block access to some functions, the apps just go ahead and use them).
Why do I get the impression Google does not want people to root their phones?
Yours,
FD
Frederick Davies said:
Dear All,
Thank you for all your help and explanations concerning my questions.
I have now rooted my Pixel 3a running Android 9 following the instructions supplied (no TWRP installation), and It seems that Magisk is installed and happy (at least it thinks it is and FX has root access), but I am afraid that EdXposed and XPrivacyLua are not working as expected.
After Magisk, I installed the "Riru - Core" and "Riru - EdXposed (YAHFA)" modules. I then installed the "EdXposed Framework (YAHFA)" (giving the EdXposed Installer superuser privileges; EdExposed reports it is installed and active), and the XprivacyLua module inside it. But now Magisk complains that the SafetyNet checks are failing (this coincides with installing XPrivacyLua, but it is the only module I have in EdXposed), and XPrivacyLua is not actually blocking anything at all (that is, even when I supposedly block access to some functions, the apps just go ahead and use them).
Why do I get the impression Google does not want people to root their phones?
Yours,
FD
Click to expand...
Click to collapse
It is most certainly the things you have installed that are breaking the SafetyNet check. I don't know anything about XprivacyLua, but I would assume there is a support thread here on XDA for it. I would read that support thread and see if there is a solution to the Safetynet issue.
Dear All,
OK, I have now rooted my Pixel 3a: I am running Android 9, and I flashed Magisk (Magisk Manager version 7.4.0; Magisk version 20.1) without installing TWRP as per the instructions. Then I installed the Riru - Core (version 10) and Riru - Ed Exposed (version 0.2.8_beta) modules, which allowed me to install EdXposedInstaller (version 2.2.5). I am currently running Xposed Framework (version 90.0-0.2.8) with XPrivacyLua (version 1.25).
The result is that XPrivacyLua is working with a few caveats: the SafetyNet Check fails both the ctsProfile and basicIntegrity checks (this is triggered by XPrivacyLua, not (Ed)Xposed), and when I limit access of WhatsApp to the Contacts list, there are constant errors whenever WhatsApp tries to read it (though it seems to work as expected). Also, the Contacts list keeps disappearing from the Contacts app itself, despite WhatsApp actually seeing those contacts in there (go figure).
Other apps that require root (like FX) are working as expected.
In the end, I have decided that since I am not interested in using my mobile for Google Pay, I will have to live with it as it is now, but I have a couple of points for others that may want to follow in my footsteps (this is not necessarily related to the method of rooting; those who helped me here are certainly not at fault for the following):
1. XPrivacyLua is in no way as capable and easy to use as XPrivacy was (XPrivacy is the main reason why I am rooting my phone). If I could install Android 4 on my Pixel 3a, I would do so and go back to XPrivacy (my venerable Nexus 5's second battery is shot, so I had to get new hardware). There is nothing in Android 9 that I actually need that was not there in Android 4.
2. We really need a Nexus Toot Toolkit for Pixel phones. The multitude of versions and steps required in rooting them successfully is too much for those like me who will root their phone for one or two apps and then leave it as it is. I know that these forums are really for tinkerers who want to extract the maximum from their hardware, and hence my point of view is not representative here, but I just want a mobile that will not spy on me, the rest is irrelevant to me.
I guess I will have to open a thread in the XPrivacyLua forums to see if I can sort out my problems, but I would like to thank you all for your help in getting me here and answering my questions (no matter how pointless they may have seemed).
Yours,
FD
Frederick Davies said:
Dear All,
OK, I have now rooted my Pixel 3a: I am running Android 9, and I flashed Magisk (Magisk Manager version 7.4.0; Magisk version 20.1) without installing TWRP as per the instructions. Then I installed the Riru - Core (version 10) and Riru - Ed Exposed (version 0.2.8_beta) modules, which allowed me to install EdXposedInstaller (version 2.2.5). I am currently running Xposed Framework (version 90.0-0.2.8) with XPrivacyLua (version 1.25).
The result is that XPrivacyLua is working with a few caveats: the SafetyNet Check fails both the ctsProfile and basicIntegrity checks (this is triggered by XPrivacyLua, not (Ed)Xposed), and when I limit access of WhatsApp to the Contacts list, there are constant errors whenever WhatsApp tries to read it (though it seems to work as expected). Also, the Contacts list keeps disappearing from the Contacts app itself, despite WhatsApp actually seeing those contacts in there (go figure).
Other apps that require root (like FX) are working as expected.
In the end, I have decided that since I am not interested in using my mobile for Google Pay, I will have to live with it as it is now, but I have a couple of points for others that may want to follow in my footsteps (this is not necessarily related to the method of rooting; those who helped me here are certainly not at fault for the following):
1. XPrivacyLua is in no way as capable and easy to use as XPrivacy was (XPrivacy is the main reason why I am rooting my phone). If I could install Android 4 on my Pixel 3a, I would do so and go back to XPrivacy (my venerable Nexus 5's second battery is shot, so I had to get new hardware). There is nothing in Android 9 that I actually need that was not there in Android 4.
2. We really need a Nexus Toot Toolkit for Pixel phones. The multitude of versions and steps required in rooting them successfully is too much for those like me who will root their phone for one or two apps and then leave it as it is. I know that these forums are really for tinkerers who want to extract the maximum from their hardware, and hence my point of view is not representative here, but I just want a mobile that will not spy on me, the rest is irrelevant to me.
I guess I will have to open a thread in the XPrivacyLua forums to see if I can sort out my problems, but I would like to thank you all for your help in getting me here and answering my questions (no matter how pointless they may have seemed).
Yours,
FD
Click to expand...
Click to collapse
Cool story bro
Hi everyone.
to see if anyone can help me get full root please.
I have tried to root my "poco x3 pro" many times but to no avail.
According to magisk and root checker they say that if there is root but when using the apps, they request root access and according to magisk it grants it but then it says that the option is temporarily unavailable.
this happens to me with "es file Explorer", "root Essentials" "sixaxis controller" etc ,.
I already tried it with the global official miui, miui.eu and xperience rom, I installed it with twrp and with orangefox. Thank you very much and greetings.
Edit:
Well, it's appear that the apps I used, are incompatible and obsolete on android 11.
Magisk can grants root very well.
Thanks everyone
What magisk versions are you using
Try some other versions
LR7875 said:
What magisk versions are you using
Try some other versions
Click to expand...
Click to collapse
Hi. Thanks for answer
I try v21,22and23
Re-flash Stock ROM to get rid off of all modifications you applied so far.
jwoegerbauer said:
Re-flash Stock ROM to get rid off of all modifications you applied so far.
Click to expand...
Click to collapse
I already flash the stock rom and it remains the same
Not surprising me: don't think phone's Stock ROM ( Android 10 MIUI 12 ) is pre-rooted.
BTW:
To root phone's Android TWRP isn't needed, you achieve this by means of Magisk. How-to in detail is described here
How to Root Poco X3 & Unlock Bootloader: Step-by-Step Guide
One of the largest smartphone producers, Xiaomi has recently released its new device from Poco, the Poco X3. It has one NFC variant and a standard variant of Poco X3. Moreover, Xiaomi devices are best for customization, and to achieve this, one needs to root their device. Rooting a phone gives...
techburner.in
brakaman said:
I already flash the stock rom and it remains the same
Click to expand...
Click to collapse
Try fastboot method as shown here:
https://forum.xda-developers.com/t/4288121/post-85137969
pl1992aw said:
Try fastboot method as shown here:
https://forum.xda-developers.com/t/4288121/post-85137969
Click to expand...
Click to collapse
I did try it too. Thanks
did you install the manager after rooting?
brakaman said:
I did try it too. Thanks
Click to expand...
Click to collapse
Do you have other apps that can use root access?
For example: root explorer, MiXplorer, termux, terminal emulator... any apps that can use root.
Try them and see if those apps can get root access.
A) If those example apps can get root permission and works properly, then the problems are within those apps that does not work properly with root.
es file Explorer : original ones cannot be found on Play store, suspect lack of maintenance for new Android version
root Essentials : last update : October 27, 2017, some comment on Play store states issues for Android 10
sixaxis controller : can't find on Play store, last update found was 2017
B) If those example apps cannot get root permission, then prepare to do a clean flash, which will completely wipe data. Do backup of the data on your own.
jwoegerbauer said:
Not surprising me: don't think phone's Stock ROM ( Android 10 MIUI 12 ) is pre-rooted.
BTW:
To root phone's Android TWRP isn't needed, you achieve this by means of Magisk. How-to in detail is described here
How to Root Poco X3 & Unlock Bootloader: Step-by-Step Guide
One of the largest smartphone producers, Xiaomi has recently released its new device from Poco, the Poco X3. It has one NFC variant and a standard variant of Poco X3. Moreover, Xiaomi devices are best for customization, and to achieve this, one needs to root their device. Rooting a phone gives...
techburner.in
Click to expand...
Click to collapse
This phone it come with a11 miui 12
I did try that too
Thanks
Lu5ck said:
did you install the manager after rooting?
Click to expand...
Click to collapse
I did install it after and before
pl1992aw said:
Do you have other apps that can use root access?
For example: root explorer, MiXplorer, termux, terminal emulator... any apps that can use root.
Try them and see if those apps can get root access.
A) If those example apps can get root permission and works properly, then the problems are within those apps that does not work properly with root.
es file Explorer : original ones cannot be found on Play store, suspect lack of maintenance for new Android version
root Essentials : last update : October 27, 2017, some comment on Play store states issues for Android 10
sixaxis controller : can't find on Play store, last update found was 2017
B) If those example apps cannot get root permission, then prepare to do a clean flash, which will completely wipe data. Do backup of the data on your own.
Click to expand...
Click to collapse
pl1992aw said:
Do you have other apps that can use root access?
For example: root explorer, MiXplorer, termux, terminal emulator... any apps that can use root.
Try them and see if those apps can get root access.
A) If those example apps can get root permission and works properly, then the problems are within those apps that does not work properly with root.
es file Explorer : original ones cannot be found on Play store, suspect lack of maintenance for new Android version
root Essentials : last update : October 27, 2017, some comment on Play store states issues for Android 10
sixaxis controller : can't find on Play store, last update found was 2017
B) If those example apps cannot get root permission, then prepare to do a clean flash, which will completely wipe data. Do backup of the data on your own.
Click to expand...
Click to collapse
pl1992aw said:
Do you have other apps that can use root access?
For example: root explorer, MiXplorer, termux, terminal emulator... any apps that can use root.
Try them and see if those apps can get root access.
A) If those example apps can get root permission and works properly, then the problems are within those apps that does not work properly with root.
es file Explorer : original ones cannot be found on Play store, suspect lack of maintenance for new Android version
root Essentials : last update : October 27, 2017, some comment on Play store states issues for Android 10
sixaxis controller : can't find on Play store, last update found was 2017
B) If those example apps cannot get root permission, then prepare to do a clean flash, which will completely wipe data. Do backup of the data on your own.
Click to expand...
Click to collapse
Hi.
Appear you're right
The example apps can get root.
So my apps are incompatible.
I almost get crazy
Well thank you so much.
Now I need to fix the apps or find another's.
Help anyone cant find system/xbin/su folder in note 20 ultra rooted with twrp and custom rom 13 everything else works perfectly the reason am asking because i used to play a game before i root and now after root the game says that it detected root in system/xbin/su
But when i search in the phone i cant find this folder anywhere i have used mix and root explorer with no luck to find it.
TWRP does not root your device; it simply provides a means for you to easily install custom software.
You may need to use DenyList to hide Magisk from your game, or use modules such as Shamiko. You also will have better luck asking for help in the Magisk section of these forums.
V0latyle said:
TWRP does not root your device; it simply provides a means for you to easily install custom software.
You may need to use DenyList to hide Magisk from your game, or use modules such as Shamiko. You also will have better luck asking for help in the Magisk section of these forums.
Click to expand...
Click to collapse
I understand that twrp dont give me root but i already have root with magisk and still got the issue
Im running out of ideas even google is not helping
Shamiko was the fix for my problem.
How to close this thread.
Thank you.
next_1989 said:
How to close this thread.
Thank you.
Click to expand...
Click to collapse
No need to close it, just let it disappear into history