Related
I'm using a cm nightly with the new super user built into the ROM. So, can I uninstall the app or what?
Free your mind!
50cr473s said:
I'm using a cm nightly with the new super user built into the ROM. So, can I uninstall the app or what?
Free your mind!
Click to expand...
Click to collapse
Uninstalling it would remove root. You can replace it with another superuser app.
I'd be careful with this. I did it by accident (switched ROMs, had a had SuperSU installed on my old ROM, but new ROM came with its own SU program. When I reinstalled everything I included SuperSU) and it messed everything up - no programs could successfully get root access. I ended up just wiping and re-installing the ROM, this time not re-installing SuperSU on top of it and sticking with the built-in one on Viper.
Is there really any difference between SU apps? Hardly seems worth the hassle.
I'm using cm's app which is open source and built to be compatible with android platform, thus the ability to be integrated into the ROM. I've noticed that when I switch ROMs(e.g. carbon's unofficial port) Supersu is there in the app tray(instead of cm's) and cm's is in the settings. I had supersu installed before, but removed it when I installed cm's app. Oh my I've gone crosseyed. I've decided that it works as is and my only need is to clean up a little. I was just wondering if any one knew about specifically CM's super user?
Free your mind!
50cr473s said:
I'm using cm's app which is open source and built to be compatible with android platform, thus the ability to be integrated into the ROM. I've noticed that when I switch ROMs(e.g. carbon's unofficial port) Supersu is there in the app tray(instead of cm's) and cm's is in the settings. I had supersu installed before, but removed it when I installed cm's app. Oh my I've gone crosseyed. I've decided that it works as is and my only need is to clean up a little. I was just wondering if any one knew about specifically CM's super user?
Free your mind!
Click to expand...
Click to collapse
Well here's two cents for what its worth. When I moved from Rooted Stock (with SuperSU) to CM10 based Rom (LiquidSmooth), the CM10 app superseded from under Settings. SuperSU had to ask that app for permission before opening its own shop. From then on SuperSU ruled.
You don't necessarily have to do this. I did it because I like and support Chainfire's work. You can uninstall SuperSU if you are getting a CM based ROM with their app. It does not matter either way. They both are good.
Now as to SuperUser is concerned, I had a string of bad luck on ICS when that app tried to update SU Binary and ended deleting it. Of course I lost Root and since it was messed up, I could not use any Rooting Tools to get back.
Perseus71 said:
Now as to SuperUser is concerned, I had a string of bad luck on ICS when that app tried to update SU Binary and ended deleting it. Of course I lost Root and since it was messed up, I could not use any Rooting Tools to get back.
Click to expand...
Click to collapse
You could have flashed root back just the root zip
a box of kittens said:
You could have flashed root back just the root zip
Click to expand...
Click to collapse
I tried and failed. Recovery Flash had error unable to obtain Root.
Perseus71 said:
Now as to SuperUser is concerned, I had a string of bad luck on ICS when that app tried to update SU Binary and ended deleting it. Of course I lost Root and since it was messed up, I could not use any Rooting Tools to get back.
Click to expand...
Click to collapse
The SuperUser in CM now is not the same as it used to be, this is a new, open source SuperUser built by Koush and designed to be integrated into the system. Also this new version has two ways of updating the binary should one fail you.
Sent from my One X using Tapatalk 2
bliind said:
The SuperUser in CM now is not the same as it used to be, this is a new, open source SuperUser built by Koush and designed to be integrated into the system. Also this new version has two ways of updating the binary should one fail you.
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Yes I am aware of CM's inbuilt app. My comment that you quoted, pertains to the SuperUser App by ChainsDD as against SuperSU by Chainfire. This for the part 2 of OP.
Do either of the devs have a thread pertaining to switching su apps? I couldn't find anything?
Free your mind!
50cr473s said:
Do either of the devs have a thread pertaining to switching su apps? I couldn't find anything?
Free your mind!
Click to expand...
Click to collapse
Here's SuperSU. Best to download the App from Google Play. The thread can be confusing.
The CWM Superuser app on Google Play.
The original Superuser App by Chainsdd. As before best get it on Google Play.
i always download the supersu cwm flashable from the supersu thread, then after you flash it you can disable the original one.
somebody could teach me the easiest way to replace kinguser with supersu please?
dewagame said:
somebody could teach me the easiest way to replace kinguser with supersu please?
Click to expand...
Click to collapse
Follow these simple steps:
1. Go to the Play Store and install SuperSU.
2. When SuperSU is installed, give it permission as Super User.
3. Uninstall KingUser.
4. Done.
ИΘΘK¡€ said:
Follow these simple steps:
1. Go to the Play Store and install SuperSU.
2. When SuperSU is installed, give it permission as Super User.
3. Uninstall KingUser.
4. Done.
Click to expand...
Click to collapse
hI! I try on my HUAWEI ASCEND G6 and... dont work ... is possibel that an update that Kinguser had done make it impossibel?????
I root with RootGenius_en, was ok, kinguser ask for a update, done. But Now i whant to change do SuperSu and dont work. I had permissions and every thing...
Help! :crying:
Me too
I'm trying to do this too, but I aint sure how to do it. I mean I guess if its not super necessary I can leave it the way it is. Tried this method and its a no go. I don't think the KingUser SU is letting superSU update its binaries. I already have twrp, but not sure what next. If its not necessary I'll leave it alone, but I was just wondering if theres any reason to change over or if it could even be done.
P.S This way never worked for me as superSU can't get past trying to install the binaries. I got twrp so I'm wondering if I'd have to flash it. Nothings wrong on my end are anything, but I just assumed having superSU would be better then kinguser but not really sure.
many people have this problem.
first of all, kinguser is great to root the G6, and in most cases the only working method without custom recovery,
but because it flashes kinguser.apk as system app you can't uninstall it the normal way.
the solution is to flash supersu.zip and then uninstall kinguser. this way supersu will be your systemapp.
find the files and tutorials you need on our facebook group,
we have 1500+ members, CWM + TWRP, android 4.3 + 4.4, we can root your g6 and unlock your bootloader.
but we still don't have a subforum on XDA....
https://www.facebook.com/groups/328261053999820
Must vary from device to device cause I've did all that, and it gives the message "Installing Please wait..." and then after it fails it says " Installation Failed! Please reboot and try again" and if kinguser is removed in superSU when trying to update/install the binaries it says "There is no SU binary installed, and SuperSU cannot install it. This is a problem! If just upgraded to Android 4.3 you need to manually re-root- consult the relevant forums for your device."
This aint the g6 though but this thread is the kinguser replace with superSU thread. So I thought I'd post in it.
washichi said:
many people have this problem.
first of all, kinguser is great to root the G6, and in most cases the only working method without custom recovery,
but because it flashes kinguser.apk as system app you can't uninstall it the normal way.
the solution is to flash supersu.zip and then uninstall kinguser. this way supersu will be your systemapp.
find the files and tutorials you need on our facebook group,
we have 1500+ members, CWM + TWRP, android 4.3 + 4.4, we can root your g6 and unlock your bootloader.
but we still don't have a subforum on XDA....
https://www.facebook.com/groups/328261053999820
Click to expand...
Click to collapse
Install SuperSu rom magazin play.
Then instal rom lite box.
Open the app, and uninstall kinguser
easy, and it`s working.I just deleted kinguser 2 mins ago
Hum
@andruala Never worked for me that way, anytime I remove king user root gets removed. Never was able to flash superSU rom correctly because binaries couldn't get updated from superSU because root was removed once king user was uninstalled. I've heard people mention it working the way you suggested, but I've also read posts where people have a hard time getting it replaced with superSU because root gets removed when king user is replaced, which doesn't allow superSU to install the binaries correctly. Most people probably can't get the binaries installed correctly from superSU which is the same problem I had so they end up just leaving it king user. I could try whats suggested here but I very much doubt its going to work as explained from my conflict that when king user is removed, root is removed and whether you flash a SU zip or not root still aint enabled because SU binaries are nt installed correctly. So until I actually can confirm this works myself I'm gonna prob say its a no-go for me. Could be device specific but I did all this to a tee and still had problems. There was a post on freak tab where someone had the same problem. I might still try this, I just dont see it working like as said.
freestilesteve said:
@andruala Never worked for me that way, anytime I remove king user root gets removed. Never was able to flash superSU rom correctly because binaries couldn't get updated from superSU because root was removed once king user was uninstalled. I've heard people mention it working the way you suggested, but I've also read posts where people have a hard time getting it replaced with superSU because root gets removed when king user is replaced, which doesn't allow superSU to install the binaries correctly. Most people probably can't get the binaries installed correctly from superSU which is the same problem I had so they end up just leaving it king user. I could try whats suggested here but I very much doubt its going to work as explained from my conflict that when king user is removed, root is removed and whether you flash a SU zip or not root still aint enabled because SU binaries are nt installed correctly. So until I actually can confirm this works myself I'm gonna prob say its a no-go for me. Could be device specific but I did all this to a tee and still had problems. There was a post on freak tab where someone had the same problem. I might still try this, I just dont see it working like as said.
Click to expand...
Click to collapse
Yes...i`m really sorry.For me wit worked before i restarted the phone...
After de restart i`ve seen that the root is not working anymore...
Sorry for my bad.
No worries bro. Probably varies depending on how you root from device to device.
Its not your fault. No worries. I'm just thinking it varies from device to device and how you actually go about rooting . I'm also thinking that maybe if I rooted with another app/prog that it would have been easier to switch from king user to superSU. I use lookout premium security on my phone and kingroot and king user have never been flagged with any viruses so I've just left it on and running the way it is and so far so good. Other then the two errors I mentioned in the previous post king user/kingroot has been working good. I'm sure if I did a whole restore/wipe/clean and root with another program there might be a possibility to remove king user and replace with superSU but in the end I just decided to roll with king user/kingroot as I didn't feel like doing al that and its been doing its job fine.
QUOTE=andruala;58880236]Yes...i`m really sorry.For me wit worked before i restarted the phone...
After de restart i`ve seen that the root is not working anymore...
Sorry for my bad.[/QUOTE]
Well I thought about leaving kinguser sitting there on my system too until one day I installed network monitor stuff and noticed kinguser sure likes to make HTTP connections every time the Internet is available. Imagine that. Also have a look, there are /system/bin/.usr/.ku etc. hiding all over your system.
The earlier versions of Kingo Root were much better
jidanni said:
Well I thought about leaving kinguser sitting there on my system too until one day I installed network monitor stuff and noticed kinguser sure likes to make HTTP connections every time the Internet is available. Imagine that. Also have a look, there are /system/bin/.usr/.ku etc. hiding all over your system.
Click to expand...
Click to collapse
Those earlier versions were putting SuperSU binaries into the root. But now they are putting on this King User crap. Reason I say it's crap is exactly what you mentioned. As soon as I root a phone with Kingo Root, Google Search immediately tells me that it will not allow me to search for anything because "your computer or network may be sending automated queries. To protect our users, we can't process your request right now"
Good God! What the heck is Kingo Root putting onto these phones now? It sure isn't putting just su binaries in there.
Indeed. What is needed is for someone to take a vanilla phone into a cleanroom, install the mess, and report back on exactly what ended up getting put where, in order for somebody to make a "kinguser detox/.antidote" APP and/or shell scripts that would clean the mess totally back off.
don't know if it's gonna help you ( have alcatel onetouch idol 2 mini s):
i also couldn't update binaries su and had kinguser.
then i downloaded the beta version of supersu (on xda) and flashed it with my cwm. after that when supersu asked if i wanted to update, i said yes and choose normal update (not the cwm/t... one) it than updates and asked if i wanted to remove the external root apps (ie: kinguser) and voila!
(sorry English isn't my language, so don't know if i explained myself well^^)
satine01black said:
don't know if it's gonna help you ( have alcatel onetouch idol 2 mini s):
i also couldn't update binaries su and had kinguser.
then i downloaded the beta version of supersu (on xda) and flashed it with my cwm. after that when supersu asked if i wanted to update, i said yes and choose normal update (not the cwm/t... one) it than updates and asked if i wanted to remove the external root apps (ie: kinguser) and voila!
(sorry English isn't my language, so don't know if i explained myself well^^)
Click to expand...
Click to collapse
Why did you need to root with kingo if you have custom recovery?!
I rooted first then found the cwm for my phone?
satine01black said:
I rooted first then found the cwm for my phone?
Click to expand...
Click to collapse
Oh. I wasn't angry at you Was just asking.
it took me like a year to root my phone then i couldn't make it work well with kinguser, and i wanted supersu anyway, so i found that i could install manually the app with cwm .
anyway, i don't now if you can use cwm without a root?
satine01black said:
it took me like a year to root my phone then i couldn't make it work well with kinguser, and i wanted supersu anyway, so i found that i could install manually the app with cwm .
anyway, i don't now if you can use cwm without a root?
Click to expand...
Click to collapse
You can, but it doesn't really make much sense to.
Use Eroot, then try superSU installation
CVAngelo said:
Those earlier versions were putting SuperSU binaries into the root. But now they are putting on this King User crap. Reason I say it's crap is exactly what you mentioned. As soon as I root a phone with Kingo Root, Google Search immediately tells me that it will not allow me to search for anything because "your computer or network may be sending automated queries. To protect our users, we can't process your request right now"
Good God! What the heck is Kingo Root putting onto these phones now? It sure isn't putting just su binaries in there.
Click to expand...
Click to collapse
I had the same issue with my mobile, (Sony Ericsson Xperia Ray (ST18i)), I then rooted my phone with EROOT Software which installed a superuser app, then i got the .apk file of SuperSU via Bluetooth from a friend and installed it. one has to grant permission when it asks for superuser rights, then updating binary files is no longer a problem. It also asks for removal of the Superuser-app that was pushed through the EROOT software, you do that. Then I installed link2SD and link2sd pro key from google play store and converted the SuperSU app into a system-app. Now SuperSU is working perfectly again.
You both should try it!!
Hey everyone, I got Android Pay working with the latest version of TruPure (2.6)
This should also work on other stock moto ROM's, as it isn't much different.
I saw this thread (http://forum.xda-developers.com/nexus-5x/general/passing-safetynet-root-t3307659) and made a few changes.
Step 0:
I do not think that this will work with Xposed or Google Dialer/Contacts installed, but I have not tested to confirm. I also uninstalled and reinstalled Android Pay before starting the process, and did not set it up. No need to wipe google play services data as other ways of implementing Pay have done (this causes problems with Android Wear, which I have) This works with the latest version of supersu, 2.67.
Step 1:
Reboot into TWRP recovery, wipe system, cache, and dalvik (art). Data wipe is not needed, at least on my phone.
Step 2:
go to the terminal (in twrp, under the advanced tab) and enter the following two commands.
Code:
echo SYSTEMLESS=true>>/data/.supersu
Code:
echo BINDSYSTEMXBIN=false>>/data/.supersu
this will make TruPure use systemless root on the next install.
Step 3:
Flash TruPure 2.6, and do not select Google Dialer in the installer. Make sure in the log that SuperSu is installed systemless, if not, you did step 2 wrong.
Step 3v2: if you don't want to install TruPure (honestly why not it's great) flash your room of choice in this step. If the ROM comes with xposed or other tweaks, this will not work.
For a stock ROM, flash here, then flash SuperSU 2.67, then continue.
Step 4: Reboot system, wait for apps to optimize.
Step 5: start up your favorite terminal app, run
Code:
su
accept the prompt
Code:
chmod 751 /su/bin
Step 6: Launch and set up Android Pay, no reboot required
Hope this helps! Your milage may vary!
:good: say thanks if I helped! :good:
Just so you're aware the link you included is broken and depending on which version of SU is installed Step 2 might not be necessary as version 2.62-3 automatically installs systemless.
Well this is big news.. The newest SuperSU is systemless by default? If im reading this correctly, the Google Play update will make this option usable/.
Xposed will definitely break Pay for obvious reasons.
Installing Google Dialer will break Pay too if the required framework JAR and permissions XML are also installed. You can install the dialer without those files, but I doubt CID and lookup will function as it should.
Sent from my XT1575 using Tapatalk
Fixed the broken link, and clarified that this is only tested on the latest supersu.
SR3TLAW said:
Well this is big news.. The newest SuperSU is systemless by default? If im reading this correctly, the Google Play update will make this option usable/.
Click to expand...
Click to collapse
The newest SuperSU isn't systemless by default, step 2 is where we change the string to request the systemless. No need to download a special SuperSU package.
drewksparks said:
The newest SuperSU isn't systemless by default, step 2 is where we change the string to request the systemless. No need to download a special SuperSU package.
Click to expand...
Click to collapse
Spasticdroid said:
Xposed will definitely break Pay for obvious reasons.
Installing Google Dialer will break Pay too if the required framework JAR and permissions XML are also installed. You can install the dialer without those files, but I doubt CID and lookup will function as it should.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Sounds like regardless there is no still no way with Exposed or Google Dialer
SR3TLAW said:
Sounds like regardless there is no still no way with Exposed or Google Dialer
Click to expand...
Click to collapse
There definitely isn't a way with google dialer, but Xposed may work if you use the RootCloak module. I personally havn't tested it.
drewksparks said:
There definitely isn't a way with google dialer, but Xposed may work if you use the RootCloak module. I personally havn't tested it.
Click to expand...
Click to collapse
Whats all the fuss about Google Dialer, does it make dreams come true?
drewksparks said:
There definitely isn't a way with google dialer, but Xposed may work if you use the RootCloak module. I personally havn't tested it.
Click to expand...
Click to collapse
RootCloak has never worked with Android Pay.
Sent from my XT1575 using Tapatalk
Spasticdroid said:
RootCloak has never worked with Android Pay.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
My mistake. I thought I remembered something about it working. So, at the moment, there seems to be no way to make Android Pay work with Xposed or Google Dialer. I personally get by very well without both.
Has anyone tried it with multirom and have the second rom without any root or xposed? I'm gonna give it a go and see how it pans out.
Sent from my XT1575 using Tapatalk
Hi All. Can't seem to get this working. I'm on my 5th attempt at installing. I entered the install commands in TWRP 3.0 exactly as described using TruPure 2.6. Installed OpenGApps Stock. Confirmed I achieved systemless root and changed the permission in the su/bin folder using Root Explorer. I don't have ad-away or any other modification and I installed TruPure as this thread suggests. Each time, SafetyNet check fails. Any other thoughts on what might be causing this?
On a possibly related note, root doesn't seem to survive a reboot after changing the folder permissions...
bsilver2988 said:
Hi All. Can't seem to get this working. I'm on my 5th attempt at installing. I entered the install commands in TWRP 3.0 exactly as described using TruPure 2.6. Installed OpenGApps Stock. Confirmed I achieved systemless root and changed the permission in the su/bin folder using Root Explorer. I don't have ad-away or any other modification and I installed TruPure as this thread suggests. Each time, SafetyNet check fails. Any other thoughts on what might be causing this?
On a possibly related note, root doesn't seem to survive a reboot after changing the folder permissions...
Click to expand...
Click to collapse
Android Pay is going to fail if there's more GApps installed to system other than what was shipped by default on the Pure. You can however, install updated versions of the default shipped apps, or even debloat the ROM of the default shipped apps (which TPMM does), and still have Android Pay working.
Looking at the list of stock Open GApps, Google+, Google Calculator, Google Camera, Google Contacts, Google Fit are a few that never was installed as system apps on stock ROM.
EDIT: Stock apps on the Moto X Pure Edition
/system/app
Android System WebView (WebViewGoogle)
Chrome Browser - Google (Chrome)
Clock (DeskClockGoogle)
Cloud Print (CloudPrint2)
Exchange Services (Exchange3Google)
Gmail (Gmail2)
Google Calendar (CalendarGoogle)
Google Docs (EditorsDocs)
Google Drive (Drive)
Google Keyboard (LatinImeGoogle)
Google Now Launcher (GoogleHome)
Google Photos (Photos)
Google Play Movies & TV (Videos)
Google Play Music (Music2)
Google Sheets (EditorsSheets)
Google Slides (EditorsSlides)
Google Talkback (talkback)
Google Text-to-Speech (GoogleTTS)
Google Translate (Translate)
Hangouts (Hangouts)
Maps (Maps)
YouTube (YouTube)
/system/priv-app
Google Play Services (GmsCore)
Google Play Store (Phonesky)
Google App (Velvet)
Click to expand...
Click to collapse
Spasticdroid said:
Android Pay is going to fail if there's more GApps installed to system other than what was shipped by default on the Pure. You can however, install updated versions of the default shipped apps, or even debloat the ROM of the default shipped apps (which TPMM does), and still have Android Pay working.
Looking at the list of stock Open GApps, Google+, Google Calculator, Google Camera, Google Contacts, Google Fit are a few that never was installed as system apps on stock ROM.
EDIT: Stock apps on the Moto X Pure Edition
Click to expand...
Click to collapse
Thanks for this! It makes perfect sense. Unfortunately I'm still getting a Fail when I run the test. Any other thoughts?
EDIT: Figured it out! I guess OpenGapps itself was incompatible with this setup. Installing TruPure without it solved the problem. Thanks for the help!
Thanks @drewksparks, followed your detailed instructions and confirmed by buying me a beer with my phone running True Pure 2.6.2. Now to decide if it's worth giving up Xposed, Gravity Box, Amplify, etc. Hmmm I want it all.
drewksparks said:
Hey everyone, I got Android Pay working with the latest version of TruPure (2.6)
This should also work on other stock moto ROM's, as it isn't much different.
I saw this thread (http://forum.xda-developers.com/nexus-5x/general/passing-safetynet-root-t3307659) and made a few changes.
Step 0:
I do not think that this will work with Xposed or Google Dialer/Contacts installed, but I have not tested to confirm. I also uninstalled and reinstalled Android Pay before starting the process, and did not set it up. No need to wipe google play services data as other ways of implementing Pay have done (this causes problems with Android Wear, which I have) This works with the latest version of supersu, 2.67.
Step 1:
Reboot into TWRP recovery, wipe system, cache, and dalvik (art). Data wipe is not needed, at least on my phone.
Step 2:
go to the terminal (in twrp, under the advanced tab) and enter the following two commands.
Code:
echo SYSTEMLESS=true>>/data/.supersu
Code:
echo BINDSYSTEMXBIN=false>>/data/.supersu
this will make TruPure use systemless root on the next install.
Step 3:
Flash TruPure 2.6, and do not select Google Dialer in the installer. Make sure in the log that SuperSu is installed systemless, if not, you did step 2 wrong.
Step 3v2: if you don't want to install TruPure (honestly why not it's great) flash your room of choice in this step. If the ROM comes with xposed or other tweaks, this will not work.
For a stock ROM, flash here, then flash SuperSU 2.67, then continue.
Step 4: Reboot system, wait for apps to optimize.
Step 5: start up your favorite terminal app, run
Code:
su
accept the prompt
Code:
chmod 751 /su/bin
Step 6: Launch and set up Android Pay, no reboot required
Hope this helps! Your milage may vary!
:good: say thanks if I helped! :good:
Click to expand...
Click to collapse
To all the smart puppies outthere, would like to know is it is possible to get this to work on CM13 or AOSP based Custom ROMs. Android Pay is the only thing keeping me runnign TruePureMM. Not that it's a bad ROM but the customization you get from the CM13 ROMs like Bliss is crazy awesome. I'd be a ginnie pig and try it out if someone comes up with something like this for CM13 or AOSP ROMs. Thanks guys.
cerobles1 said:
To all the smart puppies outthere, would like to know is it is possible to get this to work on CM13 or AOSP based Custom ROMs. Android Pay is the only thing keeping me runnign TruePureMM. Not that it's a bad ROM but the customization you get from the CM13 ROMs like Bliss is crazy awesome. I'd be a ginnie pig and try it out if someone comes up with something like this for CM13 or AOSP ROMs. Thanks guys.
Click to expand...
Click to collapse
Won't work unfortunately. Too many files and apps and such are needed in CM and CM-based ROMs (example: Bliss) for them to work properly, and in turn breaks Android Pay.
If we can ever get an AOSP-based ROM, which is bare (meaning not built with AOSP apps included) working on this device, we may have a chance, just like how some ROMs on Nexus devices, such as Chroma and PureNexus, works with Android Pay.
The last thing needed would be a proper GApps package containing only the default GApps found in a stock Pure/Style ROM to install (can be updated versions of those apps too.)
Sent from my XT1575 using Tapatalk
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.
I have a Motorola G 4 Plus, rooted SU 2.82, latest TWRP, Havoc 2.9, Android 9 Pie. Arm v7I.
Upon trying to install Youtube Vanced through the Vanced Manager, the app crashes and the install fails with the message "failed for unknown reason blah blah blah please go to the Telegraph Discord group" I can post a log file if needed.
After that ordeal, the Youtube app appears in my app drawer, when I try to open it it says "you don't have Google Play Services" and closes.
I tried this with micro-g installed, I disabled apk signature verification with Lucky Patcher, doesn't make a difference.
I even made sure to allow unknown sources and checked the permissions. No go.
I also tried the apks installer through the SIS installer or whatever its called, SAS, SAI or whatever, no luck.
Feels like my phone can go as far as to root and custom recovery and custom rom and busybox and such but continue to find myself in these annoying situations with no resolution. Other people seem to be able to get it to work though. Perhaps its the phone?
Any help is appreciated, thanks!
Do you have magisk installed or are you using another solution for root? I saw your post about brave not working , may I suggest a rom reinstall? Try it with the microg gapps package.
Edit: grammar.
ThatLatinGuy said:
Do you have magisk installed or are you using another solution for root? I saw your post abou brave not working , may I suggest a rom reinstall? Try it with the microg gapps package
Click to expand...
Click to collapse
Rooted with SU 2.82 flashed via TWRP and use SU app. Not magisk. Perhaps I'll try another ROM. Too bad Havoc seems really good customizable.
I originally forgot to wipe cache and dalvik/art cache after flashing the Havoc ROM so maybe that screwed things up, I'll try re-flashing.
I'd remove SU and use magisk 21.4 (not higher, and never update it ever).
when was 2.82 released ? it must be a long time ago now and I don't think it's recommended for anything anymore.
even without any root Vanced manager would install your microg and vanced just fine.
3mel said:
I'd remove SU and use magisk 21.4 (not higher, and never update it ever).
when was 2.82 released ? it must be a long time ago now and I don't think it's recommended for anything anymore.
even without any root Vanced manager would install your microg and vanced just fine.
Click to expand...
Click to collapse
Super SU was last updated 2020 from my understanding.
big bad brad 31 said:
Super SU was last updated 2020 from my understanding.
Click to expand...
Click to collapse
the last post in chainfire's superSU thread here is from 2018, it says just use magisk
big bad brad 31 said:
Super SU was last updated 2020 from my understanding.
Click to expand...
Click to collapse
this is the last and latest version of SuperSU
SuperSU Download
it was released back in 2017 all other website that has SuperSU for downloads except that site are Unofficial Released
big bad brad 31 said:
I have a Motorola G 4 Plus, rooted SU 2.82, latest TWRP, Havoc 2.9, Android 9 Pie. Arm v7I.
Upon trying to install Youtube Vanced through the Vanced Manager, the app crashes and the install fails with the message "failed for unknown reason blah blah blah please go to the Telegraph Discord group" I can post a log file if needed.
After that ordeal, the Youtube app appears in my app drawer, when I try to open it it says "you don't have Google Play Services" and closes.
I tried this with micro-g installed, I disabled apk signature verification with Lucky Patcher, doesn't make a difference.
I even made sure to allow unknown sources and checked the permissions. No go.
I also tried the apks installer through the SIS installer or whatever its called, SAS, SAI or whatever, no luck.
Feels like my phone can go as far as to root and custom recovery and custom rom and busybox and such but continue to find myself in these annoying situations with no resolution. Other people seem to be able to get it to work though. Perhaps its the phone?
Any help is appreciated, thanks!
Click to expand...
Click to collapse
Try installing a custom rom based on A10 n see if this works out for u, it works perfectly on my g4+ on A10 ...