Develop Bugs

Why won't SuperSU update on CM13?

My Tab Pro 8.4 has been bootloader unlocked since I got it months ago. It has always run a custom ROM, usually just CM12 nightlies with root from SuperSU flashed in TWRP and no Xposed or other "fancy" stuff installed. Since the CM nightlies shifted to CM13 I can't get SuperSU to "update" (the notice that says you must update SuperSU). I've tried reflashing, I've tried wiping and doing new installation from CM13, I've tried different versions of SuperSU. Nothing works to successfully install an updated SuperSU. I've never had this problem before. I've read everything I can find and found several places where something like this is being discussed, but no path to resolution. How can I fix this?

I believe SuperSU doesn't work in CM13. Just use the built-in root method. Open the developer options and use the root method in there.

Sicron said:
I believe SuperSU doesn't work in CM13. Just use the built-in root method. Open the developer options and use the root method in there.
Click to expand...
Click to collapse
I've tried using only the built-in root method. I set it to "both APPS and ABP" (or whatever that last option is). That's not enough for Root Explorer, not enough for PIE Control, not enough for AdAway, at least in my case. All those apps still indicate that I'm not rooted.

Both AdAway and Rootexplorer work fine for me. Actually, I haven't seen a root app that doesn't work with the built-in root.

Sicron said:
Both AdAway and Rootexplorer work fine for me. Actually, I haven't seen a root app that doesn't work with the built-in root.
Click to expand...
Click to collapse
Hmmm. Well, that'd be a great solution for me so I'll give it another go. Wipe wipe wipe, flash a CM13 daily, flash CM13 GAPPS, wipe Dalvic cache and cache, reboot. In Settings, enable Developer Options, set Root Access to Apps and ADB. Reboot. If that's not the recommended procedure I hope someone will let me know.

Sicron said:
Both AdAway and Rootexplorer work fine for me. Actually, I haven't seen a root app that doesn't work with the built-in root.
Click to expand...
Click to collapse
Well, maybe the problem I have is different than the one I THOUGHT I had. Wiped, installed CM13 daily, installed CM13 GAPPS, set Root Access in System/Developer Options/Root Access to Apps and ADB. I guess root access exists but I'm not sure. In Root Explorer I CAN switch folders from Read/Write to Read Only (normally a root only option) and AdAway installed and ran fine. BUT -- in PIE Control I still get "Can not, rooted only" when I try to use the "Back" command. There is often a "hashtag" (or "pound sign") symbol in the Status Bar, just as there would be if I needed to update SuperSU, but the symbol is on the far RIGHT and doesn't correspond to any message in the drop down box. Plus, I have never seen the pop up box that normally appears to ask me if I want to grant root access to an app or process. So, what am I? Partially rooted?

