Okay, I am running Stock Nvidia Shield K1 android 5.1.1 firmware, with TWRP installed, and I just recently updated to Magisk to get the Sony Framework working on my Nvidia Shield K1 to use the Remote Play app, but, it always tells me when I choose the install option from inside of the app that it is not a Magisk module. I downloaded it directly from the app, so it should be the correct framework. I am also having troubles with Viper4Android, when I install the module, it installs properly, but the app? Oh no, the app basically tells me unsupported driver installed and tells me to update the driver, which I say yes, and then, it errors out and tells me I need the busybox or it is corrupted. So, I go and get the BusyBox Magisk module, and it tells me that it is not a Magisk module when I try and install the module. What am I doing wrong here? Is Android 5.1.1 not supported by root users anymore? Is my tablet just an unsupported tablet? What is happening to Magisk that's making it so difficult to install drivers and modules directly from the app? Can someone please help me out with Magisk? I am a noob, and no one makes videos on Youtube about the Nvidia Shield K1 with Magisk on YouTube in English. Everyone makes Magisk look so easy to use, but, with my experience so far, it is a dang nightmare to use, because I cannot get any modules installed on my tablet.
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.
Hey all,
Just purchased a LG U2 and now trying to make it work in the way i want it.
All informations here seem very old, so I wanted to open an update thread, with all what is possible on th lgu2, while
I found only very outdated informations...:crying:
So far:
First I setup the watch with AW2.0, after that flashed twrp 3.1.1.0 and supersu wear 2.82
I managed to get busybox installed and wanted further add Xposed.
There my problem starts, flashing xposed didn't work out.
So right after that, I switchd to Magisk root, to try work with the modules supplied.
(Steps -> use script UnSU, after that flash boot.img again, than flash MAgisk through twrp)
But after that the same with the modules. I try to install busybox, magisk tell me its no magisk module (i've downloaded the module and pushed it on the sd through adb, while the download button isn't reachable in magisk dialogue menu)
in twrp the module tells me there is no magisk installed.
so how can we go on from here? is there a way to make it all work?
did somebody try to change dpi and download the module directly through magisk? does it work?
also if somebody could help with an updated list of sideload able full android apps?
would need an email that can handle at least two accounts directly on the watch (please not advice outlook, its working from the phone i know)
thanks to all in advance
sebj84 said:
Hey all,
Just purchased a LG U2 and now trying to make it work in the way i want it.
All informations here seem very old, so I wanted to open an update thread, with all what is possible on th lgu2, while
I found only very outdated informations...:crying:
So far:
First I setup the watch with AW2.0, after that flashed twrp 3.1.1.0 and supersu wear 2.82
I managed to get busybox installed and wanted further add Xposed.
There my problem starts, flashing xposed didn't work out.
So right after that, I switchd to Magisk root, to try work with the modules supplied.
(Steps -> use script UnSU, after that flash boot.img again, than flash MAgisk through twrp)
But after that the same with the modules. I try to install busybox, magisk tell me its no magisk module (i've downloaded the module and pushed it on the sd through adb, while the download button isn't reachable in magisk dialogue menu)
in twrp the module tells me there is no magisk installed.
so how can we go on from here? is there a way to make it all work?
did somebody try to change dpi and download the module directly through magisk? does it work?
also if somebody could help with an updated list of sideload able full android apps?
would need an email that can handle at least two accounts directly on the watch (please not advice outlook, its working from the phone i know)
thanks to all in advance
Click to expand...
Click to collapse
Ok i did a fresh flash.
i see my fault was to install busybox the first time after installing supersu.
did it this time without and mgisk works so far fine. granting access for total commander no problem.
but now another thing. i installed now busybox from the repos in magisk, he say installation successful, but the module isn't there after reboot?
anyone got the same?
sebj84 said:
Ok i did a fresh flash.
i see my fault was to install busybox the first time after installing supersu.
did it this time without and mgisk works so far fine. granting access for total commander no problem.
but now another thing. i installed now busybox from the repos in magisk, he say installation successful, but the module isn't there after reboot?
anyone got the same?
Click to expand...
Click to collapse
another try. i switched back to supersu wear 2.82, installed stericsons busybox. works.
installed xposed sdk25 via twrp, says success, but after reboot xposed installer says no active framework.
i used a systemless framework... will search for the link again.
anybody got it done this way?
Hi,
I am trying to root my Google Pixel on 8.1. I was on Magisk for a long time but I gave up on it because a few root apps I was trying to use aren't compatible.
I read some guides but they are ridiculously out of date. They say to use an experimental version of TWRP because it fails unlock codes and such; a lot of really out of date stuff. Some don't mention the ElementalX step, and then other guides say a custom kernel is required for rooting. But I had root with Magisk and never had to install a custom kernel. Other guides are still telling me to use the signature zips which supposedly hasn't been needed in forever. Trying to piece this all together is causing me to rip my hair out.
Anyway this is what I did, and it kept failing (I kept getting a "patching sepolicy" error in TWRP).
1) I booted the TWRP.img
2) I installed the twrp.zip
3) I booted into recovery
4) I installed Elemental X 13.3 zip
5) I installed SuperSU zip
6) I installed SuperSUHide zip
This isn't working. Every time I try to open SuperSU it says I don't have root. I also get an error every time I boot about their being an internal problem with my hardware and to contact the manufacturer. I believe Elemental X 13.3 is the cause. I wiped my phone and reinstalled stock and I am no longer getting that error.
Can anybody let me know what the deal is? Do I still have to install a custom kernel to install SuperSU? If so, what are the steps? Obviously whatever I am doing is wrong. Thanks so much in advance.
SuperSU is not working in the Pixel with 8.1
Sh0X31 said:
SuperSU is not working in the Pixel with 8.1
Click to expand...
Click to collapse
Oh. I had no idea.
Do any root methods that aren't Magisk work?
daddylonglegs said:
Oh. I had no idea.
Do any root methods that aren't Magisk work?
Click to expand...
Click to collapse
Looks like Magisk is becoming more and more popular nowadays, so I don't think any other method with 8.1 works.
What's the problem with magisk? It's super easy and you can also install systemless modules, which is a big advantage
TENN3R said:
Looks like Magisk is becoming more and more popular nowadays, so I don't think any other method with 8.1 works.
What's the problem with magisk? It's super easy and you can also install systemless modules, which is a big advantage
Click to expand...
Click to collapse
1) Magisk doesn't work with StickMount. I need a way for my USB-C flash drive to mount as something all file explorer programs can see. There seems to be no way to do this with Magisk
2) Magisk does not work with WifiTetherRouter. I need to use it to tether without being capped at 512kbps. It only works with "real root" like SuperSU.
3) I don't benefit at all from systemless modules because I use GravityBox, which makes the whole systemless thing pointless for me
daddylonglegs said:
1) Magisk doesn't work with StickMount. I need a way for my USB-C flash drive to mount as something all file explorer programs can see. There seems to be no way to do this with Magisk
2) Magisk does not work with WifiTetherRouter. I need to use it to tether without being capped at 512kbps. It only works with "real root" like SuperSU.
3) I don't benefit at all from systemless modules because I use GravityBox, which makes the whole systemless thing pointless for me
Click to expand...
Click to collapse
1) OTG
2) There are tether modules on magisk and other tether apps that will work with magisk
3) How does gravity box make systemless pointless? To my knowledge gravity box just builds custom rom features on top of stock, systemless modules should work regardless and provide things GB cannot
Lastly SuperSU isn't to be trusted anymore as it is no longer owned and maintained by chainfire. And could you explain the "real root" thing because magisk is a very real tangible root.
TENN3R said:
Looks like Magisk is becoming more and more popular nowadays, so I don't think any other method with 8.1 works.
What's the problem with magisk? It's super easy and you can also install systemless modules, which is a big advantage
Click to expand...
Click to collapse
KittyRgnarok said:
1) OTG
2) There are tether modules on magisk and other tether apps that will work with magisk
3) How does gravity box make systemless pointless? To my knowledge gravity box just builds custom rom features on top of stock, systemless modules should work regardless and provide things GB cannot
Lastly SuperSU isn't to be trusted anymore as it is no longer owned and maintained by chainfire. And could you explain the "real root" thing because magisk is a very real tangible root.
Click to expand...
Click to collapse
1) Doesn't that depend on the phone? Does my phone support OTG? And if so, why does my USB flash drive not show up in a bunch of apps?
2) None of them work with WiFi tethering except for WifiTetherRouter. PDANet works but it requires a PDANet program to be installed on the receiving computer, which means I am out of luck on stuff like the Nintendo Switch
3) Because from what I understand the entire point of Systemless root is to pass SafetyNet, and SafetyNet fails if you have GravityBox installed.
As for the "real root" thing, the developer of Auto Call Recorder here on XDA told me the newest version is not compatible with Magisk, only "real root" (his words). The developer of WifiTetherRouter told me the same thing.
daddylonglegs said:
1) Doesn't that depend on the phone? Does my phone support OTG? And if so, why does my USB flash drive not show up in a bunch of apps?
2) None of them work with WiFi tethering except for WifiTetherRouter. PDANet works but it requires a PDANet program to be installed on the receiving computer, which means I am out of luck on stuff like the Nintendo Switch
3) Because from what I understand the entire point of Systemless root is to pass SafetyNet, and SafetyNet fails if you have GravityBox installed.
As for the "real root" thing, the developer of Auto Call Recorder here on XDA told me the newest version is not compatible with Magisk, only "real root" (his words). The developer of WifiTetherRouter told me the same thing.
Click to expand...
Click to collapse
Pretty sure otg should work but I could be wrong. Try mounting otg via twrp. And ohh my bad I see what you mean about the tethering thing I misunderstood. As far as the magisk thing meh safetynet isn't that important and u can have a second slot that is properly intact and idk about the real root business but if that's what the devs said then fair enough
TENN3R said:
Looks like Magisk is becoming more and more popular nowadays, so I don't think any other method with 8.1 works.
What's the problem with magisk? It's super easy and you can also install systemless modules, which is a big advantage
Click to expand...
Click to collapse
KittyRgnarok said:
Pretty sure otg should work but I could be wrong. Try mounting otg via twrp. And ohh my bad I see what you mean about the tethering thing I misunderstood. As far as the magisk thing meh safetynet isn't that important and u can have a second slot that is properly intact and idk about the real root business but if that's what the devs said then fair enough
Click to expand...
Click to collapse
Thanks so much for the reply!
For some reason when I flash TWRP on this phone my phone will only boot into recovery until I flash back the stock boot.img (or the patched Magisk one). I am using the newest TWRP. Anyone else with this problem?
Anyway I mounted OTG in TWRP using the bootable image for TWRP. Would it make a difference? Does it have to be done in the installed version of TWRP where TWRP is my actual recovery?
After enabling OTG in TWRP I still can't find my SD/USB store in storage/emulated which is where I need it to be if I want all my apps to see it. Is there any way to do that?
daddylonglegs said:
Thanks so much for the reply!
For some reason when I flash TWRP on this phone my phone will only boot into recovery until I flash back the stock boot.img (or the patched Magisk one). I am using the newest TWRP. Anyone else with this problem?
Anyway I mounted OTG in TWRP using the bootable image for TWRP. Would it make a difference? Does it have to be done in the installed version of TWRP where TWRP is my actual recovery?
After enabling OTG in TWRP I still can't find my SD/USB store in storage/emulated which is where I need it to be if I want all my apps to see it. Is there any way to do that?
Click to expand...
Click to collapse
I don't flash twrp zip, just boot it, I know twrp on pixel oreo has still some troubles.
You can try to put your pin and AFTER (when you are on the main scrren with all the actions) plug the otg. On nougat this worked for me, now I just put the 2 or 3 files in internal storage so I don't use otg anymore from recovery so I don't know if this method works or not.
daddylonglegs said:
Hi,
I am trying to root my Google Pixel on 8.1. I was on Magisk for a long time but I gave up on it because a few root apps I was trying to use aren't compatible.
I read some guides but they are ridiculously out of date. They say to use an experimental version of TWRP because it fails unlock codes and such; a lot of really out of date stuff. Some don't mention the ElementalX step, and then other guides say a custom kernel is required for rooting. But I had root with Magisk and never had to install a custom kernel. Other guides are still telling me to use the signature zips which supposedly hasn't been needed in forever. Trying to piece this all together is causing me to rip my hair out.
Anyway this is what I did, and it kept failing (I kept getting a "patching sepolicy" error in TWRP).
1) I booted the TWRP.img
2) I installed the twrp.zip
3) I booted into recovery
4) I installed Elemental X 13.3 zip
5) I installed SuperSU zip
6) I installed SuperSUHide zip
This isn't working. Every time I try to open SuperSU it says I don't have root. I also get an error every time I boot about their being an internal problem with my hardware and to contact the manufacturer. I believe Elemental X 13.3 is the cause. I wiped my phone and reinstalled stock and I am no longer getting that error.
Can anybody let me know what the deal is? Do I still have to install a custom kernel to install SuperSU? If so, what are the steps? Obviously whatever I am doing is wrong. Thanks so much in advance.
Click to expand...
Click to collapse
Install ElementalX before TWRP if you wish to install TWRP.
SuperSU is no longer maintained and will not work any longer on modern versions of Android until further notice.
About the "internal problem" this can be completely ignored and does not harm the functionality of the device whatsoever.
Magisk 16.3 is the best version of Magisk and mounting USB-OTG shouldn't be problematic whatsoever. Mounting the drive in TWRP has no effect on it mounting in the system and vice-versa.
To mount the OTG in TWRP, plug it in, go to "mount" and select storage location, here you can choose between the internal sdcard and the USB-OTG storage device.
Regarding the mounting of the USB-OTG device in Android the drive must be formatted using a filesystem/partition scheme that Android is capable of mounting. I think FAT32 is the most compatible option.
Applications won't just magically see the external storage unless they're made to support such devices. Google kinda messed up some external storage functionality in Nougat and Oreo, it's kind of quirky. :silly:
Anyone give me any info on where I'm going wrong or why it isn't working?
So I'm on Android 9 - Running stock OS, rooted with Magisk 19.4, custom Kernel SJ1 (MentalMusos)
I've installed both Riru Core (v19.5) and Riru EdExposed (v.0.4.5.1 beta (tried both Yafta & Sandyhook)) via Magisk and installed the XposedInstaller (by dvdandroid) but each time the app tells me the Xposed Framework is not installed. The app also prompts me to update it, which just returns a parsing error.
Also, not sure if relevant, but if I try to flash Riru Core or EdExposed modules via TWRP I get an "unable to mount system" error?
Thanks for any help guys.
Sorry posted in wrong section, thought I was in Q&A. ?*
Update for anyone that's interested...
Managed to get EdExposed installed. Seems DVDandroids apk, is specifically for Xposed. I used the wrong APK the entire time, you need to get the APK from the Magisk module instructions which is specifically for EdExposed (EdExposed Manager by ElderDrivers) - How I didn't notice they were different APKs is shocking and I guess I deserved the bootloop I got. I Think the mishmash of modules I had installed and uninstalled probably caused that. Or maybe because I aborted the setup process that Tab entered into once it rebooted. Learning experience I guess.
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 ...