Related
Just heard Super Mario Run has came out on android but its not showing as supported for my HTC 10 on the play store?? I tried the app from an alternative store and got an error message after being able to do the first level. Why would the HTC 10 not be supported. would a build prop edit make it work?
Edit: Looks like it might be because Im rooted, going to try Magisk.
Edit 2: seems to be working with Magisk installed, still not available on playstore though.
I installed it through the play store without any problem(root-magisk)
fratorga100 said:
I installed it through the play store without any problem(root-magisk)
Click to expand...
Click to collapse
I'm glad this is working for someone.
Perhaps you could add some insight into what my issue may be? I'm sure others might be experiencing it.
I've Magisk v11.6 installed, "Properly rooted" via 2.79 SuperSu.
SafetyNet Failed: CTS Profile mismatch- is occurring though.
I followed these steps, but no success.
What could I try? Does anyone have advice?
I have downloaded it, and played the game successfully. I am stock, non-rooted. I have the unlocked version sold from HTC.
typhoonikan said:
I'm glad this is working for someone.
Perhaps you could add some insight into what my issue may be? I'm sure others might be experiencing it.
I've Magisk v11.6 installed, "Properly rooted" via 2.79 SuperSu.
SafetyNet Failed: CTS Profile mismatch- is occurring though.
I followed these steps, but no success.
What could I try? Does anyone have advice?
Click to expand...
Click to collapse
If you flashed Magisk, it would (attempt to) remove SuperSU and replace it with MagiskSU afaik. Incorrect on my part, apologies. It only removes SuperSU if it is not systemless.
If you have SuperSU, I think that may be the issue but I am not entirely sure. I remember issues with Magisk hide and SuperSU back on an earlier build.
EDIT: Have you togged Super Mario Run in the Magisk hide section of the Magisk Manager app?
tokuzumi said:
I have downloaded it, and played the game successfully. I am stock, non-rooted. I have the unlocked version sold from HTC.
Click to expand...
Click to collapse
Yes, it is working for un-rooted users. Rooted users, not so well in most cases.
Ariac Konrel said:
If you flashed Magisk, it would (attempt to) remove SuperSU and replace it with MagiskSU afaik. Incorrect on my part, apologies. It only removes SuperSU if it is not systemless.
If you have SuperSU, I think that may be the issue but I am not entirely sure. I remember issues with Magisk hide and SuperSU back on an earlier build.
EDIT: Have you togged Super Mario Run in the Magisk hide section of the Magisk Manager app?
Click to expand...
Click to collapse
Yes. I am able to run the tutorial level, then I receive error 804-5100.
typhoonikan said:
I'm glad this is working for someone.
Perhaps you could add some insight into what my issue may be? I'm sure others might be experiencing it.
I've Magisk v11.6 installed, "Properly rooted" via 2.79 SuperSu.
SafetyNet Failed: CTS Profile mismatch- is occurring though.
I followed these steps, but no success.
What could I try? Does anyone have advice?
Click to expand...
Click to collapse
you need magisk SU to be able to use magisk hide and pass safety net. supersu won't work.
I can not install magisk modules and my device constantly loses its root without a reason.
I have the same problem. Magisk seems to be still buggy. But at least I haven't seen the "losing root" issue after disabling "Magisk Hide" in the settings.
Thanks
romhippo.com said:
I have the same problem. Magisk seems to be still buggy. But at least I haven't seen the "losing root" issue after disabling "Magisk Hide" in the settings.
Click to expand...
Click to collapse
Thanks Romhippo.com for responding!
If anyone knows more about it, I'd be happy to know.
Had that issue on a One Plus 3T. Finally updated Magisk in the app and it fixed itself. Was really flakey on root.
larsdennert said:
Had that issue on a One Plus 3T. Finally updated Magisk in the app and it fixed itself. Was really flakey on root.
Click to expand...
Click to collapse
Cool! I hope they also correct here.
Loosing root + possible fix
I was getting the same problem, magisk loosing root and phone getting encryptation problems... making me to format my phone twice.
After i noticed the problem was with magisk 13.3, so i tried to install 13.6 beta but no success, it give me error "Unable to detect boot image" during instalation.
Then i decided to mod magisk zip file (updater_script) , installed then and jrummy busybox (I think oldversions are conflicting with magiskSu)... and now i got 2 days without problem.
Magisk 13.6 beta modded
https://drive.google.com/open?id=0B1UKyTc_LCSOc09UMFhHNVFTd1U
raphamfc said:
I was getting the same problem, magisk loosing root and phone getting encryptation problems... making me to format my phone twice.
After i noticed the problem was with magisk 13.3, so i tried to install 13.6 beta but no success, it give me error "Unable to detect boot image" during instalation.
Then i decided to mod magisk zip file (updater_script) , installed then and jrummy busybox (I think oldversions are conflicting with magiskSu)... and now i got 2 days without problem.
Magisk 13.6 beta modded
https://drive.google.com/open?id=0B1UKyTc_LCSOc09UMFhHNVFTd1U
Click to expand...
Click to collapse
LoL Many thanks for your help. It's all normal here.
I'm going to agree on conflict issues being the likely cause. Between custom roms having su built in like Resurrection remix, SuperSU and standalone magisk, there are plenty of possibilities for messed up boot images.
In fact, 2 things bother me the most.
1. I can not install magisk modules
2. The magisk does not pass SafetyNet.
I do not know if that happens to you.
My Z2 is a verizon one so this is where my advice stops on that phone. I've Magisk on the 3T and pixel only
anyone have a guide to install Magisk?
Refer the following threads completely. Junior answered all my querries. His Moto Brazil blog has systematic and structured guides as well. Very well done.
https://forum.xda-developers.com/z2-play/help/indian-stock-firmware-xt1710-10-t3711423
http://motozbrasil.blogspot.in/search/label/TutorialZ2Play
Upgrading to OOS 4.7.4 has fixed this for me.
Hi guys,
Just got this phone the other day and it seems that I can't get adaway to actually block any ads? I got magisk su, the app works (I can grant it root, it updates the hosts files successfully, I've rebooted, etc) but none of the ads in chrome actually get blocked, for example.
I've done this for every other phone I've previously had without issue, so I was wondering if you have any thoughts around what might be happening?
Thanks.
NSD said:
Hi guys,
Just got this phone the other day and it seems that I can't get adaway to actually block any ads? I got magisk su, the app works (I can grant it root, it updates the hosts files successfully, I've rebooted, etc) but none of the ads in chrome actually get blocked, for example.
I've done this for every other phone I've previously had without issue, so I was wondering if you have any thoughts around what might be happening?
Thanks.
Click to expand...
Click to collapse
Did you tried togling systemless hosts switch in Magisk Manager?
It will be usefull if you inform exact version of OOS, Magisk and Adaway
NSD said:
I've done this for every other phone I've previously had without issue, so I was wondering if you have any thoughts around what might be happening?
Click to expand...
Click to collapse
Have you enabled systemless hosts in Magisk settings?
Edit: someone beat me to it
Flint2 said:
Did you tried togling systemless hosts switch in Magisk Manager?
It will be usefull if you inform exact version of OOS, Magisk and Adaway
Click to expand...
Click to collapse
I have tried with it both enabled and disabled (and with reboots in between). The box in Adaway gets checked automatically as well.
In terms of versions:
OOS: 4.7.2
Magisk: 14.0
Adaway: 3.2
https://app.box.com/s/h43do6fi37x9s8vj8qr0dsstlsw01qw1
try this version of adaway.for me this works.
beaverhead said:
https://app.box.com/s/h43do6fi37x9s8vj8qr0dsstlsw01qw1
try this version of adaway.for me this works.
Click to expand...
Click to collapse
Hmm no dice
NSD said:
Hmm no dice
Click to expand...
Click to collapse
You probably use FreedomOS rom right? More people complained about it from what I've read there
benno4403 said:
You probably use FreedomOS rom right? More people complained about it from what I've read there
Click to expand...
Click to collapse
No, I'm on Oxygen 4.7.2.
Not sure what to tell you. I have stock OOS, rooted with Magisk 14.0, using AdAway 3.2.
Attached are my settings. Check and see?
Thanks everyone for your suggestions. Oddly enough, upgrading to OOS 4.7.4 has fixed this for me. Will update the initial post in case anyone else runs into the same problem.
Can anyone confirm if Magisk root works with the 8.1 release?
It Works
Its working but when you reboot the device I'm getting the "there's an internal problem with your device " which has to do with a mismatch between the Vendor and System Partitions. Only happens after flashing the 14.5(1456) Build either from TWRP or using the boot.img patcher in Magisk Manager. Not sure how to fix this error but otherwise everything is working.
Edit: Picture for reference
Edit 2: Root, safetynet pass, and modules are all working just an annoying error message on boot.
Edit 3: Known issue with the 1456 build of Magisk. Developers are already aware of it. Information below.
topjohnwu said:
The additional avb-verity removal from DTBO on the Pixel 2 devices results in a scary pop-up. No need to worry here, it's Google warning you that your vendor partition doesn't work as expected. I decided to strip off avb-verity to make modifications to the vendor partition possible, as people tend to modify their partitions a lot, and not sure if this might save a few soft brick devices.... As the old dm-verity and avb-verity works so different, it is very difficult for me to come up with a proper way that doesn't complicate things on the user side.
Click to expand...
Click to collapse
Itachisasuke said:
Its working but when you reboot the device I'm getting the "there's an internal problem with your device " which has to do with a mismatch between the Vendor and System Partitions. Only happens after flashing the 14.5(1456) Build either from TWRP or using the boot.img patcher in Magisk Manager. Not sure how to fix this error but otherwise everything is working.
Click to expand...
Click to collapse
Yep, Magisk works....unfortunately the error upon boot is there. Prior to Magisk, 8.1 didn't show the error. After the Magisk flash, the error always pops up upon start up.
Guess I'll wait with re-rooting then.
Colchiro said:
Guess I'll wait with re-rooting then.
Click to expand...
Click to collapse
Why, it still works fine. Just ignore the message :good:
Badger50 said:
Why, it still works fine. Just ignore the message :good:
Click to expand...
Click to collapse
Does it still pass Safetynet?
MrBrady said:
Does it still pass Safetynet?
Click to expand...
Click to collapse
Yup :good:
The error is just an annoyance, you still have root and pass safety net. I used Magisk on the last Beta build and got the same error It did not impact anything.
Sav_Droid said:
Yep, Magisk works....unfortunately the error upon boot is there. Prior to Magisk, 8.1 didn't show the error. After the Magisk flash, the error always pops up upon start up.
Click to expand...
Click to collapse
14.4 doesn't show the error message, but fails the SafetyNet check. Android Pay still works, though.
Do you need to flash stock 8.0 boot.img before applying 8.1 OTA?
swooperstar said:
Do you need to flash stock 8.0 boot.img before applying 8.1 OTA?
Click to expand...
Click to collapse
Yes I would def uninstall magisk before going on to 8.1 and flash boot.img to both slots
lucky_strike33 said:
Yes I would def uninstall magisk before going on to 8.1 and flash boot.img to both slots
Click to expand...
Click to collapse
I didn't.
Sideloading the new OTA will overwrite the patched image
Just curious, but wondering why people are in such a rush to install 8.1. With all of the contact sync issues oh, this would drive me absolutely crazy. I might just wait until January to update unless there is a quick fix.
Cowbell_Guy said:
Just curious, but wondering why people are in such a rush to install 8.1. With all of the contact sync issues oh, this would drive me absolutely crazy. I might just wait until January to update unless there is a quick fix.
Click to expand...
Click to collapse
Probably just because we can. We flashaholics gotta have our fix! Everything is working fine on my end. Then again, all my contacts are synced through Gmail :good:
Cowbell_Guy said:
Just curious, but wondering why people are in such a rush to install 8.1. With all of the contact sync issues oh, this would drive me absolutely crazy. I might just wait until January to update unless there is a quick fix.
Click to expand...
Click to collapse
Contact sync issues? Never had that before.. what's the issue exactly? Not getting all of them or all the info?
You can get rid of the error message by rooting with Magisk, then uninstalling Magisk Manager, reflashing the stock (or your kernel's) dtbo, then rebooting and reinstalling Magisk Manager. Passes SafetyNet and have full root.
jbarcus81 said:
Contact sync issues? Never had that before.. what's the issue exactly? Not getting all of them or all the info?
Click to expand...
Click to collapse
Some Google contacts aren't syncing since installing the 8.1 official release. I have this issue and so do many others. There's a thread taking about it in this section already. It effected almost all of the contacts I talk to the most.
There is a workaround. Go into the web interface of Google contacts on your computer and edit the contract to reminder their profile URL and it forces the sync to go through for that contact. I did this for my 10 most frequent contacts. However, this would be a nightmare to do for every contact.
Google development is aware of the issue and working on a fix.
---------- Post added at 03:27 AM ---------- Previous post was at 03:27 AM ----------
gettingerr said:
You can get rid of the error message by rooting with Magisk, then uninstalling Magisk Manager, reflashing the stock (or your kernel's) dtbo, then rebooting and reinstalling Magisk Manager. Passes SafetyNet and have full root.
Click to expand...
Click to collapse
What's "dtbo"?
Yeah I did this too and bam,,,error message on boot gone LOL,,,just have to stay with Magisk Manager 5.4.0 and not update through Magisk. But it all works, safety net pass.
gettingerr said:
You can get rid of the error message by rooting with Magisk, then uninstalling Magisk Manager, reflashing the stock (or your kernel's) dtbo, then rebooting and reinstalling Magisk Manager. Passes SafetyNet and have full root.
Click to expand...
Click to collapse
Archangel said:
Yeah I did this too and bam,,,error message on boot gone LOL,,,just have to stay with Magisk Manager 5.4.0 and not update through Magisk. But it all works, safety net pass.
Click to expand...
Click to collapse
I actually was curious what would happen if I used the latest Magisk Manager, and nothing happened. So I am using the latest. No error and no issues that I can note. Except maybe installing modules if you're into that sort of thing.
---------- Post added at 05:07 AM ---------- Previous post was at 05:06 AM ----------
sn0warmy said:
What's "dtbo"?
Click to expand...
Click to collapse
No clue. http://lmgtfy.com/?q=dtbo
I didn't read the links but maybe something there can explain it.
hey guys,
I was just trying to root so I can fix a broken alert slider problem.
Everything was going smoothly until trying to install the supersu.zip from TWRP.
No matter what I try, I can't seem to get it to install (downgraded to an older oneplus kernel, tried a more srecent version of supersu..)
The installation process stops at
- Patching sepolicy
--- Failure, aborting
What is the problem here? It does not seem to be a common issue so I am wondering what would cause it to occur on my phone and also how to install supersu.
Any help would be appreciated. Thanks!
oppp3 said:
hey guys,
I was just trying to root so I can fix a broken alert slider problem.
Everything was going smoothly until trying to install the supersu.zip from TWRP.
No matter what I try, I can't seem to get it to install (downgraded to an older oneplus kernel, tried a more srecent version of supersu..)
The installation process stops at
- Patching sepolicy
--- Failure, aborting
What is the problem here? It does not seem to be a common issue so I am wondering what would cause it to occur on my phone and also how to install supersu.
Any help would be appreciated. Thanks!
Click to expand...
Click to collapse
Try magisk
oppp3 said:
hey guys,
I was just trying to root so I can fix a broken alert slider problem.
Everything was going smoothly until trying to install the supersu.zip from TWRP.
No matter what I try, I can't seem to get it to install (downgraded to an older oneplus kernel, tried a more srecent version of supersu..)
The installation process stops at
- Patching sepolicy
--- Failure, aborting
What is the problem here? It does not seem to be a common issue so I am wondering what would cause it to occur on my phone and also how to install supersu.
Any help would be appreciated. Thanks!
Click to expand...
Click to collapse
If you are on Oreo, flashing Magisk will solve the issue.
i too am having this issue. Installing magisk fixes the issue or it's just a bandaid? I don't really care for magisk and SuperSU is what I really want. I have 2 app that won't work without SuperSU
PizzaG said:
i too am having this issue. Installing magisk fixes the issue or it's just a bandaid? I don't really care for magisk and SuperSU is what I really want. I have 2 app that won't work without SuperSU
Click to expand...
Click to collapse
It is not a bandaid. Magisk has overtaken Supersu long back. It will fix this issue.