It has full root, sounds like the app needs updating for CM13 and / or other root methods. (not CM13's fault)

otyg said:
It has full root, sounds like the app needs updating for CM13 and / or other root methods. (not CM13's fault)
Click to expand...
Click to collapse
What I'm reading here makes sense but there must be another variable. My phone (Moto X Pure) is running a custom MM ROM, SuperSU DOES install and run just fine, I get all the expected root prompts and controls and the Back button (which requires root) works in PIE Control. I'm guessing, therefore, that the "problem" lies with CM13 as a specific MM ROM rather than with all MM ROMs. Time to flash a different MM ROM on my SM-T320.

How to install Magisk v12.0 root, re-enable Samsung Health, and pass safetynet

sorry guys Magisk currently does not pass safetynet checks (24-06-2017) so this guide is a bit out of date but you can still use it, I will make another guide for this once magisk v13 comes out and fixes this problem
Hi guys! just a quick guide on how to install magisk, re-enable use of Samsung Health, and pass SafetyNet and be play store certified.
This guide will be pretty brief as i don't have the time or commitment to do an in-depth guide and I believe if you are here that you should know what you are doing (if anyone wants to make this in-depth, please be my guest).
this guide is for people who have tripped knox and still want to use s health while still getting the most out of their phone
You will need:
Odin:
https://www.androidfilehost.com/?fid=529152257862705230
TWRP for your device (you should be able to find guides with the download link)(you should also flash back to complete stock if you are already rooted to avoid any problems with previous roots)
no-verity-no-encrypt_ashyx.zip:
https://www.androidfilehost.com/?fid=24591000424951049
Magisk v12.0:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Now that you have those 4 files we can start.
Skip steps 1-6 if you already have root and only wish to use samsung health
1. put magisk v12.0 and dm-verity patch onto the sdcard in the phone
2. flash TWRP using odin
3. boot into recovery and swipe to allow modifications.
4. under wipe there should be a button to format data (its in the bottom right). you will need to do this to flash magisk and dm verity.
5. flash Magisk and THEN dm verity
6a. boot into phone and complete setup to get to home page.
6b. download any systemless root app that you want (adaway works you just have to turn on systemless host files in magisk settings + viper4andriod has a module in magisk that you download for it to work)
(DO NOT TURN ON HIDE MAGISK UNTIL THE END)
7. download the app buildprop editor, open it and grant it root. search for the line ro.config.tima=1 and change the value from 1 to 0.
8. reboot the phone and you should now be able to use s health.
continue following if you wish to pass safetynet and be playstore certified (set up your root apps like viper and adaway before doing this)
9. go into magisk settings and enable the setting Magisk Hide. reboot phone. check that you pass safetynet in magisk manager after booting up again
10. go into app manager, find google play store, tap storage and then clear the data.
11. open app again and you should be certified. (this took me a few tries. not sure if it was play store needing to update the property or me needing to reboot the phone)
12. Yay! your device should now be able to pass safetynet and will be play store certified in the play store app. you should soon be able to see netflix in the play store again.
source: I done this on my a520 just on the weekend to be able to update netflix

I'll try this next update, thnx!

Does this require an external sd card?

korwynkim said:
Does this require an external sd card?
Click to expand...
Click to collapse
Yes i believe so, although I have never tried doing it without

According to the XDA page of Magisk it already supports dm-verity and forceencrypt. So is the separate download of no-verity-no-encrypt_ashyx.zip still necessary?
Edit: What does the change " ro.config.tima=0" do?

reayard said:
According to the XDA page of Magisk it already supports dm-verity and forceencrypt. So is the separate download of no-verity-no-encrypt_ashyx.zip still necessary?
Edit: What does the change " ro.config.tima=0" do?
Click to expand...
Click to collapse
oh i did not know that it supported it already so maybe its not? not sure, try it out and see what happens?
the config change make it so that the rom thinks you still have knox enabled to you are able to use samsung health still (it got a "security update" that makes it so that phones with knox tripped will not be able to use it)

Good to know ! Thank so much !
But what's the real possibilities of this recent "magisk" ?
It can root with systemless ?
And in theory with systemless-root ,that don't trip the knox and we can use all apps and full hardware ....because it consider that the system is safe and untouched ===> i'm truth or wrong ?

Loulou-13 said:
And in theory with systemless-root ,that don't trip the knox...
Click to expand...
Click to collapse
According to some other threads (and if I remember correctly from my own experience with the S7) Knox gets triggered as soon as you flash a custom recovery.
A positive effect of Magisk vs. SuperSU could be that system updates are still possible as the system partition is still unchanged. On the other hand the custom recovery will most probably cause the update to fail.
What seems to make Magisk superior to SuperSU is MagiskHide so that the system appears to be unchanged for PlayStore and apps using SafetyNet.

reayard said:
According to some other threads (and if I remember correctly from my own experience with the S7) Knox gets triggered as soon as you flash a custom recovery.
A positive effect of Magisk vs. SuperSU could be that system updates are still possible as the system partition is still unchanged. On the other hand the custom recovery will most probably cause the update to fail.
What seems to make Magisk superior to SuperSU is MagiskHide so that the system appears to be unchanged for PlayStore and apps using SafetyNet.
Click to expand...
Click to collapse
Thank so much for sharing Samsung experience
Before i have had olds goods samsung fully customised ! It was funny before ,at this time ....and then always have had LG phones and just an unlock of bootloader+Systemless root din't have problem at all (full playstore&experience)
Now with the samsung evolution and my new A5 ,i don't want at all loose OTA updates,knox flag.... and all functions+playstore as you have said . And magisk is recent...
I want to be sure at 100....0000% that "magisk" systemless root doesn't affect anything .
i'm not interested at all by TWRP ...completely useless until there eventually have "real" customs developments and many things can be flashed by flashfire,flashify....

Loulou-13 said:
I want to be sure at 100....0000% that "magisk" systemless root doesn't affect anything .
i'm not interested at all by TWRP ...completely useless until there eventually have "real" customs developments and many things can be flashed by flashfire,flashify....
Click to expand...
Click to collapse
I doubt that FlashFire or Flashify can flash anything without root. The website of FlashFire for example says "FlashFire is the most advanced on-device firmware flasher available for rooted Android devices.". And the same for Flashify: [APP][4.0+][ROOT] Flashify.

reayard said:
I doubt that FlashFire or Flashify can flash anything without root. The website of FlashFire for example says "FlashFire is the most advanced on-device firmware flasher available for rooted Android devices.". And the same for Flashify: [APP][4.0+][ROOT] Flashify.
Click to expand...
Click to collapse
Yes yes....sure...i didn't have precised...
Root with a method who din't need twrp and don't touch samsung things....and then flash what we want with these apps ...

Hi, Im XxViRUsPRO.
1.You Need Magisk Manager (Removed Form PlayStore) So this is the Download Link https://mega.nz/#!olRzFRTZ!eNOb6yVtvsAlb3V8sIOaRRfsHtQG952_WU--3TCDvck
2.To Use S Health On Rooted Phone You Need To Edit /System/Build.prop
and Change ro.config.tima=1 to ro.config.tima=0 using (Es File Explorer or Root Browser)

safety net check does not pass in Samsung galaxy a5 2015
What is this dm verity and for encryption? I have the latest magisk and i see those options in my magisk manager but donot know its utilization! and probably for the same reason my safety net check does not pass in Samsung galaxy a5 2015
reayard said:
According to the XDA page of Magisk it already supports dm-verity and forceencrypt. So is the separate download of no-verity-no-encrypt_ashyx.zip still necessary?
Edit: What does the change " ro.config.tima=0" do?
Click to expand...
Click to collapse

Dis any one could enable the fm chip in nougat once rooted ,in Canada Samsung disable the fm chip and i would get it back

why does flashing magisk wipes all user data including internal storage?

Samsung A5 sm-a500f

Solved - Working Non Stock Rom for Android Pay on M8

I am looking for any ROM that can be installed and allows Android Pay to work. I sometimes forget my wallet and would like to have the ability to use Android Pay. I was excited when I got AICP to install and pass safety check, but it doesn`t actually work at the terminal. I now read that all AOSP based roms have problems with NFC payments.
Does anyone have this working on an M8. There are some old threads, but none that actually report that it works.

Are you rooted with Magisk?

redpoint73 said:
Are you rooted with Magisk?
Click to expand...
Click to collapse
Yes. So far I have tried AICP 7.1 Rom, which passed safetynet check, but would not actually work on a store's terminal. Perhaps an NFC issue with AOSP Rom? I also tried Lineage 15, but could not get it to recognize google play services and could not get the play store to work as a result. I am now on lineage 14.1, which agains passes safetynet check but will not work at the terminal.
As I am aware, Magisk only allows Android Pay to be installed, but when it comes time to validate the purchase, there is either an NFC problem or something prevents the purchase from being validated.
So if anyone has a non stock rom that works with android pay on the m8, I would like to know about it. There have been a few threads, but none seem to offer a current resolution.

I'm not personally a user of AOSP ROMs, nor Android Pay, so my advice is limited. Just chiming in, as long as you are passing SafetyNet, and have Magisk Hide enabled (in Magisk Manager settings) than I don't think it's a safety net or root issue. Like you said, it might be an issue with AOSP ROMs and NFC.

I tried Resurrection Remix. Same result. Passed safety check but would not work at the store terminal.

Cannot use payments on nougat. Have to go to marshmellow.
NFC works, but HCE does not, which is whats required.

Success. I went to ViperOneM8 6.1.0. Installed the rom. Then deactivated Su in the Su app. Then properly installed Magisk by creating a new boot.img file and then flashing that new boot.img file with twrp. Magisk 14 showed safetynet passed both test. Off I went to the store to buy a chocolate bar, unlocked the phone, tapped it on the terminal and buzz buzz, payment approved. Very nice.

Issues bypassing apps on rooted rom

Hey folks, I have a note 10+ n975f and used to root all my older phones in past for freedom and a bit of a change to customising etc... Anyhow tried using magisk to disguised my banking apps before on other phones but them and a few others still won't work, the apps crash, tried a few rooms and all do the se thing, restored phone to factory and they all work. As its been years since I used to root my phones am I missing something? I've followed as many guided here as I can but can't seem to get around this issue.

possible the apps have learnt to detect it better, security is a cat and mouse game and firms are getting better at stopping people using their stuff on devices they don't want them to, you may have to look into certain apps for specific ways to bypass the detection. but chances are a lot of apps are now designed to detect the things blocking the detection of the phone being unlocked.
sad fact is if you want to use secure stuff on your phone the only really bulletproof option is to keep the phone locked.

Yea I know what you mean. Aww I used to have oneplus 6 and it's software was amazing but love the note for its size and camera etc but software just seems so bloated and it's got double the ram like

I know what you mean, but for me personally I just disable the stuff I don't need and use Lawnchair launcher to get the phone running like a Pixel device, but on the other hand the Samsung software can often give extra features that havent gone into base Android yet.

I had apps that wouldn't work because it detected root. So I did this: Magisk/Settings/Hide Magisk Manager. My apps worked after that.

Eagle 3 said:
I had apps that wouldn't work because it detected root. So I did this: Magisk/Settings/Hide Magisk Manager. My apps worked after that.
Click to expand...
Click to collapse
Thanks for the reply however not meaning to be rude, I stated I already tried Magisk in the original post. It doesn't work for some apps like banking apps etc.

cruisinbeatz said:
Thanks for the reply however not meaning to be rude, I stated I already tried Magisk in the original post. It doesn't work for some apps like banking apps etc.
Click to expand...
Click to collapse
You were very unclear about what you did in Magisk. Did you use Magisk Hide or Hide Magisk Manager?

Eagle 3 said:
You were very unclear about what you did in Magisk. Did you use Magisk Hide or Hide Magisk Manager?
Click to expand...
Click to collapse
I used Magisk Hide from what I recall. Opened it up, safenet etc was all green and good to go, it worked for snapchat etc but would not work on 3 of my banking apps, those are the only ones it wouldn't work on. From memory, I when I opened Magisk, I checked safety net was goo, it was. so went and hid root from each app I knew would look for safety net. The apps in question are Co-Operative Bank, Ulsterbank and Dansk (Mobile Bank in store) They will not open, they try, a quick flash on the screen and it returns back to home screen. Tried 3 different roms and they all done same thing.

cruisinbeatz said:
I used Magisk Hide from what I recall. Opened it up, safenet etc was all green and good to go, it worked for snapchat etc but would not work on 3 of my banking apps, those are the only ones it wouldn't work on. From memory, I when I opened Magisk, I checked safety net was goo, it was. so went and hid root from each app I knew would look for safety net. The apps in question are Co-Operative Bank, Ulsterbank and Dansk (Mobile Bank in store) They will not open, they try, a quick flash on the screen and it returns back to home screen. Tried 3 different roms and they all done same thing.
Click to expand...
Click to collapse
As I stated in my first reply to you, you need to Hide Magisk Manager. This is different than Magisk Hide. Go to Settings and select Hide Magisk Manager. You will get a popup for new name, leave it as Manager, tap OK.
Then open Manager, you will get a message to update Magisk Manager, tap OK.
Restart the phone. Your banking apps should work now.
I had the same problem as you in that the apps didn't work by just selecting the apps in Magisk Hide. They did after Hide Magisk Manager. So you have to do both.

Intune on rooted OP7T

When I first got my 7T I managed to root it and install Intune rather easily - just hid a bunch of things in Magisk Hide. Last night I boneheadedly reset my device to factory settings and had to start all over again. However when I attempted to install Intune root was detected. Tried removing device from company portal, clearing cache, uninstalling, reinstalling, adding a bunch more things to Magisk Hide - no luck, root is always detected.
Two questions to get me going
a) I used to be on an older version of Magisk Manager, don't remember which one, but am now on the newest version. Has anyone had any luck with MH and Intune with the latest versions
b) I vaguely recall that once Intune detects a root it "brands" the device serial number and the only way to work around that is to change the serial number. Is that correct?
Thanks

You musst rename the magisk manager with random name on magisk settings and hide root then it should work again

ChrisFeiveel84 said:
You musst rename the magisk manager with random name on magisk settings and hide root then it should work again
Click to expand...
Click to collapse
Nope. I had done that and it did not work. Just tried it with the old MM (7.5.1) and it worked beautifully. That is why I never update Magisk once I get it running on a particular device

I only use the latest version of magisk canary myself and haven't had any problems so far (so far I haven't found an app that recognized the root despite magisk hide)

Interesting. Does this include Intune? I saw TopJonWu post on twitter that the latest version handles Intune "out if the box" but that is not my experience so far.